A method and device for implementing computing services

Abstract

The embodiment of the present application provides a method and device for implementing a computing service, the method comprising: a first wireless access network RAN ​​device obtains computing capability information of a first communication device; the first RAN device sends a first request to the first communication device, the first request is used to request the first communication device to perform the computing service of the first RAN device; the first RAN device receives a first response from the first communication device, the first response is used to indicate the computing service of the first RAN device accepted by the first communication device; and the first RAN device exchanges data of the computing service of the first RAN device accepted by the first communication device with the first communication device. Through the method and device, the first RAN device uses the first communication device to perform its computing service, and effectively utilizes network resources.

Description

Technical Field

[0001] The present invention relates to the field of wireless communications, and in particular to a method and device for computing services. Background Art

[0002] With the rapid development of wireless communication technology, the fifth generation (5G) wireless communication technology has become a hot topic in the industry. 5G will support a variety of application requirements, including access capabilities that support higher speed experience and larger bandwidth, lower latency and highly reliable information interaction, and access and management of larger-scale and low-cost machine-type communication devices. The access of massive terminals, the carrying of services with differentiated quality of service (QoS) requirements, the management of ultra-large bandwidth, and the deployment of multiple antennas make the processing complexity of radio access network (RAN) equipment extremely high. RAN equipment needs to dynamically perform self-optimization according to the rapidly changing network status to ensure network performance and user experience. The computing resources required for self-optimization of RAN equipment are very expensive. How to effectively use network resources to achieve the self-optimization requirements of RAN equipment is a problem that needs to be solved urgently. Summary of the invention

[0003] The embodiment of the present application provides a method for implementing a computing service, which can effectively utilize network resources to achieve self-optimization of RAN equipment.

[0004] The present application is introduced from multiple aspects below. It is easy to understand that the implementation methods of the following multiple aspects can refer to each other.

[0005] In a first aspect, the present application provides a method for implementing a computing service, including: a first radio access network RAN ​​device obtains computing capability information of a first communication device; the first RAN device sends a first request to the first communication device, the first request being used to request the first communication device to perform the computing service of the first RAN device; the first RAN device receives a first response from the first communication device, the first response being used to indicate the computing service of the first RAN device accepted by the first communication device; and the first RAN device exchanges data of the computing service of the first RAN device accepted by the first communication device with the first communication device.

[0006] It can be seen that the method provided in the embodiment of the present application enables the first RAN device to use the first communication device to implement the computing service of the first RAN device, thereby solving the problem that the first RAN device itself cannot complete the computing service.

[0007] In a possible implementation manner, the computing capability information of the first communication device includes the type of computing services supported by the first communication device and available resource information.

[0008] In a possible implementation manner, the computing capability information of the first communication device includes a service support list and an available resource list.

[0009] In a possible implementation manner, the computing capability information of the first communication device further includes at least one of the following parameters: service area, service continuity support, availability schedule, and availability reporting period.

[0010] In a possible implementation manner, the first request includes a quality of service (QoS) requirement of a computing service of the first RAN device; and the first response includes at least one computing service flow of the first RAN device accepted by the first communication device.

[0011] In a possible implementation, the first request includes a requested computing service flow list and a corresponding requested resource list.

[0012] In a possible implementation manner, the first request includes at least one requested computing service flow and resource information required by each service flow in the at least one computing service flow.

[0013] In a possible implementation, the first request further includes a service continuity guarantee indication, a requested key performance indicator, and transport layer information.

[0014] In a possible implementation, the first RAN device obtains computing capability information of the first communication device, including: the first RAN device sends a second request to the first communication device, the second request is used to request to obtain the computing capability information of the first communication device, and the first RAN device receives the computing capability information of the first communication device from the first communication device; or, the first RAN device sends a second request to the second communication device, the second request is used to request to obtain the computing capability information of the first communication device, and the first RAN device receives the computing capability information of the first communication device from the second communication device.

[0015] It can be seen that the first RAN device, by requesting to obtain the computing capability information of the first communication device, helps the first RAN device determine whether the first communication device can provide computing services for it.

[0016] In a possible implementation manner, the first RAN device obtains the computing capability information of the first communication device, including: the first RAN device receives the computing capability information of the first communication device from the first communication device, and the first RAN device sends confirmation information to the first communication device, where the confirmation information is used to indicate that the first RAN device correctly receives the computing capability information of the first communication device; or, the first RAN device receives the computing capability information of the first communication device from the second communication device, and the first RAN device sends confirmation information to the second communication device, where the confirmation information is used to indicate that the first RAN device correctly receives the computing capability information of the first communication device.

[0017] It can be seen that the first RAN device directly obtains the computing capability information of the first communication device, which helps the first RAN device determine whether the first communication device can provide computing services for it.

[0018] In a possible implementation manner, the first communication device is a second RAN device, and the second communication device is a core network CN device; or, the first communication device is a terminal device, and the second communication device is the second RAN device or the CN device.

[0019] In a possible implementation manner, the first RAN device sends a first request to the first communication device, including: when the first communication device is the second RAN device or the terminal device, the first RAN device determines that the first communication device is a target communication device according to the computing capability information of the first communication device, and the first RAN device sends the first request to the target communication device; or, when the first communication device is the second RAN device and the second communication device is the CN device, the first RAN device determines that the first communication device is a target communication device according to the computing capability information of the first communication device, and the first RAN device sends the first request to the target communication device through the second communication device.

[0020] In a second aspect, the present application provides a method for implementing a computing service, including: a first communication device receives a first request from a second communication device, the first request being used to request the first communication device to perform a computing service of a first RAN device; the first communication device sends a first response to the second communication device, the first response being used to indicate the computing service of the first RAN device accepted by the first communication device; and the first communication device interacts with the first RAN device to exchange data on the computing service of the first RAN device accepted by the first communication device.

[0021] It can be seen that the method provided in the embodiment of the present application enables the first communication device to provide computing services for the first RAN device, thereby solving the problem that the first RAN device itself cannot complete the computing service.

[0022] In a possible implementation, before the first communication device receives the first request from the second communication device, the method further includes: the first communication device generates computing capability information of the first communication device; and the first communication device sends the computing capability information of the first communication device to the second communication device.

[0023] It can be seen that the first communication device sends its computing capability information in response to the request, which helps the first RAN device determine whether the first communication device can provide computing services for it.

[0024] In a possible implementation manner, the first request includes a quality of service (QoS) requirement of a computing service of the first RAN device; and the first response includes at least one computing service flow of the first RAN device accepted by the first communication device.

[0025] In a possible implementation, the first request includes a requested computing service flow list and a corresponding requested resource list.

[0026] In a possible implementation manner, the first request includes at least one requested computing service flow and resource information required by each service flow in the at least one computing service flow.

[0027] In a possible implementation, the first request further includes a service continuity guarantee indication, a requested key performance indicator, and transport layer information.

[0028] In a possible implementation manner, the computing capability information of the first communication device includes the type of computing services supported by the first communication device and available resource information.

[0029] In a possible implementation manner, the computing capability information of the first communication device includes a service support list and an available resource list.

[0030] In a possible implementation manner, the computing capability information of the first communication device further includes at least one of the following parameters: service area, service continuity support, availability schedule, and availability reporting period.

[0031] In a possible implementation, before the first communication device sends the first response to the second communication device, the method further includes: the first communication device performs admission control, where the admission control is used to determine the computing service of the first RAN device admitted by the first communication device.

[0032] It can be seen that, through admission control, the first communication device determines the computing service of the accepted first RAN device, thereby ensuring the QoS of the computing service provided by it.

[0033] In a possible implementation manner, the first communication device is a second RAN device, and the second communication device is the first RAN or CN device; or, the first communication device is a terminal device, and the second communication device is the first RAN device.

[0034] In a possible implementation, when the first communication device is the second RAN device and the second communication device is the first RAN device or a CN device, before the first communication device receives the first request from the second communication device, the method further includes: the second RAN device generates computing capability information of the second RAN device; and the second RAN device sends the computing capability information of the second RAN device to the second communication device.

[0035] In a possible implementation, when the first communication device is the terminal device and the second communication device is the first RAN device, before the first communication device receives the first request from the second communication device, the method further includes: the terminal device generates computing capability information of the terminal device, and the terminal device sends the computing capability information of the terminal device to the first RAN device; or, the terminal device generates the computing capability information of the terminal device, and the terminal device sends the computing capability information of the terminal device to the first RAN device through the CN device.

[0036] In a third aspect, the present application provides a method for implementing a computing service, including: a first communication device generates its own computing capability information, and the first communication device sends the computing capability information to a second communication device.

[0037] It can be seen that the method provided in the embodiment of the present application enables the first communication device to report its computing capability information to other communication devices, so that other communication devices can determine whether the first communication device can provide computing services, which helps other communication devices to use the first communication device to provide computing services to other communication devices.

[0038] In a possible implementation manner, the computing capability information of the first communication device includes the type of computing services supported by the first communication device and available resource information.

[0039] In a possible implementation manner, the first communication device is a first RAN device, and the second communication device is a second RAN device or a CN device; or, the first communication device is a terminal device, and the second communication device is the first RAN device or the CN device.

[0040] In a possible implementation, before the first communication device sends the computing capability information to the second communication device, the first communication device receives a first request from the second communication device, where the first request is used to request the first communication device to send its computing capability information.

[0041] In a possible implementation, after the first communication device sends the computing capability information to the second communication device, the first communication device receives confirmation information from the second communication device, where the confirmation information is used to indicate that the second communication device correctly receives the computing capability information sent by the first communication device.

[0042] In a fourth aspect, the present application provides a method for implementing a computing service, including: a second communication device receives computing capability information from a first communication device, and the second communication device stores the computing capability information of the first communication device; the computing capability information of the first communication device includes the type of computing service supported by the first communication device and available resource information.

[0043] It can be seen that the method provided in the embodiment of the present application enables the second communication device to obtain the computing capability information of the first communication device, so that the second communication device can determine whether the first communication device can provide computing services, which helps the second communication device to use the first communication device to provide computing services to other communication devices.

[0044] In a possible implementation manner, the first communication device is a first RAN device, and the second communication device is a second RAN device or a CN device; or, the first communication device is a terminal device, and the second communication device is the first RAN device or the CN device.

[0045] In a possible implementation, before the second communication device receives the computing capability information from the first communication device, the second communication device sends a first request to the first communication device, where the first request is used to request the first communication device to send its computing capability information.

[0046] In a possible implementation, after the second communication device receives the computing capability information from the first communication device, the second communication device sends confirmation information to the first communication device, where the confirmation information is used to indicate that the second communication device correctly receives the computing capability information sent by the first communication device.

[0047] In a fifth aspect, the present application provides a method for implementing a computing service, including: a service radio access network RAN ​​device determines to transfer a computing service; the service RAN device sends a transfer request to a target terminal device, the transfer request is used to indicate that the service RAN device requests the target terminal device to take over all or part of the computing services of a source terminal device; the service RAN device receives a transfer response from the target terminal device, the transfer response is used to indicate the computing service flow of the source terminal device accepted by the target terminal device; the service RAN device sends configuration information to the target terminal device; and the service RAN device and the target terminal device interact to compute service flow data.

[0048] It can be seen that the method provided in the embodiment of the present application enables the RAN device to transfer computing services between terminal devices, thereby ensuring the continuity of computing services.

[0049] In a possible implementation manner, before the service RAN device and the target terminal device interactively calculate the service flow data, it also includes: the service RAN device and the source terminal device perform intermediate calculation of service data and context transfer interaction.

[0050] In the sixth aspect, a communication device is provided for executing the method in the first aspect or any possible implementation of the first aspect, or the method in the second aspect or any possible implementation of the second aspect, or the method in the third aspect or any possible implementation of the third aspect, or the method in the fourth aspect or any possible implementation of the fourth aspect, or the method in the fifth aspect or any possible implementation of the fifth aspect. Specifically, the communication device may include a unit for executing the method in the first aspect or any possible implementation of the first aspect, or the second aspect or any possible implementation of the second aspect, or the third aspect or any possible implementation of the third aspect, or the fourth aspect or any possible implementation of the fourth aspect, or the fifth aspect or any possible implementation of the fifth aspect.

[0051] In the seventh aspect, a computer program product is provided, comprising: a computer program code, wherein when the computer program code is executed by a communication unit, a processing unit or a transceiver, or a processor of a communication device (for example, a wireless access network device or a positioning device), the communication device executes the method in the first aspect or any possible implementation of the first aspect, or the second aspect or any possible implementation of the second aspect, or the third aspect or any possible implementation of the third aspect, or the fourth aspect or any possible implementation of the fourth aspect, or the fifth aspect or any possible implementation of the fifth aspect.

[0052] In the eighth aspect, a computer-readable storage medium is provided, which stores a program, which enables a computer to execute the method in the first aspect or any possible implementation of the first aspect, or the second aspect or any possible implementation of the second aspect, or the third aspect or any possible implementation of the third aspect, or the fourth aspect or any possible implementation of the fourth aspect, or the fifth aspect or any possible implementation of the fifth aspect.

[0053] In the ninth aspect, an embodiment of the present application provides a chip, which is coupled to a memory and executes the method in the first aspect of the embodiment of the present application or any possible implementation of the first aspect, or the second aspect or any possible implementation of the second aspect, or the third aspect or any possible implementation of the third aspect, or the fourth aspect or any possible implementation of the fourth aspect, or the fifth aspect or any possible implementation of the fifth aspect.

[0054] These and other aspects of the invention will become more apparent from the following description of the embodiment(s). BRIEF DESCRIPTION OF THE DRAWINGS

[0055] The following is a brief introduction to the drawings used in the embodiments of the present application or the description of the prior art:

[0056] Figure 1 is a schematic diagram of a communication system provided in an embodiment of the present application;

[0057] Figure 2 This is a schematic diagram of the architecture of a gNB divided into a CU and a DU provided in an embodiment of the present application;

[0058] Figure 3 This is a flowchart of a method for reporting RAN device computing capability provided by an embodiment of the present application;

[0059] Figure 4 This is a schematic diagram of a method flow for reporting computing capability of a terminal device provided in an embodiment of the present application;

[0060] Figure 5 This is a flowchart of another method for reporting computing capability of a terminal device provided in an embodiment of the present application;

[0061] Figure 6 It is a flowchart of a method for requesting a RAN device to provide a computing service provided by an embodiment of the present application;

[0062] Figure 7 It is a flowchart of another method for requesting a RAN device to provide a computing service provided by an embodiment of the present application;

[0063] Figure 8 It is a flow chart of a method provided by an embodiment of the present application in which a source CN device requests a target RAN device to provide a computing service;

[0064] Fig. 9 It is a flowchart of a method for requesting a terminal device to provide a computing service provided by an embodiment of the present application;

[0065] Fig.10 It is a flowchart of another method for requesting a terminal device to provide a computing service provided by an embodiment of the present application;

[0066] Fig.11 It is a flowchart of a method for a RAN device to transfer computing services between terminal devices provided in an embodiment of the present application;

[0067] Fig.12 It is a flowchart of a method provided by an embodiment of the present application for a RAN device to switch a computing service following the movement of a terminal device;

[0068] Fig.13 is a schematic block diagram of a terminal device provided in an embodiment of the present application;

[0069] Fig.14 is another schematic block diagram of a terminal device provided in an embodiment of the present application;

[0070] Fig.15 is a schematic block diagram of a RAN device provided in an embodiment of the present application;

[0071] Fig.16 is another schematic block diagram of a RAN device provided in an embodiment of the present application;

[0072] Fig.17 is a schematic block diagram of a CN device provided in an embodiment of the present application;

[0073] Fig.18 It is another schematic block diagram of the CN device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0074] The embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0075] In this application, the word "exemplary" is used to mean "serving as an example, illustration, or illustration." Any embodiment described in this application as "exemplary" is not necessarily to be construed as being preferred or advantageous over other embodiments. The following description is given to enable any person skilled in the art to implement and use the invention. In the following description, details are listed for the purpose of explanation. It should be understood that a person of ordinary skill in the art can recognize that the invention can be implemented without using these specific details. In other instances, well-known structures and processes are not elaborated in detail to avoid obscuring the description of the invention with unnecessary details. Therefore, the present invention is not intended to be limited to the embodiments shown, but is consistent with the widest scope consistent with the principles and features disclosed in this application.

[0076] The terms "first", "second", "third", "fourth", etc. (if any) in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0077] The terms "system" and "network" are often used interchangeably herein.

[0078] The technical solution of the present invention is described in detail with specific embodiments below. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments.

[0079] The following describes the embodiments of the present application in conjunction with the accompanying drawings. Figure 1 , Figure 1A schematic diagram of a communication system applied in an embodiment of the present application. It should be understood that the technical solution of the embodiment of the present application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, Code Division Multiple Access (CDMA) system, Universal Mobile Telecommunication System (UMTS), wireless local area network (WLAN), fifth generation (5th generation, 5G) mobile communication system, new wireless (new radio, NR) communication system, communication system based on orthogonal frequency division multiplexing (OFDM) technology or next generation (next generation, NG) communication system, such as 6G, etc. This application is described by taking the 5G system as an example, but is not limited to the 5G system. It is known to those of ordinary skill in the art that with the emergence of new business scenarios and the evolution of network architecture, the technical solution provided in the embodiment of the present application is also applicable to similar technical problems.

[0080] Figure 1 The communication system 100 shown includes a terminal device 120, a radio access network (RAN) and a 5G core network (5GC) 180, wherein the RAN includes a RAN device 140 and a RAN device 142. It should be understood that Figure 1 This is just a schematic description of a communication system. In an actual system, the RAN may include more RAN devices, and multiple terminal devices may each be connected to the core network (CN) through their serving RAN devices. Figure 1In the embodiment, the terminal device 120 wirelessly communicates with the RAN device 140 through the wireless link 160. Optionally, the terminal device 120 can also be wirelessly connected to the RAN device 142 at the same time to achieve multi-connection communication. The RAN device 140 / 142 can be connected to the 5GC 180 through the control plane interface NG-C and the user plane interface NG-U respectively, and the RAN devices can be connected to each other through the control plane interface Xn-C and the user plane interface Xn-U. Among them, NG-C and NG-U are combined to be referred to as the NG interface, and Xn-C and Xn-U are combined to be referred to as the Xn interface. 5GC includes different types of core network devices. For example, the RAN device 140 / 142 is connected to the access and mobility management function (AMF) node in the 5GC 180 through the NG-C interface, and the RAN device 140 / 142 is connected to the user plane function (UPF) node in the 5GC 180 through the NG-U interface. The core network device 140 may include a session management function (SMF), an access and mobility management function (AMF), a network data analytics function (NWDAF), a user plane function (UPF), etc. Among them, SMF is mainly responsible for session management (such as session establishment, session modification and session release), UE IP address allocation and management, user plane function selection and control, and termination of the session management part in the non-access stratum (NAS) message. AMF is mainly responsible for access control, mobility management, attachment and detachment, and gateway selection. NWDAF is mainly responsible for data collection and analysis. UPF is mainly responsible for message routing and forwarding.

[0081] In the embodiment of the present application, the RAN device is a device deployed in a wireless access network to provide wireless communication functions for terminal devices. The RAN device may include various forms, for example, it may be a next-generation base station, such as a next-generation Node B (gNB) or a next-generation evolved Node B (ng-eNB), etc., or it may be an access point (AP) in a wireless local area network (WLAN), or an evolved Node B (eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device and a wearable device, etc. Among them, a RAN device has one or more transmission and reception points (TRP). It should be understood that the terminal device communicates with the RAN device through the transmission resources (for example, frequency domain resources, time domain resources, code domain resources, etc.) used by one or more cells managed by the network device. The cell may belong to a macro cell, a hyper cell, or a small cell. The small cells here may include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0082] Figure 1The terminal device shown may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device. The terminal device may be a station (ST) in a WLAN, a cellular phone, a cordless phone, a SIP phone, a wireless local loop (WLL) station, a personal digital assistant (PDA) device, a tablet (pad), a handheld device or computer with wireless communication function, a relay device, a computing device or other processing device coupled to a wireless modem, a vehicle-mounted device, a wearable device, and a next-generation communication system, for example, a terminal device in a 5G network or a terminal device in a future-evolved public land mobile network (PLMN) network. As an example but not limitation, in the embodiment of the present application, the terminal device can also be a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical, a wireless terminal device in smart grid, a wireless terminal device in transportation safety, a wireless terminal device in smart city, a wireless terminal device in smart home, a navigation device, an Internet of Things (IoT) device, and a wearable device. Wearable devices can also be called wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also powerful functions achieved through software support, data interaction, and cloud interaction. In a broad sense, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0083] Optionally, in a 5G system, a RAN device (such as a gNB) can be further divided into a central unit (CU) and a distributed unit (DU) according to the protocol stack, where the CU and DU can be deployed on different physical devices. The CU is responsible for the operation of the RRC layer, SDAP layer, and PDCP layer, and the DU is responsible for the operation of the RLC layer, MAC layer, and PHY layer. Figure 2 (a) shows an architecture of a gNB divided into CU and DU. Among them, a gNB may include a CU and one or more DUs, and the one or more DUs are controlled by the one CU. A DU is connected to the CU through a control plane interface (such as F1-C) for transmitting control plane data; a DU is connected to the CU through a user plane interface (such as F1-U) for transmitting user plane data. Furthermore, the CU can also be divided into a centralized unit of the control plane (i.e., a centralized unit control plane CU-CP network element) and a centralized unit of the user plane (i.e., a centralized unit user plane CU-UP network element), wherein the CU-CP and CU-UP can also be deployed on different physical devices respectively, the CU-CP is responsible for the processing of the control plane of the RRC layer and the PDCP layer, and the CU-UP is responsible for the processing of the user plane of the SDAP layer and the PDCP layer. Figure 2(b) shows an architecture of a gNB divided into CU-CP, CU-UP and DU. Among them, a gNB may include a CU-CP, one or more CU-UPs and one or more DUs. A CP-UP is connected to only one CU-CP through a control plane interface (such as E1) for transmitting control plane data; a DU is connected to only one CU-CP through a control plane interface (such as F1-C) for transmitting control plane data; under the control of the CU-CP, a DU can be connected to one or more CU-UPs, and a CU-UP can also be connected to one or more DUs. The CU-UP and DU are connected through a user plane interface (such as F1-U) for transmitting user plane data. It is worth noting that in order to maintain the resilience of the network, a DU or a CU-UP can also be connected to multiple CU-CPs. At this time, multiple CU-CPs serve as backups for each other; in actual applications, only one CU-CP is running at the same time. It should be understood that for the RAN device architecture divided into CU and DU, the protocol stack division method based on which the above-mentioned RAN device is divided into CU and DU is only exemplary, and the RAN device can also divide CU and DU according to other division methods. For example, the CU can be responsible for the operations of the RRC layer, SDAP layer, PDCP layer and RLC layer, and the DU can be responsible for the operations of the MAC layer and the PHY layer; or the CU can be responsible for the operations of the RRC layer and the SDAP layer, and the DU can be responsible for the operations of the PDCP layer, RLC layer, MAC layer and PHY layer, etc.; similarly, the protocol stack division method between CU-CP and CU-UP in the CU is also variable; the application does not make specific limitations on this.

[0084] Exemplarily, the communication system proposed in the embodiment of the present application can use 5G technology. Due to the diversity of services and the flexibility of configuration, 5G RAN has extremely high processing complexity. For example, 5G RAN needs to support different physical layer parameters (numerology), ultra-large bandwidth (>200MHz), ultra-low latency services (such as unmanned driving, wireless medical care), ultra-high rate services (such as virtual reality, augmented reality), large-scale antenna array deployment, etc. Therefore, during operation, RAN equipment needs to have self-optimization capabilities, dynamically optimize its own configuration and the configuration of terminal equipment according to business conditions and network status, so that network performance and user experience are guaranteed. The self-optimization processing of the RAN device is to calculate various data collected and counted, such as establishing a data model to calculate the optimization result, etc. This process is also called the computing service of the RAN device. The inventor found that due to the different hardware capabilities, resource configurations and current resource usage of different RAN devices, there are RAN devices that do not have the resources or capabilities to perform computing services, resulting in the inability of the RAN device to achieve self-optimization to ensure network performance and user experience. To this end, the embodiment of the present application provides a technical solution for implementing computing services of RAN devices. Specifically, a RAN device can use other RAN devices or terminal devices with appropriate computing capabilities to complete its own computing services. Furthermore, the technical solution of the embodiment of the present application is also applied to a RAN device architecture with CU and DU, where the CU may also include CU-CP and CU-UP separation.

[0085] First, define the following two terms:

[0086] 1) Device computing capability information: used to indicate the computing capability that the device can provide for computing services in the current state. The device computing capability information includes the types of computing services supported by the device and the available resource information. Optionally, the types of supported computing services are represented by a service support list, and the available resource information is represented by an available resource list. Among them, the service support list is used to indicate the types of computing services supported by the device; generally, a device can support one or more different types of computing services, such as the types of artificial intelligence (AI) models supported, the types of microservices supported, etc. The available resource list is used to indicate one or more resources currently available to the device, such as graphics processing unit (GPU) resources, central processing unit (CPU) resources, storage resources, etc.; further, the available resource list can also indicate the availability of various resources, such as the RAN device can provide 20% of GPU resources for computing services, or can provide 50% of storage resources for computing services, or can provide 30% of CPU utilization for computing services, or can provide 2G bytes of storage resources for computing services, etc.

[0087] Optionally, the device computing capability information also includes at least one of the following parameters: service area, service continuity support, availability schedule, and availability reporting period. The service area is used to indicate the area range in which the device can provide computing services; illustratively, the area range can be a tracking area (TA) in the network, a tracking area list (TAL) formed by multiple tracking areas, or a registration area (RA). Service continuity support is used to indicate whether the device supports the continuity of computing services, for example, when the computing service is interrupted, whether the device can continue to process subsequent processes of the computing service at the breakpoint. The availability schedule is used to indicate the schedule in which the device can be used for computing services, for example, within which time window the computing service is provided. The availability reporting period is used to indicate the period for the device to report computing capacity information. Generally, since the device needs to perform other communication connections and data processing in addition to providing computing services, the available computing capacity of the device changes dynamically. In addition, during the device's computing service, the available computing capacity of the device also changes dynamically due to different processing states of the process. It is precisely because of the dynamic nature of the device's available computing capacity that the device usually needs to report its computing capacity information periodically.

[0088] For a RAN device, its device computing capability information is called RAN device computing capability information, and may also be called a RAN device computing capability profile.

[0089] For a terminal device, its device computing capability information is called terminal device computing capability information, and may also be called a terminal device computing capability template.

[0090] 2) Quality of service (QoS) requirements for computing services: including the type of computing service requested and the resource information required for computing services of this type. Optionally, the type of computing service requested is represented by a list of requested computing service flows, and the required resource information is represented by a list of requested resources. Among them, one type of computing service corresponds to one computing service flow, and the resource information required for one type of computing service can be represented as a list of resources required for a computing service flow of the corresponding type, such as required GPU resources, CPU resources, storage resources, etc., and can also include the quantity of various resources required.

