WO2020232720A1 - 一种通信方法及装置、网络架构 - Google Patents

一种通信方法及装置、网络架构 Download PDF

Info

Publication number
WO2020232720A1
WO2020232720A1 PCT/CN2019/088197 CN2019088197W WO2020232720A1 WO 2020232720 A1 WO2020232720 A1 WO 2020232720A1 CN 2019088197 W CN2019088197 W CN 2019088197W WO 2020232720 A1 WO2020232720 A1 WO 2020232720A1
Authority
WO
WIPO (PCT)
Prior art keywords
cloud
access
nodes
interface
edge cloud
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/CN2019/088197
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.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp 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 Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority to EP19929371.3A priority Critical patent/EP3972219A4/en
Priority to PCT/CN2019/088197 priority patent/WO2020232720A1/zh
Priority to CN201980088399.4A priority patent/CN113273162B/zh
Publication of WO2020232720A1 publication Critical patent/WO2020232720A1/zh
Priority to US17/533,808 priority patent/US12001890B2/en
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
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • G06F9/5038—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering the execution order of a plurality of tasks, e.g. taking priority or time dependency constraints into consideration
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • G06F9/505—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering the load
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5061—Partitioning or combining of resources
    • G06F9/5072—Grid computing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management

Definitions

  • the embodiments of the present application relate to the field of mobile communication technology, and specifically relate to a communication method, device, and network architecture.
  • the network architecture Since the evolution of the network architecture, it is mainly composed of three parts: core network, access network, and terminal. Among them, the types of network nodes in the core network and the access network are relatively single. The current network architecture does not consider all possible networks for information transmission. The characteristics of the node.
  • the embodiments of the present application provide a communication method and device, and network architecture.
  • the communication method provided by the embodiment of the present application applies a network architecture, and the network architecture includes: an edge cloud, an access cloud, and a core cloud; the method includes:
  • the edge cloud is connected to the core cloud through the access cloud, the edge cloud includes a plurality of edge cloud nodes, the access cloud includes at least one access cloud node, and the core cloud includes at least one core cloud Nodes, at least two edge cloud nodes of the plurality of edge cloud nodes jointly provide business services for user terminals.
  • the user terminal communicates with each of the at least two edge cloud nodes based on a connectionless interface.
  • the network architecture provided by the embodiments of the present application includes: an edge cloud, an access cloud, and a core cloud; wherein the edge cloud is connected to the core cloud through the access cloud, and the edge cloud includes multiple edge cloud nodes,
  • the access cloud includes at least one access cloud node, the core cloud includes at least one core cloud node, and at least two edge cloud nodes of the plurality of edge cloud nodes jointly provide business services for user terminals.
  • the communication unit is configured to communicate with each edge cloud node of the at least two edge cloud nodes based on a connectionless interface.
  • the communication device provided in the embodiment of the present application includes a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program stored in the memory to execute the aforementioned communication method.
  • the chip provided in the embodiment of the present application is used to implement the aforementioned communication method.
  • the chip includes: a processor, configured to call and run a computer program from the memory, so that the device installed with the chip executes the aforementioned communication method.
  • the computer-readable storage medium provided by the embodiments of the present application is used to store a computer program, and the computer program enables a computer to execute the aforementioned communication method.
  • the computer program product provided by the embodiments of the present application includes computer program instructions, and the computer program instructions cause a computer to execute the aforementioned communication method.
  • the computer program provided in the embodiment of the present application when it runs on a computer, causes the computer to execute the above-mentioned communication method.
  • the technical solutions of the embodiments of this application propose a new type of network architecture, which takes into account the characteristics of all network nodes that may carry out information transmission.
  • the network architecture as a whole includes the edge cloud, access cloud and core cloud. Part, where the edge cloud is connected to the core cloud through the access cloud, the edge cloud includes multiple edge cloud nodes, the access cloud includes at least one access cloud node, the core cloud includes at least one core cloud node, and the edge cloud includes at least one core cloud node. At least two edge cloud nodes in the cloud nodes jointly provide business services for user terminals.
  • Figure 1 is an optional 3G network architecture diagram
  • Figure 2 is an optional 4G network architecture diagram
  • Figure 3 is an optional 5G network architecture diagram
  • Figure 4 is a schematic diagram of an access network network element provided by an embodiment of the application.
  • FIG. 5 is a schematic flowchart of a communication method applied to a network architecture proposed by an embodiment of the application
  • FIG. 6 is a schematic diagram of a network architecture proposed in an embodiment of this application.
  • FIG. 7 is a schematic diagram of a data flow in the network architecture proposed in an embodiment of the application.
  • FIG. 8 is a schematic diagram of an interface in a network architecture proposed in an embodiment of this application.
  • FIG. 9 is a schematic diagram of multi-node to multi-node communication according to an embodiment of the application.
  • FIG. 10 is a schematic diagram of a multi-node to multi-node protocol stack proposed by an embodiment of the application;
  • FIG. 11 is a schematic flowchart of a communication method based on a connectionless interface proposed in an embodiment of the application;
  • FIG. 12 is a schematic diagram of a communication scenario based on a connectionless interface proposed in an embodiment of the application.
  • FIG. 13 is a schematic diagram of resources proposed in an embodiment of the application.
  • FIG. 14 is a schematic diagram of a communication device provided by an embodiment of the application.
  • FIG. 15 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 16 is a schematic structural diagram of a chip of an embodiment of the present application.
  • the wireless communication network has gone through the development stage from 1G to 5G.
  • the overall network architecture can basically be divided into three layers, including core network, access network, and terminal. The layers are connected through fixed interfaces.
  • FIG. 1 is an optional 3G network architecture diagram.
  • the access network part of the 3G network is called UMTS Terrestrial Radio Access Network (UTRAN), UTRAN Including one or more radio network subsystems (Radio Network Subsystem, RNS).
  • the network elements in the core network include a mobile switching center (Mobile Switching Center, MSC), a service support node (Serving GPRS Support Node, SGSN), and a gateway support node (Gateway GPRS Support Node, GGSN).
  • the MSC is responsible for circuit domain services such as voice and SMS.
  • SGSN/GGSN is responsible for packet domain services such as data transmission.
  • the network elements in the RNS include a radio network controller (Radio Network Controller, RNC) and a Node B (Node B, NB). Each network element in the 3G network is connected through a fixed interface.
  • RNC Radio Network Controller
  • FIG. 2 is an optional 4G network architecture diagram.
  • the 4G network greatly simplifies the 3G network. For example, the circuit domain network architecture is removed and some network elements are merged (such as RNC and NB).
  • the access network part of the 4G network is called the evolved UMTS terrestrial radio access network (Evolved UMTS Terrestrial Radio Access Network, E-UTRAN).
  • the network elements in the CN include mobility management function (Mobility Management Entity, MME) network elements, Serving GateWay (S-GW), etc.
  • MME Mobility Management Entity
  • S-GW Serving GateWay
  • the network elements in E-UTRAN include evolved Node B (evolved Node B, eNB). Each network element in the 4G network is connected through a fixed interface.
  • Figure 3 is an optional 5G network architecture diagram.
  • the 5G network does not have much change in the access network, but the core network is due to vertical services.
  • the core network elements are further refined to form a new architecture.
  • the access network part of the 5G network is called Next Generation Radio Access Networking (NG-RAN), and the core network part of the 5G network is called 5G Core Networking (5GC).
  • the network elements in the 5GC include mobility management function (Mobility Management Function, AMF) network elements, user plane function (User plane Function, UPF) network elements, and so on.
  • the network elements in NG-RAN include gNB and ng-eNB. Each network element in the 5G network is connected through a fixed interface.
  • the network architecture has evolved from the traditional network architecture to the present, and it is mainly composed of three parts: the core network, the access network, and the terminal.
  • the terminal is connected to one or more access network elements of the same type; and the access network is respectively connected to one or more core network elements of the same type in the control plane and the user plane.
  • access nodes in addition to typical base stations as access network elements (also called access nodes), other types of access nodes will also be used to provide services to users, including mobile access Nodes and access nodes that cannot be moved.
  • the access nodes that can be moved include: satellites, aircraft, cars, mobile terminals, etc.; the access nodes that cannot be moved include: base stations, fixed terminals (such as routers, televisions, etc.), as shown in Figure 4.
  • the current network architecture does not take into account the characteristics of all possible information transmission nodes, including: coverage area, mobility, whether they always exist, etc., but simply connect some of them using existing technologies, such as satellites and base stations Uu/NG interface connection is adopted between them; Side Link (SL) connection is adopted between ordinary smart phones or smart phones and cars; Uu interface connection is adopted between smart phones/cars and base stations.
  • existing technologies such as satellites and base stations Uu/NG interface connection is adopted between them; Side Link (SL) connection is adopted between ordinary smart phones or smart phones and cars; Uu interface connection is adopted between smart phones/cars and base stations.
  • SL Side Link
  • Uu interface connection is adopted between smart phones/cars and base stations.
  • the technical solutions of the embodiments of the present application propose a new type of network architecture, which is a service-oriented network architecture, which can also be called a service-centric network architecture, or a service-oriented network (SERON, Service Oriented). Network), or called Service Oriented Architecture (SOA).
  • a service-oriented network architecture which can also be called a service-centric network architecture, or a service-oriented network (SERON, Service Oriented). Network), or called Service Oriented Architecture (SOA).
  • SOA Service Oriented Architecture
  • the network architecture includes: an edge cloud, an access cloud, and a core cloud; the edge cloud communicates with the core cloud through the access cloud Connected, the edge cloud includes multiple edge cloud nodes, the access cloud includes at least one access cloud node, and the core cloud includes at least one core cloud node; as shown in FIG. 5, the communication method includes the following process :
  • Step 501 At least two edge cloud nodes of the plurality of edge cloud nodes jointly provide business services for user terminals.
  • the network architecture in the embodiment of the present application includes edge cloud, access cloud, and core cloud, refer to FIG. 6.
  • the following describes the specific structures of edge cloud, access cloud, and core cloud.
  • the edge cloud includes a plurality of edge cloud nodes, the edge cloud node is an access node of a user terminal, and the edge cloud node is a mobile terminal or a fixed terminal.
  • the mobile terminal is, for example, an airplane, a train, a car, a mobile phone, etc.
  • the fixed terminal is, for example, a home fixed access point, a public fixed access point, and the like.
  • the types of multiple edge cloud nodes in the edge cloud may be the same or different.
  • the access cloud includes at least one access cloud node, the access cloud node is an access node of a user terminal and/or an edge cloud node, and the access cloud node is an access satellite or a base station.
  • the types of multiple access cloud nodes in the access cloud may be the same or different.
  • the core cloud includes at least one core cloud node, and the core cloud node is a core server.
  • the core server includes at least one of the following: a central processing unit, a memory, and a charging server.
  • the clouds in the aforementioned network architecture may also form a vertical cloud and a horizontal cloud, where 1) information is performed between at least two of the edge cloud, the access cloud, and the core cloud Sharing forms a vertical cloud. 2) Information sharing among different nodes in any one of the edge cloud, the access cloud, and the core cloud forms a horizontal cloud.
  • vertical clouds are relative to horizontal clouds.
  • horizontal cloud refers to the cloud formed through information sharing between different edge cloud nodes within the edge cloud, or between different access cloud nodes within the access cloud, or between different core cloud nodes within the core cloud.
  • the logical connection relationship is located inside the same cloud.
  • the logical connection relationship of the vertical cloud is from the core cloud to the access cloud, from the access cloud to the edge cloud, and then from the edge cloud to the terminal. Compared with the horizontal cloud, the logical connection relationship is just vertical.
  • at least two edge cloud nodes of multiple edge cloud nodes jointly provide services for the terminal. These at least two edge cloud nodes can be connected to different access cloud nodes or to the same access cloud node. When connected to different access cloud nodes, the different access cloud nodes can be connected to one core cloud or can be connected to different core clouds.
  • the network elements in the vertical cloud belong to vertical network elements
  • the network elements in the horizontal cloud belong to horizontal network elements
  • At least two edge cloud nodes of the plurality of edge cloud nodes jointly provide business services for user terminals, which may have the following implementation modes:
  • the at least two edge cloud nodes jointly provide business services for user terminals through information sharing; or,
  • the at least two edge cloud nodes provide business services for the user terminal through the access cloud or,
  • the at least two edge cloud nodes provide business services for user terminals through the access cloud and the core cloud.
  • the above solution can provide business services for user terminals through edge cloud, or jointly provide business services for user terminals through edge cloud and access cloud, or jointly provide business services for user terminals through edge cloud, access cloud and core cloud.
  • the technical solutions of the embodiments of the present application are not limited to this, and it is also possible to provide business services for user terminals through the access cloud, or provide business services for the user terminals through the access cloud and the core cloud.
  • the following examples illustrate the communication process of providing business services for user terminals.
  • the edge cloud in the following example refers to at least two edge cloud nodes in the edge cloud.
  • the edge cloud receives the business data sent by the user terminal, and processes the business data; the edge cloud sends the processing result to the user terminal.
  • the edge cloud receives the service data sent by the user terminal, and forwards the service data to the access cloud; the access cloud processes the service data, and sends the processing result to the edge cloud through ; The edge cloud forwards the processing result to the user terminal.
  • the edge cloud receives the service data sent by the user terminal, processes the first part of the service data, and forwards the second part of the service data to the access cloud;
  • the second part of the service data is processed, and the processing result of the second part is sent to the edge cloud;
  • the edge cloud forwards the processing results of the first part and the second part to the user terminal .
  • the edge cloud communication receives the service data sent by the user terminal, and forwards the service data to the access cloud; the access cloud forwards the service data to the core cloud; the core cloud responds to the The service data is processed, and the processing result is sent to the access cloud; the access cloud sends the processing result to the edge cloud; and the edge cloud forwards the processing result to the user terminal.
  • the edge cloud receives the service data sent by the user terminal, processes the first part of the service data, and forwards the second part of the service data to the access cloud;
  • the second part of the service data is forwarded to the core cloud;
  • the core cloud processes the second part of the service data, and sends the processing result of the second part to the access cloud;
  • the access cloud Sending the processing result of the second part to the edge cloud;
  • the edge cloud forwards the processing result of the first part and the second part to the user terminal.
  • the edge cloud receives the service data sent by the user terminal, and forwards the service data to the access cloud; the access cloud processes the first part of the service data and transfers the service data The second part of the business data is forwarded to the core cloud; the core cloud processes the second part of the business data, and sends the processing result of the second part to the access cloud; the access cloud sends the The processing results of the first part and the second part are sent to the edge cloud; the edge cloud communication forwards the processing results of the first part and the second part to the user terminal.
  • the access cloud receives the service data sent by the user terminal, and processes the service data; the access cloud sends the processing result to the user terminal.
  • the access cloud receives the service data sent by the user terminal, and forwards the service data to the core cloud; the core cloud processes the service data, and sends the processing result to the access cloud; The access cloud forwards the processing result to the user terminal.
  • the access cloud receives the service data sent by the user terminal, processes the first part of the service data, and forwards the second part of the service data to the core cloud; the core cloud The second part of the business data is processed, and the processing result of the second part is sent to the access cloud; the access cloud forwards the processing results of the first part and the second part to the user terminal.
  • Figure 7 shows the data flow in two directions.
  • the data flow from the user terminal to the core cloud is called Converged Data, and accordingly, the direction from the user terminal to the core cloud can be called the Converged Direction.
  • the data flow from the core cloud to the user terminal is called Distributed Data.
  • the direction from the core cloud to the user terminal can be called the distributed direction.
  • the network architecture can provide business services for user terminals in a cloud manner, and further, can provide business services for user terminals through horizontal clouds or vertical clouds.
  • a user terminal refers to a terminal serving a user or a terminal to which the user belongs.
  • the user terminal is, for example, a mobile phone, smart glasses, smart watch, etc.
  • the user terminal can be used as an edge cloud node, located in the edge cloud, or independent of the edge cloud.
  • the user terminal can terminate services in the edge cloud, access cloud, or core cloud, that is, the service may exist in some clouds or in all clouds.
  • business services can be provided for user terminals according to user or user terminal selection and business requirements to be processed.
  • the business service or the processing of business data in the above solution includes at least one of the following: business encoding and decoding, business rendering, business enhancement, and business storage.
  • edge cloud, access cloud, and core cloud are processing capabilities, stability, and availability (whether they can be serviced at any time), but the functions for business processing are basically the same. Therefore, after the service is completed on any layer of the cloud, it can be sent to the user terminal as long as the demand is met, thereby ensuring that the service has a consistent service experience no matter which layer is processed. Further, after the user terminal receives the data from the edge cloud and/or the access cloud, it can perform simple processing and present it to the user, or directly present it to the user.
  • edge cloud the coverage of fixed terminals (such as home fixed access nodes) is limited, and the topology of mobile terminals (such as cars, trains, or airplanes) changes relatively quickly. Therefore, the edge cloud is used to handle the small and scattered business needs of users.
  • the access cloud the base station or access satellite is relatively stable, but the transmission coverage and transmission capacity are limited, and the computing power of all nodes in the network cannot be used. Therefore, the access cloud handles the relatively concentrated business needs of users and provides access to the core cloud.
  • the core server can provide powerful computing and processing capabilities. Therefore, the core cloud handles the user's core business needs, but requires access through the access cloud.
  • the edge cloud There is a first interface between the edge cloud and the user terminal, and the first interface is a connection-based interface.
  • the first interface connects the user terminal and the edge cloud node in the edge cloud.
  • the user terminal can be used as a part of the edge cloud or the user terminal can be served by the edge cloud.
  • the above two have the following differences at the business level:
  • the user terminal is a part of the edge cloud, that is, in addition to its own initiation of the service, the user terminal will also process the service, including the processing of its own service or the service processing of other destination terminals. If the user terminal is processing services of other destination terminals, the user terminal also needs to forward the processing result to the destination terminal.
  • the user terminal is served by the edge cloud, that is, the user terminal itself has no processing capabilities, only information collection (Information Collection) and display (Display) capabilities. At this time, the user terminal needs to use at least one of the edge cloud, access cloud and core cloud 1. Perform business processing and present the processing results obtained to the user.
  • the edge cloud that is, the user terminal itself has no processing capabilities, only information collection (Information Collection) and display (Display) capabilities.
  • the user terminal needs to use at least one of the edge cloud, access cloud and core cloud 1. Perform business processing and present the processing results obtained to the user.
  • the first interface is designed as a connectionless interface.
  • the second interface is a connection-based interface.
  • the second interface connects the user terminal and the access cloud node in the access cloud.
  • the nodes connected to the cloud are relatively stable and have weak mobility. Therefore, the second interface can use a traditional connection-based interface, and the second interface needs to support corresponding mobility management to ensure business continuity.
  • the edge cloud There is a third interface between the edge cloud and the access cloud, and the third interface is a connection-based interface.
  • the third interface connects the edge cloud node and the access cloud node.
  • the service data of the user terminal forwarded by the edge cloud is carried between the edge cloud and the access cloud.
  • the nodes in the edge cloud change relatively dynamically and have strong mobility; the nodes in the access cloud are relatively stable and have weak mobility, so the third interface can use the traditional connection-based interface, and the third interface needs to support corresponding mobility To ensure business continuity.
  • the fourth interface is a connection-based interface.
  • the fourth interface connects the access cloud node and the core cloud node.
  • the fourth interface can use an interface design similar to the LTE S1 interface or the NR NG interface.
  • the fifth interface connects different edge cloud nodes. Since the nodes in the edge cloud have the feature of frequent movement, the fifth interface needs to have strong flexibility and be able to support flexible changes of the topology interface.
  • the fifth interface is designed as a connectionless interface.
  • the sixth interface is a connection-based interface.
  • the sixth interface is connected to different access cloud nodes.
  • the relative topology interfaces between different nodes in the access cloud are relatively static and can be maintained for a certain period of time. Therefore, the sixth interface can use an interface design similar to the LTE X2 interface or the NR Xn interface.
  • the first interface and the second fifth interface are connection-based interfaces
  • the connection-based interface means that the transmission resources corresponding to the interface are pre-configured or obtained through competition.
  • the transmission resource corresponding to the connected interface needs to be applied for (or requested). For example: Device 1 and Device 2 communicate based on a connectionless interface. Then, if there are pre-configured resources, Device 1 and Device 2 will use the pre-configured resources to communicate. If there are no pre-configured resources, Device 1 and Device 2 wait for pre-configured resources or compete for resources before communicating.
  • the above-mentioned interfaces in the embodiments of the present application can be divided into vertical type interfaces and horizontal type interfaces according to the interface direction, where 1) the first interface, the second interface, the third interface, and the fourth interface belong to A vertical type interface, where different interfaces in the vertical type interface have a controlling or controlled relationship.
  • the control or controlled relationship means that the upper node controls the establishment, modification, and deletion of the interface; and controls the service establishment, resource allocation, and error recovery of the lower node through the interface.
  • the fifth interface and the sixth interface are horizontal type interfaces, and the roles of nodes on both sides of the horizontal type interface are equal, and there is information interaction and information sharing, but there is no control or controlled relationship.
  • the interfaces of the network architecture are divided into vertical type interfaces and horizontal type interfaces. Different types of interfaces have different functions and meanings, thus forming a complete network architecture together with edge cloud, access cloud, and core cloud.
  • the interface between the user terminal and the access cloud or the edge cloud and the access cloud is similar to the Uu interface in LTE and NR.
  • the access cloud includes multiple access cloud nodes
  • the interface between the edge cloud and the access cloud supports communication between the multiple edge cloud nodes and multiple access cloud nodes. Referring to FIG. 9, multiple edge cloud nodes and multiple access clouds Many-to-many communication is supported between nodes.
  • the communication between the multiple edge cloud nodes and the multiple access cloud nodes includes at least one of the following:
  • One or at least two edge cloud nodes of the plurality of edge cloud nodes are connected to an access cloud node;
  • One or at least two of the multiple access cloud nodes are connected to one edge cloud node.
  • the communication between the multiple edge cloud nodes and the multiple access cloud nodes includes at least one of the following:
  • Multi-node to multi-node communication in the decentralized direction
  • Multi-node to multi-node communication in the convergence direction Multi-node to multi-node communication in the convergence direction.
  • the access cloud and the user terminal have a target protocol layer, and the target protocol layer is located between the application layer and the access cloud.
  • the target protocol layer on the access cloud side is used to aggregate business data from the at least two access cloud nodes Processing, or decentralized processing of the service data to be sent to the at least two access cloud nodes;
  • the target protocol layer on the user terminal side is used to decentralize the service data to be sent to the at least two edge cloud nodes Or, perform aggregation processing on the service data from the at least two edge cloud nodes.
  • the user terminal communicates with two edge cloud nodes (such as node 1 and node 2) and one access cloud node (such as node A and node B).
  • the target protocol layer on the user terminal side disperses the service data to be sent to node 1 and node 2 into data stream 1 and data stream 2, where data stream 1 is sent to node 1, and data stream 2 is sent to node 2.
  • Node 1 can forward data stream 1 to node A, or it can copy two copies of data stream 1 to node A and node B.
  • node 2 can forward data stream 2 to node B, or copy data stream 2 Two copies are sent to node A and node B respectively.
  • the target protocol layer on the access cloud side converges all the data streams of node A and node B.
  • the target protocol layer on the access cloud side disperses the service data to be sent to node A and node B into data stream 1 and data stream 2, where data stream 1 is sent to node A, and data stream 2 is sent to node B.
  • Node A can forward data stream 1 to node 1, or can copy two copies of data stream 1 to node 1 and node 2 respectively.
  • node B can forward data stream 2 to node 2, or copy data stream 2 Two copies are sent to node 1 and node 2.
  • the target protocol layer on the user terminal side converges all data streams from node 1 and node 2.
  • the above target protocol layer is at the access cloud level (across different access cloud nodes) or even at the cross cloud level (cross access cloud and edge cloud), so as to jointly provide services for a certain user terminal.
  • the protocol stack is shown in Figure 10.
  • the target protocol layer has the following characteristics: 1) Guarantee the quality of service (QoS) of data packets, data packet counting, recovery, encryption and decryption, and retransmission functions. 2)
  • the target protocol layer can take a certain access cloud node as the main body, that is, the logical function of the target protocol layer is placed in a certain access cloud node. 3)
  • the target protocol layer can not only span different access points within the access cloud, but also span different nodes between the access cloud and the edge cloud.
  • connection-based interface can be used for data Interactive.
  • the following describes the communication process supported by the connectionless interface with reference to FIG. 11.
  • FIG. 11 is a schematic flowchart of a communication method based on a connectionless interface proposed in an embodiment of the application. As shown in FIG. 11, the communication method includes the following processes:
  • Step 1101 The user terminal communicates with each of the at least two edge cloud nodes based on a connectionless interface.
  • the communication process based on the connectionless interface includes the following steps:
  • the user terminal receives a broadcast message sent by each of the at least two edge cloud nodes, where the broadcast message includes system information, and the system information includes at least one of the following: link bandwidth, transmission resource Configuration information, business information carried by current resources, processing capabilities of edge cloud nodes, coverage of edge cloud nodes, and movement information of edge cloud nodes.
  • the user terminal may receive broadcast messages sent by one or more edge cloud nodes.
  • the user terminal receives broadcast messages sent by three edge cloud nodes.
  • the broadcast message includes the system information of the corresponding edge cloud node.
  • the system information includes at least one of the following: link bandwidth, transmission resource configuration information, edge cloud node processing capability, edge cloud node coverage, edge cloud node Mobile information.
  • the broadcast message also includes synchronization information, and the synchronization information is synchronization information in a dispersion direction.
  • the transmission resource configuration information includes at least one of the following: time resource information, frequency resource information, time resource determination method, frequency resource determination method, available time, and service preemption priority.
  • the available time refers to the length of time that the transmission resource can occupy, and the available time can be several cycles or an absolute length of time.
  • the service preemption priority is used to indicate which services can be preempted first when resources are preempted, so as to ensure that the service can still preempt the resources even when the resources have been used.
  • the above-mentioned transmission resource configuration information further includes transmission resource configuration information corresponding to the sent data and transmission resource configuration information corresponding to the received data.
  • the user terminal can determine the first target resource corresponding to the sent data and/or the second target resource corresponding to the received data through the foregoing transmission resource configuration information.
  • This transmission resource configuration method realizes that the network side allocates transmission resources in advance to the user terminal. When the user terminal sends and/or receives data, it does not need to apply for resources, and can directly send and/or receive data on the pre-allocated transmission resources. .
  • the user terminal determines corresponding frequency resource information based on the time resource information.
  • the time resource determination method includes the following time resource determination method corresponding to the sent data:
  • the user terminal For the target time unit, if the target time unit is not occupied for multiple consecutive cycles, the user terminal occupies the target time unit in a competitive manner to send data. Or, for the target time unit, the user terminal occupies the target time unit in a competitive manner for data transmission.
  • the target time unit is the nth frame or the ath time slot in the nth frame. If the target time unit for m consecutive cycles is empty (that is, not occupied), the user terminal can pass Data transmission in a competitive way.
  • m is an integer greater than or equal to zero.
  • the time resource determination method includes the following time resource determination method corresponding to the received data:
  • the user terminal determines that it needs to receive data on all time units; or,
  • the user terminal determines the target time unit that needs to receive data according to the terminal identifier; or,
  • the user terminal determines the target time unit that needs to receive data according to the time unit occupied by sending data.
  • the time unit may be a symbol, or a time slot, or a subframe.
  • the pre-allocated transmission resource (that is, the aforementioned first target resource and/or the second target resource) may be a specific resource or a group of resources (such as a resource pool).
  • the user terminal sends data on a preset first target resource and/or receives data on a second target resource based on the transmission resource configuration information.
  • the first target resource and the second target resource have a corresponding relationship.
  • the data sent by the user terminal on the first target resource carries a first identification number, and the first identification number is used to identify the first target resource.
  • the edge cloud node After receiving the data sent by the user terminal, the edge cloud node will An identification number can determine the first target resource, and feed back data to the user terminal on the second target resource corresponding to the first target resource, so that the user terminal displays data on the second target resource corresponding to the first target resource. Receive data on.
  • the time corresponding to label 2 is the time that cannot be sent and received
  • the time corresponding to labels 3 and 5 is the time that can be sent
  • the time corresponding to labels 4 and 6 is the time that can be received
  • the edge cloud node passes The broadcast message gives the corresponding transmission resource configuration, and the user terminal only needs to send and/or receive data at the corresponding time according to the instructions.
  • the edge cloud node can also associate the times marked 3 and 4, and associate the times marked 5 and 6. If the user terminal sends data at the time marked 3, it will be marked as Data is received at the time corresponding to 4; if the user terminal sends data at the time corresponding to the label 5, it will receive the data at the time corresponding to the label 6.
  • the time corresponding to each label may include one or more time slots. The length of time corresponding to each label can be the same or different.
  • Fig. 6 is a schematic diagram of a network architecture provided by an embodiment of the application.
  • the network architecture includes: an edge cloud 601, an access cloud 602, and a core cloud 603; wherein the edge cloud 601 passes through the connection
  • the access cloud 602 is connected to the core cloud 603, the edge cloud 601 includes a plurality of edge cloud nodes, the access cloud 602 includes at least one access cloud node, and the core cloud 603 includes at least one core cloud node.
  • At least two edge cloud nodes among the multiple edge cloud nodes jointly provide business services for user terminals.
  • the edge cloud node is an access node of a user terminal, and the edge cloud node is a mobile terminal or a fixed terminal.
  • the access cloud node is an access node of the user terminal and/or the edge cloud node, and the access cloud node is an access satellite or a base station.
  • the core cloud node is a core server.
  • At least two of the edge cloud 601, the access cloud 602, and the core cloud 603 perform information sharing to form a vertical cloud.
  • information sharing among different nodes in any one of the edge cloud 601, the access cloud 602, and the core cloud 603 forms a horizontal cloud.
  • the at least two edge cloud nodes jointly provide business services for user terminals through information sharing; or, the at least two edge cloud nodes provide service for user terminals through the access cloud 602 Business services; or, the at least two edge cloud nodes provide business services for user terminals through the access cloud 602 and the core cloud 603.
  • the first interface, the second interface, the third interface, and the fourth interface are vertical type interfaces.
  • the interface between the edge cloud 601 and the access cloud 602 supports the multiple edge cloud nodes Communication with multiple access cloud nodes.
  • the communication between the multiple edge cloud nodes and the multiple access cloud nodes includes at least one of the following:
  • One or at least two edge cloud nodes of the plurality of edge cloud nodes are connected to an access cloud node;
  • One or at least two of the multiple access cloud nodes are connected to one edge cloud node.
  • the access cloud 602 and the user terminal have a target protocol layer, and the target protocol layer is located between the application layer and the access layer;
  • the target protocol layer on the access cloud 602 side is used to aggregate the service data from the at least two access cloud nodes, or to be sent to Decentralized processing of the service data of the at least two access cloud nodes;
  • the target protocol layer on the user terminal side is used to perform distributed processing on the service data to be sent to the at least two edge cloud nodes, or perform aggregation processing on the service data from the at least two edge cloud nodes.
  • FIG. 14 is a schematic diagram of a communication device provided by an embodiment of the application. As shown in FIG. 14, the communication device includes:
  • the communication unit 1401 is configured to communicate with each edge cloud node of at least two edge cloud nodes based on a connectionless interface.
  • the communication unit 1401 is configured to receive a broadcast message sent by each edge cloud node of the at least two edge cloud nodes, where the broadcast message includes system information, and the system The information includes at least one of the following: link bandwidth, transmission resource configuration information, service information carried by current resources, processing capabilities of edge cloud nodes, coverage of edge cloud nodes, and movement information of edge cloud nodes; based on the transmission resource configuration Information, sending data on the preset first target resource and/or receiving data on the second target resource.
  • the transmission resource configuration information includes at least one of the following: time resource information, frequency resource information, time resource determination method, frequency resource determination method, available time, and service preemption priority.
  • the communication unit 1401 determines corresponding frequency resource information based on the time resource information.
  • the time resource determination method includes the following time resource determination method corresponding to the sent data:
  • the communication unit 1401 occupies the target time unit in a competitive manner for data transmission.
  • the time resource determination method includes the following time resource determination method corresponding to the received data:
  • the communication unit 1401 determines that it needs to receive data in all time units; or,
  • the communication unit 1401 determines the target time unit that needs to receive data according to the terminal identifier; or,
  • the communication unit 1401 determines the target time unit that needs to receive data according to the time unit occupied by sending data.
  • the first target resource and the second target resource have a corresponding relationship;
  • the communication unit 1401 carries a first identification number in the data sent on the first target resource, and The first identification number is used to identify the first target resource;
  • the communication unit 1401 receives data on a second target resource corresponding to the first target resource.
  • the broadcast message further includes synchronization information.
  • FIG. 15 is a schematic structural diagram of a communication device 1500 according to an embodiment of the present application.
  • the communication device may be a terminal or a network device.
  • the communication device 1500 shown in FIG. 15 includes a processor 1510.
  • the processor 1510 can call and run a computer program from a memory to implement the method in the embodiment of the present application.
  • the communication device 1500 may further include a memory 1520.
  • the processor 1510 may call and run a computer program from the memory 1520 to implement the method in the embodiment of the present application.
  • the memory 1520 may be a separate device independent of the processor 1510, or may be integrated in the processor 1510.
  • the communication device 1500 may further include a transceiver 1530, and the processor 1510 may control the transceiver 1530 to communicate with other devices, specifically, it may send information or data to other devices, or receive other devices. Information or data sent by the device.
  • the transceiver 1530 may include a transmitter and a receiver.
  • the transceiver 1530 may further include an antenna, and the number of antennas may be one or more.
  • the communication device 1500 may specifically be a network device of an embodiment of the application, and the communication device 1500 may implement the corresponding process implemented by the network device in each method of the embodiment of the application. For brevity, details are not repeated here. .
  • the communication device 1500 may specifically be a mobile terminal/terminal device of an embodiment of the present application, and the communication device 1500 may implement the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application. For simplicity , I won’t repeat it here.
  • FIG. 16 is a schematic structural diagram of a chip of an embodiment of the present application.
  • the chip 1600 shown in FIG. 16 includes a processor 1610, and the processor 1610 can call and run a computer program from the memory to implement the method in the embodiment of the present application.
  • the chip 1600 may further include a memory 1620.
  • the processor 1610 may call and run a computer program from the memory 1620 to implement the method in the embodiment of the present application.
  • the memory 1620 may be a separate device independent of the processor 1610, or may be integrated in the processor 1610.
  • the chip 1600 may further include an input interface 1630.
  • the processor 1610 can control the input interface 1630 to communicate with other devices or chips, and specifically, can obtain information or data sent by other devices or chips.
  • the chip 1600 may further include an output interface 1640.
  • the processor 1610 can control the output interface 1640 to communicate with other devices or chips, specifically, can output information or data to other devices or chips.
  • the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding process implemented by the network device in the various methods of the embodiment of the present application.
  • the chip can implement the corresponding process implemented by the network device in the various methods of the embodiment of the present application.
  • the chip can be applied to the mobile terminal/terminal device in the embodiment of the present application, and the chip can implement the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application.
  • the chip can implement the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application.
  • the chip can implement the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application.
  • the chip can be applied to the mobile terminal/terminal device in the embodiment of the present application, and the chip can implement the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application.
  • the chip can be applied to the mobile terminal/terminal device in the embodiment of the present application, and the chip can implement the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application.
  • the chip can implement the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application.
  • the chip mentioned in the embodiment of the present application may also be referred to as a system-level chip, a system-on-chip, a system-on-chip, or a system-on-chip.
  • the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capability.
  • the steps of the foregoing method embodiments can be completed by hardware integrated logic circuits in the processor or instructions in the form of software.
  • the above-mentioned processor can be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a ready-made programmable gate array (Field Programmable Gate Array, FPGA) or other Programming logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA ready-made programmable gate array
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), and electrically available Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be a random access memory (Random Access Memory, RAM), which is used as an external cache.
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM DDR SDRAM
  • ESDRAM enhanced synchronous dynamic random access memory
  • Synchlink DRAM SLDRAM
  • DR RAM Direct Rambus RAM
  • the memory in the embodiment of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiment of the present application is intended to include but not limited to these and any other suitable types of memory.
  • the embodiment of the present application also provides a computer-readable storage medium for storing computer programs.
  • the computer-readable storage medium may be applied to the network device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer-readable storage medium can be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application ,
  • the computer program enables the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application ,
  • I will not repeat it here.
  • the embodiments of the present application also provide a computer program product, including computer program instructions.
  • the computer program product may be applied to the network device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer program product can be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application, For brevity, I won't repeat them here.
  • the embodiment of the present application also provides a computer program.
  • the computer program can be applied to the network device in the embodiment of the present application.
  • the computer program runs on the computer, the computer is caused to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • I won’t repeat it here.
  • the computer program can be applied to the mobile terminal/terminal device in the embodiment of the present application.
  • the computer program runs on the computer, the computer executes each method in the embodiment of the present application. For the sake of brevity, the corresponding process will not be repeated here.
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • each unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of this application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the method described in each embodiment of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory,) ROM, random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code .

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mathematical Physics (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例提供一种通信方法及装置、网络架构，所述网络架构包括：边缘云、接入云以及核心云；所述方法包括：所述边缘云通过所述接入云与所述核心云连接，所述边缘云包括多个边缘云节点，所述接入云包括至少一个接入云节点，所述核心云包括至少一个核心云节点，所述多个边缘云节点中的至少两个边缘云节点共同为用户终端提供业务服务。

Description

一种通信方法及装置、网络架构 技术领域
本申请实施例涉及移动通信技术领域，具体涉及一种通信方法及装置、网络架构。
背景技术
网络架构演进至今，主要由核心网、接入网、终端三部分组成，其中，核心网和接入网中的网络节点的类型较为单一，当前网络架构并未统筹考虑所有可能进行信息传输的网络节点的特性。
发明内容
本申请实施例提供一种通信方法及装置、网络架构。
本申请实施例提供的通信方法，应用网络架构，所述网络架构包括：边缘云、接入云以及核心云；所述方法包括：
所述边缘云通过所述接入云与所述核心云连接，所述边缘云包括多个边缘云节点，所述接入云包括至少一个接入云节点，所述核心云包括至少一个核心云节点，所述多个边缘云节点中的至少两个边缘云节点共同为用户终端提供业务服务。
本申请实施例提供的通信方法，包括：
用户终端基于无连接的接口与至少两个边缘云节点中的每个边缘云节点进行通信。
本申请实施例提供的网络架构包括：边缘云、接入云以及核心云；其中，所述边缘云通过所述接入云与所述核心云连接，所述边缘云包括多个边缘云节点，所述接入云包括至少一个接入云节点，所述核心云包括至少一个核心云节点，所述多个边缘云节点中的至少两个边缘云节点共同为用户终端提供业务服务。
本申请实施例提供的通信装置包括：
通信单元，用于基于无连接的接口与至少两个边缘云节点中的每个边缘云节点进行通信。
本申请实施例提供的通信设备，包括处理器和存储器。该存储器用于存储计算机程序，该处理器用于调用并运行该存储器中存储的计算机程序，执行上述的通信方法。
本申请实施例提供的芯片，用于实现上述的通信方法。
具体地，该芯片包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有该芯片的设备执行上述的通信方法。
本申请实施例提供的计算机可读存储介质，用于存储计算机程序，该计算机程序使得计算机执行上述的通信方法。
本申请实施例提供的计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行上述的通信方法。
本申请实施例提供的计算机程序，当其在计算机上运行时，使得计算机执行上述的通信方法。
本申请实施例的技术方案，提出了一种新型的网络架构，该网络架构统筹考虑了所有可能进行信息传输的网络节点的特性，网络架构从整体上包括边缘云、接入云和核心云三部分，其中，边缘云通过接入云与核心云连接，边缘云包括多个边缘云节点，接入云包括至少一个接入云节点，核心云包括至少一个核心云节点，通过所述多个边缘云节点中的至少两个边缘云节点共同为用户终端提供业务服务。
附图说明
此处所说明的附图用来提供对本申请的进一步理解，构成本申请的一部分，本申请的示意性实施例及其说明用于解释本申请，并不构成对本申请的不当限定。在附图中：
图1为一种可选的3G网络架构图；
图2为一种可选的4G网络架构图；
图3为一种可选的5G网络架构图；
图4为本申请实施例提供的接入网网元的示意图；
图5为本申请实施例提出的应用于网络架构的通信方法的流程示意图；
图6为本申请实施例提出的网络架构的示意图；
图7为本申请实施例提出的网络架构中的数据流的示意图；
图8为本申请实施例提出的网络架构中的接口的示意图；
图9为本申请实施例提出的多节点对多节点的通信示意图；
图10为本申请实施例提出的多节点对多节点的协议栈示意图；
图11为本申请实施例提出的基于无连接的接口的通信方法的流程示意图；
图12为本申请实施例提出的基于无连接的接口的通信场景示意图；
图13为本申请实施例提出的资源示意图；
图14为本申请实施例提供的通信装置的示意图；
图15是本申请实施例提供的一种通信设备示意性结构图；
图16是本申请实施例的芯片的示意性结构图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
无线通信网络经历了从1G到5G的发展阶段。在无线通信网络发展过程中，整体网络架构基本可以分为三层，包括核心网、接入网与终端三个层次，层与层之间通过固定接口进行连接。
在3G网络中，如图1所示，图1为一种可选的3G网络架构图，3G网络中的接入网部分叫做UMTS陆地无线接入网(UMTS Terrestrial Radio Access Network，UTRAN)，UTRAN包括一个或多个无线网络子系统(Radio Network Subsystem，RNS)。其中，核心网(Core Network，CN)中的网元包括移动交换中心(Mobile Switching Center，MSC)、服务支持节点(Serving GPRS Support Node，SGSN)、网关支持节点(Gateway GPRS Support Node，GGSN)。MSC负责语音、短信等电路域业务。SGSN/GGSN负责数据传输等分组域业务。RNS中的网元包括无线网络控制器(Radio Network Controller，RNC)和节点B(Node B，NB)。3G网络中的各个网元之间通过固定接口连接。
在4G网络中，如图2所示，图2为一种可选的4G网络架构图，4G网络对3G网 络进行了极大的简化，例如去掉了电路域网络架构，合并了部分网元(如RNC和NB)。4G网络中的接入网部分叫做演进的UMTS陆地无线接入网(Evolved UMTS Terrestrial Radio Access Network，E-UTRAN)。其中，CN中的网元包括移动管理功能(Mobility Management Entity，MME)网元、服务网关(Serving GateWay，S-GW)等。E-UTRAN中的网元包括演进的节点B(evolved Node B，eNB)。4G网络中的各个网元之间通过固定接口连接。
在5G网络中，如图3所示，图3为一种可选的5G网络架构图，5G网络相比4G网络在接入网方面并未有太大变化，但是在核心网方面由于垂直业务和虚拟化的需要，将核心网网元进行了进一步细化，从而形成了新的架构。5G网络中的接入网部分叫做下一代无线接入网(Next Generation Radio Access Networking，NG-RAN)，5G网络中的核心网部分叫做5G核心网(5G Core Networking，5GC)。其中，5GC中的网元包括移动管理功能(Mobility Management Function，AMF)网元、用户平面功能(User plane Function，UPF)网元等。NG-RAN中的网元包括gNB和ng-eNB。5G网络中的各个网元之间通过固定接口连接。
从图1到图3可以看出，网络架构从传统网络架构演进至今，主要由核心网、接入网、终端三部分组成。其中终端对接某一个或者多个相同类型的接入网网元；而接入网在控制面与用户面分别对接一个或者多个相同类型的核心网网元。
然而在未来无线网络中，除了典型的基站作为接入网网元(也称为接入节点)之外，其他类型的接入节点也会被应用起来为用户提供服务，包括可以移动的接入节点和无法移动的接入节点。其中，可以移动的接入节点包括：卫星、飞行器、汽车、移动终端等；不能移动的接入节点包括：基站、固定终端(如路由器、电视机等)，如图4所示。
当前网络架构并未统筹考虑所有可能进行信息传输的节点的特性，包括：覆盖区域、移动性、是否总是存在等，只是简单的将其中的一些节点采用现有技术联系起来，例如卫星与基站之间采用Uu/NG接口连接；普通智能手机之间或者智能手机与车之间采用侧行链路(Side Link，SL)连接；智能手机/车与基站之间采用Uu接口连接。但是有很多问题仍然未能明确，例如融合多种类型网络节点的网络架构目前尚未定义。再例如不同类型网络节点之间如何连接以及如何进行通信尚未定义。为此提出了本申请实施例的以下技术方案。
本申请实施例的技术方案提出了一种新型的网络架构，该网络架构为面向服务的网络架构，也可以称为以业务为中心的网络架构，或者称为面向服务的网络(SERON，Service Oriented Network)，或者称为面向服务的架构(Service Oriented Architecture，SOA)。同时，本申请实施例给出了该网络架构中不同节点之间连接的接口以及通信方式。
图5为本申请实施例提出的应用于网络架构的通信方法的流程示意图，该网络架构包括：边缘云、接入云以及核心云；所述边缘云通过所述接入云与所述核心云连接，所述边缘云包括多个边缘云节点，所述接入云包括至少一个接入云节点，所述核心云包括至少一个核心云节点；如图5所示，所述通信方法包括以下流程：
步骤501：所述多个边缘云节点中的至少两个边缘云节点共同为用户终端提供业务服务。
本申请实施例中的网络架构包括边缘云、接入云以及核心云，参照图6。以下对边缘云、接入云以及核心云的具体结构进行说明。
Figure PCTCN2019088197-appb-000001
边缘云
所述边缘云包括多个边缘云节点，所述边缘云节点为用户终端的接入节点，所述边缘云节点为移动终端或固定终端。
在本申请一些可选实施方式中，移动终端例如是飞机、火车、汽车、手机等。
在本申请一些可选实施方式中，固定终端例如是家庭固定接入点、公共场合固定接入点等。
本申请实施例中，边缘云内的多个边缘云节点的类型可以相同，也可以不同。
Figure PCTCN2019088197-appb-000002
接入云
所述接入云包括至少一个接入云节点，所述接入云节点为用户终端和/或边缘云节点的接入节点，所述接入云节点为接入卫星或基站。
本申请实施例中，接入云内的多个接入云节点的类型可以相同，也可以不同。
Figure PCTCN2019088197-appb-000003
核心云
所述核心云包括至少一个核心云节点，所述核心云节点为核心服务器。
在本申请一些可选实施方式中，所述核心服务器包括以下至少之一：中央处理器、存储器、计费服务器。
本申请实施例中，上述网络架构中的云还可以形成垂直云和水平云，其中，1)所述边缘云、所述接入云和所述核心云中的至少两个云之间进行信息共享形成垂直云。2)所述边缘云、所述接入云和所述核心云中的任意一个云内部不同节点间进行信息共享形成水平云。
这里，垂直云是相对水平云来说的。其中，水平云是指边缘云内部不同边缘云节点之间，或接入云内部不同接入云节点之间，或核心云内部不同核心云节点之间通过信息共享形成的云，可见，水平云的逻辑连接关系是位于同一个云的内部。而垂直云的逻辑连接关系是从核心云到接入云，从接入云到边缘云，进而再从边缘云到终端，其逻辑连接关系相比水平云来说刚好垂直的。在垂直云中，多个边缘云节点中的至少两个边缘云节点共同为终端提供服务，这至少两个边缘云节点可以连接到不同的接入云节点，也可以连接到同一个接入云节点。当连接到不同的接入云节点时，所述不同的接入云节点可以连接到一个核心云，也可以连接到不同的核心云。
这里，垂直云中的网元属于垂直网元，水平云中的网元属于水平网元。
本申请实施例中，所述多个边缘云节点中的至少两个边缘云节点共同为用户终端提供业务服务，可以具有以下实现方式：
Figure PCTCN2019088197-appb-000004
所述至少两个边缘云节点通过信息共享共同为用户终端提供业务服务；或者，
Figure PCTCN2019088197-appb-000005
所述至少两个边缘云节点通过所述接入云为用户终端提供业务服务或者，
Figure PCTCN2019088197-appb-000006
所述至少两个边缘云节点通过所述接入云和所述核心云为用户终端提供业务服务。
上述方案可以实现通过边缘云为用户终端提供业务服务，或者通过边缘云和接入云共同为用户终端提供业务服务，或者通过边缘云、接入云和核心云共同为用户终端提供业务服务。本申请实施例的技术方案不局限于此，还可以通过接入云为用户终端提供业务服务，或者通过接入云和核心云为用户终端提供业务服务。以下举例说明为用户终端提供业务服务的通信流程，需要说明的是，以下例子中的边缘云是指边缘云中的至少两个边缘云节点。
举个例子：所述边缘云接收用户终端发送的业务数据，对所述业务数据进行处理；所述边缘云将处理结果发送给所述用户终端。
举个例子：所述边缘云接收用户终端发送的业务数据，将所述业务数据转发给接入云；所述接入云对所述业务数据进行处理，将处理结果通过发送给所述边缘云；所述边缘云将所述处理结果转发给所述用户终端。
举个例子：所述边缘云接收用户终端发送的业务数据，对所述业务数据的第一部分进行处理，并将所述业务数据的第二部分转发给接入云；所述接入云对所述业务 数据的第二部分进行处理，将所述第二部分的处理结果发送给所述边缘云；所述边缘云将所述第一部分和所述第二部分的处理结果转发给所述用户终端。
举个例子：所述边缘云通接收用户终端发送的业务数据，将所述业务数据转发给接入云；所述接入云将所述业务数据转发给核心云；所述核心云对所述业务数据进行处理，将处理结果发送给所述接入云；所述接入云将所述处理结果发送给所述边缘云；所述边缘云将所述处理结果转发给所述用户终端。
举个例子：所述边缘云接收用户终端发送的业务数据，对所述业务数据的第一部分进行处理，并将所述业务数据的第二部分转发给接入云；所述接入云将所述业务数据的第二部分转发给核心云；所述核心云对所述业务数据的第二部分进行处理，将所述第二部分的处理结果发送给所述接入云；所述接入云将所述第二部分的处理结果发送给所述边缘云；所述边缘云将所述第一部分和所述第二部分的处理结果转发给所述用户终端。
举个例子：所述边缘云接收用户终端发送的业务数据，通过将所述业务数据转发给接入云；所述接入云对所述业务数据的第一部分进行处理，并将所述业务数据的第二部分转发给核心云；所述核心云对所述业务数据的第二部分进行处理，将所述第二部分的处理结果发送给所述接入云；所述接入云将所述第一部分和所述第二部分的处理结果发送给所述边缘云；所述边缘云通将所述第一部分和所述第二部分的处理结果转发给所述用户终端。
举个例子：所述接入云接收用户终端发送的业务数据，对所述业务数据进行处理；所述接入云将处理结果发送给所述用户终端。
举个例子：所述接入云接收用户终端发送的业务数据，将所述业务数据转发给核心云；所述核心云对所述业务数据进行处理，将处理结果发送给所述接入云；所述接入云将所述处理结果转发给所述用户终端。
举个例子：所述接入云接收用户终端发送的业务数据，对所述业务数据的第一部分进行处理，并将所述业务数据的第二部分转发给核心云；所述核心云对所述业务数据的第二部分进行处理，将所述第二部分的处理结果发送给所述接入云；所述接入云将所述第一部分和所述第二部分的处理结果转发给所述用户终端。
上述例子中的通信流程可以参照图7，图7给出了两个方向的数据流。其中，1)用户终端到核心云方向的数据流称为汇聚数据流(Converged Data)，相应地，可以将用户终端到核心云的方向称为汇聚方向。2)核心云到用户终端方向的数据流称为分散数据流(Distributed Data)，相应地，可以将核心云到用户终端的方向称为分散方向。
本申请实施例的技术方案，网络架构能够按照云的方式为用户终端提供业务服务，进一步，可以通过水平云或垂直云为用户终端提供业务服务。
本申请实施例中，用户终端是指服务用户的终端或者用户所属的终端。在本申请一些可选实施方式中，用户终端例如是手机、智能眼镜、智能手表等。
需要说明的是，用户终端可以作为边缘云节点，位于边缘云内，也可以独立于边缘云之外。
本申请实施例中，用户终端在边缘云、接入云或者核心云均可以终结业务，即业务可以存在于部分云中，也可以存在于所有云中。具体应用时，可以按照用户或者用户终端选择以及需要处理的业务需求，为用户终端提供业务服务。
上述方案中的业务服务或者对业务数据进行的处理，包括以下至少之一：业务的编译码、业务的渲染、业务的增强、业务的存储。需要说明的是，边缘云、接入云以及核心云主要的不同在于处理能力、稳定性以及可获得性(是否随时可以服务)，但是对于 业务处理的功能上基本相同。因此，业务在任何一层云上完成后，只要满足需求就可以发送至用户终端，从而保证业务无论经过哪一层的处理，都有一致的业务体验。进一步，用户终端接收来自于边缘云和/或接入云的数据后，可以进行简单的处理呈现给用户，也可以直接呈现给用户。
以下举例说明边缘云、接入云以及核心云的区别。在边缘云中，固定终端(如家庭固定接入节点)覆盖有限，移动终端(如汽车、火车或者飞机)拓扑变化相对较快，因此，采用边缘云处理用户较小且零散的业务需求。在接入云中，基站或者接入卫星相对稳定，但是传输覆盖和传输容量有限，无法发挥网络中所有节点的计算能力，因此，接入云处理用户较为集中的业务需求且为核心云提供接入能力。在核心云中，核心服务器可以提供强大的计算和处理能力，因此，核心云处理用户核心业务需求，但是需要通过接入云的接入。
本申请实施例中，参照图8，上述网络架构需要支持以下接口：
Figure PCTCN2019088197-appb-000007
所述边缘云与所述用户终端之间具有第一接口，所述第一接口为基于无连接的接口。
这里，第一接口连接了用户终端与边缘云中的边缘云节点。
需要说明的是，用户终端可以作为边缘云的一部分或者用户终端被边缘云服务，以上两者在业务层面存在如下区别：
I：用户终端作为边缘云的一部分，即用户终端除了自身发起业务之外，也会对于业务进行处理，包括针对自身业务的处理或者其他目的终端的业务处理。如果用户终端是处理其他目的终端的业务，则用户终端还需要将处理结果转发给目的终端。
II：用户终端被边缘云服务，即用户终端本身没有处理能力，只有信息收集(Information Collection)和显示(Display)能力，此时用户终端需要借助边缘云、接入云和核心云中的至少之一进行业务处理，并将获得的处理结果呈现给用户。
以上两种情况从接口来讲并无区别，均可以传输高速数据。此外，由于边缘云中的节点具有频繁移动的特点，因此第一接口需要具有较强的灵活性，能够支持拓扑接口的灵活变化，本申请实施例将第一接口设计为基于无连接的接口。
Figure PCTCN2019088197-appb-000008
所述接入云与用户终端之间具有第二接口，所述第二接口为基于连接的接口。
这里，第二接口连接了用户终端与接入云中的接入云节点。接入云中的节点相对稳定，移动性较弱，因此第二接口可以采用传统的基于连接的接口，第二接口需要支持相应的移动性管理，从而保证业务的连续性。
Figure PCTCN2019088197-appb-000009
所述边缘云与所述接入云之间具有第三接口，所述第三接口为基于连接的接口。
这里，第三接口连接了边缘云节点和接入云节点。
边缘云与接入云之间承载着由边缘云转发的用户终端的业务数据。其中边缘云中的节点变化相对动态，移动性较强；接入云中的节点相对稳定，移动性较弱，因此第三接口可以采用传统的基于连接的接口，第三接口需要支持相应的移动性管理，从而保证业务的连续性。
Figure PCTCN2019088197-appb-000010
所述接入云与所述核心云之间具有第四接口，所述第四接口为基于连接的接口。
这里，第四接口连接了接入云节点和核心云节点。
第四接口可以使用与LTE S1接口或者NR NG接口类似的接口设计。
Figure PCTCN2019088197-appb-000011
所述多个边缘云节点中不同边缘云节点之间具有第五接口，所述第五接口为基于无连接的接口。
这里，第五接口连接了不同的边缘云节点。由于边缘云中的节点具有频繁移动的特点，因此第五接口需要具有较强的灵活性，能够支持拓扑接口的灵活变化，本申请实施例将第五接口设计为基于无连接的接口。
Figure PCTCN2019088197-appb-000012
所述多个接入云节点中不同接入云节点之间具有第六接口，所述第六接口为基于连接的接口。
这里，第六接口连接了不同的接入云节点。
接入云中不同节点间相对拓扑接口较为静态，且能够维持一定时间，因此第六接口可以使用与LTE X2接口或者NR Xn接口类似的接口设计。
本申请实施例的上述接口中，第一接口和第二五接口为基于无连接的接口，基于无连接的接口是指该接口对应的传输资源是预配置的或者竞争获得的。相对而言，基于连接的接口对应的传输资源需要申请(或者请求)。举个例子：设备1和设备2之间基于无连接的接口进行通信，那么，如果有预配置的资源，设备1和设备2就使用该预配置的资源进行通信，如果没有预配置的资源，设备1和设备2就等待有预配置的资源或者竞争获得资源后再进行通信。
本申请实施例的上述接口，按照接口方向可以分为垂直类型接口与水平类型接口，其中，1)所述第一接口、所述第二接口、所述第三接口以及所述第四接口属于垂直类型接口，所述垂直类型接口中的不同接口之间具有控制或被控制关系。这里，控制或被控制关系是指由上层节点控制接口的建立、修改、删除；并通过接口控制下层节点的业务建立、资源分配、错误恢复等。2)所述第五接口和所述第六接口属于水平类型接口，水平类型接口两侧的节点的角色平等，存在信息交互与信息共享，但是不存在控制或被控制关系。
通过上述方案，将网络架构的接口分为垂直类型接口与水平类型接口，不同类型的接口所体现的功能和意义不同，从而与边缘云、接入云以及核心云一起形成完整的网络架构。
本申请实施例的技术方案中，用户终端与接入云或者边缘云与接入云之间的接口与LTE和NR中的Uu接口类似，此外，当接入云包括多个接入云节点时，所述边缘云与所述接入云之间的接口支持所述多个边缘云节点与多个接入云节点之间的通信，参照图9，多个边缘云节点与多个接入云节点之间支持多对多通信。
这里，所述多个边缘云节点与多个接入云节点之间的通信，包括以下至少之一：
所述多个边缘云节点中的一个或至少两个边缘云节点连接一个接入云节点；
所述多个接入云节点中的一个或至少两个接入云节点连接一个边缘云节点。
这里，所述多个边缘云节点与多个接入云节点之间的通信，包括以下至少之一：
在分散方向上的多节点对多节点的通信；
在汇聚方向上的多节点对多节点的通信。
具体实现上述多个边缘云节点与多个接入云节点之间的通信，可以采用如下方式：所述接入云和所述用户终端具有目标协议层，所述目标协议层位于应用层与接入层之间；其中，当一个边缘云节点连接至少两个接入云节点时，所述接入云侧的目标协议层用于对来自所述至少两个接入云节点的业务数据进行汇聚处理，或者对待发送给所述至少两个接入云节点的业务数据进行分散处理；所述用户终端侧的目标协议层用于对待发送给所述至少两个边缘云节点的业务数据进行分散处理，或者，对来自所述至少两个边缘云节点的业务数据进行汇聚处理。
举个例子：用户终端与2个边缘云节点(如节点1和节点2)，以及个接入云节点(如节点A和节点B)之间进行通信。用户终端侧的目标协议层将待发送给节点1和节点2的业务数据分散为数据流1和数据流2，其中，数据流1发给节点1，数据流2发给节点2。节点1可以转发数据流1给节点A，也可以将数据流1复制两份分别发给节点A和节点B，同理，节点2可以转发数据流2给节点B，也可以将数据流2复制两份分别发给节点A和节点B。接入云侧的目标协议层对节点A和节点B的 全部数据流进行汇聚处理。反之，接入云侧的目标协议层将待发送给节点A和节点B的业务数据分散为数据流1和数据流2，其中，数据流1发给节点A，数据流2发给节点B。节点A可以转发数据流1给节点1，也可以将数据流1复制两份分别发给节点1和节点2，同理，节点B可以转发数据流2给节点2，也可以将数据流2复制两份分别发给节点1和节点2。用户终端侧的目标协议层对来自节点1和节点2的全部数据流进行汇聚处理。
需要说明的是，上述目标协议层为接入云级别(跨不同的接入云节点)，甚至是跨云级别(跨接入云与边缘云)，从而共同为某个用户终端提供服务，具体协议栈如图10所示，目标协议层具有如下特点：1)保证数据包的服务质量(Quality of Service，QoS)、数据包计数、恢复、加解密、重传等功能。2)目标协议层可以以某个接入云节点为主体，即目标协议层的逻辑功能放在某一接入云节点中。3)目标协议层不仅可以跨接入云内部不同的接云入点，也可以跨接接入云与边缘云之间不同的节点。
本申请实施例的技术方案中，对于上述用户终端与边缘云或者边缘云中不同节点间的接口，由于节点移动性较强，节点间的拓扑较为动态，因此可以采用基于无连接的接口进行数据交互。以下结合图11对基于无连接的接口所支持的通信流程进行描述。
图11为本申请实施例提出的基于无连接的接口的通信方法的流程示意图，如图11所示，所述通信方法包括以下流程：
步骤1101：用户终端基于无连接的接口与至少两个边缘云节点中的每个边缘云节点进行通信。
具体地，基于无连接的接口的通信流程包括以下步骤：
(1)用户终端接收所述至少两个边缘云节点中的每个边缘云节点发送的广播消息，所述广播消息包括系统信息，所述系统信息包括以下至少之一：链路带宽、传输资源配置信息、当前资源承载的业务信息、边缘云节点的处理能力、边缘云节点的覆盖范围、边缘云节点的移动信息。
这里，用户终端可以接收一个或多个边缘云节点发送的广播消息。参照图12，用户终端接收3个边缘云节点发送的广播消息。其中，广播消息包括相应边缘云节点的系统信息，具体地，系统信息包括以下至少之一：链路带宽、传输资源配置信息、边缘云节点的处理能力、边缘云节点的覆盖范围、边缘云节点的移动信息。进一步，所述广播消息还包括同步信息，该同步信息为分散方向上的同步信息。
在本申请一些可选实施方式中，所述传输资源配置信息包括以下至少之一：时间资源信息、频率资源信息、时间资源确定方法、频率资源确定方法、可占用时间、业务抢占优先级。
这里，可占用时间是指传输资源可以占用的时间长度，可占用时间可以是若干个周期或者某个绝对时间长度。
这里，业务抢占优先级用于指示：在抢占资源时，哪些业务可以优先抢占，从而保证该业务即使在资源已经使用的情况下，仍然可以抢占该资源。
需要说明的是，上述传输资源配置信息进一步包括发送数据对应的传输资源配置信息和接收数据对应的传输资源配置信息。用户终端通过上述传输资源配置信息可以确定发送数据对应的第一目标资源和/或接收数据对应的第二目标资源。这种传输资源配置方式实现了网络侧给用户终端预先分配传输资源，用户终端在进行数据发送和/或接收时，无需申请资源，可以直接在预先分配的传输资源上进行数据发送和/或接收。
在本申请一些可选实施方式中，所述传输资源配置信息仅包括时间资源信息的情况下，所述用户终端基于所述时间资源信息确定相应的频率资源信息。
在本申请一些可选实施方式中，所述时间资源确定方法包括以下发送数据对应 的时间资源确定方法：
对于目标时间单元，若连续多个周期内所述目标时间单元均未被占用，则所述用户终端通过竞争方式占用所述目标时间单元进行数据发送。或者，对于目标时间单元，用户终端通过竞争方式占用所述目标时间单元进行数据发送。
举个例子：目标时间单元为第n个帧或第n个帧中的第a个时隙，若连续m个周期目标时间单元都是空的(即未被占用)，此时用户终端可以通过竞争方式进行数据发送。这里，m为大于等于0的整数。
在本申请一些可选实施方式中，所述时间资源确定方法包括以下接收数据对应的时间资源确定方法：
I：所述用户终端确定需要在全部的时间单元上接收数据；或者，
II：所述用户终端按照终端标识确定需要接收数据的目标时间单元；或者，
III：所述用户终端按照发送数据占用的时间单元确定需要接收数据的目标时间单元。
这里，时间单元可以是符号、或时隙、或子帧。
在本申请一些可选实施方式中，预先分配传输资源(即上述第一目标资源和/或第二目标资源)可以是具体的某个资源，也可以是一组资源(如资源池)。
(2)所述用户终端基于所述传输资源配置信息，在预设的第一目标资源上发送数据和/或在第二目标资源上接收数据。
本申请实施例中，所述第一目标资源和所述第二目标资源具有对应关系。所述用户终端在第一目标资源上发送的数据中携带第一识别号，所述第一识别号用于标识所述第一目标资源，边缘云节点接收到用户终端发送的数据后，根据第一识别号可以确定出第一目标资源，并在与第一目标资源对应的第二目标资源上向用户终端反馈数据，从而所述用户终端在与所述第一目标资源对应的第二目标资源上接收数据。
以图13为例，其中标号2对应的时间是不能发送和接收的时间，标号3和5对应的时间是可以发送的时间，标号4和6对应的时间是可以接收的时间，边缘云节点通过广播消息给出相应的传输资源配置，用户终端按照指示在相应的时间上进行数据的发送和/或接收即可。另一方面，边缘云节点还可以将标号为3和4的时间关联起来，将标号为5和6的时间关联起来，若用户终端在标号为3对应的时间上发送数据，则会在标号为4对应的时间上接收数据；若用户终端在标号为5对应的时间上发送数据，则会在标号为6对应的时间上接收数据。需要说明的是，各个标号对应的时间可以包括一个或多个时隙。每个标号对应的时间的长度可以相同或者不同。
图6为本申请实施例提供的网络架构的示意图，如图6所示，所述网络架构包括：边缘云601、接入云602以及核心云603；其中，所述边缘云601通过所述接入云602与所述核心云603连接，所述边缘云601包括多个边缘云节点，所述接入云602包括至少一个接入云节点，所述核心云603包括至少一个核心云节点，所述多个边缘云节点中的至少两个边缘云节点共同为用户终端提供业务服务。
在本申请一些可选实施方式中，所述边缘云节点为用户终端的接入节点，所述边缘云节点为移动终端或固定终端。
在本申请一些可选实施方式中，所述接入云节点为所述用户终端和/或所述边缘云节点的接入节点，所述接入云节点为接入卫星或基站。
在本申请一些可选实施方式中，所述核心云节点为核心服务器。
在本申请一些可选实施方式中，所述边缘云601、所述接入云602和所述核心云603中的至少两个云之间进行信息共享形成垂直云。
在本申请一些可选实施方式中，所述边缘云601、所述接入云602和所述核心云 603中的任意一个云内部不同节点间进行信息共享形成水平云。
在本申请一些可选实施方式中，所述至少两个边缘云节点通过信息共享共同为用户终端提供业务服务；或者，所述至少两个边缘云节点通过所述接入云602为用户终端提供业务服务；或者，所述至少两个边缘云节点通过所述接入云602和所述核心云603为用户终端提供业务服务。
在本申请一些可选实施方式中，所述边缘云601与所述用户终端之间具有第一接口，所述接入云602与用户终端之间具有第二接口，所述边缘云601与所述接入云602之间具有第三接口，所述接入云602与所述核心云603之间具有第四接口；所述第一接口为基于无连接的接口，所述第二接口、所述第三接口以及所述第四接口为基于连接的接口。
在本申请一些可选实施方式中，所述第一接口、所述第二接口、所述第三接口以及所述第四接口属于垂直类型接口。
在本申请一些可选实施方式中，所述多个边缘云节点中不同边缘云节点之间具有第五接口，所述第五接口为基于无连接的接口。
在本申请一些可选实施方式中，所述多个接入云节点中不同接入云节点之间具有第六接口，所述第六接口为基于连接的接口。
在本申请一些可选实施方式中，当所述接入云602包括多个接入云节点时，所述边缘云601与所述接入云602之间的接口支持所述多个边缘云节点与多个接入云节点之间的通信。
在本申请一些可选实施方式中，所述多个边缘云节点与多个接入云节点之间的通信，包括以下至少之一：
所述多个边缘云节点中的一个或至少两个边缘云节点连接一个接入云节点；
所述多个接入云节点中的一个或至少两个接入云节点连接一个边缘云节点。
在本申请一些可选实施方式中，所述接入云602和所述用户终端具有目标协议层，所述目标协议层位于应用层与接入层之间；
当一个边缘云节点连接至少两个接入云节点时，所述接入云602侧的目标协议层用于对来自所述至少两个接入云节点的业务数据进行汇聚处理，或者对待发送给所述至少两个接入云节点的业务数据进行分散处理；
所述用户终端侧的目标协议层用于对待发送给所述至少两个边缘云节点的业务数据进行分散处理，或者，对来自所述至少两个边缘云节点的业务数据进行汇聚处理。
本领域技术人员应当理解，本申请实施例的上述网络架构的相关描述可以参照本申请实施例的通信方法的相关描述进行理解。
图14为本申请实施例提供的通信装置的示意图，如图14所示，所述通信装置包括：
通信单元1401，用于基于无连接的接口与至少两个边缘云节点中的每个边缘云节点进行通信。
在本申请一些可选实施方式中，所述通信单元1401，用于接收所述至少两个边缘云节点中的每个边缘云节点发送的广播消息，所述广播消息包括系统信息，所述系统信息包括以下至少之一：链路带宽、传输资源配置信息、当前资源承载的业务信息、边缘云节点的处理能力、边缘云节点的覆盖范围、边缘云节点的移动信息；基于所述传输资源配置信息，在预设的第一目标资源上发送数据和/或在第二目标资源上接收数据。
在本申请一些可选实施方式中，所述传输资源配置信息包括以下至少之一：时间资源信息、频率资源信息、时间资源确定方法、频率资源确定方法、可占用时间、业务抢占优先级。
在本申请一些可选实施方式中，所述传输资源配置信息仅包括时间资源信息的情况下，所述通信单元1401基于所述时间资源信息确定相应的频率资源信息。
在本申请一些可选实施方式中，所述时间资源确定方法包括以下发送数据对应的时间资源确定方法：
对于目标时间单元，若连续多个周期内所述目标时间单元均未被占用，则所述通信单元1401通过竞争方式占用所述目标时间单元进行数据发送。
在本申请一些可选实施方式中，所述时间资源确定方法包括以下接收数据对应的时间资源确定方法：
所述通信单元1401确定需要在全部的时间单元上接收数据；或者，
所述通信单元1401按照终端标识确定需要接收数据的目标时间单元；或者，
所述通信单元1401按照发送数据占用的时间单元确定需要接收数据的目标时间单元。
在本申请一些可选实施方式中，所述第一目标资源和所述第二目标资源具有对应关系；所述通信单元1401在第一目标资源上发送的数据中携带第一识别号，所述第一识别号用于标识所述第一目标资源；
所述通信单元1401在与所述第一目标资源对应的第二目标资源上接收数据。
在本申请一些可选实施方式中，所述广播消息还包括同步信息。
本领域技术人员应当理解，本申请实施例的上述通信装置的相关描述可以参照本申请实施例的通信方法的相关描述进行理解。
图15是本申请实施例提供的一种通信设备1500示意性结构图。该通信设备可以是终端，也可以是网络设备，图15所示的通信设备1500包括处理器1510，处理器1510可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图15所示，通信设备1500还可以包括存储器1520。其中，处理器1510可以从存储器1520中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器1520可以是独立于处理器1510的一个单独的器件，也可以集成在处理器1510中。
可选地，如图15所示，通信设备1500还可以包括收发器1530，处理器1510可以控制该收发器1530与其他设备进行通信，具体地，可以向其他设备发送信息或数据，或接收其他设备发送的信息或数据。
其中，收发器1530可以包括发射机和接收机。收发器1530还可以进一步包括天线，天线的数量可以为一个或多个。
可选地，该通信设备1500具体可为本申请实施例的网络设备，并且该通信设备1500可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该通信设备1500具体可为本申请实施例的移动终端/终端设备，并且该通信设备1500可以实现本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
图16是本申请实施例的芯片的示意性结构图。图16所示的芯片1600包括处理器1610，处理器1610可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图16所示，芯片1600还可以包括存储器1620。其中，处理器1610可以从存储器1620中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器1620可以是独立于处理器1610的一个单独的器件，也可以集成在处理器1610中。
可选地，该芯片1600还可以包括输入接口1630。其中，处理器1610可以控制该输入接口1630与其他设备或芯片进行通信，具体地，可以获取其他设备或芯片发送的信息或数据。
可选地，该芯片1600还可以包括输出接口1640。其中，处理器1610可以控制该输出接口1640与其他设备或芯片进行通信，具体地，可以向其他设备或芯片输出信息或数据。
可选地，该芯片可应用于本申请实施例中的网络设备，并且该芯片可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该芯片可应用于本申请实施例中的移动终端/终端设备，并且该芯片可以实现本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
应理解，本申请实施例的处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解，上述存储器为示例性但不是限制性说明，例如，本申请实施例中的存储器还可以是静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synch link DRAM，SLDRAM)以及直接内存总线随机存取存储器(Direct Rambus  RAM，DR RAM)等等。也就是说，本申请实施例中的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请实施例还提供了一种计算机可读存储介质，用于存储计算机程序。
可选的，该计算机可读存储介质可应用于本申请实施例中的网络设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机可读存储介质可应用于本申请实施例中的移动终端/终端设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序产品，包括计算机程序指令。
可选的，该计算机程序产品可应用于本申请实施例中的网络设备，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机程序产品可应用于本申请实施例中的移动终端/终端设备，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序。
可选的，该计算机程序可应用于本申请实施例中的网络设备，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机程序可应用于本申请实施例中的移动终端/终端设备，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说 对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，)ROM、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应所述以权利要求的保护范围为准。

