Communication method and communication apparatus

Abstract

The present application relates to the field of communications, and specifically relates to a communication method and a communication apparatus. In an existing core network, there are functional coupling and dependency between services, and both the deployment and launching of new services and the upgrade of existing services affect the stability of an underlying mobile network. In the embodiments provided in the present application, a basic access service can complete event notification between an ultra-micro service and the basic access service without scheduling the ultra-micro service, and the launching or update of new services does not affect the basic access service, thereby enabling the requirement for a rapid innovation capability to be met while maintaining the stability of the underlying mobile network.

Description

Communication method and communication apparatus

[0001] The present application claims priority to the Chinese patent application No. 202411120044.8, filed on August 14, 2024, and entitled "Communication method and communication apparatus", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] The present application relates to the field of communication, in particular to a communication method and a communication apparatus. BACKGROUND

[0003] The function of the core network is mainly to provide user connection, user management and service bearing, and to provide an interface to an external network (such as the Internet) as a bearing network. In a core network based on a service-based architecture (SBA), network functions are defined as a number of "services" that can be flexibly invoked. Based on this, operators can flexibly network according to business needs. The interaction between network functions is realized by service invocation, and each network function presents a general service interface to the outside, and can be authorized network functions or service invocation.

[0004] In the SBA, each service can be deployed online and locally autonomous through the SBA bus, however, there is still a coupling and dependence between services, therefore, the deployment of new services and the upgrade of existing services will affect the stability of the underlying mobile network. Facing the world of everything intelligent connection, the future mobile network not only needs to have the ability of rapid innovation, but also needs to maintain the stability of the underlying mobile network while having the ability of rapid innovation, and the current SBA cannot meet the demand of having the ability of rapid innovation while maintaining the stability of the underlying mobile network. SUMMARY

[0005] Embodiments of the present application provide a communication method, a communication apparatus, a communication system, a computer readable storage medium and a computer program product, which can meet the demand of rapid innovation ability on the basis of maintaining the stability of the underlying mobile network.

[0006] In a first aspect, embodiments of the present application provide a communication method, which is applied to a third module, the third module can be a software module and / or a hardware module in a cloud computing infrastructure, and the following will be described taking the third module as a distributed network scheduling service. The method comprises: receiving first information, the first information indicating a first rule of a first module; receiving second information from a second module, the second information indicating that a first event has occurred; when the first event meets the first rule, sending third information to the first module, the third information indicating that the first event has occurred.

[0007] The first module is a module of a consumption event, that is, a module that needs to be processed based on the event, for example, a hyper-service that provides a new service. The second module is a module that generates an event, for example, a module that provides a basic access service of a mobile network. After the basic access service generates a first event, the distributed network scheduling service is notified of the first event through second information, and the distributed network scheduling service determines whether the hyper-service needs to be notified based on a first rule associated with the hyper-service. If the first event meets the first rule, the distributed network scheduling service can schedule the hyper-service, that is, send third information to the hyper-service to notify the hyper-service that the first event has been generated, so that the hyper-service performs subsequent processing based on the first event. As can be seen, in the embodiment, the basic access service does not need to schedule the hyper-service to complete the event notification between the hyper-service and the basic access service, and the online or update of the new service will not affect the basic access service, thereby meeting the demand for rapid innovation capability on the basis of maintaining the stability of the basic mobile network.

[0008] In an optional implementation of the first aspect, the method further includes: receiving fourth information, the fourth information indicating an association relationship between the first rule and the first event; and determining whether the first event meets the first rule according to the fourth information.

[0009] After receiving the second information, the distributed network scheduling service determines that the first event has been generated, and then the distributed network scheduling service can determine the rule corresponding to the first event, that is, the first rule, according to the association relationship indicated by the fourth information, and determine whether the first event meets the first rule. If the demand of the hyper-service for the first event changes, the hyper-service can update the rule associated with the first event, thereby flexibly adapting to different application scenarios.

[0010] In an optional implementation of the first aspect, the method further includes: receiving fifth information from the second module, the fifth information indicating an event supported by the second module, and the event supported by the second module including the first event.

[0011] The basic access service (an example of the second module) can register the events that it can provide to the distributed network scheduling service through the fifth information, so as to provide the event subscription capability of the hyper-service to the distributed network scheduling service.

[0012] In an optional implementation of the first aspect, the method further includes: receiving sixth information, the sixth information indicating that the first module subscribes to the first event; and determining whether the first event meets the first rule according to the sixth information.

[0013] The super micro service (an example of the first module) can subscribe to events required by the super micro service through the sixth information. After the first event occurs, the distributed network scheduling service can determine whether the first event is an event required by the super micro service according to the sixth information. If the first event is an event required by the super micro service, the distributed network scheduling service further determines whether the first event meets the first rule. In this way, the super micro service can be prevented from being notified of events that are not required by the super micro service, thereby saving communication resource overhead.

[0014] In an optional implementation of the first aspect, the method further includes: receiving seventh information, the seventh information indicating a deployment parameter of the first module; and deploying the first module according to the seventh information.

[0015] If the first event meets the first rule, the distributed network scheduling service needs to notify the super micro service that the first event has occurred. In some cases, an entity that implements a business function in the super micro service has not been deployed. The distributed network scheduling service can deploy the entity that implements the business function in the super micro service according to seventh information sent by another module (for example, an entity that implements a management function in the super micro service), thereby implementing on-demand deployment of the super micro service and saving resource overhead of the cloud computing infrastructure.

[0016] In an optional implementation of the first aspect, the first information includes a matching rule of at least one piece of information in the first event; and / or the first information includes first code for determining whether the first event meets the first rule.

[0017] The first information received by the distributed network scheduling service can include a matching rule (for example, the first rule) or executable code (for example, the first code). A simple rule can be implemented directly using the matching rule, and a complex rule can be implemented using the executable code, thereby flexibly adapting to different application scenarios.

[0018] In an optional implementation of the first aspect, the method further includes: when the first event does not meet the first rule, determining not to send third information to the first module, the third information indicating that the first event has occurred.

[0019] If the first event does not meet the first rule, it means that the first event is not an event required by the super micro service. The distributed network scheduling service can determine not to send third information to the super micro service, thereby saving communication resource overhead.

[0020] In a second aspect, embodiments of the present application provide a communication method applied to a first module, the first module can be a software module and / or a hardware module in a cloud computing infrastructure, and the first module is taken as an ultra micro service in the following description. The method comprises: sending first information to a third module, the first information indicating a first rule of the first module; and receiving third information from the third module, the third information indicating that a first event has occurred, wherein the first event is an event satisfying the first rule.

[0021] The first module is a module consuming events, i.e., a module requiring corresponding processing based on events, for example, an ultra micro service providing a new service. The second module is a module generating events, for example, a module providing a basic access service of a mobile network. After the basic access service generates the first event, the second module notifies a distributed network scheduling service through second information, and the distributed network scheduling service determines whether the ultra micro service needs to be notified based on the first rule associated with the ultra micro service. If the first event satisfies the first rule, the distributed network scheduling service can schedule the ultra micro service, i.e., send the third information to the ultra micro service, notifying the ultra micro service that the first event has occurred, so that the ultra micro service performs subsequent processing based on the first event. As can be seen, in the embodiment, the basic access service can complete the event notification between the ultra micro service and the basic access service without scheduling the ultra micro service, and the online or update of the new service will not affect the basic access service, thereby meeting the demand for rapid innovation capability on the basis of maintaining the stability of the basic mobile network.

[0022] In an optional implementation of the second aspect, the method further comprises: sending fourth information to the third module, the fourth information indicating an association between the first rule and the first event.

[0023] The demand of the ultra micro service for the event can be expressed through the first rule, and if the demand of the ultra micro service for the first event changes, the ultra micro service can update the rule associated with the first event, thereby flexibly adapting to different application scenarios.

[0024] In an optional implementation of the second aspect, the method further comprises: sending sixth information to the third module, the sixth information indicating that the first module subscribes to the first event.

[0025] The ultra micro service can subscribe to the event it needs through the sixth information, and the distributed network scheduling service can determine whether the first event is the event needed by the ultra micro service according to the sixth information after the first event occurs. In the case that the first event is the event needed by the ultra micro service, the distributed network scheduling service further judges whether the first event satisfies the first rule, which can avoid notifying the ultra micro service of events that the ultra micro service does not need, thereby saving communication resource overhead.

[0026] In an optional implementation of the second aspect, the method further includes: sending, to the third module, seventh information, the seventh information indicating the deployment parameter of the first module.

[0027] In some cases, the entity implementing the business function in the hyper microservice has not been deployed, and the entity implementing the management function in the hyper microservice can send the seventh information to the distributed network scheduling service, so that the distributed network scheduling service deploys the entity implementing the business function in the hyper microservice, thereby realizing on-demand deployment of the hyper microservice and saving resource overhead of the cloud computing infrastructure.

[0028] In an optional implementation of the second aspect, the first information includes a matching rule of at least one piece of information in the first event; and / or, the first information includes a first code, the first code being used to determine whether the first event satisfies the first rule.

[0029] The first information sent by the hyper microservice can include a matching rule (e.g., the first rule) or executable code (e.g., the first code), where a simple rule can be directly implemented using the matching rule, and a complex rule can be implemented using the executable code, thereby flexibly adapting to different application scenarios.

[0030] In an optional implementation of the second aspect, the method further includes: after the first module is deployed, sending, to the service registration module, eighth information, the eighth information indicating the service of the first module.

[0031] After the entity implementing the business function in the hyper microservice is deployed, the entity implementing the management function in the hyper microservice can send the eighth information to the service registration module, and register the service of the entity implementing the management function in the hyper microservice to the service registration module, so as to facilitate the distributed network scheduling service and other modules to discover and schedule the hyper microservice.

[0032] In the third aspect, the embodiments of the present application provide a communication method, which is applied to a second module, the second module can be a software module and / or a hardware module in a cloud computing infrastructure, and the following is described by taking a third module as an example. The method includes: determining a first event; sending, to the third module, second information, the second information indicating that the first event has occurred, and the second information being used to send, by the third module, third information to the first module, where the third module sends the third information to the first module when the first event satisfies a first rule of the first module, the third information indicating that the first event has occurred.

[0033] The first module is a module of a consumption event, that is, a module that needs to be processed based on the event, for example, a hyper-service that provides a new service. The second module is a module that generates an event, for example, a module that provides a basic access service of a mobile network. After the basic access service generates a first event, the distributed network scheduling service is notified of the generation of the first event through second information. The distributed network scheduling service determines whether the hyper-service needs to be notified based on a first rule associated with the hyper-service. If the first event satisfies the first rule, the distributed network scheduling service can schedule the hyper-service, that is, send third information to the hyper-service to notify the hyper-service that the first event has been generated, so that the hyper-service performs subsequent processing based on the first event. As can be seen, in the embodiment, the basic access service can complete the event notification between the hyper-service and the basic access service without scheduling the hyper-service, and the online or update of the new service will not affect the basic access service, thereby meeting the demand for rapid innovation capability on the basis of maintaining the stability of the basic mobile network.