[0091] Optionally, the computing service QoS requirement also includes a service continuity guarantee indication, a requested key performance indicator (requested KPI), transport layer information, etc. Among them, the service continuity guarantee indication is used to indicate whether business continuity needs to be provided, that is, when the service is interrupted, whether it is necessary to continue the subsequent process from the breakpoint or restart the service. The requested KPI is used to indicate the KPI required for the service, such as latency indicators. The transport layer information is used to identify the tunnel transport layer information of the device that proposes the computing service QoS requirement, such as the IP address and / or tunnel endpoint identifier (TEID).

[0092] This article specifically provides the following embodiments. Figures 3 to 12 , the technical solution of the present application is described in detail with specific method embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. It should be noted that Figures 3 to 12 is a schematic flow chart of a method embodiment of the present application, showing detailed communication steps or operations of the method, but these steps or operations are only examples, and the present application embodiment may also perform other operations or Figures 3 to 12 In addition, Figures 3 to 12 The steps in Figures 3 to 12 are executed in a different order than those presented, and may not be executed in the order Figures 3 to 12 All operations in .

[0093] Figure 3 A flowchart of a method for reporting RAN device computing capability provided in an embodiment of the present application is provided. The method 300 is applied to the interaction between a RAN device and another network device. Figure 3 The process includes the following steps:

[0094] S301. A first RAN device generates RAN device computing capability information.

[0095] In this step, the first RAN device generates the RAN device computing capacity information of the first RAN device according to its current resource status and / or policy. It should be understood that the RAN device computing capacity information changes dynamically due to the different resource usage status of the RAN device at different times.

[0096] S302: The first RAN device sends the RAN device computing capability information of the first RAN device to the first network device. Correspondingly, the first network device receives the RAN device computing capability information from the first RAN device.

[0097] Typically, the first RAN device may periodically send RAN device computing capacity information to the first network device; or may send RAN device computing capacity information to the first network device based on event triggering, for example, when the available resources of the first RAN device reach a preset threshold, or the first RAN device receives a request for computing capacity information from other network devices.

[0098] The first RAN device may send the RAN device computing capability information in a variety of forms. In one form, the first RAN device sends complete RAN device computing capability information, and the complete RAN device computing capability information includes various parameters and their values ​​in the current RAN device computing capability information of the first RAN device. In another form, the first RAN device sends part of the RAN device computing capability information, and the part of the RAN device computing capability information includes some parameters and their values ​​in the current RAN device computing capability information of the first RAN device. For example, the first RAN device may send parameters and their values ​​that have changed from the RAN device computing capability information sent last time, or the amount of change in the values ​​of the changed parameters, etc. This application does not specifically limit the form in which the first RAN device sends the RAN device computing capability information.

[0099] In one possible implementation, the first network device is a CN device, such as an AMF. In this case, the first RAN device sends its RAN device computing capability information to the CN device in the process of establishing an NG interface with the CN device or in the RAN device configuration update process. For example, the first RAN device carries the RAN device computing capability information in an NG Setup Request message, or the first RAN device carries the RAN device computing capability information in a RAN Configuration Update message. It should be understood that the first RAN device can also send the RAN device computing capability information to the CN device through other processes of interacting with the CN device, and the first RAN device can also carry the RAN device computing capability information in other existing messages or newly defined messages of the NG interface, and this application does not make specific limitations on this.

[0100] In another possible implementation, the first network device is a second RAN device. In this case, the first RAN device sends its RAN device computing capability information to the second RAN device in the process of establishing an Xn interface with the second RAN device or in the Xn interface configuration update process. For example, the first RAN device carries the RAN device computing capability information in an Xn Setup Request message, or the first RAN device carries the RAN device computing capability information in an NG-RAN Node Configuration Update message. It should be understood that the first RAN device can also send the RAN device computing capability information to the second RAN device through other processes of interacting with the second RAN device, and the first RAN device can also carry the RAN device computing capability information in other existing messages or newly defined messages of the Xn interface, and this application does not specifically limit this.

[0101] S303: The first network device saves the RAN device computing capability information of the first RAN device.

[0102] In this step, after receiving the RAN device computing capability information from the first RAN device, the first network device saves the RAN device computing capability information.

[0103] Optionally, when the first network device periodically receives the RAN device computing capacity information sent by the first RAN device, the first network device also periodically saves the latest received RAN device computing capacity information. When the first network device aperiodically receives the RAN device computing capacity information sent by the first RAN device, the first network device saves the latest received RAN device computing capacity information whenever it receives new RAN device computing capacity information.

[0104] When the first network device receives complete RAN device computing capability information, the first network device directly saves the received RAN device computing capability information; when the first network device receives partial RAN device computing capability information, the first network device updates the saved RAN device computing capability information based on the received partial RAN device computing capability information, thereby saving new complete RAN device computing capability information.

[0105] S304: The first network device sends first confirmation information to the first RAN device. Correspondingly, the first RAN device receives the first confirmation information from the first network device. The first confirmation information is used to confirm that the first network device correctly receives the RAN device computing capacity information sent by the first RAN device.

[0106] It should be understood that step S304 is optional.

[0107] In a possible implementation, the first network device is a CN device, such as an AMF. In this case, if the first RAN device carries the computing capability information of the RAN device in the NG setup request message in the above step S302, then in this step, the CN device carries the first confirmation information in the NG setup response (NG Setup Response) message; if the first RAN device carries the computing capability information of the RAN device in the RAN configuration update message in the above step S302, then in this step, the CN device carries the first confirmation information in the RAN Configuration Update ACK message. It should be understood that the CN device can also carry the first confirmation information in other existing messages or newly defined messages of the NG interface, and this application does not specifically limit this.

[0108] In another possible implementation, the first network device is a second RAN device. In this case, if the first RAN device carries the computing capability information of the RAN device in the Xn setup request message in the above step S302, then in this step, the second RAN device carries the first confirmation information in the Xn setup response (Xn Setup Response) message; if the first RAN device carries the computing capability information of the RAN device in the NG-RAN node configuration update message in the above step S302, then in this step, the second RAN device carries the first confirmation information in the NG-RAN Node Configuration Update ACK message. It should be understood that the second RAN device can also carry the first confirmation information in other existing messages or newly defined messages of the Xn interface, and this application does not specifically limit this.

[0109] Optionally, this embodiment further includes step S305.

[0110] S305: The first network device sends a first request to the first RAN device. Correspondingly, the first RAN device receives the first request from the first network device. The first request is used to request the first RAN device to report RAN device computing capability information.

[0111] Optionally, the first network device requests the first RAN device to periodically report the RAN device computing capability information; at this time, the first request further includes periodic information of the first RAN device reporting the RAN device computing capability information configured by the first network device.

[0112] Optionally, this embodiment includes step S305 but does not include step S304, or includes step S304 but does not include step S305.

[0113] It is worth noting that, in the case where the first RAN device is a CU-DU separation architecture, the steps executed by the first RAN device in the above steps of this embodiment are executed by the CU of the first RAN device; further, in the case where the CU includes a CU-CP and a CU-UP, the steps executed by the first RAN device in the above steps are executed by the CU-CP of the first RAN device. Similarly, in the case where the first network device is a second RAN device and the second RAN device is a CU-DU separation architecture, the steps executed by the first network device in the above steps of this embodiment are executed by the CU of the second RAN device; further, in the case where the CU includes a CU-CP and a CU-UP, the steps executed by the first network device in the above steps are executed by the CU-CP of the second RAN device. It should be understood that the CU-CP can store the RAN device computing capacity information in the CU-CP or the CU-UP.

[0114] Through the above steps of this embodiment, the RAN device notifies other network devices of its own RAN device computing capability information, so that other network devices can use the computing capability of the RAN device to provide computing services.

[0115] Figure 4 A flow chart of a method for reporting computing capability of a terminal device provided in an embodiment of the present application. The method 400 is applied to the interaction between a terminal device and a RAN device wirelessly connected thereto, and then the interaction with other network devices is realized through the RAN device, so that the RAN device and other network devices obtain computing capability information of the terminal device. It should be understood that the information interaction between the terminal device and the RAN device is realized through access stratum (AS) layer messages. Figure 4 The process includes the following steps:

[0116] S401. The terminal device generates terminal device computing capability information.

[0117] In this step, the terminal device generates the terminal device computing capability information of the terminal device according to its current resource status and / or strategy. It should be understood that the terminal device computing capability information changes dynamically due to the different resource usage status of the terminal device at different times.

[0118] S402: The terminal device sends the terminal device computing capability information of the terminal device to the first RAN device. Correspondingly, the first RAN device receives the terminal device computing capability information from the terminal device.

[0119] Typically, the terminal device can periodically send the terminal device computing capacity information to the first RAN device; it can also send the terminal device computing capacity information to the first RAN device based on event triggering, for example, when the available resources of the terminal device reach a preset threshold, or the terminal device receives a request for computing capacity from other network devices.

[0120] The terminal device can send the terminal device computing capability information in a variety of forms. In one form, the terminal device sends the complete terminal device computing capability information, and the complete terminal device computing capability information includes the various parameters and their values ​​in the current terminal device computing capability information of the terminal device. In another form, the terminal device sends part of the terminal device computing capability information, and the part of the terminal device computing capability information includes some parameters and their values ​​in the current terminal device computing capability information of the terminal device. For example, the terminal device can send the parameters and their values ​​that have changed from the terminal device computing capability information sent last time, or the value change of the changed parameters, etc. in this transmission. The present application does not specifically limit the form in which the terminal device sends the terminal device computing capability information.

[0121] It should be understood that the first RAN device is a RAN device wirelessly connected to the terminal device. Optionally, the RAN device is a service RAN device of the terminal device, providing data transmission services for the terminal device.

[0122] Optionally, the terminal device carries the terminal device computing capability information in a terminal device capability information (UE Capability Information) message and a measurement report (Measurement Report) message sent to the first RAN device.

[0123] S403: The first RAN device stores terminal device computing capability information of the terminal device.

[0124] In this step, after receiving the terminal device computing capability information from the terminal device, the first RAN device saves the terminal device computing capability information.

[0125] Optionally, when the first RAN device periodically receives the terminal device computing capability information sent by the terminal device, the first RAN device also periodically saves the latest received terminal device computing capability information. When the first RAN device aperiodically receives the terminal device computing capability information sent by the terminal device, the first RAN device saves the latest received terminal device computing capability information whenever the terminal device computing capability information is newly received.

[0126] When the first RAN device receives complete terminal device computing capability information, the first RAN device directly saves the received terminal device computing capability information; when the first RAN device receives partial terminal device computing capability information, the first RAN device updates the saved terminal device computing capability information based on the received partial terminal device computing capability information, thereby saving new complete terminal device computing capability information.

[0127] S404: The first RAN device sends second confirmation information to the terminal device. Correspondingly, the terminal device receives the second confirmation information sent by the first RAN device. The second confirmation information is used to confirm that the first RAN device correctly receives the terminal device computing capability information sent by the terminal device.

[0128] It should be understood that step S404 is optional.

[0129] Through the above steps of this embodiment, the terminal device notifies the RAN device to which it is connected of its own terminal device computing capability information, so that the RAN device can use the computing capability of the terminal device in subsequent computing services.

[0130] Optionally, this embodiment may further include the following steps S405-S408. It should be understood that there may be no coupling relationship between steps S405-S408 and the aforementioned steps S401-S404, and steps S405-S408 may be executed as long as the first RAN device has the computing capability information of the terminal device.

[0131] S405: The first RAN device forwards the computing capability information of the terminal device to the first network device. Accordingly, the first network device receives the computing capability information of the terminal device from the first RAN device.

[0132] S406: The first network device saves the received computing capability information of the terminal device.

[0133] S407: The first network device sends third confirmation information to the first RAN device. Correspondingly, the first RAN device receives the third confirmation information from the first network device. The third confirmation information is used to confirm that the first network device correctly receives the terminal device computing capability information sent by the first RAN device.

[0134] S408: The first network device sends a third request to the first RAN device. Correspondingly, the first RAN device receives the third request from the first network device. The third request is used to request the first RAN device to send the computing capability information of the terminal device.

[0135] The above steps S405-S408 are similar to the steps S302-S305 of the above embodiment, and will not be described in detail. The main difference is that in this embodiment, the first network device receives and stores the computing capability information of the terminal device sent by the first RAN device, while in the above embodiment, the first network device receives and stores the computing capability information of the RAN device sent by the first RAN device. Optionally, in the above step S405, the first RAN device carries the computing capability information of the terminal device in a RAN Configuration Update message sent to the first network device; in the above step S407, the first network device carries the third confirmation information in a RAN Configuration Update ACK message sent to the first RAN device.

[0136] Optionally, this embodiment further includes step S409.

[0137] S409: The first RAN device sends a second request to the terminal device. Correspondingly, the terminal device receives the second request from the first RAN device. The second request is used to request the terminal device to report the computing capability information of the terminal device.

[0138] Optionally, the first RAN device requests the terminal device to periodically report the terminal device computing capability information; at this time, the second request further includes periodic information of the terminal device reporting the terminal device computing capability information configured by the first RAN device.

[0139] Optionally, the first RAN device carries the second request in a terminal device capability request (UE Capability Enquiry) message sent to the terminal device.

[0140] Optionally, this embodiment includes step S409 but does not include step S404, or includes step S304 but does not include step S409.