Claims (56)

  1. 一种通信方法，应用网络架构，所述网络架构包括：边缘云、接入云以及核心云；所述方法包括：
    所述边缘云通过所述接入云与所述核心云连接，所述边缘云包括多个边缘云节点，所述接入云包括至少一个接入云节点，所述核心云包括至少一个核心云节点，所述多个边缘云节点中的至少两个边缘云节点共同为用户终端提供业务服务。
  2. 根据权利要求1所述的方法，其中，所述边缘云节点为用户终端的接入节点，所述边缘云节点为移动终端或固定终端。
  3. 根据权利要求1或2所述的方法，其中，所述接入云节点为所述用户终端和/或所述边缘云节点的接入节点，所述接入云节点为接入卫星或基站。
  4. 根据权利要求1至3中任一项所述的方法，其中，所述核心云节点为核心服务器。
  5. 根据权利要求1至4中任一项所述的方法，其中，所述边缘云、所述接入云和所述核心云中的至少两个云之间进行信息共享形成垂直云。
  6. 根据权利要求1至5中任一项所述的方法，其中，所述边缘云、所述接入云和所述核心云中的任意一个云内部不同节点间进行信息共享形成水平云。
  7. 根据权利要求1至6中任一项所述的方法，其中，所述多个边缘云节点中的至少两个边缘云节点共同为用户终端提供业务服务，包括：
    所述至少两个边缘云节点通过信息共享共同为用户终端提供业务服务；或者，
    所述至少两个边缘云节点通过所述接入云为用户终端提供业务服务；或者，
    所述至少两个边缘云节点通过所述接入云和所述核心云为用户终端提供业务服务。
  8. 根据权利要求1至7中任一项所述的方法，其中，所述边缘云与所述用户终端之间具有第一接口，所述接入云与用户终端之间具有第二接口，所述边缘云与所述接入云之间具有第三接口，所述接入云与所述核心云之间具有第四接口；所述第一接口为基于无连接的接口，所述第二接口、所述第三接口以及所述第四接口为基于连接的接口。
  9. 根据权利要求8所述的方法，其中，所述第一接口、所述第二接口、所述第三接口以及所述第四接口属于垂直类型接口。
  10. 根据权利要求1至9中任一项所述的方法，其中，所述多个边缘云节点中不同边缘云节点之间具有第五接口，所述第五接口为基于无连接的接口。
  11. 根据权利要求1至10中任一项所述的方法，其中，所述多个接入云节点中不同接入云节点之间具有第六接口，所述第六接口为基于连接的接口。
  12. 根据权利要求8或10所述的方法，其中，所述基于无连接的接口支持以下通信方式：
    用户终端接收所述至少两个边缘云节点中的每个边缘云节点发送的广播消息，所述广播消息包括系统信息，所述系统信息包括以下至少之一：链路带宽、传输资源配置信息、当前资源承载的业务信息、边缘云节点的处理能力、边缘云节点的覆盖范围、边缘云节点的移动信息；
    所述用户终端基于所述传输资源配置信息，在预设的第一目标资源上发送数据和/或在第二目标资源上接收数据。
  13. 根据权利要求12所述的方法，其中，所述传输资源配置信息包括以下至少 之一：时间资源信息、频率资源信息、时间资源确定方法、频率资源确定方法、可占用时间、业务抢占优先级。
  14. 根据权利要求13所述的方法，其中，所述传输资源配置信息仅包括时间资源信息的情况下，所述用户终端基于所述时间资源信息确定相应的频率资源信息。
  15. 根据权利要求13所述的方法，其中，所述时间资源确定方法包括以下发送数据对应的时间资源确定方法：
    对于目标时间单元，若所述目标时间单元均未被占用，则所述用户终端通过竞争方式占用所述目标时间单元进行数据发送。
  16. 根据权利要求13或15所述的方法，其中，所述时间资源确定方法包括以下接收数据对应的时间资源确定方法：
    所述用户终端确定需要在全部的时间单元上接收数据；或者，
    所述用户终端按照终端标识确定需要接收数据的目标时间单元；或者，
    所述用户终端按照发送数据占用的时间单元确定需要接收数据的目标时间单元。
  17. 根据权利要求12至16中任一项所述的方法，其中，所述第一目标资源和所述第二目标资源具有对应关系；
    所述用户终端在第一目标资源上发送的数据中携带第一识别号，所述第一识别号用于标识所述第一目标资源；
    所述用户终端在与所述第一目标资源对应的第二目标资源上接收数据。
  18. 根据权利要求12至17中任一项所述的方法，其中，所述广播消息还包括同步信息。
  19. 根据权利要求1至18中任一项所述的方法，其中，当所述接入云包括多个接入云节点时，所述边缘云与所述接入云之间的接口支持所述多个边缘云节点与多个接入云节点之间的通信。
  20. 根据权利要求19所述的方法，其中，所述多个边缘云节点与多个接入云节点之间的通信，包括以下至少之一：
    所述多个边缘云节点中的一个或至少两个边缘云节点连接一个接入云节点；
    所述多个接入云节点中的一个或至少两个接入云节点连接一个边缘云节点。
  21. 根据权利要求19或20所述的方法，其中，所述接入云和所述用户终端具有目标协议层，所述目标协议层位于应用层与接入层之间；
    当一个边缘云节点连接至少两个接入云节点时，所述接入云侧的目标协议层用于对来自所述至少两个接入云节点的业务数据进行汇聚处理，或者对待发送给所述至少两个接入云节点的业务数据进行分散处理；
    所述用户终端侧的目标协议层用于对待发送给所述至少两个边缘云节点的业务数据进行分散处理，或者，对来自所述至少两个边缘云节点的业务数据进行汇聚处理。
  22. 一种通信方法，所述通信方法包括：
    用户终端基于无连接的接口与至少两个边缘云节点中的每个边缘云节点进行通信。
  23. 根据权利要求22所述的方法，其中，所述用户终端基于无连接的接口与至少两个边缘云节点中的每个边缘云节点进行通信，包括：
    用户终端接收所述至少两个边缘云节点中的每个边缘云节点发送的广播消息，所述广播消息包括系统信息，所述系统信息包括以下至少之一：链路带宽、传输资源配置信息、当前资源承载的业务信息、边缘云节点的处理能力、边缘云节点的覆盖范围、边缘云节点的移动信息；
    所述用户终端基于所述传输资源配置信息，在预设的第一目标资源上发送数据和/或在第二目标资源上接收数据。
  24. 根据权利要求23所述的方法，其中，所述传输资源配置信息包括以下至少之一：时间资源信息、频率资源信息、时间资源确定方法、频率资源确定方法、可占用时间、业务抢占优先级。
  25. 根据权利要求24所述的方法，其中，所述传输资源配置信息仅包括时间资源信息的情况下，所述用户终端基于所述时间资源信息确定相应的频率资源信息。
  26. 根据权利要求24所述的方法，其中，所述时间资源确定方法包括以下发送数据对应的时间资源确定方法：
    对于目标时间单元，若连续多个周期内所述目标时间单元均未被占用，则所述用户终端通过竞争方式占用所述目标时间单元进行数据发送。
  27. 根据权利要求24或26所述的方法，其中，所述时间资源确定方法包括以下接收数据对应的时间资源确定方法：
    所述用户终端确定需要在全部的时间单元上接收数据；或者，
    所述用户终端按照终端标识确定需要接收数据的目标时间单元；或者，
    所述用户终端按照发送数据占用的时间单元确定需要接收数据的目标时间单元。
  28. 根据权利要求23至27中任一项所述的方法，其中，所述第一目标资源和所述第二目标资源具有对应关系；
    所述用户终端在第一目标资源上发送的数据中携带第一识别号，所述第一识别号用于标识所述第一目标资源；
    所述用户终端在与所述第一目标资源对应的第二目标资源上接收数据。
  29. 根据权利要求23至28中任一项所述的方法，其中，所述广播消息还包括同步信息。
  30. 一种网络架构，所述网络架构包括：边缘云、接入云以及核心云；其中，所述边缘云通过所述接入云与所述核心云连接，所述边缘云包括多个边缘云节点，所述接入云包括至少一个接入云节点，所述核心云包括至少一个核心云节点，所述多个边缘云节点中的至少两个边缘云节点共同为用户终端提供业务服务。
  31. 根据权利要求30所述的网络架构，其中，所述边缘云节点为用户终端的接入节点，所述边缘云节点为移动终端或固定终端。
  32. 根据权利要求30或31所述的网络架构，其中，所述接入云节点为所述用户终端和/或所述边缘云节点的接入节点，所述接入云节点为接入卫星或基站。
  33. 根据权利要求30至32中任一项所述的网络架构，其中，所述核心云节点为核心服务器。
  34. 根据权利要求30至33中任一项所述的网络架构，其中，所述边缘云、所述接入云和所述核心云中的至少两个云之间进行信息共享形成垂直云。
  35. 根据权利要求30至34中任一项所述的网络架构，其中，所述边缘云、所述接入云和所述核心云中的任意一个云内部不同节点间进行信息共享形成水平云。
  36. 根据权利要求30至35中任一项所述的网络架构，其中，所述至少两个边缘云节点通过信息共享共同为用户终端提供业务服务；或者，所述至少两个边缘云节点通过所述接入云为用户终端提供业务服务；或者，所述至少两个边缘云节点通过所述接入云和所述核心云为用户终端提供业务服务。
  37. 根据权利要求30至36中任一项所述的网络架构，其中，所述边缘云与所述用户终端之间具有第一接口，所述接入云与用户终端之间具有第二接口，所述边缘 云与所述接入云之间具有第三接口，所述接入云与所述核心云之间具有第四接口；所述第一接口为基于无连接的接口，所述第二接口、所述第三接口以及所述第四接口为基于连接的接口。
  38. 根据权利要求37所述的网络架构，其中，所述第一接口、所述第二接口、所述第三接口以及所述第四接口属于垂直类型接口。
  39. 根据权利要求30至38中任一项所述的网络架构，其中，所述多个边缘云节点中不同边缘云节点之间具有第五接口，所述第五接口为基于无连接的接口。
  40. 根据权利要求30至39中任一项所述的网络架构，其中，所述多个接入云节点中不同接入云节点之间具有第六接口，所述第六接口为基于连接的接口。
  41. 根据权利要求30至40中任一项所述的网络架构，其中，当所述接入云包括多个接入云节点时，所述边缘云与所述接入云之间的接口支持所述多个边缘云节点与多个接入云节点之间的通信。
  42. 根据权利要求41的网络架构，其中，所述多个边缘云节点与多个接入云节点之间的通信，包括以下至少之一：
    所述多个边缘云节点中的一个或至少两个边缘云节点连接一个接入云节点；
    所述多个接入云节点中的一个或至少两个接入云节点连接一个边缘云节点。
  43. 根据权利要求41或42所述的网络架构，其中，所述接入云和所述用户终端具有目标协议层，所述目标协议层位于应用层与接入层之间；
    当一个边缘云节点连接至少两个接入云节点时，所述接入云侧的目标协议层用于对来自所述至少两个接入云节点的业务数据进行汇聚处理，或者对待发送给所述至少两个接入云节点的业务数据进行分散处理；
    所述用户终端侧的目标协议层用于对待发送给所述至少两个边缘云节点的业务数据进行分散处理，或者，对来自所述至少两个边缘云节点的业务数据进行汇聚处理。
  44. 一种通信装置，所述装置包括：
    通信单元，用于基于无连接的接口与至少两个边缘云节点中的每个边缘云节点进行通信。
  45. 根据权利要求44所述的装置，其中，所述通信单元，用于接收所述至少两个边缘云节点中的每个边缘云节点发送的广播消息，所述广播消息包括系统信息，所述系统信息包括以下至少之一：链路带宽、传输资源配置信息、当前资源承载的业务信息、边缘云节点的处理能力、边缘云节点的覆盖范围、边缘云节点的移动信息；基于所述传输资源配置信息，在预设的第一目标资源上发送数据和/或在第二目标资源上接收数据。
  46. 根据权利要求45所述的装置，其中，所述传输资源配置信息包括以下至少之一：时间资源信息、频率资源信息、时间资源确定方法、频率资源确定方法、可占用时间、业务抢占优先级。
  47. 根据权利要求46所述的装置，其中，所述传输资源配置信息仅包括时间资源信息的情况下，所述通信单元基于所述时间资源信息确定相应的频率资源信息。
  48. 根据权利要求46所述的装置，其中，所述时间资源确定方法包括以下发送数据对应的时间资源确定方法：
    对于目标时间单元，若连续多个周期内所述目标时间单元均未被占用，则所述通信单元通过竞争方式占用所述目标时间单元进行数据发送。
  49. 根据权利要求46或48所述的装置，其中，所述时间资源确定方法包括以下接收数据对应的时间资源确定方法：
    所述通信单元确定需要在全部的时间单元上接收数据；或者，
    所述通信单元按照终端标识确定需要接收数据的目标时间单元；或者，
    所述通信单元按照发送数据占用的时间单元确定需要接收数据的目标时间单元。
  50. 根据权利要求45至49中任一项所述的装置，其中，所述第一目标资源和所述第二目标资源具有对应关系；
    所述通信单元在第一目标资源上发送的数据中携带第一识别号，所述第一识别号用于标识所述第一目标资源；
    所述通信单元在与所述第一目标资源对应的第二目标资源上接收数据。
  51. 根据权利要求45至50中任一项所述的装置，其中，所述广播消息还包括同步信息。
  52. 一种通信设备，包括：处理器和存储器，该存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，执行如权利要求1至21中任一项所述的方法，或者权利要求22至29中任一项所述的方法。
  53. 一种芯片，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如权利要求1至21中任一项所述的方法，或者权利要求22至29中任一项所述的方法。
  54. 一种计算机可读存储介质，用于存储计算机程序，所述计算机程序使得计算机执行如权利要求1至21中任一项所述的方法，或者权利要求22至29中任一项所述的方法。
  55. 一种计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行如权利要求1至21中任一项所述的方法，或者权利要求22至29中任一项所述的方法。
  56. 一种计算机程序，所述计算机程序使得计算机执行如权利要求1至21中任一项所述的方法，或者权利要求22至29中任一项所述的方法。