[0034] In an optional implementation of the third aspect, the method further includes: sending fifth information to the third module, the fifth information indicating an event supported by the second module, and the event supported by the second module including the first event.

[0035] The basic access service can register the events that can be provided by the basic access service to the distributed network scheduling service through the fifth information, so as to provide the event subscription capability of the hyper-service to the distributed network scheduling service.

[0036] In a fourth aspect, an embodiment of the present application provides a communication device. The communication device can include a processing unit and a communication unit, configured to perform: any one of the methods in the first aspect and the optional implementations thereof, or any one of the methods in the second aspect and the optional implementations thereof, or any one of the methods in the third aspect and the optional implementations thereof.

[0037] In a fifth aspect, an embodiment of the present application provides a communication device, which can be a cloud computing infrastructure or a chip applied to the cloud computing infrastructure. The communication device can include a processor configured to perform: any one of the methods in the first aspect and the optional implementations thereof, or any one of the methods in the second aspect and the optional implementations thereof, or any one of the methods in the third aspect and the optional implementations thereof.

[0038] Optionally, the communication device can further include a transceiver. When the communication device is a cloud computing infrastructure, the transceiver can be a transceiver circuit, an antenna, etc. When the communication device is a chip applied to the cloud computing infrastructure, the transceiver can be an input / output interface, a pin, a circuit, etc.

[0039] Optionally, the communication apparatus further comprises a memory for storing a computer program or instructions, and the processor executes the computer program or instructions stored in the memory to enable the communication apparatus to perform the method of any one of the first aspect and the optional embodiments thereof, or the method of any one of the second aspect and the optional embodiments thereof, or the method of any one of the third aspect and the optional embodiments thereof. When the communication apparatus is a cloud computing infrastructure, the memory can be a read-only memory, a random access memory, etc.; when the communication apparatus is a chip applied to a cloud computing infrastructure, the memory can be a register, a cache, etc.

[0040] In a sixth aspect, the embodiments of the present application provide a communication system, comprising at least two of the communication apparatus for performing the method of any one of the first aspect and the optional embodiments thereof, the communication apparatus for performing the method of any one of the second aspect and the optional embodiments thereof, and the communication apparatus for performing the method of any one of the third aspect and the optional embodiments thereof according to the fourth aspect; or at least two of the communication apparatus for performing the method of any one of the first aspect and the optional embodiments thereof, the communication apparatus for performing the method of any one of the second aspect and the optional embodiments thereof, and the communication apparatus for performing the method of any one of the third aspect and the optional embodiments thereof according to the fifth aspect.

[0041] In a seventh aspect, the embodiments of the present application provide a computer readable storage medium storing a computer program or instructions; when the computer program or instructions are executed on a communication apparatus, the communication apparatus performs the method of any one of the first aspect and the optional embodiments thereof, or the method of any one of the second aspect and the optional embodiments thereof, or the method of any one of the third aspect and the optional embodiments thereof.

[0042] In an eighth aspect, the embodiments of the present application provide a computer program product comprising a computer program or instructions; when the computer program or instructions are run on a communication apparatus, the communication apparatus performs the method of any one of the first aspect and the optional embodiments thereof, or the method of any one of the second aspect and the optional embodiments thereof, or the method of any one of the third aspect and the optional embodiments thereof. BRIEF DESCRIPTION OF DRAWINGS

[0043] FIG. 1 is a schematic diagram of an architecture of a communication system to which the embodiments of the present application are applied;

[0044] FIG. 2 is a schematic diagram of an architecture of a core network to which the embodiments of the present application are applied;

[0045] FIG. 3 is a schematic diagram of a communication system applying microservices and serverless architecture according to an embodiment of the present application;

[0046] FIG. 4 is a schematic diagram of a communication method according to an embodiment of the present application;

[0047] FIG. 5 is a schematic diagram of a scheduling chain according to an embodiment of the present application;

[0048] FIG. 6 is a schematic diagram of a method of scheduling microservices according to an embodiment of the present application;

[0049] FIG. 7 is a schematic diagram of another communication method according to an embodiment of the present application;

[0050] FIG. 8 is a schematic diagram of still another communication method according to an embodiment of the present application;

[0051] FIG. 9 is a schematic diagram of still another communication method according to an embodiment of the present application;

[0052] FIG. 10 is a schematic diagram of still another communication method according to an embodiment of the present application;

[0053] FIG. 11 is a schematic diagram of still another communication method according to an embodiment of the present application;

[0054] FIG. 12 is a schematic diagram of a structure of a communication apparatus according to an embodiment of the present application;

[0055] FIG. 13 is a schematic diagram of a structure of another communication apparatus according to an embodiment of the present application. DETAILED DESCRIPTION

[0056] The technical solutions in the present application will be described below with reference to the accompanying drawings.

[0057] FIG. 1 is a schematic diagram of an architecture of a communication system 1000 to which embodiments of the present application are applied. As shown in FIG. 1, the communication system 1000 includes a radio access network (RAN) 100, wherein the RAN 100 includes at least one RAN node (e.g., 110a-110b, collectively referred to as 110 in FIG. 1), and can further include at least one terminal (e.g., 120a-120j, collectively referred to as 120 in FIG. 1). The RAN 100 can further include other RAN nodes, such as wireless relay devices and / or wireless backhaul devices (not shown in FIG. 1). The terminals 120 are connected to the RAN nodes 110 in a wireless manner. Terminals and terminals, and RAN nodes and RAN nodes can be connected to each other in a wired or wireless manner. The communication system 1000 can further include a core network (CN) 200. The RAN nodes 110 are connected to the core network 200 in a wireless or wired manner. The core network devices in the core network 200 and the RAN nodes 110 in the RAN 100 can be independent and different physical devices, or can be the same physical device integrated with the logical functions of the core network devices and the logical functions of the RAN nodes. Optionally, the communication system 1000 can further include an Internet 300.

[0058] The RAN 100 can be an evolved universal terrestrial radio access (E-UTRA) system, a new radio (NR) system, or a future wireless access system defined in the 3rd generation partnership project (3GPP), or a Wi-Fi system. The RAN 100 can also include two or more different wireless access systems. The RAN 100 can also be an open RAN (O-RAN).

[0059] The RAN node, also referred to as a network device, an access network device, a radio access network device, a RAN entity, or an access node, is used to help the terminal access the communication system in a wireless manner.

[0060] In different systems, the RAN node can have different names, for example, in an O-RAN system, the CU can be referred to as an open CU (O-CU), the DU can be referred to as an open DU (O-DU), and the RU can be referred to as an open RU (O-RU). The RAN node in the embodiments of the present application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module. For example, the RAN node can be a server loaded with a corresponding software module. The embodiments of the present application do not limit the specific technology and specific device form of the RAN node. For ease of description, a base station is described as an example of the RAN node in the following.

[0061] A terminal is a device with wireless transceiver function, which can send signals to a base station or receive signals from a base station. The terminal can also be referred to as a terminal device, user equipment (UE), mobile station, mobile terminal, etc. The terminal can be widely applied in various scenarios, such as device-to-device (D2D), vehicle to everything (V2X) communication, machine-type communication (MTC), internet of things (IoT), virtual reality (VR), augmented reality (AR), industrial control, autonomous driving, remote medical treatment, smart grid, smart furniture, smart office, smart wear, smart transportation, smart city, etc. The terminal can be a mobile phone (such as 120a, 120e, 120f and 120j in FIG. 1), a notebook computer (such as 120g in FIG. 1), a printer with wireless transceiver function (such as 120h in FIG. 1), a wearable device, a vehicle (such as 120b in FIG. 1), a charging pile (such as 120c in FIG. 1), an airplane (such as 120i in FIG. 1), a ship, a robot, a mechanical arm, a smart home device, etc. The embodiments of the present application do not limit the specific technology and specific device form of the terminal.

[0062] The base station and the terminal can be fixed in position or movable. The base station and the terminal can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; can also be deployed on the water surface; can also be deployed on an airplane, a balloon and a man-made satellite. The embodiments of the present application do not limit the application scenarios of the base station and the terminal.

[0063] The roles of the base station and the terminal can be relative, for example, 120i in FIG. 1 (which can be a helicopter or a drone) can be configured as a mobile base station, and for 120j that accesses the wireless access network 100 through 120i, 120i is a base station; but for 110a, 120i is a terminal, that is, 110a and 120i communicate through a wireless air interface protocol. Of course, 110a and 120i can also communicate through a base station-to-base station interface protocol, in which case 120i is also a base station relative to 110a. Therefore, the base station and the terminal can be collectively referred to as a communication device, and 110a and 110b in FIG. 1 can be referred to as a communication device with a base station function, and 120a-120j in FIG. 1 can be referred to as a communication device with a terminal function.

[0064] Next, the functions of the core network 200 are briefly introduced.

[0065] The functions of the core network 200 mainly include user connection, user management, and service bearing, and as a bearing network, the core network 200 provides an interface to an external network (such as the Internet 300). Optionally, taking SBA as an example, the architecture of the core network 200 is shown in FIG. 2.

[0066] SBA is mainly reflected in the control plane, and the essence of SBA is to define network functions as a number of services that can be flexibly invoked according to the three principles of "self-contained, reusable, and independent management". Based on this, the operator can flexibly customize the network according to the business requirements. The interaction between network functions is realized by service invocation, and each network function presents a general service interface to the outside, which can be authorized by network functions or service invocation.

[0067] As shown in FIG. 2, the core network 200 can include a user plane function (UPF), an access and mobility management function (AMF), a session management function (SMF), a unified data management function (UDM), an authentication server function (AUSF), a policy control function (PCF), and a network repository function (NRF).

[0068] The above UPF, AMF, SMF, UDM, AUSF, PCF and NRF can be referred to as core network elements or core network devices, which can be independent hardware devices, or modules integrated in the same hardware device to realize different functions, or software functions running on a dedicated hardware or virtualized functions instantiated on a cloud platform, and embodiments of the present application do not limit the specific form of the core network elements.

[0069] The core network elements in FIG. 2 are briefly introduced as follows.

[0070] The UPF, which can also be referred to as a user plane device, a user plane function network element, a user plane network element, or a user plane function entity, can be understood as the naming of the user plane function network element in 5G. The user plane function network element mainly includes the following functions: data packet routing and transmission, packet detection, service usage reporting, QoS processing, uplink packet detection, downlink data packet storage and other user plane related functions.

[0071] Optionally, the UPF can be divided into a protocol data unit (PDU) session anchor UPF (PSA-UPF) and an intermediate UPF (I-UPF), wherein the PSA-UPF is a UPF supporting the PDU session anchor function, is a UPF connected with a DN through an N6 interface, and is responsible for data transmission between the core network and the DN; all UPFs between the RAN and the PSA-UPF can be referred to as I-UPFs, the I-UPF can be connected with the RAN through an N3 interface, and the I-UPF can be connected with the PSA-UPF through an N9 interface.

