WO2025223329A1 - Communication method, apparatus and system, related device, storage medium, and computer program product - Google Patents

Abstract

Disclosed in embodiments of the present application are a communication method, apparatus and system, a related device, a storage medium, and a computer program product. The system comprises a first network function and an access network device. The access network device comprises a first functional entity and a second functional entity, the first functional entity is used for implementing one or more network capabilities on the basis of various network resources in a communication network, and the second functional entity is used for managing the one or more network capabilities and providing the one or more network capabilities for the first network function. The first network function is used for performing service exposure on the basis of the various network capabilities provided by one or more connected access network devices.

Description

Communication methods, devices, systems, related equipment, storage media, and computer program products

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is based on and claims priority to Chinese Patent Application No. 202410509035.1, filed on April 25, 2024, the entire contents of which are incorporated herein by reference.

Technical Field

This application relates to the field of wireless communication technology, and in particular to a communication method, apparatus, system, related equipment, storage medium, and computer program product.

Background Technology

The 5G (5th Generation Mobile Communication Technology) protocol architecture defines the Distributed Unit (DU) and Centralized Unit (CU) of the base station. The next-generation Node B-CU-Control Plane (gNB-CU-CP) is responsible for connection establishment control, while the next-generation Node B-CU-User Plane (gNB-CU-UP) and DU are responsible for data transmission and processing. This network architecture, separating the signaling plane and user plane, effectively meets connection-oriented service requirements, enabling efficient connection establishment and data transmission.

The 6th Generation Mobile Communication Technology (6G) network will introduce multi-dimensional capabilities such as computing power, intelligence, and sensing, and will feature flexible and customizable network characteristics. These new capabilities and characteristics require a restructuring of the wireless communication network architecture, necessitating the design of a new network architecture to realize the new capabilities and characteristics of the 6G wireless access network. However, currently, it is impossible to integrate multi-dimensional capabilities such as sensing, computing power, and intelligence while retaining the high bandwidth, low latency, and compatibility of traditional networks.

Summary of the Invention

To address the related technical problems, embodiments of this application provide a communication method, apparatus, system, related equipment, storage medium, and computer program product.

To achieve the above objectives, the technical solution of this application embodiment is implemented as follows:

In a first aspect, embodiments of this application provide a communication system, including a first network function and an access network device, wherein...

The access network device includes a first functional entity and a second functional entity; the first functional entity is configured to implement one or more network capabilities based on various network resources in the communication network, and the second functional entity is configured to manage the one or more network capabilities and provide the one or more network capabilities to the first network function.

The first network function is configured to provide services based on various network capabilities provided by one or more access network devices connected to the network.

Secondly, embodiments of this application also provide a communication method applied to a first network function; the method includes:

Services are provided based on various network capabilities offered by one or more connected access network devices; wherein the network capabilities are implemented by the corresponding access network device through a first functional entity based on various network resources in the communication network, and provided through a second functional entity.

Thirdly, embodiments of this application also provide a communication method applied to a first functional entity in an access network device; the method includes:

One or more network capabilities are implemented based on various network resources in the communication network; the one or more network capabilities are managed by a second functional entity in the access network device and provided by the second functional entity to a first network function that manages the access network device, and the one or more network capabilities are used by the first network function to provide services.

Fourthly, embodiments of this application also provide a communication method applied to a second functional entity in an access network device; the method includes:

The device manages one or more network capabilities and provides these network capabilities to a first network function that manages the access network device. The one or more network capabilities are implemented by a first functional entity in the access network device based on various network resources in the communication network, and the one or more network capabilities are used by the first network function to provide services.

Fifthly, embodiments of this application also provide a communication method applied to an access network device; the method includes:

A first functional entity implements one or more network capabilities based on various network resources in the communication network, and a second functional entity manages the one or more network capabilities and provides the one or more network capabilities to a first network function that manages the access network device; the one or more network capabilities are used by the first network function to provide services.

In a sixth aspect, embodiments of this application also provide a communication device applied to a first network function; the device includes a first processing unit configured to provide services based on various network capabilities provided by one or more connected access network devices; wherein the network capabilities are implemented by the corresponding access network device through a first functional entity based on various network resources in the communication network, and provided through a second functional entity.

In a seventh aspect, embodiments of this application also provide a communication device applied to a first functional entity in an access network device; the device includes a second processing unit configured to implement one or more network capabilities based on various network resources in the communication network; the one or more network capabilities are managed by the second functional entity in the access network device and provided by the second functional entity to a first network capability that manages the access network device, and the one or more network capabilities are used by the first network capability to provide services.

In a ninth aspect, embodiments of this application also provide a communication apparatus applied to a second functional entity in an access network device; the apparatus includes a third processing unit configured to manage one or more network capabilities and to provide the one or more network capabilities to a first network function managing the access network device; the one or more network capabilities are implemented by the first functional entity in the access network device based on various network resources in the communication network, and the one or more network capabilities are used by the first network function to provide services.

In a tenth aspect, embodiments of this application also provide an access network device, including a first functional entity and a second functional entity; wherein,

The first functional entity is configured to implement one or more network capabilities based on various network resources in the communication network;

The second functional entity is configured to manage the one or more network capabilities and provide the one or more network capabilities to the first network function; the one or more network capabilities are used to manage the service exposure of the first network function of the access network device.

Eleventhly, embodiments of this application also provide a communication device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the steps of the methods described in the second, third, or fourth aspects.

In a twelfth aspect, embodiments of this application also provide a computer-readable storage medium having a computer program stored thereon that, when executed by a processor, implements the steps of the methods described in the second, third, or fourth aspects.

In a thirteenth aspect, embodiments of this application also provide a computer program product, including a computer program that, when executed by a processor, implements the steps of the methods described in the second, third, or fourth aspects.

The communication method, apparatus, system, related equipment, storage medium, and computer program product provided in this application embodiment enable the communication system to implement one or more network capabilities based on various network resources through a first functional entity in the access network device, and to manage the one or more network capabilities and provide them to a first network function through a second functional entity in the access network device. This allows the first network function to provide services based on the various network capabilities provided by the managed access network devices. The network open capabilities can reside in the first network function and be managed separately from traditional data transmission services. This achieves the provision of open capabilities while ensuring the system performance of traditional data services, realizing a new network architecture characterized by elasticity, flexibility, on-demand, and openness, which can meet various application scenarios.

Attached Figure Description

Figure 1 is a schematic diagram of the composition structure of the communication system according to an embodiment of this application;

Figure 2 is a schematic diagram of the process of adding the second module to the access network device according to an embodiment of this application;

Figure 3 is a schematic diagram of task management corresponding to each network capability in the access network device according to an embodiment of this application;

Figure 4 is a flowchart illustrating the communication method according to an embodiment of this application;

Figure 5 is a schematic flowchart of the communication method according to an embodiment of this application;

Figure 6 is a schematic diagram of the initial terminal access process in related technologies;

Figure 7 is a schematic diagram of the initial terminal access process according to an embodiment of this application;

Figure 8 is a flowchart illustrating the communication method according to an embodiment of this application.

Figure 9 is a schematic flowchart of the communication method according to an embodiment of this application;

Figure 10 is a schematic diagram of a communication network architecture according to an embodiment of this application;

Figure 11 is a schematic diagram of the connection relationship between various network elements in the communication system of this application embodiment;

Figure 12 is a schematic diagram of data flow in the communication system according to an embodiment of this application;

Figure 13 is a functional distribution block diagram of a communication system according to an embodiment of this application;

Figure 14 is a functional distribution block diagram of an xNB according to an embodiment of this application;

Figure 15 is a schematic diagram of a service process of a communication system according to an embodiment of this application for network capabilities related to perception.

Figure 16 is a flowchart illustrating the acquisition of perception-related strategies according to an embodiment of this application;

Figure 17 is a schematic diagram of another service process for network capabilities related to perception in the communication system of this application embodiment;

Figure 18 is a schematic diagram of a service process of a communication system according to an embodiment of this application for network capabilities related to data services;

Figure 19 is a schematic diagram of a service process of a communication system according to an embodiment of this application for network capabilities related to computing power;

Figure 20 is a schematic diagram of a service process of a communication system according to an embodiment of this application for intelligent network capabilities;

Figure 21 is a schematic diagram of the composition structure of a communication device according to an embodiment of this application;

Figure 22 is a schematic diagram of the composition structure of the communication device according to an embodiment of this application;

Figure 23 is a schematic diagram of the composition structure of the communication device according to an embodiment of this application;

Figure 24 is a schematic diagram of the composition structure of the access network device according to an embodiment of this application;

Figure 25 is a schematic diagram of the network function in an embodiment of this application.

Detailed Implementation

The present application will now be described in further detail with reference to the accompanying drawings and specific embodiments. Obviously, the described embodiments are only some, not all, of the embodiments of the present application. All other embodiments obtained by those skilled in the art based on the embodiments of the present application without inventive effort are within the scope of protection of the present application.

In the description of the embodiments of this application, it should be noted that the terms "first," "second," "third," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance. These terms are only used to distinguish one element (or threshold, application, instruction, or operation) from another element (or threshold, application, instruction, or operation). For example, a first operation may be referred to as a second operation, and a second operation may be referred to as a first operation, without departing from the scope of this application. Both the first operation and the second operation are operations, but they are not the same operation.

The term "and/or" in the embodiments of this application refers to any and all possible combinations including one or more of the associated listed items. It should also be noted that, when used in this specification, "including/comprising" specifies the presence of the stated features, integers, steps, operations, elements, and/or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, and/or components and/or groups thereof.

The steps in the embodiments of this application are not necessarily processed in the order described. The steps can be rearranged, deleted, or added as needed. The step descriptions in the embodiments of this application are only optional combinations of sequences and do not represent all possible combinations of steps in the embodiments of this application. The order of steps in the embodiments should not be considered as a limitation of this application.

This application provides a communication system. Figure 1 is a schematic diagram of the composition structure of the communication system according to an embodiment of this application. As shown in Figure 1, the communication system 100 includes a first network function 110 and an access network device 120, wherein...

The access network device 120 includes a first functional entity 121 and a second functional entity 122; the first functional entity 121 is configured to implement one or more network capabilities based on various network resources in the communication network, and the second functional entity 122 is configured to manage the one or more network capabilities and provide the one or more network capabilities to the first network function.

The first network function 110 is configured to provide services based on various network capabilities provided by one or more access network devices connected to the network.

In this embodiment, the first functional entity 121 can implement one or more network capabilities, the second functional entity 122 can manage the one or more network capabilities, and the first network function 110 can provide service opening for the one or more network capabilities, thereby forming a three-domain division of the access network in the functional domain, management domain, and service domain. The network opening capability of the access network resides in the first network function 110 and can be managed separately from traditional data transmission services, so as to provide capability opening while ensuring the system performance of traditional data services.

