Communication method and communication apparatus

Abstract

A communication method and a communication apparatus, which can be applied to the technical field of communications. The method comprises: a first network element receiving first information from a terminal device, wherein the first information is used for requesting a computing service; and the first network element sending second information to the terminal device, wherein the second information is determined on the basis of computing resource information of a second network element, the second information is used for accepting or rejecting the request from the first information, and the second network element is used for providing the computing service. By means of the present application, the requirements of a computing service can be better satisfied.

Description

Communication methods and communication devices

[0001] This application claims priority to Chinese Patent Application No. 202411668115.8, filed on November 19, 2024, with the China National Intellectual Property Administration, entitled “Communication Method and Communication Device”, the entire contents of which are incorporated herein by reference. Technical Field

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

[0003] Computing resources (or computing power) are a crucial driving force for the development of artificial intelligence (AI). AI computing resources are typically provided by cloud platforms (such as application servers, AS). When terminal devices perform AI-related computing tasks, the relevant computing data can be transmitted to the cloud platform via communication networks, and the cloud platform then provides computing services to the terminal devices.

[0004] However, current communication networks are not well-suited to meet the demands of computing services. Summary of the Invention

[0005] This application provides a communication method and a communication device that can better meet the needs of computing services.

[0006] In a first aspect, embodiments of this application provide a communication method applied to a first network element. The method includes:

[0007] The system receives first information from a terminal device, which is used to request computing services; and sends second information to the terminal device. The second information is determined based on the computing resource information of the second network element, and is used to accept or reject the request of the first information. The second network element is used to provide computing services.

[0008] In this embodiment, the first network element is an access network element. For example, the first network element can be an access network device, a centralized unit (CU) or a distributed unit (DU), or a core network device (such as an access and mobility management function (AMF)). After receiving a computing service request from a terminal device, the first network element rejects or accepts the request based on the computing resource information of the second network element. The first network element can participate in the admission decision of computing service requests, rather than simply transmitting relevant data for computing services, thereby better meeting the needs of computing services.

[0009] In conjunction with the first aspect, in one possible implementation, the first information includes a first cause value and / or first calculation information, wherein the first cause value corresponds to a calculation service; the first calculation information includes the terminal device's computing capability information and / or computing requirement information.

[0010] In this embodiment, the first information can indicate that the terminal device has a computing service requirement through a first cause value. Alternatively, the first information can request a computing service through first computing information. The terminal device's computing capability information includes information on the computing services supported by the terminal device and / or the quality of service (QoS) information of the computing services supported by the terminal device. The terminal device's computing requirement information includes information on the computing services requested by the terminal settings and / or the QoS information of the computing services requested by the terminal device. Through the above information, the first network element can better determine whether the second network element can meet the computing service requirements of the terminal device, thereby making a better admission decision.

[0011] In conjunction with the first aspect, in one possible implementation, the first reason value is carried in the reason value field of the RRC establishment request message, the first reason value corresponds to the first access category and / or the first access identifier, and the first access category and / or the first access identifier corresponds to the computing service.

[0012] In this embodiment, the first reason value can be obtained by mapping the first access category and / or the first access identifier. For a terminal device in an RRC non-connected state (e.g., radio resource control (RRC) inactive state or RRC idle state), when the terminal device has computing service requirements, the terminal device can carry the first reason value in the RRC establishment request message to request the establishment of an RRC connection between the terminal device and the first network element, while simultaneously instructing the terminal device to request computing services. This allows for the reuse of the reason value field in the RRC establishment request message, reducing signaling overhead.

[0013] In conjunction with the first aspect, in one possible implementation, the first cause value is carried in the computation request message.

[0014] In this embodiment of the application, the computing request message is an RRC message. For a terminal device in the RRC connection state, when the terminal device has computing service requirements, it can carry a first reason value in the RRC message to indicate that the terminal device requests computing services.

[0015] In conjunction with the first aspect, in one possible implementation, the computing capacity information and / or computing demand information includes information on the first computing service; the computing resource information of the second network element includes information on the computing services supported by the second network element and the load information of the computing services of the second network element.

[0016] The second information is determined based on the computing resource information of the second network element. The second information is used to accept or reject the request of the first information, including: if the second network element supports the first computing service and the load allows, the second information is used to accept the request of the first information; or if the second network element supports the first computing service and the load does not allow, the second information is used to reject the request of the first information; or if the second network element does not support the first computing service, the second information is used to reject the request of the first information.

[0017] In this embodiment, the computing capability information includes information about the first computing service, indicating that the terminal device supports the first computing service. Alternatively, the computing demand information includes information about the first computing service, indicating that the terminal device requests the first computing service. "Load allowed" means that the computing service load of the second network element is relatively light, and it can still provide the first computing service to the terminal device. "Load not allowed" means that the computing service load of the second network element is too heavy, and it can no longer provide the first computing service to the terminal device. The first network element can determine whether the second network element can provide computing services to the terminal device based on the terminal device's computing capability information or computing demand information, the computing services supported by the second network element, and the load information of the second network element's computing services. This allows for better control of the computing services on the second network element, preventing excessive load on the second network element that would fail to meet the terminal device's computing service needs. Furthermore, it ensures the computing speed of the computing services being executed by the second network element, avoiding any impact on the computing services being executed by the second network element.

[0018] In conjunction with the first aspect, in one possible implementation, the second network element is an access network element or a core network element; the first information is used to request computing services, including: the first information is used to request the second network element to provide computing services to the terminal device.

[0019] In this embodiment, the second network element is a network element in the access network or core network that provides computing services. This second network element can be co-located with the first network element; for example, the first network element is a base station, and the functions of the second network element can be deployed on the base station. Alternatively, the second network element and the first network element can be directly connected. Providing computing services to the terminal device by the second network element can also be referred to as on-network computing. The transmission path between the second network element and the first network element is short, ensuring end-to-end latency for the computing services provided by the second network element. Therefore, the terminal device can request the second network element to provide computing services through first information to ensure end-to-end latency for the terminal device's computing services.

[0020] In conjunction with the first aspect, in one possible implementation, the second information is used to reject the request of the first information, and the method further includes:

[0021] Receive third information from the terminal device. The third information is used to request a third network element to provide computing services to the terminal device. The third network element is a network element in the data network or an edge application server (EAS).

[0022] In this embodiment of the application, when the access network or core network cannot provide computing services to the terminal device, the terminal device can request the EAS or network elements (such as AS) in the data network to provide computing services to the terminal device so that the computing services requested by the terminal device can be executed.

[0023] In conjunction with the first aspect, in one possible implementation, the second information is used to reject the request of the first information. The second information also indicates at least one of the following: a waiting time, the second network element being unable to provide computing services to the terminal device, information about the first cell, or instructing the terminal device to request computing services from the third network element. The waiting time is used to instruct the terminal device to re-request computing services from the second network element after the waiting time. The first cell supports computing services, and the third network element is a network element in the data network or an edge application server (EAS).

[0024] In this embodiment, when the second information rejects the terminal device's computing service request, the second information may carry a second reason value. The second reason value indicates a waiting time, allowing the terminal device to reselect and request computing services from the second network element after the waiting time, thus increasing the probability of the terminal device successfully requesting computing services. Alternatively, the second reason value indicates that the second network element cannot provide computing services to the terminal device, allowing the terminal device to determine whether to perform local computing or request computing from another network element based on the second reason value. Alternatively, the second reason value indicates information about the first cell, allowing the terminal device to reselect to the first cell, which then provides computing services to the terminal device. Alternatively, the second reason value indicates that the terminal device requests computing services from a third network element, enabling the requested computing services to be executed.

[0025] In conjunction with the first aspect, in one possible implementation, the second network element is an edge computing server, and the first information is used to request computing services, including: the first information is used to request the second network element to provide computing services for terminal devices.

[0026] In conjunction with the first aspect, in one possible implementation, the method further includes: receiving computing resource information from the second network element.

[0027] In this embodiment of the application, the first network element can receive the computing resource information of the second network element from the second network element or other core network elements (such as AMF or CMF) so as to perform access control on the computing service requests of the terminal device based on the computing resource information of the second network element.

[0028] In conjunction with the first aspect, in one possible implementation, the computing resource information of the second network element includes at least one of the following: the load information of the computing services of the second network element, the information of the computing services supported by the second network element, and the QoS information of the computing services supported by the second network element.

[0029] In conjunction with the first aspect, in one possible implementation, the method further includes: sending a first broadcast message, the first broadcast message including access control information, the access control information being determined based on the computing resource information of the second network element.

[0030] In this embodiment, access control information is used by the terminal device to access the first network element, or in other words, the access control information is used by the terminal device to attempt to access the network. This access control information is determined based on the computing resource information of the second network element. When the terminal device has computing service requirements, it determines whether it is allowed to attempt access based on this access control information, thereby determining whether the terminal device is allowed to request computing services. Through this access control information, the computing resource information of the second network element can influence whether the terminal device is allowed to request computing services, allowing the terminal device to assess the computing status of the second network element in advance, thereby better ensuring the performance requirements of the terminal device's computing services.

[0031] In this application embodiment, "the terminal device is allowed to attempt access" can also be understood as "the terminal device is allowed to request computing services". That is, in this application, "the terminal device is allowed to attempt access" and "the terminal device is allowed to request computing services" can be used interchangeably.

[0032] In conjunction with the first aspect, in one possible implementation, the access control information includes access parameters corresponding to the first access category, and the first access category corresponds to the computing service.

[0033] In this embodiment, each access attempt by a terminal device corresponds to one access category, which indicates the type of access the terminal device is attempting. When a terminal device triggers an access attempt due to computing service requirements, it corresponds to the first access category. The first access category can be an access category specifically for the corresponding computing service, and the access parameters corresponding to the first access category are computing-specific access control parameters. These access parameters can be used to control whether the terminal device is allowed to request computing services. Alternatively, the first access category may not be a computing-specific access category. For example, computing services and other access attempt types (such as paging-triggered user NAS signaling transmission) may both correspond to the first access category. In this case, a computing service-specific access identifier (called the first access identifier) ​​can be defined, and the access parameters corresponding to the first access category can be used to indicate whether the first access identifier is allowed to access, thereby controlling whether the corresponding terminal device is allowed to request computing services.

[0034] In conjunction with the first aspect, in one possible implementation, the access parameters corresponding to the first access category include at least one of the following: first indication information, prohibition time, prohibition factor, and number of attempts. The first indication information indicates that the access identifier corresponding to the terminal device is allowed to attempt access; the prohibition time indicates the waiting time for the terminal device to retry access after a failed access attempt; the prohibition factor indicates the probability that the terminal device will successfully attempt access; and the number of attempts indicates the maximum number of times the terminal device can attempt access.

[0035] Secondly, embodiments of this application provide a communication method that can be applied to the terminal side, such as a terminal device or a communication module within the terminal device, or a circuit or chip (such as a modem chip, also known as a baseband chip, or a system-on-a-chip (SoC) chip containing a modem core, or a system-in-package (SIP) chip) responsible for communication functions within the terminal device. Taking the application of this method to a terminal device as an example, in this method, the terminal device receives a first broadcast message, which includes access control information determined based on the computing resource information of a second network element. The terminal device determines to send first information based on the access control information, and the first information is used to request computing services.

