A communication method and apparatus

Abstract

A communication method and device are used to implement a new service provided by a mobile network. The communication method comprises: a management network element receiving a first service trigger request, the first service trigger request being used to request execution of a first service; the management network element determining first service orchestration information according to the first service trigger request; the first service orchestration information being used to orchestrate a plurality of tasks, the plurality of tasks being respectively used to implement partial processing functions of the first service; the plurality of tasks comprising a first task and a second task; the management network element sending first indication information to a device processing the first task and second indication information to a device processing the second task according to the first service orchestration information; wherein the first indication information is used to instruct execution of the first task through a first data session group; and the second indication information is used to instruct execution of the second task through a second data session group.

Description

Technical Field

[0001] This application relates to the field of mobile communication technology, and in particular to a communication method and apparatus. Background Technology

[0002] In traditional communication scenarios, the mobile network (or simply network) is responsible for providing connectivity services to terminal devices, that is, establishing a transmission channel (or transmission pipe, transmission path, or forwarding path, etc.) so that the terminal device and the DN can transmit data packets of various services quickly and reliably.

[0003] However, future communication networks may need to support service types beyond connectivity, such as artificial intelligence (AI), sensing, and computing. A solution is urgently needed to enable these new services in future communication networks. Summary of the Invention

[0004] This application provides a communication method and apparatus for enabling mobile networks to provide new services.

[0005] In a first aspect, this application provides a communication method that can be applied to a management network element, or components (such as processors, chips, chip systems, circuits, functional modules, or others) or software modules within the management network element. The method may include: the management network element receiving a trigger request for a first service, the trigger request for which the first service is requested to execute the first service; the management network element determining first service orchestration information based on the first service trigger request; the first service orchestration information orchestrating multiple tasks, each task being used to implement a portion of the processing functions of the first service; the multiple tasks including a first task and a second task; the management network element sending first instruction information to a device processing the first task and second instruction information to a device processing the second task based on the first service orchestration information; wherein the first instruction information instructs the execution of the first task through a first data session group; and the second instruction information instructs the execution of the second task through a second data session group.

[0006] In this way, after receiving the trigger request of the first service, the management network element can orchestrate multiple tasks to implement the first service, and send instruction information to the devices executing the tasks according to the orchestration information, so that multiple devices can execute different tasks to implement the first service.

[0007] In one possible design, when the first data session group includes at least two data sessions, the first indication information is also used to indicate the execution order of the at least two data sessions in the first data session group; when the second data session group includes at least two data sessions, the second indication information is also used to indicate the execution order of the at least two data sessions in the second data session group.

[0008] In this way, the management network element can indicate the orchestration information corresponding to the first task (including the execution order of at least two data sessions in the first data session group) through the first instruction information, and indicate the orchestration information corresponding to the second task through the second instruction information, thereby improving the accuracy of multiple devices executing the first service.

[0009] In one possible design, before the management network element determines the first service orchestration information, the management network element may also receive multiple session registration information from multiple devices; the multiple session registration information is used to indicate the set of data sessions established by each device; the multiple devices include the device that performs the aforementioned first task and the device that performs the aforementioned second task.

[0010] Based on the aforementioned design, the process by which the management network element determines the orchestration information of the first service may include: the management network element determining the orchestration information of the first service based on multiple session registration information and the first service triggering request; wherein, the data sessions in the first data session group are included in the set of data sessions already established by the device processing the first task, and the data sessions in the second data session group are included in the set of data sessions already established by the device processing the second task.

[0011] In this way, the management network element can orchestrate the first service based on the registration information of multiple sessions of multiple devices. In other words, the management network element can use the data sessions that have been established between multiple devices to orchestrate the first service, which can improve the service orchestration efficiency.

[0012] In one possible design, the multiple session registration information includes the granularity information supported by each data session in the set of data sessions established by each device; the management network element can also determine the transmission granularity of each data session based on the granularity information supported by each data session and the first service triggering request; wherein, the first indication information includes the transmission granularity of each data session in the first data session group.

[0013] In this way, the transmission granularity of different data sessions in the first data session group can be different. The management network element can use the first indication information to indicate the transmission granularity of each data session, thereby improving the processing accuracy of the first service.

[0014] In one possible design, the transmission granularity includes any of the following: service granularity, task granularity, track granularity, group granularity, subgroup granularity, and object granularity.

[0015] In one possible design, the management network element can also send a third instruction to the device handling the first task, the third instruction being used to instruct the establishment of at least one data session in the first data session group; the management network element can also send a fourth instruction to the device handling the second task, the fourth instruction being used to instruct the establishment of at least one data session in the second data session group.

[0016] In this way, the management network element can send instruction information to the device that is processing the task, so that the device can establish a data session according to the instruction information, thereby meeting the needs of executing the task (first task or second task); that is, the device that is processing the task does not need to establish redundant (unrelated to the current task) data sessions, which can improve resource utilization.

[0017] Secondly, this application provides a communication method that can be applied to a first device, or a component (such as a processor, chip, chip system, circuit, functional module, or others) or software module within the first device. The method may include: the first device receiving first instruction information from a management network element, the first instruction information indicating the execution of a first task through a first data session group, the first task being used to implement partial processing functions of a first service; the first device also determining output data for the first task based on the first instruction information and the input data of the first task; the first device also sending the output data of the first task to a second device through the first data session; the first data session is included in the first data session group and is an established data session between the first device and the second device.

[0018] In this way, the first device can receive the first instruction information from the management network element and perform the first task based on the first data session indicated in the first instruction information.

[0019] In one possible design, when the first data session group includes at least two data sessions, the first indication information is also used to indicate the execution order of at least two data sessions in the first data session group; the first device may also send a fifth indication information to the second device, the fifth indication information being used to indicate the execution order of at least two data sessions in the first data session group.

[0020] In one possible design, when the first data session group includes a data session, the second device is the device that processes the next task of the first task.

[0021] In one possible design, the first indication information includes the transmission granularity of each data session in the first data session group; the process of the first device sending the output data of the first task to the second device through the first data session may include: the first device determining that the output data of the first task is the transmission granularity of the first data session; the first device sending the output data of the first task to the second device through the first data session.

[0022] In one possible design, the transmission granularity includes any of the following: service granularity, task granularity, track granularity, group granularity, subgroup granularity, and object granularity.

[0023] In one possible design, the first device can also establish a first data session.

[0024] In some examples, the first device can establish multiple data sessions (including the first data session) before the first service is triggered, thus saving service processing time. Correspondingly, the first device can also send its first session registration information to the management network element. This first session registration information indicates the set of data sessions already established by the first device, which includes the first data session. In this way, the first device can establish multiple data sessions (including the first data session) before the first service is triggered and report the session registration information of the established data sessions to the management network element. This allows the management network element to orchestrate the first service based on the session registration information, thereby improving service orchestration efficiency.

[0025] In other examples, the first device can establish a first data session after the first service triggers a request. Correspondingly, before establishing the first data session, the first device can also receive third instruction information from the management network element, which instructs the establishment of the first data session. In this way, after the management network element determines the orchestration information of the first service, the first device can establish data sessions (including the first data session) specifically according to demand, without establishing redundant data sessions, thus improving resource utilization.

[0026] Thirdly, embodiments of this application provide a communication device. The device can implement any possible implementation of any of the first to second aspects described above.