[0141] It is worth noting that, in the case where the first RAN device is a CU-DU separation architecture, the steps performed by the first RAN device in the above steps of this embodiment are performed by the CU of the first RAN device; further, in the case where the CU includes a CU-CP and a CU-UP, the steps performed by the first RAN device in the above steps are performed by the CU-CP of the first RAN device, and the CU-CP can save the terminal device computing capability information in the CU-CP or CU-UP. It should be understood that the terminal device interacts with the CU or CU-CP of the first RAN device through the DU of the first RAN device to which it is wirelessly connected. Similarly, in the case where the first network device is a second RAN device and the second RAN device is a CU-DU separation architecture, the steps performed by the first network device in the above steps of this embodiment are performed by the CU of the second RAN device; further, in the case where the CU includes a CU-CP and a CU-UP, the steps performed by the first network device in the above steps are performed by the CU-CP of the second RAN device, and it should be understood that the CU-CP can save the terminal device computing capability information in the CU-CP or CU-UP.

[0142] Through the above steps of this embodiment, the network device obtains the terminal device computing capability information of the terminal device through the RAN device to which the terminal device is connected, thereby enabling the network device to use the computing capability of the terminal device in subsequent computing services.

[0143] In the embodiment in which the network device obtains the computing capability information of the terminal device, the above method 400 describes that the terminal device sends the computing capability information of the terminal device to the network device through an AS layer message. In the case where the first network device is a CN device, the terminal device may also send the computing capability information of the terminal device to the CN device through a NAS layer message. In this case, the RAN device or other RAN devices wirelessly connected to the terminal device need to obtain the computing capability information of the terminal device through forwarding by the CN device.

[0144] Figure 5 A flowchart of another method for reporting computing capability of a terminal device provided in an embodiment of the present application. The method 500 is applied to the interaction between a terminal device and a CN device so that the CN device obtains computing capability information of the terminal device; and further, the CN device can also interact with a RAN device so that the RAN device obtains computing capability information of the terminal device.

[0145] Figure 5 The process includes the following steps:

[0146] S501. The terminal device generates terminal device computing capability information.

[0147] This step is similar to step S401 in the above embodiment and will not be described again here.

[0148] S502: The terminal device sends the terminal device computing capability information to the first CN device. Correspondingly, the first CN device receives the terminal device computing capability information from the terminal device.

[0149] In this step, the terminal device sends a NAS message to the first CN device through the first RAN device connected thereto, and the NAS message carries the computing capability information of the terminal device. It should be understood that after receiving the NAS message sent by the terminal device, the first RAN device does not parse the message, but forwards the message to the first CN device.

[0150] Optionally, the terminal device carries the computing capability information of the terminal device in a registration request (Registration Request) message sent to the first CN device.

[0151] S503: The first CN device saves the computing capability information of the terminal device.

[0152] S504: The first CN sends the computing capability information of the terminal device to the first RAN device. Correspondingly, the first RAN device receives the computing capability information of the terminal device from the first CN device.

[0153] S505. The first RAN device stores computing capability information of the terminal device.

[0154] S506: The first RAN device sends fourth confirmation information to the first CN device. Correspondingly, the first CN device receives the fourth confirmation information from the first RAN device. The fourth confirmation information is used to confirm that the first RAN device correctly receives the terminal device computing capability information sent by the first CN device.

[0155] S507: The first RAN device sends a fourth request to the first CN device. Correspondingly, the first CN device receives the fourth request from the first RAN device. The fourth request is used to request the first CN device to send terminal device computing capability information.

[0156] S508: The first CN device sends fifth confirmation information to the terminal device. Correspondingly, the terminal device receives the fifth confirmation information from the first CN device. The fifth confirmation information is used to confirm that the first CN device correctly receives the terminal device computing capability information sent by the terminal device.

[0157] It should be understood that step S508 is optional.

[0158] The fifth confirmation information is also carried on the NAS message. Optionally, the first CN device carries the fifth confirmation information in a registration accept message sent to the terminal device.

[0159] The above steps S502 and S503 are similar to steps S302 and S303 of the aforementioned embodiment, respectively, and will not be described in detail. The main difference is that in this embodiment, the first CN device receives and saves the terminal device computing capability information sent by the terminal device, while in the aforementioned embodiment, the first network device receives and saves the RAN device computing capability information sent by the first RAN device.

[0160] It should be understood that the above step S503 is optional and is performed when the first CN device needs to save the computing capability information of the terminal device; if the first CN device does not need to save the computing capability information of the terminal device, this step does not need to be performed.

[0161] The above steps S504-S507 are similar to the steps S302-S305 of the above embodiment, and are not described here. The main difference is that in this embodiment, the first RAN receives and stores the computing capability information of the terminal device sent by the first CN device, while in the above embodiment, the first network device receives and stores the computing capability information of the RAN device sent by the first RAN device. Optionally, in the above step S504, the first CN device carries the computing capability information of the terminal device in an Initial Context Setup Request message or a UE Context Modification Request message sent to the first RAN device; in the above step S506, the first RAN device carries the fourth confirmation information in an Initial Context Setup Response message or a UE Context Modification Response message sent to the first CN device. It should be understood that there may be no coupling relationship between steps S504-S507 and the aforementioned steps S501-S503, and steps S504-S507 can be executed as long as the first CN device has the computing capability information of the terminal device.

[0162] It should be understood that the above steps S504-S507 are optional and are performed when the first RAN device needs to save the computing capability information of the terminal device; if the first RAN device does not need to save the computing capability information of the terminal device, these steps do not need to be performed.

[0163] It should be noted that, in the above steps S502 and S508, the NAS message interacted between the terminal device and the first CN device is forwarded through the first RAN device, and the first RAN device is a RAN device having a wireless connection with the terminal device; in the above steps S504-S507, the first RAN device is not limited to a RAN device having a wireless connection with the terminal device, but may also be any RAN device connected to the first CN device.

[0164] Optionally, this embodiment includes step S509 but does not include step S508, or includes step S508 but does not include step S509.

[0165] Optionally, the first CN device is an AMF.

[0166] It is worth noting that, in the case where the first RAN device is a CU-DU separation architecture, the steps performed by the first RAN device in the above steps of this embodiment are performed by the CU of the first RAN device; further, in the case where the CU includes a CU-CP and a CU-UP, the steps performed by the first RAN device in the above steps are performed by the CU-CP of the first RAN device, and the CU-CP can save the terminal device computing capability information in the CU-CP or CU-UP. It should be understood that the terminal device interacts with the CU or CU-CP of the first RAN device through the DU of the first RAN device.

[0167] Through the above steps of this embodiment, the CN device and / or the RAN device connected to the CN device obtains the terminal device computing capability information of the terminal device, thereby enabling the CN device and / or the RAN device to utilize the computing capability of the terminal device in computing services.

[0168] The above-mentioned methods 300, 400 and 500 implement that the RAN device computing capability information of a RAN device is acquired by other RAN devices or CN devices, or the terminal device computing capability information of a terminal device is acquired by a RAN device or a CN device, so that the network can use the computing capability of a RAN device or a terminal device to provide computing services for another RAN device.

[0169] Figure 6 A flowchart of a method for requesting a RAN device to provide computing services is provided in an embodiment of the present application. The method 600 is applied to a scenario in which a RAN device (also referred to as a source RAN device) requests another RAN device (also referred to as a target RAN device) to provide computing services for the RAN device, wherein an Xn interface exists between the two RAN devices for communication. Figure 6 The process includes the following steps:

[0170] S601: A source RAN device determines a target RAN device.

[0171] In this step, the source RAN device determines a target RAN device that can provide computing services for it according to the RAN device computing capability information of other RAN devices acquired by it.

[0172] Exemplarily, the source RAN device may obtain the RAN device computing capability information of other RAN devices through interaction between RAN devices; the source RAN device may also obtain the RAN device computing capability information of other RAN devices stored on the CN device through interaction with the CN device.

[0173] Typically, the RAN device computing capability information includes the types of computing services supported by the RAN device; further, the RAN device computing capability information also includes the resources that the RAN device can use for various types of computing services in one or more types of computing services it supports. Exemplarily, if a RAN device supports two types of computing services, AI model #1 and AI model #2, the RAN device computing capability information may include the two types of computing services; further, the RAN device computing capability information may also include the CPU / GPU / storage resources that the RAN device can use for computing services of the AI ​​model #1 type, and the CPU / GPU / storage resources that can be used for computing services of the AI ​​model #2 type.

[0174] The source RAN device determines one or more RAN devices as target RAN devices in the other RAN devices according to the QoS requirements of the computing services to be performed and in combination with the RAN device computing capacity information of the other RAN devices obtained by the source RAN device, and the one or more target RAN devices are used to provide computing services for the source RAN device. In one possible implementation, one or more RAN devices in the other RAN devices can each meet the QoS requirements of the computing services of the source RAN device; in this case, the source RAN device determines one RAN device from the one or more RAN devices as the target RAN device. In another possible implementation, none of the other RAN devices can meet the QoS requirements of the computing services of the source RAN device alone; in this case, the source RAN device determines multiple RAN devices from the other RAN devices as target RAN devices, and the sum of the computing capacity of each RAN device in the multiple RAN devices can meet the QoS requirements of the computing services of the source RAN device. In another possible implementation, the source RAN device can determine multiple RAN devices as target RAN devices based on policies, such as for load balancing, fault tolerance, etc., and the sum of the computing capacity of each RAN device in the multiple RAN devices meets or exceeds the QoS requirements of the computing services of the source RAN device.

[0175] Exemplarily, the computing services required by the source RAN device include two types of computing services, AI model #1 and AI model #2, wherein the computing services of AI model #1 include computing service flow #1A and computing service flow #1B, and the computing services of AI model #2 include computing service flow #2A. In this step, in a possible implementation, the source RAN device determines a RAN device that can simultaneously support the computing service types of AI model #1 and AI model #2 as the target RAN device from the RAN device computing capability information of other RAN devices it obtains. Further, the source RAN device can also estimate the CPU / GPU / storage resources that each computing service flow needs to occupy according to the respective QoS requirements of computing service flow #1A, computing service flow #1B, and computing service flow #2A, and determine a RAN device that can simultaneously meet the QoS requirements of each computing service flow as the target RAN device in combination with the available CPU / GPU / storage resources of other RAN devices it obtains. In another possible implementation, the source RAN device can determine a RAN device that supports the computing service type of AI model #1 as a target RAN device, and another RAN device that supports the computing service type of AI model #2 as another target RAN device. In this way, the source RAN device determines that multiple target RAN devices respectively perform part of the computing services. In another possible implementation, the source RAN device may determine multiple RAN devices of computing service types that support both AI model #1 and AI model #2 as target RAN devices, so that each target RAN device respectively performs part of the computing services, or respectively performs all the computing services for backup or fault tolerance. It should be understood that the source RAN device may also determine the target RAN device in other ways, which is not specifically limited in this application.

[0176] S602: The source RAN device sends a sixth request to the target RAN device. Correspondingly, the target RAN device receives the sixth request from the source RAN device. The sixth request is used to instruct the source RAN device to request the target RAN device to provide a computing service.

[0177] The sixth request includes the QoS requirement of the computing service of the source RAN device.

[0178] It should be understood that the target RAN device in this step is any one of the one or more target RAN devices determined by the source RAN in the above step S601. If the source RAN device determines that the target RAN device is one RAN device in the above step S601, then in this step, the source RAN device sends a sixth request to the RAN device, and the sixth request is used to request the RAN device to provide all computing services for the source RAN device; if the source RAN device determines that the target RAN device is multiple RAN devices in the above step S601, then in this step, the source RAN device sends a sixth request to each of the multiple RAN devices, and the sixth request is used to request the RAN device to provide part or all of the computing services for the source RAN device.

[0179] Exemplarily, the sixth request includes one or more computing service flows requested by the source RAN device and resource information required by each computing service flow.

[0180] S603: The target RAN device performs admission control on the computing service request.

[0181] In this step, the target RAN device performs admission control on one or more computing service flows received from the source RAN device.

[0182] It should be understood that the target RAN device decides to accept one or more computing service flows from the source RAN device based on its own resource status and / or policies. In one possible implementation, the target RAN device accepts all computing service flows of the source RAN device in the sixth request; in another possible implementation, the target RAN device accepts part of the computing service flows of the source RAN device in the sixth request.

[0183] S604: The target RAN device sends a sixth response to the source RAN device. Accordingly, the source RAN device receives the sixth response from the target RAN device. The sixth response is a response of the target RAN device to the sixth request, and is used to indicate the computing service flow requested by the source RAN device and accepted by the target RAN device.

[0184] Specifically, the sixth response includes the identification information of one or more computing service flows requested by the source RAN device accepted by the target RAN device. In addition, the sixth response also includes the transport layer information of the target RAN device, for example, the Xn tunnel transport layer information of the target RAN device (IP address and / or TEID of the target RAN device, etc.).

[0185] S605: The source RAN device interacts with the target RAN device for computing service data.

[0186] In this step, the source RAN device transmits data of one or more computing service flows to the target RAN device. It should be understood that the one or more computing service flows are computing service flows accepted by the target RAN device. The target RAN device processes the data of the one or more computing service flows, generates result data, and sends the result data to the source RAN device. Optionally, in the process of the target RAN device performing service calculation, the source RAN device and the target RAN device also exchange intermediate data of the computing service, that is, before the target RAN device generates the result data, it is necessary to exchange the intermediate data in the processing process with the source RAN device. It should be understood that in the case of multiple target RAN devices, this step is used for the interaction of computing service data between the source RAN device and each of the multiple target RAN devices.