[0036] In this embodiment, the access control information is used by the terminal device to access the first network element, or in other words, the access control information is used by the terminal device to attempt access. The terminal device can determine whether to allow the attempt to access based on the access control information. The access control information is determined based on the computing resource information of the second network element. For example, the access control information includes access control information corresponding to computing services, used to indicate whether the terminal device is allowed to request computing services. The terminal device can assess the computing status of the second network element in advance based on the access control information, thereby determining whether to initiate a computing service request. For example, when the computing status of the second network element is good (e.g., light load), it is determined to send the first information to request computing services, which can better guarantee the performance requirements of the terminal device's computing services. Conversely, when the computing status of the second network element is poor (e.g., heavy load), it is determined not to send the first information, which can reduce signaling overhead.

[0037] In conjunction with the second aspect, in one possible implementation, the access control information includes access parameters corresponding to the first access category, and the first access category corresponds to the computing service; determining to send the first information based on the access control information includes: determining to send the first information based on the access parameters corresponding to the first access type.

[0038] In this embodiment, the first access category corresponds to a computing service, and the access parameters corresponding to the first access category are access control information for the computing service, used to indicate whether the terminal device is allowed to request the computing service. Based on the access parameters corresponding to the first access category, the terminal device can better determine whether to initiate a computing service request, that is, whether to send the first information.

[0039] In conjunction with the second aspect, in one possible implementation, the access parameters corresponding to the first access category include first indication information and a prohibition factor; wherein, the first indication information is used to indicate whether the access identifier corresponding to the terminal device is allowed to access. The terminal device determines to send the first information if the first indication information indicates that the access identifier corresponding to the terminal device is allowed to access; or, the terminal device determines to send the first information if the first indication information indicates that the access identifier corresponding to the terminal device is not allowed to access, and the first random number is less than or equal to the prohibition factor; wherein, the first random number is generated by the terminal device.

[0040] In this embodiment, the first indication information is used to indicate whether the access identifier corresponding to the terminal device is allowed to access; it can also be understood as the first indication information being used to indicate whether the terminal device is allowed to request computing services. Through the aforementioned first indication information and the prohibition factor, it can be determined whether the terminal device is allowed to request computing services.

[0041] In conjunction with the second aspect, in one possible implementation, the access identifier corresponding to the terminal device includes a first access identifier, which corresponds to a computing service.

[0042] In this embodiment of the application, the first access identifier is an access identifier dedicated to computing services. Through this first access identifier, it is possible to better indicate whether the terminal device is allowed to request computing services.

[0043] In conjunction with the second aspect, in one possible implementation, the access parameters corresponding to the first access type also include at least one of the following: prohibition time and number of attempts.

[0044] In conjunction with the second aspect, in one possible implementation, the first information includes a first cause value and / or first calculation information, the first cause value corresponding to a calculation service, and the first calculation information including the terminal device's computing capability information and / or computing requirement information.

[0045] In conjunction with the second aspect, in one possible implementation, the first reason value is carried in the reason value field of the RRC establishment request message, and the first reason value corresponds to the first access type and / or the first access identifier.

[0046] In conjunction with the second aspect, in one possible implementation, the first cause value is carried in the computation request message.

[0047] In conjunction with the second aspect, in one possible implementation, the second network element is an access network element or a core network element; the first information is used to request computing services, including: the first information is used to request the second network element to provide computing services to the terminal device.

[0048] In conjunction with the second aspect, in one possible implementation, the method further includes: receiving second information, the second information being used to reject the request of the first information; the second information also indicating at least one of the following: a waiting time, the inability of a second network element to provide computing services to the terminal device, information about the first cell, and instructing the terminal device to request computing services from a third network element. Wherein, the waiting time is used to instruct the terminal device to re-request computing services from the second network element after the waiting time, the first cell supports the computing request, and the third network element is a network element in the data network or an edge application server (EAS).

[0049] In conjunction with the second aspect, in one possible implementation, the method further includes: sending third information, the third information being used to request a third network element to provide computing services to the terminal device.

[0050] In conjunction with the second aspect, in one possible implementation, the second network element is an access network element, a core network element, an edge application server, or a network element in a data network; the method further includes: receiving second information, the second information instructing the second network element to provide computing services to the terminal device.

[0051] In this embodiment, the first information does not specify a particular network element to provide computing services to the terminal device. Therefore, the second network element can be any one of the following: an access network element, a core network element, an edge application server, or a network element in the data network. When the second information is used to receive a computing service request from the terminal device, it can indicate one of the following: an access network element, a core network element, an edge application server, or a network element in the data network, to indicate the network element that provides computing services to the terminal device. In this way, the terminal device can determine the user plane session required to transmit computing data based on the second information.

[0052] Thirdly, embodiments of this application provide a communication device for executing the methods in any one of the first to second aspects or any possible implementations thereof. The communication device includes a module having the function of executing the methods in any one of the first to second aspects or any possible implementations thereof.

[0053] Fourthly, embodiments of this application provide a communication device including a processor, the processor being configured to cause the communication device to perform the methods shown in any of the first to second aspects or any possible implementations described above.

[0054] Optionally, the communication device further includes a transceiver for sending and / or receiving information. For example, the transceiver is used to cause the communication device to perform the sending and receiving steps in the method described in any of the first or second aspects or any possible implementation thereof.

[0055] Fifthly, embodiments of this application provide a communication device including a logic circuit and an interface, wherein the logic circuit and the interface are coupled; the interface is used to input and / or output information, and the logic circuit is used to cause the communication device to perform processing steps in the method described in any one of the first or second aspects or any possible implementation thereof.

[0056] Sixthly, embodiments of this application provide a computer-readable storage medium for storing a computer program that, when run on a computer, causes the methods described in any of the first to second aspects or any possible implementation thereof to be executed.

[0057] In a seventh aspect, embodiments of this application provide a computer program product that, when run on a computer, causes the methods described in any of the first to second aspects or any possible implementations described above to be executed.

[0058] Eighthly, embodiments of this application provide a communication system, which includes a first network element and a terminal device. The first network element is used to execute the method described in the first aspect or any possible implementation thereof, and the terminal device is used to execute the method described in the second aspect or any possible implementation thereof. Attached Figure Description

[0059] Figure 1 is a schematic diagram of the architecture of a multi-edge computing (MEC) system provided in an embodiment of this application;

[0060] Figure 2 is a schematic diagram of the structure of a communication system provided in an embodiment of this application;

[0061] Figure 3A is a schematic diagram of the architecture of an O-RAN system provided in an embodiment of this application;

[0062] Figure 3B is a schematic diagram of the division of protocol functions under an O-RAN architecture provided in an embodiment of this application;

[0063] Figure 4 is a flowchart illustrating a communication method provided in an embodiment of this application;

[0064] Figure 5 is a flowchart illustrating another communication method provided in an embodiment of this application;

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

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

[0067] Figure 8 is a schematic diagram of another communication device provided in an embodiment of this application;

[0068] Figure 9 is a schematic diagram of the structure of another communication device provided in an embodiment of this application. Detailed Implementation

[0069] The terms "first" and "second," etc., used in the specification, claims, and drawings of this application are only used to distinguish different objects and not to limit the order, sequence, priority, or importance of multiple objects. In the embodiments of this application, "multiple" refers to two or more. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or devices. Additionally, the character " / ," unless otherwise specified, generally indicates that the preceding and following objects are in an "or" relationship.

[0070] The term "embodiment" as used herein means that a specific feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment mutually exclusive with other embodiments. Those skilled in the art will explicitly and implicitly understand that, unless otherwise specified or logically conflicting, the terminology and / or descriptions between the various embodiments of this application are consistent and can be mutually referenced, and technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0071] It should be understood that in this application, "at least one (item)" means one or more, "more than one" means two or more, "at least two (items)" means two or three or more, and "and / or" is used to describe the relationship between related objects, indicating that there can be three relationships. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0072] The technical solutions in the embodiments of this application will be described below with reference to the accompanying drawings. The technical solutions in the embodiments of this application can be applied to various communication systems, such as Universal Mobile Telecommunications System (UMTS), Wireless Local Area Network (WLAN), Wireless Fidelity (Wi-Fi) system, 4th generation (4G) mobile communication system, such as Long Term Evolution (LTE) system, 5th generation (5G) mobile communication system, such as New Radio (NR) system, and future evolution communication systems, such as 6th generation (6G) mobile communication system, etc.

[0073] This application will present various aspects, embodiments, or features relating to systems that may include multiple devices, components, modules, etc. It should be understood and appreciated that individual systems may include additional devices, components, modules, etc., and / or may not include all the devices, components, modules, etc. discussed in conjunction with the accompanying drawings. Furthermore, combinations of these approaches are also possible.

[0074] Furthermore, in the embodiments of this application, words such as "exemplarily" and "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design scheme described as an "example" in this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the term "example" is intended to present concepts in a concrete manner. In the embodiments of this application, "of," "corresponding, relevant," and "corresponding" may sometimes be used interchangeably, and it should be noted that their intended meanings are consistent unless their distinction is emphasized.

[0075] In this application, "send" and "receive" indicate the direction of signal transmission. For example, "send information to XX" can be understood as the destination of the information being XX, which can include direct transmission via the air interface or indirect transmission via the air interface from other units or modules. "Receive information from YY" can be understood as the source of the information being YY, which can include direct reception from YY via the air interface or indirect reception from YY via the air interface from other units or modules. "Send" can also be understood as the "output" of a chip interface, and "receive" can also be understood as the "input" of a chip interface. In other words, sending and receiving can occur between devices, such as between network devices and terminal devices, or within a device, such as between components, modules, chips, software modules, or hardware modules within the device via buses, traces, or interfaces.

[0076] The communication systems and service scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new service scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0077] Typically, computing resources (or computing power) for artificial intelligence (AI) are provided by cloud platforms, and AI-related data from terminal devices can be sent to the cloud platform for processing via the network. With the widespread adoption of personal terminals such as smartphones and tablets, data volume has surged, placing higher demands on cloud platforms. Furthermore, in practical applications, many scenarios require the computation of massive amounts of data with timely feedback. In such cases, the data transmission path from the collection point to the central server may be long, failing to meet latency requirements and potentially posing security and privacy issues. Therefore, edge computing has been developed based on cloud platform computing, distributing computing tasks from central nodes to edge nodes. Compared to cloud platform computing, edge computing's computing resources are closer to users and data sources, resulting in lower latency and improved data security and user privacy protection.