[0027] In one optional implementation, the apparatus may include modules, units, or means corresponding one-to-one to the methods / operations / steps / actions that perform any possible implementation of any of the first to second aspects. These modules, units, or means may be hardware circuits, software, or a combination of hardware circuits and software. In another optional implementation, the apparatus includes a processing module (sometimes also called a processing unit) and a communication module (sometimes also called a transceiver module, communication unit, etc.). The communication module is capable of both sending and receiving functions. When the communication module performs the sending function, it may be called a sending unit (sometimes also called a sending module); when the communication module performs the receiving function, it may be called a receiving unit (sometimes also called a receiving module). The sending unit and the receiving unit may be the same functional module, referred to as the communication module, which performs both sending and receiving functions; or, the sending unit and the receiving unit may be different functional modules, with "communication module" being a collective term for these functional modules.

[0028] For example, when the apparatus is used to perform the method described in any one of the first to second aspects, the apparatus may include a processing module and a communication module.

[0029] Fourthly, embodiments of this application also provide a communication device, including a processor for executing a computer program (or computer-executable instructions) stored in a memory, which, when executed, causes the device to perform a method as described in any possible implementation of any of the first to second aspects.

[0030] In one possible implementation, the processor and memory are integrated together.

[0031] In another possible implementation, the memory is located outside the communication device.

[0032] The communication device also includes a communication interface for communicating with other devices, such as sending or receiving data and / or signals. Exemplarily, the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface.

[0033] Fifthly, a computer-readable storage medium is provided for storing a computer program or instructions that, when executed, enable the implementation of a method in any possible implementation of the first or second aspect, and the method shown in any possible implementation thereof.

[0034] In a sixth aspect, a computer program product containing instructions is provided, which, when run on a computer, enables the implementation of any possible implementation of the first or second aspect.

[0035] In a seventh aspect, embodiments of this application also provide a communication device for performing a method for any possible implementation of any of the first to second aspects described above.

[0036] Eighthly, a chip or chip system is provided, comprising logic circuitry (or, as understood, a processor, which may include logic circuitry, etc.), and further comprising an input / output interface. The input / output interface can be used to input messages or to output messages. The input / output interface can be the same interface, i.e., the same interface can implement both sending and receiving functions; or, the input / output interface includes an input interface and an output interface, the input interface being used to implement the receiving function, i.e., to receive messages; and the output interface being used to implement the sending function, i.e., to send messages. The logic circuitry can be used to perform operations other than the sending and receiving functions in any possible implementation of any of the first to second aspects described above; the logic circuitry can also be used to transmit messages to the input / output interface or to receive messages from other communication devices from the input / output interface. The chip system can be used to implement any possible implementation of any of the first to second aspects described above. The chip system can be composed of a chip or can include chips and other discrete devices.

[0037] Optionally, the chip system may also include a memory, which can be used to store instructions, and the logic circuits can call the instructions stored in the memory to implement the corresponding functions.

[0038] A ninth aspect provides a communication system that may include a management network element and a first device. The management network element may be used to implement the methods shown in the first aspect and any possible implementation thereof, and the first device may be used to implement the methods shown in the second aspect and any possible implementation thereof.

[0039] The technical effects brought about by the second to ninth aspects above can be found in the description of the beneficial effects of the corresponding solutions in the first aspect above, and will not be repeated here. Attached Figure Description

[0040] Figure 1 This application provides a schematic diagram of the architecture of a communication system.

[0041] Figure 2a This is a schematic diagram of the architecture of another communication system provided in an embodiment of this application;

[0042] Figure 2b This is a schematic diagram of the architecture of another communication system provided in an embodiment of this application;

[0043] Figure 3 A flowchart illustrating a communication method provided in an embodiment of this application;

[0044] Figure 4a A business process example diagram provided for an embodiment of this application;

[0045] Figure 4b A task flow example diagram provided for an embodiment of this application;

[0046] Figure 4c This application provides an example diagram of a task flow in a communication system.

[0047] Figure 4d A task flow example diagram provided for an embodiment of this application;

[0048] Figure 5a A flowchart illustrating a communication method provided in an embodiment of this application;

[0049] Figure 5b A flowchart illustrating another communication method provided in an embodiment of this application;

[0050] Figure 6a A flowchart illustrating another communication method provided in an embodiment of this application;

[0051] Figure 6b A flowchart illustrating another communication method provided in an embodiment of this application;

[0052] Figure 7 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0053] Figure 8 This is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0054] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings. The specific operational methods in the method embodiments can also be applied to the device embodiments or system embodiments; therefore, the implementation of the device and the method can refer to each other, and repeated details will not be repeated.

[0055] In the description of this application, unless otherwise stated, " / " signifies "or," for example, A / B can mean A or B. "And / or" in this application merely describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. Furthermore, in the description of this application, "at least one" refers to one or more items, and "multiple" refers to two or more items. In the description of this application, terms such as "first" and "second" are used only for descriptive purposes and should not be construed as indicating or implying relative importance or order.

[0056] The steps marked with dashed lines in the accompanying figures are optional.

[0057] The technical solutions of the embodiments of this application can be applied to various communication systems, such as: Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, and LTE Time Division Duplex (TDD) systems. The technical solutions of the embodiments of this application can also be applied to other communication systems, such as Public Land Mobile Network (PLMN) systems, LTE Advanced (LTE-A) systems, the 5th generation (5G) systems, New Radio (NR) systems, Machine-to-Machine (M2M) systems, or other future communication systems, or other wireless communication systems employing wireless access technologies, all of which can adopt the technical solutions of the embodiments of this application.

[0058] See Figure 1 This paper illustrates a network architecture diagram of a communication system applicable to embodiments of this application. The communication system mainly includes the following network functions and entities: user equipment (UE), radio access network (RAN) element 1, RAN element 2 (optional), interface user plane function (UPF) element, interface user plane function (I-UPF) element (optional), data network (DN), access and mobility management function (AMF) element, session management function (SMF) element, and policy control function (PCF) element.

[0059] Terminal equipment: also known as user equipment, terminal, mobile station, mobile terminal, etc. Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc. The embodiments of this application do not limit the specific technology or device form used in the terminal.

[0060] Access network elements: sometimes also called access network equipment, RAN entities, access nodes, or RAN nodes, etc., constitute part of the communication system and are used to help terminals achieve wireless access.

[0061] In one possible scenario, a RAN node can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB), a base station in a future mobile communication system, or an access node in a WiFi system. A RAN node can be a macro base station, a micro base station, an indoor station, a relay node, a donor node, or a radio controller in a CRAN scenario. Optionally, a RAN node can also be a server, a wearable device, a vehicle, or in-vehicle equipment. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). All or part of the functions of the RAN node in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (e.g., a cloud platform). The RAN node in this application can also be a logical node, logical module, or software capable of implementing all or part of the RAN node functions.

[0062] In another possible scenario, multiple RAN nodes collaborate to assist the terminal in achieving wireless access, with different RAN nodes each implementing a portion of the base station's functions. For example, RAN nodes can be central units (CUs), distributed units (DUs), CU-control plane (CPs), CU-user plane (UPs), or radio units (RUs), etc. CUs and DUs can be set up separately or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).

[0063] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.

[0064] Data network: A data network that provides business services to users. Generally, the client is located on the terminal device, and the server is located on the data network. The data network can be a private network, such as a local area network (LAN), or an external network not controlled by the operator, such as the Internet. It can also be a dedicated network jointly deployed by operators, such as a network that provides Internet Protocol (IP) multimedia core network subsystem (IMS) services.

[0065] Session management function network elements are primarily used for session management, allocation and management of terminal device (Internet Protocol, IP) addresses, selection of manageable user equipment plane functions, policy control, or endpoints for charging function interfaces, and downlink data notification. In 5G, the session management function network element can be an SMF network element. In future communications, the session management function network element can still be an SMF network element, or have other names; this application does not impose any limitations.

[0066] Access and mobility management function network elements: These are mainly used for mobility management and access management, and can be, for example, the mobility management entity (MME) function in a 4G communication network or the AMF network element in a 5G network. In future communications, access and mobility management function network elements may still be AMF network elements, or may have other names; this application does not limit this.