[0187] It is worth noting that, in the case where the source RAN device is a CU-DU separation architecture, the steps executed by the source RAN device in the above steps of this embodiment are executed by the CU of the source RAN device; further, in the case where the CU includes a CU-CP and a CU-UP, the steps executed by the source RAN device in the above steps are executed by the CU-CP of the source RAN device. Similarly, in the case where the target RAN device is a CU-DU separation architecture, the steps executed by the target RAN device in the above steps of this embodiment are executed by the CU of the target RAN device; further, in the case where the CU includes a CU-CP and a CU-UP, the steps executed by the target RAN device in the above steps are executed by the CU of the target RAN device.

[0188] Through the above steps of this embodiment, the source RAN device directly communicates with the target RAN device, and the computing service of the source RAN device is implemented by using the target RAN device, which solves the problem that the source RAN device itself cannot complete the computing service.

[0189] In the above method 600, the source RAN device interacts with the target RAN device via the Xn interface, thereby using the target RAN device to implement the computing service of the source RAN device. In an actual network, the source RAN device and the target RAN device may not necessarily have an Xn interface. For example, when the two are deployed far apart, in this case, the source RAN device needs to interact with the target RAN device via the CN device.

[0190] Figure 7A flowchart of another method for requesting a RAN device to provide computing services provided by an embodiment of the present application. The method 700 is applied to a scenario in which a RAN device (also referred to as a source RAN device) requests another RAN device (also referred to as a target RAN device) to provide computing services for the RAN device, wherein the communication between the source RAN and the target RAN devices requires the source RAN to communicate with a second CN device, and then the second CN device communicates with the target RAN device to achieve. For example, the second CN device is connected to the source RAN device and the target RAN device respectively through an NG interface. Figure 7 The process includes the following steps:

[0191] S701: A source RAN device determines a target RAN device.

[0192] This step is similar to step S601 in the above-mentioned embodiment and will not be described again here.

[0193] The above step 701 is optional.

[0194] S702: The source RAN device sends a seventh request to the second CN device. Correspondingly, the second CN device receives the seventh request from the source RAN device.

[0195] In a possible implementation, when the source RAN device determines the target RAN device in the above step S701, the seventh request is used to instruct the source RAN device to request the target RAN device to provide computing services. At this time, in addition to the content of the sixth request in the above embodiment, the seventh request also includes the identification information of each target RAN device in the one or more target RAN devices determined by the source RAN device.

[0196] In another possible implementation, when this embodiment does not include step S701, the seventh request is used to instruct the source RAN device to request other RAN devices to provide computing services. At this time, the content included in the seventh request is the same as the content included in the sixth request in the above embodiment. At this time, the seventh request only instructs the source RAN device to request computing services provided by other RAN devices, and does not indicate which target RAN device(s) provide computing services.

[0197] S703: The second CN device determines a target RAN device.

[0198] In this step, the second CN device determines a target RAN device that can provide computing services for the source RAN device according to the RAN device computing capability information of different RAN devices acquired by the second CN device.

[0199] Exemplarily, the second CN device may obtain the RAN device computing capability information of each RAN device through interaction with different RAN devices; the second CN device may also obtain the RAN device computing capability information of each RAN device from the RAN device computing capability information stored therein.

[0200] This step is similar to step S601 in the aforementioned embodiment and will not be described in detail here. The main difference is that in this step, the second CN device determines one or more RAN devices as target RAN devices based on the QoS requirement of the computing service obtained in step S702 and the RAN device computing capability information of each RAN device obtained by it, while in the aforementioned embodiment, the source RAN device determines one or more RAN devices as target RAN devices based on the QoS requirement of the computing service to be performed and the RAN device computing capability information of each RAN device obtained by it.

[0201] The above step S703 is optional. If this embodiment includes step S701, then step S703 may not be included; if this embodiment does not include step S701, then step S703 may be included.

[0202] S704: The second CN device sends an eighth request to the target RAN device. Correspondingly, the target RAN device receives the eighth request from the second CN. The eighth request is used to instruct the source RAN device to request the target RAN device to provide computing services.

[0203] In a possible implementation, if the embodiment includes the above step S701, in this step, the second CN device sends the eighth request to each target RAN device indicated by the identification information of the one or more target RAN devices obtained from the seventh request in the above step S702. In another possible implementation, if the embodiment includes the above step S703, in this step, the second CN device sends the eighth request to the one or more target RAN devices determined by it.

[0204] S705: The target RAN device performs admission control on the computing service request.

[0205] S706: The target RAN device sends an eighth response to the second CN device. Accordingly, the second CN device receives the eighth response from the target RAN device. The eighth response is a response of the target RAN device to the eighth request, and is used to indicate the computing service flow requested by the source RAN device and accepted by the target RAN device.

[0206] Specifically, the eighth response includes identification information of one or more computing service flows requested by the source RAN device accepted by the target RAN device. In addition, the eighth response also includes transport layer information of the target RAN device, for example, Xn tunnel transport layer information of the target RAN device.

[0207] The above steps S704-S706 are similar to steps S602-S604 in the aforementioned embodiment and will not be repeated here. The main difference is that in this embodiment, the second CN device requests the target RAN device to perform the computing service of the source RAN device, while in the aforementioned implementation, the source RAN device requests the target RAN device to perform the computing service of the source RAN device.

[0208] S707: The second CN device sends a seventh response to the source RAN device. Accordingly, the source RAN device receives the seventh response from the second CN device. The seventh response is a response of the second CN device to the seventh request, and is used to indicate the computing service flow requested by the source RAN device and accepted by the target RAN device.

[0209] Specifically, the seventh response includes identification information of each of the one or more target RAN devices, and identification information of one or more computing service flows requested by the source RAN device accepted by each target RAN device. In addition, the eighth response also includes transport layer information of each target RAN device, for example, Xn tunnel transport layer information of each target RAN device.

[0210] S708. The source RAN device interacts with the target RAN device for computing service data.

[0211] This step is similar to step S605 in the above-mentioned embodiment and will not be described in detail here.

[0212] It is worth noting that, in the case where the source RAN device is a CU-DU separation architecture, the steps executed by the source RAN device in the above steps of this embodiment are executed by the CU of the source RAN device; further, in the case where the CU includes a CU-CP and a CU-UP, the steps executed by the source RAN device in the above steps are executed by the CU-CP of the source RAN device. Similarly, in the case where the target RAN device is a CU-DU separation architecture, the steps executed by the target RAN device in the above steps of this embodiment are executed by the CU of the target RAN device; further, in the case where the CU includes a CU-CP and a CU-UP, the steps executed by the target RAN device in the above steps are executed by the CU of the target RAN device.

[0213] Through the above steps of this embodiment, the source RAN device communicates with the target RAN device through the CN device, and the target RAN device is used to implement the computing service of the source RAN device, thereby solving the problem that the source RAN device itself cannot complete the computing service.

[0214] In the above method 700, both the source RAN device and the target RAN device are connected to the second CN device through the NG interface. In an actual network, the source RAN device and the target RAN device may not both be connected to the second CN device. In this case, the second CN device needs to communicate with the target RAN device through other CN devices. At this time, the second CN device is called the source CN device, and the other CN devices that the source CN device needs to communicate with the target RAN device through are called target CN devices. This process is also called CN device redirection (relocation). In order to achieve CN device redirection, the source CN device needs to retrieve the CN device to which the target RAN device is connected from a network management device. In this application, the network management device is called a computing configuration function (CCF). It should be understood that this name is only exemplary. Other names can also be used in an actual network, and this application does not specifically limit this. CCF has the following functions: retrieving and providing AMF configuration information that supports specific computing services, computing service discovery across AMFs, and application layer data interaction.

[0215] Figure 8 A schematic flow chart of a method for a source CN device to request a target RAN device to provide computing services provided in an embodiment of the present application. The method 800 corresponds to the functions completed by steps S704-S706 of the aforementioned embodiment, wherein Figure 8 The source CN device and the target RAN device correspond to Figure 7 The second CN device and the target RAN device in. Figure 8 The process includes the following steps:

[0216] S801. The source CN device retrieves target CN device information from the CCF.

[0217] In this step, the source CN device retrieves the target CN device information from the CCF. Specifically, the source CN device may send the identification information of each target RAN device in the one or more target RAN devices obtained in step S702 of the aforementioned embodiment to the CCF. The CCF determines the information of one or more target CN devices connected to the one or more target RAN devices based on the identification information, such as the identification information of the CN device, and then sends the identification information of the one or more target CN devices to the source CN device. Optionally, the CCF sends the identification information of the one or more target CN devices and the identification information of one or more target RAN devices to which each target CN device is connected to the source CN device.

[0218] Through this step, the source CN device obtains the identification information of one or more target CN devices corresponding to one or more target RAN devices. Exemplarily, the source CN device obtains the target RAN device #1, the target RAN device #2 and the target RAN device #3 in step S702 of the aforementioned embodiment, wherein the target RAN device #1 and the target RAN device #2 are connected to the target CN device #1, and the target RAN device #3 is connected to the target CN device #2. Optionally, through this step, the source CN device obtains the following two parts of information: one part of the information is the identification of the target CN device #1 and its corresponding identifications of the target RAN device #1 and the target RAN device #2; the other part of the information is the identification of the target CN device #2 and its corresponding identification of the target RAN device #3.

[0219] S802: The source CN device sends a ninth request to the target CN device. Correspondingly, the target CN device receives the ninth request from the source CN device. The ninth request is used to instruct the source RAN device to request the target RAN device to provide computing services.

[0220] Exemplarily, in the above example, the source CN device sends a ninth request to the target CN device #1, which includes the identifier of the target RAN device #1 and the computing service that the source RAN device requests the target RAN device #1 to provide, and the identifier of the target RAN device #2 and the computing service that the source RAN device requests the target RAN device #2 to provide. The source CN device sends a ninth request to the target CN device #2, which includes the identifier of the target RAN device #3 and the computing service that the source RAN device requests the target RAN device #3 to provide.

[0221] S803: The target CN device sends a tenth request to the target RAN device. Correspondingly, the target RAN device receives the tenth request from the target CN device. The tenth request is used to instruct the source RAN device to request the target RAN device to provide computing services.

[0222] Exemplarily, in the above example, the target CN device #1 sends the tenth request to the target RAN device #1, which includes the computing service that the source RAN device requests the target RAN device #1 to provide. The target CN device #1 sends the tenth request to the target RAN device #2, which includes the computing service that the source RAN device requests the target RAN device #2 to provide. The target CN device #2 sends the tenth request to the target RAN device #3, which includes the computing service that the source RAN device requests the target RAN device #3 to provide.

[0223] S804: The target RAN device performs admission control on the computing service request.

[0224] Exemplarily, in the above example, the target RAN device #1 performs admission control on one or more computing service flows that the source RAN device requests to provide computing services. The target RAN device #2 performs admission control on one or more computing service flows that the source RAN device requests to provide computing services. The target RAN device #3 performs admission control on one or more computing service flows that the source RAN device requests to provide computing services.

[0225] S805, the target RAN device sends a tenth response to the target CN device. Accordingly, the target CN device receives the tenth response from the target RAN device. The tenth response is a response of the target RAN device to the tenth request, and is used to indicate the computing service flow requested by the source RAN device and accepted by the target RAN device.

[0226] The above steps S803-S805 are similar to steps S602-S604 of the aforementioned embodiment and will not be repeated here. The main difference is that in this embodiment, the target CN device requests the target RAN device to perform the computing service of the source RAN device, while in the aforementioned implementation, the source RAN device requests the target RAN device to perform the computing service of the source RAN device.

[0227] S806. The target CN device sends a ninth response to the source CN device. Accordingly, the source CN device receives the ninth response from the target CN device. The ninth response is a response of the target CN device to the ninth request, and is used to indicate the computing service flow requested by the source RAN device accepted by the target RAN device connected to the target CN.

[0228] It is worth noting that, in the case where the target RAN device is a CU-DU separation architecture, the steps executed by the target RAN device in the above steps of this embodiment are executed by the CU of the target RAN device; further, in the case where the CU includes CU-CP and CU-UP, the steps executed by the target RAN device in the above steps are executed by the CU-CP of the target RAN device.

[0229] Through the above steps of this embodiment, the source CN device finds the target RAN device through CN device redirection. Further, this embodiment is combined with method 700 to achieve the source RAN device communicating with the target RAN device through CN device redirection, and the target RAN device is used to implement the computing service of the source RAN device, solving the problem that the source RAN device itself cannot complete the computing service.

[0230] The above methods 600, 700 and 800 enable the source RAN device to use other RAN devices to provide computing services for it. In an actual network, the RAN device can also use the resources of the terminal device to provide computing services for it. Fig. 9A flowchart of a method for requesting a terminal device to provide computing services provided by an embodiment of the present application is provided. The method 900 is applied to a scenario in which a RAN device requests a terminal device to provide computing services for the RAN device. Fig. 9 The process includes the following steps:

[0231] S901. The RAN device determines a target terminal device.

[0232] In this step, the RAN device determines one or more target terminal devices for which computing services can be provided based on the terminal device computing capability information of the one or more terminal devices it obtains. For example, the RAN device can obtain the terminal device computing capability information of any terminal device wirelessly connected to it through the aforementioned method 400 or method 500.

[0233] The RAN device determines one or more terminal devices as target terminal devices in the one or more terminal devices according to the QoS requirements of the computing service to be performed and the terminal device computing capacity information of the one or more terminal devices obtained by the RAN device, and the one or more target terminal devices are used to provide computing services for the RAN device. In one possible implementation, one or more terminal devices in the one or more terminal devices can each meet the QoS requirements of the computing service of the RAN device; in this case, the RAN device determines a terminal device from the one or more terminal devices as the target terminal device. In another possible implementation, none of the one or more terminal devices can meet the QoS requirements of the computing service of the RAN device alone; in this case, the RAN device determines multiple terminal devices from the one or more terminal devices as target terminal devices, and the sum of the computing capacity of each terminal device in the multiple terminal devices can meet the QoS requirements of the computing service of the RAN device. In another possible implementation, the RAN device can determine multiple terminal devices as target terminal devices based on policies, such as for load balancing, fault tolerance, etc., and the sum of the computing capacity of each terminal device in the multiple terminal devices meets or exceeds the QoS requirements of the computing service of the RAN device.