For example, the first functional entity 121 may be a user plane function/entity of the access network device 120, and the second functional entity 122 may be a control plane function/entity of the access network device 120. Alternatively, the first functional entity 121 may be a function/entity of the access network device 120 oriented towards a functional domain/resource domain, and the second functional entity 122 may be a function/entity of the access network device 120 oriented towards a management domain/control domain.

In this embodiment, a first network function 110 can connect to one or more access network devices 120, and an access network device 120 can be connected to one and only one first network function 110 at any given time.

As an optional implementation, the first network function 110 can be accessed by the core network or the first network function 110 is a network function in the core network. The access network device 120 can be connected to the authentication management function (AMF) in the core network. For example, the control interface between the communication system and the core network can adopt the Stream Control Transmission Protocol (SCTP) protocol, and the service interface can use the General Packet Radio Service (GPRS) Tunneling Protocol User Plane (GTPU) protocol.

It should be noted that, in this embodiment, the first network function 110 is at least a device capable of providing services for one or more network capabilities. Specifically, it can be a server, a network function (NF), an access network device, or a core network device. For example, the first network function 110 can be an independent network device, or it can be a device that includes functions/modules/components/units capable of providing services for one or more network capabilities. For example, it can be one or more network functions or devices combined with core network devices, network functions (such as Network Exposure Function (NEF)), or access network devices. It is understood that this application does not limit the implementation form of the first network function; any device capable of implementing the function of the first network function in this application is within the protection scope of this application.

In some embodiments, the first network function 110 and the access network device 120 can interact via a first interface, which includes a control plane interface and a data plane interface; and/or, the first functional entity 121 and the second functional entity 122 can interact via a second interface. For example, the first interface is an open interface (OI interface), which may include a control plane interface and a data plane interface. The control plane interface may use SCTP or User Datagram Protocol (UDP) interface protocol, and the data plane interface may use the UDP interface protocol. The second interface may, for example, use the F1-C (i.e., the control plane between the CU and DU) interface protocol.

In some embodiments, the external interface of the first network function 110 can be implemented using service-oriented technology, and can be consistent with the core network service-oriented protocol standard. For example, the external capability opening interface uses the Quick UDP Internet Connections (QUIC) protocol. That is, the first network function can be configured to complete the service-oriented interface for opening external network capabilities and the centralized management of multi-dimensional capabilities provided by one or more access network devices. The service-oriented interface can be configured, for example, to implement external capability opening and security authentication, and to realize the division of access network function security interfaces. The centralized management of multi-dimensional capabilities means acting as the "intelligent brain" in the access network, which can include the management of multi-dimensional capabilities such as computing power, intelligence, data, and security, and realize the on-demand allocation and hierarchical management of capabilities.

As an example, the access network device can be responsible for the management and service of traditional network wireless communication capabilities, as well as multi-dimensional capabilities such as computing power, intelligence, data, and sensing. Exemplarily, the second functional entity can be understood as the cerebellum of the access network, and may include an interface layer, a service management layer, a sub-task management layer, and process control, etc. The first functional entity can be understood as the embodiment of the access network's capabilities, and may include user plane data processing functions, state management, sensing plane management functions, data plane data management functions, mobile computing power scheduling and resource selection functions, etc. The second functional entity (cerebellum) can independently provide the ability to provide computing power, intelligence, and data services to devices (e.g., mobile terminals) within the wireless access network, or together with the first network function, implement a distributed-centralized hierarchical management mechanism for network capabilities. In this embodiment, each sub-service layer within the access network device can be embodied in a service-oriented manner, realizing task management of each sub-service layer and enabling the combination and invocation of capabilities between sub-tasks.

The communication system of this application embodiment implements one or more network capabilities based on various network resources through a first functional entity in the access network device, and manages the one or more network capabilities and provides them to a first network function through a second functional entity in the access network device. This enables the first network function to provide services based on the various network capabilities provided by the managed access network devices. The network open capabilities can reside in the first network function and be managed separately from traditional data transmission services. This achieves the goal of providing open capabilities while ensuring the system performance of traditional data services, realizing a new network architecture characterized by elasticity, flexibility, on-demand, and openness, which can meet various application scenarios.

In one optional embodiment of this application, the system 100 further includes a second network function configured to manage one or more connected first network functions 110, and/or configured to manage one or more connected access network devices 120. In this embodiment, a second network function can connect to one or more first network functions 110, and a first network function 110 can be connected to only one second network function at a time; a second network function can also connect to one or more access network devices 120, and an access network device 120 can be connected to only one second network function at a time.

In some embodiments, the second network function can implement digital twin functionality and management orchestration functionality to manage the first network function and/or access network devices. The management orchestration functionality implements human-machine management functions for the entire communication system (e.g., the access network system), enabling interaction and management of functions such as resource configuration, operational configuration, faults, alarms, performance, topology, versioning, monitoring, and services. The digital twin functionality implements intelligent management functions for the entire communication system, including digital environment modeling, data simulation, functional verification, and intelligent network autonomy, enabling intelligent management of the communication system's operational state.

In some embodiments, the second network function may support visual programming techniques.

In one optional embodiment of this application, the first network function 110 is configured to provide at least one of the following functions: a first management function representing management related to users; a second management function representing management related to service security; a third management function representing management of network capabilities related to perception; a fourth management function representing management of network capabilities related to data services; a fifth management function representing management of network capabilities related to artificial intelligence; a sixth management function representing management related to network resources; a seventh management function representing management related to policy control corresponding to each network capability; and an eighth management function representing management related to third-party service registration.

For example, the first management function can represent the management of user-related identification information, location information, identity information, registration information, authorization information, policy information, context information, etc., where the user may include, for example, various terminal devices in the communication system, or network capability providers or users; the second management function can represent the management of service security-related aspects such as user identity authentication and service security registration, and the first network function can implement external security control and authentication based on the second management function; the third management function can represent the management of the communication network's perception capabilities, and the first network function can provide service opening related to perception capabilities based on the third management function; the fourth management function can represent the management of the communication network's data service capabilities, and the first network function can provide services related to data service capabilities based on the fourth management function. Service openness; the fifth management function can represent the management of artificial intelligence capabilities of the communication network, and the first network function can provide service openness related to intelligent service capabilities based on the fifth management function; the sixth management function can represent the management of various network resources in the communication network; the seventh management function can represent the management of policy control related to network capabilities, for example, the first network function can complete the policy management related to network capabilities in the communication system together with the core network system based on the seventh management function; the eighth management function can represent the management of the service registration process provided by third-party systems or third-party functions, and the first network function can realize the enabling interface and capability openness interface between the communication system and the third-party system or third-party function based on the eighth management function, such as cloud resources, edge resources, etc.

It is understood that the first network function in this embodiment can be configured to provide at least one of the following functions: user management, security management, resource management, intelligent management, policy management, perception management, data management, and service registration. For example, it can interact with modules such as core network billing through service interfaces to realize the identity security and billing functions of the communication network's capability opening function; maintain user personal perception data and provide information services to the outside world; save user computing power characteristics and capabilities and provide external computing power services; save user intelligent optimization and network optimization related feature information for intelligent strategies of user services, etc.

In one optional embodiment of this application, the second functional entity 122 is configured to provide at least one of the following functions: a first control function, representing regulatory control related to network capabilities; a second control function, representing regulatory control related to computing resources in the communication network, wherein the computing resources include computing resources provided through access network equipment and/or computing resources provided by terminals; a third control function, representing regulatory control related to each interface corresponding to the access network; a fourth control function, representing control related to service scheduling corresponding to network capabilities; a fifth control function, representing control related to task execution corresponding to network capabilities; a sixth control function, representing control related to bearer operation corresponding to network capabilities; and a seventh control function, representing control related to context information. It should be noted that the computing resources provided through access network equipment can be designed computing resources in the access network, such as computing resources registered with the access network equipment, computing resources possessed by the access network equipment itself, and computing resources jointly provided after connection with the access network equipment. The computing resources provided by the terminal can be computing resources possessed by the terminal itself.

For example, the second functional entity can manage the registration of various network capabilities on access network devices based on the first control function, and can further realize the execution and management of on-demand combination of various network capabilities, customized services, system compatibility, capability openness, and interface openness.

Based on the second control function, the second functional entity can manage the computing power network, such as the management of computing power nodes, computing power routing, link service quality (QoS), computing power attributes, computing power strength, and on-demand allocation of computing power resources. The computing power resources in the communication system may include terminals, base stations, and core network equipment, and have the characteristics of being dedicated to the near end. In this embodiment, the second functional entity mainly meets the computing power resource usage within the communication system, and can provide low latency, mobility, and high reliability computing power services to form a mobile computing power network, and together with traditional network computing power, provide end-to-end computing network services.

Based on the third control function, the second functional entity can realize connection management and interface management related to the access network. For example, it can manage the connection and interface functions between access networks, between access networks and core networks, between access networks and air interfaces, between access networks and intelligent orchestration systems, between access networks and first network functions, and between access networks and third-party services. Specifically, it can include communication link maintenance, message encoding and decoding, visual programming message translation, message scheduling, and the ability of the network platform layer to open up third-party applications (computing power, intelligence, data, collaborative control, etc.) and the identification, translation and conversion of application layer protocols, which can realize message interaction between the access network and the application layer.

Based on the fourth control function, the second functional entity can identify and schedule service operations. For example, it can split, coordinate, and invoke service sub-layers corresponding to various network capabilities according to the service type, satisfying the service's needs for communication, sensing, data, computing, and intelligence. Each service sub-layer can guarantee resource allocation, QoS assessment, and service function combination of the subsystems corresponding to each network capability. Therefore, the second functional entity in the access network device can generate services dynamically based on the QoS characteristics of the service through process control (automatic orchestration).

Based on the fifth control function, the second functional entity can manage the task execution and task lifecycle of the service sublayer corresponding to each network capability, and complete functions such as service quality assurance and link decision-making for the task.

Based on the sixth control function, the second functional entity can realize functions such as on-demand invocation of network capabilities, connection establishment, modification, maintenance, and abnormal rollback for wireless bearers, computing bearers, data bearers, and sensing bearers.

Based on the seventh control function, the second functional entity can manage static and semi-static parameters, such as maintaining and modifying system context information, cell context information, user context information, and connection context information, or it can provide relevant resources for data services to external modules.