[0067] Policy control function network elements are control plane functions provided by operators to provide session (such as protocol data unit (PDU) sessions) policies to session management function network elements. These policies can include charging-related policies, quality of service (QoS)-related policies, and authorization-related policies. In 5G, the policy control function network element can be a PCF network element. In future communications, the policy control function network element can still be a PCF network element, or it may have other names; this application does not limit this.

[0068] User plane function network elements are used for packet routing and forwarding, or QoS processing of user plane data. In 5G, user plane function network elements can be UPF network elements, as shown in the example in the figure, which is an I-UPF network element. In future communications, user plane function network elements can still be UPF network elements, or may have other names; this application does not limit this.

[0069] Optionally, the communication system may also include other network functions and entities (not shown in the figure), which are not limited in this application. For example, the communication system may also include application function (AF) network elements, unified data management (UDM) network elements, network exposure function (NEF) network elements, network repository function (NRF) network elements, network data analytics function (NWDAF) network elements, transmission control function (TCF) network elements, and so on.

[0070] Application function network elements (AF elements) are used for data routing affected by applications, accessing network open functions, or interacting with policy frameworks for policy control. In 5G, AF elements can be AF network elements, and in future communications, AF elements may still be AF network elements or have other names; this application does not limit this.

[0071] Unified data management network element: used to handle user identification, subscription, access authentication, registration, or mobility management, etc. In 5G, the unified data management network element can be a UDM network element. In future communications, the unified data management network element can still be a UDM network element, or have other names; this application does not limit this.

[0072] Network Open Function (NEF) elements: These are used to securely expose services and capabilities provided by 3GPP network functions to the outside world. In 5G, NEF elements can be NEF elements, and in future communications, NEF elements may still be NEF elements or have other names; this application does not limit this.

[0073] Network storage function network element: used to store network function entities and their service description information, and to support service discovery, network element entity discovery, and other functions. In 5G, the network storage function network element can be an NRF network element. In future communications, the network storage function network element can still be an NRF network element, or have other names; this application does not limit this.

[0074] It should be noted that the names of the network elements in this application are merely examples, and this application does not preclude the possibility of using other names for the network elements in the future, or the merging of functions between the network elements. With the evolution of technology, any device or network element capable of implementing the functions of the aforementioned network elements is within the scope of protection of this application.

[0075] It should be understood that Figure 1The interface names between the various network elements are merely examples; in actual implementations, the interface names may differ, and this application does not impose any specific limitations on them. Furthermore, the names of the messages (or signaling) transmitted between the aforementioned network elements are also merely examples and do not constitute any limitation on the function of the messages themselves.

[0076] For ease of description, each network element will be referred to by its corresponding English abbreviation in the following text. For example, “SMF” will be used to represent the session management function network element.

[0077] In the aforementioned communication system, the mobile network (referred to as the network for short) provides connectivity services for terminal devices, that is, it establishes a transmission channel (or transmission pipe, transmission path, or forwarding path, etc.) to enable fast and reliable transmission of data packets for various services between the terminal device and the DN. It can be understood that the transmission channel referred to in this article refers to the transmission path of data packets between the terminal device and the DN. For example, the terminal device can establish a session (such as a PDU session) with the UPF (intermediate device), and then provide connectivity services to the terminal device based on this session, enabling fast and reliable transmission of data packets (containing the processing results of service data) between the terminal device and the DN.

[0078] With the development of technology and the diversification of business needs, it is necessary to enable the mobile network to support diverse service types in the future. This application proposes a new mobile network architecture. Figure 2a This application provides a network architecture diagram for a communication system, which includes a process service function (PSF) network element and a mission control function (MCF) network element (not shown in the figure); optionally, the communication system may also include a gateway (GW). This application does not limit the number of each network element in the communication system.

[0079] PSF network elements can also be called PSF nodes or process (PROC) nodes. (Combined with...) Figure 1 The communication system shown can have its PSF network element deployed independently on the UE side / RAN side / core network side / data network side, or it can be deployed in conjunction with network elements on the RAN side / core network side / data network side. For example, the PSF network element can be deployed in conjunction with the RAN (e.g., deployed on the CU / DU), or it can be deployed in conjunction with network elements on the core network side (e.g., TCF network element, NWDAF network element, UPF network element, and other NF network elements). The PSF can be used to implement Service 1 in a new service, or it can be used to implement Service 2 in a new service.

[0080] MCF network elements are used to manage various services within the business communication system. Combined with... Figure 1 In the communication system shown, the MCF network element can be deployed independently on the RAN side or the core network side (e.g., the control plane). The MCF network element does not need to be deployed in conjunction with the SMF network element; the MCF network element can connect to the NF network element on the core network side via the SBI.

[0081] The Gateway (GW) supports media over QUIC (MoQ) transmission based on Quick UDP internet connections (QUIC), and is therefore also called a MoQ-GW or relay. The GW can act as a proxy device for devices that do not support MoQ, and / or, the GW can act as a data forwarding device. Figure 1 The communication system shown can be deployed independently or integrated with core network elements; for example, the GW can be integrated with core network NF elements. The GW can be used to implement Service 1 in a new service.

[0082] Based on the foregoing Figure 2a The communication system shown in the diagram is illustrated in this application embodiment, which also provides a network architecture diagram for another communication system. For example... Figure 2b As shown, the communication system includes PSF network elements, MCF network elements, and GW; the communication system also includes a connection network between multiple devices.

[0083] The above architecture enables mobile networks to provide the following two services:

[0084] Service 1: In the transmission channel of the aforementioned connection service, intermediate devices need to adjust the transmission granularity of data packets. For example, a terminal device sends a data packet (group granularity) to the UPF; the UPF can adjust the transmission granularity of this data packet from group granularity to subgroup granularity (the content of the data packet remains unchanged), and send the subgroup granularity data packet to the DN.

[0085] Service 2: In scenarios such as computing, sensing, and data processing, mobile networks may also need to provide some connectionless services; that is, the devices through which the transmission channel flows, such as the aforementioned terminal devices and / or intermediate devices, may also need to perform some processing functions of the business, that is, they need to process data packets to generate new data packets.

[0086] For example, the data packets for a certain type of service provided by DN are large in size. To improve transmission efficiency, terminal devices can compress the data packets before transmission to reduce the amount of data transmitted and improve transmission efficiency. However, in some scenarios, such as when the terminal device does not have such compression processing capabilities or when the terminal device has insufficient power, this solution is not applicable. In these scenarios, it is necessary to move some of the service processing functions to the network side (such as the core network) for execution.

[0087] For example, in video rendering services, if the terminal device offloads (or moves) the video rendering computing capabilities to the network side, it can reduce the terminal device's processing requirements for local computing power, which is beneficial for terminal devices with lower hardware quality to obtain a better video service experience. In addition, it can also reduce the power consumption of the terminal device.

[0088] For example, if a terminal device has the ability to train and infer small models, while the network side has large models with more parameters, the terminal device can interact with the large and small models on the network side to move (or unload) some model training and inference processing to the network side for execution, thereby improving the terminal device's model's ability to process artificial intelligence (AI) services.

[0089] For ease of description, the embodiments of this application will be understood as the new service regarding the modification of the transmission granularity of data packets and the processing of business data.

[0090] Combination Figure 3 This application provides a communication method that can be applied to Figure 2a The communication system shown is implemented by a management network element and multiple devices (including a first device); the management network element can be... Figure 2a In the communication system shown, the first device of the MCF network element can be... Figure 2a This refers to any PSF network element in the communication system shown. The following section combines... Figure 3 The technical solution of this application will be described in detail with specific method embodiments. Figure 3 As shown, the communication method may include S301 to S303.