[0234] S902: The RAN device sends an eleventh request to the target terminal device. Correspondingly, the target terminal device receives the eleventh request from the RAN device. The eleventh request is used to instruct the RAN device to request the target terminal device to provide computing services.

[0235] S903: The target terminal device performs admission control on the computing service request.

[0236] S904: The target terminal device sends an eleventh response to the RAN device. Correspondingly, the RAN device receives the eleventh response from the terminal device.

[0237] The above steps S901-S904 are similar to steps S601-S604 in the aforementioned embodiment and will not be repeated here. The main difference is that in this embodiment, the RAN device determines the target terminal device and requests the target terminal device to execute the computing service of the RAN device, while in the aforementioned implementation, the source RAN device determines the target RAN device and requests the target RAN device to execute the computing service of the source RAN device.

[0238] It should be understood that the terminal device can be in a variety of RRC states, such as an RRC connected state, an RRC inactive state, or an RRC idle state. In this embodiment, if the target terminal device is in an RRC connected state, the RAN device can directly send the eleventh request to the target terminal device. If the target terminal device is in an RRC inactive state, the RAN device needs to page the target terminal device to restore the RRC connection. If the target terminal device is in an RRC idle state, the RAN device needs to page the target terminal device to enter an RRC connected state. It should be noted that the eleventh response contains the identification information of each of the one or more computing service flows requested by the RAN device accepted by the target terminal device.

[0239] S905, the RAN device sends first configuration information to the target terminal device. Correspondingly, the target terminal device receives the configuration information from the RAN device. The first configuration information is used to perform RRC configuration on the target terminal device, such as configuring the operating environment of the computing service on the target terminal device.

[0240] Optionally, the RRC reconfiguration message sent by the RAN device to the target terminal device carries the first configuration information.

[0241] S906: The target terminal device interacts with the RAN device for computing service data.

[0242] In this step, the RAN device transmits data of one or more computing service flows to the target terminal device. It should be understood that the one or more computing service flows are computing service flows accepted by the target terminal device. In one possible implementation, the target terminal device processes the data of the one or more computing service flows, generates result data, and sends the result data to the RAN device. In another possible implementation, in the process of the target terminal device performing service calculation, the RAN device and the target terminal device also exchange intermediate data of the computing service, that is, before the target terminal device generates the result data, it is necessary to interact with the RAN device to process the intermediate data. It should be understood that in the case of multiple target terminal devices, this step is used for the interaction of computing service data between the RAN device and each of the multiple target terminal devices.

[0243] It is worth noting that, in the case where the RAN device is a CU-DU separation architecture, the steps performed by the RAN device in the above steps of this embodiment are performed by the CU of the RAN device; further, in the case where the CU includes a CU-CP and a CU-UP, the steps performed by the RAN device in the above steps are performed by the CU-CP of the RAN device. It should be understood that the terminal device implements interaction with the CU or CU-CP of the RAN device through the DU of the RAN device to which it is wirelessly connected.

[0244] Through the above steps of this embodiment, the RAN device requests a specific terminal device to implement the computing service of the RAN device, thereby solving the problem that the source RAN device itself cannot complete the computing service.

[0245] In the above method 900, the RAN device determines the target terminal device based on the terminal device computing capability information obtained from the process of reporting computing capability information of multiple terminal devices. In another possible implementation, the first RAN device can obtain a terminal device that can meet its computing service requirements by broadcasting its computing service requirements, and use the computing capability of the device to complete the computing service.

[0246] Fig.10 Another method flow chart of requesting a terminal device to provide computing services provided by an embodiment of the present application is shown in FIG. 1000. The method 1000 is applied to a scenario in which a RAN device broadcasts its computing service requirements and the terminal device responds by providing computing services for the RAN device. Fig.10 The process includes the following steps:

[0247] S1001. RAN equipment broadcasts computing service demand information.

[0248] In this step, the RAN device broadcasts its computing service requirement information. Optionally, the RAN device includes its computing service requirement information in the system information and broadcasts it through the cell. Generally, the computing service requirement information includes one or more computing service types requested by the RAN device; further, the computing service requirement information also includes the respective QoS requirements of one or more computing service flows in the computing services of each type of the one or more computing service types.

[0249] S1002. The terminal device performs access control on computing service requirements.

[0250] In this step, the terminal device performs access control on the received computing service demand. It should be understood that the terminal device decides whether to accept the computing service demand from the RAN device based on its own resource status and / or policy. In one possible implementation, if the computing service demand includes the type of computing service, the terminal device decides the type of computing service it provides. In another possible implementation, if the computing service demand also includes the QoS requirement of the computing service flow, the terminal device decides to accept some or all of the computing service flows.

[0251] S1003: The terminal device sends first admission information to the RAN device. Correspondingly, the RAN device receives the first admission information from the terminal device. The first admission information is used to indicate the type of computing service or computing service flow requested by the RAN device to be accepted by the terminal device.

[0252] If the terminal device determines the type of computing service it accepts in step S1002, the first access information includes the type of computing service accepted by the terminal device. Furthermore, the first access information also includes the resources that the terminal device can provide computing services, such as GPU / CPU / storage resources. If the terminal device determines that it accepts the computing service flow in step S1002, the first access information includes the identification information of each computing service flow in one or more computing service flows accepted by the terminal device.

[0253] S1004. The RAN device determines a target terminal device.

[0254] In this step, the RAN device determines the target terminal device according to the first access information. This step is similar to step S601 in the aforementioned embodiment and will not be described in detail here. The main difference is that in this step, the RAN device determines one or more terminal devices as target terminal devices based on the QoS requirements of the computing service to be performed by it and the first access information obtained in the aforementioned step S1003, while in the aforementioned embodiment, the source RAN device determines one or more RAN devices as target RAN devices based on the QoS requirements of the computing service to be performed by it and the RAN device computing capacity information of each RAN device obtained by it.

[0255] S1005. The RAN device sends second configuration information to the terminal device. Correspondingly, the terminal device receives the second configuration information from the RAN device. The second configuration information is used to perform RRC configuration on the terminal device, such as configuring the operating environment of the computing service on the terminal device.

[0256] It should be understood that, in the case where multiple terminal devices send the first access information to the RAN device, the terminal device in this step is any one of the one or more target terminal devices determined by the RAN device in the above step S1004.

[0257] S1006. The terminal device interacts with the RAN device for computing service data.

[0258] The above steps S1005 and S1006 are similar to the steps S905 and S906 of the above embodiment, respectively, and are not described again here.

[0259] It is worth noting that, in the case where the RAN device is a CU-DU separation architecture, the steps performed by the RAN device in the above steps of this embodiment are performed by the CU of the RAN device; further, in the case where the CU includes a CU-CP and a CU-UP, the steps performed by the RAN device in the above steps are performed by the CU-CP of the RAN device. It should be understood that the terminal device implements interaction with the CU or CU-CP of the RAN device through the DU of the RAN device.

[0260] Through the above steps of this embodiment, the RAN device broadcasts computing service requirements and selects appropriate terminal devices from terminal devices that meet the requirements to implement the computing services of the RAN device, thereby solving the problem that the source RAN device itself cannot complete the computing service.

[0261] When RAN equipment uses terminal equipment to provide computing services, the terminal equipment may switch from one cell to another cell during the process of providing computing services due to the mobility of the terminal equipment. The switching of terminal equipment may cause the interruption of computing services. In order to ensure the continuity of computing services, one implementation method is to transfer the unfinished computing services provided by the original terminal equipment to other terminal equipment for execution; another implementation method is to switch the computing services following the movement of the terminal equipment.

[0262] Fig.11 A flow chart of a method for a RAN device to transfer computing services between terminal devices provided in an embodiment of the present application. The method 1100 is applied to a scenario in which a RAN device transfers computing services from a terminal device (also called a source terminal device) currently providing computing services for the RAN device to other terminal devices (also called target terminal devices) served by the RAN device. Fig.11 The process includes the following steps:

[0263] S1101. The serving RAN device determines to transfer computing services.

[0264] Transferring computing services refers to transferring the unfinished part of the computing services executed by the source terminal device to the target terminal device for execution. Among them, the computing services executed by the source terminal device may be some or all of the computing services required by the service RAN device. In this step, the service RAN device determines to transfer the computing services from the source terminal device to the target terminal device for execution. It should be understood that the service RAN device is a RAN device that provides communication services for the source terminal device and the target terminal device at the current moment. The source terminal device provides computing services for the service RAN device at the current moment, and the target terminal device may provide computing services for the service RAN device at the current moment or may not provide computing services for the service RAN device. In one possible implementation, the service RAN device determines that the source terminal device will switch to a cell controlled by other RAN devices, and the service RAN device determines to transfer the computing services executed by the source terminal device to the target terminal device. In another possible implementation, the service RAN device determines to transfer the computing services executed by the source terminal device to the target terminal device based on load and / or policy. In this case, the source terminal device may not be switched. It should be noted that the target terminal device may be one or more terminal devices, that is, the service RAN device can transfer the computing services of a source terminal device to one or more target terminal devices for execution.

[0265] The service RAN device determines one or more terminal devices as target terminal devices based on the computing service information currently assigned to the source terminal device (such as which computing services the source terminal device is assigned to perform and the QoS characteristics of the computing service flow to be performed, etc.), combined with the terminal device computing capacity information of multiple terminal devices obtained by it, and the one or more target terminal devices are used to undertake the computing service of the current source terminal device. It should be understood that the target terminal device undertakes the computing service of the source terminal device, which means that the target terminal device continues to perform the unfinished part of the computing service performed by the source terminal device. In one possible implementation, there are one or more terminal devices that can each undertake the computing service provided by the source terminal device; in this case, the service RAN device determines a terminal device from the one or more terminal devices as the terminal RAN device. In another possible implementation, no terminal device can independently undertake the computing service provided by the source terminal device; in this case, the service RAN device determines multiple terminal devices as target terminal devices, and the sum of the computing capacity of each terminal device in the multiple terminal devices can meet the QoS requirements of the computing service provided by the source terminal device. In another possible implementation, the service RAN device may intentionally determine multiple terminal devices as target terminal devices based on policies, such as for load balancing, fault tolerance, etc., and the sum of the computing capabilities of each of the multiple terminal devices meets or exceeds the QoS requirements of the computing service provided by the source terminal device.

[0266] S1102, the service RAN device sends a twelfth request to the target terminal device. Correspondingly, the target terminal device receives the twelfth request from the service RAN device. The twelfth request is used to instruct the service RAN device to request the target terminal device to undertake all or part of the computing services of the source terminal device.

[0267] S1103: The target terminal device performs access control on the computing service request.

[0268] S1104, the target terminal device sends a twelfth response to the serving RAN device. Accordingly, the serving RAN device receives the twelfth response from the target terminal device. The twelfth response is a response of the target terminal device to the twelfth request, and is used to indicate the computing service flow of the source terminal device accepted by the target terminal device.

[0269] The above steps S1102-S1104 are similar to steps S602-S604 of the aforementioned embodiment, and will not be repeated here. The main difference is that in this embodiment, the service RAN device requests the target terminal device to undertake the computing service of the source terminal device, while in the aforementioned implementation, the source RAN device requests the target RAN device to perform the computing service of the source RAN device.

[0270] S1105. The service RAN device interacts with the source terminal device in intermediate computing service data and context transfer.

[0271] In this step, the service RAN device instructs the source terminal device to end the current service calculation, and obtains the intermediate data in the service calculation processing process, as well as the context information of the current calculation service (such as service processing status and progress, etc.).

[0272] S1106: The serving RAN device sends third configuration information to the target terminal device. Accordingly, the target terminal device receives the third configuration information from the serving RAN device. The third configuration information is used to perform RRC configuration on the target terminal device, such as configuring the operating environment of the computing service on the target terminal device.

[0273] S1107. The service RAN device interacts with the target terminal device to perform computing service data.

[0274] In this step, the service RAN device transmits data of one or more computing service flows to the target terminal device. Optionally, the service RAN device transmits context information of the computing service to the target terminal device. It should be understood that the one or more computing service flows are partial computing service flows that have not been completed by the source terminal device, and the target terminal device now carries the partial computing service flows. The target terminal device continues to execute the partial computing service flows, generates result data, and sends the result data to the service RAN device. Optionally, in the process of the target terminal device performing the service calculation, the target terminal device and the service RAN device also exchange intermediate data of the computing service, that is, before the target terminal device generates the result data, the intermediate data in the interactive processing process of the service RAN device is required. It should be understood that in the case of multiple target terminal devices, this step is used for the interaction of computing service data between the service RAN device and each of the multiple target terminal devices.

[0275] It is worth noting that, in the case where the service RAN device is a CU-DU separation architecture, the steps performed by the service RAN device in the above steps of this embodiment are performed by the CU of the service RAN device; further, in the case where the CU includes a CU-CP and a CU-UP, the steps performed by the service RAN device in the above steps are performed by the CU-CP of the service RAN device. It should be understood that the source terminal device interacts with the CU or CU-CP of the service RAN device through the DU of the service RAN device to which it is wirelessly connected, and the target terminal device interacts with the CU or CU-CP of the service RAN device through the DU of the service RAN device to which it is wirelessly connected.

[0276] Through the above steps of this embodiment, the RAN device transfers the computing service between terminal devices, thereby ensuring the continuity of the computing service.

