WO2023116355A1 - 通信方法、装置、相关设备及存储介质 - Google Patents

通信方法、装置、相关设备及存储介质 Download PDF

Info

Publication number
WO2023116355A1
WO2023116355A1 PCT/CN2022/134805 CN2022134805W WO2023116355A1 WO 2023116355 A1 WO2023116355 A1 WO 2023116355A1 CN 2022134805 W CN2022134805 W CN 2022134805W WO 2023116355 A1 WO2023116355 A1 WO 2023116355A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
data
application
signaling
merging
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2022/134805
Other languages
English (en)
French (fr)
Inventor
种璟
游正朋
唐小勇
朱磊
赵立君
李颖
张鸿佳
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Mobile Communications Group Co Ltd
China Mobile Chengdu ICT Co Ltd
Original Assignee
China Mobile Communications Group Co Ltd
China Mobile Chengdu ICT Co Ltd
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 China Mobile Communications Group Co Ltd, China Mobile Chengdu ICT Co Ltd filed Critical China Mobile Communications Group Co Ltd
Publication of WO2023116355A1 publication Critical patent/WO2023116355A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]

Definitions

  • the present application relates to the communication field, and in particular to a communication method, device, related equipment and storage medium.
  • MEC Mobile Edge Computing
  • 5G fifth generation mobile communication technology
  • IT Information Technology
  • CPE Customer Premise Equipment
  • CPE Customer Premise Equipment
  • Embodiments of the present application provide a communication method, device, related equipment, and storage medium.
  • the embodiment of the present application provides a communication method applied to the first device, including:
  • the service data is obtained by combining at least one piece of first data.
  • the method also includes:
  • the first signaling is used to describe the service transmission performance;
  • the first request is based on the transmission performance parameters of the first network and/or the transmission of the second network Determination of performance parameters;
  • the method also includes:
  • the first instruction includes at least one of the following:
  • An identifier of the first device a network type of the first network, a local configuration identifier, and a second merging policy.
  • the second merging strategy includes at least one of the following:
  • the identification of the application the type of traffic ratio allocation for each application, the length of the traffic ratio allocation for each application, and the traffic ratio allocation strategy for each application;
  • the flow ratio distribution type is represented by numbers and/or character strings
  • the flow proportional distribution length is represented by numbers
  • the traffic proportion allocation policy is represented by a character string and/or a codebook index.
  • the local configuration identifier is used to indicate whether the first device performs data merging according to the second merging policy sent by the second device.
  • the priority of the first merging strategy is higher than the priority of the second merging strategy in the first instruction.
  • the first signaling is used to indicate at least one of the following:
  • the identifier of the first device The identifier of the first device, the network type of the first network, the network connection status of the first network, and the performance information of the application program.
  • the sending the first signaling to the second device includes at least one of the following:
  • the aperiodically sending the first signaling to the second device includes:
  • the first signaling is sent to the second device.
  • the transmission performance parameters include at least one of the following: throughput, delay, and packet loss rate.
  • the first data is data transmitted through the first network.
  • the first network is a network between the target device and the first device
  • the second network is a network between the first device and the second device.
  • the embodiment of the present application provides a communication method applied to a second device, including:
  • Service data from the first device is received; the service data is obtained by combining at least one piece of first data.
  • the method also includes:
  • the first signaling is used to describe the service transmission performance;
  • the first request is based on the transmission performance parameters of the first network and/or the transmission performance parameters of the second network Determination of transmission performance parameters;
  • the first signaling is used to indicate at least one of the following:
  • the identifier of the first device The identifier of the first device, the network type of the first network, the network connection status of the first network, and the performance information of the application program.
  • the first instruction includes at least one of the following:
  • An identifier of the first device a network type of the first network, a local configuration identifier, and a second merging policy.
  • the second merging strategy includes at least one of the following:
  • the identification of the application the type of traffic ratio allocation for each application, the length of the traffic ratio allocation for each application, and the traffic ratio allocation strategy for each application;
  • the flow ratio distribution type is represented by numbers and/or character strings
  • the flow proportional distribution length is represented by numbers
  • the traffic proportion allocation policy is represented by a character string and/or a codebook index.
  • the local configuration identifier is used to indicate whether the first device performs data merging according to the second merging policy sent by the second device.
  • the priority of the first merging policy saved by the first device is higher than the priority of the second merging policy in the first instruction.
  • the transmission performance parameters include at least one of the following: throughput, delay, and packet loss rate.
  • the first data is data transmitted through the first network.
  • the first network is a network between the target device and the first device
  • the second network is a network between the first device and the second device.
  • the embodiment of the present application provides a communication device, which is set on the first device, including:
  • the first communication unit is configured to send service data to the second device; the service data is obtained by combining at least one piece of first data.
  • the first communication unit is configured to send a first signaling and/or a first request to the second device; the first signaling is used to describe service transmission performance; the The first request is determined according to transmission performance parameters of the first network and/or transmission performance parameters of the second network;
  • the first device further includes: a first processing unit configured to merge the at least one first data according to a preset first merge policy and/or the first instruction , to obtain the business data.
  • the first instruction includes at least one of the following:
  • An identifier of the first device a network type of the first network, a local configuration identifier, and a second merging policy.
  • the second merging strategy includes at least one of the following:
  • the identification of the application the type of traffic ratio allocation for each application, the length of the traffic ratio allocation for each application, and the traffic ratio allocation strategy for each application;
  • the flow ratio distribution type is represented by numbers and/or character strings
  • the flow proportional distribution length is represented by numbers
  • the traffic proportion allocation policy is represented by a character string and/or a codebook index.
  • the local configuration identifier is used to indicate whether the first device performs data merging according to the second merging policy sent by the second device.
  • the priority of the first merging strategy is higher than the priority of the second merging strategy in the first instruction.
  • the first signaling is used to indicate at least one of the following:
  • the identifier of the first device The identifier of the first device, the network type of the first network, the network connection status of the first network, and the performance information of the application program.
  • the first communication unit is configured to perform at least one of the following:
  • the first communication unit is configured to send the first signaling to the second device when it is determined that the transmission performance parameter of the first network exceeds a preset threshold.
  • the transmission performance parameters include at least one of the following: throughput, delay, and packet loss rate.
  • the first data is data transmitted through the first network.
  • the first network is a network between the target device and the first device
  • the second network is a network between the first device and the second device.
  • the embodiment of the present application provides a communication device, which is set on the second device, including:
  • the second communication unit is configured to receive service data from the first device; the service data is obtained by combining at least one piece of first data.
  • the second communication unit is configured to receive the first signaling and/or the first request sent by the first device; the first signaling is used to describe service transmission performance; the The first request is determined according to the transmission performance parameters of the first network and/or the transmission performance parameters of the second network;
  • the second device may further include: a second processing unit configured to generate the first instruction.
  • the first signaling is used to indicate at least one of the following:
  • the identifier of the first device The identifier of the first device, the network type of the first network, the network connection status of the first network, and the performance information of the application program.
  • the first instruction includes at least one of the following:
  • An identifier of the first device a network type of the first network, a local configuration identifier, and a second merging policy.
  • the second merging strategy includes at least one of the following:
  • the identification of the application the type of traffic ratio allocation for each application, the length of the traffic ratio allocation for each application, and the traffic ratio allocation strategy for each application;
  • the flow ratio distribution type is represented by numbers and/or character strings
  • the flow proportional distribution length is represented by numbers
  • the traffic proportion allocation policy is represented by a character string and/or a codebook index.
  • the local configuration identifier is used to indicate whether the first device performs data merging according to the second merging policy sent by the second device.
  • the priority of the first merging policy saved by the first device is higher than the priority of the second merging policy in the first instruction.
  • the transmission performance parameters include at least one of the following: throughput, delay, and packet loss rate.
  • the first data is data transmitted through the first network.
  • the first network is a network between the target device and the first device
  • the second network is a network between the first device and the second device.
  • the embodiment of the present application provides a first device, including: a first processor and a first communication interface; wherein,
  • the first communication interface is configured to send service data to the second device; the service data is obtained by combining at least one piece of first data.
  • the first processor is configured to combine the at least one piece of first data according to a preset first combination policy and/or the first instruction to obtain the service data .
  • the first communication interface is further configured as:
  • the first signaling is used to describe the service transmission performance;
  • the first request is based on the transmission performance parameters of the first network and/or the transmission of the second network Determination of performance parameters;
  • the first communication interface is further configured as:
  • the first communication interface is further configured as:
  • the first signaling is sent to the second device.
  • the embodiment of the present application provides a second device, including: a second processor and a second communication interface; wherein,
  • the second communication interface is configured to receive service data from the first device; the service data is obtained by combining at least one piece of first data.
  • the second communication interface is further configured as:
  • the first signaling is used to describe the service transmission performance;
  • the first request is based on the transmission performance parameters of the first network and/or the transmission performance parameters of the second network Determination of transmission performance parameters;
  • the second processor is configured to generate the first instruction.
  • the embodiment of the present application further provides a network device, including: a processor and a memory configured to store a computer program that can run on the processor, wherein the processor is configured to run the computer program When, execute the steps of any one of the methods described above on the first device side; or, when the processor is configured to run the computer program, execute the steps of any one of the methods described above on the second device side.
  • a network device including: a processor and a memory configured to store a computer program that can run on the processor, wherein the processor is configured to run the computer program When, execute the steps of any one of the methods described above on the first device side; or, when the processor is configured to run the computer program, execute the steps of any one of the methods described above on the second device side.
  • the embodiment of the present application also provides a storage medium on which a computer program is stored, and when the computer program is executed by a processor, the steps of any one of the methods on the first device side are implemented; or, the When the computer program is executed by the processor, the steps of any one of the methods on the second device side are implemented.
  • the communication system, method, device, first device, second device, and storage medium provided in the embodiments of the present application includes: the first device sends service data to the second device; the service data is obtained based on at least one first data combination ; The second device receives service data from the first device; the service data is obtained by combining at least one piece of first data.
  • the solution of the embodiment of the present application implements the combination of the first data on the first device, and sends the combined service data to the second device. In this way, the differentiated requirements of the first data of different networks can be met.
  • FIG. 1 is a schematic diagram of a system structure of an MEC in the related art
  • FIG. 2 is a schematic structural diagram of a host layer and a system layer of an MEC in the related art
  • FIG. 3 is a schematic flow diagram of a CPE accessing an MEC system in the related art
  • FIG. 4 is a schematic diagram of a routing scheme of a CPE in the related art
  • Fig. 5 is the structure diagram of the IP header of the network layer in the related art
  • Figure 6(a) is a schematic diagram of an IP quintuple before passing through the CPE in the related art
  • Figure 6(b) is a schematic diagram of another quintuple after passing through CPE in the related art
  • FIG. 7 is a schematic diagram of a business scenario of an application embodiment of the present application.
  • FIG. 8 is a schematic flowchart of a communication method provided by an embodiment of the present application.
  • FIG. 9 is a schematic flowchart of another communication method provided by the embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a communication system provided by an embodiment of the present application.
  • FIG. 11 is a schematic flowchart of a communication method provided by an application embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of a communication device according to an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of another communication device according to an embodiment of the present application.
  • Fig. 14 is a schematic structural diagram of the first device of the embodiment of the present application.
  • FIG. 15 is a schematic structural diagram of a second device according to an embodiment of the present application.
  • MEC is a multi-access edge computing platform standard led by the European Telecommunications Standards Institute (ETSI, European Telecommunications Standards Institute). Access to the edge computing platform, and provide more efficient business operation services by virtualizing and serving MEC applications, platforms, and resources to meet the differentiated needs of different businesses in terms of processing capabilities.
  • ETSI European Telecommunications Standards Institute
  • 3GPP provides the system framework shown in Figure 1 for the combination of 5G core network (5GC, 5G core) and MEC in standards TS23.501 and TS23.502.
  • UPF uplink filter/IPv6 branch point
  • MEC platform MEC Platform
  • AF Application Function
  • NEF Network Exposure Function
  • MEC platform mainly includes: MEC system-level (MEC system-level), MEC host level (MEC host level).
  • MEC system-level MEC system-level
  • MEC host level MEC host level
  • the architecture of the host layer and system layer of MEC defined by ETSI is shown in Figure 2.
  • MEC orchestrator MEC orchestrator
  • MEAO MEC application orchestrator
  • MEC application orchestrator MEC application orchestrator
  • the process of CPE accessing the MEC system is shown in Figure 3.
  • the CPE discovers network elements through the terminal routing selection policy (URSP, UE Route Selection Policy) or access network discovery and selection policy (ANDSP, Access Network Discovery and Selection Policy). and select a routing policy.
  • URSP is defined in 3GPP TS 23.503 and is a set of one or more URSP rules, where a URSP rule includes the priority value of the URSP rule, flow descriptor, etc.; ANDSP is used to control the access network on the non-3GPP access network Discovery and selection of relevant UE behaviors.
  • the CPE performs service distribution and scheduling through the ATSSS network element.
  • 3GPP TS23.501 describes the ATSSS architecture based on non-3GPP access.
  • ATSSS is Access Traffic Steering, Switching, Splitting, also known as access traffic control, switching, and splitting. It is a network-level traffic aggregation technology. A user-transparent method of balancing data traffic between mobile networks and non-3GPP access.
  • the UE transmits to the 5G core network through the 5G physical layer (PHY, Physical) and the 5G base station wireless access network (RAN, wireless access network), and then accesses the application services on the MEP.
  • PHY Physical
  • RAN wireless access network
  • FIG. 4 is a schematic diagram of a 5G CPE routing scheme.
  • a 5G CPE is generally composed of a 5G modem (Modem) and a 5G router (Router).
  • the 5G Modem is responsible for the 5G UE protocol stack, baseband, and radio frequency processing. , to convert 5G signals into network port signals.
  • the 5G Router is responsible for the routing function, converting the network port data of the 5G modem (Modem) into data such as Wi-Fi and ZigBee in the LAN.
  • Fig. 5 is a schematic structural diagram of an IP packet header of a Transmission Control Protocol/Internet Protocol (TCP/IP, Transmission Control Protocol/Internet Protocol) network layer.
  • TCP/IP Transmission Control Protocol/Internet Protocol
  • IP quintuple includes source IP address, source port, destination IP address, destination port, and transport layer protocol.
  • identity identification
  • the "identification (identification)" field in the IP message header occupies 16 bits, and the IP software maintains a counter in the memory. Whenever a datagram is generated, the counter is incremented by 1, and this value is assigned to the identification field. It is used to identify the data slices belonging to the same IP group, and the data slices belonging to the same IP group have the same identification field value.
  • edge computing platform MEP
  • a related technology provides a 5G CPE forwarding method.
  • terminal A sends an IP message to terminal B through 5G CPE.
  • the destination IP address of the message is the IP address of terminal B
  • the source IP address is the IP address of terminal A.
  • the target MAC address is exactly the MAC address of port 1 (Port1) of its CPE
  • the source MAC address is exactly the MAC address of terminal A;
  • Figure 6 (a) is shown in the schematic diagram of the IP quintuple before passing CPE.
  • the CPE when the CPE receives the message and finds that the destination MAC is the local Port1 port, it indicates that the local machine needs to perform further analysis (if the destination MAC is not the local machine, it indicates that the second-layer forwarding is performed directly, and other content of the frame does not need to be analyzed.
  • FIB table Forwarding Info Base
  • CPE In the current industry application scenarios where CPE is common, CPE is used as a conversion gateway from 5G signals to other signal formats (Wi-Fi, optical fiber, cable, HDMI, Bluetooth, etc.), to meet the needs of medical devices that do not support 5G access. Access to the 5G network, and access to the medical dedicated network built based on network slicing technology and dedicated medical services; however, in the actual service matching process, the network connected to the CPE presents diversification and complexity (Wi -Fi, optical fiber, cable, HDMI, Bluetooth, etc.), differentiated requirements for service end-to-end QoS guarantees, etc., as shown in Figure 7, the following provides several service scenarios:
  • Business scenario 1 Accessing CPE through Wi-Fi and accessing application services on MEC generally bears the requirements for network quality (throughput, end-to-end delay, service level agreement (SLA, Service Level Agreement) guarantee, etc.) Low-cost services, such as office automation (OA, Office Automation) applications, public applications, etc.
  • SLA service level agreement
  • OA Office Automation
  • Business scenario 2 Connect to CPE through optical fiber or cable and access application services on MEC, usually services that require high network quality (throughput, end-to-end delay, SLA guarantee, etc.), such as medical imaging equipment, medical Ultrasound equipment and other medical testing or monitoring equipment, etc.
  • services that require high network quality such as medical imaging equipment, medical Ultrasound equipment and other medical testing or monitoring equipment, etc.
  • Business scenario 3 Accessing CPE through Bluetooth, LoRa (LORA), etc. and accessing application services on MEC is a business that requires high latency but low throughput, such as positioning services, device management and control services, etc. . This type of business needs to update location information or accept instructions in real time to ensure the accuracy and speed of business execution.
  • LORA LoRa
  • This type of business needs to update location information or accept instructions in real time to ensure the accuracy and speed of business execution.
  • Business scenario 4 Access to CPE and access application services on the MEC through the tunnel mode of Internet Protocol Security (IPSec, Internet Protocol Security) virtual private network (VPN, Virtual Private Network), mainly for services that require particularly high data security .
  • IPSec Internet Protocol Security
  • VPN Virtual Private Network
  • the orchestrator (MEAO/MEO) on the MEC side needs to be able to identify different service types or access network types connected to the CPE, and all The end-to-end transmission quality requirements of the accessed business or network (transmission throughput, transmission delay, transmission SLA, etc.); so that the MEC orchestrator (MEAO/MEO) can arrange the application services on the MEC. Guarantee the differentiated requirements for services or network performance connected to the CPE.
  • the 5G CPE implemented based on the existing IP layer protocol, there are two key technical problems:
  • the routing method of the above CPE since the source IP address of the IP packet header has been converted into a public IP address by NAT, "the network or service IP data flow connected to the CPE by the back end" and "the IP address of the CPE connected to the MEC Data flow” does not form a mapping relationship. Therefore, the existing technology cannot judge the network or service type accessed by the CPE from the IP data packet of the 5G cellular port of the CPE.
  • the MEC orchestrator MEAO/MEO cannot dynamically base the access Priority of network data to CPE to ensure differentiated transmission requirements of services.
  • the problems existing in the above-mentioned existing CPE will cause the differentiated network requirements of the multi-standard network or network type between the 5G CPE and the terminal to be unable to be effectively transmitted to the MEC side, and the orchestrator MEAO/MEO of the MEC service system cannot obtain the network type (or business type) information, which cannot be reasonably and effectively arranged for specific services, and ultimately cannot guarantee the end-to-end performance of the business.
  • the first device is used to send service data to the second device; the second device is used to receive service data from the first device; the service data is based on at least one first A combination of data obtained.
  • Fig. 8 is a schematic flow diagram of a communication method provided by an embodiment of the present application; as shown in Fig. 8, the method is applied to a first device, and the method includes:
  • Step 801. Send service data to a second device; the service data is obtained by combining at least one piece of first data.
  • the first device is a CPE
  • the second device is a multi-access edge computing device (MEC, Multi-access Edge Computing), and may also be other information technology (IT) common platform.
  • MEC multi-access edge computing device
  • IT information technology
  • the embodiment of the present application does not limit the names of the first device and the second device, as long as the functions of the first device and the second device can be realized.
  • the method also includes:
  • the first merging policy is a local merging policy saved by the first device; the merging policy is used to indicate a manner of merging the first data.
  • the first data is data to be uploaded to the second device.
  • the first terminal may determine the way to combine the first data according to the local combining strategy, and according to the determined combining first data merging the at least one first data in the form of one data to obtain the service data;
  • the first terminal determines the second merging strategy sent by the second device according to the first instruction sent by the second device, and may also determine the method of merging the first data according to the second merging strategy. Merge the at least one first data in a data manner to obtain the service data.
  • the first terminal determines the method of merging the first data according to the first merging strategy and/or the second merging strategy (one of which can be selected, or one can be selected according to the priority of different preset merging strategies). and merging the at least one piece of first data according to the determined way of merging the first data to obtain the service data.
  • the method also includes:
  • the first signaling is used to describe the service transmission performance;
  • the first request is based on the transmission performance parameters of the first network and/or the transmission of the second network Determination of performance parameters;
  • the first signaling, the first request, and the first instruction are respectively described below.
  • the first signaling is used to describe service transmission performance, and may also be described as service transmission performance reporting (PRTL, Performance reporting of traffic link to UE) of the first network.
  • the first network refers to the network between the target device (eg, medical device) and the first device.
  • the first device (such as CPE) sends the first signaling (that is, PRTL) to the second device (such as MEC).
  • the second device (such as MEC) has two important functions: one is to allow the second device (such as MEC) to quickly adapt to the transmission changes of the back-end network or services of the first device (such as CPE), and the other is to avoid uploading the first information to the first device too frequently. order (that is, PRTL), to ensure that the network transmission overhead is controllable. That is, according to different business needs, the second device (such as MEC) can quickly adapt to the transmission changes of the back-end network or services of the first device (such as CPE) within a certain range of signaling transmission delay.
  • the first signaling is used to indicate at least one of the following:
  • the identifier of the first device The identifier of the first device, the network type of the first network, the network connection status of the first network, and the performance information of the application program.
  • MAC Media Access Control Address
  • IMSI International Mobile Subscriber Identity
  • ID Identity document
  • MAC Media Access Control Address
  • IMSI International Mobile Subscriber Identity
  • ID Identity document
  • MAC address description method use the MAC address of the CPE as the globally unique identifier, such as "2A:DA:0B:84:03:9B"; when using the IMSI, use the IMSI of the mobile phone card provided by the operator as the Identifier; when using the ID expression method, use the mobile phone number or the IMEI corresponding to the CPE or the factory serial number set by the manufacturer as the identifier.
  • CPE For the "network type", its implementation can be index array, string array or Bitmap.
  • CPE supports wireless communication technology (Wi-Fi, Wireless Fidelity), Bluetooth, infrared, narrowband Internet of Things (NB-IoT, Narrow Band Internet of Things), high-definition multimedia interface (HDMI, High Definition Multimedia Interface), optical fiber, VPN, etc.
  • Wi-Fi Wireless Fidelity
  • Bluetooth infrared
  • NB-IoT narrowband Internet of Things
  • NB-IoT narrowband Internet of Things
  • HDMI High Definition Multimedia Interface
  • optical fiber VPN, etc.
  • Network Type Network Type.
  • Wi-Fi Wireless Fidelity
  • Bluetooth Wireless Fidelity
  • optical fiber Enter the index array
  • bitmap expression you can use “Wi-Fi” to represent the wireless LAN Wi-Fi network, “Bluetooth” to represent Bluetooth, “fiber” to represent optical fiber, and then "Wi-Fi, Bluetooth, fiber” Put it into a string array; when using the bitmap expression method, use an 8-bit or 16-bit bitmap, and set the bit 0, 1, and 5 to 1, which respectively represent Wi-Fi, Bluetooth, optical fiber 3 networks, and others is 0 by default.
  • Network Connection Status the implementation can be Boolean or String.
  • Boolean expression you can use 1 to indicate that the network connection is normal, use 0 to indicate that the network is abnormally disconnected; when using a string expression, use "up” to indicate that the network connection is normal, use “down” to indicate that the network is abnormally disconnected . Only when the network connection status of the CPE is normal, the STC indication will be sent, otherwise it will not be sent.
  • performance information of the application program at least include the application identification, throughput, delay, and packet loss rate.
  • the detailed implementation of the included information is described as follows:
  • appD application identification
  • the attribute field of appD includes the application identity (appDId), application name (appName), application provider (appProvider), application software version (appSoftVersion), application version number (appDVersion ), application information name (appInfoName), application description (appDescription), virtual computing descriptor (virtualComputeDescriptor), application exposed external interface (appExtCpd), application required service (appServiceRequired), application business option (appServiceOptional ), application-produced services (appServiceProduced), application required features (appFeatureRequired), application optional features (appFeatureOptional), transport dependencies (transportDependencies), application routing rules (appTrafficRule), application DNS rules (appDNSRule ), application latency (appLatency), configuration parameters for terminating application instance operations (terminateAppInstanceOpConfig), and configuration parameters for changing application instance state (changeAppInstanceStateOpConfig).
  • throughput it means the maximum data rate that the CPE can receive and forward without frame loss. Its implementation is an integer, and the unit is bits per second (bps) or bits per megabyte (Mbps) or other .
  • delay it means the time required to receive forwarding from a CPE backend to the front-end egress, and its implementation is an integer, and the unit is milliseconds or seconds, for example, 3ms.
  • Packet loss rate it refers to the percentage of lost packets in the transmission packets during the network transmission process, and its implementation is expressed in floating-point numbers, such as 3.5%.
  • the sending the first signaling to the second device includes at least one of the following:
  • the aperiodically sending the first signaling to the second device includes:
  • the first signaling is sent to the second device.
  • the first network is a network between the target device and the first device; for example, the target device may be a medical device, and the first network is a network between the medical device and the CPE.
  • the network type of the first network includes at least one of the following: Wi-Fi, Bluetooth, Zigbee, NB-loT, LoRa, infrared network and the like.
  • the transmission performance parameters include at least one of the following: throughput, delay, and packet loss rate.
  • the trigger strategy of the first signaling includes two modes: periodic triggering and aperiodic triggering.
  • Periodic triggering refers to: no matter whether the transmission performance of the first network changes, it uploads to the second device (such as MEC) at regular intervals (which can be pre-set by the developer, or set by the user)
  • the first signaling ie PRTL
  • the period unit of time can be milliseconds, seconds, minutes, hours, etc.
  • Aperiodic trigger In order to avoid frequently uploading the first signaling (ie PRTL) to the second device (such as MEC), causing unnecessary network resource overhead, only when the change in the transmission performance of the first network exceeds the trigger condition threshold, the first signaling (that is, PRTL) is sent to the second device (such as MEC).
  • Trigger conditions can be combined using "and (and)/or (or)" logic conditions.
  • the embodiment of the trigger condition of the change of the transmission performance parameter (throughput, time delay, packet loss rate) of the first network is as shown in the following table 2, the trigger condition table of the transmission performance parameter change of the first network:
  • Trigger condition A 2.1% 1.8% 3% and Trigger condition B 2.8% 1.3% 1% or Trigger condition C. 3.0% 2% 1.5% mix
  • the throughput is the change percentage threshold, recorded as throughput_per;
  • the time delay is the change percentage threshold, recorded as delay_per;
  • the packet loss rate is a change percentage threshold, which is recorded as loss_per.
  • the thresholds in Table 2 can be adjusted according to the actual business situation.
  • the trigger conditions can be obtained according to Table 2 as follows:
  • Trigger condition A (throughput_per>2.1%) and (delay_per>1.8%) and (loss_per>3%);
  • Trigger condition B (throughput_per>2.8%) or (delay_per>1.3%) or (loss_per>1%);
  • Trigger condition C (throughput_per>3.0% and delay_per>2%) or (loss_per>1.5%).
  • the first signaling is uploaded.
  • a time window (for example, 10s) can be added before the trigger condition, and only when the set time window is exceeded, the above trigger condition can be judged, which can further avoid network transmission resource overhead.
  • the time window can be fixed or variable. When the first signaling (ie PRTL) is triggered more frequently, the time window can be appropriately increased; when the first signaling (ie PRTL) is less triggered, the time window can be appropriately reduced window.
  • the first instruction is used to instruct the first device to perform data combination, and may also be described as a service traffic combination instruction (STC, Strategy of traffic combination at UE) of the first network.
  • STC service traffic combination instruction
  • the first instruction includes at least one of the following:
  • An identifier of the first device a network type of the first network, a local configuration identifier, and a second merging policy.
  • the second merging strategy includes at least one of the following:
  • the identification of the application the type of traffic ratio allocation for each application, the length of the traffic ratio allocation for each application, and the traffic ratio allocation strategy for each application;
  • the flow ratio distribution type is represented by numbers and/or character strings
  • the flow proportional distribution length is represented by numbers
  • the traffic proportion allocation policy is represented by a character string and/or a codebook index.
  • the local configuration identifier is used to indicate whether the first device performs data merging according to the second merging policy sent by the second device.
  • the local configuration identifier allows the first device (such as CPE) to locally configure the combination of application data
  • the first device such as CPE
  • the priority of the local configuration is higher than the configuration issued from the second device (such as MEC), that is, in some embodiments, the priority of the first merging strategy may be higher than the second merging strategy in the first instruction the priority of the strategy;
  • the first device uses the local configuration.
  • the first device (such as CPE) can complete the data merging and "many-to-one" mapping functions according to the received first command (ie, STC), as shown in Table 3, the data of the first command (ie, STC) shown in the structure table.
  • the first device eg, CPE
  • the default traffic combining strategy that is, the first combining strategy.
  • the "local configuration identifier” its implementation can be a Boolean parameter or a string.
  • Boolean parameters if the local configuration flag is 1, local configuration is allowed; if the local configuration flag is 0, local configuration is not allowed.
  • a string if the local configuration flag is "true”, local configuration is allowed, and if the local configuration flag is "false”, local configuration is not allowed.
  • each application ID corresponds to corresponding traffic ratio distribution parameters, including traffic ratio distribution type, traffic ratio distribution length, and traffic ratio distribution strategy.
  • quota_type For the "traffic ratio allocation type (quota_type)", its implementation can be a number or a character string. When using numbers, if quota_type is 1, it means allocation according to time latitude; if quota_type is 2, it means allocation according to storage space latitude. When using a character string, if the quota_type is "time”, it means to allocate according to the time latitude; if the quota_type is "memory”, it means to allocate according to the storage space latitude.
  • quota_length For the "flow proportional allocation length (quota_length)", its implementation can be a number. When quota_type is 1, it indicates the allocated transmission time length, and the unit can be milliseconds or seconds, such as 100ms, 10s, etc. When quota_type is 2, it indicates the length of the allocated storage space, and the unit can be Byte, KB, MB, GB, such as 10KB, 5MB, etc.
  • quota_strategy For the "traffic proportional allocation strategy (quota_strategy)", its implementation may be a character string or a proportional allocation codebook index, or other equivalent descriptions.
  • quota_strategy App1, 40%; App2, 30%; App3, 20%; App4, 10%
  • the traffic ratio allocation strategy is configured in a codebook manner.
  • one quota_strategy ID can represent multiple multi-channel data traffic merging strategies. For example, when three application programs are connected to the terminal or the networks are A, B, and C respectively, it is assumed that the codebook set is 8 at the same time. As shown in Table 4 and the codebook index table, each column represents the data transmission ratio of each service or network.
  • the first request is determined according to transmission performance parameters of the first network and/or transmission performance parameters of the second network;
  • the first request may also be described as a service traffic combination indication (STC, Strategy of traffic combination at UE).
  • STC service traffic combination indication
  • the first device (such as CPE) actively sends information to the second device (such as MEC) based on the transmission performance of the first network and the transmission performance between the first device (such as CPE) and the second device (such as MEC). ) to apply for a new traffic combining strategy, that is, a second combining strategy. That is, the first request is sent to the second device (such as the MEC).
  • the data structure of the first request (that is, the TCR) is shown in Table 5 and the data structure table of the TCR.
  • parameter name type of data illustrate CPE identification string The global uniqueness used to identify the CPE
  • the triggering strategy of the first request may be an aperiodic triggering manner.
  • the first device (such as CPE) comprehensively evaluates the transmission performance of the first network and the transmission performance between the first device (such as CPE) and the second device (such as MEC). ) sends the first request (ie TCR).
  • the first request (that is, TCR) to meet the trigger condition needs to meet the following two conditions at the same time:
  • the change of the transmission performance index (referring to the transmission performance index between the target device and the first device) of the first network of the first device (such as CPE) does not meet the trigger strategy of the first signaling (ie PRTL);
  • the transmission performance change of the transmission index (throughput, delay, packet loss rate) between the first device (such as CPE) and the second device (such as MEC) reaches a threshold.
  • the change of the performance index between the first device (such as CPE) and the second device (such as MEC) refers to the trigger strategy of the first signaling (that is, PRTL), and sets the trigger threshold and trigger combination of each transmission index according to the actual needs of the business. I won't go into details here.
  • the method further includes generating a first request.
  • the first device (such as the CPE) can comprehensively determine and generate the first request (ie TCR). Based on the above description about the first signaling (that is, PRTL), it can be seen that the first signaling (that is, PRTL) will be sent when the transmission performance index of the first network changes too much, so the generation of the first request (that is, TCR) mainly considers the first device A change in the network performance index between the second device and the second device.
  • TCR The relevant embodiment of generating the first request (ie TCR) is as follows:
  • the quota_type in the first request (ie TCR) is set to Time latitude, that is, set quota_type to 1.
  • the implementation method of quota_strategy is a string, for applications with low latency requirements, the proportion of traffic allocation time is smaller; for applications with high latency requirements, the proportion of time for traffic allocation is more.
  • the implementation method of quota_strategy is codebook index, for applications with low latency requirements, the codebook index should use an index with a smaller time ratio; for applications with high latency requirements, its codebook index should use a more time ratio index.
  • the quota_type in the TCR is set to the spatial latitude, that is, the quota_type is set to for 2.
  • the implementation method of quota_strategy is a string, for applications with low throughput requirements, the proportion of space allocation is smaller; for applications with high throughput requirements, the proportion of space allocation is more.
  • the implementation method of quota_strategy is codebook index, for applications with low throughput requirements, the codebook index should use an index with a smaller space ratio; for applications with high throughput requirements, its codebook index should use a more space ratio index.
  • the delay and throughput between the first device (such as CPE) and the second device (such as MEC) vary greatly, you can choose to use the delay index or the throughput index as the standard according to the actual needs of the business.
  • the first data is data transmitted through the first network.
  • the network type of the first network includes at least one of the following: Wi-Fi, Bluetooth, Zigbee, NB-loT, LoRa, infrared network, and the like.
  • the target device communicates with the first device, and the first device communicates with the second device;
  • the first network is a network between the target device and the first device; for example, the target device may be a medical device, and the first network is a network between the medical device and the CPE.
  • the first network may also be described as a second-hop network; correspondingly, the second-hop performance index refers to the transmission performance index of the second-hop network; the second-hop data is data transmitted by the second-hop network.
  • the second network is a network between the first device and the second device, and the second network may also be described as a first-hop network.
  • the target device is a device involved in an actual application, such as a medical device.
  • FIG. 9 provides a schematic flowchart of another communication method according to an embodiment of the present application; as shown in FIG. 9, the method is applied to a second device, and the method includes:
  • Step 901. Receive service data from a first device; the service data is obtained by combining at least one piece of first data.
  • the first device is a CPE
  • the second device is a mobile edge computing device (MEC), and may also be other general information technology (IT) platforms with wireless network information application programming interface (API) interaction capabilities, and computing, storage, and analysis functions.
  • MEC mobile edge computing device
  • IT general information technology
  • API application programming interface
  • the embodiment of the present application does not limit the names of the first device and the second device, as long as the functions of the first device and the second device can be realized.
  • the method also includes:
  • the first signaling is used to describe the service transmission performance;
  • the first request is based on the transmission performance parameters of the first network and/or the transmission performance parameters of the second network Determination of transmission performance parameters;
  • the method further includes: generating a first instruction.
  • the data that MEO can obtain includes time delay, available MEC services, and available MEC resources.
  • the time delay is the first device (such as CPE ) and the second device (such as MEC), the specific performance indicators of each application of the second-hop service cannot be obtained, so it is necessary to analyze and judge the performance indicators of each application of the second-hop service to generate The first command (ie STC).
  • the M-TMMM module can quickly generate and issue the first command (ie STC) within a certain range of signaling transmission delays to adapt to the back-end network of the first device (such as CPE) Or business transmission changes.
  • the MEO obtains the performance parameters of the second-hop service data, it allocates different traffic ratios according to the actual needs of the service according to the different requirements of delay and throughput.
  • the relevant embodiment of generating the first instruction (ie STC) is as follows:
  • quota_type For applications that require latency, set quota_type to 1 based on the time latitude.
  • the implementation method of quota_strategy is a character string, for applications with low latency requirements, the proportion of time for traffic allocation is relatively small; for applications with high latency requirements, the proportion of time for traffic allocation is relatively large.
  • the implementation method of quota_strategy is codebook index, for applications with low latency requirements, the codebook index uses an index with a smaller time ratio; for applications with high latency requirements, its codebook index uses an index with a larger time ratio;
  • quota_type For applications that require throughput, set quota_type to 2 based on the spatial latitude.
  • the implementation method of quota_strategy is a string, for applications with low throughput requirements, the proportion of space allocation is relatively small; for applications with high throughput requirements, the proportion of space allocation is relatively large.
  • the implementation method of quota_strategy is codebook index, for applications with low throughput requirements, the codebook index uses an index with a smaller space ratio; for applications with high throughput requirements, its codebook index uses an index with a larger space ratio;
  • the requirements for delay or space indicators can be prioritized according to different services.
  • the rules may be preset and stored in the second device, and the second merging strategy may be determined based on the preset rules during application.
  • the first signaling is used to indicate at least one of the following:
  • the identifier of the first device The identifier of the first device, the network type of the first network, the network connection status of the first network, and the performance information of the application program.
  • the first instruction includes at least one of the following:
  • An identifier of the first device a network type of the first network, a local configuration identifier, and a second merging policy.
  • the second merging strategy includes at least one of the following:
  • the identification of the application the type of traffic ratio allocation for each application, the length of the traffic ratio allocation for each application, and the traffic ratio allocation strategy for each application;
  • the flow ratio distribution type is represented by numbers and/or character strings
  • the flow proportional distribution length is represented by numbers
  • the traffic proportion allocation policy is represented by a character string and/or a codebook index.
  • the local configuration identifier is used to indicate whether the first device performs data merging according to the second merging policy sent by the second device.
  • the priority of the first merging policy saved by the first device is higher than the priority of the second merging policy in the first instruction.
  • the transmission performance parameters include at least one of the following: throughput, delay, and packet loss rate.
  • the first data is data transmitted through the first network.
  • the first network is a network between the target device and the first device
  • the second network is a network between the first device and the second device.
  • the first device such as CPE
  • the first device can effectively support the above-mentioned four scenarios (business scenario 1, business scenario 2, business scenario 3, and business scenario 4), thereby ensuring that the uplink data During the transmission process, as well as the differentiated requirements of the services connected to the CPE or network performance.
  • the second device (such as MEC) can effectively identify the network type or service type between the first device (such as CPE) and the terminal, as well as the differentiated requirements for transmission performance, and can effectively guarantee the communication between the first device (such as CPE) and the terminal. Differentiated requirements for transmission performance of inter-network or business.
  • the first device, the second device, and the system architecture realized by the above solutions are operable, safer, implementable, and evolving, and more suitable for vertical industry customer needs.
  • Fig. 10 is a schematic structural diagram of a communication system provided by an embodiment of the present application; as shown in Fig. 10 , the communication system includes: a first device and a second device; the first device is a CPE; the second device for MEC.
  • the first device as a CPE and the second device as an MEC as an example.
  • the CPE adds or has a traffic mapping module (M-TMM), and the orchestrator MEO of the MEC adds or has a traffic mapping management module (M-TMMM).
  • M-TMM traffic mapping module
  • M-TMMM traffic mapping management module
  • Traffic merging and mapping refers to the "many-to-one" merging and mapping function of multiple CPE second-hop data to the cellular network, hereinafter referred to as "traffic merging" or "traffic mapping”.
  • traffic merging or "traffic mapping”.
  • the functions of the traffic mapping module and the traffic mapping management module are as follows:
  • Traffic mapping module (M-TMM, Multiple traffic mapping module): carried on the CPE, realizes the traffic merging and mapping function of multiple networks or service data connected to the CPE to the 5G transmission channel, through which the CPE can be effectively guaranteed
  • the transmission performance guarantee of multiple networks or services between the terminal and the terminal such as key performance indicators such as transmission rate, transmission delay, and packet loss rate.
  • Traffic mapping management module carried in the MEC system, realizes the second merged policy management function for the CPE side back-end multi-access network or business data, through which effective decision-making and Instruct the CPE backend network or service transmission method.
  • the traffic mapping module is managed by the traffic mapping management module. Through the signaling interaction between the traffic mapping module and the traffic mapping management module, the SLA transmission performance guarantee for the network or business between the CPE and the terminal is realized.
  • the first hop network refers to the network between the CPE and the MEC
  • the second hop network refers to the network between the CPE and the medical equipment.
  • the signaling interaction process between the traffic mapping module in the CPE and the traffic mapping management module in the MEC system is shown in Figure 11 . It includes at least the following steps:
  • Step 1101 the CPE sends the service transmission performance of the second hop network to the MEC (PRTL, Performance reporting of traffic link to UE);
  • the actual transmission performance of the network or service connection connected to the CPE is reported to the traffic mapping management module on the MEC side.
  • the network or service connection connected to the CPE refers to the connection established with the CPE through Wi-Fi, Bluetooth, HDMI, optical fiber, network cable or APP.
  • the network connected to the CPE refers to the second-hop network, such as the network connected to the CPE by medical equipment.
  • the PRTL is equivalent to the first signaling in the methods shown in FIG. 8 and FIG. 9 , which has been described in detail in the methods shown in FIG. 8 and FIG. 9 , and will not be repeated here.
  • Step 1102 the CPE receives the service traffic combination indication (STC, Strategy of traffic combination at UE) of the second hop network sent by the MEC;
  • STC Service Traffic combination indication
  • the traffic mapping management module on the MEC side performs policy scheduling for the traffic on the CPE side, and sends the policy scheduling content to the CPE through the STC.
  • the CPE based on the received STC, Complete data merging and mapping functions.
  • the STC is equivalent to the first instruction in the methods shown in FIG. 8 and FIG. 9 , which has been detailed in the methods shown in FIG. 8 and FIG. 9 , and will not be repeated here.
  • Step 1103 the CPE sends the service data transmission (DTC, Data transmission at CPE) of the second hop network to the MEC;
  • DTC Service data transmission at CPE
  • the CPE completes the assembling and merging of the service data of the second hop of the CPE according to the service flow merging instruction received from the second hop network, and completes the data transmission process from the CPE to the MEC side.
  • the method may also include:
  • Step 1101-1 the CPE sends a service traffic combination request (TCR, Traffic combination requirement at UE) of the second hop network to the MEC;
  • TCR Service traffic combination request
  • the CPE can actively apply for a new traffic combination method from the traffic mapping management module on the MEC side, so as to quickly adapt to the CPE back-end network or service transmission changes.
  • the TCR is equivalent to the first request in the methods shown in FIG. 8 and FIG. 9 , which has been described in detail in the methods shown in FIG. 8 and FIG. 9 , and will not be repeated here.
  • the step 1102-1 may be executed simultaneously with the step 1102, or may be performed before or after the step 1102, which is not limited here.
  • the embodiment of the present application also provides a communication device, which is set on the first device, as shown in FIG. 12 , the device includes:
  • the first communication unit 1201 is configured to send service data to the second device; the service data is obtained by combining at least one piece of first data.
  • the first communication unit 1201 is further configured to send a first signaling and/or a first request to the second device; the first signaling is used to describe service transmission performance; the first The request is determined based on transmission performance parameters of the first network and/or transmission performance parameters of the second network;
  • the first device further includes: a first processing unit 1202 configured to merge the at least one first data according to a preset first merge strategy and/or the first instruction to obtain the business data.
  • a first processing unit 1202 configured to merge the at least one first data according to a preset first merge strategy and/or the first instruction to obtain the business data.
  • the first instruction includes at least one of the following:
  • An identifier of the first device a network type of the first network, a local configuration identifier, and a second merging policy.
  • the second merging strategy includes at least one of the following:
  • the identification of the application the type of traffic ratio allocation for each application, the length of the traffic ratio allocation for each application, and the traffic ratio allocation strategy for each application;
  • the flow ratio distribution type is represented by numbers and/or character strings
  • the flow proportional distribution length is represented by numbers
  • the traffic proportion allocation policy is represented by a character string and/or a codebook index.
  • the local configuration identifier is used to indicate whether the first device performs data merging according to the second merging policy sent by the second device.
  • the priority of the first merge strategy is higher than the priority of the second merge strategy in the first instruction.
  • the first signaling is used to indicate at least one of the following:
  • the identifier of the first device The identifier of the first device, the network type of the first network, the network connection status of the first network, and the performance information of the application program.
  • the first communication unit 1201 is configured to perform at least one of the following:
  • the first communication unit 1201 is configured to send the first signaling to the second device when it is determined that the transmission performance parameter of the first network exceeds a preset threshold.
  • the transmission performance parameters include at least one of the following: throughput, delay, and packet loss rate.
  • the first data is data transmitted through the first network.
  • the first network is a network between the target device and the first device
  • the second network is a network between the first device and the second device.
  • the first communication unit 1201 and the first processing unit 1202 may be implemented by a processor in a communication device combined with a communication interface.
  • the embodiment of the present application also provides a communication device, which is set on the second device, as shown in FIG. 13 , the device includes:
  • the second communication unit 1301 is configured to receive service data from the first device; the service data is obtained by combining at least one piece of first data.
  • the second communication unit 1301 is configured to receive a first signaling and/or a first request sent by a first device; the first signaling is used to describe service transmission performance; the first The request is determined based on transmission performance parameters of the first network and/or transmission performance parameters of the second network;
  • the second device may further include: a second processing unit 1302 configured to generate the first instruction.
  • the first signaling is used to indicate at least one of the following:
  • the identifier of the first device The identifier of the first device, the network type of the first network, the network connection status of the first network, and the performance information of the application program.
  • the first instruction includes at least one of the following:
  • An identifier of the first device a network type of the first network, a local configuration identifier, and a second merging policy.
  • the second merging strategy includes at least one of the following:
  • the identification of the application the type of traffic ratio allocation for each application, the length of the traffic ratio allocation for each application, and the traffic ratio allocation strategy for each application;
  • the flow ratio distribution type is represented by numbers and/or character strings
  • the flow proportional distribution length is represented by numbers
  • the traffic proportion allocation policy is represented by a character string and/or a codebook index.
  • the local configuration identifier is used to indicate whether the first device performs data merging according to the second merging policy sent by the second device.
  • the priority of the first merging policy saved by the first device is higher than the priority of the second merging policy in the first instruction.
  • the transmission performance parameters include at least one of the following: throughput, delay, and packet loss rate.
  • the first data is data transmitted through the first network.
  • the first network is a network between the target device and the first device
  • the second network is a network between the first device and the second device.
  • the second communication unit 1301 and the second processing unit 1302 may be implemented by a processor in a communication device combined with a communication interface.
  • the embodiment of the present application further provides a first device, as shown in FIG. 14 , the first device 1400 includes:
  • the first communication interface 1401 is capable of exchanging information with the second device
  • the first processor 1402 is connected to the first communication interface 1401 to implement information interaction with the second device, and is configured to execute the methods provided by one or more technical solutions on the first device side when running a computer program. Instead, the computer program is stored on the first memory 1403 .
  • the first communication interface 1401 is configured to send service data to the second device; the service data is obtained by combining at least one piece of first data.
  • the first processor 1402 is configured to combine the at least one piece of first data according to a preset first combination strategy and/or the first instruction to obtain the service data.
  • the first communication interface 1401 is further configured as:
  • the first signaling is used to describe the service transmission performance;
  • the first request is based on the transmission performance parameters of the first network and/or the transmission of the second network Determination of performance parameters;
  • the first communication interface 1401 is further configured as:
  • the first communication interface 1401 is further configured as:
  • the first signaling is sent to the second device.
  • bus system 1404 various components in the first device 1400 are coupled together through the bus system 1404 .
  • the bus system 1404 is used to realize connection and communication between these components.
  • the bus system 1404 also includes a power bus, a control bus and a status signal bus.
  • the various buses are labeled as bus system 1404 in FIG. 14 .
  • the first memory 1403 in the embodiment of the present application is used to store various types of data to support the operation of the first device 1400 .
  • Examples of such data include: any computer programs for operating on the first device 1400 .
  • the methods disclosed in the foregoing embodiments of the present application may be applied to the first processor 1402 or implemented by the first processor 1402 .
  • the first processor 1402 may be an integrated circuit chip, which has a signal processing capability. In the implementation process, each step of the above method may be implemented by an integrated logic circuit of hardware in the first processor 1402 or an instruction in the form of software.
  • the aforementioned first processor 1402 may be a general-purpose processor, a digital signal processor (DSP, Digital Signal Processor), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like.
  • the first processor 1402 may implement or execute various methods, steps, and logic block diagrams disclosed in the embodiments of the present application.
  • a general purpose processor may be a microprocessor or any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor.
  • the software module may be located in a storage medium, and the storage medium is located in the first memory 1403.
  • the first processor 1402 reads the information in the first memory 1403, and completes the steps of the foregoing method in combination with its hardware.
  • the first device 1400 may be implemented by one or more Application Specific Integrated Circuits (ASIC, Application Specific Integrated Circuit), DSP, Programmable Logic Device (PLD, Programmable Logic Device), complex programmable logic device (CPLD, Complex Programmable Logic Device), field-programmable gate array (FPGA, Field-Programmable Gate Array), general-purpose processor, controller, microcontroller (MCU, Micro Controller Unit), microprocessor (Microprocessor), or others Electronic components are implemented for performing the aforementioned methods.
  • ASIC Application Specific Integrated Circuit
  • DSP Programmable Logic Device
  • PLD Programmable Logic Device
  • CPLD Complex Programmable Logic Device
  • FPGA Field-Programmable Gate Array
  • controller controller
  • microcontroller MCU, Micro Controller Unit
  • microprocessor Microprocessor
  • the embodiment of the present application further provides a second device, as shown in FIG. 15 , the second device 1500 includes:
  • the second communication interface 1501 is capable of information interaction with the first device and the third device;
  • the second processor 1502 is connected to the second communication interface 1501 to realize information interaction with the first device and the third device, and is configured to execute one or more technical solutions on the second device side when running a computer program. Methods. Instead, the computer program is stored on the second memory 1503 .
  • the second communication interface 1501 is configured to receive service data from the first device; the service data is obtained by combining at least one piece of first data.
  • the second communication interface 1501 is further configured as:
  • the first signaling is used to describe the service transmission performance;
  • the first request is based on the transmission performance parameters of the first network and/or the transmission performance parameters of the second network Determination of transmission performance parameters;
  • the second processor 1502 is configured to generate the first instruction.
  • bus system 1504 various components in the second device 1500 are coupled together through the bus system 1504 . It can be understood that the bus system 1504 is used to realize connection and communication between these components. In addition to the data bus, the bus system 1504 also includes a power bus, a control bus and a status signal bus. However, the various buses are labeled as bus system 1504 in FIG. 15 for clarity of illustration.
  • the second memory 1503 in the embodiment of the present application is used to store various types of data to support the operation of the second device 1500 .
  • Examples of such data include: any computer programs for operating on the second device 1500 .
  • the methods disclosed in the foregoing embodiments of the present application may be applied to the second processor 1502 or implemented by the second processor 1502 .
  • the second processor 1502 may be an integrated circuit chip and has signal processing capabilities. In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the second processor 1502 or instructions in the form of software.
  • the aforementioned second processor 1502 may be a general-purpose processor, DSP, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like.
  • the second processor 1502 may implement or execute various methods, steps, and logic block diagrams disclosed in the embodiments of the present application.
  • a general purpose processor may be a microprocessor or any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor.
  • the software module may be located in a storage medium, and the storage medium is located in the second storage 1503, and the second processor 1502 reads information in the second storage 1503, and completes the steps of the aforementioned method in combination with its hardware.
  • the second device 1500 may be implemented by one or more ASICs, DSPs, PLDs, CPLDs, FPGAs, general processors, controllers, MCUs, Microprocessors, or other electronic components for performing the aforementioned methods.
  • the memory in this embodiment of the present application may be a volatile memory or a nonvolatile memory, and may also include both volatile and nonvolatile memories.
  • the non-volatile memory can be read-only memory (ROM, Read Only Memory), programmable read-only memory (PROM, Programmable Read-Only Memory), erasable programmable read-only memory (EPROM, Erasable Programmable Read-Only Memory) Only Memory), Electrically Erasable Programmable Read-Only Memory (EEPROM, Electrically Erasable Programmable Read-Only Memory), Magnetic Random Access Memory (FRAM, ferromagnetic random access memory), Flash Memory (Flash Memory), Magnetic Surface Memory , CD, or CD-ROM (Compact Disc Read-Only Memory); magnetic surface storage can be disk storage or tape storage.
  • the volatile memory may be random access memory (RAM, Random Access Memory), which is used as an external cache.
  • RAM random access memory
  • RAM Random Access Memory
  • many forms of RAM are available, such as Static Random Access Memory (SRAM, Static Random Access Memory), Synchronous Static Random Access Memory (SSRAM, Synchronous Static Random Access Memory), Dynamic Random Access Memory Memory (DRAM, Dynamic Random Access Memory), synchronous dynamic random access memory (SDRAM, Synchronous Dynamic Random Access Memory), double data rate synchronous dynamic random access memory (DDRSDRAM, Double Data Rate Synchronous Dynamic Random Access Memory), enhanced Synchronous Dynamic Random Access Memory (ESDRAM, Enhanced Synchronous Dynamic Random Access Memory), Synchronous Link Dynamic Random Access Memory (SLDRAM, SyncLink Dynamic Random Access Memory), Direct Memory Bus Random Access Memory (DRRAM, Direct Rambus Random Access Memory ).
  • SRAM Static Random Access Memory
  • SSRAM Synchronous Static Random Access Memory
  • DRAM Dynamic Random Access Memory
  • SDRAM Synchronous Dynamic Random Access Memory