[0091] S301: The management network element receives the trigger request for the first service. The trigger request for the first service is used to request the execution of the first service.

[0092] Optionally, the triggering request for the first service includes the service identification information (missionidentifier, mission ID) of the first service.

[0093] In this embodiment of the application, the complete service flow of a non-connection service initiated by any node in the communication system is called a mission. This mission needs to be completed by multiple PSF network elements in the complete service flow. A PSF network element is a network element with processing function. The data passing through the PSF network element usually changes.

[0094] S302: The management network element determines the orchestration information of the first service based on the first service trigger request; the orchestration information of the first service is used to orchestrate multiple tasks, each task corresponding to a data session group; the multiple tasks include the first task and the second task.

[0095] The first service orchestration information may include at least one data session group and its identification information, as well as the execution order of the data sessions within each data session group. This application embodiment does not limit the combination of multiple tasks in the first service orchestration information, nor does it limit the combination of PSF network elements corresponding to each task.

[0096] In one possible design, the management network element can determine multiple tasks and their execution order based on a first service trigger request. Each task is used to implement a portion of the processing functions of that service. Accordingly, the first service orchestration information may include task identifier (task ID) information for each of the multiple tasks.

[0097] In this application, the execution process of the task includes the process of processing task data (implemented by PSF network elements), and may also include the process of forwarding the processed task data to the PSF network element of the next task (implemented by PSF network elements and / or at least one GW network element).

[0098] In this context, the input data of a task can be understood as the task data before processing, and the output data of a task can be understood as the task data after processing. The task data before and after processing are different; that is, the input data and output data for any given task are different. The execution process of the first task of a service includes: the PSF network element (i.e., the starting device of the service) acquiring the task data (i.e., the initial data of the service) and sending this task data to the PSF network element of the next task. In other words, for the first task of a service, there is no input data; the output data of the first service is the initial data of the service. The execution process of the last task of a service includes: the PSF network element (i.e., the ending device of the service) processing the task data; the processed task data is the final data of the service.

[0099] In the aforementioned tasks, the output data of the previous task becomes the input data of the next task. When the second task is the next task after the first task, the output data of the first task becomes the input data of the second task; when the second task is the previous task of the first task, the output data of the second task becomes the input data of the first task.

[0100] Optionally, in addition to a PSF network element, the device executing each task may also include at least one GW. The GW does not process the data in the task, but only has the function of forwarding. Therefore, the data passing through the GW does not change.

[0101] The following example illustrates the business logic and the tasks derived from it.

[0102] In some examples, suppose service A includes: predicting the information of class A and class B targets appearing at the next time node based on class A and class B targets in video data, and rendering the video data based on the prediction results. Correspondingly, the management network element decomposes service A into multiple tasks: generating video data (task 1), identifying class A target information in the video data (task 2), combining historical data and the class A target information identified in task 2 to predict the information of class A targets appearing at the next time node (task 3), identifying class B targets in the video data and combining historical data to predict the information of class B targets appearing at the next time node (task 4), and combining the class A target information obtained from task 3 and the class B target information obtained from task 4 to render the video data (task 5). Among these, PSF1 has the ability to acquire video data (e.g., generate video data), PSF2 has the ability to identify targets, PSF3 has the ability to predict target information, PSF4 has the ability to identify targets and predict target information, and PSF5 has the ability to integrate data and perform video rendering.

[0103] In the example above, tasks 2 and 3 are used to implement the functionalities related to category A in business A, while task 4 is used to implement the functionalities related to category B in business A. That is, the input data for task 2 and task 4 are the same, but the output data for tasks 3 and 4 are different.

[0104] In some examples, suppose Service A includes: predicting information about Class A targets appearing at the next time point based on Class A targets in video data, and rendering the video data based on the prediction results. Correspondingly, the management network element decomposes Service A into several tasks: generating video data and dividing it into two parts (a first part and a second part) (Task 1); identifying information about Class A targets in the first part of the video data (Task 2); combining historical data and the information about Class A targets identified in Task 2 to predict information about Class A targets appearing at the next time point (Task 3); identifying Class A targets in the second part of the video data and combining historical data to predict information about Class A targets appearing at the next time point (Task 4); and combining the information about Class A targets obtained from Task 3 and Task 4 to render the video data (Task 5). Among these, PSF1 has the ability to acquire video data (e.g., generate and split video data), PSF2 has the ability to identify targets, PSF3 has the ability to predict target information, PSF4 has the ability to identify targets and predict target information, and PSF5 has the ability to integrate data and render the video.

[0105] In the aforementioned example, Tasks 2 and 3, along with Task 4, are all used to perform the function of "identifying Class A targets in video data and predicting the information of Class A targets that will appear at the next time node in business A". However, Tasks 2 and 3 target the first part of the video data after it has been split into segments corresponding to the business, while Task 4 targets the second part of the video data after it has been split into segments corresponding to the business.

[0106] like Figure 4a As shown, service A is implemented by PSF1, PSF2, PSF3, PSF4, and PSF5; as Figure 4b As shown, business A can be broken down into 5 tasks: Task 1, Task 2, Task 3, Task 4, and Task 5.

[0107] Task 1: PSF1 determines the output data of Task 1 based on the input data of Task 1 (i.e., the initial data of Service A); PSF1 sends the output data of Task 1 to PSF2 and PSF4 via multicast.

[0108] Task 2: PSF2 determines the output data of Task 2 based on the input data of Task 2 (i.e., the output data of Task 1); PSF2 sends the output data of Task 2 to PSF3 via unicast.

[0109] Task 3: PSF3 determines the output data of Task 3 based on the input data of Task 3 (i.e., the output data of Task 2); PSF3 sends the output data of Task 3 to PSF5 via unicast.

[0110] Task 4: PSF4 determines the output data of Task 4 based on the input data of Task 4 (i.e. the output data of Task 1); PSF4 sends the output data of Task 4 to PSF5 via unicast.

[0111] Task 5: PSF5 determines the output data for Task 5 based on the input data of Task 5 (i.e., the output data of Task 3 and the output data of Task 4). Optionally, PSF5 can also output the output data of Task 5.

[0112] Combination Figure 2a For the communication system, the implementation process of service A can be referenced. Figure 4c The different types of curves (dashed lines and solid lines) correspond to different tasks, as detailed in the diagram.

[0113] Optionally, the implementation of the aforementioned first service may also include one or more Gateways (GWs). For example, Task 1 can be replaced by: PSF1 sending the output data of Task 1 to GW1 via unicast, and GW1 sending the output data of Task 1 to PSF2 and PSF4 via multicast. Alternatively, Task 1 can be replaced by PSF1 sending the output data of Task 1 (including the first and second parts of the output data) to GW1 via unicast; GW1 sending the first part of the output data of Task 1 to PSF2 via unicast; and GW1 sending the first part of the output data of Task 1 to PSF4 via unicast.

[0114] Optionally, in the implementation process of the aforementioned first service, the implementation process of any data session can be abstracted as follows: Figure 4d The transmission model shown illustrates this; the PSF (or GW) acts as either a publisher or a subscriber during the data session implementation; the same PSF (or GW) may play different roles in different tasks. One publisher can correspond to one subscriber or multiple subscribers; that is, each data session corresponds to one publisher and at least one subscriber. Taking Task 1 as an example, Figure 4d In the described transport model, task 1 is divided into multiple data sessions, where GW is both a subscriber to the previous data session and a publisher of the next data session.

[0115] In one possible design, the management element can also perform the following steps A1.

[0116] Step A1: The management network element receives multiple session registration information from multiple devices; the multiple session registration information are used to indicate the set of data sessions established by each device. The multiple devices include the device performing the first task and the device performing the second task.