[0078] Figure 1 is a schematic diagram of the architecture of a multi-edge computing (MEC) system provided in an embodiment of this application. As shown in Figure 1, the MEC system includes user equipment (UE), an access network, a core network (CN), a data network (DN), and an edge application server (EAS). The access network is used to implement functions related to radio access and mainly includes access network (AN) equipment. The core network may include one or more of the following logical network elements (or network functions (NFs)): user plane function (UPF), access and mobility management function (AMF), session management function (SMF), policy control function (PCF), unified data management (UDM), network repository function (NRF), application function (AF), network exposure function (NEF), and edge application server discovery function (EASDF). The interfaces between the network elements are shown in Figure 1. It should be understood that network elements can also communicate using service-oriented interfaces.

[0079] UE, also known as terminal equipment, can communicate with one or more core networks (CNs) via AN equipment. Terminal equipment can be referred to as access terminal, terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless network equipment, user agent, or user device. Terminals can be cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices, or other devices connected to a wireless modem, in-vehicle equipment, wearable devices, or terminal equipment in the Internet of Things (IoT), vehicular networks, and any form of terminal equipment in future networks.

[0080] An AN device is a device that connects terminal devices to a wireless network. It can also be called an access network device, network device, or radio access network (RAN) node. For example, the AN device can be: an access point (AP) in a wireless local area network (WLAN), a base transceiver station (BTS) in a global system for mobile communications (GSM) or code division multiple access (CDMA), a base station (NodeB, NB) in a wideband code division multiple access (WCDMA), an evolved Node B (eNB or eNodeB) in LTE, a relay station or access point, or an in-vehicle device, wearable device, and the next generation Node B (gNB) in a 5G system, a base station in a future evolved public land mobile network (PLMN), an access network device or module of an access network device in an open RAN (ORAN) system, or a base station in a future mobile communication system or an access node in a WiFi system, etc.

[0081] Optionally, in some deployments of access network equipment, the access network equipment may include centralized units (CU) and distributed units (DU), etc. In other deployments of access network equipment, the CU may be divided into CU-control plane (CP) and CU-user plane (UP), etc. In still other deployments of access network equipment, the access network equipment may also be a radio unit (RU), etc. In still other deployments of access network equipment, the access network equipment may also be an open radio access network (ORAN) architecture, etc. The specific deployment method of the access network equipment is not limited in the embodiments of this application. For example, when the access network equipment is an ORAN architecture, the access network equipment shown in the embodiments of this application may be an access network equipment in ORAN, or a module in the access network equipment, etc. In the ORAN system, CU may also be called open (O)-CU, DU may also be called O-DU, CU-CP may also be called O-CU-CP, CU-UP may also be called O-CU-UP, and RU may also be called O-RU.

[0082] UDM has functions such as managing user contract data and generating user authentication information.

[0083] The Active Mobility Element (AMF) is primarily responsible for UE registration management, UE connection management, UE reachability management, UE access authorization and authentication, UE security functions, UE mobility management, network slice selection, and SMF selection. The AMF acts as the anchor point for N1 / N2 interface signaling connections and provides routing for N1 / N2 interface session management (SM) messages to the SMF, maintaining and managing UE state information. The AMF is a mobility management network element in 5G systems.

[0084] The SMF (Service Provider Function) is primarily responsible for all control plane functions of UE session management, including UPF (User Provider Function) selection and control, Internet Protocol (IP) address allocation and management, session quality of service (QoS) management, and obtaining policy and charging control (PCC) policies from the PCF (Process Control Provider Function). The SMF also serves as the endpoint for the SM (Service Message) portion of non-access stratum (NAS) messages.

[0085] PCF has the ability to provide policy rules to control plane functional entities.

[0086] AF can be an application server, which can belong to the operator or a third party.

[0087] The User-Defined Processing (UPP) is primarily responsible for processing user packets, such as forwarding and accounting. The UPF can serve as the anchor point for Protocol Data Unit (PDU) session connections, i.e., the PDU session anchor (PSA), responsible for filtering UE data packets, data transmission / forwarding, rate control, generating accounting information, user plane QoS processing, uplink authentication, transmission class verification, downlink packet buffering, and triggering downlink data notifications. When acting as a PSA, the UPF can also include a central PSA (C-PSA) and a local PSA (L-PSA). For example, the UPF can also serve as a branch point in a multi-homed PDU session. Furthermore, the UPF can also serve as an uplink classifier (UL CL).

[0088] A Data Network (DN) provides data transmission services to users, such as IP Multimedia Service (IMS) and the Internet. A DN may include an Application Server (AS), a software framework that provides an environment for applications to run, offering services such as security, data, transaction support, load balancing, and large-scale distributed system management. The User Equipment (UE) obtains application messages by communicating with the AS. It should be noted that the AF mentioned above refers to the AS's control plane.

[0089] Edge Application Server (EAS) can provide services as a data network. During uplink transmission, the UPF offloads computation-related data to the EAS, thereby providing computing services to terminal devices. The EAS can also be called an edge computing server.

[0090] In some possible implementations, computing resources can also be deployed in the access network or core network, which provides computing services to the terminal devices. Figure 2 shows a schematic diagram of a communication system. As shown in Figure 2, the communication system includes an access network (RAN), a core network (CN), and a far-edge intelligent node (FeIN). The access network includes RAN equipment, and the core network includes at least one of the following logical functions: AMF, SMF, PCF, NEF, Computing Management Function (CMF), and UDM. Optionally, the communication system shown in Figure 2 may also include at least one of terminal devices, DN, EAS, and MAE.

[0091] FeIN is a node that provides computing resources and is responsible for executing computing tasks. Computing applications and resources can be deployed on this FeIN to provide computing services to terminal devices. For example, FeIN supports local model inference, image rendering, etc. FeIN can be a logical function, belonging to either the core network or the access network. FeIN can be deployed independently or co-located with other access network elements or core network elements.

[0092] The Compute Function (CFF) is responsible for managing computing connectivity functions, such as computing service subscription and authorization, computing service policies (transport + computing policies), computing service session management, computing execution function registration and discovery, and computing service mobility management. The CMF can be a standalone network element or shared with other network elements; for example, the SMF can also be used to implement the CMF's functions. Alternatively, the CMF can also be configured within the RAN (Radio Ranging) equipment.

[0093] Optionally, the RAN device may include a computing user plane function (CUF) and a computing control function (CCF). The CUF is used for data plane offloading of computing traffic flows. For example, the CUF can forward computing traffic flows to the FeIN. The CCF is used for the control of computing services, such as responsible for admission control of computing services, coordination of computing resources, etc.

[0094] There is an Nx interface between the RAN equipment and the FeIN. Optionally, the Nx interface can be Nx-C or Nx-U, where Nx-U is based on a user plane transport protocol (e.g., GTP-U) and Nx-C is based on a control plane transport protocol (e.g., SCTP).

[0095] When the computing services of the terminal device are executed by FeIN, the computing service flow can be forwarded to FeIN through CUF, as shown by the thick line in Figure 2.

[0096] When the computing services of the terminal device are executed by AS or EAS, the computing service flow can be forwarded to EAS or AS through UPF, as shown by the dashed line in Figure 2.

[0097] Optionally, the communication system shown in Figure 2 may also include a mobile broadband (MBB) automation engine (MAE) for the management and access of computing resources.

[0098] In the communication system shown in Figure 2, computation-related data for terminal devices can be scheduled or forwarded via the RAN. For computational service data, the RAN can forward it to the FeIN, enabling the FeIN to provide computational services to the terminal devices. For routine service data, the RAN can forward it to the UPF, and then the UPF can forward it to the DN.

[0099] In this embodiment, FeIN is simply the name of a logical function providing computing services in the core network or access network. The name of this logical function in the core network or access network is not limited in this embodiment. For example, the logical function providing computing services in the core network or access network can also be called a task execution function (TEF) or a computing execution function (CEF), etc. Alternatively, FeIN can also be called a computing node, computing board, or smart board, etc.

[0100] In this embodiment, FeIN is a network element in the access network or core network, which provides computing services to terminal devices and can also be referred to as on-network computing.

[0101] In this embodiment, the FeIN can be deployed on an AN device as part of the AN device's functionality. Alternatively, the FeIN can be deployed independently and directly connected to the AN device. One AN device can connect to multiple FeINs, and one FeIN can connect to multiple AN devices. This embodiment does not limit the quantity relationship between AN devices and FeINs.

[0102] Figure 3A illustrates an example of a communication system based on an O-RAN architecture, and Figure 3B illustrates an example of the division of protocol functions under an O-RAN architecture. The modules involved in Figures 3A and 3B are described below:

[0103] Non-real-time RAN intelligent controller (Non-RT RIC): Used to implement non-real-time intelligent management of RAN functions. This non-real-time intelligent management includes, but is not limited to: artificial intelligence (AI) or machine learning (ML) workflows for model training, AI or ML workflows for model updates, and applications / functions in a policy-guided near-real-time RAN intelligent controller (Near-RT RIC). The Non-RT RIC can reside within the service management organization (SMO) module.

[0104] Near-real-time RAN intelligent controller (Near-RT RIC): Used to achieve near-real-time intelligent management of the RAN. Through data collection and related operations on the E2 interface, it enables near-real-time control and optimization of O-RAN modules and resources.

[0105] The O-RAN central unit (O-CU) is responsible for implementing the functions of the radio resource control (RRC) layer, the packet data convergence protocol (PDCP) layer, the service data adaptation protocol (SDAP) layer, and other control functions in the 3rd generation partnership project (3GPP) standard.

[0106] O-RAN Central Unit Control Plane (O-CU-CP): Similar to the CU-CP in new radio (NR) systems, it implements the functions of the RRC layer and the control plane functions of the PDCP layer. The O-CU-CP is a part of the O-CU.

[0107] O-RAN Central Unit User Plane (O-CU-UP): Similar to the CU-UP in the NR system, it is used to implement the functions of the SDAP layer and the user plane functions of the PDCP layer. O-CU-UP is a part of O-CU.

[0108] O-RAN Distributed Unit (O-DU): Based on low-layer function segmentation, it is used to implement the functions of the radio link control (RLC) layer, media access control (MAC) layer, and higher physical layer (PHY) layer in the 3GPP standard. The functions of the higher physical layer include one or more of the following: forward error correction (FEC) encoding / decoding, scrambling / descrambling, or modulation / demodulation.

[0109] The O-RAN radio unit (O-RU) is based on low-layer function partitioning and is used to implement lower physical layer (lower PHY) functions and radio frequency (RF) functions in the 3GPP standard. These lower PHY functions include one or more of the following: Fast Fourier Transform (FFT) / Inverse Fast Fourier Transform (iFFT), digital beamforming, or extraction and filtering of the Physical Random Access Channel (PRACH). It is similar to the TRP or Remote Radio Head (RRH) in 3GPP, but includes lower PHY functions such as FFT / iFFT or PRACH extraction.

[0110] O-RAN cloud (O-cloud): As a cloud computing platform, it includes physical infrastructure nodes for hosting O-RAN functions such as RIC and O-DU; supports software components (such as operating systems, virtual machine monitoring, container runtimes); and management and orchestration functions.

[0111] The following describes the interfaces involved in Figure 3A:

[0112] A1 Interface: The interface between non-RT RIC and near-RT RIC, used for intelligent and dynamic control of radio resources within the O-RAN. Non-RT RIC provides policies, rich information, and ML model updates to near-RT RIC through the A1 interface, while near-RT RIC provides policy feedback to non-RT RIC through the A1 interface.

[0113] E2 Interface: The E2 interface is an open interface between two endpoints used to connect the near-RT RIC and the RAN node. RAN nodes include, but are not limited to, one or more of the following: CU and DU in 5G, O-RAN compatible with gNB, O-RAN compatible with eNB, O-CU (O-CU-CP and / or O-CU-UP), O-DU, etc. in O-RAN. The RIC can obtain RAN node data collection and feedback through the E2 node, and the RAN node can obtain control feedback from the near-RT RIC through the E2 node.

[0114] O1 Interface: The interface between the management entity in the SMO and the O-RAN module, used for operation management. For example, FCAPS management, software management, and file management are implemented through this interface.

[0115] O2 Interface: The interface between the SMO and the infrastructure management framework that supports O-RAN virtual network functionality.

[0116] E1 interface: The interface between CU-CP and CU-UP.

[0117] F1-C interface: The interface between CU-CP and DU.

[0118] F1-U interface: The interface between CU-UP and DU.

[0119] The O-RAN architecture shown in Figure 3A is only an example. In specific implementations, other O-RAN architectures may also be used, and this application embodiment does not limit them.

[0120] In the communication system shown in Figure 1, 2, or 3A, the communication and computing services operate independently. The communication network is only used for transmitting data related to computing services and cannot adequately meet the needs of computing services. For example, the current communication network does not consider the load status of the network elements providing computing services, and may not be able to guarantee optimal end-to-end latency for computing services. For instance, when computing latency is long, it may not be able to reduce transmission latency to avoid failing to meet end-to-end latency requirements.

[0121] Therefore, embodiments of this application provide a communication method and a communication device that can better meet the needs of computing services.

[0122] The communication method provided in this application can be applied to the communication system shown in FIG1, FIG2, or FIG3A. For example, the method provided in this application can be applied to a terminal device and a first network element. The terminal device can be the terminal device in the communication system shown in FIG1, FIG2, or FIG3A. The first network element can be an access network device in the communication system shown in FIG1 or FIG2, or the first network element can be an O-DU or O-CU in the communication system shown in FIG3A. Alternatively, the first network element can also be a core network device, such as an AMF.

[0123] In this embodiment, "computing service" refers to a service that provides computational capabilities. A computing service can refer to a type of service, such as AI large-scale model inference, image rendering, or text-to-image processing. Alternatively, it can indicate a computing capability, such as a service type plus a service level agreement (SLA) requirement, for example, AI large-scale model inference with an end-to-end latency requirement of 300ms. Or, it can indicate a computing service provided by a specific application or model, such as generative functional intelligence (e.g., ChatGPT4), image processing (e.g., Meitu), or text processing. A computing service can also be called a computing service, a computing task, or an AI service.

[0124] Please refer to Figure 4, which is a flowchart illustrating a communication method provided in an embodiment of this application. As shown in Figure 4, the method includes, but is not limited to, the following steps.

[0125] 401, The terminal device sends the first information, and correspondingly, the first network element receives the first information.

[0126] The first information is used to request computing services, or in other words, the first information is used to indicate that the terminal device has computing needs, or in other words, the first information is used to request computing resources from the network side or the cloud.

[0127] For example, the first network element is an access network element. For instance, the first network element could be an AN device (such as a gNB) as described above. Alternatively, in an O-RAN architecture, the first network element could be a DU or CU.

[0128] For example, the first information includes a first cause value and / or first calculation information, wherein the first cause value is determined based on a first access category and / or a first access identifier, and the first access category and / or the first access identifier corresponds to a calculation service.

[0129] The first set of computational information includes the terminal device's computational capability information and / or computational requirement information. Specifically, the terminal device's computational capability information includes information on the computational services supported by the terminal device and / or the quality of service (QoS) information for the corresponding computational services. For example, the computational capability information includes information on the computational resources supported by the terminal device, such as the task identifier (task ID) of the computational service. The terminal device's computational requirement information includes information on the computational services requested by the terminal device and / or the QoS information corresponding to the requested computational services. For example, the terminal device's computational requirement information includes at least one of the following: end-to-end latency requirement, time to first token (TTFT), and time between tokens (TBT) for the requested computational services. A token is a basic unit for AI models to process and understand textual data, typically a word, phrase, or symbol.

[0130] In this embodiment, QoS information can also be replaced with SLA information.

[0131] As an example, the first information does not request a specific network element to provide computing services to the terminal device. In other words, the terminal device requests computing services through the first information, without being limited to the network element that provides computing services to the terminal device.

[0132] As another example, the first information requests a specific network element to provide computing services to the terminal device. For instance, the first information requests a second network element to provide computing services to the terminal device. Exemplarily, this second network element can be an access network element or a core network element (such as the FeIN described above), meaning the first information instructs the terminal device to request the access network or core network to provide computing services. Also exemplarily, the second network element can be an edge computing server, meaning the first information is used to request the edge computing server to provide computing services to the terminal device. Also exemplarily, the second network element can be an AS (such as a central cloud server), meaning the first information is used to request the AS to provide computing services to the terminal device. Furthermore, exemplarily, the first information is used to request end-cloud collaboration / end-edge collaboration, where end-cloud collaboration refers to the cloud (AS) assisting the terminal device in completing its computing services, and end-edge collaboration refers to the EAS or FeIN assisting the terminal device in completing its computing services.

[0133] For example, when the first information includes a first cause value, the first cause value can be obtained by mapping a first access category and / or a first access identifier. The first cause value indicates that the terminal device has a need for computing services, or it requests a second network element to provide computing services to the terminal device. The first cause value can be carried in the cause value field of the RRC establishment request message. Alternatively, the first cause value can also be carried in the computing request message.

[0134] As an example, the first information bearer is carried via an RRC message.

[0135] For example, when the first information includes a first cause value and first calculated information, the first cause value and the first calculated information can be carried in the same RRC message. For instance, the first cause value and the first calculated information can be carried in an RRC establishment request message, or the first cause value and the first calculated information can be carried in other RRC messages, such as UE Assistance Information messages.

[0136] As another example, the first cause value and the first calculation information can be carried in different RRC messages. For instance, the first cause value can be carried in the RRC establishment request message, and the first calculation information can be carried in the RRC establishment completion message.

[0137] As another example, the first information is carried through a preamble. The RAN device can allocate dedicated preamble resources for computing to the terminal device, so that when the terminal device initiates a random access procedure, it can indicate the first information to the RAN device through the dedicated preamble.

[0138] As another example, the initial information can be carried in MAC CE.

[0139] 402, the first network element sends the second information to the terminal device, and the terminal device receives the second information accordingly.

[0140] The second information is determined based on the computing resource information of the second network element. The second information is used to accept or reject the request of the first information. The second network element is used to provide computing services.

[0141] For example, when the first network element receives the first information, it determines whether to accept or reject the request of the first information based on the computing resource information of the second network element, and sends the second information to indicate whether to accept or reject the request of the first information.

[0142] For example, the computing resource information of the second network element includes at least one of the following: the load information of the computing services of the second network element, the information of the computing services supported by the second network element, and the QoS information of the computing services supported by the second network element.

[0143] The load information of the computing services of the second network element can also be referred to as the load information of the computing resources of the second network element. This load information may include at least one of the following: the total amount of computing resources of the second network element, the number of computing tasks supported by the second network element, the number of terminal devices supported by the second network element, the remaining amount of computing resources of the second network element (for example, it can be expressed as a percentage or fraction), the number of computing tasks / terminal devices in the current queue of the second network element, the number of computing tasks that the second network element can still accommodate, and the number of terminal devices that the second network element can still accommodate.

[0144] For example, the computing resources of the second network element are divided at the granularity of computing services. The load information of the computing services of the second network element may include the load information (such as the remaining computing resources) corresponding to each computing service. Alternatively, the computing resources of the second network element may also be divided at the granularity of a computing service set (task set), where a computing service set refers to a collection of multiple computing services. These multiple computing services share computing resources. The load information of the computing services of the second network element may include the load information (such as the remaining computing resources) corresponding to each computing service set.

[0145] The information of the computing services supported by the second network element may include at least one of the following: the type of computing service supported by the second network element, the computing model of the computing service supported by the second network element, the identifier (task ID) of the computing service supported by the second network element, etc.

[0146] The QoS information of the computing services supported by the second network element may include at least one of the following: computing latency guaranteed by the second network element, time to first token (TTFT), and time between tokens (TBT).

[0147] In one possible implementation, the first information is used to request the network to provide computing services to the terminal device; in other words, it does not request a specific network element to provide computing services to the terminal device, and the second network element can be any network element capable of providing computing services. For example, the second network element can be any of FeIN, EAS, and AS described above.

[0148] For example, if any of the network elements in FeIN, EAS, and AS are capable of providing computing services to the terminal device, the second information is used to accept the request of the first information. After receiving the second information, the terminal device transmits computing data through the user plane. As another example, if none of FeIN, EAS, and AS can provide computing services to the terminal device, the second information is used to reject the request of the first information. After receiving the second information, the terminal device discards the data packet containing computing data in the buffer or performs computing services locally.

[0149] Optionally, when the second information is used to accept the request of the first information, the second information may also indicate the network element that provides computing services to the terminal device, and the terminal device determines the user plane session for transmitting computing data based on the second information.

[0150] As an example, the second information indicates that the network element providing computing services to the terminal device is a FeIN. Before step 401, a computing session is established between the terminal device and the FeIN. When multiple FeINs exist, a separate computing session is established between the terminal and each FeIN. Therefore, different sessions need to be distinguished by the session identifier (ID) or FeIN ID. At this time, the second information can also indicate the session ID information corresponding to the FeIN, or the IP address information of the FeIN, or the FeIN ID information, so that the terminal device can match the computing session according to the second information and send computing data to the corresponding FeIN through the user.

[0151] As another example, the second information indicates that the network element providing computing services to the terminal device is an AS or EAS, meaning the second information indicates that the MEC or central cloud provides computing services to the terminal device. Optionally, the second information includes the IP address information of the EAS or AS. Thus, the terminal device sends computing data to the EAS or AS via the UPF.

[0152] In another possible implementation, the first information is used to request a specific network element to provide computing services to the terminal device, and the second network element is that specific network element; that is, the first information is used to request the second network element to provide computing services to the terminal device.

[0153] For example, when the second information is used to reject the request of the first information, the terminal device can request other network elements to provide computing services to the terminal device, thereby increasing the probability that the terminal device's request for computing services will be successful. For example, the second network element is an access network element or a core network element (such as the FeIN described above), and the second information is used to reject the request of the first information. After receiving the second information, the terminal device can also send a third information to the first network element, which is used to request a third network element to provide computing services to the terminal device. This third network element is a network element in the DN (such as AS) or EAS.