Landscapes

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

Abstract

本申请公开了一种通信方法、装置、第一设备、第二设备及存储介质。其中，方法包括：第一设备向第二设备发送业务数据；所述业务数据基于至少一个第一数据合并得到。如此，由第一设备进行第一数据的合并，并将合并后得到的业务数据发送给第二设备，可以满足不同网络的第一数据的差异化需求。

Description

通信方法、装置、相关设备及存储介质
相关申请的交叉引用
本申请基于申请号为202111598137.8、申请日为2021年12月24日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本申请涉及通信领域，尤其涉及一种通信方法、装置、相关设备及存储介质。
背景技术
移动边缘计算(MEC，Mobile Edge Computing)技术作为第五代移动通信技术(5G)演进的关键技术之一，是具备无线网络信息应用程序接口(API，Application Programming Interface)交互能力，以及计算、存储、分析功能的信息技术(IT，Information Technology)通用平台；依托MEC技术，可将传统外部应用拉入移动内部，更贴近用户，提供本地化服务，从而提升用户体验，发挥边缘网络的更多价值。
在当前客户前置设备(CPE，Customer Premise Equipment)普遍存在的行业应用场景中，CPE被用作5G信号到其他信号制式的转换网关，以满足不支持5G接入的设备能够接入到5G网络中，以及接入到基于网络切片技术构建的、专属服务的专用网络中；但在实际的业务匹配过程中，接入到CPE的网络呈现多样化和复杂化、业务端到端服务质量(QoS，Quality of Service)保障的差异化需求等特点。这也导致了现有CPE与终端之间的多制式网络或网络类型的差异化网络需求无法有效传递到MEC侧，MEC无法针对具体业务进行合理有效的编排，最终无法保障业务端到端的性能。
发明内容
本申请实施例提供一种通信方法、装置、相关设备及存储介质。
本申请实施例的技术方案是这样实现的：
第一方面，本申请实施例提供了一种通信方法，应用于第一设备，包括：
向第二设备发送业务数据；所述业务数据基于至少一个第一数据合并得到。
本申请的一些可选实施例中，所述方法还包括：
向第二设备发送第一信令和/或第一请求；所述第一信令用于说明业务传输性能；所述第一请求根据第一网络的传输性能参数和/或第二网络的传输性能参数确定；
接收来自所述第二设备的第一指令；所述第一指令用于指示第一设备进行数据合并。
本申请的一些可选实施例中，所述方法还包括：
根据预设的第一合并策略和/或所述第一指令，合并所述至少一个第一数据，得到所述业务数据。
本申请的一些可选实施例中，所述第一指令，包括以下至少之一：
第一设备的标识、第一网络的网络类型、本地配置标识、第二合并策略。
本申请的一些可选实施例中，所述第二合并策略，包括以下至少之一：
应用程序的标识、各应用程序的流量比例分配类型、各应用程序的流量比例分配长度、各应用程序的流量比例分配策略；
其中，所述流量比例分配类型采用数字和/或字符串的方式表示；
所述流量比例分配长度采用数字的方式表示；
所述流量比例分配策略采用字符串和/或码本索引的方式表示。
本申请的一些可选实施例中，所述本地配置标识用于指示所述第一设备是否根据所述第二设备发送的第二合并策略进行数据合并。
本申请的一些可选实施例中，所述第一合并策略的优先级高于所述第一指令中的第二合并策略的优先级。
本申请的一些可选实施例中，所述第一信令用于指示以下至少之一：
第一设备的标识、第一网络的网络类型、第一网络的网络连接状态、应用程序的性能信息。
本申请的一些可选实施例中，所述向第二设备发送第一信令包括以下至少之一：
周期性向第二设备发送第一信令；
非周期性向第二设备发送第一信令。
本申请的一些可选实施例中，所述非周期性向第二设备发送第一信令包括：
确定第一网络的传输性能参数超过预设阈值时，向第二设备发送第一信令。
本申请的一些可选实施例中，所述传输性能参数，包括以下至少之一：吞吐量、时延、丢包率。
本申请的一些可选实施例中，所述第一数据为通过第一网络传输的数据。
本申请的一些可选实施例中，所述第一网络为目标设备和所述第一设备之间的网络；
所述第二网络为所述第一设备与所述第二设备之间的网络。
第二方面，本申请实施例提供了一种通信方法，应用于第二设备，包括：
接收来自第一设备的业务数据；所述业务数据基于至少一个第一数据合并得到。
本申请的一些可选实施例中，所述方法还包括：
接收第一设备发送的第一信令和/或第一请求；所述第一信令用于说明业务传输性能；所述第一请求根据第一网络的传输性能参数和/或第二网络的传输性能参数确定；
向所述第一设备发送第一指令；所述第一指令用于指示第一设备进行数据合并。
本申请的一些可选实施例中，所述第一信令用于指示以下至少之一：
第一设备的标识、第一网络的网络类型、第一网络的网络连接状态、应用程序的性能信息。
本申请的一些可选实施例中，所述第一指令，包括以下至少之一：
第一设备的标识、第一网络的网络类型、本地配置标识、第二合并策略。
本申请的一些可选实施例中，所述第二合并策略，包括以下至少之一：
应用程序的标识、各应用程序的流量比例分配类型、各应用程序的流量比例分配长度、各应用程序的流量比例分配策略；
其中，所述流量比例分配类型采用数字和/或字符串的方式表示；
所述流量比例分配长度采用数字的方式表示；
所述流量比例分配策略采用字符串和/或码本索引的方式表示。
本申请的一些可选实施例中，所述本地配置标识用于指示所述第一设备是否根据所述第二设备发送的第二合并策略进行数据合并。
本申请的一些可选实施例中，所述第一设备保存的第一合并策略的优先级高于所述第一指令中的第二合并策略的优先级。
本申请的一些可选实施例中，所述传输性能参数，包括以下至少之一：吞吐量、时延、丢包率。
本申请的一些可选实施例中，所述第一数据为通过第一网络传输的数据。
本申请的一些可选实施例中，所述第一网络为目标设备和所述第一设备之间的网络；
所述第二网络为所述第一设备与所述第二设备之间的网络。
第三方面，本申请实施例提供了一种通信装置，设置在第一设备上，包括：
第一通信单元，配置为向第二设备发送业务数据；所述业务数据基于至少一个第一数据合并得到。
本申请的一些可选实施例中，所述第一通信单元，配置为向第二设备发送第一信令和/或第一请求；所述第一信令用于说明业务传输性能；所述第一请求根据第一网络的传输性能参数和/或第二网络的传输性能参数确定；
接收来自所述第二设备的第一指令；所述第一指令用于指示第一设备进行数据合并。
本申请的一些可选实施例中，所述第一设备还包括：第一处理单元，配置 为根据预设的第一合并策略和/或所述第一指令，合并所述至少一个第一数据，得到所述业务数据。
本申请的一些可选实施例中，所述第一指令，包括以下至少之一：
第一设备的标识、第一网络的网络类型、本地配置标识、第二合并策略。
本申请的一些可选实施例中，所述第二合并策略，包括以下至少之一：
应用程序的标识、各应用程序的流量比例分配类型、各应用程序的流量比例分配长度、各应用程序的流量比例分配策略；
其中，所述流量比例分配类型采用数字和/或字符串的方式表示；
所述流量比例分配长度采用数字的方式表示；
所述流量比例分配策略采用字符串和/或码本索引的方式表示。
本申请的一些可选实施例中，所述本地配置标识用于指示所述第一设备是否根据所述第二设备发送的第二合并策略进行数据合并。
本申请的一些可选实施例中，所述第一合并策略的优先级高于所述第一指令中的第二合并策略的优先级。
本申请的一些可选实施例中，所述第一信令用于指示以下至少之一：
第一设备的标识、第一网络的网络类型、第一网络的网络连接状态、应用程序的性能信息。
本申请的一些可选实施例中，所述第一通信单元，配置为执行以下至少之一：
周期性向第二设备发送第一信令；
非周期性向第二设备发送第一信令。
本申请的一些可选实施例中，所述第一通信单元，配置为确定第一网络的传输性能参数超过预设阈值时，向第二设备发送第一信令。
本申请的一些可选实施例中，所述传输性能参数，包括以下至少之一：吞吐量、时延、丢包率。
本申请的一些可选实施例中，所述第一数据为通过第一网络传输的数据。
本申请的一些可选实施例中，所述第一网络为目标设备和所述第一设备之 间的网络；
所述第二网络为所述第一设备与所述第二设备之间的网络。
第四方面，本申请实施例提供了一种通信装置，设置在第二设备上，包括：
第二通信单元，配置为接收来自第一设备的业务数据；所述业务数据基于至少一个第一数据合并得到。
本申请的一些可选实施例中，所述第二通信单元，配置为接收第一设备发送的第一信令和/或第一请求；所述第一信令用于说明业务传输性能；所述第一请求根据第一网络的传输性能参数和/或第二网络的传输性能参数确定；
向所述第一设备发送第一指令；所述第一指令用于指示第一设备进行数据合并。
本申请的一些可选实施例中，所述第二设备还可以包括：第二处理单元，配置为生成第一指令。
本申请的一些可选实施例中，所述第一信令用于指示以下至少之一：
第一设备的标识、第一网络的网络类型、第一网络的网络连接状态、应用程序的性能信息。
本申请的一些可选实施例中，所述第一指令，包括以下至少之一：
第一设备的标识、第一网络的网络类型、本地配置标识、第二合并策略。
本申请的一些可选实施例中，所述第二合并策略，包括以下至少之一：
应用程序的标识、各应用程序的流量比例分配类型、各应用程序的流量比例分配长度、各应用程序的流量比例分配策略；
其中，所述流量比例分配类型采用数字和/或字符串的方式表示；
所述流量比例分配长度采用数字的方式表示；
所述流量比例分配策略采用字符串和/或码本索引的方式表示。
本申请的一些可选实施例中，所述本地配置标识用于指示所述第一设备是否根据所述第二设备发送的第二合并策略进行数据合并。
本申请的一些可选实施例中，所述第一设备保存的第一合并策略的优先级高于所述第一指令中的第二合并策略的优先级。
本申请的一些可选实施例中，所述传输性能参数，包括以下至少之一：吞吐量、时延、丢包率。
本申请的一些可选实施例中，所述第一数据为通过第一网络传输的数据。
本申请的一些可选实施例中，所述第一网络为目标设备和所述第一设备之间的网络；
所述第二网络为所述第一设备与所述第二设备之间的网络。
第五方面，本申请实施例提供了一种第一设备，包括：第一处理器和第一通信接口；其中，
所述第一通信接口，配置为向第二设备发送业务数据；所述业务数据基于至少一个第一数据合并得到。
本申请的一些可选实施例中，所述第一处理器，配置为根据预设的第一合并策略和/或所述第一指令，合并所述至少一个第一数据，得到所述业务数据。
本申请的一些可选实施例中，所述第一通信接口，还配置为：
向第二设备发送第一信令和/或第一请求；所述第一信令用于说明业务传输性能；所述第一请求根据第一网络的传输性能参数和/或第二网络的传输性能参数确定；
接收来自所述第二设备的第一指令；所述第一指令用于指示第一设备进行数据合并。
本申请的一些可选实施例中，所述第一通信接口，还配置为：
周期性向第二设备发送第一信令；和/或，
非周期性向第二设备发送第一信令。
本申请的一些可选实施例中，所述第一通信接口，还配置为：
确定第一网络的传输性能参数超过预设阈值时，向第二设备发送第一信令。
第六方面，本申请实施例提供了一种第二设备，包括：第二处理器和第二通信接口；其中，
所述第二通信接口，配置为接收来自第一设备的业务数据；所述业务数据基于至少一个第一数据合并得到。
本申请的一些可选实施例中，所述第二通信接口，还配置为：
接收第一设备发送的第一信令和/或第一请求；所述第一信令用于说明业务传输性能；所述第一请求根据第一网络的传输性能参数和/或第二网络的传输性能参数确定；
向所述第一设备发送第一指令；所述第一指令用于指示第一设备进行数据合并。
本申请的一些可选实施例中，所述第二处理器，配置为生成第一指令。
第七方面，本申请实施例又提供了一种网络设备，包括：处理器及和配置为存储能够在处理器上运行的计算机程序的存储器，其中，所述处理器配置为运行所述计算机程序时，执行以上第一设备侧的任一项所述方法的步骤；或者，所述处理器配置为运行所述计算机程序时，执行以上第二设备侧的任一项所述方法的步骤。
第八方面，本申请实施例还提供了一种存储介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现第一设备侧的任一项所述方法的步骤；或者，所述计算机程序被处理器执行时实现第二设备侧的任一项所述方法的步骤。
本申请实施例提供的通信系统、方法、装置、第一设备、第二设备及存储介质，方法包括：第一设备向第二设备发送业务数据；所述业务数据基于至少一个第一数据合并得到；第二设备接收来自第一设备的业务数据；所述业务数据基于至少一个第一数据合并得到。本申请实施例的方案，实现第一设备上进行第一数据的合并，并将合并后得到的业务数据发送给第二设备，如此，可以满足不同网络的第一数据的差异化需求。
附图说明
图1为相关技术中MEC的系统结构示意图；
图2为相关技术中MEC的主机层与系统层的结构示意图；
图3为相关技术中CPE接入MEC系统的流程示意图；
图4为相关技术中CPE的路由方案的示意图；
图5为相关技术中网络层的IP报文头结构图；
图6(a)为相关技术中一种通过CPE前的IP五元组的示意图；
图6(b)为相关技术中另一种通过CPE后的五元组的示意图；
图7为本申请应用实施例的业务场景的示意图；
图8为本申请实施例提供的一种通信方法的流程示意图；
图9为本申请实施例提供的另一种通信方法的流程示意图；
图10为本申请实施例提供的一种通信系统的结构示意图；
图11为本申请应用实施例提供的一种通信方法的流程示意图；
图12为本申请实施例一种通信装置的结构示意图；
图13为本申请实施例另一种通信装置的结构示意图；
图14为本申请实施例第一设备的结构示意图；
图15为本申请实施例第二设备的结构示意图。
具体实施方式
下面结合附图及实施例对本申请再作进一步详细的描述。
相关技术中，MEC作为欧洲电信标准化协会(ETSI，European Telecommunications Standards Institute)主导的多接入边缘计算平台标准，从最初的移动边缘计算平台演进到基于虚拟网络功能(VNF，Virtual Network Feature)的多接入边缘计算平台，通过将MEC应用、平台、资源虚拟化和服务化的方式提供更高效的业务运行服务，以满足不同业务在处理能力上的差异化需求。
相关技术中，3GPP在标准TS23.501和TS23.502对5G核心网(5GC，5G core)与MEC的结合给出如图1所示的系统框架。首先，为使能垂直行业低时延、高带宽、高可靠边缘应用，UPF下沉到园区靠近MEC，通过UPF的本地分流技术、即上行过滤器/IPv6分支点(UL-CL/IPv6 BP，Uplink Classifier/IPv6 Branching Point)将数据转发到MEC平台(MEP，MEC Platform)；其次，核心网应用功能(AF，Application Function)下沉到MEC平台，与核心网的网络 能力开放功能(NEF，Network Exposure Function)对接，为部署于MEP上的应用提供更好的数据流控制策略(编码策略、QoS策略、路由策略等)。
MEC平台，主要包括：MEC系统层(MEC system-level)、MEC主机层(MEC host level)。ETSI定义的MEC的主机层与系统层的架构如图2所示。其中，MEC编排器(MEO，MEC orchestrator)又称MEC应用编排器(MEAO，MEC application orchestrator)，是MEC系统层管理的核心，支持的功能包括：
1)维护MEC系统的整体视图(即整体部署)；比如MEC的主机部署、MEC的可用资源分配、可用的MEC服务的调用、系统拓扑等；
2)管理MEC应用包的上线，包括：检查应用包的完整性和真实性；确认应用规则和需求，并判断是否需要调整应用规则和需求，若需要调整，则调整应用规则和需求以与运营商的策略相符；保存应用包的上线记录，以及为处理该应用准备虚拟基础设施管理器；
3)基于约束(比如时延、可用资源、可用服务等)为应用的初始化选择合适的MEC主机；
4)触发应用的启动和结束；
5)触发应用的按需迁移。
CPE接入MEC系统的流程如图3所示，首先，CPE通过终端路由选择策略(URSP，UE Route Selection Policy)或接入网发现和选择策略(ANDSP，Access Network Discovery and Selection Policy)网元发现和选择路由策略。URSP在3GPP TS 23.503中定义，是一组一个或多个URSP规则，其中一个URSP规则包括URSP规则的优先级值、流量描述符等；ANDSP用于控制与非3GPP接入网络上的接入网络发现和选择相关的UE行为。其次，CPE通过ATSSS网元进行业务分流和调度。3GPP TS23.501中描述了基于非3GPP接入的ATSSS架构，ATSSS即Access Traffic Steering，Switching，Splitting，又称接入流量控制、交换和分流，是一种网络级的流量聚合技术，通过使用对用户透明的、平衡移动网络和非3GPP接入之间数据流量的方法。最后，UE通过5G物理层(PHY，Physical)、5G基站无线接入网(RAN，wireless access network)传入到5G核 心网，然后访问MEP上的应用服务。
5G CPE设备相当于5G工业路由器，路由方案和大多数市面上的路由器是一样的，主要涉及到网络层的IP报文转换。图4为一种5G CPE的路由方案的示意图，如图4所示，5G CPE一般由5G调制解调器(Modem)和5G路由器(Router)两部分组成，5G Modem负责5G UE协议栈、基带、射频处理，将5G信号转化为网口信号。5G Router负责路由功能，将5G调制解调器(Modem)的网口数据转化为局域网内Wi-Fi、ZigBee等数据。图5为一种传输控制协议/网际协议(TCP/IP，Transmission Control Protocol/Internet Protocol)网络层的IP报文头的结构示意图。
目前大多数CPE都是基于DD-WRT、Tomato、OpenWRT等第三方路由固件或衍生的修改版固件进行开发设计的。“IP五元组”包括源IP地址、源端口、目的IP地址、目的端口、传输层协议。其中，IP报文头中的“标识(identification)”字段占16位，IP软件在存储器中维持一个计数器，每产生一个数据报，计数器就加1，并将此值赋给标识字段，标识字段用于标识属于同一IP分组的数据片，属于同一IP分组的数据片具有相同的标识字段值。边缘计算平台(MEP)收到IP流后，由于源IP地址已经进行了NAT转化，并不能从标识字段区分出CPE后端的网络类型等信息。
相关技术中提供了一种5G CPE的转发方法，首先由终端A通过5G CPE向终端B发送IP报文，该报文的目的IP地址为终端B的IP地址，源IP地址就是终端A的IP地址，目标MAC地址就是其CPE的端口1(Port1)的MAC地址，源MAC地址就是终端A的MAC地址；如图6(a)通过CPE前的IP五元组的示意图所示。其次，CPE收到报文，发现其目的MAC为本机Port1端口的，表明需要本机来进行进一步解析(如果目的MAC不是本机，表明直接进行二层转发，不需要再解析帧的其他内容了)；再次，CPE进一步解析报文，得知帧所承载的协议类型为IPv4(协议类型值＝0x800)，即需要进行IPv4转发；最后，查IP转发表(FIB表，Forwarding Info Base)，得知该报文并不是发给自己的，而是需要送往出端口4(Port4，即4G/5G蜂窝网接口)，因此，CPE不 再继续分析IP头后面的内容；CPE将目的MAC更换成终端B的MAC，将源MAC更换成出端口4(Port4)的MAC，将源IP地址通过NAT转换为公有IP地址，并将报文从端口4(Port4)发送出去；如图6(b)通过CPE后的IP五元组的示意图所示。
在当前CPE普遍存在的行业应用场景中，CPE被用作5G信号到其他信号制式(Wi-Fi、光纤、有线、HDMI、蓝牙等)的转换网关，以满足不支持5G接入的医疗设备能够接入到5G网络中，以及接入到基于网络切片技术构建的、医疗专属服务的医疗专用网络中；但在实际的业务匹配过程中，接入到CPE的网络呈现多样化和复杂化(Wi-Fi、光纤、有线、HDMI、蓝牙等)、业务端到端QoS保障的差异化需求等特点，如图7所示，以下提供几种业务场景：
业务场景1：通过Wi-Fi接入CPE并访问MEC上的应用服务，普遍承载的是对网络质量(吞吐量、端到端时延、服务级别协议(SLA，Service Level Agreement)保障等)要求不高的业务，比如办公自动化(OA，Office Automation)类应用、公众类应用等。
业务场景2：通过光纤或者有线接入CPE并访问MEC上的应用服务，通常是对网络质量(吞吐量、端到端时延、SLA保障等)要求较高的业务，比如医疗影像设备、医疗超声设备以及其他医学检测或监控类设备等。
业务场景3：通过蓝牙、罗拉(LORA)等接入CPE并访问MEC上的应用服务，是对时延要求很高但对吞吐量要求不高的业务，比如定位类业务、设备管控类业务等。这类业务需要实时更新位置信息或者接受指令，以保障业务执行的准确性与快速性。
业务场景4：通过网际协议安全(IPSec，Internet Protocol Security)虚拟专用网络(VPN，Virtual Private Network)的隧道模式接入CPE并访问MEC上的应用服务，主要是对数据安全性要求特别高的业务。
为了使能CPE可以有效支持上述所提及的四种垂直行业的业务场景，需要让MEC侧的编排器(MEAO/MEO)能够识别接入到CPE的不同业务类型或者接入网络类型，以及所接入的业务或者网络对端到端传输质量的要求(传输吞 吐量、传输时延、传输SLA等)；从而使得MEC的编排器(MEAO/MEO)在对MEC上应用服务进行编排时，能够保障接入到CPE的业务或网络性能的差异化要求。基于现有IP层协议实现的5G CPE而言，从技术上存在两个关键问题：
1、对于多对一的场景，例如，业务场景1、业务场景2、业务场景3的混合IP数据流。根据上述CPE的路由方法，由于IP报文头的源IP地址已经由NAT转换为公有IP地址，所以“后端接入到CPE的网络或者业务IP数据流”与“CPE接入到MEC的IP数据流”没有形成映射关系，因此，现有技术无法从CPE的5G蜂窝端口的IP数据报文中判断出该CPE接入的网络或业务类型，MEC的编排器MEAO/MEO无法动态根据接入到CPE的网络数据的优先级，以保障业务的差异化传输要求。
2、对于“一对一”的场景，例如业务场景4的单一IP数据流。根据上述CPE的VPN功能，由于IPSec VPN的隧道方式针对IP数据流(包括IP报头)加密后再封装了一个外网IP头，因此通过“IPSec VPN方式后端接入到CPE的网络(业务)IP数据流”与“CPE接入到MEC的IP数据流”也无法形成映射关系，现有技术依然无法识别接入到CPE的IPSec数据流，MEC的编排器MEAO/MEO无法动态根据接入到CPE的网络(业务)数据的优先级，以保障业务的差异化传输要求。
上述现有CPE存在的问题，会导致5G CPE与终端之间的多制式网络或网络类型的差异化网络需求无法有效传递到MEC侧，MEC业务系统的编排器MEAO/MEO无法获取网络类型(或业务类型)信息，无法针对具体业务进行合理有效的编排，最终无法保障业务端到端的性能。
基于此，在本申请的各种实施例中，第一设备，用于向第二设备发送业务数据；第二设备，用于接收来自第一设备的业务数据；所述业务数据基于至少一个第一数据合并得到。
图8为本申请实施例提供的一种通信方法的流程示意图；如图8所示，所述方法应用于第一设备，所述方法包括：
步骤801、向第二设备发送业务数据；所述业务数据基于至少一个第一数据合并得到。
实际应用时，所述第一设备为CPE；
所述第二设备为多接入边缘计算设备(MEC，Multi-access Edge Computing)，也可以为其他具备无线网络信息应用程序接口(API)交互能力，以及计算、存储、分析功能的信息技术(IT)的通用平台。
本申请实施例对所述第一设备、所述第二设备的名称不作限定，只要能实现所述第一设备、所述第二设备的功能即可。
在一些实施例中，所述方法还包括：
根据预设的第一合并策略和/或所述第一指令，合并所述至少一个第一数据，得到所述业务数据。
这里，所述第一合并策略为第一设备保存的本地的合并策略；所述合并策略用于指示合并第一数据的方式。所述第一数据为待上传到第二设备的数据。
第一设备接收到通过不同网络类型传输的、和/或不同业务需求的第一数据后，一种示例，第一终端根据本地的合并策略可以确定合并第一数据的方式，根据确定的合并第一数据的方式合并所述至少一个第一数据，得到所述业务数据；
另一种示例，第一终端根据第二设备发送的第一指令，确定出第二设备发送的第二合并策略，根据第二合并策略也可以确定合并第一数据的方式，根据确定的合并第一数据的方式合并所述至少一个第一数据，得到所述业务数据。
再一种示例，第一终端根据第一合并策略和/或第二合并策略(可以从中任选一个，也可以按照预设的不同合并策略的优先级选择一个)，确定合并第一数据的方式，根据确定的合并第一数据的方式合并所述至少一个第一数据，得到所述业务数据。
在一些实施例中，所述方法还包括：
向第二设备发送第一信令和/或第一请求；所述第一信令用于说明业务传输性能；所述第一请求根据第一网络的传输性能参数和/或第二网络的传输性能参 数确定；
接收来自所述第二设备的第一指令；所述第一指令用于指示第一设备进行数据合并。
以下对第一信令、第一请求、第一指令分别进行说明。
所述第一信令用于说明业务传输性能，也可以描述为第一网络的业务传输性能上报(PRTL，Performance reporting of traffic link to UE)。第一网络指目标设备(如医疗设备)和第一设备之间的网络。
这里，考虑到任何系统都有不同程度的信令传输时延，业务的性能指标也在实时变化中，第一设备(如CPE)向第二设备(如MEC)发送第一信令(即PRTL)有两个重要作用：一是让第二设备(如MEC)快速适配第一设备(如CPE)后端网络或者业务的传输变化，二是避免过于频繁地向第一设备上传第一信令(也即PRTL)，确保网络传输开销可控。即根据不同的业务需要，允许在一定范围的信令传输时延情况下，第二设备(如MEC)能够快速适配第一设备(如CPE)后端网络或者业务的传输变化。
在一些实施例中，所述第一信令用于指示以下至少之一：
第一设备的标识、第一网络的网络类型、第一网络的网络连接状态、应用程序的性能信息。
这里，为了支持第一设备的第一信令的技术方案，需要在第一设备上行传输信令或者数据字段中反馈包含第一设备的标识、第一网络的网络类型、第一网络的网络连接状态、应用程序的性能信息中的至少一项，如表1、第一信令(即PRTL)的数据结构表所示。
Figure PCTCN2022134805-appb-000001
Figure PCTCN2022134805-appb-000002
表1
对于“CPE的标识”而言，其实现方式可以是媒体存取控制位址(MAC，Media Access Control Address)、国际移动用户识别码(IMSI，International Mobile Subscriber Identity)、身份标识号(ID，Identity document)等描述方式。当使用MAC地址描述方式时，使用该CPE的MAC地址作为全局唯一标识符，例如“2A:DA:0B:84:03:9B”；当使用IMSI时，使用运营商提供的手机卡的IMSI作为标识符；当使用ID表述方式时，使用手机号码或CPE对应的IMEI或厂家设定的出厂编号作为标识符。
对于“网络类型”而言，其实现方式可以是索引数组、字符串数组或者Bitmap。假设CPE支持无线通信技术(Wi-Fi，Wireless Fidelity)、蓝牙、红外、窄带物联网(NB-IoT，Narrow Band Internet of Things)、高清多媒体接口(HDMI，High Definition Multimedia Interface)、光纤、VPN等网络类型。假设当前接入到CPE有包括Wi-Fi、蓝牙、光纤等3种网络；当使用数字表述方式时，比如0表示Wi-Fi，1表示蓝牙，5表示光纤，然后将0/1/5放入索引数组；当使用字符串表述方式时，可以使用“Wi-Fi”表示无线局域网Wi-Fi网络，“Bluetooth”表示蓝牙，“fiber”表示光纤，然后将“Wi-Fi、Bluetooth、fiber”放入字符串数组；当使用bitmap表述方式时，使用8位或16位的bitmap，将第0、1、5的bit位设置为1，分别表示Wi-Fi、蓝牙、光纤3中网络，其他为默认为0。
对于“网络连接状态”而言，其实现方式可以是布尔型或字符串。当使用布尔型表述方式时，可以使用1表示网络连接正常，使用0表示网络异常断开；当使用字符串表述方式时，使用“up”表示网络连接正常，使用“down”表示网络异常断开。只有当CPE的网络连接状态是正常时，才会发送STC指示， 否则不发送。
对于“应用程序的性能信息”而言，至少包含应用标识、吞吐量、时延、丢包率。对于所包含的信息的详细实现方式描述如下：
对于“应用标识(appD)”而言，其实现方式是ETSI MEC协议中的应用描述appD。当使用appD表述方式时，appD的属性字段包括应用程序的身份标识(appDId)、应用程序名(appName)、应用程序提供方(appProvider)、应用程序软件版本(appSoftVersion)、应用程序版本号(appDVersion)、应用程序信息名(appInfoName)、应用程序说明(appDescription)、虚拟计算描述符(virtualComputeDescriptor)、应用程序暴露的外部接口(appExtCpd)、应用程序所需服务(appServiceRequired)、应用程序业务选项(appServiceOptional)、应用程序产生的服务(appServiceProduced)、应用程序所需功能(appFeatureRequired)、应用程序可选功能(appFeatureOptional)、传输依赖关系(transportDependencies)、应用程序路由规则(appTrafficRule)、应用程序DNS规则(appDNSRule)、应用程序延迟(appLatency)、终止应用程序实例操作的配置参数(terminateAppInstanceOpConfig)、更改应用程序实例状态的配置参数(changeAppInstanceStateOpConfig)。
对于“吞吐量”而言，表示在没有帧丢失的情况下，CPE能够接收并转发的最大数据速率，其实现方式是整数，单位是比特每秒(bps)或者比特每兆(Mbps)或者其他。
对于“时延”而言，表示从一个CPE后端接收到转发到前端出口所需要的时间，其实现方式是整数，单位是毫秒或秒，例如3ms。
对于“丢包率”而言，指在网络传输过程中丢失报文占传输报文的百分比，其实现方式是浮点型数字表述，例如3.5％。
在一些实施例中，所述向第二设备发送第一信令包括以下至少之一：
周期性向第二设备发送第一信令；
非周期性向第二设备发送第一信令。
在一些实施例中，所述非周期性向第二设备发送第一信令包括：
确定第一网络的传输性能参数超过预设阈值时，向第二设备发送第一信令。
其中，所述第一网络为目标设备和所述第一设备之间的网络；例如，所述目标设备可以为医疗设备，所述第一网络为医疗设备和CPE之间的网络。所述第一网络的网络类型包括以下至少之一：Wi-Fi、Bluetooth、Zigbee、NB-loT、LoRa、红外网络等。
所述传输性能参数，包括以下至少之一：吞吐量、时延、丢包率。
也即，第一信令(即PRTL)的触发策略包括周期性触发和非周期性触发两种方式。
周期性触发指：无论第一网络的传输性能是否发生变化，每隔一段固定的时间(可以由开发人员预先设定，或者，由应用者设定)就向第二设备(如MEC)上传一次第一信令(即PRTL)，时间的周期单位可以是毫秒、秒、分、时等；
非周期性触发：为了避免频繁地向第二设备(如MEC)上传第一信令(即PRTL)，导致不必要的网络资源开销，只有当第一网络的传输性能的变化超出了触发条件的阈值，才向第二设备(如MEC)发送第一信令(即PRTL)。触发条件可以使用“与(and)/或(or)”的逻辑条件进行组合。第一网络的传输性能参数(吞吐量、时延、丢包率)变化的触发条件的实施例如下表2、第一网络的传输性能参数变化的触发条件表所示：
  吞吐量 时延 丢包率 组合条件