[0117] Based on the aforementioned design, S302 can be replaced by the following step A2.

[0118] Step A2: The management network element determines the orchestration information of the first service based on multiple session registration information and the first service trigger request.

[0119] Optionally, the management network element can select the data session group corresponding to each task from the data session set indicated by multiple session registration information to determine the first service orchestration information; in the process of selecting the data session group corresponding to each task, the management network element can follow the preset configuration principles (such as minimizing the number of routing hops).

[0120] The data sessions in the first data session group corresponding to the first task are included in the set of data sessions already established by the device executing the first task, and the data sessions in the second data session group corresponding to the second task are included in the set of data sessions already established by the device executing the second task. The following two examples illustrate the relationship between the data session group corresponding to the first task and the set of data sessions already established by the device executing (including processing and forwarding functions) the first task.

[0121] Example 1: The devices performing the first task include PSF6 (processing function), GW3 (forwarding function), and GW4 (forwarding function). Before executing S302, each device performing the first task (e.g., PSF6, GW3, and GW4) sends its own session registration information (set of established data sessions) to the management network element. For example, PSF6 sends its established data session set (including ID1) to the management network element, GW3 sends its established data session set (including ID1 and ID2) to the management network element, and GW4 sends its established data session set (including ID2 and ID3) to the management network element.

[0122] Based on this, the management network element can determine that the first data session group includes three data sessions (identified as ID1, ID2, and ID3 respectively). ID1 is used to identify the data session between PSF6 and GW3, ID2 is used to identify the data session between GW3 and GW4, and ID3 is used to identify the data session between GW4 and PSF7. The management network element can also determine the execution order of the data sessions included in the first data session group as follows: PSF6 determines the output data corresponding to the first task and sends the output data corresponding to the first task to GW3 through ID1; GW3 forwards the output data corresponding to the first task to GW4 through ID2; and GW4 forwards the output data corresponding to the first task to PSF7 through ID3.

[0123] Example 2: The devices performing the first task include PSF8 (processing function), GW5 (forwarding function), and GW6 (forwarding function). Before executing S302, each device performing the first task (PSF8, GW5, and GW6) sends its own session registration information (set of established data sessions) to the management network element. For example, PSF8 sends its established data session set (including ID4) to the management network element, GW5 sends its established data session set (including ID4 and ID5) to the management network element, and GW6 sends its established data session set (including ID5, ID6, and ID7) to the management network element.

[0124] Based on this, the management network element can determine that the first data session group includes four data sessions (identified as ID4, ID5, ID6, and ID7 respectively). ID4 is used to identify the data session between PSF8 and GW5, ID5 is used to identify the data session between GW5 and GW6, ID6 is used to identify the data session between GW6 and PSF9, and ID7 is used to identify the data session between GW6 and PSF10. The management network element can also determine the execution order of the data sessions included in the first data session group as follows: PSF8 determines the output data corresponding to the first task and sends the output data corresponding to the first task to GW5 through ID4; GW5 forwards the output data corresponding to the first task to GW6 through ID5; and GW6 multicasts the output data corresponding to the first task to PSF9 and PSF10 through ID6 and ID7.

[0125] Optionally, the aforementioned session registration information includes granularity information supported by each data session in the established data session set of each device; the management network element can also determine the transmission granularity of each data session based on the granularity information supported by each data session and the first service triggering request. It should be understood that data sessions within the same data session group can use the same transmission granularity or different transmission granularities. Transmission granularity includes any of the following: service granularity, task granularity, track granularity, group granularity, subgroup granularity, and object granularity.

[0126] The transmission granularity, from highest to lowest, is as follows: service granularity, task granularity, track granularity, group granularity, subgroup granularity, and object granularity. For example, if transmitting data at the group granularity requires transmitting x1 data packets, transmitting data at the subgroup granularity requires transmitting x2 data packets, and transmitting data at the object granularity requires transmitting x3 data packets, then x1 < x2 < x3.

[0127] S303: The management network element sends a first instruction message to the device that processes the first task according to the first service orchestration information; wherein the first instruction message is used to instruct the first task to be executed through the first data session group.

[0128] Optionally, when the first data session group includes at least two data sessions, the first indication information is also used to indicate the execution order of the at least two data sessions in the first data session group. Combined with... Figure 4a In the example, the first instruction information can indicate Figure 4a The first indication information may include some or all of the information; when the first task corresponding to the first data session group is task 1, the first indication information may indicate... Figure 4a Information within the dashed box.

[0129] In some instances, the first indication information can indicate the execution order of at least two data sessions in a first data session group through a data structure (structured information about the execution order of at least two data sessions).

[0130] In another example, the first indication information can indicate the execution order of at least two data sessions in a first data session group by using the identifier of the data session. For example, based on the aforementioned Example 1, the first indication information may include: ID1-ID2-ID3; based on the aforementioned Example 2, the first indication information may include: ID4-ID5-(ID6 and ID7).

[0131] Optionally, the first indication information is also used to indicate the transmission granularity of each data session in the first data session group.

[0132] In some examples, the management network element can also send second instruction information to the device that processes the second task based on the first service orchestration information. This process can refer to the aforementioned S303; wherein the second instruction information is used to instruct the execution of the second task through the second data session group.

[0133] Optionally, when the second data session group includes at least two data sessions, the second indication information is also used to indicate the execution order of the at least two data sessions in the second data session group.

[0134] Optionally, the second indication information is also used to indicate the transmission granularity of each data session in the second data session group.

[0135] In some examples, the first device is different from the device that triggered the first service. The management network element can send the initial data of the first service to the device that handles the first task among multiple tasks. For example, when the first task is the first task among multiple tasks corresponding to the first service and the device handling the first task is not the device that initiated the first service, the management network element can send the initial data of the first service to the device handling the first task.

[0136] Using the methods shown in S301 to S303 above, the management network element can orchestrate multiple tasks to implement the first service after receiving the trigger request of the first service, and send instruction information to the device processing the task according to the orchestration information, so that multiple devices can execute different tasks to implement the first service.

[0137] Assuming the device processing the first task includes a first device, the following describes part (or all) of the execution flow of the first task using the first device as an example. Based on the aforementioned S303, the first device can receive first instruction information from the management network element. The first instruction information is used to instruct the execution of the first task through the first data session group. The first task is used to implement part of the processing function of the first service. This communication method also includes S304 and S305.

[0138] S304: The first device determines the output data of the first task based on the first instruction information and the input data of the first task.

[0139] S305: The first device sends the output data of the first task to the second device through the first data session; correspondingly, the second device receives the output data of the first task through the first data session; the first data session is included in the first data session group and the first data session is a data session that has been established between the first device and the second device.

[0140] Optionally, when the first data session group includes a data session, the second device is the device that processes the next task of the first task.

[0141] In one possible design, the process of the first device sending the output data of the first task to the second device through the first data session in S305 may include: the first device determining that the output data of the first task is the transmission granularity of the first data session; and the first device sending the output data of the first task to the second device through the first data session.

[0142] Based on this design, the first device can also obtain the transmission granularity of the first data session.

[0143] For example, the first indication information includes the transmission granularity of each data session in the first data session group. In this application embodiment, the mode in which the MCF network element indicates the transmission granularity of each data session is called the MCF configuration mode. This mode can reduce end-to-end transmission latency of data sessions and improve the end-to-end transmission accuracy of data sessions.

