Network architecture and method for providing quality of service assurance

Abstract

The invention provides a network architecture and a method for providing service quality guarantee. The network architecture and the method for providing the service quality guarantee are beneficial for guaranteeing task-level service quality of an intelligent agent. The network architecture comprises a task function network element used for splitting a task of an intelligent agent into a plurality of sub-tasks and splitting data bearing the sub-tasks into one or more data packets; the method and the device are also used for providing QoS guarantee for one or more data packets bearing the subtasks.

Description

Technical Field

[0001] This application relates to the field of communications, and more particularly to a network architecture and a method for providing quality of service assurance. Background Technology

[0002] With the continuous development of communication technology, various intelligent agents are emerging, such as robots, self-driving cars, smart devices, artificial intelligence (AI) mobile phones, AI assistant devices, and software agents. Intelligent agent services have higher requirements for speed, latency, and reliability; future communication networks need to support lower transmission latency, more reliable communication transmission, and higher throughput.

[0003] In the application scenario of intelligent agents, the business of intelligent agents is task-level, or in other words, task-granular. Intelligent agents can perform single tasks or complex multi-step tasks. For example, the tasks of an autonomous vehicle may include environmental perception, path planning, and vehicle control.

[0004] For intelligent agent scenarios, ensuring the quality of service (QoS) at the task level is an urgent problem to be solved. Summary of the Invention

[0005] This application provides a network architecture and a method for providing quality of service assurance, which is beneficial for ensuring the task-level quality of service of intelligent agents.

[0006] In a first aspect, a network architecture is provided, which includes a task function unit for splitting the agent's task into multiple subtasks and splitting the data carrying the subtasks into one or more data packets; the task function unit is also used to provide QoS guarantees for one or more data packets of the subtasks.

[0007] Based on the existing network protocol architecture, this application defines a new task function unit for task-level services of intelligent agents, which can provide QoS guarantee for data packet transmission carrying tasks at the task granularity and support end-to-end implementation of task-level services for intelligent agents.

[0008] In conjunction with the first aspect, in some implementations of the first aspect, the task functional unit includes a first functional unit and a second functional unit. The first functional unit is used to split the agent's task into multiple subtasks and to split the data carrying the subtasks into one or more data packets; the second functional unit is used to provide QoS guarantees for one or more data packets of the subtasks.

[0009] The first functional unit can be deployed on the control plane of the core network, and the second functional unit can be deployed on the user plane of the core network.

[0010] In conjunction with the first aspect, in some implementations of the first aspect, the first functional unit is also used to: maintain and control the execution accuracy and / or task response time of the subtasks.

[0011] In conjunction with the first aspect, in some implementations of the first aspect, the QoS parameters of the data packet carrying the subtask include one or more of the following: latency, jitter, reliability, execution accuracy, or task response time.

[0012] In conjunction with the first aspect, in some implementations of the first aspect, the QoS parameter also includes: the label of the subtask and the label of the data packet carrying the subtask.

[0013] In conjunction with the first aspect, in some implementations of the first aspect, the network architecture also includes a centralized unit (CU) for interacting with the task function unit regarding the QoS parameter.

[0014] In conjunction with the first aspect, in some implementations of the first aspect, the CU includes a third functional unit for interacting with the task functional unit and the centralized unit (DU) regarding the QoS parameter.

[0015] In conjunction with the first aspect, in some implementations of the first aspect, the CU includes a CU-control plane (CU-CP) and a CU-user plane (CU-UP). The CU-CP is used to interact with the QoS parameters with the first functional unit; the CU-UP is used to interact with the QoS parameters with the second functional unit.