[0277] Fig.12 A flowchart of a method for a RAN device to switch computing services following the movement of a terminal device is provided in an embodiment of the present application. The method 1200 is applied to a scenario in which, as the terminal device providing computing services for the RAN device switches, the terminal device continues to provide computing services in the cell after the switch. Fig.12 The process includes the following steps:

[0278] S1201. The terminal device interacts with the source RAN device for computing service data.

[0279] In this step, the terminal device provides computing services for the source RAN device. Specifically, the source RAN device transmits data of one or more computing service flows to the terminal device. The terminal device processes the one or more computing service flows and can exchange intermediate processing data with the source RAN device during the processing.

[0280] S1202: The source RAN device determines that a terminal device is switched.

[0281] In this step, the source RAN device can determine that the terminal device is about to be switched in a variety of ways. In one possible implementation, the source RAN device receives a report of the terminal device's measurement results of the signal strength of multiple cells, and determines that the terminal device is about to be switched to a neighboring cell controlled by the target RAN device based on the report. In another implementation, the source RAN device determines to switch the terminal device to a neighboring cell controlled by a target RAN device with a lower load based on a load balancing strategy.

[0282] S1203: The source RAN device sends a thirteenth request to the target RAN device. Correspondingly, the target RAN device receives the thirteenth request from the source RAN device. The thirteenth request is used by the source RAN device to request the target RAN device to forward computing service data.

[0283] In one possible implementation, the thirteenth request may be one-bit indication information, which is used to indicate that the source RAN device requests the target RAN device to forward the computing service data. In this case, the source RAN device also sends the transport layer information of the source RAN device to the target RAN device, and the transport layer information is used to interact with the target RAN device. In another possible implementation, the thirteenth request may be a message, which is used to indicate that the source RAN device requests the target RAN device to forward the computing service data. In this case, the thirteenth request also includes the transport layer information of the source RAN device.

[0284] S1204: The target RAN device sends a thirteenth response to the source RAN device. Accordingly, the source RAN device receives the thirteenth response from the target RAN device. The thirteenth response is a response of the target RAN device to the thirteenth request. The thirteenth response is used to indicate that the target RAN device accepts the thirteenth request.

[0285] The thirteenth response includes the transport layer information of the target RAN device, which is used to interact with the source RAN device for data exchange. In addition, the thirteenth response also includes the configuration information of the target RAN device for implementing interactive computing service data with the terminal device, such as DRB configuration.

[0286] S1205. The source RAN device sends fourth configuration information to the terminal device. Correspondingly, the terminal device receives the fourth configuration information from the source RAN device. The fourth configuration information is used by the source RAN device to forward the configuration information received by the source RAN device in the thirteenth response to the terminal device.

[0287] S1206. The terminal device implements interaction of computing service data with the source RAN device through the target RAN device.

[0288] After receiving the fourth configuration information, the terminal device performs random access and accesses the target RAN device to complete the switching of the terminal device. After the terminal device completes the switching, the target RAN device provides services for the terminal device.

[0289] The computing service that the terminal device has not completed before the switching is continued to be executed by the terminal device after the switching. In one possible implementation, the terminal device still needs to exchange the intermediate data of the computing service with the source RAN device during the computing service after the switching. In this case, the terminal device exchanges the intermediate data with the target RAN device through the air interface, and then the target RAN device forwards the intermediate data through the communication between the source RAN device, thereby realizing the data interaction between the terminal device and the source RAN device. In another possible implementation, the terminal device does not need to exchange the intermediate data of the computing service with the source RAN device during the computing service after the switching. In this case, if the terminal device completes the computing service in the target cell, the result data of the computing service is sent to the source RAN device through the target RAN device. In another possible implementation, if the terminal device has not completed the computing service in the target cell, but will be switched to a cell controlled by other RAN devices again, the terminal device can exchange the intermediate data of the computing service currently completed by the terminal device with the source RAN device through the target RAN device before the switching.

[0290] It is worth noting that, in the case where the source RAN device is a CU-DU separation architecture, the steps performed by the source RAN device in the above steps of this embodiment are performed by the CU of the source RAN device; further, in the case where the CU includes CU-CP and CU-UP, the steps performed by the source RAN device in the above steps are performed by the CU-CP of the source RAN device. It should be understood that the terminal device implements the interaction with the CU or CU-CP of the source RAN device through the DU of the source RAN device to which it is wirelessly connected. In the case where the target RAN device is a CU-DU separation architecture, the steps performed by the target RAN device in the above steps of this embodiment are performed by the CU of the target RAN device; further, in the case where the CU includes CU-CP and CU-UP, the steps performed by the target RAN device in the above steps are performed by the CU-CP of the target RAN device. It should be understood that the terminal device implements the interaction with the CU or CU-CP of the target RAN device through the DU of the target RAN device to which it is wirelessly connected.

[0291] Through the above steps of this embodiment, the terminal device continues to execute the original computing service after switching, thereby ensuring the continuity of the computing service.

[0292] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium, (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state disk (SSD)), etc. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this patent application.

[0293] Combination of the above Figures 3 to 12The method embodiment of the present application is described in detail below. Figures 13 to 18 , describes in detail the device embodiment of the present application. It should be understood that the device embodiment corresponds to the method embodiment, and similar descriptions can refer to the method embodiment. It is worth noting that the device embodiment can be used in conjunction with the above method or alone.

[0294] Fig.13 A schematic block diagram of a terminal device 1300 according to an embodiment of the present application is shown. The terminal device 1300 may correspond to (for example, may be configured in or may be itself) the terminal device described in the above method 400, or the terminal device described in the above method 500, or the target terminal device described in the above method 900, or the terminal device described in the above method 1000, or the source terminal device described in the above method 1100, or the target terminal device described in the above method 1100, or the terminal device described in the above method 1200, or the terminal device described in other embodiments. The terminal device 1300 may include: a processor 1301 and a transceiver 1302, the processor 1301 and the transceiver 1302 being communicatively coupled. Optionally, the terminal device 1300 also includes a memory 1303, and the memory 1303 is communicatively coupled to the processor 1301. Optionally, the processor 1301, the memory 1303 and the transceiver 1302 may be communicatively coupled, the memory 1303 may be used to store instructions, and the processor 1301 is used to execute the instructions stored in the memory 1303 to control the transceiver 1302 to receive and / or send information or signals. Among them, the processor 1301 and the transceiver 1302 are respectively used to execute the actions or processing procedures performed by the terminal device described in the above method 400, or the terminal device described in the above method 500, or the target terminal device described in the above method 900, or the terminal device described in the above method 1000, or the source terminal device described in the above method 1100, or the target terminal device described in the above method 1100, or the terminal device described in the above method 1200, or the terminal device described in other embodiments. Here, in order to avoid redundancy, the detailed description is omitted. In the case where the terminal device 1300 is a CU-DU separated architecture, Fig.13 The terminal device 1300 shown may be a CU, or a CU-CP.

[0295] Fig.14Another schematic block diagram of a terminal device 1400 according to an embodiment of the present application is shown. The terminal device 1400 may correspond to (for example, may be configured in or may be) the terminal device described in the above method 400, or the terminal device described in the above method 500, or the target terminal device described in the above method 900, or the terminal device described in the above method 1000, or the source terminal device described in the above method 1100, or the target terminal device described in the above method 1100, or the terminal device described in the above method 1200, or a terminal device described in other embodiments. The terminal device 1400 may include: a receiving module 1401, a processing module 1402 and a sending module 1403, wherein the processing module 1402 is communicatively coupled to the receiving module 1401 and the sending module 1403, respectively. The terminal device 1400 may adopt Fig.13 The processing module 1402 can be Fig.13 The processor 1301 in the embodiment can be implemented by the receiving module 1401 and / or the sending module 1403. Fig.13 The terminal device 1400 may further include a storage unit for storing programs or data to be executed by the processing module 1402, or storing information received by the receiving module 1401 and / or sent by the sending module 1403. Each module or unit in the terminal device 1400 is used to execute the actions or processing procedures performed by the terminal device described in the above method 400, or the terminal device described in the above method 500, or the target terminal device described in the above method 900, or the terminal device described in the above method 1000, or the source terminal device described in the above method 1100, or the target terminal device described in the above method 1100, or the terminal device described in the above method 1200, or the terminal device described in other embodiments. Here, in order to avoid redundancy, the detailed description is omitted. In the case where the terminal device 1400 is a CU-DU separated architecture, Fig.14 The terminal device 1400 shown may be a CU, or a CU-CP.

[0296] Fig.15A schematic block diagram of a RAN device 1500 according to an embodiment of the present application is shown. The RAN device 1500 may correspond to (for example, may be configured on or may itself be) the first RAN device described in the method 300, or the second RAN device described in the method 300, or the first RAN device described in the method 400, or the second RAN device described in the method 400, or the first RAN device described in the method 500, or the source RAN device described in the method 600, or the target RAN device described in the method 600, or the source RAN device described in the method 700, or the target RAN device described in the method 700, or the target RAN device described in the method 800, or the RAN device described in the method 900, or the RAN device described in the method 1000, or the serving RAN device described in the method 1100, or the source RAN device described in the method 1200, or the target RAN device described in the method 1200, or the RAN device described in other embodiments. The RAN device 1500 may include: a processor 1501 and a transceiver 1502, the processor 1501 and the transceiver 1502 being communicatively coupled. Optionally, the RAN device 1500 further includes a memory 1503, the memory 1503 being communicatively coupled to the processor 1501. Optionally, the processor 1501, the memory 1503 and the transceiver 1502 may be communicatively coupled, the memory 1503 may be used to store instructions, and the processor 1501 is used to execute the instructions stored in the memory 1503 to control the transceiver 1502 to receive and / or send information or signals. Among them, the processor 1501 and the transceiver 1502 are respectively used to execute the first RAN device described in the above method 300, or the second RAN device described in the above method 300, or the first RAN device described in the above method 400, or the second RAN device described in the above method 400, or the first RAN device described in the above method 500, or the source RAN device described in the above method 600, or the target RAN device described in the above method 600, or the source RAN device described in the above method 700, or the target RAN device described in the above method 700, or the target RAN device described in the above method 800, or the RAN device described in the above method 900, or the RAN device described in the above method 1000, or the serving RAN device described in the above method 1100, or the source RAN device described in the above method 1200, or the target RAN device described in the above method 1200, or the RAN device described in other embodiments, each action or processing process performed. Here, in order to avoid redundancy, its detailed description is omitted. In the case where the RAN device 1500 is a CU-DU separated architecture, Fig.15 The RAN device 1500 shown may be a CU, or a CU-CP.

[0297] Fig.16 Another schematic block diagram of a RAN device 1600 according to an embodiment of the present application is shown. The RAN device 1600 may correspond to (for example, may be configured on or may itself be) the first RAN device described in the method 300, or the second RAN device described in the method 300, or the first RAN device described in the method 400, or the second RAN device described in the method 400, or the first RAN device described in the method 500, or the source RAN device described in the method 600, or the target RAN device described in the method 600, or the source RAN device described in the method 700, or the target RAN device described in the method 700, or the target RAN device described in the method 800, or the RAN device described in the method 900, or the RAN device described in the method 1000, or the serving RAN device described in the method 1100, or the source RAN device described in the method 1200, or the target RAN device described in the method 1200, or the RAN device described in other embodiments. The RAN device 1600 may include: a receiving module 1601, a processing module 1602 and a sending module 1603, wherein the processing module 1602 is communicatively coupled to the receiving module 1601 and the sending module 1603 respectively. Fig.15 The processing module 1602 can be Fig.15 The processor 1501 in the embodiment can be implemented by the receiving module 1601 and / or the sending module 1603. Fig.15The RAN device 1600 may further include a storage unit for storing a program or data to be executed by the processing module 1602, or for storing information received by the receiving module 1601 and / or sent by the sending module 1603. Each module or unit in the RAN device 1600 is used to execute the actions or processing procedures performed by the first RAN device described in the above method 300, or the second RAN device described in the above method 300, or the first RAN device described in the above method 400, or the second RAN device described in the above method 400, or the first RAN device described in the above method 500, or the source RAN device described in the above method 600, or the target RAN device described in the above method 600, or the source RAN device described in the above method 700, or the target RAN device described in the above method 700, or the target RAN device described in the above method 800, or the RAN device described in the above method 900, or the RAN device described in the above method 1000, or the serving RAN device described in the above method 1100, or the source RAN device described in the above method 1200, or the target RAN device described in the above method 1200, or the RAN device described in other embodiments. Here, in order to avoid redundancy, the detailed description is omitted. In the case where the RAN device 1600 is a CU-DU separated architecture, Fig.16 The RAN device 1600 shown may be a CU, or a CU-CP.

[0298] Fig.17A schematic block diagram of a CN device 1700 according to an embodiment of the present application is shown. The CN device 1700 may correspond to (for example, may be configured in or may be itself) the CN device described in the above method 300, or the CN device described in the above method 400, or the first CN device described in the above method 500, or the second CN device described in the above method 700, or the source CN device described in the above method 800, or the CCF described in the above method 800, or the target CN device described in the above method 800, or the CN device described in other embodiments. The CN device 1700 may include: a processor 1701 and a transceiver 1702, the processor 1701 and the transceiver 1702 being communicatively coupled. Optionally, the CN device 1700 also includes a memory 1703, the memory 1703 being communicatively coupled to the processor 1701. Optionally, the processor 1701, the memory 1703 and the transceiver 1702 may be communicatively coupled, the memory 1703 may be used to store instructions, and the processor 1701 is used to execute the instructions stored in the memory 1703 to control the transceiver 1702 to receive and / or send information or signals. Among them, the processor 1701 and the transceiver 1702 are respectively used to execute the actions or processing procedures performed by the CN device described in the above method 300, or the CN device described in the above method 400, or the first CN device described in the above method 500, or the second CN device described in the above method 700, or the source CN device described in the above method 800, or the CCF described in the above method 800, or the target CN device described in the above method 800, or the CN device described in other embodiments. Here, in order to avoid redundancy, its detailed description is omitted. In the case where the CN device 1700 is a CU-DU separated architecture, Fig.17 The CN device 1700 shown may be a CU, or a CU-CP.