[0144] like Figure 5a As shown, the first indication information may include information A and information B, respectively, and the transmission granularity of the first data session may be carried in information A or information B. Information A may include the QoS rules of the first data session (which can be reflected through the QoS flow identifier (QFI), the packet filtering settings of the first data session, and the QoS parameters of the first data session; information B may include the transmission granularity preference (sub preference) of the first data session, the priority of the two devices corresponding to the first data session, and the data flow path of the first data session.

[0145] For example, when the first indication information does not include the transmission granularity of the first data session, the first device and the second device can negotiate to determine the transmission granularity of the first data session. The negotiation process can refer to commonly used negotiation methods in the art, and the embodiments of this application do not limit the negotiation process. The embodiments of this application refer to the aforementioned mode of negotiating to determine the transmission granularity of the first data session as the negotiation mode. In the negotiation mode, it is not necessary to configure the transmission granularity of the data session when establishing a data session, which can reduce the consumption of computing resources.

[0146] For example, the negotiation process can be as follows: a first device can send a negotiation request to a second device, the negotiation request being used to request the selection of a transmission granularity from multiple alternative transmission granularities as the transmission granularity of the first data session, the negotiation request including multiple alternative transmission granularities; the second device selects the transmission granularity of the first data session based on the multiple alternative transmission granularities and its own capabilities, and sends the negotiation result to the first device; the first device receives the negotiation result from the second device, the negotiation result including the transmission granularity of the first data session.

[0147] For example, the negotiation process can be as follows: the first device sends a pre-selected transmission granularity to the second device. This pre-selected transmission granularity can be the most precise transmission granularity supported by the first device. The second device can determine whether to use the pre-selected transmission granularity as the transmission granularity of the first data session based on its own capabilities, and feed back the judgment result to the first device.

[0148] For example (see reference) Figure 5b Assuming the first device is device A and the second device is device B, both devices can select device C as a relay node to negotiate the transmission granularity of the first data session. Device A can send an announcement to device C, which includes multiple transmission granularities supported by device A. Device C can receive a subscription request from device B, which includes multiple transmission granularities supported by device B and the data stream (transmission granularity) preference corresponding to the first data session. Device C can also send task-related data to device B based on the aforementioned data stream preference indicated by device B. Device C can also send a subscription request to device A, which includes multiple transmission granularities supported by device C and the data stream preference corresponding to the first data stream. Device A can then send task-related data to device B (and / or device C) based on the aforementioned data stream preference indicated by device C. For example, device A and device B can negotiate and determine the transmission granularity of the first data session based on the service characteristics of the first service; for example, for live video service, the transmission granularity is selected as single frame transmission to improve the real-time performance of video transmission; for short video loading service, the transmission granularity is selected as multi-frame combined transmission to reduce signaling consumption.

[0149] It should be understood that the management network element can choose whether to carry the transmission granularity of the data session in the first instruction information based on the service characteristics of the first service. That is, the management network element can choose the MCF configuration mode or the negotiation mode.

[0150] Before executing S305, the first device can also establish a first data session with the second device.

[0151] In some examples, the first device can establish a default data session with the second device before the first service is triggered. The first device can also send its first session registration information to the management network element, indicating the set of data sessions already established by the first device, which includes the aforementioned default data session (which may be the first data session). Similarly, the second device can send its second session registration information to the management network element, indicating the set of data sessions already established by the second device. Accordingly, the management network element can receive this first session registration information through step A1.

[0152] The first session registration information (or the second session registration information) may include at least one of the following: the service identification information corresponding to the first data session, the task identification information corresponding to the first data session, the identification information of the first device, the role information of the first device in the first data session (publisher and / or subscriber), the identification information of the second device, and the role information of the second device in the first data session (publisher and / or subscriber).

[0153] In this way, before the first service is triggered, multiple devices establish their own default data sessions, and each device reports its own session registration information, so that the management network element can perform service orchestration through step A2, which can save service processing time.

[0154] In another example, before the first device establishes a data session with the second device, the management network element may also send third indication information to the first device (and / or); correspondingly, the first device receives the third indication information from the management network element, which is used to indicate the establishment of the first data session. The third indication information may further include the transmission granularity of the first data session.

[0155] In addition, when the first data session group includes at least two data sessions, the management network element can also instruct other devices performing the first task to establish other data sessions in the first data session group, which will not be elaborated here.

[0156] Similarly, the management network element can also send a fourth instruction message to the device performing the second task. The fourth instruction message is used to instruct the establishment of at least one data session in the second data session group. This application does not elaborate on the execution process of the second task. For details, please refer to the execution process of the first task.

[0157] In this way, after the first service is triggered, a data session (including the first data session) is established according to the needs of the first service, without the need to establish redundant data sessions in advance, which can improve resource utilization.

[0158] In one possible design, when the first data session group includes at least two data sessions, the first indication information is also used to indicate the execution order of at least two data sessions in the first data session group; the communication method also includes S306 and S307 (not shown in the figure).

[0159] S306: The first device sends a fifth instruction message to the second device. The fifth instruction message is used to indicate the execution order of at least two data sessions in the first data session group. The at least two data sessions include a second data session, which is the next data session after the first data session.

[0160] S307: The second device sends the output data of the first task to the third device through the second data session according to the fifth instruction information; the second data session is a data session that has been established between the second device and the third device.

[0161] Optionally, when the second data session is the last data session in the first data session group, the third device is the device that processes the next task of the first task.

[0162] Before executing S307, the second device can also establish a second data session with the third device.

[0163] The following section, in conjunction with the communication methods described in S301 to S307 above, combines... Figure 4c The communication system shown provides two embodiments.

[0164] Example 1:

[0165] Step 1-1: Device C sends a service trigger request to the MCF network element; correspondingly, the MCF network element receives the aforementioned service trigger request from device C (not shown in the figure) (for example, it could be PSF1); the service trigger request is used to request the implementation of service A.

[0166] It should be understood that the implementation process of step 1-1 can be referred to the description in S301.

[0167] Steps 1-2: The MCF network element determines the service orchestration information for service A based on the service trigger request. This service orchestration information may include multiple tasks corresponding to service A and the execution order of these tasks. For example, if the multiple tasks corresponding to service A are tasks 1 to 5, the execution order of tasks 1 to 5 is as follows: Figure 4a As shown. The service orchestration information for service A can also include the PSF network element corresponding to each task and the combination method between multiple PSF network elements (which can also be reflected through data session groups). For example, the MCF network element determines through orchestration that the data session group corresponding to task 2 includes data session A between PSF2 and PSF3. The MCF network element determines through orchestration that the data session group corresponding to task 3 includes data session B between PSF3 and GW2, and data session C between GW2 and PSF5.

[0168] Optionally, the service orchestration information for service A may also include the transmission granularity corresponding to each data session.

[0169] In some examples, the MCF network element can also determine the granularity of each data session based on the capabilities of each device. The MCF network element orchestrates the transmission granularity of data session A as granularity 1, data session B as granularity 2, and data session C as granularity 3. It should be understood that before the MCF network element determines the granularity of each data session, each device can also report its transmission granularity capability information to the MCF network element separately.

[0170] Steps 1-3: The MCF network element instructs each PSF network element to establish the data sessions required for service A (including establishing data session A, data session B, and data session C).

[0171] Steps 1-4: Each PSF network element can execute Task 2 and Task 3 based on Data Session A, Data Session B and Data Session C.

[0172] Example 2:

[0173] Step 2-1: Establish data sessions between various PSF network elements (or GW) in the communication system (e.g., Figure 2b The process of establishing a data session between any two PSF network elements (or GW) can be referred to steps a and b above (connections between different devices in the network).

[0174] refer to Figure 6a Taking the establishment of a default data session between the PSF network element and the GW network element in the communication system as an example, step 2-1 can be achieved through steps a to d.

[0175] Step a: The PSF network element initiates a default data session establishment request to the GW it is connected to. The default data session establishment request may include the task identification information corresponding to the default data session.

[0176] Step b: The aforementioned GW sends a default data session establishment response to the PSF network element. The default data session establishment response may include the transmission granularity corresponding to the default data session.

[0177] Step c: Complete the establishment of the default data session.

[0178] Step d: The PSF (and / or GW) reports the session registration information of the established default data session to the MCF network element.

[0179] The process of establishing a data session, as shown in step 2-1, is implemented in a self-organizing manner, without requiring MCF network element configuration or instructions. This self-organizing approach, compared to the centralized control based on SMF network elements in traditional communication methods, reduces control plane overhead.

[0180] In some examples, after establishing default data sessions between multiple PSFs and GWs in step 2-1, all PSFs in the communication system are connected to at least one GW, and the GWs are interconnected. Therefore, all GWs actually maintain information about all PSFs. When it is necessary to select a PSF based on the operational requirements of the service, the MCF network element can select the corresponding PSF network element through the GW. Since the number of GWs is significantly less than the number of PSFs, the overhead of control plane signaling can be greatly reduced.

[0181] Step 2-2: When the MCF network element receives the trigger request of service A, the MCF network element performs service orchestration for service A, that is, establishes a data session group.

[0182] Steps 2-3: Based on the service orchestration results of the MCF network element, execute service A.

[0183] Combination Figure 6b Steps 2-2 and 2-3 can be achieved through steps e to g.

[0184] Step e: The UE sends a service trigger request to the MCF network element.

[0185] Step f: MCF can determine the service orchestration result based on the service trigger request, that is, establish a data session group.

[0186] Step g: The MCF network element sends the configuration information of the data session group to the PSF network element (and / or GW).

[0187] It should be understood that the aforementioned Figure 6a and Figure 6b This can be combined into a first communication example, which will not be repeated here.

[0188] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions between different embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0189] It should also be noted that each step in the above embodiments can be executed by the corresponding device, or by components such as chips, processors, or chip systems within that device. The embodiments of this application do not limit their execution. The above embodiments are merely illustrative examples of execution by the corresponding device. Furthermore, the specific implementation methods or examples in the above embodiments do not limit the solutions provided by the embodiments of this application.

[0190] Based on the same technical concept, this application provides a communication device, which includes modules, units or means that perform the method steps in the above method embodiments. The functions, units or means can be implemented by software, or by hardware, or by hardware executing corresponding software.

[0191] For example, see Figure 7 The communication device 700 may include a processing module 701 and a communication module 702.

[0192] Optionally, the communication module 702 may include a sending module and / or a receiving module. The sending module is used to perform the sending operation in the above method embodiments. The receiving module is used to perform the receiving operation in the above method embodiments. It should be noted that the communication device 700 may only include a sending module and not a receiving module. Alternatively, the communication device 700 may only include a receiving module and not a sending module. Specifically, it depends on whether the above scheme performed by the communication device 700 includes both sending and receiving actions.

[0193] The processing module 701 is used for data processing. The communication module 702 can implement the corresponding communication functions.

[0194] Optionally, the communication device 700 may further include a storage module, which can be used to store instructions and / or data. The processing module 701 can read the instructions and / or data in the storage module so that the communication device 700 can implement the aforementioned method embodiments.

[0195] It should be understood that all relevant content of each step involved in the above method embodiments can be referenced to the functional description of the corresponding functional module.

[0196] The processing module 701 in the above embodiments can be implemented by at least one processor or processor-related circuitry. The communication module 702 can be implemented by a transceiver or transceiver-related circuitry. The communication module 702 can also be referred to as a communication module or a communication interface.

[0197] For example, the communication device 700 can be a management network element or a component configured within the management network element. The communication module 702 is used to receive a trigger request for a first service, the trigger request being used to request the execution of the first service; the processing module 701 is used to determine first service orchestration information based on the first service trigger request; the first service orchestration information is used to orchestrate multiple tasks, each task being used to implement a portion of the processing functions of the first service; the multiple tasks include a first task and a second task; the processing module 701 is also used to perform the following steps through the communication module 702: according to the first service orchestration information, sending first instruction information to a device processing the first task, and sending second instruction information to a device processing the second task; wherein, the first instruction information is used to instruct the execution of the first task through a first data session group; the second instruction information is used to instruct the execution of the second task through a second data session group.

[0198] In one possible design, when the first data session group includes at least two data sessions, the first indication information is also used to indicate the execution order of the at least two data sessions in the first data session group; when the second data session group includes at least two data sessions, the second indication information is also used to indicate the execution order of the at least two data sessions in the second data session group.

[0199] In one possible design, before the communication device 700 determines the first service orchestration information, the communication module 702 is further configured to: receive multiple session registration information from multiple devices; the multiple session registration information is used to indicate the set of data sessions established by each device, and the multiple devices include the device performing the aforementioned first task and the device performing the aforementioned second task.

[0200] Based on the aforementioned design, the processing module 701 is specifically used to: determine the first service orchestration information based on multiple session registration information and the first service trigger request; wherein, the data sessions in the first data session group are included in the set of data sessions already established by the device executing the first task, and the data sessions in the second data session group are included in the set of data sessions already established by the device executing the second task.

[0201] In one possible design, the multiple session registration information includes the granularity information supported by each data session in the set of data sessions established by each device; the processing module 701 is further configured to: determine the transmission granularity of each data session based on the granularity information supported by each data session and the first service triggering request; wherein, the first indication information includes the transmission granularity of each data session in the first data session group.

[0202] In one possible design, the transmission granularity includes any of the following: service granularity, task granularity, track granularity, group granularity, subgroup granularity, and object granularity.

[0203] In one possible design, the communication module 702 is further configured to: send a third instruction message to the device processing the first task, the third instruction message being used to instruct the establishment of at least one data session in the first data session group; the communication module 702 is further configured to: send a fourth instruction message to the device processing the second task, the fourth instruction message being used to instruct the establishment of at least one data session in the second data session group.

[0204] For example, the communication device 700 may be a first device or a component configured within the first device. The communication module 702 is configured to receive first instruction information from a management network element, the first instruction information instructing the execution of a first task through a first data session group, the first task being used to implement a portion of the processing functions of a first service; the processing module 701 is configured to determine the output data of the first task based on the first instruction information and the input data of the first task; the communication module 702 is further configured to: send the output data of the first task to a second device through the first data session; the first data session is contained within the first data session group and is an established data session between the communication device 700 and the second device.

[0205] In one possible design, when the first data session group includes at least two data sessions, the first indication information is also used to indicate the execution order of at least two data sessions in the first data session group; the communication module 702 is also used to: send a fifth indication information to the second device, the fifth indication information being used to indicate the execution order of at least two data sessions in the first data session group.

[0206] In one possible design, when the first data session group includes a data session, the second device is the device that performs the next task of the first task.

[0207] In one possible design, the first indication information includes the transmission granularity of each data session in the first data session group; the communication module 702 is specifically used to: determine the output data of the first task as the transmission granularity of the first data session through the processing module 701; and send the output data of the first task to the second device through the first data session.

[0208] In one possible design, the transmission granularity includes any of the following: service granularity, task granularity, track granularity, group granularity, subgroup granularity, and object granularity.

[0209] In one possible design, the processing module 701 is also used to: establish a first data session.

[0210] In some examples, the processing module 701 is specifically used to: establish multiple data sessions (including the first data session) before the first service is triggered. Correspondingly, the communication module 702 is also used to: send the first session registration information of the communication device 700 to the management network element, the first session registration information being used to indicate the set of data sessions established by the communication device 700, the set of data sessions established by the communication device 700 including the first data session.

[0211] In other examples, the processing module 701 is specifically used to: establish a first data session after the first service trigger request; correspondingly, the communication module 702 is also used to: receive third instruction information from the management network element before establishing the first data session, the third instruction information being used to instruct the establishment of the first data session.

[0212] The following is another structural schematic diagram of the communication device according to an embodiment of this application. For example... Figure 8 As shown, this application embodiment also provides a communication device 800, including:

[0213] At least one processor 801; and a communication interface 803 communicatively connected to the at least one processor 801; the at least one processor 801 causes the device to perform the method steps in the above method embodiments through the communication interface 803 by executing instructions stored in the memory 802.

[0214] The memory 802 may be located outside the communication device 800. Alternatively, the memory 802 may be located inside the communication device 800. Optionally, the communication device 800 includes the memory 802, which is connected to the at least one processor 801, and stores instructions executable by the at least one processor 801. (Appendix) Figure 8 The dashed line indicates that memory 802 is optional for communication device 800.

[0215] The processor 801 and the memory 802 can be coupled through an interface circuit or integrated together; no restriction is imposed here.

[0216] This application embodiment does not limit the specific connection medium between the processor 801, memory 802, and communication interface 803. This application embodiment... Figure 8 The processor 801, memory 802, and communication interface 803 are connected via a bus 804. Figure 8 The connections between other components are shown in bold and are for illustrative purposes only, not as limiting information. The bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, Figure 8The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0217] Taking a management network element as an example, when the communication device 800 is a management network element, the management network element may include a processor, a memory, and a transceiver. The memory can store computer program code, and the transceiver includes a transmitter and a receiver.