In some embodiments, the second functional entity is further configured to manage and/or provide services related to the one or more network capabilities provided by the terminal to the terminal. In this embodiment, the one or more network capabilities may include network capabilities related to sensing, network capabilities related to computing power, network capabilities related to data services, network capabilities related to intelligence, etc. It can be understood that, in addition to managing and using the one or more network capabilities implemented by the first functional entity based on various network resources for service provisioning by the first network function, the second functional entity can also manage and/or provide services related to the one or more network capabilities provided by the terminal to the terminal. Thus, the second network function can independently provide services related to sensing, computing power, intelligence, and data to devices in the wireless access network. Alternatively, it can work with the first network function to implement a distributed-centralized hierarchical management of the one or more network capabilities. For example, the first network function centrally manages the network capabilities provided by one or more connected access network devices and/or the network capabilities provided by terminals connected to the one or more access network devices. Simultaneously, each access network device manages the network capabilities implemented by its respective first functional entity and/or the network capabilities provided by terminals connected to the access network device.

In one optional embodiment of this application, the second functional entity 122 includes at least a first module configured to provide a first control function, the first control function representing regulatory control related to network capabilities; the first module is configured to receive a first message sent by each second module, register the network capabilities corresponding to each second module based on the first message; and send a first response message of the first message to each second module; wherein each second module is configured to provide a corresponding network capability.

In this embodiment, the second functional entity can implement the first control function based on the first module. For example, it can manage the capability registration process of each network capability in the access network device. Furthermore, it can also realize the execution and management of on-demand combination of network capabilities, customized services, system compatibility, capability openness, and interface openness. It can be understood that in this embodiment, service functions and mobile computing resources can be discovered through registration, supporting the generation of customized base station functions on demand, supporting plug-and-play of new functional features and mobile computing resources. At the same time, each second module can provide independent services or joint services. The management domain of the access network device can deploy a separate communication task system or a task system for each network capability as needed.

In some embodiments, the first message includes at least one of the following: identification information of the corresponding second module, parameter information, and link information. In this embodiment, the parameter information includes, for example, the parameter requirements for calling the second module, and the link information includes, for example, information related to establishing a link or function scheduling, such as the Transport Network Layer (TNL) or callback function.

As an example, the first response message may include at least one of the following: identification information, parameter information, and link information of the first module. For instance, the link information may include link establishment or function scheduling information, such as TNL or callback function information.

In some embodiments, the first module is further configured to send a second message to a second network function, the second message being used to notify the second network function that the access network device has added a corresponding second module; the second network function is at least configured to manage the access network device.

In some embodiments, the second module may obtain the destination address of the first message through pre-configuration, or it may obtain the destination address of the first message through the second network function.

As an optional implementation, the second network function can also modify and optimize process management based on service type or service QoS, providing basic service processes for network intelligent services.

Figure 2 is a schematic diagram of the process of adding the second module to the access network device according to an embodiment of this application. As shown in Figure 2, after completing the initialization function, the second module can send a first message to the first module, which can be used to indicate that the second module has been successfully initialized and request to be added to the access network device. The first message may include the identification information of the second module, the parameter requirements for the call, and information on establishing a link or function scheduling. After receiving the first message, the first module can register and save the second module in the second functional entity, and can send a first response message of the first message to the second module to indicate that the registration is complete. Thus, the second module can enter the service state and provide the corresponding network capabilities. The first response message may include the identification information of the first module, capability parameter information, and information on establishing a link or function scheduling. At the same time, the first module can also send a second message to the second network function to notify the second network function that the second module has been added and can work normally.

In this embodiment, the access network device can implement multiple network capabilities based on each second module. These multiple network capabilities can be embodied in a service-oriented manner to realize task management of each sub-service layer, such as the combination and invocation of capabilities between sub-tasks. Figure 3 is a schematic diagram of task management corresponding to each network capability in the access network device of this application embodiment. As shown in Figure 3, the access network device in this embodiment can at least realize communication task management, computing power task management, data task management, perception task management, and intelligent task management.

In some embodiments, the second functional entity can define business requirements, schedule resources and capabilities among various task management systems, and provide independent services for each task function, such as providing computing power services based on computing power task management and providing data services based on data task management; and support service federation among task management systems, such as intelligent services may need to connect intelligent task management, computing power task management, data task management, etc., and perception services may need to be federated with perception task management and communication task management, etc. Thus, the access network device or the second functional entity therein can deploy a separate communication task system or deploy multiple task systems for different network capabilities as needed.

In an optional embodiment of this application, the first functional entity 121 is further configured to perform secure mode and/or authentication encryption for air interface signaling. In this embodiment, the security and authentication air interface process of the communication system terminates at the first functional entity, which can shorten the signaling process path length and reduce communication latency. For example, the reconfiguration message can be generated by the first functional entity, which can enable the security mode command message and the RRC reconfiguration/reconnection message to run in parallel over the air interface, reducing access latency.

In some embodiments, during the establishment of a Signaling Radio Bearer (SRB1) signaling connection between the terminal and the access network device, admission control can be performed by the first functional entity. After the RRC connection establishment complete message is sent, the first functional entity can carry the Radio Network Temporary Identifier (RNTI) information, Short Term Mobile Subscriber Identity (S-TMSI) information, and other resource information and Non-Access Stratum (NAS) information allocated by the first functional entity to the terminal in the uplink RRC transmission (e.g., UL RRC MESSAGE TRANSFER) sent to the second functional entity. The S-TMSI information may include relevant information for selecting the core network and the F1 Application Protocol/F1 Interface Application Protocol (F1AP) identity (ID) information that identifies the terminal.

Furthermore, the second functional entity carries in the UE CONTEXT SETUP REQUEST message sent to the first functional entity the F1AP ID information allocated by the first functional entity for signaling routing of the terminal, CU-DU container parameters, encryption-related information from the core network, and Data Radio Bearer (DRB) related parameters. The CU-DU container parameters may include, for example, measurement configuration information. The encryption-related information from the core network can be used to generate parameters related to the access network encryption and integrity algorithm key. Thus, the first functional entity can perform encryption and integrity protection and generate a security mode command message to verify encryption and integrity protection with the terminal. Simultaneously, the first functional entity can also generate an RRC connection reconfiguration/reconnection message, which can be sent to the terminal before receiving a security mode complete message from the terminal. On the other hand, the first functional entity sends a UE CONTEXT SETUP RESPONSE message to the second functional entity, which may carry relevant information allocated by the first functional entity for air interface resources and information carrying to the terminal. Therefore, compared to related technologies, the signaling messages required for the terminal access procedure can be reduced from 18 to 14, thus reducing terminal access latency.

In one optional embodiment of this application, the first network function 110 is configured to receive a first request sent by a service caller, the first request being used to request the invocation of a service related to a first network capability; based on the first request, send a second request to the access network device, the second request being used to request the invocation of the first network capability; the first network capability is any network capability provided by the first network function and/or the terminal; the access network device 120 is configured to receive the second request and send a capability invocation result corresponding to the first network capability to the first network function 110; the first network function 110 is configured to receive the capability invocation result sent by the access network device 120, determine a service invocation result based on the capability invocation result, and send the service invocation result to the service caller.

In this embodiment, the first network capability can be any network capability implemented by the first functional entity in the access network device through various network resources, or any network capability provided by the terminal managed by the access network device, or any network capability jointly improved by the access network device and the terminal, such as network capabilities related to perception, network capabilities related to intelligence, network capabilities related to data services, network capabilities related to computing power, etc.

As an optional implementation, the access network device may be configured to send the capability call result to the first network function through the second module corresponding to the first network capability; and/or, may be configured to send the capability call result to the first network function through the terminal providing the first network capability.

In some embodiments, the first request may be used to request at least one of the following services: perception-related services, data-related services, computing/computing power-related services, and (artificial) intelligence-related services.

In some embodiments, the first request is used to request a first service, which is a sensing-related service. The process of the communication system processing the first request may include: a service caller sending the first request to a first network function, the first request including the service caller's identification information or identity information (e.g., the service caller's ID card number or mobile phone number), and first service requirement information; sending a second request to an access network device to request the invocation of a first network capability corresponding to the first service, i.e., a sensing-related network capability; after receiving the second request, the access network device may execute tasks related to the first network capability based on a corresponding second module, such as initiating a paging to a corresponding sensing terminal, notifying the corresponding sensing terminal to establish a connection for obtaining sensing data, and transmitting sensing data with the sensing terminal and the first network function based on the established connection, thereby enabling the first network function to provide the service caller with the sensing data corresponding to the first service.

As an optional implementation, the first network function may also send a query message to the core network based on the first request, for querying whether the network associated with the service caller supports the first service and querying the network identification information associated with the service caller. The query message may include the identification information or identity information of the service caller. If the query result determines that the service caller does not support the first service, a response message indicating that the first service is not supported may be returned to the service caller. If the query result determines that the service caller supports the first service, the first network function may determine whether the data stored in the first network function related to the network identification information can meet the first requirement information based on the queried network identification information. If it meets the requirement, the service call result of the first service is provided to the service caller. If it does not meet the requirement, the second request is sent to the access network device. The second request may include the network identification information.

In some embodiments, the first request is used to request a second service, which is a data-related service. The process of the communication system processing the first request may include: a service caller sending the first request to a first network function, the first request including second requirement information for the second service, such as the data type, data attributes, data volume, time information, and personal attribute information of the target data; sending a second request to one or more access network devices based on the first request, the second request including the second requirement information and the TNL address of the first network function; and after receiving the second request, the access network device triggering a second module related to the data service, executing a service related to the first network capability through the second module, such as performing a data query and determining whether local storage meets the second requirement information, and if so, sending a corresponding request to the first network function. The response message can carry the downlink data TNL address assigned by the access network device, and perform data transmission according to the TNL address of the first network function. If the conditions are not met, the access network device can send a data request message to the associated terminal to collect data. For example, it can establish a data transmission service bearer based on the network capabilities related to communication, and the data stream carried can be distributed and stored on demand in the first network function and the access network device. After the access network device completes the data in-path processing and/or data collection, it can transmit data to the first network function according to the TNL address of the first network function. After the first network function has collected all the data sent by the access network devices, it can send corresponding indication information to the service caller to indicate data transmission. Subsequently, service billing and corresponding data transmission services can be performed.

As an optional implementation, if the first network function determines that the local storage meets the second requirement information based on the first request, it can directly send the service response message of the second service to the service caller, and then perform service billing and corresponding data transmission services.

In some embodiments, the first request is used to request a third service, which is a service related to computing/computing power. The process of the communication system processing the first request may include: a service caller sending the first request to a first network function, the first request including third requirement information for the third service, such as the target computing power's computing power size, characteristics, type, and memory requirements; sending a second request to one or more access network devices to request the invocation of a first network capability corresponding to the third service, i.e., a computing power-related network capability, the second request including the TNL address of the first network function and identification information corresponding to the mobile terminal providing the target computing power; and the access network device, upon receiving the second request, executing a computing power service response based on the corresponding second module.