[0072] The AMF, which can also be referred to as a mobility management device, can be understood as the naming of the mobility management network element in the 5G architecture. The mobility management network element mainly includes the following functions: connection management, mobility management, registration management, access authentication and authorization, reachability management, security context management and other access and mobility related functions.

[0073] The SMF, which can be understood as the naming of the session management function network element in the 5G architecture. The session management function network element mainly performs session management, execution of control policies issued by the PCF, selection of the UPF, UE internet protocol (IP) address allocation and other functions.

[0074] The UDM, which can also be referred to as a unified data management network element, a unified data management entity, or a data management device, can be understood as the naming of the unified data management network element in the 5G architecture. The unified data management network element is mainly used for processing terminal device identification, access authentication, registration and mobility management, etc.

[0075] The AUSF, which can also be referred to as an authentication service function network element, an authentication service function entity, an authentication service device, or an authentication device, can be understood as the naming of the authentication service function network element in the 5G architecture. The authentication service function network element is mainly used for user authentication. For example, after receiving an authentication request initiated by a subscription user, the authentication service function network element can authenticate and / or authorize the subscription user by using authentication information and / or authorization information stored in the unified data management network element, or generate authentication and / or authorization information of the subscription user by using the unified data management network element. The authentication service function network element can feed back the authentication information and / or authorization information to the subscription user. In a possible implementation manner, the authentication service function network element can also be combined with the unified data management network element.

[0076] The PCF, which can also be referred to as a policy control network element, a policy control function network element, a policy control device, or a policy control function entity, can be understood as the naming of the policy control function network element in the 5G architecture. The policy control function network element is mainly responsible for providing a unified policy framework for network behavior management, policy rules for control plane functions, obtaining registration information related to policy decision, charging for a session or a service flow, quality of service (QoS) bandwidth guarantee, and the like.

[0077] The NRF, which can also be referred to as a network storage device, a network storage function network element, or a network storage function entity, can be understood as the naming of the network storage function network element in the 5G architecture. The NRF is mainly used to support the service discovery function. After receiving a network element discovery request from a network element or a service communication proxy (SCP), the NRF can send feedback information of the network element discovery request. Meanwhile, the NRF is also used to maintain information of available network functions and services supported by each network function. The NRF can provide an IP address, a fully qualified domain name (FQDN), or a unified resource identifier (URI) of a network function (NF) instance or an NF service instance to realize the service discovery function. In addition, the NRF can also realize the discovery process across public land mobile networks (PLMNs) by providing a PLMN identifier (ID). In order to realize the addressing discovery of the NF, each NF can be registered in the NRF, and optionally, some NFs can be registered in the NRF at the first run.

[0078] DN is an example of the Internet 300, which is a network located outside the operator network. The operator network (e.g., the core network 200) can access multiple DNs, and the DNs can deploy various services and provide data and / or voice services for terminal devices. For example, the DN is a private network of a smart factory, and the sensors installed in the workshop of the smart factory can be terminal devices, and the control server of the sensors is deployed in the DN, and the control server can provide services for the sensors. The sensors can communicate with the control server, obtain instructions from the control server, and transmit the collected sensor data to the control server according to the instructions, and the like. For another example, the DN is an internal office network of a company, and the mobile phones or computers of employees of the company can be terminal devices, and the mobile phones or computers of the employees can access information and data resources on the internal office network of the company.

[0079] In FIG. 2, Uu, N1, N2, N3, N4, N6, N9, N11, and N14 are interface numbers, in which the dashed lines corresponding to N9 and N14 indicate that these two interfaces are optional interfaces. In addition, Namf is a service interface corresponding to the AMF, Nsmf is a service interface corresponding to the SMF, Nausf is a service interface corresponding to the AUSF, Nudm is a service interface corresponding to the UDM, Npcf is a service interface corresponding to the PCF, and Nnrf is a service interface corresponding to the NRF. The meanings of these interfaces shown in FIG. 2 can refer to the meanings defined in the 3GPP standard protocol, which are not limited herein.

[0080] The above network architecture is only illustrative, and the network architecture to which the embodiments of the present application are applicable is not limited thereto. Any network architecture including the functions of the above-mentioned network elements is applicable to the embodiments of the present application.

[0081] The above naming is only defined for the purpose of distinguishing different functions, and should not constitute any limitation on the present application. The present application does not exclude the possibility of using other names in the 5G network and other future networks. For example, in future communication networks, part or all of the above-mentioned network elements can use the terms in 5G, or other names, etc. The above interface name is only an example, and the name of the interface in the specific implementation can be other names, which are not limited in the present application.

[0082] In the SBA, network functions are decoupled into multiple independent services, and the deployment and local autonomy of services are implemented through the SBA bus. However, there is still a problem of coupling and dependence between services. The online of new functions or new features will affect existing services, and the upgrade of an existing service will also affect other existing services. In particular, for basic access services, frequent service changes or service upgrades will lead to insufficient stability of basic access services. Therefore, operators have strict requirements for the online of new features or new services, which leads to an increase in the deployment and online period of new features or new functions, affecting the innovation and rapid evolution of 5G services.

[0083] Taking 5G local area network (LAN) business innovation for enterprises as an example, under the 5G SBA, the addition of LAN services needs to extend the function of SMF. The main effects of SMF are as follows:

[0084] (1) SMF needs to provide UE grouping capability on the basis of the existing UE single session. An independent microservice is used to implement this function. This function is basically decoupled from the original session management process, and only needs to sense events such as session establishment and deletion.

[0085] (2) SMF needs to create a 5G LAN UE set session on the basis of the original N4 session, and decouple from the original UE session.

[0086] (3) The 5G LAN function is weakly associated with SMF. However, due to the large granularity of the function of SMF, after adding the 5G LAN service and function, the SMF code needs to be modified, compiled, packaged and deployed again, which may affect the basic session management function of SMF. At the same time, due to the re-release of the entire SMF software, in-network testing is required, which leads to an increase in the deployment and online time of the 5G LAN feature.

[0087] In the face of a world of everything connected, future mobile networks not only need to have rapid innovation capability, but also need to maintain the stability of the basic mobile network while rapidly innovating. The current SBA cannot meet the demand of having rapid innovation capability while maintaining the stability of the basic access service.

[0088] In order to facilitate the understanding of the embodiments of the present application, before introducing the embodiments of the present application, the technologies involved in the embodiments of the present application are briefly introduced.

[0089] 1. Microservice.

[0090] Microservices architecture is a service-oriented architectural pattern. It involves breaking down a large application into a set of small, autonomous microservices, each focusing on completing a specific business function, and each being independently deployable, scalable, and replaceable, and communicating through lightweight communication mechanisms such as HTTP or message queues.

[0091] Microservices architecture has the following characteristics:

[0092] High scalability: Each microservice can be independently scaled, with the number of instances of a microservice being increased or decreased as needed, allowing better handling of application load.

[0093] Independent deployment: Each microservice can be independently deployed without affecting other services. This allows developers to release new features, fix bugs, or make updates more quickly without stopping the entire application.

[0094] Technology stack flexibility: Different microservices can use different technology stacks and programming languages, allowing developers to choose the appropriate tools and frameworks based on their expertise.

[0095] Loose coupling: Each microservice is autonomous and has no strong dependencies on other services, allowing developers to independently develop and test each service, reducing code conflicts and integration issues.

[0096] 2. Serverless.

[0097] Serverless is an architecture of cloud computing that enables the construction and operation of applications that do not require server management. Based on the serverless architecture, developers can manage application deployment at the service deployment level rather than the server deployment level. The difference between serverless architecture and traditional architecture is that serverless architecture is completely managed by a third party, triggered by events, and exists in a stateless, temporary (may only exist in the process of a single call) computing container. Building a serverless application means that developers can focus on product code without having to manage and operate servers in the cloud or on-premises. Serverless architecture achieves automatic building, deployment, and starting of services, and does not require involvement of infrastructure construction when deploying applications, while the business-level state is recorded by the databases and storage resources used by developers.

[0098] Serverless architecture is mainly applied in the following scenarios. First, in the global wide web (Web) and mobile services, application programming interface (API) gateways and serverless services can be integrated to build Web and mobile backends, helping developers build elastic, scalable, and efficient mobile or Web backend application services. In the IoT scenario, real-time stream data can be efficiently processed. Massive real-time information stream data generated by devices can be classified and processed by serverless services and written to the backend for processing. In the real-time media content processing scenario, users upload audio and video to object storage services (OSS), and multiple functions are triggered by upload events to complete high-definition transcoding, audio transcoding, and other functions, meeting the high requirements of users for real-time and concurrency. Serverless computing is also suitable for various event-driven use cases, including the Internet of Things, mobile applications, network-based applications, and chatbots.

[0099] Serverless architecture covers many technologies, mainly divided into two categories: backend as a service (BaaS) and function as a service (FaaS).

[0100] BaaS refers to a technology that allows developers to no longer write or manage all server components and use domain-specific remote components (rather than in-process libraries) to provide services. BaaS can be some backend cloud services, such as cloud databases, object storage, and message queues. With BaaS, application development difficulty can be simplified.

[0101] FaaS is a computing execution model that implements serverless computing methods in an event-driven manner, has fully automatic, elastic, and horizontally scalable capabilities managed by service providers, and can help developers reduce operating and development costs. On the FaaS platform, developers only need to write simple event processing functions to build their own services, and leave everything else to the platform. Users only need to focus on their business code to improve business development efficiency.

[0102] 3. Super microservices.

[0103] Super microservices can be considered as services with a granularity between microservices and serverless / FaaS. Compared with microservices, the main differences between super microservices and microservices are service granularity and runtime. The granularity of most super microservices is smaller than that of microservices. In addition, the runtime of super microservices can be bound to one or more runtimes, which can be seamlessly migrated and deployed on various cloud infrastructures without the need to change the code.

[0104] FIG. 3 is a schematic diagram of a communication system applying microservices and serverless architecture according to an embodiment of the present application.

[0105] The communication system shown in FIG. 3 includes a basic access service, a distributed network scheduling service, a hyper microservice, a context database, a software image warehouse, and a runtime. These modules are all running on a cloud computing infrastructure, which refers to a collection of infrastructure required by a cloud computing system, including computing resources, storage resources, and network resources, etc. These resources are integrated through virtualization technology to realize the sharing, management, and optimization of resources. The cloud computing infrastructure is the cornerstone of the cloud computing system, providing reliable support for upper-layer cloud computing services. The functions of each module running on the cloud computing infrastructure are introduced below.

[0106] Basic access service: provides mobile network basic access functions, such as core network authentication, session, charging, policy, and mobility functions, which can be implemented through monolithic or microservice, etc. The basic access service needs to have stability, high reliability, and high performance. New services can be extended based on the basic access service.

[0107] Distributed network scheduling service: completes the distributed deployment and scheduling of hyper microservices based on the basic access service and the configured service call chain.

[0108] The main responsibilities of the distributed network scheduling service include:

[0109] Service registration: receives the basic information registered by the hyper microservice, such as deployment resources, service type, and runtime, etc.

[0110] Event registration: receives the events registered by the basic access service and acts as an agent to publish the events;

[0111] Event subscription and publication: publishes the events of the basic access service to the hyper microservice based on the subscription of the hyper microservice;

[0112] Service scheduling: triggers the deployment and scheduling of the hyper microservice when the event occurs, completes the event notification; if multiple hyper microservices have completed service registration, the distributed network scheduling service can perform service chain calling;

[0113] Characteristic decision: the hyper microservice can provide a plug-in for nearby deployment, and the distributed network scheduling service provides a characteristic decision function based on the plug-in to reduce the number of event notification messages when the characteristic is not turned on.

[0114] New service: a software module carrying new functions and features, which can implement feature functions according to the API provided by the basic access service, such as the 5G LAN service described above. It can be implemented using technologies such as hyper-service, FaaS, or Service Weaver. The communication system shown in FIG. 3 can include multiple new services.

[0115] Context database: a database carrying external data (such as context) of the basic access service or the new service. The distributed network scheduling service can read the data in the context database to make service decisions, and the new service can also access this database to read the context to support the implementation of service logic.

[0116] Software image warehouse: a warehouse providing hyper-service image resources. The distributed network scheduling service can dynamically pull the image of the hyper-service to be deployed from the software image warehouse and deploy it.

[0117] Runtime: a module responsible for providing a service running environment. The runtime can provide a running environment such as the language and version of the code running, callable objects, and system information. Based on the granularity of the service, the runtime can have different implementations, for example, when the service granularity is large, the runtime can be implemented through microservices; when the service granularity is small, the runtime can be implemented through functions.

[0118] The communication system shown in FIG. 3 is an example and is not limited, and the communication system shown in FIG. 3 can include more or fewer modules, or some modules in the communication system shown in FIG. 3 can be divided in other ways.

[0119] The following describes a communication method provided by an embodiment of the application.

[0120] As shown in FIG. 4, the execution subject of the method 400 includes a first module, a second module, and a third module, which can be software modules and / or hardware modules in a cloud computing infrastructure. The following describes an example in which the first module is a hyper-service, the second module is a basic access service, and the third module is a distributed network scheduling service.

[0121] S410, the hyper-service sends first information to the distributed network scheduling service, indicating a first rule of the first module.

[0122] Correspondingly, the distributed network scheduling service receives the first information from the hyper-service. It should be noted that the hyper-service can include an entity implementing a service function and an entity implementing a management function, and the hyper-service sending the first information refers to the entity implementing the management function in the hyper-service. Alternatively, the distributed network scheduling service can also receive the first information from a module (such as a module responsible for service registration) other than the hyper-service.

[0123] The ultra microservice is an optional way to implement a new service, which can also be implemented by microservice, serverless or other technologies. The new service is, for example, the 5G LAN service described above.

[0124] The ultra microservice can send first information to the distributed network scheduling service in a service decision algorithm registration process.

[0125] In some cases, the first information can not include the event ID, and the event associated with the first rule can be implemented in a predefined or preconfigured manner (e.g., configured by a developer), or the event associated with the first rule can be configured by another information (e.g., fourth information), which can include the event ID of the first event and the ID of the first rule, indicating the association relationship between the first rule and the first event.

[0126] After the distributed network scheduling service determines that the first event occurs, it can determine the rule corresponding to the first event, i.e., the first rule, according to the association relationship indicated by the fourth information, and determine whether the first event meets the first rule. If the demand of the ultra microservice for the first event changes, the ultra microservice can update the rule associated with the first event, for example, update the rule ID in the fourth information to the ID of another rule, so as to flexibly adapt to different application scenarios.

[0127] In other cases, the first information can include the event ID, and the event associated with the first rule is specified in the service decision algorithm registration process. For example, the first information can include: the event ID, the service type ID and the content or ID of the first rule.

[0128] The first rule described above can be a matching rule, for example, the first rule can match the PLMN, access point (AP), PDU type, address, user subscription attribute, etc. in the user information (e.g., dynamic context or subscription data). The service type ID is used to indicate the ultra microservice associated with the first rule. The event ID is used to indicate the event associated with the first rule.

[0129] For example, the first information includes event ID1, service type A and PLMN1, and the first information indicates the first rule of the ultra microservice of service type ID service type A, wherein the first rule is: matching the event ID is ID1, and the ID of the PLMN is PLMN1.

[0130] In the above example, the first information includes a matching rule of at least one piece of information (e.g., the ID of the PLMN) in the event. Alternatively, the first information can also include a first code used to determine whether the event meets the first rule; in this case, the hyper-service can send executable code containing the first rule to the distributed network scheduling service in the business decision algorithm registration process, and when the event (e.g., the first event) meeting the triggering condition triggers the distributed network scheduling service to perform event information matching, the distributed network scheduling service can locally call the executable code to perform event information matching. For example, the distributed network scheduling service can read the corresponding context from the context database according to the context type (which can be carried by the first information) specified by the hyper-service when registering the business decision algorithm, and call the executable code to perform matching of the context information to determine whether the first event meets the first rule.

[0131] The first information can also include both the matching rule and the executable code, where simple rules can be directly implemented using the matching rule, and complex rules can be implemented using the executable code, so that different application scenarios can be flexibly adapted.

[0132] S420, the basic access service sends second information to the distributed network scheduling service, indicating that the first event has occurred.

[0133] Correspondingly, the distributed network scheduling service receives the second information from the basic access service. It should be noted that the second module can also be a hyper-service capable of generating an event, that is, the distributed network scheduling service can receive the second information from a hyper-service capable of generating an event.

[0134] The first event can be an event of successful creation of a 5G LAN session, or other events, and embodiments of the present application do not limit the specific content of the first event.

[0135] The second information can include: an event ID and event information. The event information can include user identification and session identification of the first event, and can also include extension information related to the first event.

[0136] Alternatively, before sending the second information to the distributed network scheduling service, the basic access service can send fifth information to the distributed network scheduling service in an event registration process, and the fifth information can include: an event ID and a service type ID. The service type ID is used to indicate the basic access service, and the event ID is used to indicate the event supported by the basic access service.

[0137] For example, the fifth information includes the event ID 1 and the service type B, the fifth information indicates the subscription of the event with the event ID 1 by the event with the service type ID as the service type B, or in other words, the fifth information indicates that the event with the event ID as ID 1 can be generated by the basic access service with the service type ID as the service type B. In this way, the basic access service can register the events that can be provided by the basic access service to the distributed network scheduling service, so as to facilitate the distributed network scheduling service to provide the event subscription capability to the micro service.

[0138] Optionally, the micro service can subscribe to the events required by the micro service from the distributed network scheduling service.

[0139] For example, the micro service can send the sixth information to the distributed network scheduling service, the sixth information can include ID 1 and the service type A, where the service type A indicates the micro service, and ID 1 indicates that the micro service subscribes to the first event. The distributed network scheduling service can save the association between ID 1 and the service type A according to the sixth information. After the distributed network scheduling service determines that the first event is generated, the distributed network scheduling service can determine whether the first event is the event required by the micro service according to the association indicated by the sixth information. If the first event is the event required by the micro service, the distributed network scheduling service further determines whether the first event meets the first rule. In this way, the micro service can be prevented from being notified of the event that is not required by the micro service, thereby saving the communication resource overhead.

[0140] It should be noted that the subscription process of the micro service does not need to depend on the event registration process of the basic access service (the process corresponding to the fifth information), and the events supported by the basic access service can also be implemented in a predetermined or preconfigured manner, for example, by a developer configuring in the distributed network scheduling service.

[0141] For the scenario of multiple micro services subscribing to multiple events, the distributed network scheduling service can manage the events in the form of a chain with the event ID as the key value.

[0142] As shown in FIG. 5, each node of the micro service includes the service type of the micro service and the business decision algorithm. The service type is used to indicate the micro service, which can be understood as the ID of the micro service. The business decision algorithm can be a matching rule or an executable code indicating the matching rule.

[0143] Each event can be associated with one or more micro services. For example, event 1 is associated with three micro services, and the scheduling strategies of the three micro services are independent. That is, when the distributed network scheduling service schedules the micro services according to the event 1, the distributed network scheduling service can simultaneously schedule the micro service A, the micro service B and the micro service C, or the distributed network scheduling service can schedule the micro service A, the micro service B and the micro service C in a certain order.

[0144] Each super microservice can be associated with one or more events, and the business decision algorithms associated with different events can be the same or different. Taking super microservice A as an example, super microservice A is associated with event 1 and event 3, and the business decision algorithm associated with super microservice A and event 1 can be a matching rule for matching a PLMN, and the business decision algorithm associated with super microservice A and event 3 can be executable code indicating a matching rule for matching a session type.

[0145] Based on the chain management method, the super microservice can flexibly register the associated events and business decision algorithms according to business requirements.

[0146] Returning to S420, after the distributed network scheduling service determines that the first event is generated, if the first event is an event associated with a super microservice, the distributed network scheduling service can perform the following steps.

[0147] S430, the distributed network scheduling service determines whether the first event satisfies the first rule.

[0148] For example, the first rule is: matching an event with an event ID of ID1 and a PLMN ID of PLMN1, the distributed network scheduling service can obtain the event ID and the PLMN ID from the first event, and determine whether the first event satisfies the first rule according to the two IDs. If the event ID of the first event is ID1 and the event information of the first event includes PLMN1, the distributed network scheduling service determines that the first event satisfies the first rule; otherwise, the distributed network scheduling service determines that the first event does not satisfy the first rule.

[0149] When the first event does not satisfy the first rule, it means that the first event is not the event required by the super microservice, and the distributed network scheduling service determines not to send information indicating that the first event has been generated to the first module, so as to save the communication resource overhead.

[0150] When the first event satisfies the first rule, the distributed network scheduling service can perform the following steps.

[0151] S440, the distributed network scheduling service sends third information to the super microservice, indicating that the first event has been generated, wherein the first event satisfies the first rule.

[0152] If the entity implementing the business function in the hyper microservice has been deployed, the distributed network scheduling service can directly send the third information to the hyper microservice; if the entity implementing the business function in the hyper microservice has not been deployed, the distributed network scheduling service can obtain the image of the hyper microservice from the software image warehouse according to the deployment parameter of the hyper microservice, and deploy the entity implementing the business function in the hyper microservice, and then send the third information to the entity implementing the business function in the hyper microservice, wherein the deployment parameter of the hyper microservice can be indicated by the entity implementing the management function in the hyper microservice through the seventh information in the service registration process. The latter case realizes the on-demand deployment of the hyper microservice, and saves the resource overhead of the cloud computing infrastructure.

[0153] After the entity implementing the business function in the hyper microservice is deployed, the entity implementing the management function in the hyper microservice can send the eighth information to the service registration module (such as NRF) to register its own service to the service registration module, so as to facilitate the discovery and scheduling of the hyper microservice by the distributed network scheduling service and other modules.