[0016] Secondly, a method for providing quality of service assurance is provided. This method can be executed by a communication device, which can be a task function unit, a component configured in the task function unit (such as a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the task function unit. This application does not limit the scope of this method. The method of this application is described below using a task function unit as an example.

[0017] The method includes: splitting the agent's task into multiple subtasks; splitting the data carrying the subtasks into one or more data packets; and providing QoS guarantees for one or more data packets of the subtasks.

[0018] In conjunction with the second aspect, in some implementations of the second aspect, the QoS parameters of the data packet carrying the subtask include one or more of the following: latency, jitter, reliability, execution accuracy, or task response time.

[0019] In conjunction with the second aspect, in some implementations of the second aspect, the QoS parameter also includes: the label of the subtask and the label of the data packet carrying the subtask.

[0020] It should be understood that the second aspect of this application corresponds to the technical solution of the first aspect of this application, and the beneficial effects achieved by each aspect and the corresponding feasible implementation are similar, and will not be repeated here.

[0021] Thirdly, a communication apparatus is provided, comprising: a method for performing any possible implementation of the second aspect described above. Specifically, the apparatus includes a module for performing the method in any possible implementation of the second aspect described above.

[0022] In one design, the device may include modules that perform the methods / operations / steps / actions described in the second aspect above. These modules may be hardware circuits, software, or a combination of hardware circuits and software.

[0023] In another design, the device is a communication chip, which may include input circuitry or interface for transmitting information or data, and output circuitry or interface for receiving information or data.

[0024] In another design, the device is a mission function unit, which may include a transmitter for sending information or data and a receiver for receiving information or data.

[0025] In another design, the device is used to perform the method in any possible implementation of the second aspect described above, and the device can be configured in a task function unit.

[0026] Fourthly, a communication device is provided, comprising at least one processor for calling and running a computer program from a memory, such that the device performs the method in any possible implementation of the second aspect described above.

[0027] Optionally, the device further includes a memory for storing instructions and data. The memory is coupled to the processor, which, when executing the instructions stored in the memory, can implement the method described in the second aspect above.

[0028] Optionally, the device may also include a transmitter and a receiver, which may be separate or integrated together and referred to as a transceiver.

[0029] Fifthly, a computer program product is provided, the computer program product comprising: a computer program (also referred to as code or instructions), which, when the computer program is run, causes a computer to perform the method in any possible implementation of the second aspect above.

[0030] In a sixth aspect, a computer-readable storage medium is provided that stores a computer program (also referred to as code or instructions) that, when executed on a computer, causes the computer to perform the methods in any of the possible implementations of the second aspect described above.

[0031] In a seventh aspect, this application provides a chip system including at least one processor for supporting the implementation of the functions involved in any possible implementation of the second aspect above, such as receiving or processing data involved in the above methods.

[0032] In one possible design, the chip system also includes a memory for storing program instructions and data, which may be located within or outside the processor.

[0033] Optionally, the chip system may consist of chips or may include chips and other discrete components. Attached Figure Description

[0034] Figure 1 This is a schematic diagram of a communication system applicable to embodiments of this application;

[0035] Figure 2 This is a schematic diagram of a 5G system network architecture.

[0036] Figure 3 This is a schematic diagram of a voice VMOS network architecture;

[0037] Figure 4 This is a schematic diagram of a C-V2X system;

[0038] Figure 5 This is a diagram illustrating how AI-powered mobile phones upload data.

[0039] Figure 6 This is a business process diagram of an AI intelligent assistant;

[0040] Figure 7 This is a schematic diagram of a network architecture provided in an embodiment of this application;

[0041] Figure 8 This is a schematic diagram of another network architecture provided in an embodiment of this application;

[0042] Figure 9 This is a schematic diagram of another network architecture provided in the embodiments of this application;

[0043] Figure 10 This is a schematic diagram of yet another network architecture provided in the embodiments of this application;

[0044] Figure 11 This is a schematic diagram of the network element function division and protocol layer of an O-RAN system provided in an embodiment of this application;

[0045] Figure 12 This is a schematic diagram of the network element function division and protocol layer of another O-RAN system provided in the embodiments of this application;

[0046] Figure 13 This is a schematic flowchart illustrating a method for providing quality of service assurance according to an embodiment of this application;

[0047] Figure 14 and Figure 15 This is a schematic block diagram of a communication device provided in an embodiment of this application. Detailed Implementation

[0048] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0049] Before introducing the network architecture and the method for providing quality of service assurance provided in the embodiments of this application, the following points should be made first.

[0050] First, in the embodiments shown below, the terms and English abbreviations, such as TFU, TCFU, task function unit, QoS parameters, etc., are merely exemplary examples given for ease of description and should not constitute any limitation on this application. This application does not preclude the possibility of defining other terms that can achieve the same or similar functions in existing or future agreements.

[0051] Second, in the embodiments shown below, the first, second, and various numerical designations are merely distinctions for ease of description and are not intended to limit the scope of the embodiments of this application.

[0052] Third, "at least one" means one or more, while "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, and c can mean: a, or b, or c, or a and b, or a and c, or b and c, or a, b, and c, where a, b, and c can be single or multiple.