触发条件A 2.1％ 1.8％ 3％ 与
触发条件B 2.8％ 1.3％ 1％ 或
触发条件C 3.0％ 2％ 1.5％ 混合
表2
所述吞吐量为变化百分比阈值，记做throughput_per；
所述时延为变化百分比阈值，记做delay_per；
所述丢包率为变化百分比阈值，记做loss_per。
Figure PCTCN2022134805-appb-000003
Figure PCTCN2022134805-appb-000004
Figure PCTCN2022134805-appb-000005
具体地，表2中的阈值可以根据业务实际情况进行调整，例如，根据表2可以得到触发条件如下所示：
触发条件A：(throughput_per>2.1％)and(delay_per>1.8％)and(loss_per>3％)；
触发条件B：(throughput_per>2.8％)or(delay_per>1.3％)or(loss_per>1％)；
触发条件C：(throughput_per>3.0％and delay_per>2％)or(loss_per>1.5％)。
当满足上述任一触发条件，上传第一信令。
优选地，在非周期性触发时，可以在触发条件前，加入时间窗口(例如10s)的判断，只有超过设置的时间窗口，才进行上述触发条件的判断，可以进一步避免网络传输资源开销。
时间窗口可以是固定或者变化的，当第一信令(即PRTL)触发比较频繁时，可以适当地增大时间窗口；当第一信令(即PRTL)触发比较少时，可以适当地减小时间窗口。
在一些实施例中，所述第一指令用于指示第一设备进行数据合并，也可以描述为第一网络的业务流量合并指示(STC，Strategy of traffic combination at UE)。
所述第一指令，包括以下至少之一：
第一设备的标识、第一网络的网络类型、本地配置标识、第二合并策略。
其中，所述第二合并策略，包括以下至少之一：
应用程序的标识、各应用程序的流量比例分配类型、各应用程序的流量比例分配长度、各应用程序的流量比例分配策略；
其中，所述流量比例分配类型采用数字和/或字符串的方式表示；
所述流量比例分配长度采用数字的方式表示；
所述流量比例分配策略采用字符串和/或码本索引的方式表示。
所述本地配置标识用于指示所述第一设备是否根据所述第二设备发送的第二合并策略进行数据合并。
所述本地配置标识与第二合并策略之间存在耦合关系。当本地配置标识允许第一设备(如CPE)对应用数据的合并进行本地配置的场景下，存在以下的情况与处理流程与方法，如下所示：
本地配置的优先级，高于从第二设备(如MEC)下发的配置，即在一些实施例中，所述第一合并策略的优先级可以高于所述第一指令中的第二合并策略的优先级；
当本地配置缺失的情况下，使用第二设备(如MEC)下发的配置；
当本地配置与第二设备(如MEC)的配置同时存在时，第一设备(如CPE)使用本地配置。
具体来说，第一设备(如CPE)可以根据接收到的第一指令(即STC)，完成数据的合并与“多对一”映射功能，如表3、第一指令(即STC)的数据结构表所示。当第一设备(如CPE)没有收到STC时，按照默认的流量合并策略、即第一合并策略执行。
Figure PCTCN2022134805-appb-000006
表3
对于“CPE的标识”和“网络类型”而言，实现方式如表1中的“CPE的标识”和“网络类型”相同，这个不再赘述。
对于“本地配置标识”而言，其实现方式可以是布尔型参数或字符串。当使用布尔型参数时，如果本地配置标识为1时，允许进行本地配置；如果本地配置标识为0时，不允许进行本地配置。当使用字符串时，如果本地配置标识为“true”时，允许进行本地配置，如果本地配置标识为“false”时，不允许进行本地配置。
对于“第二合并策略”而言，至少包含应用程序的标识、各应用程序的流量比例分配类型、各应用程序的流量比例分配长度、各应用程序的流量比例分配策略。
对于“应用程序的标识(appD)”而言，实现方式如表1中的“应用程序的标识(appD)”相同，这里不再赘述。每个应用标识都对应有相应的流量比例分配参数，包括流量比例分配类型、流量比例分配长度、流量比例分配策略。
对于“流量比例分配类型(quota_type)”而言，其实现方式可以是数字或字符串。当使用数字时，如果quota_type为1表示按照时间纬度进行分配，如果quota_type为2表示按照存储空间纬度进行分配。当使用字符串时，如果quota_type为“time”表示按照时间纬度进行分配，如果quota_type为“memory”表示按照存储空间纬度进行分配。
对于“流量比例分配长度(quota_length)”而言，其实现方式可以是数字。当quota_type为1时表示分配的传输时间长度，单位可以是毫秒、秒，例如100ms、10s等。当quota_type为2时表示分配的存储空间长度，单位可以是Byte、KB、MB、GB，例如10KB、5MB等。
对于“流量比例分配策略(quota_strategy)”而言，其实现方式可以是字符串或者是比例分配码本索引，或者其他同等描述方式。在为字符串描述方式下，以quota_strategy＝”App1,40％；App2,30％；App3,20％；App4,10％”为例，并且当quota_type＝1与quota_length＝10s的场景下，表示的是在10秒内，应用程序1传输4秒，应用程序2传输3秒，应用程序3传输2秒，应用程序4传输1秒。当在quota_type＝2并且quota_length＝100MB的场景下，表示的是应用程序1传输40MB数据量，应用程序2传输30MB数据量，应用程序3传输20MB 数据量，应用程序4传输10MB数据量。
优选地，对于流量比例分配策略(quota_strategy)为比例分配码本索引的实施方案之下，通过码本的方式配置流量比例分配策略。该指示方式下，一个quota_strategy ID即可表示多个多路数据的流量合并策略。比如当终端上接入了3个应用程序或者网络分别是A、B、C，同时假设码本集合为8。如表4、码本索引表所示，每列代表每个业务或者网络的数据传输比例。举例说明，从表3中可以看出，当ID＝0时(对应于P0所在的列)，编码码本为[1 0 0]，则表示只发送A的数据；当ID＝3(对应于P3所在的列)时，编码码本为[1/3 1/3 1/3],则表示A/B/C各占发送数据的1/3；当ID＝5时，编码码本为[0.7 0.1 0.2]，表示A发送数据占70％，B发送数据占10％，C发送数据占20％。
  P0 P1 P2 P3 P4 P5 P6 P7 P8