[0154] FIG. 6 is a schematic diagram of a method for scheduling a hyper microservice according to an embodiment of the present application.

[0155] The hyper microservice A, the hyper microservice B and the hyper microservice C complete service registration and business decision algorithm registration in the distributed network scheduling service, and the hyper microservice A subscribes to event 1, the hyper microservice B subscribes to event 1, and the hyper microservice C subscribes to event 1 and event 2, as shown in scheduling chain 1 and scheduling chain 2 in FIG. 5.

[0156] After the basic access service generates event 1, the message that event 1 has been generated is notified to the distributed network scheduling service through step S1. The distributed network scheduling service determines that the hyper microservice A, the hyper microservice B and the hyper microservice C are to be scheduled based on the scheduling chain 1, and the distributed network scheduling service can schedule the business decision algorithm of the hyper microservice A, the hyper microservice B and the hyper microservice C through the characteristic decision module respectively, to determine whether event 1 meets the matching rules of the three hyper microservices. If yes, the distributed network scheduling service can schedule the hyper microservice A, the hyper microservice B and the hyper microservice C through the service scheduling module respectively.

[0157] For example, the distributed network scheduling service schedules the service decision algorithm of super microservice A, matches the ID of the PLMN of event 1, and the matching result is successful. Then the distributed network scheduling service schedules super microservice A through step S1a, and informs super microservice A that event 1 has occurred. The distributed network scheduling service schedules the service decision algorithm of super microservice B, matches the data read from the context database, and the matching result is failure. Then the distributed network scheduling service determines not to schedule super microservice B. The distributed network scheduling service schedules the service decision algorithm of super microservice C, matches the session type of event 1, and the matching result is successful. Then the distributed network scheduling service schedules super microservice C through step S1c, and informs super microservice C that event 1 has occurred.

[0158] It should be noted that after the basic access service generates event 1, the data related to event 1 needs to be written into the database (such as the context database shown in FIG. 6). The distributed network scheduling service can determine whether to read the database according to actual conditions when calling the service decision algorithm. For example, some information (such as the ID of the PLMN) can be obtained from the event notification message (such as the message carrying the second information), so the distributed network scheduling service does not need to read the database. If some information cannot be obtained from the event notification message, the distributed network scheduling service can read the database. Whether to read the database can also be indicated by the super microservice when registering the service decision algorithm (such as when sending the first information).

[0159] Optionally, after super microservice A is scheduled by the distributed network scheduling service, event 1 is processed, and event 2 is generated. Super microservice A can write event 2 into the context database for reading by the distributed network scheduling service and other super microservices. Super microservice A can also notify the distributed network scheduling service of the message of event 2. The distributed network scheduling service schedules the service decision algorithm of super microservice C based on the scheduling chain 2 shown in FIG. 5, matches the information of event 2, and the matching result is successful. Then the distributed network scheduling service schedules super microservice C through step S2c, and informs super microservice C that event 2 has occurred.

[0160] In summary, in the method 400, the first module is a module of a consumption event, i.e., a module that needs to be processed based on the event, such as a hyper-service that provides a new service. The second module is a module that generates an event, such as a module that provides a basic access service of a mobile network. After the basic access service generates a first event, the distributed network scheduling service is notified through the second information, and the distributed network scheduling service determines whether the hyper-service needs to be notified based on the first rule associated with the hyper-service. If the first event meets the first rule, the distributed network scheduling service can schedule the hyper-service, i.e., send the third information to the hyper-service to notify the hyper-service that the first event has been generated, so that the hyper-service performs subsequent processing based on the first event. As can be seen, in the method 400, the basic access service does not need to schedule the hyper-service to complete the event notification between the hyper-service and the basic access service, and the online or update of the new service will not affect the basic access service, thereby being able to meet the demand for rapid innovation capability on the basis of maintaining the stability of the basic mobile network.

[0161] The following describes a communication method provided by some embodiments of the present application.

[0162] As shown in FIG. 7, the method 700 includes the following.

[0163] S701, the basic access service sends an event registration message to the distributed network scheduling service.

[0164] Taking 5G as an example, the basic access service can be AMF or SMF, and the new service implements an extended function based on the basic access service. The event registration message includes an event ID and a service type ID. The service type ID is used to indicate the basic access service, and the event ID is used to indicate an event supported by the basic access service.

[0165] After receiving the event registration message, the distributed network scheduling service records the event supported by the basic access service locally, and provides a corresponding event subscription capability to the hyper-service.

[0166] For example, the event ID included in the event registration message is event ID1, and the service type ID included in the event registration message is SMF. The event subscription function provided by the distributed network scheduling service for the hyper-service is the event ID1 generated by the SMF.

[0167] S702, the distributed network scheduling service sends an event registration confirmation message to the basic access service.

[0168] The event registration confirmation message indicates that the event registration is successful.

[0169] S703, the hyper-service sends a service registration message to the distributed network scheduling service.

[0170] Taking 5G as an example, the super micro service can be a 5G LAN service. The service registration message can include: a service type ID, service image information, and information of resources required for service running. The service type ID is used to indicate the super micro service; the service image information includes an image name and an image warehouse address, and is used to indicate software resources required for deploying the super micro service; and the information of resources required for service running includes information of resources such as a processor, memory, network, and runtime. These parameters in the service registration message are used for deploying the super micro service, and can be referred to as deployment parameters.

[0171] S704, the distributed network scheduling service sends a service registration confirmation message to the super micro service.

[0172] The service registration confirmation message indicates that the service registration is successful.

[0173] S705, the super micro service sends a business decision algorithm registration message to the distributed network scheduling service.

[0174] The business decision algorithm registration message can include: an event ID, a service type ID, and a business decision algorithm. The event ID indicates an event associated with the business decision algorithm, the service type ID indicates a super micro service associated with the business decision algorithm, and the business decision algorithm indicates a trigger condition of event notification. The business decision algorithm can be the matching rule and / or the executable code described above.

[0175] S706, the distributed network scheduling service sends a business decision algorithm registration confirmation message to the super micro service.

[0176] The business decision algorithm registration confirmation message indicates that the business decision algorithm registration is successful.

[0177] S707, the super micro service sends an event subscription message to the distributed network scheduling service.

[0178] The event subscription message can include: an event ID, a service type ID, and operation mode indication information. The event ID indicates an event subscribed by the super micro service, the service type ID indicates the super micro service, and the operation mode indication information indicates whether the event notification mode is synchronous notification or asynchronous notification.

[0179] S708, the distributed network scheduling service sends an event subscription confirmation message to the super micro service.

[0180] The event subscription confirmation message indicates that the event subscription is successful.

[0181] For event notification, the distributed network scheduling service can adopt an asynchronous notification mode or a synchronous notification mode to notify the super micro service that the event subscribed by the super micro service has occurred. The asynchronous notification mode is shown in S709-S712, and the synchronous notification mode is shown in S713-S716.

[0182] S709, the basic access service sends an event notification message to the distributed network scheduling service.

[0183] The event notification message can include an event ID and event information, for example, the event ID indicates a first event, the event information includes user identification and session identification and other information, and extension information related to the event. The distributed network scheduling service can determine whether the hypermicro service subscribes to the first event according to a local event subscription list; if the hypermicro service subscribes to the first event, the distributed network scheduling service can determine whether the first event meets a business decision algorithm associated with the hypermicro service; if the first event meets the matching rule of the business decision algorithm, the distributed network scheduling service can perform the following steps.

[0184] S710, the distributed network scheduling service sends an event notification confirmation message to the basic access service.

[0185] The distributed network scheduling service can send the event notification confirmation message to the basic access service immediately after receiving the event notification message, without relying on S711.

[0186] S711, the distributed network scheduling service sends an event notification message to the hypermicro service.

[0187] When the distributed network scheduling service performs S711, if an entity implementing a business function in the hypermicro service already exists, the distributed network scheduling service can directly schedule the entity implementing the business function in the hypermicro service to send the event notification message; if the entity implementing the business function in the hypermicro service does not exist, the distributed network scheduling service can deploy the entity implementing the business function in the hypermicro service according to the deployment parameters in the service registration message, and schedule the entity implementing the business function in the hypermicro service after deployment is completed to send the event notification message.

[0188] S712, the hypermicro service sends an event notification confirmation message to the distributed network scheduling service.

[0189] The event notification confirmation message indicates that the event notification message has been received. The hypermicro service can process the first event based on the event notification message, and trigger subsequent business processing.

[0190] S713, the basic access service sends an event notification message to the distributed network scheduling service.

[0191] S713 is the same as S709, and will not be described again.

[0192] S714, the distributed network scheduling service sends an event notification message to the hypermicro service.

[0193] When the distributed network scheduling service executes S714, if the entity for implementing the business function in the hyper micro service already exists, the distributed network scheduling service can directly schedule the entity for implementing the business function in the hyper micro service and send the event notification message; if the entity for implementing the business function in the hyper micro service does not exist, the distributed network scheduling service can deploy the entity for implementing the business function in the hyper micro service according to the deployment parameter in the service registration message, and schedule the entity for implementing the business function in the hyper micro service and send the event notification message after the deployment is completed.

[0194] S715, the hyper micro service sends an event notification confirmation message to the distributed network scheduling service.

[0195] The event notification confirmation message indicates that the event notification message has been received. The hyper micro service can process the first event based on the event notification message and trigger subsequent business processing.

[0196] S716, the distributed network scheduling service sends an event notification confirmation message to the underlying access business.

[0197] The distributed network scheduling service can send the event notification confirmation message to the underlying access business only after receiving the event notification confirmation message of the hyper micro service. If the event notification confirmation message of the hyper micro service carries some reason values, the distributed network scheduling service can instruct the underlying access business to perform specific processing based on these reason values.

[0198] For example, if the reason value carried by the event notification confirmation message of the hyper micro service indicates that the session creation fails, the distributed network scheduling service can instruct the underlying access business to delete the corresponding session.

[0199] As can be known from the method 700, due to the introduction of the distributed network scheduling service, after the event required by the hyper micro service is generated, the underlying access business does not need to schedule the hyper micro service, and the online or function update of the hyper micro service does not affect the function of the underlying access business, thereby realizing the rapid online and deployment of the hyper micro service.

[0200] Next, taking the hyper micro service as a 5G LAN service and the underlying access business as an SMF as an example, a communication method example is further given.

[0201] As shown in FIG. 8, the method 800 includes the following contents.

[0202] S801, the 5G LAN service and the distributed network scheduling service complete the service registration process.

[0203] The 5G LAN service can register its service type ID to the distributed network scheduling service and indicate its deployment parameter. The specific service registration process can refer to S703 and S704, which will not be described herein.

[0204] S802, the 5G LAN service and the distributed network scheduling service complete an event subscription process.

[0205] The event of the 5G LAN service subscription can be a session creation success event of the SMF, wherein the event registration process between the SMF and the distributed network scheduling service has been completed, and the distributed network scheduling service has the capability to provide event subscription for the 5G LAN service. The specific event subscription process can refer to S707 and S708, and will not be described herein.