[0053] Figure 1 This is a schematic diagram of a communication system applicable to embodiments of this application. Figure 1 The communication system 1000 shown includes a radio access network (RAN) 100 and a core network (CN) 200. Optionally, the communication system 1000 also includes an Internet 300. The radio access network 100 may include at least one RAN node (e.g., Figure 1 110a and 110b in the above), may also include at least one terminal (such as Figure 1 (Referring to 120a-120j in the original text). Terminals connect wirelessly to the RAN nodes, and the RAN nodes connect wirelessly or via wired connection to the core network 200. Core network equipment and RAN nodes can be independent physical devices, or the functions of the core network equipment and the logical functions of the RAN nodes can be integrated into the same physical device. Alternatively, a single physical device can integrate some core network equipment functions and some RAN node functions. Terminals and RAN nodes can be interconnected via wired or wireless connections. Figure 1 This is just an illustration; the communication system may also include other RAN nodes, such as wireless relay equipment and wireless backhaul equipment. Figure 1 Not shown in the image.

[0054] The wireless access network 100 can be a cellular system related to the 3rd generation partnership project (3GPP), such as the 4th generation mobile communication technology (4G) system (also known as the long term evolution (LTE) system), the 5th generation mobile communication technology (5G) system (also known as the new radio (NR) system), or it can be applied to future communication systems or other similar communication systems, etc., and this application does not limit it in this regard.

[0055] The wireless access network 100 can also be an open RAN (open-RAN, O-RAN, or ORAN) or a cloud radio access network (CRAN). The wireless access network 100 can also be a non-terrestrial network (NTN), a satellite communication network, a high altitude platform station (HAPS) communication network, an integrated access and backhaul (IAB) communication network, a reconfigurable intelligent surface (RIS) communication network, etc. The wireless access network 100 can also be a communication system that integrates two or more of the above systems.

[0056] RAN nodes, also known as RAN devices or access network devices, are used to help terminals achieve wireless access. Multiple RAN nodes in the communication system 1000 can be of the same type or different types.

[0057] The RAN node provided in this application can be a base station, a Node B, an evolved Node B (eNodeB or eNB), a transmission reception point (TRP), a next-generation Node B (gNB) in 5G or NR, a RAN node in an open radio access network (O-RAN or open RAN), or a next-generation base station in 6th-generation mobile communication technology (6G). Alternatively, the RAN node can also be a satellite base station in a non-terrestrial network (NTN) communication network, a base station in a future mobile communication system, or an access node in a wireless fidelity (Wi-Fi) system. Alternatively, the RAN node can also be a module or unit that performs some of the functions of a base station, such as a CU or DU. The functions of the CU can be implemented by one entity or by different entities. For example, the functions of the CU can be further divided, such as separating the control plane and the user plane, i.e., the control plane (CU-CP) and the user plane (CU-UP) of the CU. RAN nodes can be macro base stations, micro base stations, indoor stations, relay nodes, or host nodes, etc. This application does not limit the specific technologies or equipment forms used in the RAN nodes.

[0058] A terminal is a device with wireless transceiver capabilities, capable of sending signals to or receiving signals from RAN nodes. Terminals can also be called terminal devices, terminal equipment, user equipment (UE), mobile stations, mobile terminals, etc. Terminals can be widely used in various scenarios, such as enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine-type communications (mMTC), device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), the Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, intelligent transportation, and smart cities. Specifically, terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, 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.

[0059] RAN nodes and terminals can be fixed or mobile. RAN nodes and terminals can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can be deployed on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of RAN nodes and terminals.

[0060] The roles of RAN nodes and terminals can be relative. For example, Figure 1 The helicopter or drone 120i can be configured as a mobile RAN node. For terminals 120j accessing the wireless access network 100 via 120i, terminal 120i is a RAN node; however, for RAN node 110a, 120i is a terminal, meaning that 110a and 120i communicate via a radio interface protocol. Alternatively, 110a and 120i can also communicate via a RAN node-to-RAN node interface protocol; in this case, 120i is also a RAN node relative to 110a. Therefore, both RAN nodes and terminals can be collectively referred to as communication devices. Figure 1 110a and 110b can be referred to as communication devices with RAN node functions. Figure 1The 120a-120j in the text can be referred to as communication devices with terminal functions.

[0061] Communication between RAN nodes and terminals, between RAN nodes, and between terminals can be conducted using licensed spectrum, unlicensed spectrum, or both simultaneously. Communication can also be conducted using spectrum below 6 gigahertz (GHz), spectrum above 6 GHz, or both simultaneously. The embodiments of this application do not limit the spectrum resources used for wireless communication.

[0062] In the embodiments of this application, the functions of the RAN node can be executed by modules (such as chips) within the RAN node, or by a control subsystem that includes RAN node functions. This control subsystem, including RAN node functions, can be a control center in the aforementioned application scenarios such as smart grids, industrial control, intelligent transportation, and smart cities. Similarly, the functions of the terminal can be executed by modules (such as chips or modems) within the terminal, or by a device that includes terminal functions.

[0063] Core network equipment refers to the equipment in the core network that provides service support to terminals. Examples of some core network equipment include: access and mobility management function (AMF) network elements, session management function (SMF) network elements, user plane function (UPF) network elements, etc., which will not be listed here.

[0064] The relevant technologies and concepts involved in this application are introduced below.

[0065] 1. Core network (CN) protocol architecture of 5G system

[0066] To address the challenges of wireless broadband technology and maintain the leading advantage of 3GPP networks, the 3GPP standards group formulated the Next Generation System (NGS) architecture, known as the 5G network architecture, at the end of 2016. This architecture not only supports wireless technologies defined by the 3GPP standards group (e.g., LTE, NR) to access the core network, but also supports non-3GPP access technologies to access the core network through non-3GPP interworking functions (N3IWF) or next-generation packet data gateways (ngPDG). The core network functions are divided into user plane network element functions (e.g., UPF) and control plane network element functions. User plane network element functions are mainly responsible for packet forwarding, QoS control, and billing information statistics. Control plane network element functions are mainly responsible for user registration and authentication, mobility management, and issuing packet forwarding policies and QoS control policies to the user plane.

[0067] See Figure 2 The 5G network architecture shown includes the following network functions and entities: UE, RAN, UPF, AMF, SMF, and data network (DN). It should be noted that in some embodiments, additional components may be included. Figure 2 The number of network functions and entities shown is not limited herein. For example, the network architecture may optionally include unified data management (UDM), network exposure function (NEF), policy control function (PCF), network repository function (NRF), network slice selection function (NSSF), authentication server function (AUSF), and network data analytics function (NWDAF).