As an optional implementation, if the first network function determines, based on the first request, that the third requirement information cannot be met and/or the service caller has not subscribed to the third service, it returns a corresponding response message to the service caller, which may carry a specific reason for failure; if, based on the first request, it determines that the third requirement information can be met and the service caller has subscribed to the third service, the first network function may further satisfy the computing power type of the target computing power; if the target computing power is determined to be cloud (edge) computing power, it requests computing power allocation from the cloud computing power device, and then performs computing power billing and corresponding computing power service response processes; if the target computing power is determined to be mobile computing power, it sends the second request to one or more access network devices.

As an example, after receiving the second request, if the access network device determines that it has the target computing power, it directly sends the corresponding instruction information to the first network function and performs a computing power service response; or, if it determines that the target computing power is provided by the mobile terminal, the access network device can establish a communication connection with the mobile terminal and request computing power service, and complete the computing power service response based on the corresponding second module.

In some embodiments, the first request is used to request a fourth service, which is a smart-related service. The service caller may be a digital twin in the communication network, such as a function or module configured to provide smart management in a second network function, or the second network function itself. The process of the communication system processing the first request may include: the service caller sending the first request to a first network function, the first request including a task identifier for training the smart algorithm model, TNL address information, etc.; sending a second request to one or more access network devices, the second request including the task identifier, TNL address information, identifier information representing the existence of data, and selectable terminal information, etc.; after receiving the second request, the access network device executes a corresponding smart service response based on the corresponding second module. For example, the fourth service can be disassembled and analyzed through a second module related to intelligence. For instance, the four elements of the intelligent service (computing power, algorithm, data, and connection) can be analyzed. Based on the analysis results, one or more second modules related to computing power can be called as needed to perform computing power matching and mobile computing power selection. Furthermore, a connection with each mobile computing power entity can be established through a module related to communication to collect data related to the model training task and/or execute the corresponding model training task. Thus, the access network device can collect the intelligent service results of each mobile computing power entity and provide intelligent service responses to the first network function.

In one optional embodiment of this application, the first network function 110 is further configured to perform security authentication and/or identity authentication on the service caller. In this embodiment, before receiving the first request sent by the service caller, the first network function can perform security-related authentication, authorization, and/or identity recognition on the service caller, complying with relevant laws and policies regarding communication network external computing power services. It can be understood that in this embodiment, the security authentication and security capabilities exposed by the communication network reside within the first network function, enabling effective and appropriately complex security management.

In an optional embodiment of this application, the first network function 110 is further configured to obtain first policy information corresponding to the service caller, and provide corresponding network capabilities to the service caller based on the first policy information; the first policy information includes policies for security control of the corresponding network capabilities and/or policies for service billing of the corresponding network capabilities. In this embodiment, the first policy information can be obtained from the core network, or pre-stored through the first management function of the first network function (i.e., user-related management).

In one optional embodiment of this application, the network capability includes a second network capability related to perception; the access network device 120 is further configured to receive a third request sent by a terminal and send a fourth request to the first network function 110, wherein both the third request and the fourth request are used to request the establishment of a first bearer corresponding to the second network capability, and the first bearer is used by the terminal to transmit data related to the second network capability to the first network function 110; the access network device 120 is further configured to receive a second response message from the first network function 110 to the fourth request and establish the first bearer based on the second response message.

In this embodiment, service requests corresponding to the second network capability related to perception can be initiated not only by the service caller to the first network function, but also directly by the terminal to the access network device. For example, the service processing corresponding to the second network capability related to perception may include personal consumption services, environmental monitoring services, and perception-assisted networks, etc. Personal consumption services, such as the acquisition of personal health data, can be initiated by the terminal to the connected access network device, and intelligently processed and stored by the corresponding second module.

In some embodiments, the third request is sent periodically or in an event-triggered manner.

In some embodiments, the third request may include a sense service type. The access network device may send the fourth request to the first network function if it determines that the terminal has a sense service requirement based on the third request. For example, the fourth request may include a downlink user identifier (O1AP ID), a downlink bearer (TNL), and terminal identification information. The terminal identification information may be, for example, a unique identifier assigned to the terminal by the first network function or a network-wide unique identifier assigned to the terminal by the core network. Upon receiving a second response message from the first network function regarding the fourth request, the access network device may trigger the establishment of the first bearer. The second response message may include identification information assigned to the terminal by the access network device, an uplink O1AP ID assigned to the terminal by the first network function, an uplink bearer (TNL) address, and security and accounting policy information corresponding to the terminal.

In some embodiments, the access network device 120 is further configured to send an indication/notification message to the first network function 110 indicating that the first bearer has been successfully established when the first bearer establishment is completed.

In one optional embodiment of this application, the first network function 110 is further configured to obtain second policy information corresponding to the terminal from the core network. The second policy information includes a policy for security control of the second network capability and/or a policy for service billing of the second network capability.

In some embodiments, after receiving the fourth request, the first network function further determines whether context information of the terminal exists based on the first management function. If the context information does not exist, the first network function establishes the context information of the terminal and requests the second policy information from the core network, wherein the terminal AP ID allocated by the first network function may be carried, and the terminal AP ID is used by the core network to send a corresponding response message. If the context information exists but the second policy information does not exist, the first network function requests the second policy information from the core network, wherein the second policy information may be carried, wherein the first network function allocates a unique user identifier for the terminal. If both the context information and the second policy information exist, the first network function sends the second response message to the access network device, and the second response message may include the second policy information.

In some embodiments, the first network function may also store the second policy information based on the first management function.

This application also provides a communication method, which is applied to a first network function. Figure 4 is a schematic flowchart of the communication method according to an embodiment of this application. As shown in Figure 4, the method includes:

Step 201: Provide services based on the various network capabilities provided by one or more connected access network devices; wherein the network capabilities are implemented by the corresponding access network device through a first functional entity based on various network resources in the communication network, and provided through a second functional entity.

In one optional embodiment of this application, the method may further include performing at least one of the following: user-related management; service security-related management; perception-related network capability management; data service-related network capability management; artificial intelligence-related network capability management; network resource-related management; policy control-related management; and third-party service registration-related management. In this embodiment, the first network function can provide user management, security management, resource management, intelligent management, policy management, perception management, data management, and service registration functions, such as implementing external security control and authentication, meeting the global data collection and intelligent needs of the communication system, and working with the core network to complete the policy management of the communication system.

In one optional embodiment of this application, the method may further include: receiving a first request sent by a service caller, the first request being used to request the invocation of a service related to a first network capability; sending a second request to the access network device based on the first request, the second request being used to request the invocation of the first network capability; the first network capability being any network capability provided by the access network device and/or a terminal connected to the access network device; receiving a capability invocation result sent by the access network device; determining a service invocation result based on the capability invocation result; and sending the service invocation result to the service caller.

In one optional embodiment of this application, the method may further include: performing security authentication and/or identity authentication on the service caller.

In one optional embodiment of this application, the method may further include: obtaining first policy information corresponding to the service caller, and providing the service caller with corresponding network capabilities based on the first policy information; the first policy information includes a policy for security control of the corresponding network capabilities and/or a policy for service billing of the corresponding network capabilities.

In one optional embodiment of this application, the network capability includes a second network capability related to perception; the method may further include: receiving a fourth request sent by the access network device, the fourth request being used to request the establishment of a first bearer corresponding to the second network capability, the first bearer being used by the terminal to transmit data related to the second network capability to the first network function; and sending a second response message of the fourth request to the access network device, the second response message being used by the access network device to establish the first bearer.

In one optional embodiment of this application, the method may further include: obtaining second policy information corresponding to the terminal from the core network, wherein the second policy information includes a policy for security control of the second network capability and/or a policy for service billing of the second network capability.

This application also provides a communication method, which is applied to a first functional entity in an access network device. Figure 5 is a second flowchart illustrating the communication method according to an embodiment of this application. As shown in Figure 5, the method includes:

Step 301: Implement one or more network capabilities based on various network resources in the communication network; the one or more network capabilities are managed by a second functional entity in the access network device and provided by the second functional entity to a first network function that manages the access network device, and the one or more network capabilities are used by the first network function to provide services.

In some embodiments, the method may further include: performing secure mode and/or authentication encryption for air interface signaling. In this embodiment, the secure and authentication air interface process terminates at the first functional entity, shortening the signaling process path length and reducing latency.

In related technologies, the 5G communication system architecture defines a base station distributed unit (gNB-DU) and a centralized unit (gNB-CU). Figure 6 is a schematic diagram of the initial terminal access process in related technologies. As shown in Figure 6, the initial terminal access process requires a total of 18 signaling messages. Figure 7 is a schematic diagram of the initial terminal access process according to an embodiment of this application. As shown in Figure 7, the signaling messages can be shortened to 14.

Specifically, the first three messages in Figure 7 are the RRC Connection Establishment Request (RRCSetupRequest) message, the RRC Setup (RRCSetup) message, and the RRC Connection Establishment Complete (RRCSetupComplete) message, which can complete the establishment of the SRB1 signaling connection. Admission control is completed by the first functional entity. After the RRCSetupComplete message, the uplink RRC transmission (UL RRC MESSAGE TRANSFER) can carry information allocated by the first functional entity, such as RNTI information, S-TMSI, etc. (e.g., information used to select the core network and F1AP ID identifying the terminal), other resource information allocated by the first functional entity, and NAS information, and notify the second functional entity. Messages 5 to 7 are used to trigger the core network bearer establishment, consistent with the process in the related technologies in Figure 6. The terminal context establishment request (UE CONTEXT SETUP REQUEST) message sent by the second functional entity to the first functional entity can carry information from the second functional entity. The allocated F1AP ID information for signaling routing of the terminal, CU2DU container parameters (such as measurement configuration information), encryption-related information sent from the core network (parameters that can be used to generate access network encryption and integrity algorithm key related parameters), DRB-related parameters, etc.; subsequently, the first functional entity can perform encryption and integrity protection functions and generate a security mode control (securityModeCommand) message to verify encryption and integrity protection with the terminal; at the same time, the first functional entity also generates an RRC Reconnection message and performs integrity protection and encryption, which can be sent before the security mode complete (securityModeComplete) message is received; furthermore, the terminal context establishment response (UE CONTEXT SETUP RESPONSE) message sent by the first functional entity to the second functional entity can carry relevant information allocated by the first functional entity for air interface resources; messages 12 to 14 are consistent with the flow of related technologies in Figure 6.

As can be seen, in this embodiment, the first functional entity in the access network device can implement signaling processes related to security and authentication, and can also generate reconfiguration/reconnection messages. This enables security mode command messages and reconfiguration/reconnection messages to run in parallel over the air interface, reducing terminal access latency.

This application also provides a communication method, which is applied to a second functional entity in an access network device. Figure 8 is a flowchart of the communication method according to an embodiment of this application. As shown in Figure 8, the method includes:

Step 401: Manage one or more network capabilities and provide the one or more network capabilities to a first network function that manages the access network device; the one or more network capabilities are implemented by a first functional entity in the access network device based on various network resources in the communication network, and the one or more network capabilities are used by the first network function to provide services.