PCT/CN2019/088197 2019-05-23 2019-05-23 一种通信方法及装置、网络架构 Ceased WO2020232720A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP19929371.3A EP3972219A4 (en) 2019-05-23 2019-05-23 Communication method and apparatus, and network architecture
PCT/CN2019/088197 WO2020232720A1 (zh) 2019-05-23 2019-05-23 一种通信方法及装置、网络架构
CN201980088399.4A CN113273162B (zh) 2019-05-23 2019-05-23 一种通信方法及装置、网络架构
US17/533,808 US12001890B2 (en) 2019-05-23 2021-11-23 Communication method and apparatus, and network architecture

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/088197 WO2020232720A1 (zh) 2019-05-23 2019-05-23 一种通信方法及装置、网络架构

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/533,808 Continuation US12001890B2 (en) 2019-05-23 2021-11-23 Communication method and apparatus, and network architecture

Publications (1)

Publication Number Publication Date
WO2020232720A1 true WO2020232720A1 (zh) 2020-11-26

Family

ID=73459513

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/088197 Ceased WO2020232720A1 (zh) 2019-05-23 2019-05-23 一种通信方法及装置、网络架构

Country Status (4)

Country Link
US (1) US12001890B2 (zh)
EP (1) EP3972219A4 (zh)
CN (1) CN113273162B (zh)
WO (1) WO2020232720A1 (zh)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112953770A (zh) * 2021-02-18 2021-06-11 上海宽带技术及应用工程研究中心 边缘云网关免配置接入的方法、系统、介质及云端管理系统
CN113645119A (zh) * 2021-08-16 2021-11-12 中国电信股份有限公司广州分公司 一种云网融合架构及网吧云平台
CN114461392A (zh) * 2022-01-25 2022-05-10 西南交通大学 一种带宽感知的选择性数据多播方法
WO2023005317A1 (zh) * 2021-07-27 2023-02-02 华为技术有限公司 通信系统、方法及装置
CN117014487A (zh) * 2023-09-28 2023-11-07 中国电子科技集团公司第二十八研究所 一种面向高机动环境的自适应接入边缘云方法
CN117176671A (zh) * 2022-05-27 2023-12-05 华为技术有限公司 一种云资源推荐方法及相关设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102638582A (zh) * 2012-04-12 2012-08-15 华为技术有限公司 数据通信方法及通信端
CN103297507A (zh) * 2013-05-13 2013-09-11 西安电子科技大学 云计算运营系统及向用户提供服务的方法
US20180376338A1 (en) * 2016-08-05 2018-12-27 Nxgen Partners Ip, Llc Sdr-based massive mimo with v-ran cloud architecture and sdn-based network slicing

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102684817A (zh) * 2011-03-10 2012-09-19 万鑫明 一种基于数字喷泉码的云存储体系结构及服务提供方法
CN102497406B (zh) * 2011-12-07 2014-07-30 湖南大学 一种面向节点移动性的无线mesh网资源分发方法
US9949133B2 (en) * 2016-08-05 2018-04-17 Nxgen Partners Ip, Llc Ultra-broadband virtualized telecom and internet
CN107333281B (zh) * 2017-05-15 2019-08-20 北京邮电大学 移动计算卸载协同控制系统及方法
CN109426245A (zh) * 2017-06-29 2019-03-05 李志远 车辆智能行车安全控制技术
CN108243245B (zh) * 2017-12-20 2020-06-12 上海交通大学 基于混合雾计算的无线接入网络及其资源调配方法
CN108600310A (zh) * 2018-03-21 2018-09-28 南京邮电大学 一种物联网环境下的雾计算体系架构
CN111936973A (zh) * 2018-06-29 2020-11-13 英特尔公司 用于提供在云边缘处对服务的高效迁移的技术
US11974272B2 (en) * 2018-12-18 2024-04-30 Nokia Technologies Oy Apparatus and method for utilizing uplink resources
CN109640348B (zh) * 2019-01-08 2020-11-20 中国联合网络通信集团有限公司 多业务mec网络架构、多业务数据流的处理方法及装置
CN109788069B (zh) * 2019-02-27 2021-02-12 电子科技大学 物联网中基于移动边缘计算的计算卸载方法
CN113841370B (zh) * 2019-05-17 2024-11-26 瑞典爱立信有限公司 网络节点和在其中实施的用于处理无线通信网络中的通信的方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102638582A (zh) * 2012-04-12 2012-08-15 华为技术有限公司 数据通信方法及通信端
CN103297507A (zh) * 2013-05-13 2013-09-11 西安电子科技大学 云计算运营系统及向用户提供服务的方法
US20180376338A1 (en) * 2016-08-05 2018-12-27 Nxgen Partners Ip, Llc Sdr-based massive mimo with v-ran cloud architecture and sdn-based network slicing

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ZHANG, YONG ET AL.: "The Evolution Planning and Deployment Plan of China Unicom’s Multi-access Edge Computing Technology", DESIGNING TECHNIQUES OF POSTS AND TELECOMMUNICATIONS, 30 April 2018 (2018-04-30), pages 1 - 6, XP055755086 *
ZHU, JINBIN ET AL.: "Edge Cloud Clustering Algorithm Based on Maximal Clique", COMPUTER SCIENCE, vol. 45, no. 4, 30 April 2018 (2018-04-30), pages 1 - 6, XP055754984 *

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112953770A (zh) * 2021-02-18 2021-06-11 上海宽带技术及应用工程研究中心 边缘云网关免配置接入的方法、系统、介质及云端管理系统
CN112953770B (zh) * 2021-02-18 2023-07-14 上海宽带技术及应用工程研究中心 边缘云网关免配置接入的方法、系统、介质及云端管理系统
WO2023005317A1 (zh) * 2021-07-27 2023-02-02 华为技术有限公司 通信系统、方法及装置
CN113645119A (zh) * 2021-08-16 2021-11-12 中国电信股份有限公司广州分公司 一种云网融合架构及网吧云平台
CN114461392A (zh) * 2022-01-25 2022-05-10 西南交通大学 一种带宽感知的选择性数据多播方法
CN114461392B (zh) * 2022-01-25 2023-03-31 西南交通大学 一种带宽感知的选择性数据多播方法
CN117176671A (zh) * 2022-05-27 2023-12-05 华为技术有限公司 一种云资源推荐方法及相关设备
CN117014487A (zh) * 2023-09-28 2023-11-07 中国电子科技集团公司第二十八研究所 一种面向高机动环境的自适应接入边缘云方法
CN117014487B (zh) * 2023-09-28 2023-12-15 中国电子科技集团公司第二十八研究所 一种面向高机动环境的终端自适应就近连接边缘云方法