[0068] The names of the network functions and entities shown in this application are exemplary examples given for ease of description and should not be construed as limiting the scope of this application. This application does not preclude the possibility of defining other terms that can achieve the same or similar functions in existing or future agreements.

[0069] Figure 2In the core network, UE, RAN, UPF, and DN are typically referred to as user plane (or data plane) network functions and entities. User data traffic is transmitted through Protocol Data Unit (PDU) sessions established between the UE and DN. This transmission passes through the RAN node and the UPF, which can be considered a user plane network element in the core network. Other network elements are called control plane network functions and entities (or control plane network elements), primarily responsible for authentication and authorization, registration management, session management, mobility management, and policy control, thereby ensuring reliable and stable transmission of user layer traffic. The user plane carries service data, while the control plane carries signaling messages.

[0070] Figure 2 The diagram illustrates the interaction relationships between network functions and entities, as well as their corresponding interfaces. For example, the UE and AMF can interact via the N1 interface, and the interaction messages are called N1 messages. Some interfaces are implemented using a service-oriented approach.

[0071] AMF (Access Management Function) is a network element, module, or component that provides access management functions. It is mainly responsible for signaling processing, such as access control, mobility management, attach and detach, and gateway selection. When an AMF network element provides services to a session in a terminal, it provides control plane storage resources for that session to store the session identifier and the identifier of the SMF associated with the session identifier.

[0072] SMF is a network element, module, or component responsible for handling user services, such as user plane function selection, user plane function redirection, Internet Protocol (IP) address allocation, bearer establishment, modification, and release, and QoS control.

[0073] The UPF is responsible for forwarding and receiving user data in the terminal. The UPF can receive user data from the DN and transmit it to the UE through the RAN node; the UPF can also receive user data from the UE through the RAN node and forward it to the DN. The transmission resources and scheduling functions that provide services to the UE in the UPF are managed and controlled by the SMF network element.

[0074] AUSF is responsible for authenticating user equipment and determining its legitimacy.

[0075] UDM is used to store subscription data for user equipment.

[0076] PCF is used to send business-related policies to AMF or SMF.

[0077] AF is used to send application-related requirements to PCF, so that PCF can generate corresponding policies.

[0078] DN is used to provide services to users, such as providing mobile operator services, internet services, or third-party services.

[0079] 2. LTE Voice Over LTE (VoLTE) Network Protocol Architecture

[0080] See Figure 3 The VoLTE network protocol architecture shown has a core network divided into two parts: the evolved packet core (EPC) and the IP multimedia subsystem (IMS). The EPC is used to process data services in 4G mobile voice services, providing a channel from the terminal to the packet data network gateway (PGW) for voice-related signaling and media.

[0081] EPC-side network elements include, but are not limited to: mobility management entity (MME), serving gateway (SGW) or PGW, and policy and charging rule function (PCRF).

[0082] SGW and PGW typically share the same physical entity and are functionally similar to a media gateway (MGW). SGW is used to aggregate traffic transmitted from the base station. PGW is used to interface with IMS (e.g., with the IMS application server). After the terminal sends voice-related information to the PGW, the PGW then forwards the voice-related information to the IMS. SGW is an interface for EPC to connect to IMS (signaling / media sent to IMS must pass through the PGW).

[0083] PCRF is used in conjunction with SGW / PGW to establish a channel between the terminal and the PGW. As mentioned earlier, the network elements of EPC are used to process data services, and voice services also pass through the data service channel. PCRF is used to ensure that this channel meets the requirements of voice services and to control parameters such as jitter, latency, and packet loss rate of the channel from the terminal to the PGW.

[0084] Network elements on the IMS side include, but are not limited to: Home Subscriber Service (HSS), Application Service (AS), Call Session Control Function (CSCF), and Session Border Controller (SBC).

[0085] The HSS functions similarly to the Home Location Register (HLR), storing user information and locating called parties. The AS provides voice services such as caller ID and call forwarding. The CSCF functions similarly to the Mobile Switching Center Server (MSC-server), triggering voice services from the AS and locating called parties from the HSS. The SBC isolates network elements between the access network and the IMS core network (signaling and media must pass through the SBC), serving as an entry point for the PGW to access IMS.

[0086] 3. Cellular vehicle to everything (C-V2X)

[0087] C-V2X is a V2X communication technology developed based on cellular systems. It utilizes and enhances the functions and elements of current cellular networks to achieve low-latency and high-reliability communication between various nodes in the vehicle network. For example... Figure 4 As shown, C-V2X includes vehicle-to-vehicle (V2V) communication, vehicle-to-pedestrian (V2P) communication, vehicle-to-infrastructure (V2I) communication, and vehicle-to-network (V2N) communication.

[0088] As cellular systems evolve from 4G (LTE) to 5G (NR), C-V2X is evolving from LTE-V2X to NR-V2X glasses. NR-V2X can support lower transmission latency, more reliable communication, higher throughput, and a better user experience, meeting the needs of a wider range of application scenarios. Furthermore, the vehicle-to-vehicle communication technology supported by V2X can be extended to D2D in mission systems.