In one optional embodiment of this application, the management of one or more network capabilities includes at least one of the following: monitoring and controlling the one or more network capabilities; monitoring and controlling computing resources in the communication network, wherein the computing resources include computing resources provided by access network devices and/or computing resources provided by terminals; monitoring and controlling each interface corresponding to the access network; controlling the service scheduling corresponding to the one or more network capabilities; controlling the execution tasks corresponding to the one or more network capabilities; controlling the bearers corresponding to the one or more network capabilities; and controlling context information.

In one optional embodiment of this application, the method may further include: managing the one or more network capabilities provided by the terminal, and/or providing the terminal with services related to the one or more network capabilities.

In one optional embodiment of this application, the method may further include: receiving a first message sent by each of the second modules through a first module, registering the network capabilities corresponding to each of the second modules based on the first message; sending a first response message of the first message to each of the second modules through the first module; wherein each of the second modules is configured to provide the corresponding network capabilities.

In one optional embodiment of this application, the first message includes at least one of the identification information, parameter information, and link information of the corresponding second module.

In one optional embodiment of this application, the method may further include: sending a second message to a second network function through the first module, the second message being used to notify the second network function that the access network device has added a corresponding second module; the second network function is at least configured to manage the access network device.

This application also provides a communication method applied to an access network device. Figure 9 is a schematic flowchart of the communication method according to an embodiment of this application. As shown in Figure 9, the method includes:

Step 501: Implement one or more network capabilities based on various network resources in the communication network through a first functional entity, and manage the one or more network capabilities through a second functional entity and provide the one or more network capabilities to a first network function that manages the access network device; the one or more network capabilities are used by the first network function to provide services.

In one optional embodiment of this application, the method may further include: managing the one or more network capabilities provided by the terminal through the second functional entity, and/or providing services related to the one or more network capabilities to the terminal through the second functional entity.

In an optional embodiment of this application, the method may further include: receiving a second request sent by the first network function, the second request being used to request the invocation of a first network capability, the first network capability being any network capability provided by the access network device and/or the terminal; sending a capability invocation result corresponding to the first network capability to the first network function; the capability invocation result being used by the first network function to send a corresponding service invocation result to a service caller.

In one optional embodiment of this application, the network capability includes a second network capability related to perception; the method may further include: receiving a third request sent by a terminal, sending a fourth request to the first network function, wherein both the third request and the fourth request are used to request the establishment of a first bearer corresponding to the second network capability, and the first bearer is used by the terminal to transmit data related to the second network capability to the first network function; receiving a second response message from the first network function to the fourth request, and establishing the first bearer based on the second response message.

The communication scheme of this application embodiment will be described in detail below with reference to specific application scenarios.

Figure 10 is a schematic diagram of a communication network architecture according to an embodiment of this application. As shown in Figure 10, the communication system in this example includes a first network function 610, an access network device 620, and a second network function 630. The first network function (hereinafter referred to as the RAN centralized open management domain, RAN-S domain, or RAN-S) 610 can be connected to the core network and simultaneously connected to one or more access network devices (hereinafter referred to as RAN distributed units or xNBs) 620. Each access network device 620 includes a first functional entity (hereinafter referred to as a function/resource domain, or RAN-U, RAN-DU) 621 and a second functional entity (hereinafter referred to as a control domain, or RAN-C, RAN-CU) 622. The second functional entity 622 is connected to the AMF in the core network. The second network function (hereinafter referred to as the intelligent management domain or RAN-O&M) 630 is connected to the first functional entity 621 and the second functional entity 622 in the first network function 610 and the access network device 620, and is configured to manage the first network function 610, the first functional entity 621, and the second functional entity 622.

In this example, the main functions of RAN-O&M include digital twin and management orchestration functions to manage the entire RAN system. The management orchestration function enables human-machine management of the RAN system, allowing interaction and management of functions such as resource configuration, operation configuration, faults, alarms, performance, topology, version, monitoring, and services. The digital twin function enables intelligent management of the RAN system, including digital environment modeling, data simulation, functional verification, and network intelligent autonomy, to achieve intelligent management of the RAN system in its operational state.

In some examples, RAN-O&M can support visual programming techniques to modify and optimize process management based on service type or service QoS, providing basic service processes for network intelligent services.

The main functions of RAN-S are to provide service-oriented interfaces for external capability exposure and centralized management of global multi-dimensional capabilities. The service-oriented interfaces enable external capability exposure and security authentication, and implement the division of the RAN functional security interface. The centralized management of multi-dimensional capabilities acts as the "brain" of the RAN network, primarily managing computing power, intelligence, data, and security capabilities, enabling on-demand allocation and hierarchical (e.g., centralized-distributed) management of capabilities. In this example, Figure 11 is a schematic diagram of the connection relationships between network elements in the communication system of this application embodiment. As shown in Figure 11, one RAN-O&M can manage one or more RAN-S domains; and at any given time, only one RAN-O&M is connected to a RAN-S domain.

xNBs can include RAN-C and RAN-U. An xNB can manage and service traditional wireless communication RAN capabilities, as well as the computing power, intelligence, and data capabilities of distributed units. Specifically, one RAN-S domain can manage one or more xNBs, and an xNB can be connected to only one RAN-S domain at any given time; one RAN-O&M domain can manage one or more xNBs, and an xNB can be connected to only one RAN-O&M domain at any given time.

In some examples, referring to Figure 11, the interface between the RAN-S domain and the xNB can be an O1 interface, which may include a control plane (O1-C) and a data plane (O1-U). The O1 control plane can use either the SCTP or UDP interface protocol, and the O1 data plane can use the UDP interface protocol. The F1-C interface protocol can be used between RAN-C and RAN-U. The external interface of RAN-S can be implemented using service-oriented technology, consistent with the core network service-oriented protocol standard. The interface between xNB and the core network can use an Ng interface (i.e., the interface between the radio access network and the core network), where xNB-DU uses the Ng-U interface and xNB-CU uses the Ng-C interface. Exemplarily, the end-to-end bearer establishment interface of the RAN remains unchanged, the control interface with the core network uses the SCTP protocol, the service interface uses the GTPU protocol, and the external capability exposure interface uses the QUIC protocol.

Figure 12 is a schematic diagram of the data flow in the communication system of this application embodiment. As shown in Figure 12, in this example, the access network device 620 can realize the service scheduling of communication, sensing, computing power, intelligence and security. The communication service of the access network device 620 is the same as that of related technologies, ensuring high data rate and low latency data flow. In addition, it also outputs data flow corresponding to various network capabilities such as sensing, computing power, intelligence and security, and provides services to the outside world through the first network function 610.

Figure 13 is a functional distribution block diagram of a communication system according to an embodiment of this application. As shown in Figure 13, the functions of the RAN-S may include user management (i.e., the first management function), security management (i.e., the second management function), resource management (i.e., the sixth management function), intelligent management (i.e., the fifth management function), policy management (i.e., the seventh management function), perception management (i.e., the third management function), data management (i.e., the fourth management function), and service registration function (i.e., the eighth management function). The RAN-S domain is the enabling interface and capability opening interface between the RAN system and third-party systems or functions. It can realize external security control and authentication, meet the global data collection and intelligent requirements, and complete the policy management of the RAN system together with the core network system.

The main functions of the xNB consist of two parts: the control domain and the function/resource domain. The control domain (RAN-C) is the cerebellum of the RAN system, including the interface layer, service management layer, task management layers, and process control functions. The function/resource domain (RAN-U) embodies the capabilities of the RAN system, including user plane data processing, state management, sensing plane management, data plane management, mobile computing power scheduling, and resource selection. Referring to Figure 3, each service sub-layer within the xNB is represented as a service, enabling task management for each sub-service layer and allowing for the combination and invocation of capabilities between sub-tasks. In this example, the xNB can achieve isolation between control and services, while the function domain provides functional services and resource management capabilities for communication, sensing, computing power, and intelligence.

Figure 14 is a functional distribution block diagram of an xNB according to an embodiment of this application. As shown in Figure 14, the platform layer corresponding to the service network in this example can realize the management, scheduling and control functions of the RAN. Dividing the platform layer from the perspective of protocol architecture is part of the general mechanism of control plane functions. The specific capabilities in this example may include network service supervision (i.e., the first control function), computing resource supervision (i.e., the second control function), interface supervision (i.e., the third control function), service management layer (not shown in Figure 14, i.e., the fourth control function), process management (i.e., the sixth control function), data management (i.e., the seventh control function), and task management function (i.e., the fifth control function).

Among them, the Network Service Monitoring module is responsible for the functional registration of services across all aspects. It is the execution and management unit for on-demand combination of RAN functions, customized services, system compatibility, capability openness, and interface openness. After each task management module (i.e., the second module) runs, it sends messages to the Network Service Monitoring module to establish routing relationships between each module and the Service Scheduling module (i.e., the first module). It should be noted that the communication task management function is a basic function of xNB and does not require registration and discovery. The registration process for other functions is shown in Figure 2. The registration of each task module has no specific order.

Taking the registration process of the sensing module (i.e., the second module corresponding to the network capabilities related to sensing) as an example, referring to Figure 2, the sensing module dynamically joins the xNB. After the sensing module completes the initialization function, it sends a sensing module initialization instruction (sensor indi req) message (i.e., the first message) to the module monitoring function of the service management module (i.e., the first module), indicating that the sensing module has been successfully initialized and needs to join the xNB system. The sensor indi req message may include the identification information of the sensing module, the parameter requirements for the call, and the link establishment or function scheduling information (such as TNL or callback function, etc.). The destination address of the sensor indi req message can be obtained through pre-configuration or through communication with the RAN-O&M module. Upon receiving the message, the module monitoring function of the service management module registers and saves the information within the service management module. It then sends a sensor module initialization indication response (sensor init indi res) message (the first response message) to the sensing module, indicating that registration is complete and the sensing module is ready to enter service mode. The sensor init indi res message may include the service management module's identification information, capability parameters, and link establishment or function scheduling information (such as TNL or callback functions). Simultaneously, the service management module's module monitoring function sends a sensor module initialization (sensor module initial) message (the second message) to the RAN-O&M, notifying the xNB entity that a new sensing module has been added and is ready to operate normally. The processing flow for other network capability-related task modules is similar to that of the sensing module, and will not be elaborated upon here for brevity.

In this example, service-oriented functions and mobile computing resources can be discovered through registration, supporting xNB to generate customized base station functions on demand, supporting plug-and-play of new features, and supporting plug-and-play of mobile computing resources.

Referring again to Figure 14, computing resource management refers to the management of the computing network, which may include the management of computing nodes, computing routes, link QoS, computing attributes, computing power, and on-demand allocation of computing resources. In this example, computing network resources may include terminals, base stations, and core network equipment, and are characterized by near-end dedicatedness; they mainly meet the computing resource usage within the mobile communication network, providing low-latency, mobile, and highly reliable computing services, forming a mobile computing network, and together with traditional network computing power, providing end-to-end computing network services.