[0154] For example, when the second information is used to reject the request of the first information, the second information further indicates at least one of the following: a waiting time, the second network element being unable to provide computing services to the terminal device, information about the first cell, or instructing the terminal device to request computing services from the third network element. The waiting time is used to instruct the terminal device to re-request computing services from the second network element after the waiting time. The first cell supports computing services, and the second information instructs the terminal device to reselect to the first cell by indicating the information of the first cell, so that it can request computing services under that first cell. The third network element is another network element that provides computing services. If the second network element is unable to provide computing services to the terminal device, the second information can also instruct the terminal device to request computing services from the third network element, so that the terminal device can successfully request computing services. For example, the second network element is an access network element or a core network element, and the third network element is a network element in the data network or an edge application server (EAS).

[0155] For example, the second information may include a second cause value, which indicates one or more of the following: waiting time, the inability of the second network element to provide computing services to the terminal device, information about the first cell, and an instruction for the terminal device to request computing services from the third network element.

[0156] For example, the second network element is FeIN. The first information is used to request FeIN to provide computing services to the terminal device. The second information is used when the request of the first information is accepted. The second information includes the session ID information, IP address information, or FeIN ID information corresponding to FeIN. The terminal device determines FeIN based on the second information and sends computing data to FeIN.

[0157] For example, the second network element is an EAS or AS. The first information is used to request the EAS or AS to provide computing services to the terminal device. The second information is used when the terminal device sends computing data to the EAS or AS via the UPF after accepting the request from the first information. Optionally, the second information includes the IP address information of the EAS or AS.

[0158] Regarding the determination of the second information, this application provides the following implementation methods:

[0159] Implementation Method 1: The first information includes a first cause value, which indicates that the terminal device has a service requirement, or that the first cause value requests the second network element to provide computing services to the terminal device. The first network element determines the second information based on the first cause value and the load information of the computing services of the second network element. For example, if the load of the computing services of the second network element allows, the second information is used to accept the request of the first information. Conversely, if the load information of the computing services of the second network element does not allow, the second information is used to reject the request of the first information.

[0160] In this implementation, "load allowed" means that the remaining amount of computing resources of the second network element is allowed (e.g., the remaining amount of computing resources of the second network element is greater than a threshold), or the number of computing tasks that the second network element can accommodate is allowed (e.g., the number of computing services currently provided by the second network element is less than the number of computing tasks supported by the second network element), or the number of terminal devices that the second network element can accommodate is allowed (e.g., the number of terminal devices currently provided by the second network element is less than the number of terminal devices supported by the second network element).

[0161] Implementation Method 2: The first information includes first computing information, which includes information about the first computing service. That is, the computing capability information and / or computing requirement information of the terminal device includes the information about the first computing service. The first network element determines the second information based on the information about the first computing service and the computing resource information of the second network element.

[0162] In this implementation, the first information request computation service refers to the first information used to request the first computation service.

[0163] The computing resource information of the second network element may include information on the computing services supported by the second network element and / or the load information of the computing services of the second network element. The first network element may determine whether the second network element supports the first computing service based on the information on the computing services supported by the second network element, and / or determine whether the load of the second network element allows the terminal device to access based on the load information of the computing services of the second network element.

[0164] For example, if the second network element supports the first computing service and the load allows, the second information is used to accept the request from the first information. This ensures that the second network element supports the computing service requested by the terminal device and has sufficient load to provide computing services to the terminal device. It also ensures the computing speed of the second network element when providing computing services to the terminal device, and can better meet the performance requirements of the terminal device's computing services.

[0165] For example, if the second network element supports the first computing service but the load does not allow it, the second information is used to reject the request of the first information. In this way, the backlog of computing services on the second network element can be avoided, the computing speed of the computing services being executed by the second network element can be guaranteed, and the performance requirements of the computing services being executed by the second network element can be guaranteed.

[0166] For example, if the second network element does not support the first computing service, the second information is used to reject the request from the first information.

[0167] In this implementation, "load allowed" means that the load corresponding to the first computing service in the second network element is allowed. For example, the remaining amount of computing resources corresponding to the first computing service is greater than a threshold, or the number of first computing services supported by the second network element is greater than the number of first computing services currently being executed by the second network element. "Load not allowed" means that the load corresponding to the first computing service in the second network element is not allowed. For example, the remaining amount of computing resources corresponding to the first computing service is less than a threshold, or the number of first computing services currently being executed by the second network element reaches the number of first computing services supported by the second network element.

[0168] Implementation Method 3: The first information includes first computational information, which includes QoS information of the computational services requested by the terminal device. The second network element's computational resource information includes QoS information of the computational services supported by the second network element and / or computational load information. The first network element determines the second information based on the first computational information and the second network element's computational resource information, thus ensuring that the second network element can meet the QoS requirements of the terminal device's computational services (such as end-to-end latency requirements).

[0169] For example, the second network element estimates the time required for computation based on the information of the computing load, and assesses whether it can meet the QoS requirements of the computing service requested by the terminal device. If it can meet the requirements, the second information is used to accept the request of the first information; if it cannot meet the requirements, the second information is used to reject the request of the first information.

[0170] For example, the QoS information for the computing service requested by the terminal device includes the end-to-end latency required by the terminal device. The QoS information for the computing service supported by the second network element includes the expected computing latency or end-to-end latency. If the computing latency or end-to-end latency supported by the second network element is less than or equal to the end-to-end latency required by the terminal device, the second network element provides information that meets the latency requirements of the terminal device, and the second information is used to accept the request from the first information. If the second network element cannot meet the latency requirements of the terminal device, the second information is used to reject the request from the first information.

[0171] Implementation Method 4: The first network element determines the second information based on the authorization information of the terminal device configured on the network side and the computing resource information of the second network element. The authorization information of the terminal device includes the terminal device's computing capability information (such as information on the computing services supported by the terminal device and / or the QoS information of the corresponding computing services supported by the terminal device), the maximum allowed number of requests / tokens / prompts, etc.

[0172] For example, the authorization information may be the authorization information of the terminal device configured in the core network during the terminal device's registration process (such as information on the computing services supported by the terminal device, the maximum allowed number of requests / tokens / prompts, etc.). During the registration process, the AMF sends this authorization information to the first network element, and the first network element determines whether to accept the request based on the authorization information of the terminal device and the computing resource information of the second network element.

[0173] For example, the computing capability information of the terminal device includes information about a first computing service, used to indicate that the terminal device supports the first computing service. If the second network element supports the first computing service and the load allows, the second information is used to accept the request from the first information. If the second network element supports the first computing service but the load does not allow, the second information is used to reject the request from the first information. If the second network element does not support the first computing service, the second information is used to reject the request from the first information.

[0174] For example, the maximum allowed number of requests / tokens / prompts indicates the maximum number of times a terminal device can request computing services / the maximum number of tokens that can be requested / the maximum number of prompts that can be requested. If the second network element determines that the terminal device's request exceeds the maximum allowed number of requests / tokens / prompts, the second information is used to reject the request from the first information.

[0175] For example, the first and second information can be carried in an RRC message. In this embodiment, the messages used to carry the first and second information differ depending on the RRC state of the terminal device. For instance, when the terminal device is in an RRC disconnected state (such as an RRC inactive state or an RRC idle state), the first information is carried in an RRC establishment request message or an RRC establishment completion message. When the second information is used to accept a request for the first information, it is carried in an RRC establishment message. When the second information is used to reject a request for the first information, it is carried in an RRC rejection message. As another example, when the terminal device is in an RRC connected state, the first information can be carried in a UE assistance information message. The second information can be carried in an RRC reconfiguration message. Furthermore, when the terminal device is in an RRC disconnected state, the first information is carried through a preamble, and the second information can be carried in Msg2 during the random access procedure.

[0176] As another example, the first and second information can also be carried in the MAC control element (CE), thereby reducing the signaling transmission delay.

[0177] As an example, the first information and the second information can also be transmitted through the user plane. This application does not limit the specific transmission method of the first information and the second information.

[0178] Before sending the second information, the first network element can first obtain the computing resource information of the second network element. For example, the second network element or CMF sends this computing resource information to the first network element, and the first network element receives the computing resource information accordingly. Alternatively, the first network element can also obtain the computing resource information of the second network element through configuration of other core network elements, OAM, or capability exposure. For example, in the MEC architecture, the second network element is AS, and the AS's computing resource information can be configured by the network management system, or transmitted to the first network element (gNB) via NEF.

[0179] After the terminal device receives the second information, the embodiments of this application also provide the following examples:

[0180] As an example, in the case where the second information is used to request the acceptance of the first information, if the terminal device is in the RRC idle state before sending the first information, the terminal device sends the fourth information to the fourth network element, and the fourth network element receives the fourth information accordingly. The fourth information is used to request the establishment of a user plane session required for the transmission of computing services.

[0181] The fourth network element possesses a Computing Service Connection Management (CMF) function. For example, the fourth network element can be an independent network element, a Computing Service Management (SMF), or an access network device. For instance, if the fourth network element is an SMF, the fourth information can be carried in a service request message or a PDU session setup request message. If the second information indicates that computing services are provided to the terminal device via the FeIN, the fourth information indicates the establishment of a dedicated computing session. For example, the fourth information indicates at least one of the following: indicating that the computing type is a dedicated computing session, indicating the ID of the computing session, or the ID information of the FeIN. Thus, the fourth network element can establish a corresponding data transmission channel based on the fourth information.

[0182] As another example, if the second information is used to request the acceptance of the first information, and if the relevant data transmission channel for transmitting computing services has been established before the terminal device sends the first information, then the terminal device sends computing data to the second network element. Optionally, if the second information indicates the address information of the second network element or the address information of the application server, the terminal device determines the QoS flow and / or data radio bearer (DRB) for transmitting computing data based on the second information.

[0183] As another example, if the second information is used to reject the request of the first information, and the second information indicates that the network cannot provide the requested computing service to the terminal device, then the terminal device discards the data packets in the buffer. Since the network cannot support the computing service requested by the terminal device, the terminal device can perform the computing service locally.

[0184] As another example, if the first message is used to request FeIN to provide computing services to the terminal device, and the second message is used to reject the request of the first message, and the second message indicates that FeIN cannot provide services to the terminal device, then the terminal device will send the computing data packet to the cloud server.