[0218] The processor is primarily used for processing communication protocols and data; controlling terminal devices; executing software programs; and processing data from those programs. The memory is primarily used for storing software programs and data. The transmitter is used to send signals to other communication devices or equipment, and the receiver is used to receive signals from other communication devices or equipment.

[0219] When the communication device 800 is a chip in a terminal device, the chip may include a processor, a memory, and a transceiver. The transceiver may be an input / output circuit or a communication interface. The processor may be a processing module integrated on the chip, a microprocessor, or an integrated circuit. In the above method embodiments, the sending operation of the terminal device can be understood as the output of the chip, and the receiving operation of the terminal device in the above method embodiments can be understood as the input of the chip.

[0220] It should be understood that the processor mentioned in the embodiments of this application can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, integrated circuit, etc. When implemented in software, the processor can be a general-purpose processor, implemented by reading software code stored in memory.

[0221] For example, the processor can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.

[0222] It should be understood that the memory mentioned in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0223] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, the memory (storage module) can be integrated into the processor.

[0224] It should be noted that the memories described herein are intended to include, but are not limited to, these and any other suitable types of memories.

[0225] Based on the same technical concept, embodiments of this application also provide a computer-readable storage medium, including a program or instructions, which, when run on a computer, cause the methods in the above method embodiments to be executed.