[0089] Currently, mobile phones equipped with large-scale AI models (such as AI phones) are gaining increasing market favor. Many terminal manufacturers have launched mobile phones with large-scale AI models as their main feature, which can support functions such as generative AI (AI-generated content, AIGC) image assistant, generative editing, real-time call translation, health assistant, and instant photo taking.

[0090] Figure 5 This is a diagram illustrating how AI-powered mobile phones upload data. (See also...) Figure 5 The AI ​​phone is estimated to upload 1 gigabyte (GB) of training data to the cloud each month. This training data includes, but is not limited to, status information, system data, image data, and video data. The cloud can then perform inference based on the training data uploaded by the AI ​​phone and send relevant feedback to the AI ​​phone, such as rendered images and videos.

[0091] Figure 6 This is a business process diagram for an AI-powered intelligent assistant. (See also...) Figure 6 The terminal (such as an AI-powered mobile phone) has a microphone and / or camera, which can collect voice data, image data, video data, etc., and interact with the cloud with text, speech, images, and videos. The cloud includes a large AI model platform, which can recognize and process text, speech, images, and videos.

[0092] As we can see, for many intelligent agent services in the future (such as robots, autonomous vehicles, smart devices, AI phones, AI assistant devices, and software agents), such as vehicle networking services, in-vehicle entertainment services, and uplink services of AI phones, intelligent agent services have higher requirements for speed, latency, and reliability. Future communication networks need to support lower transmission latency, more reliable communication transmission, and higher throughput.

[0093] In the application scenario of intelligent agents, the business of intelligent agents is task-level, or in other words, task-granular, and can be called task-level business. Intelligent agents can perform some single tasks or complex multi-step tasks. For example, the tasks of an autonomous vehicle may include environmental perception, path planning, vehicle control, etc.

[0094] The network architecture described above is designed for packet and voice services. This architecture definition does not support service guarantees for task-level data packets in agent scenarios. Therefore, ensuring task-level QoS is a critical issue that needs to be addressed in agent-based scenarios.

[0095] In view of this, embodiments of this application provide a network architecture that can be seen as an improvement on the existing 5G network architecture. Specifically, a task function unit (TFU) is added to the existing 5G network architecture, which can guarantee the QoS of task-level services of the intelligent agent and support end-to-end implementation of task-level services for the intelligent agent.

[0096] Figure 7 This is a schematic diagram of a network architecture provided in an embodiment of this application. See also... Figure 7 The network architecture includes TFUs, which reside in the control plane of the core network. TFUs are used to: break down an agent's task into multiple subtasks, and to break down the data carrying the subtasks into one or more data packets. TFUs are also used to: provide QoS guarantees for one or more data packets of a subtask. If the task does not need to be broken down, the TFU is used to provide QoS guarantees for one or more data packets of the agent's task.

[0097] It should be understood that the business of an intelligent agent is at the task level, and is called task-level business.

[0098] The tasks performed by an agent can be specific tasks or a series of tasks, ranging from simple single tasks to complex multi-step tasks. For a single task, TFU does not require breaking it down. Agents typically require network resources to perform tasks, including data transmission resource allocation and computing resources.

[0099] For example, the tasks of an intelligent agent can include, but are not limited to, the following types:

[0100] 1. Data processing tasks: such as image recognition, speech recognition, natural language processing, etc.

[0101] 2. Control tasks: For example, robot control, autonomous driving control, drone flight control, etc.

[0102] 3. Communication tasks: such as data packet transmission, information exchange, real-time communication, etc.

[0103] 4. Decision-making tasks: such as path planning, strategy selection, and dynamic adjustment.

[0104] Robot control includes, for example, controlling robots to perform public service tasks such as traffic management, environmental monitoring, and rescue missions, or controlling robots to perform service tasks such as food delivery, luggage handling, and room cleaning. Robots can also perform many other tasks, which will not be listed here.

[0105] The following example illustrates the breakdown of a complex task.

[0106] In one example, the agent is a robot whose task is a rescue mission, which can be broken down into:

[0107] Subtask 1: Environmental perception, such as acquiring data about the surrounding environment through cameras and sensors.

[0108] Subtask 2: Personnel search and rescue, such as real-time processing of environmental data to identify personnel.

[0109] Subtask 3: Mark locations, such as marking and recording the locations of people and hazardous areas found.

[0110] Furthermore, TFU can split the data carrying subtasks into one or more data packets. Each subtask can be a single task consisting of a single data packet or a single task consisting of multiple data packets, depending on the size of the subtask's data.

[0111] For example, subtask 1 is a task consisting of a single data packet, while subtask 2 is a task consisting of the joint transmission of multiple data packets.

[0112] Alternatively, for a simple task, there is no need to split it up. The single task can be a task consisting of a single data packet or a task consisting of multiple data packets transmitted together.