[0185] In this embodiment, the first network element can determine whether to accept the computing service request from the terminal device based on the computing resource information of the second network element. That is, the first network element participates in the admission decision-making for computing service requests, rather than simply transmitting related data, thereby better meeting the needs of computing services. For example, the first network element can accept the computing service request from the terminal device when the second network element meets its computing service needs, ensuring that the terminal device's computing service requirements are met. Alternatively, the first network element can reject the terminal device's computing service request in advance when the second network element does not meet its computing service needs (e.g., the second network element's computing service load is too high), avoiding computing service backlog on the second network element, ensuring the speed of computing services executed by the second network element, and thus ensuring that the needs of computing services executed on the second network element are met.

[0186] Please refer to Figure 5, which is a flowchart illustrating another communication method provided in an embodiment of this application. As shown in Figure 5, the method includes, but is not limited to, the following steps.

[0187] 501, the terminal device sends the first information, and correspondingly, the first network element receives the first information.

[0188] For details on the specific implementation of step 501, please refer to the specific implementation of step 401 in Figure 4, which will not be elaborated here.

[0189] 502, the first network element sends the fifth information, and correspondingly, the second network element receives the fifth information. The fifth information includes the first information.

[0190] For example, the fifth information is used to request the second network element to provide computing services to the terminal device, and the fifth information may also carry information of the terminal device identifier (UE ID).

[0191] For example, when the first information includes end-to-end delay, the first network element can estimate the delay required for transmission, thereby estimating the delay required for computation. Therefore, in the fifth information, the first network element can indicate the expected computation delay requirement to the second network element.

[0192] 503, the second network element sends the sixth message, and correspondingly, the first network element receives the sixth message.

[0193] The second network element determines the sixth information based on its computing resource information and the fifth information. The sixth information is used to accept or reject the request from the fifth information. It is understood that the specific implementation method for the second network element to determine the sixth information can refer to the specific implementation method for the first network element to determine the second information in step 402 (such as implementation methods 1 to 4), and will not be detailed here.

[0194] For example, the sixth information may also carry information about the terminal device identifier (UE ID).

[0195] For example, the sixth information may also carry expected computational delay or end-to-end delay information, so that the first network element can determine the second information to accept or reject the terminal device's request.

[0196] For example, when the sixth piece of information is used to reject the request of the fifth piece of information, the sixth piece of information is carried in a service accept message. When the sixth piece of information is used to accept the request of the fifth piece of information, the sixth piece of information is carried in a service reject message.

[0197] 504, the first network element sends the second information to the terminal device, and the terminal device receives the second information accordingly.

[0198] For details on the specific implementation of step 504, please refer to the specific implementation of step 402 in Figure 4, which will not be elaborated here.

[0199] In this embodiment, after receiving the computing request from the terminal device, the first network element sends the computing request to the second network element. The second network element can determine whether to accept the computing request from the terminal device based on its own computing resource information, which can avoid the second network element's computing load being too high and unable to meet the needs of computing services.

[0200] Please refer to Figure 6, which is a flowchart illustrating another communication method provided in an embodiment of this application. As shown in Figure 6, the method includes, but is not limited to, the following steps.

[0201] 601, the first network element sends the first broadcast message, and the corresponding terminal device receives the first broadcast message.

[0202] The first broadcast message includes access control information, which is determined based on the computing resource information of the second network element. This access control information is used by the terminal device to access the network. The computing resource information of the second network element can be found in the preceding description and will not be detailed here.

[0203] The first network element is the access network element. For example, the first network element can be the AN device described above (such as gNB), or, in the O-RAN architecture, the first network element can be O-DU or O-CU.

[0204] As an example, the first network element obtains the computing resource information of the second network element and determines access control information based on the computing resource information of the second network element. Exemplarily, the first network element can receive the computing resource information of the second network element from the second network element or other core network elements.

[0205] As another example, the second network element generates access control information based on its computing resource information and sends the access control information to the first network element, which then receives the access control information from the second network element.

[0206] As another example, access control information can be configured through network management.

[0207] For example, the first broadcast message may be a system message from the cell where the terminal device is camped.

[0208] Access control information consists of parameter information under the unified access control (UAC) mechanism, corresponding to the first access category. When a terminal device triggers an access attempt due to computing service needs, it corresponds to the first access category. The terminal device then matches the appropriate access control information based on this first access category and attempts to access the network. This access control information indicates whether the terminal device is permitted to initiate an access attempt of type requesting the network to provide computing services.

[0209] In one possible implementation, the first access category is a dedicated access category for computing services, and the first access category can be any value from 11 to 31. In this implementation, by introducing a new access category to indicate computing services, when a terminal device has computing service requirements, it can directly determine whether to allow the request for computing services based on the access parameters corresponding to the access category.

[0210] In another possible implementation, the first access category is not a dedicated access category for computing services. For example, the first access category could be AC=3, and it could also correspond to non-paging triggered user NAS signaling transmissions. In other words, when the terminal device receives computing data, or receives an end-to-edge / end-to-cloud collaboration request from the upper layer, it determines the access category value to be AC=3. In this implementation, a computing-specific first access identity can be defined. This first access identity corresponds to the computing service, and the access identity corresponding to the terminal device includes the first access identity. A detailed explanation of the first access identity can be found below.

[0211] For example, the aforementioned access control information includes access parameters corresponding to the first access category (or the UAC parameter set corresponding to the first access category). The first access category corresponds to computing services, or in other words, the first access category corresponds to edge-to-edge collaboration / edge-to-cloud collaboration. When the terminal device receives computing data, or receives an edge-to-edge collaboration / edge-to-cloud collaboration request from the upper layer, it determines the access category to be the first access category. The access parameters corresponding to the first access category are determined by the computing resource information of the second network element. For example, the access parameters corresponding to the first access category are determined by the load information of the computing services of the second network element.

[0212] For example, the access parameters corresponding to the first access category include at least one of the following: first indication information, prohibition factor, prohibition time, and number of attempts.

[0213] The first indication information indicates whether the access identifier corresponding to the terminal device is allowed to access. It can also be understood as whether the access identifier corresponding to the terminal device is allowed to request computing services.

[0214] As an example, the first indication information may include a list of access identifiers allowed to request computing services. If the list includes the access identifier corresponding to the terminal device, the first indication information indicates that the access identifier corresponding to the terminal device is allowed to request computing services. If the list does not include the access identifier corresponding to the terminal device, the first indication information indicates that the access identifier corresponding to the terminal device is not allowed to request computing services. More specifically, the correspondence between access identifiers and the configured service attributes of the terminal device can be shown in Table 1.

[0215] Table 1

[0216] As another example, the first indication information may include a list of access identifiers that are prohibited from requesting computing services. If the list includes the access identifier corresponding to the terminal device, the first indication information indicates that the access identifier corresponding to the terminal device is prohibited from requesting computing services. If the list does not include the access identifier corresponding to the terminal device, the first indication information indicates that the access identifier corresponding to the terminal device is allowed to request computing services.

[0217] As another example, the first indication information indicates whether one or more access identifiers are allowed to access, including the access identifier corresponding to the terminal device. For example, the first indication information includes one or more bits, each bit corresponding to an access identifier, used to indicate whether the corresponding access identifier is allowed to request computation services. For example, a bit value of 0 indicates that the corresponding access identifier is allowed. A bit value of 1 indicates that the corresponding access identifier is not allowed. Similarly, a bit value of 1 indicates that the corresponding access identifier is allowed. A bit value of 0 indicates that the corresponding access identifier is not allowed.

[0218] Optionally, the access identifier corresponding to the terminal device includes a first access identifier, which corresponds to a computing service. This first access identifier can be a newly defined access identifier used to correspond to the computing service. By introducing a new access identifier, the computing service is indicated, thereby indicating whether the terminal device is allowed to request the computing service. For example, the first access identifier can be any value from 3 to 10. The aforementioned first indication information is used to indicate whether the first access identifier is allowed to request the computing service, thereby indicating whether the terminal device's computing service request is allowed.

[0219] The first indication information can be determined by the load information of the computing services of the second network element. For example, if the load of the computing services of the second network element is permissible (e.g., the load is light), the first indication information indicates that the access identifier (e.g., the first access identifier) ​​corresponding to the terminal device is allowed to access. Conversely, if the load of the computing services of the second network element is not permissible (e.g., the load is heavy), the first indication information indicates that the access identifier (e.g., the first access identifier) ​​corresponding to the terminal device is prohibited from accessing. In this way, when the computing services of the second network element are heavily loaded, the terminal device can be prohibited from requesting computing services, avoiding excessive backlog of tasks on the second network element, thereby ensuring the latency requirements of the computing services being executed by the second network element.

[0220] The aforementioned prohibition factor indicates the probability that a terminal device is allowed to request computing services. The value of this prohibition factor can be determined by the set {p00, p05, p10, ...}. For example, a prohibition factor value of p10 indicates a 10% probability that the terminal device is allowed to request computing services. The value of this prohibition factor can be determined by the load information of the computing services of the second network element. For example, the heavier the load of the computing services of the second network element (e.g., the less remaining computing resources the second network element has), the smaller the value of the prohibition factor. Thus, even when the computing services of the second network element are heavily loaded, the probability of the terminal device being allowed to request computing services is lower, preventing excessive task backlog on the second network element, thereby ensuring the computing speed of the computing services being executed by the second network element, and ultimately guaranteeing the needs of the computing services being executed by the second network element.

[0221] The aforementioned blocking time indicates the waiting time for a terminal device to re-request a computing service after its request has been rejected, or, alternatively, the waiting time for a terminal device to attempt to request a computing service again after being blocked from doing so, or the minimum interval between two consecutive access attempts. This blocking time is determined by the computing service load information of the second network element. For example, the heavier the computing service load of the second network element (e.g., the less remaining computing resources the second network element has), the longer the blocking time. Thus, when the computing service load of the second network element is heavy, the terminal device needs to wait longer, thereby avoiding frequent attempts to request computing services and reducing signaling overhead.

[0222] The aforementioned number of attempts indicates the maximum number of times the terminal device can attempt to request computing services. This number of attempts is determined by the load information of the computing services of the second network element. For example, the heavier the load of the computing services of the second network element (e.g., the less remaining computing resources the second network element has), the fewer attempts will be made. Thus, when the computing services of the second network element are heavily loaded, the number of times the terminal device attempts to request computing services is reduced, thereby reducing signaling overhead.

[0223] For example, the aforementioned access control information corresponds to a computing service, determined by the load information of that computing service. In this example, the computing resources of the second network element are divided at the granularity of computing services. Each computing service among the multiple computing services supported by the second network element corresponds to a set of access control information, and the broadcast message includes the access control information corresponding to each computing service. For instance, through computing-specific AC parameters, the terminal device matches the corresponding access control information, which is a list of access control parameters. Each set of access control parameters in the list can be distinguished by the identifier of the corresponding computing service.

[0224] For example, the access control information mentioned above corresponds to a set of computing services, which is determined by the load information of the set of computing services. In this example, the computing resources of the second network element can also be divided at the granularity of a set of computing services. For example, multiple computing services in the set of computing services share computing resources, and these multiple computing services correspond to the same access control information.

[0225] 602, The terminal device determines to send first information based on the access control information, and the first information is used to access the network.

[0226] When the terminal device meets the triggering conditions for the computing service, the terminal device determines whether to send the first information based on the access control information. The triggering conditions include at least one of the following: receiving computing data and / or end-to-cloud collaboration instructions from the upper layer, or receiving end-to-cloud collaboration instructions from the network device.

[0227] For example, when the terminal device is in the RRC Idle state or the RRC Inactive state, the terminal device receives computing data and / or end-to-cloud collaboration instructions from the upper layer, and the terminal device meets the triggering conditions for computing services. At this time, the terminal device wishes to perform computing services by utilizing the network's computing resources. The terminal then selects to perform access control based on the aforementioned access control information to determine whether to send the first information.

[0228] For example, when a terminal device receives an end-to-cloud collaboration instruction from a network device, the terminal device meets the triggering conditions for computing services. The end-to-cloud collaboration instruction can be carried via an RRC release message. At this time, if the terminal device receives computing data and / or an end-to-cloud collaboration request from the upper layer, it can choose to execute access control based on the aforementioned access control information. The access control process is described in the preceding text.

[0229] For example, the access parameters corresponding to the first access category include at least one of the following: first indication information, prohibition factor, prohibition time, and number of attempts (or maximum number of attempts). The terminal device can determine whether it is allowed to initiate an access attempt of type requesting network computing services based on the access parameters corresponding to the first access category, thereby determining whether to send the first information. If the terminal device successfully attempts to access, the terminal device determines to send the first information. If the terminal device attempts to access, the terminal device determines not to send the first information.

[0230] For example, based on the access control information described in step 601, if the first indication information indicates that the access identifier corresponding to the terminal device is allowed to access, the terminal device considers the access attempt successful and thus determines to send the first information. If the terminal device corresponds to multiple access identifiers, and the first indication information indicates that any one of the multiple access identifiers is allowed to access, it means that the terminal device is allowed to initiate an access attempt of type requesting the network to provide computing services. Therefore, the terminal device determines to send the first information, using this first information to initiate an access attempt of type requesting the network to provide computing services.

[0231] For example, when the first indication information indicates that the access identifier corresponding to the terminal device is not allowed to access, the terminal device generates a first random number. If the first random number is less than or equal to the prohibition factor, the terminal device considers the access attempt successful and thus determines to send the first information. The first random number is randomly generated by the terminal device and is greater than 0 and less than 1.

[0232] For example, if the first random number is greater than the prohibition factor, the terminal device can wait for a period of time before retrying access. This period is determined by the prohibition time in the access parameters. For instance, after the terminal device waits for the timer to expire, it regenerates the first random number and determines whether access is allowed based on the relationship between the first random number and the prohibition factor. The duration of this timer is determined by the prohibition time. If the regenerated first random number is less than or equal to the prohibition factor, the access attempt is successful. Otherwise, the terminal device determines that the access attempt has failed and will not attempt to access again. Optionally, the terminal device discards the calculated data in the buffer.

[0233] For example, if the first random number generated by the terminal device in the Nth iteration is greater than the prohibition factor, the terminal device has reached the maximum number of attempts to access the network, and the access attempt is determined to have failed, and no further access attempts will be made. N is the maximum number of access attempts in the access parameters.

[0234] For example, the second network element is FeIN, meaning the access control information is determined based on the computing resource information of FeIN. If the access attempt is successful, the terminal device can request FeIN to provide computing services to the terminal device. Optionally, when the access attempt fails, the terminal device can fall back to UAC parameter access based on communication load, thereby sending the computing data to AS / EAS for processing.

[0235] For example, the second network element is AS / EAS, meaning the access control information is determined based on the computing resource information of AS / EAS. If the access attempt is successful, the terminal device can request AS / EAS to provide computing services to the terminal device.

[0236] For example, the access control information is determined jointly based on the computing resource information of FeIN / AS / EAS. If the access attempt is successful, the terminal device can request the network to provide computing services for the terminal device.

[0237] In one possible implementation, the first information attempts to access the network due to computing service needs; in other words, the first information is used by the terminal device to request computing services from the network. For example, the first information includes a first cause value, which is determined based on a first access category and / or a first access identifier. For example, the NAS layer of the terminal device obtains the first cause value by mapping the first access category and / or the first access identifier; the description of the first cause value is provided above.

[0238] Optionally, the method shown in Figure 6 further includes steps 603 and 604.

[0239] 603, the terminal device sends the first information, and correspondingly, the first network element receives the first information.

[0240] 604, the first network element sends the second information, and the corresponding terminal device receives the second information.

[0241] For details on the implementation of steps 603 and 604, please refer to the implementation of steps 401 and 402 in Figure 4, which will not be described in detail here.

[0242] In this embodiment, access control information allows the computing resource information of the second network element to influence the probability that a terminal device is allowed to request computing services. The terminal device can assess the computing status of the second network element in advance based on this access control information, thereby determining whether to initiate a computing service request. For example, when the second network element's computing status is good (e.g., light load), sending the first information to request computing services better guarantees the performance requirements of the terminal device's computing services. Conversely, when the second network element's computing status is poor (e.g., heavy load), not sending the first information reduces signaling overhead.

[0243] The following describes the communication device provided in the embodiments of this application.

[0244] This application divides the communication device into functional modules according to the above method embodiments. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated modules can be implemented in hardware or as software functional modules. It should be noted that the module division in this application is illustrative and only represents one logical functional division; other division methods may be used in actual implementation. The communication device of the embodiments of this application will be described in detail below with reference to Figures 7 to 9.

[0245] Figure 7 is a schematic diagram of a communication device provided in an embodiment of this application. As shown in Figure 7, the communication device includes a processing module 701 and a transceiver module 702. The transceiver module 702 can implement corresponding communication functions, and the processing module 701 is used to implement corresponding processing functions. For example, the transceiver module 702 can also be called an interface, a communication interface, or a communication module, etc.

[0246] In some embodiments of this application, the communication device can be used to perform the actions performed by the first network element in the above method embodiments. In this case, the communication device can be the first network element itself or a chip or functional module used to implement the first network element. The transceiver module 702 is used to perform the transceiver-related operations of the first network element in the above method embodiments, and the processing module 701 is used to perform the processing-related operations of the first network element in the above method embodiments.

[0247] For example, the transceiver module 702 is used to receive or input first information and send or output second information.

[0248] Processing module 701 is used to determine the second information.

[0249] Optionally, the transceiver module 702 is used to receive or input third-party information.

[0250] Optionally, the transceiver module 702 is used to send or output the first broadcast message.

[0251] It is understood that specific descriptions of the first information, second information, third information, first broadcast message, etc., can be found in the relevant descriptions in the above method embodiments, and will not be elaborated here.

[0252] Reusing Figure 7, in some other embodiments of this application, the communication device can be used to perform the actions performed by the terminal device in the above method embodiments. In this case, the communication device can be the terminal device itself or a chip or functional module configurable in the terminal device. The transceiver module 702 is used to perform the transceiver-related operations of the terminal device in the above method embodiments, and the processing module 701 is used to perform the processing-related operations of the terminal device in the above method embodiments.

[0253] For example, the transceiver module 702 is used to receive or input a first broadcast message; the processing module 701 is used to determine to send the first information. The transceiver module 702 is also used to send or output the first information.

[0254] Optionally, the transceiver module 702 is also used to receive or input second information.

[0255] Optionally, the transceiver module 702 is also used to send or output third information.

[0256] It is understood that specific descriptions of the first information, second information, third information, first broadcast message, etc., can be found in the relevant descriptions in the above method embodiments, and will not be elaborated here.

[0257] For example, transceiver module 702 may include radio frequency module, antenna module, etc. For example, transceiver module 702 may include pin module, etc.

[0258] Optionally, in the above embodiments, the communication device may further include a storage module, which can be used to store instructions and / or data. The processing module 701 can read the instructions and / or data from the storage module to enable the communication device to implement the aforementioned method embodiments. For example, the storage module can store the radio frequency signal transmission strategy, etc., as shown above.

[0259] For example, the transceiver module 702 may be a communication module or interface connected to the processing module 701, or the transceiver module 702 may be an input / output interface of the processing module 701.

[0260] For details regarding the specific explanations of each term, noun, or step in the above embodiments, please refer to the descriptions in the above method embodiments; they will not be detailed here.

[0261] The specific descriptions of the transceiver module and processing module shown in the above embodiments are merely examples. For the specific functions or execution steps of the transceiver module and processing module, please refer to the above method embodiments, which will not be described in detail here.

[0262] The communication device of the present application embodiments has been described above. The following describes possible product forms of the communication device. Any product possessing the functions of the communication device described in FIG8 above falls within the protection scope of the present application embodiments. The following description is merely illustrative and does not limit the product form of the communication device of the present application embodiments to this.

[0263] In one possible implementation, in the communication device shown in FIG7, the processing module 701 can be one or more processors, and the transceiver module 702 can be a transceiver, or the transceiver module 702 can also be a transmitting module and a receiving module. The transmitting module can be a transmitter, and the receiving module can be a receiver. The transmitting module and the receiving module are integrated into one device, such as a transceiver. In the embodiments of this application, the processor and the transceiver can be coupled, etc., and the connection method of the processor and the transceiver is not limited in the embodiments of this application. In the process of executing the above method, the process of sending information in the above method can be the process of the processor outputting the above information. When outputting the above information, the processor outputs the above information to the transceiver so that the transceiver can transmit it. After the above information is output by the processor, it may need to undergo other processing before reaching the transceiver. Similarly, the process of receiving information in the above method can be the process of the processor receiving the input above information. When the processor receives the input information, the transceiver receives the above information and inputs it into the processor. Furthermore, after the transceiver receives the above information, the above information may need to undergo other processing before being input into the processor.

[0264] As shown in Figure 8, the communication device 80 includes one or more processors 820 and transceivers 810.

[0265] In some embodiments of this application, the communication device can be used to execute the steps, methods, or functions performed by the first network element described above. For example, the processor 820 can be used to execute the functions or steps implemented by the processing module 701 shown in FIG. 7, and the transceiver 810 can be used to execute the functions or steps implemented by the transceiver module 702 shown in FIG. 7. For a detailed description of the processor 820 and the transceiver 810, please refer to FIG. 7 or the method embodiments shown above, which will not be described in detail here.

[0266] In other embodiments of this application, the communication device can be used to execute the steps, methods, or functions performed by the terminal device described above. For example, the processor 820 can be used to execute the functions or steps implemented by the processing module 701 shown in FIG. 7, and the transceiver 810 can be used to execute the functions or steps implemented by the transceiver module 702 shown in FIG. 7. Detailed descriptions of the processor 820 and transceiver 810 can be found in FIG. 7 or the method embodiments shown above, and will not be elaborated further here.

[0267] In various implementations of the communication device shown in Figure 8, the transceiver may include a receiver for performing a receiving function (or operation) and a transmitter for performing a transmitting function (or operation). The transceiver is also used to communicate with other devices / appliances via a transmission medium.

[0268] Optionally, the communication device 80 may further include one or more memories 830 for storing program instructions and / or data. The memory 830 is coupled to the processor 820. The coupling in this embodiment is an indirect coupling or communication connection between communication devices, units, or modules, and can be electrical, mechanical, or other forms, used for information exchange between the communication devices, units, or modules. The processor 820 may operate in conjunction with the memory 830. The processor 820 may execute program instructions stored in the memory 830. Optionally, at least one of the above-mentioned memories may be included in the processor.

[0269] This application embodiment does not limit the specific connection medium between the transceiver 810, processor 820, and memory 830. In this application embodiment, the memory 830, processor 820, and transceiver 810 are connected via a bus 840 in Figure 8. The bus is represented by a thick line in Figure 8. The connection methods between other components are only for illustrative purposes and are not intended to be limiting. The bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used in Figure 8, but this does not mean that there is only one bus or one type of bus.

[0270] In the embodiments of this application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc., and can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or being executed by a combination of hardware and software modules within the processor.

[0271] In this application embodiment, the memory may include, but is not limited to, non-volatile memory such as hard disk drive (HDD) or solid-state drive (SSD), random access memory (RAM), erasable programmable read-only memory (EPROM), read-only memory (ROM), or compact disc read-only memory (CD-ROM), etc. Memory is any storage medium capable of carrying or storing program code having instruction or data structure forms, and capable of being read and / or written by a computer (such as the communication device shown in this application), but is not limited to this. The memory in this application embodiment may also be a circuit or any other device capable of implementing storage functions, used to store program instructions and / or data.

[0272] The processor 820 is primarily used for processing communication protocols and data, controlling the entire communication device, executing software programs, and processing software program data. The memory 830 is primarily used for storing software programs and data. The transceiver 810 may include control circuitry and an antenna. The control circuitry is primarily used for converting baseband signals to radio frequency signals and processing radio frequency signals. The antenna is primarily used for transmitting and receiving radio frequency signals in the form of electromagnetic waves. Input / output devices, such as touchscreens, displays, and keyboards, are primarily used for receiving user input data and outputting data to the user.

[0273] When the communication device is powered on, the processor 820 can read the software program in the memory 830, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be transmitted wirelessly, the processor 820 performs baseband processing on the data to be transmitted and outputs the baseband signal to the radio frequency (RF) circuit. The RF circuit processes the baseband signal and transmits the RF signal outward in the form of electromagnetic waves through the antenna. When data is sent to the communication device, the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor 820. The processor 820 converts the baseband signal into data and processes the data.

[0274] In another implementation, the radio frequency circuitry and antenna can be set up independently of the processor performing baseband processing. For example, in a distributed scenario, the radio frequency circuitry and antenna can be arranged remotely, independent of the communication device.

[0275] The communication device shown in this application embodiment may also have more components than those in Figure 8, and this application embodiment does not limit this. The methods executed by the processor and transceiver shown above are only examples, and the specific steps executed by the processor and transceiver can be referred to the methods described above.

[0276] In another possible implementation, in the communication device shown in Figure 7, the processing module 701 can be one or more logic circuits, and the transceiver module 702 can be an input / output interface, or a communication interface, or an interface circuit, or an interface, etc. Alternatively, the transceiver module 702 can also be a transmitting module and a receiving module. The transmitting module can be an output interface, and the receiving module can be an input interface. The transmitting module and the receiving module are integrated into one module, such as an input / output interface. As shown in Figure 9, the communication device shown in Figure 9 includes a logic circuit 901 and an interface 902. That is, the above-mentioned processing module 701 can be implemented using the logic circuit 901, and the transceiver module 702 can be implemented using the interface 902. Among them, the logic circuit 901 can be a chip, a processing circuit, an integrated circuit, or a system-on-a-chip (SoC) chip, etc., and the interface 902 can be a communication interface, an input / output interface, pins, etc. For example, Figure 9 illustrates the above-mentioned communication device as a chip, which includes the logic circuit 901 and the interface 902.

[0277] In this embodiment, the logic circuit and the interface can also be coupled to each other. The specific connection method of the logic circuit and the interface is not limited in this embodiment. For example, the logic circuit 901 can be used to execute the functions or steps implemented by the processing module 701 shown in FIG. 7, and the interface 902 can be used to execute the functions or steps implemented by the transceiver module 702 shown in FIG. 7. For a detailed description of the logic circuit 901 and the interface 902, please refer to FIG. 7 or the method embodiment shown above, which will not be detailed here.

[0278] The communication device shown in the embodiments of this application can implement the method provided in the embodiments of this application in hardware form, or it can implement the method provided in the embodiments of this application in software form, etc., and the embodiments of this application do not limit it in this way.

[0279] Furthermore, embodiments of this application also provide a communication system, which includes a first network element and a terminal device, which can be used to execute the methods in any of the foregoing embodiments.

[0280] This application also provides a computer program for implementing the operations and / or processes performed by the first network element or terminal device in the method provided in this application.

[0281] This application also provides a computer-readable storage medium storing computer code, which, when executed on a computer, causes the computer to perform the operations and / or processes performed by the first network element or terminal device in the method provided in this application.

[0282] This application also provides a computer program product, which includes computer code or a computer program, which, when run on a computer, causes the operations and / or processes performed by a first network element or terminal device in the method provided in this application to be executed.

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

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

[0285] Furthermore, the functional modules in the various embodiments of this application can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0286] If the integrated module is implemented as a software functional module 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 application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a readable storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned readable storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

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