[0206] S803, the 5G LAN service and the distributed network scheduling service complete a service decision algorithm registration process.

[0207] The 5G LAN service can instruct the distributed network scheduling service to read the user context and subscription data of the SMF from the context database in the service decision algorithm registration process. The specific service decision algorithm registration process can refer to S705 and S706, and will not be described herein.

[0208] S804, the terminal and the SMF complete session creation.

[0209] The SMF can write the session-related user context and subscription data and the like into the context database.

[0210] S805, the SMF and the distributed network scheduling service complete a session creation success notification process.

[0211] The SMF sends a session creation success notification message to the distributed network scheduling service, and the distributed network scheduling service sends a session creation success confirmation message to the SMF, indicating that the notification message has been received.

[0212] S806, the distributed network scheduling service performs service decision.

[0213] For example, the event ID in the session creation success notification message indicates a first event, and the 5G LAN service subscribes to the first event. Then, the distributed network scheduling service can call the service decision algorithm registered by the 5G LAN service, execute the service decision algorithm to process the user context information and the like read from the context database, and determine whether to schedule the 5G LAN service. If the execution result of the service decision algorithm indicates that the session needs to be subjected to 5G LAN service, the distributed network scheduling service determines to schedule the 5G LAN service.

[0214] S807, the distributed network scheduling service performs service deployment.

[0215] After the distributed network scheduling service determines to schedule the 5G LAN service, the distributed network scheduling service can query the NRF whether the 5G LAN service (an entity implementing a service function in the 5G LAN service) has been deployed. If the query result is that the 5G LAN service has not been deployed, the distributed network scheduling service can select a deployment location of the 5G LAN service according to the deployment parameters obtained in S801, obtain the image of the 5G LAN service from the software image warehouse, and perform service deployment.

[0216] In S808, the 5G LAN service completes the service registration process with the NRF.

[0217] After the 5G LAN service is online, the 5G LAN service registers service information with the NRF to support topology discovery function. After successful registration, the NRF can send a registration confirmation message to the 5G LAN service to indicate that the registration is successful.

[0218] In S809, the distributed network scheduling service sends a session creation success message to the 5G LAN service.

[0219] The distributed network scheduling service can query the NRF again whether the 5G LAN service has been deployed. If the query result is that the 5G LAN service has been deployed, the distributed network scheduling service can send a session creation success message to the 5G LAN service to indicate that the session associated with the first event is created.

[0220] In S810, the 5G LAN service sends a session creation success confirmation message to the distributed network scheduling service.

[0221] The session creation success confirmation message indicates that the 5G LAN service receives the session creation success message.

[0222] In S811, the 5G LAN service completes the session modification process with the SMF.

[0223] The 5G LAN service performs services related to the service, for example, the 5G LAN service can send a message to the SMF to modify the N4 session (i.e., the 5G LAN group session) to request the SMF to modify the N4 session. After receiving the message, the SMF can send a packet forwarding control protocol (PFCP) message to the UPF to request the UPF to modify the N4 session. The UPF can forward an N4 session modification completion message to the SMF after the N4 session modification is completed. Subsequently, the SMF can send an N4 session modification completion message to the 5G LAN service to indicate that the N4 session modification is completed.

[0224] In the method 800, after the event required by the 5G LAN service is generated, the SMF does not need to schedule the 5G LAN service, and thus the online of the 5G LAN service does not affect the function of the SMF, achieving the rapid online and on-demand deployment of the 5G LAN service.

[0225] Next, taking the ultra micro service as the 5G LAN service and the basic access service as the SMF as an example, a communication method example is further given.

[0226] As shown in FIG. 9, the method 900 includes the following.

[0227] S901, the 5G LAN service and the distributed network scheduling service complete a service registration process.

[0228] S902, the 5G LAN service and the distributed network scheduling service complete an event subscription process.

[0229] S903, the 5G LAN service and the distributed network scheduling service complete a business decision algorithm registration process.

[0230] S904, the terminal and the SMF complete session creation.

[0231] S905, the SMF and the distributed network scheduling service complete a session creation success notification process.

[0232] S906, the distributed network scheduling service performs business decision.

[0233] S901-S906 can be performed with reference to S801-S806, and will not be described in detail.

[0234] S907, the distributed network scheduling service performs service discovery.

[0235] After the distributed network scheduling service determines to schedule the 5G LAN service, the distributed network scheduling service can query the NRF whether the 5G LAN service (an entity implementing a business function in the 5G LAN service) has been deployed, and if the query result is that the 5G LAN service has been deployed, the distributed network scheduling service can perform the following steps.

[0236] S908, the distributed network scheduling service sends a session creation success message to the 5G LAN service.

[0237] For example, the session creation success message indicates that the session associated with the first event is created.

[0238] S909, the 5G LAN service sends a session creation success confirmation message to the distributed network scheduling service.

[0239] The session creation success confirmation message indicates that the 5G LAN service receives the session creation success message.

[0240] S910, the 5G LAN service and the SMF complete a session modification procedure.

[0241] S910 can be performed with reference to S811, and details are not repeated.

[0242] In the method 900, after the event required by the 5G LAN service occurs, the SMF does not need to schedule the 5G LAN service, and therefore, the function update of the 5G LAN service does not affect the function of the SMF, and the rapid update of the 5G LAN service is achieved.

[0243] Next, taking the ultra micro service as the 5G LAN service and the multimedia broadcast multicast service (MBMS), and taking the basic access service as the SMF as an example, a communication method example is further given.

[0244] As shown in FIG. 10, the method 1000 includes the following.

[0245] S101a, the 5G LAN service and the distributed network scheduling service complete a service registration procedure, an event subscription procedure, and a service decision algorithm registration procedure.

[0246] S102a, the MBMS and the distributed network scheduling service complete a service registration procedure, an event subscription procedure, and a service decision algorithm registration procedure.

[0247] S101a and S102a can be performed with reference to S801-S803, and details are not repeated. The event registration procedure between the SMF and the distributed network scheduling service has been completed, and the distributed network scheduling service has the capability of providing event subscription to the 5G LAN service and the MBMS. The execution order of S101a and S102a in the method 1000 is not limited, and S101a and S102a can be executed simultaneously or sequentially.

[0248] S101b, the terminal and the SMF complete creation of session 1.

[0249] S101c, the SMF and the distributed network scheduling service complete a session creation success notification procedure.

[0250] For example, after the SMF writes the data related to the session 1 into the context database, the SMF sends a session 1 creation success notification message to the distributed network scheduling service. After receiving the notification message, the distributed network scheduling service sends a session 1 creation success confirmation message to the SMF, indicating that the notification message has been received.

[0251] S101d, the distributed network scheduling service executes the service decision algorithm associated with the 5G LAN service.

[0252] For example, the event ID in the session 1 creation success notification message indicates the first event, the 5G LAN service subscribes to the first event, and then the distributed network scheduling service can call the business decision algorithm registered by the 5G LAN service, and process the data such as reading the user context information from the context database to determine whether to schedule the 5G LAN service. If the execution result of the business decision algorithm indicates that the session needs to perform 5G LAN service, the distributed network scheduling service determines to schedule the 5G LAN service.

[0253] S101e, the distributed network scheduling service performs service deployment.

[0254] After the distributed network scheduling service determines to schedule the 5G LAN service, the distributed network scheduling service can query the NRF whether the 5G LAN service (an entity implementing a business function in the 5G LAN service) has been deployed. If the query result is not deployed, the distributed network scheduling service can select a deployment location of the 5G LAN service according to the deployment parameters obtained in S101a, obtain the image of the 5G LAN service from the software image warehouse, and perform service deployment.

[0255] S101f, the 5G LAN service and the NRF complete the service registration process.

[0256] After the 5G LAN service is online, the 5G LAN service registers service information to the NRF to support topology discovery function. After successful registration, the NRF can send a registration confirmation message to the 5G LAN service to indicate that the registration is successful.

[0257] S101g, the 5G LAN service and the distributed network scheduling service complete the session creation success notification process.

[0258] The distributed network scheduling service can query the NRF again whether the 5G LAN service has been deployed. If the query result is that the 5G LAN service has been deployed, the distributed network scheduling service can send a session creation success message to the 5G LAN service to indicate that the session 1 associated with the first event is created. The 5G LAN service can send a session creation success confirmation message to the distributed network scheduling service to indicate that the 5G LAN service receives the session creation success message.

[0259] S101h, the 5G LAN service and the SMF complete the session modification process.

[0260] S101h can be performed with reference to S811, and will not be described again.

[0261] S102b, the terminal and the SMF complete the creation of session 2.

[0262] S102c, the SMF and the distributed network scheduling service complete the session creation success notification process.

[0263] For example, after the SMF writes the session 2 related data into the context database, the SMF sends a session 2 creation success notification message to the distributed network scheduling service, and after the distributed network scheduling service receives the notification message, the distributed network scheduling service sends a session 2 creation success confirmation message to the SMF, indicating that the notification message has been received.

[0264] S102d, the distributed network scheduling service executes the MBMS associated service decision algorithm.

[0265] For example, the event ID in the session 2 creation success notification message indicates the first event, and the MBMS subscribes to the first event. Then, the distributed network scheduling service can call the MBMS registered service decision algorithm, and process the user context information and other data read from the context database by using the service decision algorithm to determine whether to schedule the MBMS. If the service decision algorithm execution result indicates that the session needs to be subjected to the MBMS service, the distributed network scheduling service determines to schedule the MBMS.

[0266] S102e, the distributed network scheduling service executes service deployment.

[0267] After the distributed network scheduling service determines to schedule the MBMS, the distributed network scheduling service can query the NRF whether the MBMS (an entity implementing the service function in the MBMS) has been deployed. If the query result is not deployed, the distributed network scheduling service can select a deployment location of the MBMS according to the deployment parameter obtained in S101b, obtain the image of the MBMS from the software image warehouse, and execute service deployment.

[0268] S102f, the MBMS and the NRF complete the service registration process.

[0269] After the MBMS is online, the MBMS registers service information to the NRF, and supports topology discovery function. After the registration is successful, the NRF can send a registration confirmation message to the MBMS, indicating that the registration is successful.

[0270] S102g, the MBMS and the distributed network scheduling service complete the session creation success notification process.

[0271] The distributed network scheduling service can query the NRF again whether the MBMS has been deployed. If the query result is that the MBMS has been deployed, the distributed network scheduling service can send a session creation success message to the MBMS, indicating that the session 2 associated with the first event is created successfully. The MBMS can send a session creation success confirmation message to the distributed network scheduling service, indicating that the MBMS receives the session creation success message.

[0272] S102h, the MBMS and a multicast / broadcast session management function (MB-SMF) complete a join broadcast session procedure.

[0273] The MBMS can send a join broadcast session request message to the MB-SMF, requesting to add session 2 to the broadcast session group. After adding session 2 to the broadcast session group, the MB-SMF can send a join broadcast session group confirmation message to the MBMS, indicating that session 2 has been added to the broadcast session group.