对应A的分配比例 1 0 0 1/3 0.2 0.7 0.34 0.4 0.5
对应B的分配比例 0 1 0 1/3 0.5 0.1 0.53 0.4 0.2
对应C的分配比例 0 0 1 1/3 0.3 0.2 0.13 0.2 0.3
表4
在一些实施例中，所述第一请求根据第一网络的传输性能参数和/或第二网络的传输性能参数确定；
所述第一请求也可以描述为业务流量合并指示(STC，Strategy of traffic combination at UE)。
实际应用时，第一设备(如CPE)根据第一网络的传输性能，并综合第一设备(如CPE)与第二设备(如MEC)之间的传输性能，主动向第二设备(如MEC)申请新的流量合并策略、即第二合并策略。即向第二设备(如MEC)发送第一请求。
所述第一请求(即TCR)的数据结构如表5、TCR的数据结构表所示。
参数名 数据类型 说明
CPE的标识 字符串 用于标识该CPE的全局唯一性
网络类型 数字或字符串 用于表示CPE与终端之间的网络类型
第二合并策略 结构体 用于主动向MEC申请新的流量合并策略
表5
对于“CPE的标识”和“网络类型”而言，实现方式如表1中的“CPE的标识”和“网络类型”相同，这个不再赘述。
对于“第二合并策略”而言，实现方式如表3中的“第二合并策略”相同，这个不再赘述。
所述第一请求(即TCR)的触发策略可以是非周期性触发方式。第一设备(如CPE)综合评估第一网络的传输性能、第一设备(如CPE)与第二设备(如MEC)之间的传输性能，达到了阈值条件才会向第二设备(如MEC)发送第一请求(即TCR)。第一请求(即TCR)达到触发条件需要同时满足如下两个条件：
1)、第一设备(如CPE)的第一网络的传输性能指标(指目标设备与第一设备之间的传输性能指标)的变化没有达到第一信令(即PRTL)的触发策略；
2)、第一设备(如CPE)与第二设备(如MEC)之间的传输指标(吞吐量、时延、丢包率)的传输性能变化达到了阈值。第一设备(如CPE)与第二设备(如MEC)之间的性能指标的变化参考第一信令(即PRTL)的触发策略，根据业务实际需要设置各个传输指标的触发阈值和触发组合，这里不再赘述。
在一些实施例中，所述方法还包括：生成第一请求。
具体来说，第一设备(如CPE)可以根据第一网络的传输性能指标、第一设备(如CPE)与第二设备(如MEC)之间传输指标的性能，综合判断生成第一请求(即TCR)。基于上述关于第一信令(即PRTL)的说明可知，第一网络的传输性能指标变化太大时会发送第一信令(即PRTL)，所以生成第一请求(即TCR)主要考虑第设备与第二设备之间的网络性能指标变化。
生成第一请求(即TCR)的相关实施例如下所示：
1)、当第一设备(如CPE)与第二设备(如MEC)之间的时延变化太大，时延变化的百分比超过了一定阈值，第一请求(即TCR)中的quota_type设置 为时间纬度，即将quota_type设置为1。当quota_strategy实现方式是字符串时，针对时延要求低的应用，其流量分配的时间比例更加少；针对时延要求高的应用，其流量分配的时间比例更加多。当quota_strategy实现方式是码本索引时，针对时延要求低的应用，其码本索引应选用时间比例更少的索引；针对时延要求高的应用，其码本索引应选用时间比例更多的索引。
2)、当第一设备(如CPE)与第二设备(如MEC)之间的吞吐量变化太大，吞吐量变化的百分比超过了一定阈值，TCR中的quota_type设置为空间纬度，即将quota_type设置为2。当quota_strategy实现方式是字符串时，针对吞吐量要求低的应用，空间分配的比例更加少；针对吞吐量要求高的应用，空间分配的比例更加多。当quota_strategy实现方式是码本索引时，针对吞吐量要求低的应用，其码本索引应选用空间比例更少的索引；针对吞吐量要求高的应用，其码本索引应选用空间比例更多的索引。
当第一设备(如CPE)与第二设备(如MEC)之间的时延和吞吐量变化都很大时，可以根据业务实际需要选择以时延指标为准或以吞吐量指标为准。
在一些实施例中，所述第一数据为通过第一网络传输的数据。
这里，所述第一网络的网络类型包括以下至少之一：Wi-Fi、Bluetooth、Zigbee、NB-loT、LoRa、红外网络等。
应用时，目标设备与第一设备通信，第一设备与第二设备通信；
所述第一网络为目标设备和所述第一设备之间的网络；例如，所述目标设备可以为医疗设备，所述第一网络为医疗设备和CPE之间的网络。所述第一网络也可以描述为第二跳网络；相应的，所述第二跳性能指标指第二跳网络的传输性能指标；第二跳数据为第二跳网络传输的数据。
所述第二网络为所述第一设备与所述第二设备之间的网络，所述第二网络也可以描述为第一跳网络。
这里，所述目标设备为实际应用所涉及到的设备，如医疗设备等。
相应的，图9为本申请实施例提供了另一种通信方法的流程示意图；如图9所示，所述方法应用于第二设备，所述方法包括：
步骤901、接收来自第一设备的业务数据；所述业务数据基于至少一个第一数据合并得到。
实际应用时，所述第一设备为CPE；
所述第二设备为移动边缘计算设备(MEC)，也可以为其他具备无线网络信息应用程序接口(API)交互能力，以及计算、存储、分析功能的信息技术(IT)的通用平台。
本申请实施例对所述第一设备、所述第二设备的名称不作限定，只要能实现所述第一设备、所述第二设备的功能即可。
在一些实施例中，所述方法还包括：
接收第一设备发送的第一信令和/或第一请求；所述第一信令用于说明业务传输性能；所述第一请求根据第一网络的传输性能参数和/或第二网络的传输性能参数确定；
向所述第一设备发送第一指令；所述第一指令用于指示第一设备进行数据合并。
在一些实施例中，所述方法还包括：生成第一指令。
以第二设备为MEC为例，根据以上关于MEC的编排器MEO的功能描述，MEO能够获取的数据包括时延、可用MEC服务、可用MEC资源，此处的时延是第一设备(如CPE)与第二设备(如MEC)之间的时延，无法获取到第二跳业务的各个应用的具体性能指标，所以要针对第二跳业务的各个应用的性能指标进行分析和判断，以生成第一指令(即STC)。
根据不同的业务需要，允许在一定范围的信令传输时延情况下，M-TMMM模块能够快速生成和下发第一指令(即STC)，以适配第一设备(如CPE)后端网络或者业务的传输变化。当MEO获取到第二跳业务数据的性能参数后，针对时延和吞吐量的不同要求，根据业务实际需要来分配不同的流量比例。生成第一指令(即STC)的相关实施例如下所示：
对时延有要求的应用，以时间纬度为准，将quota_type设置为1。当quota_strategy实现方式是字符串时，针对时延要求低的应用，其流量分配的时 间比例相对少一点；针对时延要求高的应用，其流量分配的时间比例相对多一点。当quota_strategy实现方式是码本索引时，针对时延要求低的应用，其码本索引选用时间比例更少的索引；针对时延要求高的应用，其码本索引选用时间比例更多的索引；
对吞吐量有要求的应用，以空间纬度为准，将quota_type设置为2。当quota_strategy实现方式是字符串时，针对吞吐量要求低的应用，空间分配的比例相对少一点；针对吞吐量要求高的应用，空间分配的比例相对多一点。当quota_strategy实现方式是码本索引时，针对吞吐量要求低的应用，其码本索引选用空间比例更少的索引；针对吞吐量要求高的应用，其码本索引选用空间比例更多的索引；
对时延和吞吐量都有要求的应用，根据不同业务可以优先以时延或空间指标的要求为准。
具体地规则可以预先设定并保存在第二设备中，应用时可以基于预设的规则确定出第二合并策略。
在一些实施例中，所述第一信令用于指示以下至少之一：
第一设备的标识、第一网络的网络类型、第一网络的网络连接状态、应用程序的性能信息。
在一些实施例中，所述第一指令，包括以下至少之一：
第一设备的标识、第一网络的网络类型、本地配置标识、第二合并策略。
在一些实施例中，所述第二合并策略，包括以下至少之一：
应用程序的标识、各应用程序的流量比例分配类型、各应用程序的流量比例分配长度、各应用程序的流量比例分配策略；
其中，所述流量比例分配类型采用数字和/或字符串的方式表示；
所述流量比例分配长度采用数字的方式表示；
所述流量比例分配策略采用字符串和/或码本索引的方式表示。
在一些实施例中，所述本地配置标识用于指示所述第一设备是否根据所述第二设备发送的第二合并策略进行数据合并。
在一些实施例中，所述第一设备保存的第一合并策略的优先级高于所述第一指令中的第二合并策略的优先级。
在一些实施例中，所述传输性能参数，包括以下至少之一：吞吐量、时延、丢包率。
在一些实施例中，所述第一数据为通过第一网络传输的数据。
在一些实施例中，所述第一网络为目标设备和所述第一设备之间的网络；
所述第二网络为所述第一设备与所述第二设备之间的网络。
关于第一信令、第一请求、第一指令的其他说明已在图8所示方法中详细说明，这里不再赘述。
通过本申请实施例提供的方法，第一设备(如CPE)可以有效支持以上提及的四种场景(业务场景1、业务场景2、业务场景3、业务场景4)，从而能够保障在上行数据的传输过程中，以及所接入到CPE的业务或者网络性能的差异化要求。
第二设备(如MEC)可有效识别到第一设备(如CPE)与终端之间的网络类型或者业务类型，以及传输性能的差异化要求，能够有效保障第一设备(如CPE)与终端之间网络或者业务的传输性能差异化需求。
上述方案提供的第一设备、第二设备及两者实现的系统架构，可运营、更安全、可落地、可演进，更加贴合垂直行业客户需求。
图10为本申请实施例提供的一种通信系统的结构示意图；如图10所示，所述通信系统包括：第一设备、第二设备；所述第一设备为CPE；所述第二设备为MEC。
以下以所述第一设备为CPE、所述第二设备为MEC为例进行说明。
在不改动物理层的前提下，CPE增加或具有流量映射模块(M-TMM)、MEC的编排器MEO上增加或具有流量映射管理模块(M-TMMM)。
流量合并和映射指的是多个CPE第二跳数据到蜂窝网络的“多对一”的合并和映射功能，以下简称为“流量合并”或“流量映射”。其中，流量映射模块与流量映射管理模块的功能如下所述：
流量映射模块(M-TMM，Multiple traffic mapping module)：承载于CPE之上，实现对CPE接入的多个网络或者业务数据到5G传输通道的流量合并和映射功能，通过该模块可有效保障CPE与终端之间的多个网络或者业务的传输性能保障，比如传输速率、传输时延、丢包率等关键性能指标。
流量映射管理模块(M-TMMM，Multiple traffic mapping management module)：承载于MEC系统中，实现对CPE侧后端多接入网络或者业务数据的第二合并策略管理功能，通过该模块可有效决策并指导CPE后端网络或者业务的传输方法。
信令交互：流量映射模块被流量映射管理模块所管理，通过流量映射模块与流量映射管理模块之间的信令交互，从而实现对CPE与终端之间的网络或者业务的SLA传输性能保障。
在本实施例中，第一跳网络指CPE与MEC之间的网络，第二跳网络指的是CPE与医疗设备之间的网络。在CPE中的流量映射模块与MEC系统中的流量映射管理模块的信令交互流程如图11所示。其至少包括以下步骤：
步骤1101、CPE向MEC发送第二跳网络的业务传输性能(PRTL，Performance reporting of traffic link to UE)；
具体地，将接入到CPE的网络或者业务连接的实际传输性能，上报给MEC侧的流量映射管理模块。特别注意的是，接入到CPE的网络或者业务连接，指的是通过Wi-Fi、Bluetooth、HDMI、光纤、网线或者APP等方式与CPE建立的连接。
所述接入到CPE的网络指第二跳网络，如医疗设备接入到CPE的网络。
所述PRTL相当于图8和图9所示方法中的第一信令，具体已在图8和图9所示方法中详细说明，这里不再赘述。
步骤1102、CPE接收MEC发送的第二跳网络的业务流量合并指示(STC，Strategy of traffic combination at UE)；
根据CPE上报的CPE第二跳网络的业务传输性能，MEC侧的流量映射管理模块针对CPE侧的流量进行策略调度，并将策略调度内容通过该STC下发 给CPE，CPE根据接收到的STC，完成数据的合并与映射功能。
所述STC相当于图8和图9所示方法中的第一指令，具体已在图8和图9所示方法中详细说明，这里不再赘述。
步骤1103、CPE向MEC发送第二跳网络的业务数据传输(DTC，Data transmission at CPE)；
CPE根据接收的第二跳网络的业务流量合并指示，完成CPE第二跳业务数据的组装与合并，完成从CPE到MEC侧的数据传输过程。
所述方法还可以包括：
步骤1101-1、CPE向MEC发送第二跳网络的业务流量合并请求(TCR，Traffic combination requirement at UE)；
具体地，CPE可以根据第二跳网络的传输性能，并综合第一跳网络的传输性能，主动向MEC侧的流量映射管理模块申请新的流量合并方式，以快速适配CPE后端网络或者业务的传输变化。
所述TCR相当于图8和图9所示方法中的第一请求，具体已在图8和图9所示方法中详细说明，这里不再赘述。
所述步骤1102-1可以与步骤1102同时执行，也可以在1102之前或之后，这里不做限定。
需要说明的是，关于上述技术方案的具体实施例、PRTL、STC、DTC、TCR，可以参考图8和图9所示方法，这里不再赘述。
为了实现本申请实施例第一设备侧的方法，本申请实施例还提供了一种通信装置，设置在第一设备上，如图12所示，该装置包括：
第一通信单元1201，配置为向第二设备发送业务数据；所述业务数据基于至少一个第一数据合并得到。
在一些实施例中，所述第一通信单元1201，还配置为向第二设备发送第一信令和/或第一请求；所述第一信令用于说明业务传输性能；所述第一请求根据第一网络的传输性能参数和/或第二网络的传输性能参数确定；
接收来自所述第二设备的第一指令；所述第一指令用于指示第一设备进行 数据合并。
在一些实施例中，所述第一设备还包括：第一处理单元1202，配置为根据预设的第一合并策略和/或所述第一指令，合并所述至少一个第一数据，得到所述业务数据。
在一些实施例中，所述第一指令，包括以下至少之一：
第一设备的标识、第一网络的网络类型、本地配置标识、第二合并策略。
在一些实施例中，所述第二合并策略，包括以下至少之一：
应用程序的标识、各应用程序的流量比例分配类型、各应用程序的流量比例分配长度、各应用程序的流量比例分配策略；
其中，所述流量比例分配类型采用数字和/或字符串的方式表示；
所述流量比例分配长度采用数字的方式表示；
所述流量比例分配策略采用字符串和/或码本索引的方式表示。
在一些实施例中，所述本地配置标识用于指示所述第一设备是否根据所述第二设备发送的第二合并策略进行数据合并。
在一些实施例中，所述第一合并策略的优先级高于所述第一指令中的第二合并策略的优先级。
在一些实施例中，所述第一信令用于指示以下至少之一：
第一设备的标识、第一网络的网络类型、第一网络的网络连接状态、应用程序的性能信息。
在一些实施例中，所述第一通信单元1201，配置为执行以下至少之一：
周期性向第二设备发送第一信令；
非周期性向第二设备发送第一信令。
在一些实施例中，所述第一通信单元1201，配置为确定第一网络的传输性能参数超过预设阈值时，向第二设备发送第一信令。
在一些实施例中，所述传输性能参数，包括以下至少之一：吞吐量、时延、丢包率。
在一些实施例中，所述第一数据为通过第一网络传输的数据。
在一些实施例中，所述第一网络为目标设备和所述第一设备之间的网络；
所述第二网络为所述第一设备与所述第二设备之间的网络。
实际应用时，所述第一通信单元1201和所述第一处理单元1202可由通信装置中的处理器结合通信接口实现。
为了实现本申请实施例第二设备侧的方法，本申请实施例还提供了一种通信装置，设置在第二设备上，如图13所示，该装置包括：
第二通信单元1301，配置为接收来自第一设备的业务数据；所述业务数据基于至少一个第一数据合并得到。
在一些实施例中，所述第二通信单元1301，配置为接收第一设备发送的第一信令和/或第一请求；所述第一信令用于说明业务传输性能；所述第一请求根据第一网络的传输性能参数和/或第二网络的传输性能参数确定；
向所述第一设备发送第一指令；所述第一指令用于指示第一设备进行数据合并。
在一些实施例中，所述第二设备还可以包括：第二处理单元1302，配置为生成第一指令。
在一些实施例中，所述第一信令用于指示以下至少之一：
第一设备的标识、第一网络的网络类型、第一网络的网络连接状态、应用程序的性能信息。
在一些实施例中，所述第一指令，包括以下至少之一：
第一设备的标识、第一网络的网络类型、本地配置标识、第二合并策略。
在一些实施例中，所述第二合并策略，包括以下至少之一：
应用程序的标识、各应用程序的流量比例分配类型、各应用程序的流量比例分配长度、各应用程序的流量比例分配策略；
其中，所述流量比例分配类型采用数字和/或字符串的方式表示；
所述流量比例分配长度采用数字的方式表示；
所述流量比例分配策略采用字符串和/或码本索引的方式表示。
在一些实施例中，所述本地配置标识用于指示所述第一设备是否根据所述 第二设备发送的第二合并策略进行数据合并。
在一些实施例中，所述第一设备保存的第一合并策略的优先级高于所述第一指令中的第二合并策略的优先级。
在一些实施例中，所述传输性能参数，包括以下至少之一：吞吐量、时延、丢包率。
在一些实施例中，所述第一数据为通过第一网络传输的数据。
在一些实施例中，所述第一网络为目标设备和所述第一设备之间的网络；
所述第二网络为所述第一设备与所述第二设备之间的网络。
实际应用时，所述第二通信单元1301和所述第二处理单元1302可由通信装置中的处理器结合通信接口实现。
需要说明的是：上述实施例提供的通信装置在进行通信时，仅以上述各程序模块的划分进行举例说明，实际应用中，可以根据需要而将上述处理分配由不同的程序模块完成，即将装置的内部结构划分成不同的程序模块，以完成以上描述的全部或者部分处理。另外，上述实施例提供的通信装置与通信方法实施例属于同一构思，其具体实现过程详见方法实施例，这里不再赘述。
基于上述程序模块的硬件实现，且为了实现本申请实施例第一设备侧的方法，本申请实施例还提供了一种第一设备，如图14所示，该第一设备1400包括：
第一通信接口1401，能够与第二设备进行信息交互；
第一处理器1402，与所述第一通信接口1401连接，以实现与第二设备进行信息交互，配置为运行计算机程序时，执行上述第一设备侧一个或多个技术方案提供的方法。而所述计算机程序存储在第一存储器1403上。
具体地，所述第一通信接口1401，配置为向第二设备发送业务数据；所述业务数据基于至少一个第一数据合并得到。
其中，在一实施例中，所述第一处理器1402，配置为根据预设的第一合并策略和/或所述第一指令，合并所述至少一个第一数据，得到所述业务数据。
在一实施例中，所述第一通信接口1401，还配置为：
向第二设备发送第一信令和/或第一请求；所述第一信令用于说明业务传输性能；所述第一请求根据第一网络的传输性能参数和/或第二网络的传输性能参数确定；
接收来自所述第二设备的第一指令；所述第一指令用于指示第一设备进行数据合并。
在一实施例中，所述第一通信接口1401，还配置为：
周期性向第二设备发送第一信令；和/或，
非周期性向第二设备发送第一信令。
在一实施例中，所述第一通信接口1401，还配置为：
确定第一网络的传输性能参数超过预设阈值时，向第二设备发送第一信令。
需要说明的是：第一处理器1402和第一通信接口1401的具体处理过程可参照上述方法理解。
当然，实际应用时，第一设备1400中的各个组件通过总线系统1404耦合在一起。可理解，总线系统1404用于实现这些组件之间的连接通信。总线系统1404除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。但是为了清楚说明起见，在图14中将各种总线都标为总线系统1404。
本申请实施例中的第一存储器1403用于存储各种类型的数据以支持第一设备1400的操作。这些数据的示例包括：用于在第一设备1400上操作的任何计算机程序。
上述本申请实施例揭示的方法可以应用于所述第一处理器1402中，或者由所述第一处理器1402实现。所述第一处理器1402可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过所述第一处理器1402中的硬件的集成逻辑电路或者软件形式的指令完成。上述的所述第一处理器1402可以是通用处理器、数字信号处理器(DSP，Digital Signal Processor)，或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。所述第一处理器1402可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。 结合本申请实施例所公开的方法的步骤，可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于存储介质中，该存储介质位于第一存储器1403，所述第一处理器1402读取第一存储器1403中的信息，结合其硬件完成前述方法的步骤。
在示例性实施例中，第一设备1400可以被一个或多个应用专用集成电路(ASIC，Application Specific Integrated Circuit)、DSP、可编程逻辑器件(PLD，Programmable Logic Device)、复杂可编程逻辑器件(CPLD，Complex Programmable Logic Device)、现场可编程门阵列(FPGA，Field-Programmable Gate Array)、通用处理器、控制器、微控制器(MCU，Micro Controller Unit)、微处理器(Microprocessor)、或者其他电子元件实现，用于执行前述方法。
基于上述程序模块的硬件实现，且为了实现本申请实施例第二设备侧的方法，本申请实施例还提供了一种第二设备，如图15所示，该第二设备1500包括：
第二通信接口1501，能够与第一设备和第三设备进行信息交互；
第二处理器1502，与所述第二通信接口1501连接，以实现与第一设备和第三设备进行信息交互，配置为运行计算机程序时，执行上述第二设备侧一个或多个技术方案提供的方法。而所述计算机程序存储在第二存储器1503上。
具体地，所述第二通信接口1501，配置为接收来自第一设备的业务数据；所述业务数据基于至少一个第一数据合并得到。
其中，在一实施例中，所述第二通信接口1501，还配置为：
接收第一设备发送的第一信令和/或第一请求；所述第一信令用于说明业务传输性能；所述第一请求根据第一网络的传输性能参数和/或第二网络的传输性能参数确定；
向所述第一设备发送第一指令；所述第一指令用于指示第一设备进行数据合并。
在一实施例中，所述第二处理器1502，配置为生成第一指令。
需要说明的是：第二通信接口1501和第二处理器1502的具体处理过程可 参照上述方法理解。
当然，实际应用时，第二设备1500中的各个组件通过总线系统1504耦合在一起。可理解，总线系统1504用于实现这些组件之间的连接通信。总线系统1504除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。但是为了清楚说明起见，在图15中将各种总线都标为总线系统1504。
本申请实施例中的第二存储器1503用于存储各种类型的数据以支持第二设备1500的操作。这些数据的示例包括：用于在第二设备1500上操作的任何计算机程序。
上述本申请实施例揭示的方法可以应用于所述第二处理器1502中，或者由所述第二处理器1502实现。所述第二处理器1502可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过所述第二处理器1502中的硬件的集成逻辑电路或者软件形式的指令完成。上述的所述第二处理器1502可以是通用处理器、DSP，或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。所述第二处理器1502可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本申请实施例所公开的方法的步骤，可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于存储介质中，该存储介质位于第二存储器1503，所述第二处理器1502读取第二存储器1503中的信息，结合其硬件完成前述方法的步骤。
在示例性实施例中，第二设备1500可以被一个或多个ASIC、DSP、PLD、CPLD、FPGA、通用处理器、控制器、MCU、Microprocessor、或其他电子元件实现，用于执行前述方法。
可以理解，本申请实施例的存储器(第一存储器1403、第二存储器1503)可以是易失性存储器或者非易失性存储器，也可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(ROM，Read Only Memory)、可编程只读存储器(PROM，Programmable Read-Only Memory)、可擦除可编程 只读存储器(EPROM，Erasable Programmable Read-Only Memory)、电可擦除可编程只读存储器(EEPROM，Electrically Erasable Programmable Read-Only Memory)、磁性随机存取存储器(FRAM，ferromagnetic random access memory)、快闪存储器(Flash Memory)、磁表面存储器、光盘、或只读光盘(CD-ROM，Compact Disc Read-Only Memory)；磁表面存储器可以是磁盘存储器或磁带存储器。易失性存储器可以是随机存取存储器(RAM，Random Access Memory)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(SRAM，Static Random Access Memory)、同步静态随机存取存储器(SSRAM，Synchronous Static Random Access Memory)、动态随机存取存储器(DRAM，Dynamic Random Access Memory)、同步动态随机存取存储器(SDRAM，Synchronous Dynamic Random Access Memory)、双倍数据速率同步动态随机存取存储器(DDRSDRAM，Double Data Rate Synchronous Dynamic Random Access Memory)、增强型同步动态随机存取存储器(ESDRAM，Enhanced Synchronous Dynamic Random Access Memory)、同步连接动态随机存取存储器(SLDRAM，SyncLink Dynamic Random Access Memory)、直接内存总线随机存取存储器(DRRAM，Direct Rambus Random Access Memory)。本申请实施例描述的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
需要说明的是：“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
另外，本申请实施例所记载的技术方案之间，在不冲突的情况下，可以任意组合。
以上所述，仅为本申请的较佳实施例而已，并非用于限定本申请的保护范围。