Claims

1. A communication method, characterized in that, Applied to the first network element, the method includes: Receive first information from the terminal device, the first information being used to request computing services; Send a second message to the terminal device; the second message is determined based on the computing resource information of the second network element, and the second message is used to accept or reject the request of the first message, and the second network element is used to provide computing services.

2. The method according to claim 1, characterized in that, The first information includes a first cause value and / or first calculation information, wherein the first cause value corresponds to a calculation service; the first calculation information includes the computing capability information and / or computing requirement information of the terminal device.

3. The method according to claim 2, characterized in that, The first reason value is carried in the reason value field of the RRC establishment request message. The first reason value corresponds to the first access category and / or the first access identifier, and the first access category and / or the first access identifier corresponds to the computing service.

4. The method according to claim 2, characterized in that, The first reason value is carried in the computation request message.

5. The method according to any one of claims 2-4, characterized in that, The computing capability information and / or the computing demand information include information about the first computing service; the computing resource information of the second network element includes information about the computing services supported by the second network element and the load information of the computing services of the second network element. The second information is determined based on the computing resource information of the second network element. The second information is used to accept or reject the request of the first information, including: If the second network element supports the first computing service and the load allows, the second information is used to accept the request from the first information; or, If the second network element supports the first computing service and the load does not allow it, the second information is used to reject the request from the first information; or... If the second network element does not support the first computing service, the second information is used to reject the request of the first information.