[0299] Fig.18 Another schematic block diagram of a CN device 1800 according to an embodiment of the present application is shown. The CN device 1800 may correspond to (for example, may be configured in or may be) the CN device described in the above method 300, or the CN device described in the above method 400, or the first CN device described in the above method 500, or the second CN device described in the above method 700, or the source CN device described in the above method 800, or the CCF described in the above method 800, or the target CN device described in the above method 800, or the CN device described in other embodiments. The CN device 1800 may include: a receiving module 1801, a processing module 1802, and a sending module 1803. The processing module 1802 is communicatively coupled to the receiving module 1801 and the sending module 1803, respectively. The CN device 1800 may adopt Fig.17 The processing module 1802 can be Fig.17 The processor 1701 in the embodiment can be implemented by the receiving module 1801 and / or the sending module 1803. Fig.17 The CN device 1800 may further include a storage unit for storing programs or data to be executed by the processing module 1802, or for storing information received by the receiving module 1801 and / or sent by the sending module 1803. Each module or unit in the CN device 1800 is used to execute the actions or processing procedures performed by the CN device described in the above method 300, or the CN device described in the above method 400, or the first CN device described in the above method 500, or the second CN device described in the above method 700, or the source CN device described in the above method 800, or the CCF described in the above method 800, or the target CN device described in the above method 800, or the CN device described in other embodiments. Here, in order to avoid redundancy, the detailed description is omitted. In the case where the CN device 1800 is a CU-DU separated architecture, Fig.18 The CN device 1800 shown may be a CU, or a CU-CP.

[0300] It should be understood that the processor (1301, 1501, 1701) in the device embodiment of the present application can be a central processing unit (CPU), a network processor (NP), a hardware chip or any combination thereof. The above-mentioned hardware chip can be an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof. The above-mentioned PLD can be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL) or any combination thereof.

[0301] The memory (1303, 1503, 1703) in the device embodiments of the present application can be a volatile memory (volatile memory), such as a random-access memory (random-access memory, RAM); it can also be a non-volatile memory (non-volatile memory), such as a read-only memory (read-only memory, ROM), a flash memory (flash memory), a hard disk drive (hard disk drive, HDD) or a solid-state drive (solid-state drive, SSD); it can also be a combination of the above types of memory.

[0302] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication coupling shown or discussed can be through some interfaces, indirect coupling or communication coupling of devices or units, which can be electrical, mechanical or other forms.

[0303] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0304] In addition, each functional unit in each embodiment of the present patent application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0305] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this patent application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and contains several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the various embodiments of the method of this patent application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk, and other media that can store program codes.

[0306] The above are only specific implementations of this patent application, but the protection scope of this patent application is not limited thereto. Any technician familiar with the technical field can easily think of changes or replacements within the technical scope disclosed in this patent application, which should be included in the protection scope of this patent application. Therefore, the protection scope of this patent application should be based on the protection scope of the claims.

Claims

1. A method for implementing a computing service, characterized in that: include: A first radio access network RAN ​​device acquires computing capability information of a first communication device, where the first communication device is a second RAN device or a terminal device; The first RAN device sends a first request to the first communication device, where the first request is used to request the first communication device to perform a computing service of the first RAN device; The first RAN device receives a first response from the first communication device, where the first response is used to indicate a computing service of the first RAN device accepted by the first communication device; as well as The first RAN device exchanges data of computing services of the first RAN device accepted by the first communication device with the first communication device.

2. The method according to claim 1, characterized in that The computing capability information of the first communication device includes the type of computing services supported by the first communication device and available resource information.

3. The method according to claim 1, characterized in that The first request includes a quality of service (QoS) requirement for a computing service of the first RAN device; The first response includes at least one computing service flow of the first RAN device accommodated by the first communications device.

4. The method according to any one of claims 1 to 3, characterized in that The first RAN device acquires computing capability information of the first communication device, including: The first RAN device sends a second request to the first communication device, where the second request is used to request to obtain the computing capability information of the first communication device, and the first RAN device receives the computing capability information of the first communication device from the first communication device; or The first RAN device sends a second request to a second communication device, where the second request is used to request to obtain computing capability information of the first communication device, and the first RAN device receives the computing capability information of the first communication device from the second communication device.

5. The method according to any one of claims 1 to 3, characterized in that: The first RAN device acquires computing capability information of the first communication device, including: The first RAN device receives the computing capability information of the first communication device from the first communication device, and the first RAN device sends confirmation information to the first communication device, where the confirmation information is used to indicate that the first RAN device correctly receives the computing capability information of the first communication device; or The first RAN device receives computing capability information of the first communication device from a second communication device, and the first RAN device sends confirmation information to the second communication device, where the confirmation information is used to indicate that the first RAN device has correctly received the computing capability information of the first communication device.

6. The method according to claim 4, characterized in that In the case where the first communication device is a second RAN device, the second communication device is a core network CN device; or, In the case where the first communication device is a terminal device, the second communication device is the second RAN device or the CN device.

7. The method according to claim 6, characterized in that The first RAN device sending a first request to the first communication device includes: In a case where the first communication device is the second RAN device or the terminal device, the first RAN device determines that the first communication device is a target communication device according to the computing capability information of the first communication device, and the first RAN device sends the first request to the target communication device; or In the case where the first communication device is the second RAN device and the second communication device is the CN device, the first RAN device determines that the first communication device is the target communication device according to the computing capability information of the first communication device, and the first RAN device sends the first request to the target communication device through the second communication device.

8. A method for implementing a computing service, characterized in that: include: A first communication device receives a first request from a second communication device, where the first request is used to request the first communication device to perform a computing service of a first RAN device, and the first communication device is a second RAN device or a terminal device; The first communication device sends a first response to the second communication device, where the first response is used to indicate the computing service of the first RAN device accepted by the first communication device; as well as The first communication device exchanges data of a computing service of the first RAN device accommodated by the first communication device with the first RAN device.

9. The method according to claim 8, characterized in that Before the first communication device receives the first request from the second communication device, the method further includes: The first communication device generates computing capability information of the first communication device; The first communication device sends computing capability information of the first communication device to the second communication device.

10. The method according to claim 8 or 9, characterized in that: The first request includes a quality of service (QoS) requirement for a computing service of the first RAN device; The first response includes at least one computing service flow of the first RAN device accommodated by the first communications device.

11. The method according to claim 9, characterized in that The computing capability information of the first communication device includes the type of computing services supported by the first communication device and available resource information.

12. The method according to claim 8 or 9, characterized in that: Before the first communication device sends a first response to the second communication device, the method further includes: The first communication device performs admission control, where the admission control is used to determine the computing service of the first RAN device admitted by the first communication device.

13. The method according to claim 8 or 9, characterized in that: In the case where the first communication device is a second RAN device, the second communication device is the first RAN or CN device; or, In the case where the first communication device is a terminal device, the second communication device is the first RAN device.

14. The method according to claim 8 or 9, characterized in that In a case where the first communication device is the second RAN device and the second communication device is the first RAN device or a CN device, before the first communication device receives the first request from the second communication device, the method further includes: The second RAN device generates computing capability information of the second RAN device; The second RAN device sends computing capability information of the second RAN device to the second communication device.

15. The method according to claim 8 or 9, characterized in that: In a case where the first communication device is the terminal device and the second communication device is the first RAN device, before the first communication device receives the first request from the second communication device, the method further includes: The terminal device generates computing capability information of the terminal device, and the terminal device sends the computing capability information of the terminal device to the first RAN device; or, The terminal device generates computing capability information of the terminal device, and the terminal device sends the computing capability information of the terminal device to the first RAN device through a CN device.

16. A communication device, characterized in that: Applicable to a first radio access network RAN ​​device, comprising: A processing module, configured to obtain computing capability information of a first communication device, where the first communication device is a second RAN device or a terminal device; a sending module, communicatively coupled to the processing module, and configured to send a first request to the first communication device, wherein the first request is used to request the first communication device to perform a computing service of the first RAN device; a receiving module, communicatively coupled to the processing module, and configured to receive a first response from the first communication device, wherein the first response is used to indicate a computing service of the first RAN device accepted by the first communication device; The processing module is further configured to interact with the first communication device to obtain data of a computing service of the first RAN device accepted by the first communication device.

17. The communication device according to claim 16, characterized in that The computing capability information of the first communication device includes the type of computing services supported by the first communication device and available resource information.

18. The communication device according to claim 16, characterized in that The first request includes a quality of service (QoS) requirement for a computing service of the first RAN device; The first response includes at least one computing service flow of the first RAN device accommodated by the first communications device.

19. The communication device according to any one of claims 16 to 18, characterized in that: The processing module obtains computing capability information of the first communication device, including: The sending module sends a second request to the first communication device, where the second request is used to request to obtain the computing capability information of the first communication device, and the receiving module receives the computing capability information of the first communication device from the first communication device; or The sending module sends a second request to the second communication device, where the second request is used to request to obtain the computing capability information of the first communication device, and the receiving module receives the computing capability information of the first communication device from the second communication device.

20. The communication device according to any one of claims 16 to 18, characterized in that: The processing module obtains computing capability information of the first communication device, including: The receiving module receives the computing capability information of the first communication device from the first communication device, and the sending module sends confirmation information to the first communication device, where the confirmation information is used to indicate that the first RAN device correctly receives the computing capability information of the first communication device; or The receiving module receives the computing capability information of the first communication device from a second communication device, and the sending module sends confirmation information to the second communication device, where the confirmation information is used to indicate that the first RAN device has correctly received the computing capability information of the first communication device.

21. The communication device according to claim 19, characterized in that In the case where the first communication device is a second RAN device, the second communication device is a core network CN device; or In the case where the first communication device is a terminal device, the second communication device is the second RAN device or the CN device.

22. The communication device according to claim 21, characterized in that The sending module sends a first request to the first communication device, including: In a case where the first communication device is the second RAN device or the terminal device, the first RAN device determines that the first communication device is a target communication device according to the computing capability information of the first communication device, and the first RAN device sends the first request to the target communication device; or In the case where the first communication device is the second RAN device and the second communication device is the CN device, the first RAN device determines that the first communication device is the target communication device according to the computing capability information of the first communication device, and the first RAN device sends the first request to the target communication device through the second communication device.

23. A communication device, characterized in that: Applied to a first communication device, comprising: A receiving module, configured to receive a first request from a second communication device, wherein the first request is used to request the first communication device to perform a computing service of a first RAN device, and the first communication device is a second RAN device or a terminal device; a sending module, configured to send a first response to the second communication device, wherein the first response is used to indicate a computing service of the first RAN device accepted by the first communication device; A processing module is communicatively coupled to the receiving module and the sending module, and is used to interact with the first RAN device for data of a computing service of the first RAN device received by the first communication device.

24. The communication device according to claim 23, characterized in that Before the receiving module receives the first request from the second communication device, the method further includes: The processing module generates computing capability information of the first communication device; The sending module sends the computing capability information of the first communication device to the second communication device.

25. The communication device according to claim 23 or 24, characterized in that: The first request includes a quality of service (QoS) requirement for a computing service of the first RAN device; The first response includes at least one computing service flow of the first RAN device accommodated by the first communications device.

26. The communication device according to claim 24, characterized in that The computing capability information of the first communication device includes the type of computing services supported by the first communication device and available resource information.

27. The communication device according to claim 23 or 24, characterized in that: Before the sending module sends the first response to the second communication device, the method further includes: The processing module performs admission control, where the admission control is used to determine the computing service of the first RAN device admitted by the first communication device.

28. The communication device according to claim 23 or 24, characterized in that: In the case where the first communication device is a second RAN device, the second communication device is the first RAN or CN device; or, In the case where the first communication device is a terminal device, the second communication device is the first RAN device.

29. The communication device according to claim 23 or 24, characterized in that: In the case where the first communication device is the second RAN device and the second communication device is the first RAN device or a CN device, before the receiving module receives the first request from the second communication device, the method further includes: The processing module generates computing capability information of the second RAN device; The sending module sends the computing capability information of the second RAN device to the second communication device.

30. The communication device according to claim 23 or 24, characterized in that: In a case where the first communication device is the terminal device and the second communication device is the first RAN device, before the first communication device receives the first request from the second communication device, the method further includes: The processing module generates the computing capability information of the terminal device, and the sending module sends the computing capability information of the terminal device to the first RAN device; or, The processing module is configured to generate computing capability information of the terminal device, and the sending module sends the computing capability information of the terminal device to the first RAN device through a CN device.

31. A communication device, characterized in that: Applicable to a first radio access network RAN ​​device, comprising: at least one processor; and, A memory and a communication interface communicatively connected to the at least one processor; The memory stores instructions that can be executed by the at least one processor, and the at least one processor executes the method according to any one of claims 1 to 7 by executing the instructions stored in the memory.

32. A communication device, characterized in that: Applied to a first communication device, comprising: at least one processor; and, A memory and a communication interface communicatively connected to the at least one processor; The memory stores instructions that can be executed by the at least one processor, and the at least one processor executes the method as described in any one of claims 8 to 15 by executing the instructions stored in the memory.

33. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

34. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 8 to 15 is implemented.

Images