Interface supervision is responsible for the connection management and interface function implementation between RAN and RAN, RAN and CN, RAN and UU, RAN and intelligent orchestration body, RAN and RAN centralized open management body, and RAN and third-party services. Specific functions may include communication link maintenance, message encoding and decoding, visual programming message translation, message scheduling, and the network platform layer's ability to open up to third-party applications (computing power, intelligence, data, collaborative control, etc.) and the identification, translation and conversion of application layer protocols, so as to realize message interaction between RAN and application layer.

The business management layer primarily identifies and schedules business services. Based on the type of business, the management layer can break down, coordinate, and invoke various business sub-layers to meet the business's needs for communication, sensing, data, computing, and intelligence. Each business sub-layer can guarantee resource allocation, QoS assessment, and service function combination within the subsystem.

Task management includes functions such as task execution, task lifecycle management, service quality assurance, and link decision-making for each business sub-layer.

Process management is responsible for on-demand service function invocation, connection establishment, modification, maintenance, and exception rollback for wireless, compute, data, and sensing bearers. In this example, the xNB's management domain can generate services dynamically through the process control (automatic orchestration) module based on the QoS characteristics of the service subsystems.

Data management includes the maintenance and modification of static and semi-static parameters, including system context information, cell context information, user context information, and connection context information, as well as the provision of data services to external modules.

In this example, the xNB's management domain can define business requirements, schedule resources and capabilities between task management modules, and each task management module can provide independent services and support service fusion between task management modules.

In some examples, the xNB's management domain can deploy a single communication task system or multiple task subsystems as needed. The following sections, based on Figures 15 to 20, describe the relevant task flows of each task subsystem in the communication system of this example.

In this example, the perception-oriented subsystem can handle perception services, such as personal consumption services, environmental monitoring services, and perception-assisted network services. The external service provision of perception tasks and the acquisition of perception data can be divided into two relatively independent processes. Personal health and other consumption services can be initiated by the terminal and intelligently processed and stored in the perception module. Based on a personalized strategy, perception data services are provided externally when a perception service request is received. Figure 15 is a schematic diagram of a service flow for network capabilities related to perception in the communication system of this application embodiment. As shown in Figure 15, the flow includes:

Initial registration process. In this example, the user first completes the initial access process, and the user's corresponding perception data can be used to send connection establishment requests using a periodic or event-triggered strategy.

Users can send a UE application message request to the xNB, which can carry the type of sensing service.

The xNB sends a sensor message request to the RAN-S. In this example, the xNB can determine the service type and, if it determines that there is a need for sensor services, it sends a sensor message request to the RAN-S, carrying the downlink user identifier O1AP-ID, the downlink bearer TNL address, and the RAN-S entity user unique identifier (or the network-wide unique identifier assigned by the core network).

Figure 16 is a schematic diagram of the process for obtaining perception-related policies according to an embodiment of this application. As shown in Figure 16, after receiving the perception bearer establishment request message, the RAN-S can check whether the user context exists in the user management module based on the unique identifier of the RAN-S entity user. If it does not exist, the user context is established, and a policy request message is sent to the core network, carrying the UE APID allocated by the RAN-S, requesting the corresponding policy and security control information. If the context exists, it further determines whether there is a perception-related policy (i.e., second policy information), such as the security and charging policies for perception data. If there is no perception-related policy, a policy request message can also be sent to the core network, which can carry the unique identifier of the RAN-S entity user. If the RAN-S has a perception-related policy, a perception response message is sent to the xNB.

Referring to Figure 15, after receiving the policy request message, the core network can look up the user's security and charging policies based on the unique identifier of the RAN-S entity user and send a policy response message to the RAN-S entity, carrying the user identifier assigned to the user by the core network. After receiving the corresponding policy and security information, the RAN-S entity can store the relevant information in the user management module of the RAN-S entity and send a sensor message response message to the xNB. This message can carry the user identifier assigned by the xNB, the uplink O1AP-ID message assigned by the RAN-S entity, the uplink bearer TNL address, and the user's security and charging policies, etc.

After receiving the sensor message response from RAN-S, xNB triggers the establishment of the air interface data bearer. Once the air interface bearer is established, it sends a sensor DRB success message to RAN-S, indicating that the connection has been successfully established. Subsequently, sensor data transmission and service billing are performed.

In this example, the terminal-oriented capability exposure can be deployed in the xNB's management domain to identify application services and configuration requests such as sensing, computing power, and measurement data initiated by the terminal.

Figure 17 is a schematic diagram of another service process of the communication system according to an embodiment of this application for network capabilities related to perception. As shown in Figure 17, the process includes:

Users of the perception service use the RAN-S to complete security and identity authentication through the externally open interface, which complies with the relevant laws and policies of the RAN for external data services.

Sensing service users send sensing service requests to RAN-S, which may include unique identification information such as ID card numbers or mobile phone numbers.

The RAN-S queries the core network for device capabilities and network unique identifiers for the user's network, which may include the unique identity information and location information sent by the sensing service user. The core network returns the query results, which may include sensing service capabilities and the user's network unique identifier. If the sensing service user does not support the sensing service, a sensing data response message is returned indicating that the user does not have this service, and the process ends. Based on the queried network unique identifier, the RAN-S checks whether its stored sensing data can meet the data requirements of the sensing service user. If it can, it sends a sensing data response and transmits sensing data, and the process ends. If the RAN-S determines that it cannot meet the data requirements of the sensing service user, it sends a sensing device data request to the xNB to request sensing data, carrying the network unique identifier.

The xNB initiates a paging process to the sensing device through service management. This paging indicates the type of sensing data service and notifies the user to establish a connection for acquiring sensing data. After the sensing device and xNB complete the connection establishment, the sensing device and RAN-S begin transmitting sensing data.

RAN-S stores sensing data, sends sensing data responses to sensing service users, and transmits sensing data.

Figure 18 is a schematic diagram of a service process of a communication system according to an embodiment of this application for network capabilities related to data services. As shown in Figure 18, the process includes:

RAN-S ensures secure access for data service users by performing authorization and authentication processes, complying with relevant laws and policies governing RAN's external data services.

After completing security-related authentication and identity verification, the data service user sends a data service request message to the RAN-S. This message may carry specific information about the data service request, such as data category, data attributes, data volume, time information, or personal attribute information.

The RAN-S request data management function determines whether the current data information can meet the data service user's data needs. If it can, it sends a data service response message to indicate that the data service response was successful, and then performs service billing and data transmission services. If the request is a query, it retrieves the data according to the data service user's request information and can send a data service response message to the open object with the expected waiting time parameter. If the request cannot be met, the data service response message can carry the specific reason for the failure.

If the RAN-S determines that the local data does not meet the service request requirements, it can initiate a base station assistance (data acquisition) process. In this process, the RAN-S can determine whether it is a single-site data collection or multi-site data acquisition process based on the data requirements. The multi-site process is a repetition of the single-site process; this example only describes the single-site acquisition process.

When the xNB receives a base station data request from the RAN-S, it may carry information related to the data request from the data service user request message, as well as the RAN-S's TNL information. The service scheduling module in the xNB can trigger the data management subsystem, which can perform data queries and determine whether local storage meets the data requirements. If it does, it sends a base station data response message to the RAN-S, which may carry the downlink data TNL information allocated by the xNB, and performs local data transmission according to the RAN-S's TNL information. If the local storage data cannot meet the data requirements sent by the RAN-S, data collection from end users is required. The data management subsystem can call the communication management subsystem to establish a service bearer for data acquisition. The data stream on the bearer can be distributed and stored on demand in the data management entities of the xNB and RAN-S. The xNB completes in-band data processing and/or completes data collection from the terminals, and transmits data to the RAN-S according to the RAN-S's TNL information.

After collecting all data from the xNBs, the RAN-S sends a data service indication message to the data service user. The RAN-S then performs data transmission services with the data service user and handles billing based on the data service usage.

Figure 19 is a schematic diagram of a service process of the communication system according to an embodiment of this application for network capabilities related to computing power. As shown in Figure 19, the process includes:

RAN-S ensures secure access for computing power service users by performing security processes such as authorization and authentication, in compliance with relevant laws and policies governing RAN's external computing power services.

After completing security-related authentication and identity verification, the computing power service user sends a computing power service request to RAN-S, which may include information such as the required computing power size, computing power characteristics, computing power type, and memory-related requirements. In some examples, RAN-S can determine whether it can meet the requester's computing power requirements and whether to subscribe to a computing power service. If it cannot meet the requirements, it will respond with a message containing details of the failure; otherwise, it will include a success indication.

Referring again to Figure 19, the RAN-S can determine whether the computing power type is cloud (edge) computing power or mobile computing power. If cloud (edge) computing power needs to be allocated, the cloud computing power allocation process will be followed. After allocation, computing power billing will be performed, along with algorithm, data loading, and computing power calculation. If mobile computing power network is required for computing power allocation, the RAN-S can select one or more xNBs to provide computing power services based on the resource management module's policy and the statistical base station computing power capability information.

The xNB's service management module receives a computing resource request from the RAN-S, which may carry the RAN-S's TNL information or the unique identifier of the terminal network providing computing power. The xNB's computing power management module (the second module corresponding to the network capabilities related to computing power) can determine whether to use base station computing power or terminal computing power to provide services based on the policy. If it is determined that the base station needs to provide computing power services, it allocates computing power resources and sends a computing resource response message to the RAN-S, which may carry the base station's TNL information. If the computing power management module determines that the terminal needs to provide computing power services and the terminal is in a disconnected state, the computing power management module can send a connection establishment request or paging request to the communication management module, carrying the connection establishment attribute parameters and the information content initiated by the computing power management module, triggering the communication management module to establish a connection.

After the computing power management module in the xNB completes the application and confirmation of terminal computing power resources, it can send a computing power resource service response message to the RAN-S entity, carrying information about the computing power providing entity and TNL information of the base station computing power service for algorithm and/or data transmission.

RAN-S collects feedback from the computing power providing entity to meet the computing power needs of the computing power service user. RAN-S then sends a computing power service response message to the user. Upon receiving the response message, the user begins loading the computing power application and the computing power billing process, thus completing the computing power service.

In this example, the communication system can provide base station and terminal computing power and network data for network optimization and network autonomy-related services. It can also utilize the distributed computing power characteristics of mobile networks to perform federated training of intelligent algorithm models and provide network capability services related to intelligence.

Figure 20 is a schematic diagram of a service process of a communication system according to an embodiment of this application for intelligent network capabilities. As shown in Figure 20, the process includes:

Intelligent service users (such as digital twins) can send intelligent service requests to the RAN-S, which may include task identifiers, TNL address information, etc., to request network optimization or intelligent service functions. The RAN-S entity can determine the intelligent service requirements and their matching capabilities with the four elements of intelligence (computing power, algorithm, data, and connectivity), select a computing power model, and return an intelligent service response to the intelligent service user, which may include task identifiers, TNL address information, etc. If the response is successful, the intelligent service user can use the established data channel to send relevant algorithm and data information to the RAN-S.

The data management function in RAN-S can query data that meets the requirements of intelligent services. If it meets the requirements of cloud computing power/edge computing power, it will execute the model training process for cloud computing power/edge computing power. If mobile network computing power services are needed, RAN-S sends an intelligent service request to one or more xNBs, which may carry task identifier, TNL information, data presence identifier, and selectable terminal information, etc.

After receiving a smart service request, the xNB routes the message to the smart management module for analysis and scheduling. The smart management module breaks down the four elements of the smart service requirements (computing power, algorithm, data, and connectivity) and sends a smart service response message to the RAN-S, which may carry the TNL information assigned by the xNB, task identification information, etc. Simultaneously, it calls the computing power management module as needed to perform computing power matching (capability, computing power QoS, terminal information, etc.) and mobile computing power selection. The computing power management module returns the selected mobile computing power result to the smart management module. The smart management module then calls the communication management module (which may carry connection QoS, terminal information, etc.) to establish terminal connection requirements. The communication management module returns the connection task establishment result to the smart management module. Finally, the smart module calls the data management module as needed to collect data.

Upon receiving the successful response message from the xNB, the RAN-S entity sends algorithm and data information to the xNB entity using the established data transmission channel. The task management module of the intelligent service sublayer in the xNB collects the four essential elements for intelligent service preparation and triggers intelligent service, providing the intelligent service through the selected mobile computing network. After each mobile computing entity completes its intelligent service, it responds to the task management module of the intelligent service sublayer with the intelligent service result. This module, upon receiving the completion of all sub-task services, processes the information and triggers the xNB to respond to the RAN-S with the intelligent service.

After collecting all intelligent service responses from xNBs, RAN-S processes and analyzes the collected results. Once the service requirements are met, it provides intelligent service responses to intelligent service users. Intelligent service users then perform subsequent model validation and optimization based on the model results from the intelligent service.

In this example, the RAN's network open capabilities reside in the RAN-S domain, managed separately from traditional data transmission services. This allows for the provision of open capabilities while ensuring the system performance of traditional data services. The RAN's external security authentication and security capabilities reside in the RAN-S centralized open management domain, achieving effective and appropriately complex security. The RAN-S also has policy control functions, which can interact with core network billing and other modules through service interfaces to achieve identity security and billing functions for the RAN's network capability open functions. The RAN-S also has user management functions, enabling the maintenance of user-specific perception data, providing information services, storing user computing power characteristics and capabilities, providing external computing power services, and storing user intelligent optimization and network optimization related feature information for intelligent policies for user services.

Referring to Figures 18 to 20, in this example, the RAN's data and computing power are deployed in a centralized + distributed manner. The RAN-S can provide centralized network data, computing power and its resource scheduling, while the xNB is responsible for providing the RAN-S with relevant data and computing power, and providing the RAN-S with xNB services and capabilities.

This application also provides a communication device applicable to a first network function. Figure 21 is a schematic diagram of the composition structure of the communication device according to an embodiment of this application. As shown in Figure 21, the communication device 700 includes a first processing unit 701, configured to provide services based on various network capabilities provided by one or more connected access network devices; wherein, the network capabilities are implemented by the corresponding access network device through a first functional entity based on various network resources in the communication network, and provided through a second functional entity.

In one optional embodiment of this application, the first processing unit 701 is further configured to perform at least one of the following: user-related management; service security-related management; perception-related network capability management; data service-related network capability management; artificial intelligence-related network capability management; network resource-related management; policy control-related management; and third-party service registration-related management.

In an optional embodiment of this application, the apparatus 700 further includes a first communication unit configured to receive a first request sent by a service caller, the first request being used to request the invocation of a service related to a first network capability; send a second request to the access network device based on the first request, the second request being used to request the invocation of the first network capability; the first network capability being any network capability provided by the access network device and/or a terminal connected to the access network device; receive a capability invocation result sent by the access network device; determine a service invocation result based on the capability invocation result; and send the service invocation result to the service caller.

In one optional embodiment of this application, the first processing unit 701 is further configured to perform security authentication and/or identity authentication on the service caller.

In an optional embodiment of this application, the first processing unit 701 is further configured to obtain first policy information corresponding to the service caller, and provide the corresponding network capabilities to the service caller based on the first policy information; the first policy information includes a policy for security control of the corresponding network capabilities and/or a policy for service billing of the corresponding network capabilities.

In one optional embodiment of this application, the network capability includes a second network capability related to perception; the device further includes a first communication unit configured to receive a fourth request sent by the access network device, the fourth request being used to request the establishment of a first bearer corresponding to the second network capability, the first bearer being used by the terminal to transmit data related to the second network capability to the first network function; and to send a second response message of the fourth request to the access network device, the second response message being used by the access network device to establish the first bearer.

In one optional embodiment of this application, the first processing unit 701 is further configured to obtain second policy information corresponding to the terminal from the core network. The second policy information includes a policy for security control of the second network capability and/or a policy for service billing of the second network capability.

In this embodiment of the application, the first processing unit 701 in the communication device 700 can be implemented by a central processing unit (CPU), digital signal processor (DSP), microcontroller unit (MCU), or field-programmable gate array (FPGA) in the first network function in practical applications; the first communication unit in the communication device 700 can be implemented by a communication module (including: basic communication kit, operating system, communication module, standardized interface and protocol, etc.) and transceiver antenna in practical applications.

This application also provides a communication device that can be applied to a first functional entity in an access network device. Figure 22 is a schematic diagram of the composition structure of the communication device according to an embodiment of this application. As shown in Figure 22, the communication device 800 includes a second processing unit 801, configured to implement one or more network capabilities based on various network resources in the communication network; the one or more network capabilities are managed by the second functional entity in the access network device and provided by the second functional entity to the first network capability managing the access network device, and the one or more network capabilities are used by the first network capability to provide services.

In one optional embodiment of this application, the second processing unit 801 is further configured to perform secure mode and/or authentication encryption for air interface signaling.

In this embodiment of the application, the second processing unit 801 in the communication device 800 can be implemented by the CPU, DSP, MCU or FPGA in the first functional entity in practical applications.

This application also provides a communication device that can be applied to a second functional entity in an access network device. Figure 23 is a schematic diagram of the composition structure of the communication device according to an embodiment of this application. As shown in Figure 23, the communication device 900 includes a third processing unit 901, configured to manage one or more network capabilities and provide the one or more network capabilities to a first network function that manages the access network device; the one or more network capabilities are implemented by the first functional entity in the access network device based on various network resources in the communication network, and the one or more network capabilities are used for the first network function to provide services.

In one optional embodiment of this application, the third processing unit 901 includes at least one of the following: a first subunit configured to monitor and control the one or more network capabilities; a second subunit configured to monitor and control computing resources in the communication network, wherein the computing resources include computing resources provided by access network equipment and/or computing resources provided by terminals; a third subunit configured to monitor and control each interface corresponding to the access network; a fourth subunit configured to control the service scheduling corresponding to the one or more network capabilities; a fifth subunit configured to control the execution tasks corresponding to the one or more network capabilities; a sixth subunit configured to control the bearers corresponding to the one or more network capabilities; and a seventh subunit configured to control context information.

In one optional embodiment of this application, the third processing unit 901 is further configured to manage the one or more network capabilities provided by the terminal, and/or to provide services related to the one or more network capabilities to the terminal.

In one optional embodiment of this application, the third processing unit 901 is further configured to receive a first message sent by each of the second modules through the first module, register the network capabilities corresponding to each of the second modules based on the first message, and send a first response message of the first message to each of the second modules through the first module; wherein each of the second modules is configured to provide corresponding network capabilities.

In one optional embodiment of this application, the first message includes at least one of the identification information, parameter information, and link information of the corresponding second module.

In one optional embodiment of this application, the third processing unit 901 is further configured to send a second message to the second network function through the first module, the second message being used to notify the second network function that the access network device has added a corresponding second module; the second network function is at least configured to manage the access network device.

In this embodiment of the application, the third processing unit 901 and its subunits in the communication device 900 can be implemented by the CPU, DSP, MCU or FPGA in the second functional entity in actual applications.

It should be noted that the communication device provided in the above embodiments is only illustrated by the division of the above program modules. In actual applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the device can be divided into different program modules to complete all or part of the processing described above. In addition, the communication device and communication method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here.

This application also provides an access network device. Figure 24 is a schematic diagram of the composition structure of the access network device according to an embodiment of this application. As shown in Figure 24, the access network device 1000 includes a first functional entity 1001 and a second functional entity 1002; wherein...

The first functional entity 1001 is configured to implement one or more network capabilities based on various network resources in the communication network;

The second functional entity 1002 is configured to manage the one or more network capabilities and provide the one or more network capabilities to the first network function; the one or more network capabilities are used to manage the service exposure of the first network function of the access network device.

In one optional embodiment of this application, the second functional entity 1002 is configured to provide at least one of the following functions: a first control function representing regulatory control related to network capabilities; a second control function representing regulatory control related to computing resources in the communication network, wherein the computing resources include computing resources provided by access network equipment and/or computing resources provided by terminals; a third control function representing regulatory control related to each interface corresponding to the access network; a fourth control function representing control related to service scheduling corresponding to network capabilities; a fifth control function representing control related to task execution corresponding to network capabilities; a sixth control function representing control related to bearer operations corresponding to network capabilities; and a seventh control function representing control related to context information.

In one optional embodiment of this application, the second functional entity 1002 is further configured to manage the one or more network capabilities provided by the terminal and/or provide services related to the one or more network capabilities to the terminal.

In one optional embodiment of this application, the first functional entity 1001 is further configured to perform secure mode and/or authentication encryption for air interface signaling.

In one optional embodiment of this application, the first functional entity 1001 and the second functional entity 1002 interact with each other through a second interface.

This application also provides a network function. Figure 25 is a schematic diagram of the network function of this application embodiment. Exemplarily, the communication device 1100 may be the first network function, the first functional entity, or the second functional entity in the foregoing embodiments. The communication device 1100 shown in Figure 25 includes: at least one processor 1101, a memory 1102, and at least one network interface 1103. The various components in the communication device 1100 are coupled together through a bus system 1104. It is understood that the bus system 1104 is configured to realize the connection and communication between these components. In addition to a data bus, the bus system 1104 also includes a power bus, a control bus, and a status signal bus. However, for clarity, all buses are labeled as bus system 1104 in Figure 25.