Also Published As

Publication number Publication date
US12001890B2 (en) 2024-06-04
CN113273162A (zh) 2021-08-17
EP3972219A4 (en) 2022-05-25
CN113273162B (zh) 2024-01-26
EP3972219A1 (en) 2022-03-23
US20220083393A1 (en) 2022-03-17

Similar Documents

Publication Publication Date Title
CN114009096B (zh) 用于通信的方法和用于网络的控制器
US12001890B2 (en) Communication method and apparatus, and network architecture
CN109121170B (zh) 会话管理的方法、装置、设备及系统
EP3742795A1 (en) Quality of service (qos) parameter processing method, network element, system, and storage medium
WO2022048505A1 (zh) 多流关联传输的方法、装置及系统
WO2021140464A1 (en) TSC-5G QoS MAPPING WITH CONSIDERATION OF ASSISTANCE TRAFFIC INFORMATION AND PCC RULES FOR TSC TRAFFIC MAPPING AND 5G QoS FLOWS BINDING
CN104010370B (zh) 异构系统融合控制方法及装置
EP4096290A1 (en) Quality of service qos parameter processing method and network element, system, and storage medium
CN109151914B (zh) 一种通信方法及接入网设备
US20250176056A1 (en) Configuration and Reporting for Deterministic Networks
WO2023212175A2 (en) Deterministic networks
WO2021097858A1 (zh) 一种通信方法及装置
CN115348665A (zh) 一种通信方法、设备及系统
US20230254859A1 (en) Downlink Transmission Method and Communication Apparatus
CN114007087B (zh) 一种媒体流切换方法及装置
WO2023185608A1 (zh) 一种数据传输的方法及通信装置
CN114424498B (zh) 数据传输方法、装置、系统和存储介质
CN113905449A (zh) 计算资源调度方法、系统及设备
CN106714006B (zh) 一种基于单播广播技术的异构无线网络视频多路并行传输方法
WO2024012378A1 (zh) 一种通信方法及装置
WO2023185402A1 (zh) 通信方法及装置
CN118786653A (zh) 用于扩展现实流量的服务质量处理的系统和方法
WO2024065524A1 (zh) 分组数据汇聚协议实体建立、分组数据汇聚协议实体建立指示装置以及方法
CN117042036A (zh) 通信方法及装置
US20200412456A1 (en) Systems and methods for managing data on a backhaul network

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: 19929371

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019929371

Country of ref document: EP

Effective date: 20211213