Claims (29)

  1. 一种通信方法，应用于第一设备，包括：
    向第二设备发送业务数据；所述业务数据基于至少一个第一数据合并得到。
  2. 根据权利要求1所述的方法，其中，所述方法还包括：
    向第二设备发送第一信令和/或第一请求；所述第一信令用于说明业务传输性能；所述第一请求根据第一网络的传输性能参数和/或第二网络的传输性能参数确定；
    接收来自所述第二设备的第一指令；所述第一指令用于指示第一设备进行数据合并。
  3. 根据权利要求2所述的方法，其中，所述方法还包括：
    根据预设的第一合并策略和/或所述第一指令，合并所述至少一个第一数据，得到所述业务数据。
  4. 根据权利要求3所述的方法，其中，所述第一指令，包括以下至少之一：
    第一设备的标识、第一网络的网络类型、本地配置标识、第二合并策略。
  5. 根据权利要求4所述的方法，其中，所述第二合并策略，包括以下至少之一：
    应用程序的标识、各应用程序的流量比例分配类型、各应用程序的流量比例分配长度、各应用程序的流量比例分配策略；
    其中，所述流量比例分配类型采用数字和/或字符串的方式表示；
    所述流量比例分配长度采用数字的方式表示；
    所述流量比例分配策略采用字符串和/或码本索引的方式表示。
  6. 根据权利要求4所述的方法，其中，所述本地配置标识用于指示所述第一设备是否根据所述第二设备发送的第二合并策略进行数据合并。
  7. 根据权利要求3所述的方法，其中，所述第一合并策略的优先级高于 所述第一指令中的第二合并策略的优先级。
  8. 根据权利要求2所述的方法，其中，所述第一信令用于指示以下至少之一：
    第一设备的标识、第一网络的网络类型、第一网络的网络连接状态、应用程序的性能信息。
  9. 根据权利要求2所述的方法，其中，所述向第二设备发送第一信令包括以下至少之一：
    周期性向第二设备发送第一信令；
    非周期性向第二设备发送第一信令。
  10. 根据权利要求9所述的方法，其中，所述非周期性向第二设备发送第一信令包括：
    确定第一网络的传输性能参数超过预设阈值时，向第二设备发送第一信令。
  11. 根据权利要求2或10所述的方法，其中，所述传输性能参数，包括以下至少之一：吞吐量、时延、丢包率。
  12. 根据权利要求1所述的方法，其中，所述第一数据为通过第一网络传输的数据。
  13. 根据权利要求2至12任一项所述的方法，其中，所述第一网络为目标设备和所述第一设备之间的网络；
    所述第二网络为所述第一设备与所述第二设备之间的网络。
  14. 一种通信方法，应用于第二设备，包括：
    接收来自第一设备的业务数据；所述业务数据基于至少一个第一数据合并得到。
  15. 根据权利要求14所述的方法，其中，所述方法还包括：
    接收第一设备发送的第一信令和/或第一请求；所述第一信令用于说明业务传输性能；所述第一请求根据第一网络的传输性能参数和/或第二网络的传输性能参数确定；
    向所述第一设备发送第一指令；所述第一指令用于指示第一设备进行数据合并。
  16. 根据权利要求15所述的方法，其中，所述第一信令用于指示以下至少之一：
    第一设备的标识、第一网络的网络类型、第一网络的网络连接状态、应用程序的性能信息。
  17. 根据权利要求15所述的方法，其中，所述第一指令，包括以下至少之一：
    第一设备的标识、第一网络的网络类型、本地配置标识、第二合并策略。
  18. 根据权利要求17所述的方法，其中，所述第二合并策略，包括以下至少之一：
    应用程序的标识、各应用程序的流量比例分配类型、各应用程序的流量比例分配长度、各应用程序的流量比例分配策略；
    其中，所述流量比例分配类型采用数字和/或字符串的方式表示；
    所述流量比例分配长度采用数字的方式表示；
    所述流量比例分配策略采用字符串和/或码本索引的方式表示。
  19. 根据权利要求17所述的方法，其中，所述本地配置标识用于指示所述第一设备是否根据所述第二设备发送的第二合并策略进行数据合并。
  20. 根据权利要求17所述的方法，其中，所述第一设备保存的第一合并策略的优先级高于所述第一指令中的第二合并策略的优先级。
  21. 根据权利要求15所述的方法，其中，所述传输性能参数，包括以下至少之一：吞吐量、时延、丢包率。
  22. 根据权利要求14所述的方法，其中，所述第一数据为通过第一网络传输的数据。
  23. 根据权利要求15至22任一项所述的方法，其中，所述第一网络为目标设备和所述第一设备之间的网络；
    所述第二网络为所述第一设备与所述第二设备之间的网络。
  24. 一种通信装置，设置在第一设备上，包括：
    第一通信单元，配置为向第二设备发送业务数据；所述业务数据基于至少一个第一数据合并得到。
  25. 一种通信装置，设置在第二设备上，包括：
    第二通信单元，配置为接收来自第一设备的业务数据；所述业务数据基于至少一个第一数据合并得到。
  26. 一种第一设备，包括：第一处理器和第一通信接口；其中，
    所述第一通信接口，配置为向第二设备发送业务数据；所述业务数据基于至少一个第一数据合并得到。
  27. 一种第二设备，包括：第二处理器和第二通信接口；其中，
    所述第二通信接口，配置为接收来自第一设备的业务数据；所述业务数据基于至少一个第一数据合并得到。
  28. 一种网络设备，包括：处理器及和配置为存储能够在处理器上运行的计算机程序的存储器，
    其中，所述处理器配置为运行所述计算机程序时，执行权利要求1至13任一项所述方法的步骤；或者，
    所述处理器配置为运行所述计算机程序时，执行权利要求14至23任一项所述方法的步骤。
  29. 一种存储介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现权利要求1至13任一项所述方法的步骤；或者，
    所述计算机程序被处理器执行时实现权利要求14至23任一项所述方法的步骤。