It is understood that memory 1102 can be volatile memory or non-volatile memory, or both. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM); magnetic surface memory can be disk storage or magnetic tape storage. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), SyncLink Dynamic Random Access Memory (SLDRAM), and Direct Rambus Random Access Memory (DRRAM). The memory 1102 described in the embodiments of this application is intended to include, but is not limited to, these and any other suitable types of memory.

The memory 1102 in this embodiment is configured to store various types of data to support the operation of the communication device 1100. Examples of such data include any computer program used to operate on the communication device 1100, such as the program for the cell selection method in this embodiment.

The methods disclosed in the embodiments of this application can be applied to processor 1101, or implemented by processor 1101. Processor 1101 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware in processor 1101 or by instructions in the form of software. The processor 1101 may be a general-purpose processor, DSP, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Processor 1101 can implement or execute the 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, etc. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware decoding processor, or being executed by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, which is located in memory 1102. Processor 1101 reads the information in memory 1102 and completes the steps of the aforementioned method in combination with its hardware.

In an exemplary embodiment, the communication device 1100 may be implemented by one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), FPGAs, general-purpose processors, controllers, MCUs, microprocessors, or other electronic components to perform the aforementioned method.

In an exemplary embodiment, this application also provides a computer-readable storage medium, such as a memory 1102 including a computer program, which can be executed by the processor 1101 of the communication device 1100 to complete the steps described in the aforementioned method. The computer-readable storage medium may be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disc, or CD-ROM; it may also be various devices including one or any combination of the above-mentioned memories, such as mobile phones, computers, tablet devices, personal digital assistants, etc.

In an exemplary embodiment, this application also provides a computer program product, including a computer program that can be executed by the processor 1101 of the communication device 1100 to perform the steps described in any of the foregoing methods.

The methods disclosed in the several method embodiments provided in this application can be arbitrarily combined without conflict to obtain new method embodiments.

The features disclosed in the several product embodiments provided in this application can be arbitrarily combined without conflict to obtain new product embodiments.

The features disclosed in the several method or device embodiments provided in this application can be arbitrarily combined without conflict to obtain new method or device embodiments.

In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods, such as: multiple units or components can be combined, or integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the various components shown or discussed can be through some interfaces, and the indirect coupling or communication connection between devices or units can be electrical, mechanical, or other forms.

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

In addition, each functional unit in the various embodiments of this application can be integrated into one processing unit, or each unit can be a separate unit, or two or more units can be integrated into one unit; the integrated unit can be implemented in hardware or in the form of hardware plus software functional units.

Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

Alternatively, if the integrated units described above are implemented as software functional modules and sold or used as independent products, they can also be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, or the parts that contribute to related technologies, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, ROM, RAM, magnetic disks, or optical disks.

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 (28)

A communication system, the system comprising a first network function and an access network device, wherein, The access network device includes a first functional entity and a second functional entity; the first functional entity is configured to implement one or more network capabilities based on various network resources in the communication network, and the second functional entity is configured to manage the one or more network capabilities and provide the one or more network capabilities to the first network function. The first network function is configured to provide services based on various network capabilities provided by one or more access network devices connected to the network. The system according to claim 1, wherein the first network function is configured to provide at least one of the following functions: The first management function represents user-related management; The second management function represents the management related to service security; The third management function is the management of network capabilities related to characterization and perception. The fourth management function represents the management of network capabilities related to data services; The fifth management function represents the management of network capabilities related to artificial intelligence; The sixth management function represents the management related to network resources; The seventh management function represents the management related to policy control corresponding to each network capability; The eighth management function represents the management related to the registration of third-party services. The system according to claim 1, wherein the second functional entity is configured to provide at least one of the following functions: The first control function represents the regulatory controls related to network capabilities; The second control function characterizes the regulatory control related to computing resources in the communication network; wherein, the computing resources include computing resources provided through access network equipment and/or computing resources provided by terminals; The third control function represents the regulatory control related to each interface corresponding to the access network; The fourth control function represents the control related to service scheduling corresponding to network capabilities; The fifth control function represents the control related to the execution tasks corresponding to network capabilities; The sixth control function represents the bearer-related control corresponding to network capabilities; The seventh control function represents control that is related to context information. The system according to any one of claims 1 to 3, wherein the second functional entity is further configured to manage the one or more network capabilities provided by the terminal and/or to provide services related to the one or more network capabilities to the terminal. The system according to claim 1, wherein the second functional entity includes at least a first module configured to provide a first control function, the first control function representing regulatory control related to network capabilities; The first module is configured to receive a first message sent by each of the second modules, register the network capabilities corresponding to each of the second modules based on the first message, and send a first response message of the first message to each of the second modules; wherein each of the second modules is configured to provide the corresponding network capabilities. According to the system of claim 4, the first network function is configured to receive a first request sent by a service caller, the first request being used to request the invocation of a service related to a first network capability; and to send a second request to the access network device based on the first request, the second request being used to request the invocation of the first network capability; the first network capability is any network capability provided by the access network device and/or the terminal. The access network device is configured to receive the second request and send the capability call result corresponding to the first network capability to the first network function. The first network function is configured to receive the capability call result sent by the access network device, determine the service call result based on the capability call result, and send the service call result to the service caller. According to the system of claim 6, the first network function is further configured to perform security authentication and/or identity authentication on the service caller. According to the system of claim 6, the first network function is further configured to obtain first policy information corresponding to the service caller, and provide corresponding network capabilities to the service caller based on the first policy information; the first policy information includes a policy for security control of the corresponding network capabilities and/or a policy for service billing of the corresponding network capabilities. According to the system of claim 1, the first network function and the access network device interact via a first interface, the first interface including a control plane interface and a data plane interface; and/or, The first functional entity and the second functional entity exchange information through a second interface. A communication method, the method being applied to a first network function; the method comprising: Services are provided based on various network capabilities offered by one or more connected access network devices; wherein the network capabilities are implemented by the corresponding access network device through a first functional entity based on various network resources in the communication network, and provided through a second functional entity. The method according to claim 10, wherein the method further comprises: Perform at least one of the following: User-related management; Management related to service security; Management of network capabilities related to perception; Management of network capabilities related to data services; Management of network capabilities related to artificial intelligence; Management related to network resources; Management related to policy control; Management related to the registration of third-party services. The method according to claim 10, wherein the method further comprises: The system receives a first request from a service caller, the first request being used to request the invocation of a service related to a first network capability; based on the first request, the system sends a second request to the access network device, the second request being used to request the invocation of the first network capability; the first network capability is any network capability provided by the access network device and/or a terminal connected to the access network device. Receive the capability call result sent by the access network device, determine the service call result based on the capability call result, and send the service call result to the service caller. The method according to claim 12, wherein the method further comprises: Security authentication and/or identity authentication are performed on the service caller. The method according to claim 12, wherein the method further comprises: Obtain first policy information corresponding to the service caller, and provide the corresponding network capabilities to the service caller based on the first policy information; the first policy information includes a policy for security control of the corresponding network capabilities and/or a policy for service billing of the corresponding network capabilities. A communication method, the method being applied to a first functional entity in an access network device; the method comprising: One or more network capabilities are implemented based on various network resources in the communication network; the one or more network capabilities are managed by a second functional entity in the access network device and provided by the second functional entity to a first network function that manages the access network device, and the one or more network capabilities are used by the first network function to provide services. A communication method, the method being applied to a second functional entity in an access network device; the method comprising: The device manages one or more network capabilities and provides these network capabilities to a first network function that manages the access network device. The one or more network capabilities are implemented by a first functional entity in the access network device based on various network resources in the communication network, and the one or more network capabilities are used by the first network function to provide services. The method according to claim 16, wherein managing one or more network capabilities includes at least one of the following: To monitor and control one or more of the aforementioned network capabilities; The computing resources in the communication network are subject to supervision and control, wherein the computing resources include computing resources provided by access network equipment and/or computing resources provided by terminals; Monitor and control each interface corresponding to the access network; Control the service scheduling corresponding to one or more of the aforementioned network capabilities; Control the execution tasks corresponding to one or more of the aforementioned network capabilities; Control the bearers corresponding to one or more of the aforementioned network capabilities; Control the context information. The method according to claim 17, wherein the method further comprises: Manage one or more network capabilities provided by the terminal, and/or provide services related to the one or more network capabilities to the terminal. A communication method, the method being applied to an access network device; the method comprising: A first functional entity implements one or more network capabilities based on various network resources in the communication network, and a second functional entity manages the one or more network capabilities and provides the one or more network capabilities to a first network function that manages the access network device; the one or more network capabilities are used by the first network function to provide services. The method according to claim 19, wherein the method further comprises: The second functional entity manages the one or more network capabilities provided by the terminal, and/or provides services related to the one or more network capabilities to the terminal. The method according to claim 20, wherein the method further comprises: Receive a second request sent by the first network function, the second request being used to request the invocation of a first network capability, the first network capability being any network capability provided by the access network device and/or the terminal; Send the capability call result corresponding to the first network capability to the first network function; the capability call result is used by the first network function to send the corresponding service call result to the service caller. A communication apparatus includes a first processing unit configured to provide services based on various network capabilities provided by one or more connected access network devices; wherein the network capabilities are implemented by the corresponding access network devices through a first functional entity based on various network resources in the communication network, and provided through a second functional entity. A communication device includes a second processing unit configured to implement one or more network capabilities based on network resources in a communication network; the one or more network capabilities are managed by a second functional entity in an access network device and provided by the second functional entity to a first network function that manages the access network device, and the one or more network capabilities are used by the first network function to provide services. A communication apparatus includes a third processing unit configured to manage one or more network capabilities and provide the one or more network capabilities to a first network function that manages an access network device; the one or more network capabilities are implemented by a first functional entity in the access network device based on various network resources in a communication network, and the one or more network capabilities are used by the first network function to provide services. An access network device includes a first functional entity and a second functional entity; wherein, The first functional entity is configured to implement one or more network capabilities based on various network resources in the communication network; The second functional entity is configured to manage the one or more network capabilities and provide the one or more network capabilities to the first network function; the one or more network capabilities are used to manage the service exposure of the first network function of the access network device. A communication device includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the steps of the method according to any one of claims 10 to 14; or, the processor executes the program to implement the steps of the method according to claim 15; or, the processor executes the program to implement the steps of the method according to any one of claims 16 to 18. A computer-readable storage medium having a computer program stored thereon that, when executed by a processor, implements the steps of the method according to any one of claims 10 to 14; or, when executed by a processor, implements the steps of the method according to claim 15; or, when executed by a processor, implements the steps of the method according to any one of claims 16 to 18. A computer program product includes a computer program that, when executed by a processor, implements the steps of the method according to any one of claims 10 to 14; or, when executed by a processor, the computer program implements the steps of the method according to claim 15; or, when executed by a processor, the computer program implements the steps of the method according to any one of claims 16 to 18.