[0113] Each data packet carrying a subtask has its corresponding tag. For example, for a single task, its tag is "0". Then, one or more data packets carrying the tag of that task can identify that the one or more data packets belong to the same task. TFU can provide the same QoS guarantee for the one or more data packets. When the agent executes the next task, its tag flips to "1", and when the agent executes the next task again, its tag flips to "0".

[0114] For example, if a complex task is broken down into two subtasks, with the complex task labeled "0", subtask 1 labeled "0", and subtask 2 labeled "1", then one or more data packets for each subtask carry the label of the complex task and the label of the subtask. For example, the data packets for subtask 1 carry the task label "00", and the data packets for subtask 2 carry the label "01". TFU can provide the same QoS guarantee for different subtasks, or the QoS guarantee for different subtasks can be different; this application does not limit this.

[0115] Optionally, the data packets carrying the task or subtask may also carry tagging information such as the sequence number of the data packets and the total number of data packets.

[0116] Optionally, Figure 7The network architecture shown also includes an AF corresponding to the TFU, used for TFU to connect to network-side application services.

[0117] In combination with the above Figure 7 This application adds a TFU to the existing network architecture, and provides QoS guarantee for the data packet transmission of the agent's task-level services through the IP bearer network, supporting end-to-end implementation of the agent's task-level services.

[0118] In another embodiment, the TFU described above can be split into two different functional units, each responsible for a different function.

[0119] Figure 8 This is a schematic diagram of another network architecture provided in an embodiment of this application. See also... Figure 8 The task function unit includes a first function unit and a second function unit. The first function unit is used to split the agent's task into multiple sub-tasks and to split the data carrying the sub-tasks into one or more data packets. The second function unit is used to provide QoS guarantees for one or more data packets of the sub-tasks.

[0120] The first functional unit can be called the Task Control Function Unit (TCFU), and the second functional unit can be called the TFU. It should be understood that... Figure 8 The TFU shown Figure 7 The TFUs shown are different. Figure 8 The TFU shown has Figure 7 The TFU shown contains some of its functions.

[0121] The following is about Figure 8 This section introduces TCFU and TFU.

[0122] A TCFU can be located in the control plane of the core network; for example, a TCFU is a logical functional unit of an AMF. A TFU can be located in the user plane of the core network; for example, a TFU is a logical functional unit of a UPF.

[0123] Optionally, TCFU also includes a new definition of management functions for the agent's task execution, such as maintaining and controlling the execution accuracy and / or response time of the agent's subtasks.

[0124] TFU is used to provide QoS guarantees for one or more packets carrying a task or subtask, wherein the QoS parameters of the packets carrying the task or subtask include one or more of the following: latency, jitter, reliability, execution accuracy, or task response time.

[0125] For example, TFU specifies a latency of 100ms from the agent to the cloud. In other words, for a task or subtask of an agent, the maximum transmission latency from the agent to the cloud is 100ms.

[0126] Optionally, QoS parameters may also include: the label of the task or subtask and the label of the data packet carrying the task or subtask. For example, the labels of multiple data packets in the TFU-RAN CU interaction subtask indicate that the same QoS guarantee is required for these multiple data packets.

[0127] It should be understood that the QoS parameters described in the embodiments of this application are task-level QoS parameters, used to ensure the quality of service for the transmission of data packets carrying tasks or subtasks.

[0128] As one implementation method, the above Figure 7 or Figure 8 The RAN in the network architecture shown can be a centralized RAN, including CU, and TFU can interact with CU to exchange QoS parameters.

[0129] Optionally, the CU includes a third functional unit, such as CU-t. See also Figure 9 The TFU interacts with the CU to exchange QoS parameters, including the TFU interacting with the CU-t to exchange QoS parameters. It should be understood that CU-t is an optional functional unit in the CU, and the embodiments of this application do not limit whether the CU includes CU-t.

[0130] As another implementation method, the above Figure 7 or Figure 8 The RAN in the illustrated network architecture can be an O-RAN, including CU and DU. The CU is used to interact with TFU and DU for QoS parameters. The CU includes CU-UP and CU-CP. See also Figure 10 The CU-CP interacts with the CU-UP to exchange QoS parameters. Optionally, the CU also includes CU-t, which is used to interact with the TFU to exchange QoS parameters.

[0131] CU and DU are deployed with different protocol layers. See also Figure 11As one implementation, the CU deploys the Radio Resource Control (RRC) layer, Packet Data Convergence Protocol (PDCP) layer, and Service Data Adaptation Protocol (SDAP) layer in the protocol stack. The DU deploys the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and Physical Layer (PHY) layer in the protocol stack. The Physical Layer can be further divided into PHY-high and PHY-low layers. Thus, the CU has the processing capabilities of RRC, PDCP, and SDAP, while the DU has the processing capabilities of RLC, MAC, and PHY.

[0132] Depend on Figure 11 It is known that CU and DU are deployed with different protocol layers. In order to maintain data transmission between layers, TFU can interact with CU to obtain the QoS parameters of the task-level services of the intelligent agent, and with CU to interact with DU to obtain the QoS parameters of the task-level services of the intelligent agent.