PCT/CN2022/134805 2021-12-24 2022-11-28 通信方法、装置、相关设备及存储介质 Ceased WO2023116355A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111598137.8A CN116346294A (zh) 2021-12-24 2021-12-24 通信方法、装置、相关设备及存储介质
CN202111598137.8 2021-12-24

Publications (1)

Publication Number Publication Date
WO2023116355A1 true WO2023116355A1 (zh) 2023-06-29

Family

ID=86877738

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/134805 Ceased WO2023116355A1 (zh) 2021-12-24 2022-11-28 通信方法、装置、相关设备及存储介质

Country Status (2)

Country Link
CN (1) CN116346294A (zh)
WO (1) WO2023116355A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN119254619A (zh) * 2024-09-18 2025-01-03 中国移动通信集团设计院有限公司 网络配置方法、系统、装置、设备、介质及产品

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116634469B (zh) * 2023-07-21 2023-09-19 南京源兴智达信息科技有限公司 一种基于多LoRa节点的数据传输管理系统及方法
CN118804074A (zh) * 2024-02-05 2024-10-18 中国移动通信有限公司研究院 物联数据的发送方法、接收方法、序号分配方法及设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105847355A (zh) * 2016-03-23 2016-08-10 重庆秒银科技有限公司 数据合并处理系统
CN107277940A (zh) * 2016-04-01 2017-10-20 宏达国际电子股份有限公司 处理无线资源控制连结恢复程序的装置及方法
US11071051B1 (en) * 2020-03-12 2021-07-20 Verizon Patent And Licensing, Inc. Systems and methods for SCEF-assisted MEC traffic breakout
CN113517957A (zh) * 2020-04-10 2021-10-19 华为技术有限公司 一种harq信息传输方法及装置

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013150500A2 (en) * 2012-04-05 2013-10-10 Telefonaktiebolaget L M Ericsson (Publ) Qci based offloading
US9432142B2 (en) * 2013-08-30 2016-08-30 Broadcom Corporation Pre-emption in passive optical networks
WO2019174006A1 (zh) * 2018-03-15 2019-09-19 华为技术有限公司 一种数据发送方法及装置
WO2021179325A1 (zh) * 2020-03-13 2021-09-16 华为技术有限公司 一种数据处理的方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105847355A (zh) * 2016-03-23 2016-08-10 重庆秒银科技有限公司 数据合并处理系统
CN107277940A (zh) * 2016-04-01 2017-10-20 宏达国际电子股份有限公司 处理无线资源控制连结恢复程序的装置及方法
US11071051B1 (en) * 2020-03-12 2021-07-20 Verizon Patent And Licensing, Inc. Systems and methods for SCEF-assisted MEC traffic breakout
CN113517957A (zh) * 2020-04-10 2021-10-19 华为技术有限公司 一种harq信息传输方法及装置

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN119254619A (zh) * 2024-09-18 2025-01-03 中国移动通信集团设计院有限公司 网络配置方法、系统、装置、设备、介质及产品
CN119254619B (zh) * 2024-09-18 2025-11-18 中国移动通信集团设计院有限公司 网络配置方法、系统、装置、设备、介质及产品