[0274] S102i, the MBMS and the terminal complete a broadcast session join success notification procedure.

[0275] The MBMS can send a broadcast session join success message to the terminal, indicating that session 2 has been added to the broadcast session group. The terminal can send a response message to the MBMS, indicating that the broadcast session join success message has been received.

[0276] In the method 1000, although the 5G LAN service and the MBMS subscribe to the same event, the service decision algorithm of the 5G LAN service and the MBMS is independent, and therefore, the execution of S101a-S101h and the execution of S102a-S102i are not dependent. Alternatively, the 5G LAN service and the MBMS can also subscribe to different events.

[0277] In the method 1000, after the event required by the 5G LAN service and the MBMS is generated, the SMF does not need to schedule the 5G LAN service and the MBMS, and therefore, the online of the 5G LAN service and the MBMS does not affect the function of the SMF, realizing the rapid online and on-demand deployment of the 5G LAN service and the MBMS.

[0278] Next, taking two ultra microservices with a dependency relationship as an example, a communication method example is further given.

[0279] As shown in FIG. 11, the method 1100 includes the following.

[0280] S1101, the ultra microservice A and the distributed network scheduling service complete a service registration procedure, an event subscription procedure and a service decision algorithm registration procedure.

[0281] S1102, the ultra microservice B and the distributed network scheduling service complete a service registration procedure, an event subscription procedure and a service decision algorithm registration procedure.

[0282] S1101 and S1102 can be performed with reference to S801-S803, which will not be described herein again, wherein the event registration process between the basic access service and the distributed network scheduling service has been completed, and the distributed network scheduling service has the capability of providing event subscription to the hyper micro service A and the hyper micro service B. The execution sequence of S1101 and S1102 is not limited by the method 1100, and S1101 and S1102 can be executed simultaneously or sequentially.

[0283] S1103, the terminal and the basic access service complete the creation of a session.

[0284] S1104, the basic access service and the distributed network scheduling service complete the session creation success notification process.

[0285] For example, after the basic access service writes the data related to the session 1 into the context database, the basic access service sends a session 1 creation success notification message to the distributed network scheduling service. After receiving the notification message, the distributed network scheduling service sends a session 1 creation success confirmation message to the basic access service, indicating that the notification message has been received.

[0286] S1105, the distributed network scheduling service executes the business decision algorithm associated with the hyper micro service A.

[0287] For example, the event ID in the session 1 creation success notification message indicates the first event, and the hyper micro service A subscribes to the first event. Therefore, the distributed network scheduling service can call the business decision algorithm registered by the hyper micro service A, and process the data such as user context information read from the context database by using the business decision algorithm to determine whether to schedule the hyper micro service A. If the execution result of the business decision algorithm indicates that the session needs to perform the hyper micro service A related business, the distributed network scheduling service determines to schedule the hyper micro service A.

[0288] S1106, the distributed network scheduling service performs service deployment.

[0289] After the distributed network scheduling service determines to schedule the hyper micro service A, the distributed network scheduling service can query the NRF to determine whether the hyper micro service A (an entity implementing a business function in the hyper micro service A) has been deployed. If the query result is not deployed, the distributed network scheduling service can select a deployment location of the hyper micro service A according to the deployment parameter obtained in S1101, obtain the image of the hyper micro service A from the software image warehouse, and perform service deployment.

[0290] S1107, the hyper micro service A and the NRF complete the service registration process.

[0291] After the hyper micro service A is online, the hyper micro service A registers service information to the NRF to support the topology discovery function. After successful registration, the NRF can send a registration confirmation message to the hyper micro service A, indicating that the registration is successful.

[0292] S1108, the ultra microservice A and the distributed network scheduling service complete a session creation success notification process.

[0293] The distributed network scheduling service can query again whether the ultra microservice A is deployed from the NRF, and if the query result is that the ultra microservice A is deployed, the distributed network scheduling service can send a session creation success message to the ultra microservice A, indicating that the session 1 associated with the first event is created. The ultra microservice A can send a session creation success confirmation message to the distributed network scheduling service, indicating that the ultra microservice A receives the session creation success message.

[0294] S1109, the ultra microservice A and the network function (NF) 1 complete service 1 processing.

[0295] The NF 1 can be a network element related to the service 1, and the ultra microservice A can send a request message to the NF 1, requesting to process the service 1 related to the session 1. After the NF 1 processes the service 1, the NF 1 can send a response message to the ultra microservice A, indicating that the service 1 has been processed. The NF 1 and the ultra microservice A can write the data related to the service 1 into the context database.

[0296] S1110, the ultra microservice A and the distributed network scheduling service complete a service 1 processing completion notification process.

[0297] After the ultra microservice A writes the data related to the service 1 into the context database, the ultra microservice A can send a notification message to the distributed network scheduling service, indicating that the service 1 has been processed. The distributed network scheduling service can send a response message to the ultra microservice A, indicating that the notification message has been received.

[0298] S1111, the distributed network scheduling service executes a service decision algorithm associated with the ultra microservice B.

[0299] For example, the data related to the service 1 includes a second event to which the ultra microservice B subscribes. The distributed network scheduling service can call the service decision algorithm registered by the ultra microservice B, process the data related to the second event read from the context database, and determine whether to schedule the ultra microservice B. If the execution result of the service decision algorithm indicates that the session needs to perform the service related to the ultra microservice B, the distributed network scheduling service determines to schedule the ultra microservice B.

[0300] S1112, the distributed network scheduling service executes service deployment.

[0301] After determining to schedule the microservice B, the distributed network scheduling service can query the NRF whether the microservice B (an entity implementing a service function in the microservice B) has been deployed. If the query result is that the microservice B has not been deployed, the distributed network scheduling service can select a deployment location of the microservice B according to the deployment parameter obtained in S1102, obtain an image of the microservice B from a software image warehouse, and perform service deployment.

[0302] In S1113, the microservice B completes a service registration process with the NRF.

[0303] After the microservice B is online, the microservice B registers service information with the NRF to support a topology discovery function. After successful registration, the NRF can send a registration confirmation message to the microservice B to indicate that the registration is successful.

[0304] In S1114, the microservice B completes a service 1 processing completion notification process with the distributed network scheduling service.

[0305] The distributed network scheduling service can again query the NRF whether the microservice B has been deployed. If the query result is that the microservice B has been deployed, the distributed network scheduling service can send a service 1 processing completion notification message to the microservice B to indicate that the service 1 processing is completed (or to indicate that a second event has occurred). The microservice B can send a response message to the distributed network scheduling service to indicate that the microservice B has received the notification message.

[0306] In S1115, the microservice B completes service 2 processing with the NF2.

[0307] The NF2 can be a network element related to the service 2. The microservice B can send a request message to the NF2 to request processing of the service 2 related to the session 1. After processing the service 2, the NF2 can send a response message to the microservice B to indicate that the service 2 has been processed. The NF2 and the microservice B can write data related to the service 2 into the context database.

[0308] In S1116, the microservice B completes a service 2 processing completion notification process with the distributed network scheduling service.

[0309] After writing the data related to the service 2 into the context database, the microservice B can send a notification message to the distributed network scheduling service to indicate that the service 2 has been processed. The distributed network scheduling service can send a response message to the microservice B to indicate that the notification message has been received.

[0310] In the method 1100, the events to which the microservice A and the microservice B subscribe have a dependency relationship. Therefore, the execution of S1111 depends on the execution of S1110, and the distributed network scheduling service can perform chain scheduling on the related microservices based on the dependency relationship.

[0311] After the event required by the hyper microservice A and the hyper microservice B is generated, the basic access service does not need to schedule the hyper microservice A and the hyper microservice B, and therefore, the online of the hyper microservice A and the hyper microservice B does not affect the function of the basic access service, and the rapid online and on-demand deployment of the hyper microservice A and the hyper microservice B are achieved.

[0312] The method examples provided by the embodiments of the application are described in detail above, and it can be understood that the corresponding apparatuses contain the corresponding hardware structures and / or software modules for implementing the functions. Those skilled in the art should easily realize that the units and algorithm steps of each example described in combination with the embodiments disclosed in the present text can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is implemented in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. The skilled person can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0313] FIG. 12 and FIG. 13 are structural schematic diagrams of two communication apparatuses provided by the embodiments of the application, which can be used to implement the functions of the first module, the second module or the third module in the method embodiments described above, and therefore, also have the beneficial effects of the method embodiments described above.

[0314] As shown in FIG. 12, the communication apparatus 1200 includes a processing unit 1210 and a transceiver unit 1220. The transceiver unit 1220 performs the receiving step and / or the output step under the control of the processing unit 1210, wherein the transceiver unit 1220 is a transmitting unit when performing the output step (or, the transmitting step), and the transceiver unit 1220 is a receiving unit when performing the receiving step. The communication apparatus 1200 is used to implement the functions of the first module, the second module or the third module in the method embodiments described in FIG. 4.

[0315] When the communication apparatus 1200 is used to implement the function of the third module in the method embodiments described in FIG. 4, the transceiver unit 1220 is configured to: receive first information, the first information indicating a first rule of the first module; receive second information from the second module, the second information indicating that a first event has been generated; and transmit third information to the first module when the first event meets the first rule, the third information indicating that the first event has been generated.

[0316] Optionally, the transceiver unit 1220 is further configured to: receive fourth information, the fourth information indicating an association relationship between the first rule and the first event; and the processing unit 1210 is configured to: determine whether the first event meets the first rule according to the fourth information.

[0317] Optionally, the transceiver 1220 is further configured to receive fifth information from the second module, the fifth information indicating events supported by the second module, the events supported by the second module including the first event.

[0318] Optionally, the transceiver 1220 is further configured to receive sixth information, the sixth information indicating that the first module subscribes to the first event; and the processing unit 1210 is configured to determine whether the first event meets the first rule according to the sixth information.

[0319] Optionally, the transceiver 1220 is further configured to receive seventh information, the seventh information indicating deployment parameters of the first module; and the processing unit 1210 is configured to deploy the first module according to the seventh information.

[0320] Optionally, the first information includes a matching rule of at least one information in the first event; and / or the first information includes a first code, the first code being used to determine whether the first event meets the first rule.

[0321] Optionally, the processing unit 1210 is configured to determine not to send third information to the first module when the first event does not meet the first rule, the third information indicating that the first event has occurred.

[0322] When the communication apparatus 1200 is configured to implement the function of the first module in the method embodiment shown in FIG. 4, the transceiver 1220 is configured to send first information to a third module, the first information indicating a first rule of the first module; and receive third information from the third module, the third information indicating that a first event has occurred, the first event being an event meeting the first rule.

[0323] Optionally, the transceiver 1220 is further configured to send fourth information to the third module, the fourth information indicating an association between the first rule and the first event.

[0324] Optionally, the transceiver 1220 is further configured to send sixth information to the third module, the sixth information indicating that the first module subscribes to the first event.