[0133] In the case of CU separation (i.e., splitting into CU-CP and CU-UP), see [link / reference]. Figure 12 As one implementation, CU-CP deploys the control plane portion of the RRC and PDCP layers (referred to as PDCP-C), CU-UP deploys the user plane portion of the SDAP and PDCP layers (referred to as PDCP-U), and DU deploys the RLC, MAC, and PHY layers. CU-CP can interact with network elements in the core network used to implement control plane functions. These network elements can be access and mobility function network elements, such as the AMF network element in a 5G system. CU-UP can also interact with network elements in the core network used to implement user plane functions. These network elements can be, for example, the UPF network element in a 5G system.

[0134] Depend on Figure 12 It is known that CU-CP, CU-UP, and DU are deployed with different protocol layers. In order to maintain data transmission between layers, the functions of CU-CP and CU-UP are enhanced to indicate the QoS parameters of task-level services interacting between CU-CP and CU-UP. TFU can interact with CU to obtain the QoS parameters of task-level services of intelligent agents, and CU can interact with DU to obtain the QoS parameters of task-level services of intelligent agents.

[0135] The aforementioned interactive QoS parameters include, for example: the label of the interactive task or the label of the subtask, the label of the data packet carrying the subtask, the QoS flow requirements of a single data packet constituting a single task (including latency, jitter, reliability, etc.), and the QoS requirements of a single task constituting multiple data packets.

[0136] In summary, the embodiments of this application provide a method for ensuring service quality. Figure 13 This is a schematic diagram of a method 1300 for providing quality of service assurance according to an embodiment of this application. The method can be implemented by a task functional unit (e.g., Figure 7 The TFU shown is executed. Method 1300 includes S1301 and S1302, and the specific steps are as follows:

[0137] S1301, the agent's task is split into multiple subtasks, and the data carrying the subtasks is split into one or more data packets.

[0138] For example, an intelligent agent initiates a request for a task-level business, such as a request for an image recognition task or a request for an intelligent driving control task.

[0139] After receiving the request, the task function unit can split the task into multiple subtasks. This is beneficial for breaking down complex tasks into simpler subtasks, which is conducive to task implementation.

[0140] The target of the request can be the cloud (server). After receiving the request, the cloud (server) generates response data and sends it to the task function unit. The task function unit divides the response data into subtasks, obtaining one or more data packets corresponding to each subtask.

[0141] S1302 provides QoS guarantees for one or more packets of a subtask.

[0142] The task function unit provides QoS guarantees for one or more data packets for each subtask to meet the QoS requirements of the data packet transmission carrying the subtask. For example, it allocates appropriate radio resources, configures corresponding QoS levels, priorities, and bandwidths for the agent's task-level services.

[0143] During the task-level operation of the agent, the task functional unit can dynamically adjust QoS parameters based on real-time network conditions and service requirements. For example, when the network is congested, the QoS level of some low-priority services can be appropriately reduced, while the QoS level of the agent's task-level services can be increased to ensure the QoS of the agent's task-level services.

[0144] It is understood that, in order to achieve the functions in the above embodiments, the task function unit includes the corresponding hardware structure and / or software module for executing each function. Those skilled in the art should readily recognize that, based on the units and method steps described in conjunction with the embodiments disclosed in this application, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0145] Figure 14 and Figure 15 This is a schematic block diagram of a communication device provided in an embodiment of this application. These communication devices can be used to implement the functions of the task functional units in the above method embodiments, and therefore can also achieve the beneficial effects of the above method embodiments.

[0146] like Figure 14 As shown, device 1400 includes a processing module 1410. Optionally, device 1400 also includes a transceiver module 1420. The transceiver module 1420 may also be referred to as a communication interface or a communication module.

[0147] The device 1400 can be used to perform the actions performed by the task function unit in the above method embodiments. Alternatively, the device 1400 can be a component (e.g., a chip) configured in the task function unit. The processing module 1410 is used to perform processing-related operations of the task function unit in the above method embodiments. The transceiver module 1420 is used to perform receiving and sending-related operations of the task function unit in the above method embodiments.

[0148] Optionally, the transceiver module 1420 may include a sending module and 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.

[0149] It should be noted that device 1400 may include a transmitting module but not a receiving module. Alternatively, device 1400 may include a receiving module but not a transmitting module. Specifically, it depends on whether the above-described scheme executed by device 1400 includes both transmitting and receiving actions.

[0150] Optionally, the device 1400 is used to perform the above. Figure 13 In the illustrated embodiments, the actions performed by the task function units include, for example, the processing module 1410 being used to: split the agent's task into multiple sub-tasks, and to split the data carrying the sub-tasks into one or more data packets. For example, the transceiver module 1420 is used to: send QoS parameters to the CU. For details, please refer to the relevant descriptions in the above embodiments; they will not be repeated here.

[0151] Optionally, the device 1400 may further include a storage module, which can be used to store data and / or to store computer programs or instructions. The processing module 1410 can read the computer programs / instructions and / or data in the storage module so that the device 1400 can implement the above-described method embodiments.