Also Published As

Publication number Publication date
CN116346294A (zh) 2023-06-27

Similar Documents

Publication Publication Date Title
CN114172852B (zh) 分布式宽带网络网关控制分组的优先级信道
CN109600768B (zh) 网络切片的管理方法、设备及系统
US9264972B2 (en) Home networking with integrated cellular communication
EP2727297B1 (en) Variable-based forwarding path construction for packet processing within a network device
US9860156B2 (en) Accessing local network resources in a multi-interface system
CN111586642B (zh) 一种通信方法及装置
WO2023116355A1 (zh) 通信方法、装置、相关设备及存储介质
EP4124104A1 (en) Communication method and apparatus
CN105591971B (zh) 一种QoS的实现方法和装置
CN111770545A (zh) 一种业务流路由控制方法、装置及系统
WO2019033920A1 (zh) 网络侧对远端用户设备的识别和控制方法以及设备
WO2021155759A1 (zh) 分段标识的处理方法及设备
CN118432976A (zh) 通过以太网传送非接入层消息
WO2021174943A1 (zh) 数据转发方法、装置、设备和存储介质
CN114205291B (zh) 数据包的传输方法及装置
US11212230B2 (en) Quality of service control method, device, and system
WO2015192705A1 (zh) 接入装置及其执行的将用户设备接入网络的方法
WO2024074095A1 (zh) 一种通信方法及装置
WO2025180331A1 (zh) 信息处理方法、装置、设备、存储介质及计算机程序产品
WO2022268166A1 (zh) 通信系统、方法、装置、第一设备及存储介质
WO2025214307A9 (zh) 一种通信方法及网络设备、存储介质、计算机程序产品
US20240276342A1 (en) System and Method for Establishing a Dual-Layer PDU Session
CN105591967A (zh) 一种数据传输方法和装置
WO2022160982A1 (zh) 一种IPv6地址的配置方法及路由设备
CN115529589A (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: 22909670

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22909670

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 22909670

Country of ref document: EP

Kind code of ref document: A1