[0226] Based on the same technical concept, embodiments of this application also provide a computer program product, including instructions that, when run on a computer, cause the methods in the above method embodiments to be executed.

[0227] Based on the same technical concept, embodiments of this application also provide a communication system, which may include a management network element and a first device. For example, this communication system can be used to implement... Figure 3The method flow is described above. Optionally, the communication system may also include other communication devices (such as the second and third devices in the foregoing embodiments).

[0228] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0229] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0230] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0231] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0232] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions between different embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0233] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

Claims

1. A communication method, characterized in that, The method, applied to a management network element in a communication system, includes: Receive a trigger request for a first service, wherein the trigger request for the first service is used to request the execution of the first service; The first service orchestration information is determined based on the first service trigger request; the first service orchestration information is used to orchestrate multiple tasks, the multiple tasks are used to implement part of the processing function of the first service, and the multiple tasks include a first task and a second task. Based on the first service orchestration information, a first instruction message is sent to the device processing the first task, and a second instruction message is sent to the device processing the second task; wherein, the first instruction message is used to instruct the first task to be executed through a first data session group; and the second instruction message is used to instruct the second task to be executed through a second data session group.

2. The method as described in claim 1, characterized in that, When the first data session group includes at least two data sessions, the first indication information is also used to indicate the execution order of at least two data sessions in the first data session group; When the second data session group includes at least two data sessions, the second indication information is also used to indicate the execution order of at least two data sessions in the second data session group.

3. The method as described in claim 1 or 2, characterized in that, Before determining the first service orchestration information based on the first service triggering request, the method further includes: Receive multiple session registration information from multiple devices; the multiple session registration information are respectively used to indicate the set of data sessions established by each device; the multiple devices include the device performing the first task and the device performing the second task; Determining the first service orchestration information based on the first service triggering request includes: Based on the multiple session registration information and the first service triggering request, determine the first service orchestration information; The data sessions in the first data session group are included in the set of data sessions already established by the device executing the first task, and the data sessions in the second data session group are included in the set of data sessions already established by the device executing the second task.

4. The method as described in claim 3, characterized in that, The multiple session registration information respectively includes granularity information supported by each data session in the set of data sessions established by each device; the method further includes: Based on the granularity information supported by each data session and the first service triggering request, the transmission granularity of each data session is determined; The first indication information includes the transmission granularity of each data session in the first data session group.

5. The method as described in claim 4, characterized in that, The transmission granularity includes any of the following: Granularity includes mission, task, track, group, subgroup, and object.

6. The method as described in claim 1 or 2, characterized in that, The method further includes: Send a third instruction message to the device that is processing the first task, the third instruction message being used to instruct the establishment of at least one data session in the first data session group; Send a fourth instruction message to the device processing the second task, the fourth instruction message being used to instruct the establishment of at least one data session in the second data session group.

7. A communication method, characterized in that, Applied to a first device, the method includes: Receive a first instruction information from a management network element, the first instruction information being used to instruct the execution of a first task through a first data session group, the first task being used to implement part of the processing function of a first service; Based on the first instruction information and the input data of the first task, determine the output data of the first task; The output data of the first task is sent to the second device through the first data session; the first data session is included in the first data session group and the first data session is an established data session between the first device and the second device.

8. The method as described in claim 7, characterized in that, When the first data session group includes at least two data sessions, the first indication information is further used to indicate the execution order of at least two data sessions in the first data session group; the method further includes: Send a fifth instruction message to the second device, the fifth instruction message being used to indicate the execution order of at least two data sessions in the first data session group.

9. The method as described in claim 7, characterized in that, When the first data session group includes a data session, the second device is the device that processes the next task of the first task.

10. The method according to any one of claims 7-9, characterized in that, The first indication information includes the transmission granularity of each data session in the first data session group, and the step of sending the output data of the first task to the second device through the first data session includes: The output data of the first task is determined to be the transmission granularity of the first data session; The output data of the first task is sent to the second device through the first data session.

11. The method as described in claim 10, characterized in that, The transmission granularity includes any of the following: Granularity includes mission, task, track, group, subgroup, and object.

12. The method according to any one of claims 7-11, characterized in that, The method further includes: Establish the first data session with the second device.

13. The method as described in claim 12, characterized in that, The method further includes: The first session registration information of the first device is sent to the management network element. The first session registration information is used to indicate the set of data sessions that the first device has established. The set of data sessions that the first device has established includes the first data session.

14. The method as described in claim 12, characterized in that, Before establishing the first data session with the second device, the method further includes: Receive a third instruction from the management network element, the third instruction being used to instruct the establishment of the first data session.

15. A communication device, characterized in that, Includes units or modules for performing the method as described in any one of claims 1-14.

16. A communication device, characterized in that, It includes at least one processor for executing computer programs or instructions to implement the method as described in any one of claims 1-14.

17. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions, and when the computer program or instructions are executed by a communication device, the method as described in any one of claims 1-14 is implemented.

18. A computer program product, characterized in that, When the computer program product is executed by a computer, the computer performs the method as described in any one of claims 1-14.

Images