[0152] Figure 15 This is a schematic block diagram of another communication device 1500 provided in the embodiments of this application, such as... Figure 15 As shown, device 1500 includes one or more processors 1510 and interface circuitry 1520. The one or more processors 1510 and interface circuitry 1520 are coupled to each other. It is understood that interface circuitry 1520 can be a transceiver or an input / output interface. Optionally, device 1500 may also include memory 1530 for storing instructions executed by processor 1510, or for storing input data required by processor 1510 to execute instructions, or for storing data generated after processor 1510 executes instructions. Sometimes, interface circuitry 1520 can also be understood as part of the one or more processors 1510, in which case device 1500 includes the one or more processors 1510.

[0153] The one or more processors 1510 and memory 1530 can be configured separately or integrated, and this application does not limit this.

[0154] When device 1500 is used to achieve Figure 13 In the method shown, the one or more processors 1510 are used to implement the functions of the processing module 1410, and the interface circuit 1520 is used to implement the functions of the transceiver module 1420.

[0155] When the aforementioned device 1500 is a chip applied to a task function unit, the chip of the task function unit implements the functions of the task function unit in the above method embodiments. The chip of the task function unit receives information from the intelligent agent, which can be understood as the information being first received by other modules (such as a radio frequency module or antenna) in the task function unit, and then sent to the chip of the task function unit by these modules. The terminal chip sends information to the intelligent agent, which can be understood as the information being first sent to other modules (such as a radio frequency module or antenna) in the task function unit, and then sent to the intelligent agent by these modules.

[0156] This application also provides a computer-readable storage medium for storing a computer program that, when run on a computer, causes the computer to perform the methods described in the above embodiments. Alternatively, the computer program includes instructions for implementing the methods described in the above embodiments.

[0157] This application also provides a computer program product, including: a computer program or instructions that, when run on a computer, cause the computer to perform the methods described above.

[0158] This application also provides a chip, which includes at least one processor for supporting the implementation of the methods in the above embodiments, such as receiving or processing data involved in the methods in the above embodiments.

[0159] It should be understood that, in the embodiments of this application, the processor may be a central processing unit (CPU), or it may be 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. The general-purpose processor may be a microprocessor or any conventional processor.

[0160] In implementation, each step of the above method can be completed by integrated logic circuits in the processor's hardware or by instructions in software. The steps of the method disclosed in the embodiments of this application can be directly manifested as execution by a hardware processor, or as a combination of hardware and software modules within the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor executes the instructions in the memory, combining them with its hardware to complete the steps of the above method. To avoid repetition, detailed descriptions are omitted here.

[0161] Those skilled in the art will recognize that the modules and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0162] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and modules described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0163] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or modules may be electrical, mechanical, or other forms.

[0164] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0165] In addition, the functional modules in the various embodiments of this application can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module.

[0166] If the aforementioned functions are implemented as software functional modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0167] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A network architecture, characterized by The task function unit comprises a first function unit and a second function unit. The first function unit is configured to split the task of the agent into a plurality of sub-tasks, and split data carrying the sub-tasks into one or more data packets. The second function unit is configured to provide quality of service (QoS) guarantee for the one or more data packets carrying the sub-tasks.

2. The network architecture of claim 1, wherein, The task function unit comprises a first function unit and a second function unit. The first function unit is configured to split the task of the agent into a plurality of sub-tasks, and split data carrying the sub-tasks into one or more data packets. The second function unit is configured to provide quality of service (QoS) guarantee for the one or more data packets carrying the sub-tasks.

3. The network architecture of claim 2, wherein, The first function unit is further configured to: maintain and control the execution accuracy and / or task response time of the sub-tasks.

4. The network architecture of claim 3, wherein, The QoS parameters of the data packets carrying the sub-tasks comprise one or more of: latency, jitter, reliability, execution accuracy, or task response time.

5. The network architecture of claim 4, wherein, The QoS parameters further comprise: a label of the sub-tasks and a label of the data packets carrying the sub-tasks.

6. The network architecture of claim 5, wherein, The network architecture further comprises a centralized unit (CU). The CU is configured to interact with the task function unit on the QoS parameters.

7. The network architecture of claim 6, wherein, The CU comprises a third function unit. The third function unit is configured to interact with the task function unit and a distributed unit (DU) on the QoS parameters.

8. The network architecture of claim 7, wherein, The CU comprises a CU-control plane (CU-CP) and a CU-user plane (CU-UP). The CU-CP is configured to interact with the first function unit on the QoS parameters. The CU-UP is configured to interact with the second function unit on the QoS parameters.

9. A method for providing quality of service guarantees, characterized by, The method applied to a network architecture comprising a task function unit, the method comprising: splitting a task of an agent into a plurality of sub-tasks, and splitting data carrying the sub-tasks into one or more data packets; providing quality of service (QoS) guarantee for the one or more data packets carrying the sub-tasks.

10. A communications device, characterized by The computer program product comprises a computer program or instructions.

11. A communications device, characterized by The computer program product comprises a computer program or instructions.

12. A computer-readable storage medium, characterized in that, The computer program product comprises a computer program or instructions.

13. A computer program product, characterised in that, The computer program product comprises a computer program or instructions. The computer program product comprises a computer program or instructions.

Images