[0325] Optionally, the transceiver 1220 is further configured to send seventh information to the third module, the seventh information indicating deployment parameters of the first module.

[0326] Optionally, the first information includes a matching rule of at least one information in the first event; and / or the first information includes a first code, the first code being used to determine whether the first event meets the first rule.

[0327] Optionally, the transceiver 1220 is further configured to send eighth information to a service registration module after the first module is deployed, the eighth information indicating a service of the first module.

[0328] When the communication apparatus 1200 is used to implement the function of the second module in the method embodiment in FIG. 4, the processing unit 1210 is configured to determine a first event; and the transceiver 1220 is configured to send second information to the third module, the second information indicating that the first event has occurred, and the second information being used by the third module to send third information to the first module, wherein the third module sends the third information to the first module when the first event satisfies the first rule of the first module, and the third information indicates that the first event has occurred.

[0329] Optionally, the transceiver 1220 is further configured to send fifth information to the third module, the fifth information indicating events supported by the second module, and the events supported by the second module including the first event.

[0330] The communication apparatus 1200 can be a cloud computing infrastructure, or the communication apparatus 1200 can be a chip applied to the cloud computing infrastructure. The processing unit 1210 can be implemented by hardware or software. When implemented by hardware, the processing unit 1210 is a logic circuit, an integrated circuit, or the like. When implemented by software, the processing unit 1210 can be a general-purpose processor, which reads software codes stored in a storage unit to implement the processing unit 1210. The storage unit can be integrated in the processing unit 1210 or exist independently.

[0331] As shown in FIG. 13, the communication apparatus 1300 includes a processor 1310 and an interface circuit 1320. The processor 1310 and the interface circuit 1320 are coupled to each other. It can be understood that the interface circuit 1320 can be a transceiver or an input / output interface. Optionally, the communication apparatus 1300 can further include a memory 1330, which is used to store instructions executed by the processor 1310 or store input data required by the processor 1310 to run instructions or store data generated after the processor 1310 runs instructions.

[0332] When the communication apparatus 1300 is used to implement the method shown in FIG. 4, the processor 1310 is configured to implement the functions of the processing unit 1210, and the interface circuit 1320 is configured to implement the functions of the transceiver 1220.

[0333] When the communication apparatus 1300 is a chip applied to a cloud computing infrastructure, the chip implements the functions of the first module, the second module, or the third module in the above method embodiments. The chip receives information from other modules, which can be understood as that the information is first received by a transceiver module (such as a transceiver circuit or a software interface) in the cloud computing infrastructure, and then transmitted to the chip by the transceiver module. The chip sends information to other modules, which can be understood as that the information is first sent to a transceiver module (such as a transceiver circuit or a software interface) in the cloud computing infrastructure, and then transmitted to other modules by the transceiver module.

[0334] In the present application, the sending of information from entity A to entity B can be directly from A to B, or indirectly from A to B via other entities. Similarly, the receiving of information from entity A by entity B can be directly from A to B, or indirectly from A to B via other entities. The entities A and B can be network elements or modules within network elements. The sending and receiving of information can be the exchange of information between network elements, such as the exchange of information between a super micro service and a distributed network scheduling service. The sending and receiving of information can also be the exchange of information between different modules within a device, such as the exchange of information between different modules within a distributed network scheduling service when the service executes a business decision algorithm.

[0335] It can be understood that the processor in the embodiments of the present application can be a central processing unit (CPU) or a system on chip (SoC), and can also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. The general-purpose processor can be a microprocessor or any conventional processor.

[0336] The method steps in the embodiments of the present application can be implemented in hardware or in software instructions executable by a processor. The software instructions can be composed of corresponding software modules, which can be stored in a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an erasable programmable read-only memory, an electrically erasable programmable read-only memory, a register, a hard disk, a mobile hard disk, a compact disc read-only memory (CD-ROM) or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor, so that the processor can read information from and write information to the storage medium. The storage medium can also be an integral part of the processor. The processor and the storage medium can be located in an ASIC. In addition, the ASIC can be located in a base station or a terminal. The processor and the storage medium can also exist as discrete components in a base station or a terminal.

[0337] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer programs or instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments are performed. The computer can be a general purpose computer, a special purpose computer, a computer network, a network device, a user equipment or other programmable apparatus. The computer programs or instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer programs or instructions can be transferred from one website site, computer, server or data center to another website site, computer, server or data center through wired or wireless manner. The computer readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center and the like integrated with one or more available media. The available media can be a magnetic medium, such as a floppy disk, a hard disk, a magnetic tape; or an optical medium, such as a digital video disc; or a semiconductor medium, such as a solid state disk. The computer readable storage medium can be a volatile or non-volatile storage medium, or can include both volatile and non-volatile storage media.

[0338] Finally, regarding the embodiments of the present application, the following points are explained:

[0339] First, in the embodiments of the present application, the first, second and various numerical numbers are distinguished for convenience of description, and do not limit the scope of the embodiments of the present application. The size of the serial number of the above processes does not mean the order of execution, and the execution order of the processes should be determined by its function and inherent logic.

[0340] Second, in the embodiments of the present application, "indication" can include direct indication and indirect indication, and can also include explicit indication and implicit indication. The information indicated by a certain information is called to be indicated information, and there are many ways to indicate the to-be-indicated information in the specific implementation process, for example, the to-be-indicated information can be directly indicated, such as the to-be-indicated information itself or the index of the to-be-indicated information. The to-be-indicated information can also be indirectly indicated by indicating other information, wherein the other information and the to-be-indicated information have an association relationship. A part of the to-be-indicated information can also be indicated, and the other part of the to-be-indicated information is known or agreed in advance, for example, whether a certain information element exists can be used to indicate the to-be-indicated information by means of pre-agreement (for example, agreement), thereby reducing the indication overhead to a certain extent.

[0341] Thirdly, the "protocol" involved in the embodiments of the present application can refer to a standard protocol in the communication field, which can include a long term evolution (LTE) protocol, an NR protocol, and a related protocol in a future communication system, and the present application does not make any limitation thereon.

[0342] Fourthly, the "predefined" or "preconfigured" can be implemented by pre-storing a corresponding code, table or other information indicating related information in a device (for example, a terminal or a base station), and the present application does not make any limitation on the specific implementation manner. Wherein, the "storing" can refer to storing in one or more memories, which can be separately arranged or integrated in a processor or a communication device; the one or more memories can be partially separately arranged and partially integrated in the processor or the communication device. The type of the memory can be any form of storage medium, and the present application does not make any limitation thereon.

[0343] Fifthly, "at least one" refers to one or more, and "multiple" refers to two or more. The "and / or" describes the association relationship of the associated objects, which means that there can be three kinds of relationships, for example, A and / or B can represent: A exists alone, B exists alone, and A and B exist at the same time, wherein A and B can be a single object or multiple objects. The character " / " generally represents an "or" relationship between the front and rear associated objects. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single item or multiple items. For example, at least one of a, b and c can represent: a, or b, or c, or a and b, or a and c, or b and c, or a, b and c. Wherein a, b and c can be a single object or multiple objects.

[0344] Sixthly, in the embodiments of the present application, the descriptions such as "when", "in the case of", "if" and "if" all refer to the objective situation that the device (for example, a terminal or a base station) will make corresponding processing, which is not limited by time, and does not require the device to have a judgment action when implemented, nor means that there are other limitations.

[0345] Seventhly, in various embodiments of the present application, the terms and / or descriptions of different embodiments are consistent and can be mutually referenced if there is no special description and logical conflict, and the technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationship.

Claims

1. A communication method characterized by comprising: The method comprises: receiving first information, the first information indicating a first rule of a first module; receiving second information from a second module, the second information indicating that a first event has occurred; when the first event meets the first rule, sending third information to the first module, the third information indicating that the first event has occurred.

2. The method of claim 1, wherein, The method further comprises: receiving fourth information, the fourth information indicating an association relationship between the first rule and the first event; determining whether the first event meets the first rule according to the fourth information.

3. The method according to claim 1 or 2, characterized in that, The method further comprises: receiving fifth information from the second module, the fifth information indicating events supported by the second module, the events supported by the second module including the first event.

4. The method according to any one of claims 1 to 3, characterized in that, The method further comprises: receiving sixth information, the sixth information indicating that the first module subscribes to the first event; determining whether the first event meets the first rule according to the sixth information.

5. The method of any one of claims 1 to 4, wherein: the first information comprises a matching rule of at least one information in the first event; and / or the first information comprises a first code for determining whether the first event meets the first rule.

6. The method according to any one of claims 1 to 5, characterized in that, The method further comprises: when the first event does not meet the first rule, determining not to send third information to the first module, the third information indicating that the first event has occurred.

7. A communication method characterized by comprising: The method is applied to a first module, and the method comprises: sending first information to a third module, the first information indicating a first rule of the first module; receiving third information from the third module, the third information indicating that a first event has occurred, wherein the first event is an event meeting the first rule.

8. The method of claim 7, wherein, The method further comprises: sending fourth information to the third module, the fourth information indicating an association relationship between the first rule and the first event.

9. The method according to claim 7 or 8, characterized in that, The method further comprises: sending sixth information to the third module, the sixth information indicating that the first module subscribes to the first event.

10. The method of any one of claims 7 to 9, wherein: the first information comprises a matching rule of at least one information in the first event; and / or the first information comprises a first code for determining whether the first event meets the first rule.

11. A communication method, comprising: The method is applied to a second module, and the method comprises: determining a first event; sending second information to a third module, the second information indicating that the first event has occurred, the second information being used for the third module to send third information to a first module, wherein when the first event meets a first rule of the first module, the third module sends the third information to the first module, the third information indicating that the first event has occurred.

12. The method of claim 11, wherein, The method further comprises: sending fifth information to the third module, the fifth information indicating events supported by the second module, the events supported by the second module including the first event.

13. A communications device, characterized by The method comprises: A module for performing the method of any one of claims 1 to 6, or a module for performing the method of any one of claims 7 to 10, or a module for performing the method of claim 11 or 12.

14. A communications device, characterized by Comprising: a processor for implementing the method of any one of claims 1 to 6, or the method of any one of claims 7 to 10, or the method of claim 11 or 12, by logic circuitry or executing code instructions; an interface circuit for receiving signals from and transmitting signals to other devices or for transmitting signals to, and receiving signals from, other devices.

15. A communication system, characterized by Comprising: a communication device for performing the method of any one of claims 1 to 6, and a communication device for performing the method of any one of claims 7 to 10, and a communication device for performing the method of claim 11 or 12.

16. A computer-readable storage medium, characterized in that, The computer readable storage medium stores a computer program or instructions which, when executed by a communication device, implement the method of any one of claims 1 to 6, or the method of any one of claims 7 to 10, or the method of claim 11 or 12.

17. A computer program product, characterised in that, The computer program product comprises a computer program or instructions which, when executed by a communication device, implement the method of any one of claims 1 to 6, or the method of any one of claims 7 to 10, or the method of claim 11 or 12.

Images