6. The method according to any one of claims 1-5, characterized in that, The second network element is an access network element or a core network element; The first information is used to request computing services, including: the first information is used to request the second network element to provide computing services to the terminal device.

7. The method according to claim 6, characterized in that, The second information is used to reject the request of the first information, and the method further includes: The terminal device receives third information, which is used to request a third network element to provide computing services to the terminal device. The third network element is a network element in the data network or an edge application server (EAS).

8. The method according to claim 6 or 7, characterized in that, The second information is used to reject the request of the first information. The second information also indicates at least one of the following: waiting time, the second network element being unable to provide computing services to the terminal device, information of the first cell, and instructing the terminal device to request computing services from the third network element. The waiting time is used to instruct the terminal device to request computing services from the second network element again after the waiting time. The first cell supports computing services. The third network element is a network element in the data network or an edge application server (EAS).

9. The method according to any one of claims 1 to 5, characterized in that, The second network element is an edge computing server, and the first information is used to request computing services, including: the first information is used to request the second network element to provide computing services for the terminal device.

10. The method according to any one of claims 1-9, characterized in that, The method further includes: Receive computing resource information from the second network element.

11. The method according to any one of claims 1-10, characterized in that, The computing resource information of the second network element includes at least one of the following: the load information of the computing services of the second network element, the information of the computing services supported by the second network element, and the service quality agreement (SLA) information of the second network element.

12. A communication method, characterized in that, Applied to a terminal device, the method includes: Receive a first broadcast message, the first broadcast message including access control information, the access control information being determined based on the computing resource information of the second network element; The first information to be sent is determined based on the access control information, and the first information is used to request the computing service.

13. The method according to claim 12, characterized in that, The access control information includes access parameters corresponding to a first access category, where the first access category corresponds to a computing service; determining to send the first information based on the access control information includes: The first information to be sent is determined based on the access parameters corresponding to the first access category.

14. The method according to claim 13, characterized in that, The access parameters corresponding to the first access category include first indication information and prohibition factor; The first indication information is used to indicate whether the access identifier corresponding to the terminal device is allowed to access; The step of determining the first information to be sent based on the access parameters corresponding to the first access category includes: If the first indication information indicates that the access identifier corresponding to the terminal device is allowed to access, then determine to send the first information; or... If the first indication information indicates that the access identifier corresponding to the terminal device is not allowed to access, and the first random number is less than or equal to the prohibition factor, the first information is determined to be sent; wherein the first random number is generated by the terminal device.

15. The method according to claim 14, characterized in that, The access identifier corresponding to the terminal device includes a first access identifier, which corresponds to a computing service.

16. The method according to claim 14 or 15, characterized in that, The access parameters corresponding to the first access category also include at least one of the following: the blocking time and the number of attempts.

17. The method according to any one of claims 12-16, characterized in that, The first information includes a first cause value and / or first calculation information, wherein the first cause value corresponds to a calculation service; the first calculation information includes the computing capability information and / or computing requirement information of the terminal device.

18. The method according to claim 17, characterized in that, The first reason value is carried in the reason value field of the RRC establishment request message. The first reason value corresponds to the first access category and / or the first access identifier, and the first access category and / or the first access identifier corresponds to the computing service.

19. The method according to claim 17, characterized in that, The first reason value is carried in the computation request message.

20. The method according to any one of claims 12-19, characterized in that, The second network element is an access network element or a core network element; The first information is used to request computing services, including: the first information is used to request the second network element to provide computing services to the terminal device.

21. The method according to claim 20, characterized in that, The method further includes: The system receives a second message, which is used to reject the request of the first message. The second message also indicates at least one of the following: a waiting time, the second network element being unable to provide computing services to the terminal device, information about the first cell, and instructing the terminal device to request computing services from a third network element. The waiting time is used to instruct the terminal device to request computing services from the second network element again after the waiting time. The first cell supports the computing request. The third network element is a network element in the data network or an edge application server (EAS).

22. The method according to claim 21, characterized in that, The method further includes: Send a third message, which is used to request the third network element to provide computing services to the terminal device.

23. The method according to claims 12-19, characterized in that, The second network element is an access network element, a core network element, an edge application server, or a network element in a data network; the method further includes: The second information is received, which instructs the second network element to provide computing services to the terminal device.

24. A communication device, characterized in that, Includes a module for performing the method as described in any one of claims 1-23.

25. A communication device, characterized in that, Includes a processor, the processor being configured to cause the communication device to implement the method as described in any one of claims 1-23.

26. A communication device, characterized in that, It includes logic circuitry and an interface, the interface being used for inputting and / or outputting information, and the logic circuitry being used to enable the communication device to implement the method as described in any one of claims 1-23.

27. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store a computer program, which, when executed by a computer, performs the method as described in any one of claims 1-23.

28. A computer program product, characterized in that, When the computer program product is executed by a computer, the method described in any one of claims 1-23 is performed.

Images