WO2025167526A1 - Communication method and apparatus - Google Patents

Abstract

A communication method and apparatus. The method comprises: a first network element sending a first message to a third network element, wherein the first message is used for the first network element to request the recommendation of a policy corresponding to the first service; the third network element acquiring first information, wherein the first information comprises statistical information of at least one network element; and the third network element sending a first policy to the first network element on the basis of the statistical information of the at least one network element, wherein the first policy comprises the policy corresponding to the first service. The statistical information of the at least one network element comprises information of the at least one network element calling a service and/or information of a service of the at least one network element being called, and the at least one network element comprises a first network element. The method can sense services of network elements, can relieve/prevent signaling storms in a timely manner, and can improve the efficiency of relieving the signaling storms.

Description

Communication method and device

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of the People's Republic of China on February 8, 2024, with application number 202410178208.6 and application name "A Communication Method and Device", the entire contents of which are incorporated by reference into this application.

Technical Field

The present application relates to the field of communication technology, and in particular to a communication method and device.

Background Art

A network system consists of multiple functional network elements. Interactions between these elements, or between these elements and other devices, can lead to signaling storms, impacting the normal operation of these devices. For example, multiple core network elements in a network system interact with the same device. This device may experience excessive signaling overhead, leading to service interruption. Another example is when a network outage is restored and the devices whose services were interrupted request network access again, the sheer volume of simultaneous signaling requests can prevent them from accessing the network.

Currently, the control strategy for signaling storms is mainly at the network element level, which is not timely enough and has low efficiency in alleviating signaling storms.

Summary of the Invention

The embodiments of the present application provide a communication method and apparatus, which can provide a service-level control strategy for signaling storms, can timely alleviate/prevent signaling storms, and improve the efficiency of mitigating signaling storms.

To achieve the above objectives, the present invention adopts the following technical solutions:

In a first aspect, an embodiment of the present application provides a communication method that can be performed by a first communication device. The first communication device can be a combination device, component, etc. for realizing the functions of a core network network element. The first communication device can be a third network element, which has a recommendation logical function (ReLF), or the first communication device is a unit/module, circuit or chip inside the third network element. For example, the third network element is a network data analysis function (NWDAF) network element with ReLF, or the third network element can be a device that combines ReLF with the analysis logical function (AnLF) in NWDAF. The method provided in the first aspect is described below by taking the first communication device as the third network element itself as an example.

The communication method includes: a third network element receiving a first message from a first network element and obtaining first information, wherein the first message is used to request recommendation of a policy corresponding to a first service, and the first information includes statistical information of at least one network element; and the third network element sending a first policy to the first network element based on the statistical information of the at least one network element, wherein the first policy includes a policy corresponding to the first service. The statistical information of the at least one network element includes information about a service being invoked by the at least one network element and/or information about a service being invoked by the at least one network element, the at least one network element including the first network element.

The first network element is the network element requesting the prevention or mitigation of a signaling storm. When the first network element requests the prevention or mitigation of a signaling storm, it may send a first message to a third network element. Triggered by the first message, the third network element may obtain first information, which may be obtained by collecting statistics related to at least one network element, or may include statistical information about at least one network element. The statistical information/first information of the at least one network element may be used to predict or determine whether a signaling storm is occurring in the first network element. For example, the statistical information of the at least one network element may include information about the at least one network element invoking a service and/or information about the at least one network element's service being invoked. Thus, the third network element can generate a first policy based on the statistical information of the at least one network element to prevent or mitigate a signaling storm. The information about each network element invoking or being invoked can be considered service-related information for that network element, and the first policy can be considered a service-level policy. This solution is aware of the network element's services and recommends different policies based on the signaling overhead incurred by different services. Compared to signaling-level signaling storm control policies, this solution can promptly mitigate/prevent signaling storms and improve the efficiency of signaling storm mitigation.

In one implementation, the first message includes a recommendation identifier, which is a service ID requested for recommendation, so that the third network element clearly recommends the service to the first network element.

In one implementation, the first message further includes: a service scope of the first network element, identification information of the first network element, and network slice information of the first network element. Alternatively, the first message further includes: a service scope of the first network element, identification information of a set to which the first network element belongs, and network slice information of the first network element.

The above information can be understood as the attribute information of the first network element. The third network element can obtain the first information based on this information so that the first information matches the attribute information of the first network element, thereby obtaining a more appropriate first strategy.

In one implementation, the first service includes invoking a service of a second network element, and the first message further includes: information about at least one candidate network element, where the information about the at least one candidate network element is used to indicate at least one of a type, a service scope, and slice information of the at least one candidate network element. The at least one candidate network element includes the second network element, and the at least one network element includes the at least one candidate network element.

At least one network element is related to a first service. For example, the first service includes invoking a service of a second network element. The at least one network element includes at least one candidate network element as the second network element. The at least one candidate network element is at least one second network element that the first network element desires a third network element to recommend. The first network element notifies the third network element of information about the at least one candidate network element. The third network element may obtain at least one candidate network element based on the information about the at least one candidate network element, and then recommend a second network element to the first network element from the at least one candidate network element based on statistical information about the at least one network element. This solution eliminates the need to consider network elements other than the at least one candidate network element, thereby reducing processing complexity.

In one implementation, the first message further includes: identification information of at least one candidate network element.

The at least one candidate network element includes a network element that the first network element expects the third network element to recommend. The first network element notifies the third network element of the at least one candidate network element, which can reduce the need for the third network element to obtain unnecessary statistical information of network elements.

In one implementation, the first service includes calling a service of a second network element, and the method further includes: a third network element obtains at least one candidate network element serving the first network element, the at least one candidate network element includes the second network element, and the at least one network element includes at least one candidate network element.

There are multiple second network elements providing services to the first network element, and the first network element may expect one or some of the multiple second network elements to provide services. When the first network element does not provide at least one candidate network element for the third network element, in order to reduce the acquisition of statistical information of unnecessary network elements, the third network element may first determine at least one candidate network element.

In one implementation, a first message includes information about at least one candidate network element, where the information about the at least one candidate network element is used to indicate at least one of a type, a service scope, and slice information of the at least one candidate network element. Acquiring the at least one candidate network element by a third network element includes: the third network element sending a second message and receiving at least one identification information. The second message is used to request acquisition of the at least one candidate network element and may include information about the at least one candidate network element. The at least one identification information corresponds one-to-one to the at least one candidate network element, and the at least one identification information is determined based on the information about the at least one candidate network element.

Optionally, the third network element sending the second message includes the third network element sending the second message to a network repository function (NRF) network element. Because the NRF network element knows information about the second network element that can serve the first network element, when the third network element needs to obtain at least one candidate network element, it can request a candidate network element that matches the attribute information from the NRF network element.

Optionally, the third network element sending the second message includes the third network element sending the second message to other first network elements, where the other first network elements and the first network element sending the first message belong to the same set. For example, the first network element sending the first message is first network element A, and the third network element may send the second message to first network element B, where the first network element A and the second network element B have the same set identifier (ID).

In one implementation, the third network element obtains the first information, including: the third network element sends a third message to the data analysis network element, the third message is used to request the first information, and the first message includes an analysis ID to indicate the analysis service requested by the third network element. The data analysis network element may be NWDAF or AnLF in NWDAF. When the third network element is ReLF and is independent of NWDAF or AnLF, the third network element sending the third message may be the third network element sending the third message to NWDAF or AnLF. When the third network element is a NWDAF network element, the NWDAF network element includes ReLF and AnLF, and the third network element obtaining the first information may be the ReLF in NWDAF obtaining the first information from the AnLF in NWDAF. Alternatively, when the third network element is composed of ReLF and AnLF, the third network element obtaining the first information includes the third network element obtaining statistical information of at least one network element and generating the first information based on the statistical information.

In one implementation, the statistical information of the at least one network element includes one or more of the following: a rate and/or frequency of service invocation by the at least one network element within a first duration, predicted information of a rate and/or frequency of invocation of the at least one network element within the first duration, or first time information. The first time information may be used to indicate the first duration.

It is understood that the predicted rate and/or frequency of a network element being invoked over a period of time can predict the amount of signaling required to be exchanged by the network element during that period. Similarly, the rate and/or frequency of service invocations over a period of time can represent the amount of signaling exchanged by the network element during that period. The above statistical information can represent the current and/or future amount of signaling exchanged by the network element. The first policy generated by the third network element based on this statistical information can better prevent or mitigate signaling storms.

In one implementation, the first information further includes one or more of the following: prediction information of the signaling storm and an analysis ID corresponding to the first information.

The signaling storm prediction information can indicate whether a signaling storm exists or the severity of the signaling storm. In this case, the third network element can generate a matching first policy. For example, if there is no signaling storm, the first policy will minimize signaling control to ensure the normal operation of the first service. If there is a signaling storm, the first policy will control signaling to minimize the impact on the normal service of the first network element.

In one implementation, the first service includes calling a service of a second network element, and the first policy includes one or more of the following policies: a policy for selecting the second network element, a policy for calling a service of the second network element, or a policy for calling a service of the first network element.

In one implementation, the first service includes a terminal device registration service, and the first policy includes one or more of the following policies: a time interval for the terminal device to retry registration, and a policy for invoking a service of the first network element.

In a second aspect, an embodiment of the present application provides a communication method that can be performed by a second communication device. The second communication device can be a combination device, component, etc. for implementing the functions of a core network network element. The second communication device can be a first network element, such as an access and mobility management function (AMF); or the first communication device can be a unit/module, circuit, or chip inside the first network element. For example, the first network element is a unit/module, circuit, or chip in the AMF. The method provided in the second aspect is described below using the second communication device as the first network element itself as an example.

The communication method includes: a first network element sending a first message to a third network element, and receiving a first policy. The first message is used to request a recommendation of a policy corresponding to a first service. The first policy includes a policy corresponding to the first service, and the first policy is determined based on statistical information of at least one network element related to the first service. The statistical information of the at least one network element includes information about the at least one network element invoking a service and/or information about the at least one network element's service being invoked.

In one implementation, the first message includes a recommendation identifier, which is a service ID requested for recommendation.

In one implementation, the first message also includes: the service scope of the first network element, identification information of the first network element or identification information of the set to which the first network element belongs, and network slice information of the first network element.

In one implementation, the first service includes calling the service of the second network element, and the first message also includes: information of at least one candidate network element, the information of at least one candidate network element is used to indicate at least one of the type, service scope and slice information of the at least one candidate network element, and the at least one candidate network element includes the second network element.

In one implementation, the first message further includes: identification information of at least one candidate network element.

In one implementation, the first service includes calling a service of a second network element, and the first policy includes one or more of the following policies: a policy for selecting the second network element, a policy for calling a service of the second network element, or a policy for calling a service of the first network element.

In one implementation, the first service includes a terminal device registration service, and the first policy includes one or more of the following policies: a time interval for the terminal device to retry registration, or a policy for invoking a service of the first network element.

In one implementation, the method further includes: the first network element sending registration policy information to the terminal device, where the registration policy information is used to indicate a time interval for the terminal device to retry registration.

Regarding the beneficial effects of the second aspect and each implementation method, reference may be made to the beneficial effects of the aforementioned first aspect and each implementation method, which will not be repeated here.

In a third aspect, embodiments of the present application provide a communication method that can be performed by a third communication device. The third communication device can be a combination device, component, or the like for implementing the functions of a core network element. The third communication device can be a fourth network element; or the first communication device can be a unit/module, circuit, or chip within the fourth network element. For example, the fourth network element can be an AnLF network element. The fourth network element can be combined with the ReLF network element in the first aspect, for example, both the fourth network element and the third network element are NWDAF network elements. The method provided in the third aspect is described below using the example of the first communication device being the fourth network element itself.

The communication method includes: a fourth network element receiving a third message and sending first information based on raw data information obtained from multiple data sources. The third message is used to request the first information, and the first information includes statistical information of at least one network element, including information about at least one network element invoking a service and/or information about at least one network element's service being invoked. The multiple data sources include a network management system, and the raw data information indicates one or more of the following: load information of at least one of the data sources, signaling storm prediction information, or flow control policies at each data source level. The multiple data sources include a first core network element, and the raw data information indicates one or more of the following: a rate, success rate, or failure rate of service invocation by the first core network element; a rate, success rate, or failure rate of service invocation by the first core network element; a service type of the first core network element and/or a proportion of the first core network element's service type among multiple service types; the load and status of the first core network element; or behavior information of a terminal device.

In a fourth aspect, embodiments of the present application provide a communications device capable of implementing the behaviors described in any of the method examples of the first to third aspects. For their beneficial effects, please refer to the relevant descriptions of the first to third aspects and will not be further elaborated herein. For example, the communications device may be the third network element described in the first aspect, or the communications device may be a device capable of supporting the third network element in implementing the functions required by the method provided in the first aspect. For example, the third network element may be an NWDAF network element, and the communications device may be a chip or chip system within the NWDAF network element; or the third network element may be a ReLF network element, and the communications device may be a chip or chip system within the ReLF network element. For another example, the communications device may be the first network element described in the second aspect, or the communications device may be a device capable of supporting the first network element in implementing the functions required by the method provided in the second aspect. For example, the first network element may be an AMF network element, and the communications device may be a chip or chip system within the AMF network element. For another example, the communications device may be the fourth network element described in the third aspect, or the communications device may be a device capable of supporting the fourth network element in implementing the functions required by the method provided in the third aspect. For example, the third network element is a NWDAF network element, and the communication device may be a chip or a chip system in the NWDAF network element; or, the third network element is an AnLF network element, and the communication device may be a chip or a chip system in the AnLF network element.

In one possible design, the communication device includes corresponding means (means) or modules for executing the method of any aspect of the first aspect to the third aspect. For example, the communication device includes a processing unit (sometimes also referred to as a processing module or processor) and/or a transceiver unit (sometimes also referred to as a transceiver module or transceiver). The transceiver unit can realize the sending function and the receiving function. When the transceiver unit realizes the sending function, it can be called a sending unit (sometimes also referred to as a sending module). When the transceiver unit realizes the receiving function, it can be called a receiving unit (sometimes also referred to as a receiving module). The sending unit and the receiving unit can be the same functional unit, which is called a transceiver unit, and the functional unit can realize the sending function and the receiving function; or, the sending unit and the receiving unit can be different functional units, and the transceiver unit is a general term for these functional units. These units (modules) can perform the corresponding functions in the method examples of any aspect of the first aspect to the third aspect above. Please refer to the detailed description in the method examples for details, which will not be repeated here.

In a fifth aspect, an embodiment of the present application provides a communication device, which may be the communication device in the fourth aspect of the above-mentioned embodiment, or a chip or chip system provided in the communication device in the fourth aspect. The communication device includes a communication interface and a processor, and optionally, further includes a memory. The memory is used to store computer programs, instructions, or data, and the processor is coupled to the memory and the communication interface. When the processor reads the computer program, instructions, or data, the communication device executes the method performed by the first network element, the third network element, or the fourth network element in the above-mentioned method embodiment.

In a sixth aspect, an embodiment of the present application provides a chip system, which includes a processor and may also include a communication interface for implementing the method described in any of the first to third aspects. Optionally, the chip system also includes a memory. The memory is used to store computer programs (also referred to as codes, or instructions). The processor is coupled to the memory and the communication interface. The processor is used to call and run the computer program from the memory, so that the device equipped with the chip system executes the method in any of the first to third aspects and any possible implementation thereof. The chip system can be composed of chips, and may also include chips and other discrete devices.

In a seventh aspect, embodiments of the present application provide a communication device comprising an input/output interface and a logic circuit. The input/output interface is used to input and/or output information. The input/output interface can be an interface circuit, an output circuit, an input circuit, a pin, or related circuits. The logic circuit is used to execute the method described in any of aspects 1 to 3.

In an eighth aspect, an embodiment of the present application provides a communication system, comprising a first network element, a second network element, and a third network element. The first network element is configured to implement the functions described in the second aspect, the second network element can provide services for the first network element, and the third network element is configured to implement the functions described in the first aspect. For example, the first network element is an AMF network element, the second network element is a session management function (SMF) network element, and the third network element is a NEDAF network element or a ReLF network element. Optionally, the communication system further comprises a terminal device.

In the ninth aspect, an embodiment of the present application provides a computer-readable storage medium, which is used to store computer programs or instructions. When the computer-readable storage medium is executed, the method described in any aspect of the first to third aspects and any implementation method thereof is implemented.

In the tenth aspect, an embodiment of the present application further provides a computer program product comprising instructions, which, when executed on a computer, enables the method described in any of the first to third aspects and any of their implementation methods to be implemented.

The beneficial effects of the fourth to tenth aspects and their implementations can refer to the beneficial effects of the first aspect and any one of its implementations.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic diagram of a 5G network architecture provided in an embodiment of the present application;

FIG2 is a flow chart of a communication method 200 provided in an embodiment of the present application;

FIG3 is a flow chart of a communication method 300 provided in an embodiment of the present application;

FIG4 is a flow chart of a communication method 400 provided in an embodiment of the present application;

FIG5 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

FIG6 is another schematic diagram of the structure of a communication device provided in an embodiment of the present application.

DETAILED DESCRIPTION

The embodiments of the present application can recommend strategies for preventing or mitigating signaling storms based on the traffic conditions of each network element in the network system, thereby performing signaling control based on these strategies. This can timely mitigate or even avoid signaling storms and reduce service anomalies. The traffic conditions of a network element include both the traffic consumed by the network element's services and the traffic required for future interactive information within the network element. The solutions provided by the embodiments of the present application are described below with reference to the accompanying drawings.

The technical solutions provided in the embodiments of the present application can be applied to communication systems related to the 3rd Generation Partnership Project (3GPP), such as the Long Term Evolution (LTE) communication system and the 5th Generation (5G) mobile communication system, or can also be applied to other next-generation mobile communication systems, such as the 6th Generation (6G) communication system, or other similar communication systems. Other similar communication systems may include wireless fidelity (WIFI), vehicle to everything (V2X), Internet of Things (IoT) system, narrowband Internet of Things (NB-IoT) system, etc.

Please refer to Figure 1, which shows a schematic diagram of a network architecture applicable to an embodiment of the present application. The network architecture shown in Figure 1 is a 5G network architecture based on a service-oriented architecture. Figure 1 shows the interaction relationship between network functions and entities and the corresponding interfaces. For example, the user equipment (UE) and AMF can interact through the N1 interface, and the interaction message is called an N1 message. The various network elements in Figure 1 are network elements that communicate based on a service-oriented interface, that is, the communication between the network elements in Figure 1 uses a service-oriented interface. Some of the interfaces in Figure 1 can be implemented in the form of a service-oriented interface. The network architecture includes three parts, namely the terminal equipment part, the data network (DN) part and the operator network part. The functions of some of the network elements are briefly introduced below.

The terminal device section includes terminal devices, among which any device capable of data communication with a base station is considered a terminal device. Terminal devices are also called terminals or terminal devices, and include UE, mobile station, or mobile terminal. Terminal devices can be widely used in various scenarios. For example, terminal devices can be: mobile phones, computers, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, stations (STAs), robotic arms, cameras, robots, vehicles, drones, helicopters, airplanes, ships, or smart home devices (such as TVs, air conditioners, vacuum cleaners, speakers, set-top boxes), relays, customer premises equipment (CPE), smart cars (or intelligent cars), roadside units (RSUs), etc. Terminal devices can also be terminal devices in IoT systems, such as water meters and electricity meters.

The various terminal devices introduced above, if located on a vehicle (for example, placed/installed in a vehicle), can be considered as vehicle-mounted terminal devices. The vehicle-mounted terminal device can be an on-board module, on-board module, on-board component, on-board chip or on-board unit built into the vehicle as one or more components or units, and the vehicle can implement the method of the present application through the built-in on-board module, on-board module, on-board component, on-board chip or on-board unit. The on-board terminal device can be a complete vehicle device, an on-board module, a vehicle, an on-board unit (OBU), a roadside unit (RSU), a vehicle-mounted system (or a vehicle-mounted sending unit) (telematics box, T-box), a chip or a system on chip (SOC), etc. The above-mentioned chip or SOC can be installed in a vehicle, OBU, RSU or T-box.

A DN, also known as a packet data network (PDN), is a network located outside of a carrier network. The carrier network can access multiple DNs, and a variety of services can be deployed on the DN, providing data and/or voice services to terminal devices. For example, a DN is the private network of a smart factory. The sensors installed in the workshop of the smart factory can be terminal devices. The DN is equipped with a control server for the sensors, and the control server can provide services to 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. For another example, a DN is the internal office network of a company. The mobile phones or computers of the company's employees can be terminal devices, and the employees' mobile phones or computers can access information, data resources, etc. on the company's internal office network.

An operator network may include multiple network function (NF) network elements, such as a network exposure function (NEF) network element, a network repository function (NRF) network element, a policy control function (PCF) network element, a unified data management (UDM) network element, an application function (AF) network element, an AMF network element, an SMF network element, a user plane function (UPF) network element, an NWDAF network element, and a (radio) access network (R)AN). Of course, an operator network may also include other functional network elements, such as a network slice selection function (NSSF) network element and an authentication server function (AUSF) network element. The term "functional network element" may also be replaced by "functional entity." The naming of the aforementioned network elements is merely for the purpose of distinguishing different functions and shall not constitute any limitation on this application. This application does not exclude the possibility of adopting other naming in 5G networks and other future networks (such as 6G networks). For example, in a 6G network, some or all of the above network elements may continue to use the terminology used in 5G, or may adopt other names.

The above-mentioned terminal device can establish a connection with the operator network through the interface provided by the operator network (such as N1, etc.), and use the data and/or voice services provided by the operator network. The terminal device can also access the DN through the operator network, use the operator services deployed on the DN, and/or services provided by a third party. The above-mentioned third party may be a service provider other than the operator network and the terminal device, and may provide other data and/or voice services to the terminal device. The specific form of the above-mentioned third party can be determined according to the actual application scenario and is not limited here.

For ease of explanation, the following explanation will use the (R)AN as an example. RAN is a subnetwork of the operator network and is the implementation system between the service nodes and terminal devices in the operator network. To access the operator network, the terminal device first passes through the RAN and can then connect to the service nodes of the operator network through the RAN. The RAN device in this application is a device that provides wireless communication functions for the terminal device. The RAN can be a 3GPP-related cellular system, such as a 5G/new radio (NR) mobile communication system, or a future-oriented evolution system (such as a 6G mobile communication system). The RAN can also be an open access network (open RAN, O-RAN or ORAN), a cloud radio access network (cloud radio access network, CRAN), or a virtualized radio access network (virtualized RAN, vRAN). The RAN can also be a communication system that integrates two or more of the above systems. The RAN device can also be called a RAN node, RAN entity, or access node. In the embodiments of this application, the network device refers to a radio access network (RAN) device. In one possible scenario, a RAN node can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB), a next-generation base station in a 6G mobile communication system, or a base station in a future mobile communication system. A RAN node can be a macro base station, a micro base station, an indoor station, a relay node, a donor node/host node, or a wireless controller. A RAN node can also be a server, a wearable device, a vehicle, or an onboard device. For example, a RAN node in V2X technology can be a roadside unit (RSU). In another possible scenario, a RAN node can be a module or unit that performs some of the functions of a base station; or multiple RAN nodes can collaborate to assist terminal devices in achieving wireless access, with different RAN nodes each performing some of the functions of a base station. For example, a RAN node can be a centralized unit (CU), a distributed unit (DU), or a radio unit (RU).

In the above-mentioned operator network, the part other than the (wireless) access network part can be referred to as the core network part. The following briefly introduces several core network elements involved in the embodiments of the present application.

The AMF network element, also referred to as AMF, manages UE access and mobility. It is responsible for maintaining UE status, managing UE reachability, forwarding non-mobility management (MM) and non-access-stratum (NAS) messages, and forwarding session management (SM) N2 messages.

The SMF network element, abbreviated as SMF, manages UE sessions and allocates and releases resources for UE sessions. These resources include session quality of service (QoS), session paths, and forwarding rules. The SMF is responsible for selecting or reselecting the UPF, allocating Internet Protocol (IP) addresses, and establishing, modifying, and releasing bearers.

The UPF network element, abbreviated as UPF, supports all or part of the following functions: interconnecting protocol data unit (PDU) sessions with the data network, packet routing and forwarding (for example, supporting uplink classifier for forwarding traffic to the data network, supporting branching points to support multi-homed PDU sessions), or data packet inspection.

The NRF network element, also referred to as NRF, can be used to provide network element discovery. Based on requests from other network elements, it provides network element information corresponding to the network element type, such as address information and/or identification information. This enables on-demand configuration of network functions and services, as well as interconnection between NFs. The NRF network element also provides network element management services, such as service registration, service discovery, updates, deregistration, and network element status subscription and push. Service registration means that NF network elements must register with the NRF network element before providing services. Service discovery means that when an NF network element requires other NF network elements to provide services, it must first perform service discovery through the NRF network element to discover the desired NF network element to provide services. For example, when NF network element 1 requires NF network element 2 to provide services, it must first perform service discovery through the NRF network element to discover NF network element 2.

The NWDAF network element (NWDAF) provides data analysis capabilities. It is primarily responsible for collecting and analyzing network operation data from various network elements within the communications system. Based on analysis requests, the NWDAF collects and analyzes data from relevant network elements and provides feedback to the requesting party.

The NWDAF network element in the embodiments of the present application supports artificial intelligence (AI)/machine learning (ML) technology. The NWDAF network element can deploy AI/ML models and use them to implement corresponding functions. A device that "deploys" an AI/ML model can refer to a device that runs the AI/ML model. For example, "deployment" can also be understood as "running" or "using." The AI model is the specific implementation of an AI function and represents the mapping relationship between the model's input and output. The AI model can be a neural network, a linear regression model, a decision tree model, a support vector machine (SVM), a Bayesian network, a Q-learning model, or other machine learning models. In the embodiments of the present application, the AI function can include at least one of the following: data collection (collecting training data and/or inference data), data preprocessing, model training (or model learning), model information release (configuring model information), model verification (verifying the trained model), model inference (using the trained model for inference), or inference result release. Inference can also be called prediction. Optionally, the AI model can include an ML model.

NWDAF network elements can train AI models after collecting data from related network elements (for example, AMF network elements, SMF network elements, PCF network elements, etc.), and finally use the AI model to perform data inference and feedback the inference results to the corresponding requester. According to different functions, NWDAF network elements can be divided into NWDAF network elements that support training (i.e., NWDAF (MTLF)) and NWDAF network elements that support inference (i.e., NWDAF (AnLF)). NWDAF (AnLF) network elements can request AI model information from NWDAF (MTLF) network elements for data inference.

The NSSF network element, abbreviated as NSSF, is primarily used to select the appropriate network slice for a terminal's services. The identification (or identification information) of a network slice may include, but is not limited to, network slice selection assistance information (NSSAI). Specifically, single network slice selection assistance information (S-NSSAI) can be used to identify a single network slice, while NSSAI can be used to identify a group of network slices (or network slice group). A network slice group can include one or more network slices.

The UDM network element, referred to as UDM for short, is used for user subscription context management. It is responsible for managing the UE's subscription data and notifying the corresponding network elements when the subscription data is modified.

The UDR network element, abbreviated as UDR, is a unified data repository responsible for storing and retrieving contract data, policy data, and public architecture data, making it available to network elements such as the UDM, PCF, or NEF. The UDR can implement different data access authentication mechanisms for different types of data (such as contract data and policy data) to ensure data access security. The UDR should be able to return a failure response with an appropriate cause value for illegal service-based operations or data access requests.

The AF network element primarily provides application layer services and also supports interaction with the 5G core network to provide services, such as influencing data routing decisions, policy control functions, or providing third-party services to the network side. In specific applications, the AF network element can be a third-party server or application server.

In Figure 1, Nnef, Nnrf, Npcf, Nudm, Naf, Namf, Nsmf, Nnwdaf, N1, N2, N3, N4, and N6 are interface serial numbers. The meanings of these interface serial numbers can be found in the meanings defined in the 3GPP standard protocol and are not limited here. The core network elements shown in Figure 1 can be understood as network elements used to implement different functions in the core network, for example, they can be combined into network slices as needed. These core network elements can be independent devices or integrated into the same device to implement different functions. This application does not limit the specific form of the above network elements. The interface names between the network elements in Figure 1 are only an example. The names of the interfaces in the specific implementation may be other names, and this application does not specifically limit this.

The network architecture shown in Figure 1 is only a schematic, and the number of terminal devices and/or network devices may be less or more. The communication system described in the embodiment of the present application is to more clearly illustrate the technical solution of the embodiment of the present application, and does not constitute a limitation on the communication system to which the embodiment of the present application is applicable. For example, the communication system may also include other devices, such as network management network elements/systems, such as operation administration and maintenance (OAM) or management data analysis function (MDAF). OAM/MDAF can be used to manage core network network elements, for example, it can coordinate the planning of flow control thresholds and provide network element-level signaling rate policies to NFs. It is known to those skilled in the art that with the evolution of network architecture, the technical solutions provided in the embodiment of the present application are also applicable to similar technical problems. When applying the technical solutions of the embodiment of the present application to other communication systems, the devices, components, modules, etc. in the embodiment can be replaced with corresponding devices, components, modules in other communication systems without limitation.

As shown in Figure 1, the network may include multiple NF network elements and other network elements, such as access network equipment. The interaction between NF network elements or the interaction between NF network elements and other devices may cause signaling overload, affecting the normal operation of the business. For example, an AMF calls the services of multiple SMFs at the same time. The AMF may have too much signaling to process at the same time and may not be able to process one or some signaling in time, resulting in business interruption. For example, multiple UEs initiate registration requests at the same time or multiple UEs perform registration request processes at the same time. In this way, the AMF network element interacts with multiple UEs at the same time. The AMF may have too much signaling to process at the same time, resulting in UE registration interruption. In this case, the UE will initiate a registration request again, and this will be repeated, resulting in some UEs never being able to register successfully.

One control strategy for signaling storms is to have the network management system plan flow control thresholds and provide network element-level control strategies. However, network element-level control strategies have the problems of low efficiency and delay in controlling signaling storms.

In view of this, a solution of an embodiment of the present application is provided. In an embodiment of the present application, a suitable signaling storm prevention strategy or signaling storm mitigation strategy can be recommended based on the statistical information of each network element in the network (including service-related information). The solution provided in the embodiment of the present application can perceive the service of the network element, so the recommended strategy will be different for different signaling overheads caused by different services. Compared with the signaling storm control strategy at the signaling level, this solution can timely alleviate/prevent signaling storms and improve the efficiency of mitigating signaling storms.

In an embodiment of the present application, the recommended signaling storm prevention strategy or signaling storm mitigation strategy can be implemented by an entity having a recommended logical function. The entity can be called ReLF. ReLF can be an independent functional module. For example, ReLF can be a newly added functional module based on Figure 1. ReLF can also be set as part of an existing network element or combined with other functional network elements. For example, ReLF is a functional module in NWDAF, and NWDAF with ReLF can be regarded as an enhanced NWDAF. ReLF can be replaced by NWDAF (ReLF). Among them, when ReLF is a functional module of NWDAF, ReLF and AnLF can be set independently or combined. The embodiment of the present application does not limit the specific name of the device obtained by combining ReLF and AnLF. For example, ReLF and AnLF can also be called AnLF after being combined, and the AnLF has the ReLF function.

NWDAF (ReLF) can communicate with NWDAF (AnLF), for example, NWDAF (ReLF) can obtain corresponding analysis and/or prediction information from NWDAF (AnLF). For example, in an embodiment of the present application, NWDAF (ReLF) can obtain statistical information about multiple NF network elements from NWDAF (AnLF). It should be noted that the following third network element has ReLF, and the third network element can be an NWDAF with ReLF; or, the third network element can be an NWDAF with ReLF and AnLF, wherein ReLF and AnLF are independently set, or ReLF and AnLF are jointly set.

The solution provided by the embodiment of the present application is introduced below in conjunction with the accompanying drawings. In the following introduction, the communication method provided by the embodiment of the present application is applied to the network architecture shown in Figure 1 as an example. The network architecture and application scenario described in the embodiment of the present application are for the purpose of more clearly illustrating the technical solution of the embodiment of the present application, and do not constitute a limitation on the technical solution provided by the embodiment of the present application. It is known to those skilled in the art that with the evolution of the network architecture and the emergence of new application scenarios, the technical solution provided by the embodiment of the present application is also applicable to similar technical problems.

In various embodiments of this application, the phrases "when," "if," and "if" all imply that the device will perform a corresponding action under certain objective circumstances. These phrases do not limit the timeframe, do not require the device to perform a judgment action, and do not imply any other limitations. Unless otherwise specified, "if" and "if" are interchangeable, and "when" and "under the circumstances" are interchangeable. "When" and "if" are interchangeable.

In the embodiments of the present application, the number of nouns, unless otherwise specified, means "singular noun or plural noun", that is, "one or more". "At least one" means one or more, and "plural" means two or more. "And/or" describes the association relationship of associated objects, indicating that there may be three relationships. For example, A and/or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character "/" generally indicates that the previous and next associated objects are in an "or" relationship. For example, A/B means: A or B. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c means: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, c can be single or multiple.

The ordinal numbers such as "first" and "second" mentioned in the embodiments of the present application are used to distinguish between multiple objects, and are not used to limit the size, content, order, timing, priority or importance of the multiple objects. For example, the first network element and the second network element refer to two different network elements, and do not indicate the difference in priority or importance of the two network elements. For a technical feature, "A", "B", "C" and "D" are used to distinguish the technical features in the technical feature. There is no order of precedence or order of importance between the technical features described by "A", "B", "C" and "D". For example, the strategies A and B in this article are only used to distinguish different strategies, and do not limit the order of precedence or order of priority or importance between method A and method B.

The following describes the communication method provided by the embodiments of the present application from the perspective of interaction between multiple network elements. The steps performed by each network element can be implemented by the network element itself, or by a component in the network element (such as a chip, a processing unit, or a processor module). These multiple network elements are all core network elements, for example, including the first network element and the third network element, or even other network elements, such as the third network element, a terminal device, etc.

Please refer to Figure 2, which is a flowchart of a communication method 200 provided in an embodiment of the present application. Figure 2 describes the method from the perspective of interaction between a first network element and a third network element. It should be understood that communication method 200 can also be implemented by other devices, such as a chip or communication device with communication capabilities. It should be noted that the embodiment of the present application uses the first network element and the third network element as an example and is not limited to the number of network elements. For example, the embodiment of the present application can also be implemented by multiple first network elements and multiple third network elements. When multiple first network elements are involved, the execution process is the same for each of the multiple first network elements. When multiple third network elements are involved, the execution process is the same for each of the multiple third network elements. For another example, the embodiment of the present application can also be implemented by other network elements, such as a fourth network element, a terminal device, etc. For example, a first network element can call a service of a second network element, or a second network element can provide a service to the first network element. For example, the first network element is an AMF and the second network element is an SMF; or the first network element is an SMF and the second network element is a UPF. The third network element can be a ReLF or an NWDAF with a ReLF. Unless otherwise specified, the following strategies all refer to strategies for preventing or mitigating signaling storms. As shown in FIG2 , the process of the communication method 200 includes the following steps.

S201. A first network element sends a first message to a third network element. Correspondingly, the third network element receives the first message from the first network element.

The first message can be used to request the recommendation of a policy corresponding to the first service, and the policy can be used to prevent or alleviate a signaling storm. In a possible scenario, a signaling storm may occur or has occurred in the first network element. In this case, the first network element may cause a signaling storm or aggravate the signaling storm by executing the first service according to the original policy, affecting the normal operation of the first service. To this end, the first network element may send a first message to the third network element, requesting the recommendation of a policy corresponding to the first service to prevent and/or alleviate the signaling storm. In other words, the first message can be used by the first network element to request the third network element to recommend a policy for preventing and/or alleviating a signaling storm. The embodiment of the present application does not limit the specific name of the first message. For example, the first message may be called a recommendation subscription request message or a recommendation policy request message.

Taking the first network element as an example, AMF has multiple SMFs serving AMF, and multiple SMFs serve AMF in the same period of time. For AMF, there is a lot of signaling that needs to be interacted in a short period of time, and a signaling storm may occur or has already occurred. In this case, the first network element can send a first message to the third network element. For another example, taking the first network element as an example, multiple terminal devices may initiate registration processes in the same period of time. The AMF interacts with multiple terminal devices, which may cause a signaling storm or has already occurred. In this case, the first network element can also send a first message to the third network element.

It is understandable that the third network element may provide multiple services for the first network element, such as analysis services, recommendation services, etc., and there may be multiple analysis services and multiple recommendation services. In order to make the third network element clear about the service requested by the first network element so as to avoid providing mismatched services to the first network element, the first message may include a recommendation ID, which is the service ID requested for recommendation to indicate the service requested by the first network element. The embodiment of the present application does not limit the specific name of the recommendation ID. For example, the first message is used to request the execution of the recommendation strategy of the first business. The recommendation strategies of different businesses are different. From this perspective, the recommendation ID can also be called the recommendation service ID, policy type ID or recommendation type ID. Different IDs correspond to different recommendation types/recommended services. The embodiment of the present application does not limit the classification method of recommended services/recommendation types. For example, it can be classified by business. For example, the terminal device registration business corresponds to one recommendation type, and the first network element calling the second network element corresponds to another recommendation type.

The content carried by the first message may vary depending on the first service. For example, if the first service includes a first network element invoking a service of a second network element, the first message may carry one or more of the following information.

Information A: Information about the first network element, such as the service scope of the first network element, the ID of the first network element, and network slice information of the first network element. Alternatively, the information about the first network element may include the service scope of the first network element, the ID of the set to which the first network element belongs, and network slice information of the first network element. The network slice information includes the data network name (DNN) corresponding to the network slice or single network slice selection assistance information (S-NSSAI).

For example, the service scopes of different first network elements may be different. For example, the service scope of some first network elements is a province, while the service scope of some first network elements is a city or district. Generally, a first network element with a wider service scope can call more second network elements than a first network element with a narrower service scope. For example, taking the first network element as an AMF and the second network element as an SMF as an example, generally, an AMF with a service scope of a province can call more SMFs than an SMF with a service scope of a city or district. If a signaling storm occurs in the first network element, it may be expected that a third network element will select a suitable second network element from multiple second network elements serving the first network element. In this case, the first message may also include attribute information of the first network element. Accordingly, the third network element can perform subsequent operations based on the attribute information of the first network element. For example, the second network element that the third network element ultimately recommends to the first network element is a second network element that matches the service scope of the first network element.

Optionally, the first message does not include the information of the first network element. In this case, the third network element may request the information of the first network element from other network elements. For example, the third network element may request the information of the first network element from the UDM network element.

Information B: identification information of at least one candidate network element, for example, ID of at least one candidate network element.

The at least one candidate network element is at least one second network element that the first network element expects the third network element to recommend, and each second network element can serve the first network element. In a possible scenario, the first network element knows the at least one second network element that serves it. When a signaling storm occurs or is about to occur in the first network element, the first network element can independently determine which one or more second network elements among the at least one second network element to preferentially select/call. The one or more second network elements can be regarded as candidate network elements for providing services to the first network element. In this case, the first network element expects the third network element to preferentially recommend the candidate network element. Accordingly, the first message includes identification information of the at least one candidate network element, and the third network element can select one or more network elements from the at least one candidate network element and recommend them to the first network element. When the third network element recommends a second network element to the first network element, it does not need to consider network elements other than the at least one candidate network element, and naturally does not need to collect relevant information about second network elements other than the at least one candidate network element, thereby reducing the acquisition of unnecessary network element information and reducing processing complexity.

Information C: information about at least one candidate network element. The information about each candidate network element is used to indicate at least one of the type, service scope, and network slice information of the candidate network element.

The first message may include information about at least one candidate network element, and the first network element may also notify the third network element of the information about the at least one candidate network element. The third network element may obtain at least one candidate network element from other network elements based on the information about the at least one candidate network element.

For example, the NRF network element knows the information of the second network element that serves the first network element, so the third network element can request the NRF network element to obtain at least one candidate network element. For example, the third network element sends a second message to the NRF network element, and the second message may include information of at least one candidate network element, which is used to request to obtain at least one candidate network element. In response to the second message, the NRF network element determines at least one candidate network element that matches the information of the at least one candidate network element. Afterwards, the NRF network element sends at least one identification information to the third network element, and one identification information corresponds to one candidate network element. The embodiment of the present application does not limit the specific implementation method of the NRF network element sending at least one identification information. For example, the NRF network element can send a first list, and the first list includes at least one identification information.

For another example, other first network elements (for example, first network element B) in the same set as the first network element (for example, first network element A) that sends the first message also know which second network elements provide services to first network element A. In this case, the third network element can send a second message to the first network element B, and the second message may include information of at least one candidate network element for requesting to obtain at least one candidate network element. In response to the second message, the first network element B determines at least one candidate network element that matches the information of the at least one candidate network element, and sends at least one identification information to the third network element, where one identification information corresponds to one candidate network element. It can be understood that the set (Set) ID corresponding to the first network element A and the second network element B is the same. The embodiment of the present application does not limit the specific implementation method of the second network element B sending at least one identification information. For example, the second network element B can send a first list, and the first list includes at least one identification information.

The information A to information C included in the first message above are only examples. In some embodiments, the first message may also include other information, such as relevant information of the terminal device. For example, the first message may also include the ID of the terminal device and the DNN/S-NSSAI corresponding to the terminal device.

In some embodiments, the first service includes a terminal device registration service. In addition to carrying the recommendation ID, the first message may carry information A and relevant information of the terminal device, such as the ID of the terminal device and the corresponding DNN/S-NSSAI.

S202. The third network element obtains first information.

The third network element receives the first message and may send a response message to the first network element in response to the first message, so that the first network element can clearly understand whether the first message is sent successfully.

The third network element receives the first message and, based on the first message, obtains relevant information about at least one network element, including the first network element, to recommend an appropriate policy to the first network element. The at least one network element is related to the first service, and the at least one network element may vary depending on the first service. For example, the first service may include the first network element invoking a service of a second network element, and the at least one network element may include at least one candidate network element for the second network element.

For ease of description, the relevant information of at least one network element is referred to as statistical information of at least one network element. The statistical information of at least one network element can be used to analyze or predict the current and/or future signaling volume of each network element. Based on this statistical information, a third network element can obtain a better strategy for preventing or mitigating signaling storms. The embodiments of the present application do not limit the content included in the statistical information of at least one network element. For example, the statistical information of at least one network element includes one or more of the following: the rate and/or frequency of service invocation by at least one network element within a first time period, predicted information on the rate and/or frequency of invocation of at least one network element within the first time period, and first time information. The first time information can be used to indicate the first time period. It is understandable that the predicted information on the rate and/or frequency of invocation of a network element within a period of time can predict the amount of signaling required to be interacted by the network element within that period of time. Similarly, the rate and/or frequency of service invocation within a period of time can represent the amount of signaling interacted by the network element within that period of time.

The third network element obtains the first information including the third network element sending a third message to the data analysis network element, the third message including the analysis ID, and the third information including the analysis ID to indicate the analysis service requested by the third network element. For example, the analysis service is a service for requesting to obtain the first information. The data analysis network element may be an NWDAF or an AnLF in the NWDAF. If the third network element is a ReLF network element, the third network element may send a third message to the AnLF in the NWDAF network element. AnLF receives the third message and may obtain/collect raw data information from multiple data sources, determine the first information based on the obtained/collected raw data information, and send the first information to the third network element.

Multiple data sources include multiple devices in the network, such as a network management system and at least one core network element (such as AMF, SMF, UPF, PCF, etc.). The network system includes but is not limited to OAM/MDAF. When multiple data sources include a network system, the original data information may indicate one or more of the following: load information of at least one data source, signaling storm prediction information, or device-level flow control policy. The load information of each data source includes, for example, the load of the data source, the number of terminals served, the number of sessions conducted, etc. The signaling storm prediction information includes, for example, the probability of a signaling storm occurring, the degree of a signaling storm, etc. The device-level flow control policy is also the network element-level flow control policy.

When multiple data sources include core network elements, taking the example of multiple data sources including the first core network element, the original data information of the first core network element may indicate one or more of the following: one or more of the rate, success rate or failure rate of the first core network element calling the service; one or more of the rate, success rate or failure rate of the service of the first core network element being called; the service type of the first core network element and/or the proportion of the service type of the first core network element in multiple service types; the load and status of the first core network element or the behavior information of the terminal device related to the first core network element. It should be noted that in the embodiment of the present application, the core network element calling service includes the signaling of the core network element interactive non-service interfaces N2 and N4. The service type of the first core network element includes the type of registration service of the first core network element (for example, initial/mobility/periodic/update/emergency).

After AnLF collects raw data information from multiple data sources, it can determine statistical information of at least one network element by analyzing or predicting based on the raw data information. Optionally, AnLF can also predict whether the first network element or other network elements have a signaling storm or whether a signaling storm will occur based on the raw data information. In response to the third message, AnLF sends first information to the third network element, where the first information includes statistical information of at least one network element. Optionally, the first information may also include prediction information of the signaling storm and/or an analysis ID corresponding to the first information (e.g., the analysis ID carried by the third message). The prediction information of the signaling storm may indicate whether there is a signaling storm or the extent of the signaling storm, and may assist the third network element in recommending a suitable strategy for the first network element. For example, the prediction information of the signaling storm may include the probability of the occurrence of the signaling storm and the level of the signaling storm.

When the third network element is a device jointly provided by the ReLF and AnLF, the third network element may obtain/collect raw data information from multiple data sources and determine the first information based on the obtained/collected raw data information. Alternatively, if the third network element is the ReLF in the NWDAF, and the ReLF is independent of the AnLF, the third network element may obtain the first information from the AnLF. For details, please refer to the aforementioned related content and will not be repeated here.

S203. The third network element sends a first policy to the first network element according to statistical information of at least one network element.

After obtaining statistical information from at least one network element, the third network element may generate a first policy and send it to the first network element. The first policy includes a policy corresponding to the first service. For example, if the first service includes invoking a service of a second network element, the third network element may recommend the second network element to the first network element from at least one candidate network element based on the statistical information from the at least one network element. The first policy can be used to prevent or mitigate signaling storms in the first network element. After receiving the first policy, the first network element may determine whether to implement the first policy based on actual circumstances. For example, if the first information includes signaling storm prediction information, and the signaling storm prediction information indicates that the probability of a signaling storm is very low or even that a signaling storm will not occur, the first network element may not implement the first policy to minimize the impact on the first network element's normal services. For another example, if the first information includes signaling storm prediction information, and the signaling storm prediction information indicates that the signaling storm is relatively severe, the first network element may implement the first policy to mitigate the signaling storm.

The first policy may vary depending on the first service. For example, if the first service includes calling the service of the second network element, the first policy may include one or more of the following policies: a policy for selecting the second network element, a policy for calling the service of the second network element, or a policy for calling the service of the first network element. For example, the first network element is AMF, and the second network elements that can provide services to AMF include SMF1 to SMF5. The third network element may recommend SMF2 and SMF3 to the AMF as serving the AMF. Alternatively, the first and third network elements may recommend SMF2 and SMF3 to the AMF, and recommend a policy for calling the services of SMF2 and SMF3. The AMF performs corresponding operations according to the first policy. For example, SMF1, SMF4, and SMF5 will not be called, which can reduce signaling interactions and thus prevent or alleviate signaling storms.

For another example, the first service includes a terminal device registration service, and the first policy includes one or more of the following policies: the time interval for the terminal device to retry registration, and the policy for the service of the first network element to be called. The time interval for the terminal device to retry registration serves as a type of registration policy for the terminal device. The embodiment of the present application does not limit the registration policy of the terminal device. For example, the registration policy of the terminal device includes the number of terminal devices allowed to register within a period of time or the number of registration requests allowed to be processed does not exceed a certain value. A period of time can be (pre) configured, and the number of terminal devices can also be (pre) configured. For another example, the registration policy of the terminal device includes the number of terminal devices allowed to register within a specified time. For example, the registration policy of the terminal device includes allowing the processing of registration requests from A terminal devices after time xx; or, the registration policy of the terminal device includes allowing the processing of registration requests from B terminal devices from time xx to time yy).

The first network element may invoke a service or process the invoked service according to the first policy. For example, the first network element processes a registration request from a terminal device according to the terminal device's registration policy. For example, if the interval between retrying registration by the terminal device is 1 second, and the interval between the first network element receiving a registration request from the terminal device and the last registration request received from the terminal device does not exceed 1 second, the first network element refuses to process the received registration request.

Optionally, if the first service includes a terminal device registration service, the third network element may send policies related to the terminal device to the terminal device. For example, the third network element sends registration policy information to the terminal device, where the registration policy information includes a time interval for the terminal device to retry registration. Alternatively, if the first service includes a terminal device registration service, the first network element may send policies related to the terminal device to the terminal device. For example, the first network element sends the registration policy information to the terminal device via an access network device.

Optionally, the first network element may also adjust the registration policy of the terminal device and feed back the adjusted registration policy to the terminal device. For example, following the above example, when the first network element rejects the registration request of the terminal device, the first network element may also indicate to the terminal device the delay time for initiating the registration request next time. The first network element may carry the delay time in the response message of rejecting the registration request of the terminal device. It is understandable that there are multiple terminal devices, and if the first network element creates a delay time for each registration request for multiple terminal devices, it must comply with the registration policy of the terminal device recommended by the third network element. For example, the number of registration requests processed by the first network element within a period of time does not exceed a certain value.

In the communication method 200 described above, the statistical information of at least one network element is collected at the business and/or service granularity level, enabling awareness of the network element's business. This allows for different recommended strategies based on the varying signaling overhead incurred by different businesses. Compared to signaling-level signaling storm control strategies, this communication method can mitigate/prevent signaling storms in a timely manner, improving their efficiency.

In order to better understand the communication method 200 provided in the embodiment of the present application, the specific process of the communication method 200 is introduced below with specific examples (ie, the following Example 1 and Example 2).

Example 1: Take the first service as an example where the first network element calls the service of the second network element, and the first network element is the first AMF, the second network element is the SMF, and the third network element is the ReLF.

Please refer to Figure 3, which is a flow chart of a communication method 300 provided in an embodiment of the present application. The communication method 300 includes the following steps.

S301. The first AMF discovers a serviceable ReLF.

The first AMF may send a subscription request to the NRF, and the NRF, in turn, receives the subscription request from the first AMF. This subscription request is used to request a ReLF that can serve the first AMF, or to request a network function with a recommended logical function. The subscription request may include identification information indicating the recommended logical function. The NRF receives the subscription request, queries the network function with the recommended logical function, and provides feedback to the first AMF. For example, if the ReLF is an independent entity and the NRF finds a ReLF that can serve the first AMF, it may provide the ReLF ID to the first AMF. For another example, if the ReLF is a functional module in the NWDAF, and the NRF finds an NWDAF that can serve the first AMF, the NRF may provide the NWDAF ID to the first AMF. For another example, if the ReLF and AnLF are combined and still referred to as the AnLF, in this case, if the NRF finds an AnLF that can serve the first AMF and that the AnLF has a ReLF, the NRF may provide the AnLF ID to the first AMF. Example 1 uses the NRF providing the ReLF ID to the first AMF as an example.

S302. The first AMF sends a first message to the ReLF. Correspondingly, the ReLF receives the first message.

Regarding the content included in the first message, please refer to the relevant content in the aforementioned S201, which will not be repeated here.

S303. The ReLF sends a response message to the first message to the first AMF.

When the first message does not include identification information of at least one candidate network element, S304-S305 (i.e., acquisition method 1 in FIG3 ) is executed after S303, or S306-S307 (i.e., acquisition method 2 in FIG3 ) is executed after S303. When the first message includes identification information of at least one candidate network element, S304-S305 and S306-S307 do not need to be executed, and are therefore indicated by dotted lines in FIG3 .

S304. The ReLF sends a second message to the NRF. Correspondingly, the NRF receives the second message.

The second message may include information of at least one candidate network element, and is used to request obtaining the at least one candidate network element. In response to the second message, the NRF network element determines at least one candidate network element that matches the information of the at least one candidate network element.

S305. The NRF sends a first list to the ReLF, where the first list includes identification information of at least one candidate network element.

S306. ReLF sends a second message to the second AMF in the AMF Set, and correspondingly, other AMFs receive the second message.

The content carried by the second message can refer to the relevant content of S304 and will not be repeated here.

S307. The second AMF sends a first list to the ReLF, where the first list includes identification information of at least one candidate network element.

S308. The ReLF sends a third message to the AnLF. Correspondingly, the AnLF receives the third message.

The third message may include an analysis ID for requesting the first information. For details, please refer to the relevant content in the aforementioned communication method 200, which will not be described here.

S309 : AnLF collects raw data information from multiple data sources, and obtains statistical information of at least one network element based on the raw data information.

Multiple data sources may include a network management system and may also include at least one core network element. AnLF may collect corresponding raw data information from each data source. For example, AnLF may collect load information, signaling storm prediction information, or device-level flow control strategy of at least one data source from the network management system. For another example, AnLF may collect from the first core network element one or more of the rate, success rate, or failure rate at which the first core network element calls a service; one or more of the rate, success rate, or failure rate at which the service of the first core network element is called; the service type of the first core network element and/or the proportion of the service type of the first core network element in multiple service types; the load and status of the first core network element or the behavior information of the terminal device related to the first core network element.

S310: AnLF sends first information to ReLF. Correspondingly, ReLF receives the first information from AnLF.

The first information includes statistical information of at least one network element, the at least one network element including a first network element and a second network element. Optionally, the first information may further include prediction information and/or an analysis ID of a signaling storm.

S311. The ReLF sends a first policy to the first AMF. Correspondingly, the first AMF receives the first policy of the ReLF.

The ReLF determines a first policy based on the statistical information or first information of at least one network element and sends the first policy to the first AMF. The first policy includes, for example, a policy for the first AMF to select the SMF, a policy for the first AMF to call the SMF service, and a policy for the first AMF service to be called.

S312. The first AMF executes the first service according to the first policy.

For example, the first AMF selects the first SMF according to the policy of the first AMF selecting the SMF in the first policy. For another example, the SMF selected by the first AMF is the first SMF, and the first AMF calls the service of the first SMF according to the policy of the first AMF calling the service of the SMF in the first policy.

Optionally, S313 to S314 may be executed after S312 , which are indicated by dotted lines in FIG. 3 .

S313. AnLF sends a subscription notification to ReLF, where the subscription notification includes the updated first information.

S314. The ReLF generates a new first policy based on the updated first information, and sends the updated first policy to the first AMF.

Each data source can periodically send raw data information to AnLF, which can then re-determine the first information based on the updated raw data information. To ensure that the policy recommended by ReLF can promptly prevent or mitigate signaling storms, AnLF can send updated first information to ReLF, which then updates the first policy based on the updated first information. The updated first policy is determined based on the latest raw data information collected by AnLF, and therefore can better prevent or mitigate signaling storms.

In communication method 300, the raw data information collected by the AnLF is associated with the services of the first AMF and SMF. Accordingly, the first policy is a service-level policy. In this way, the first policy can promptly prevent or alleviate the signaling storm of the first AMF, reduce network anomalies, and reduce the impact on normal services.

Example 2: Take the first service as the terminal device registration service as an example, and take the first network element as the AMF as an example.

Please refer to Figure 4, which is a flow chart of a communication method 400 provided in an embodiment of the present application. The communication method 400 includes the following steps.

S401: AMF discovers a serviceable ReLF. For details, refer to S301 above and will not be repeated here.

S402. The AMF sends a first message to the ReLF. Correspondingly, the ReLF receives the first message.

The first message may include a recommendation ID, for details, refer to the relevant content in the aforementioned S201. For example, the first message may also include attribute information of the AMF and related information of the terminal device, which will not be described in detail here.

S403. ReLF sends a response message to the first message to AMF.

S404. The ReLF sends a third message to the AnLF. Correspondingly, the AnLF receives the third message.

The third message may include an analysis ID for requesting the first information. For details, please refer to the relevant content in the aforementioned communication method 200, which will not be described here.

S405: AnLF collects raw data information from multiple data sources and obtains statistical information of at least one network element based on the raw data information. For details, please refer to the relevant content in the above S309, which will not be repeated here.

S406: AnLF sends the first information to ReLF, and correspondingly, ReLF receives the first information from AnLF. For details, please refer to S310 above and will not be repeated here.

S407. ReLF sends the first policy to AMF. Correspondingly, AMF receives the first policy of ReLF.

The ReLF determines a first policy based on the statistical information or first information of at least one network element and sends the first policy to the AMF. The first policy includes, for example, the time interval for the terminal device to retry registration and the policy for invoking the AMF service.

S408. AMF sends the registration policy information to the terminal device.

The registration policy information includes the time interval for the terminal device to retry registration. The AMF can send the registration policy information to the terminal device through other devices. For example, the AMF can send the registration policy information to the terminal device through the access network device. Optionally, the AMF can notify the terminal device to re-register through the NEF and AF.

S409. AMF executes the first service according to the first strategy.

For example, the time interval for the terminal device to retry registration is 1s. The AMF determines according to the first policy: when the time interval between the registration request received from the terminal device again and the last registration request received from the terminal device does not exceed 1s, the received registration request is rejected.

Optionally, S410 to S411 may be further executed after S409 , which is indicated by dotted lines in FIG. 4 .

S410. AnLF sends a subscription notification to ReLF, where the subscription notification includes updated first information.

S411. The ReLF generates a new first policy based on the updated first information, and sends the updated first policy to the first AMF.

Each data source can periodically send raw data information to AnLF, which can then re-determine the first information based on the updated raw data information. To ensure that the policy recommended by ReLF can promptly prevent or mitigate signaling storms, AnLF can send updated first information to ReLF, which then updates the first policy based on the updated first information. The updated first policy is determined based on the latest raw data information collected by AnLF, and therefore can better prevent or mitigate signaling storms.

The communication method 400 can prevent or alleviate the signaling storm caused by multiple terminal devices collectively initiating registration requests, reduce network anomalies, and reduce the impact on normal services.

In the above embodiments provided by the present application, the method provided by the embodiment of the present application is introduced by taking the execution of the first network element and the third network element as an example. In the present application, each embodiment can be implemented independently or in combination based on certain internal connections; in each embodiment, different implementation methods can be implemented in combination or independently. In order to implement the various functions in the method provided by the above embodiments of the present application, the steps performed by each network element can be implemented by different functional entities that constitute each network element. In order to implement the various functions in the method provided by the above embodiments of the present application, each network element may include a hardware structure and/or a software module, and implement the above functions in the form of a hardware structure, a software module, or a hardware structure plus a software module. Whether one of the above functions is executed in the form of a hardware structure, a software module, or a hardware structure plus a software module depends on the specific application and design constraints of the technical solution.

Based on the same inventive concept as the method embodiment, the present embodiment provides a communication device. The following describes the communication device used to implement the above method in the present embodiment in conjunction with the accompanying drawings. The above content can be used in subsequent embodiments, and repeated content will not be repeated.

Figure 5 is a schematic block diagram of a communication device 500 provided in an embodiment of the present application. The communication device 500 can be any network element from the first network element to the fourth network element in the above-mentioned embodiments. For example, the communication device 500 can be the first network element; or, the communication device 500 is a chip (system) in the first network element; or, the communication device 500 is a software module of the first network element. The communication device 500 can implement the functions or steps implemented by the first network element in the above-mentioned various method embodiments. For another example, the communication device 500 can be the third network element as described above, and the third network element can be an NWDAF network element with ReLF and AnLF, wherein the ReLF and AnLF are independent or the ReLF and AnLF are combined; or, the third network element is an NWDAF with ReLF. Or, the communication device 500 is a chip (system) in the third network element; or, the communication device 500 is a software module of the third network element. The communication device 500 can implement the functions or steps implemented by the third network element in the above-mentioned various method embodiments. The communication device 500 can correspondingly implement the functions or steps implemented by the third network element in the above-mentioned various method embodiments.

The communication device 500 may include a processing module 510 and a transceiver module 520. Optionally, it may further include a storage module, which may be used to store instructions (codes or programs) and/or data. The storage module may be, for example, a memory. The processing module 510 and the transceiver module 520 may be coupled to the storage module. For example, the processing module 510 may read the instructions (codes or programs) and/or data in the storage module to implement the corresponding method. When the communication device 500 is a chip in the first network element or the third network element, the storage module may be a storage module in the chip, such as a register, a cache, etc. For example, the storage module may also be a storage module located outside the chip in a terminal device or a network device, such as a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM), etc. The above-mentioned units may be set independently or partially or fully integrated.

The processing module 510 can be a processor or controller, for example, a general-purpose central processing unit (CPU), a general-purpose processor, a digital signal processing (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a transistor logic device, a hardware component or any combination thereof. It can implement or execute the various exemplary logic blocks, modules and circuits described in conjunction with the disclosure of this application. The processor can also be a combination that implements computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and so on. The transceiver module 520 is a transceiver, an interface circuit, a bus, a pin or other possible communication interface for receiving signals from other devices. For example, when the device is implemented in the form of a chip, the transceiver module 520 is the interface circuit of the chip for receiving signals from other chips or devices, or the interface circuit of the chip for sending signals to other chips or devices.

In one implementation, the communication device 500 can implement the behaviors and functions of the third network element in the above-mentioned method embodiment. The communication device 500 can be a third network element, or a component (such as a chip or circuit) used in a third network element, or a chip or chipset in a third network element or a part of a chip used to perform the functions of the relevant method, or a software module capable of implementing the method executed by the third network element in the above-mentioned method (such as any communication method from communication method 200 to communication method 400), without limitation. For details, please refer to the relevant content of the above-mentioned method embodiment, which will not be repeated here.

For example, the transceiver module 520 is configured to receive a first message from a first network element, the first message being used to request a recommendation for a policy corresponding to a first service. The processing module 510 is configured to obtain first information, the first information comprising statistical information of at least one network element, the statistical information comprising information regarding service invocation by the at least one network element and/or information regarding service invocation by the at least one network element, the at least one network element including the first network element. The processing module 510 is further configured to trigger the transceiver module 520 to send a first policy to the first network element based on the statistical information of the at least one network element, the first policy comprising a policy corresponding to the first service.

As an optional implementation, the first service includes invoking a service of the second network element, and the processing module 510 is further configured to obtain at least one candidate network element serving the first service, wherein the at least one candidate network element includes the second network element, and the at least one network element includes at least one candidate network element.

As an optional implementation, the first message includes information about at least one candidate network element, and the information about the at least one candidate network element is used to indicate at least one of the type, service range, and slice information of the at least one candidate network element. The transceiver module 520 is specifically used to: send a second message and receive at least one identification information. The second message is used to request to obtain at least one candidate network element. The at least one identification information corresponds to the at least one candidate network element, and the at least one identification information is determined based on the information of the at least one candidate network element.

As an optional implementation manner, the transceiver module 520 is specifically used to: send a third message to the data analysis network element, where the third message includes an analysis ID and is used to request to obtain the first information.

As an optional implementation, the statistical information of at least one network element includes one or more of the following:

a rate and/or frequency at which at least one network element invokes a service within the first duration;

Prediction information of the rate and/or frequency at which at least one network element is called within a first time period; or,

The first time information is used to indicate a first duration.

As an optional implementation manner, the first information further includes prediction information of the signaling storm and/or an analysis ID corresponding to the first information.

As an optional implementation manner, the first service is a terminal device registration service, and a policy includes one or more of the following policies: a time interval for the terminal device to retry registration or a policy for calling a service of the first network element.

As an optional implementation, the first service includes calling the service of the second network element, and the first strategy includes one or more of the following strategies: a strategy for selecting the second network element, a strategy for calling the service of the second network element, or a strategy for calling the service of the first network element.

As an optional implementation manner, the first message includes a recommendation identifier, which is a service ID requested for recommendation.

As an optional implementation method, the first message also includes: the service scope of the first network element, identification information of the first network element or identification information of the set to which the first network element is located, and network slice information of the first network element.

As an optional implementation manner, the first message further includes: identification information of at least one candidate network element.

In one implementation, the communication device 500 can implement the behavior and functions of the first network element in the above-mentioned method embodiment. The communication device 500 can be the first network element, or a component (such as a chip or circuit) used in the first network element, or a chip or chipset in the first network element or a part of the chip used to perform the functions of the relevant method, or a software module that can implement the method executed by the first network element in the above-mentioned method (such as any communication method from communication method 200 to communication method 400), without limitation. For details, please refer to the relevant content of the above-mentioned method embodiment, which will not be repeated here.

For example, the transceiver module 520 is configured to send a first message to a third network element and receive a first policy. The first message is configured to request a policy corresponding to a first service. The first policy includes a policy corresponding to the first service, and the first policy is determined based on statistical information of at least one network element, where the at least one network element is related to the first service. The statistical information of the at least one network element includes information about the at least one network element invoking a service and/or information about the at least one network element having a service invoked.

As an optional implementation manner, the first message includes a recommendation identifier, which is a service ID requested for recommendation.

As an optional implementation method, the first message also includes: the service scope of the first network element, identification information of the first network element or identification information of the set to which the first network element is located, and network slice information of the first network element.

As an optional implementation, the first service includes invoking a service of a second network element, and the first message further includes: information about at least one candidate network element, where the information about the at least one candidate network element is used to indicate at least one of a type, a service scope, and slice information of the at least one candidate network element. The at least one candidate network element includes the second network element.

As an optional implementation manner, the first message further includes: identification information of at least one candidate network element.

As an optional implementation, the first service includes calling the service of the second network element, and the first strategy includes one or more of the following strategies: a strategy for selecting the second network element, a strategy for calling the service of the second network element, or a strategy for calling the service of the first network element.

As an optional implementation manner, the first service includes a terminal device registration service, and the first policy includes one or more of the following policies: a time interval for the terminal device to retry registration, or a policy for invoking a service of the first network element.

As an optional implementation, the transceiver module 520 is further configured to send registration policy information to the terminal device, where the registration policy information is used to indicate a time interval for the terminal device to retry registration.

In one implementation, the communication device 500 can implement the behavior and functions of the fourth network element in the above-mentioned method embodiment. The communication device 500 can be a fourth network element, or a component (such as a chip or circuit) used in the fourth network element, or a chip or chipset in the fourth network element or a part of the chip used to perform the functions of the relevant method, or a software module capable of implementing the method executed by the fourth network element in the above-mentioned method (such as any communication method from communication method 200 to communication method 400), without limitation. For details, please refer to the relevant content of the above-mentioned method embodiment, which will not be repeated here.

For example, the transceiver module 520 is configured to receive a third message requesting first information, where the first information includes statistical information of at least one network element, including information about the at least one network element invoking a service and/or information about the at least one network element's service being invoked. The processing module 510 is configured to send the first information based on raw data information obtained from multiple data sources. The multiple data sources include a network management system, and the raw data information indicates one or more of the following: load information of the at least one data source, signaling storm prediction information, or device-level flow control policy. The multiple data sources include a first core network element, and the raw data information indicates one or more of the following: the rate, success rate, or failure rate of service invocation by the first core network element; the rate, success rate, or failure rate of service invocation by the first core network element; the service type of the first core network element and/or the proportion of the first core network element's service type among multiple service types; the load and status of the first core network element; or behavior information of a terminal device.

When the communication device 500 is a chip-type device or circuit, the transceiver module may be an input/output circuit and/or a communication interface; the processing module may be an integrated processor or microprocessor or integrated circuit.

Figure 6 is a schematic block diagram of a communication device 600 provided in an embodiment of the present application. The communication device 600 can be the first network element, the third network element, or the fourth network element in the above-mentioned embodiment, or a chip (system) in the first network element, the third network element, or the fourth network element. In the embodiment of the present application, the chip system can be composed of a chip, or it can include a chip and other discrete devices. For specific functions, please refer to the description in the above-mentioned method embodiment.

The communication device 600 includes one or more processors 601, which are used to implement or support the communication device 600 to implement the functions of the first network element, the third network element or the fourth network element in the method provided in the embodiment of the present application. Please refer to the detailed description in the method example for details, which will not be repeated here. The processor 601 can also be called a processing unit or a processing module, which can implement certain control functions. The processor 601 can be a general-purpose processor or a dedicated processor. For example, it includes: a central processing unit, an application processor, a modem processor, a graphics processor, an image signal processor, a digital signal processor, a video codec processor, a controller, a memory, and/or a neural network processor. The central processing unit can be used to control the communication device 600 (such as a network device or a terminal device), execute software programs and/or process data. Different processors can be independent devices or integrated into one or more processors, for example, integrated into one or more dedicated integrated circuits.

In one design, the processor 601 may include a program 603 (sometimes also referred to as code or instructions), which may be executed on the processor 601 to cause the communication device 600 to perform the methods described in the above embodiments. In another possible design, the communication device 600 includes circuitry (not shown in FIG6 ) configured to implement the functions of the first network element, the third network element, or the fourth network element in the above embodiments.

In one design, the communication device 600 may include one or more memories 602 on which a program 604 (sometimes also referred to as code or instructions) is stored. The program 604 can be run on the processor 601 so that the communication device 600 performs the method described in the above method embodiment.

In one design, the processor 601 and/or the memory 602 may include an artificial intelligence (AI) module 606 and an AI module 608, each configured to implement AI-related functions. The AI module may be implemented using software, hardware, or a combination of software and hardware. For example, the AI module may include a RAN intelligent controller (RIC) module. For example, the AI module may be a near-real-time RIC or a non-real-time RIC.

In a possible design, data may also be stored in the processor 601 and/or the memory 602. The processor and the memory may be provided separately or integrated together.

In one possible design, the communication device 600 may further include a communication interface 605. The processor 601 may also be sometimes referred to as a processing unit, which controls the communication device 600. The communication interface 605 may also be sometimes referred to as a transceiver unit, a transceiver, a transceiver circuit, or a transceiver, etc., which is used to implement the transceiver function of the communication device 600.

The present application also provides a communication system. Specifically, the communication system includes at least one first network element, at least one second network element, and at least one third network element. Optionally, the communication system may also include at least one fourth network element and a terminal device. The first network element, the second network element, and the third network element are network elements used to implement the functions related to any of the communication methods 200 to 400 described above. For details, please refer to the relevant description in the above method embodiments and will not be repeated here.

A computer-readable storage medium is also provided in an embodiment of the present application, comprising instructions, which, when executed on a computer, enables the computer to execute a method executed by any of the first network element, the third network element, or the fourth network element in any of the communication methods 200 to 400 above.

A computer program product is also provided in an embodiment of the present application, including computer program code. When the computer program code is executed, the computer executes the method executed by any network element among the first network element, the third network element or the fourth network element in any communication method from the above-mentioned communication method 200 to the communication method 400.

An embodiment of the present application provides a chip system, which includes a processor and may also include a memory, for implementing the functions of any of the first network element, the third network element, or the fourth network element in any of the communication methods 200 to 400. The chip system may be composed of a chip or may include a chip and other discrete components.

To implement the functions of the communication device shown in Figures 5 and 6 above, embodiments of the present application further provide a chip including a processor for supporting the communication device in implementing the functions of any of the first network element, the third network element, or the fourth network element in the above method embodiments. In one possible design, the chip is connected to or includes a memory, and the memory is used to store computer programs, instructions, and data necessary for the communication device.

It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

Those skilled in the art will appreciate that the various illustrative logical blocks and steps described in conjunction with the embodiments disclosed herein can be implemented using electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

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

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

If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the part that essentially contributes to the technical solution of the present application or the part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as USB flash drives, mobile hard drives, ROM, RAM, magnetic disks or optical disks.

Obviously, those skilled in the art may make various changes and modifications to the present application without departing from the scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include these modifications and variations.

Claims (44)

A communication method, comprising: receiving a first message from a first network element, wherein the first message is used to request recommendation of a policy corresponding to a first service; Acquire first information, where the first information includes statistical information of at least one network element, the statistical information including information about the at least one network element calling a service and/or information about the at least one network element's service being called, the at least one network element including the first network element; A first policy is sent to the first network element according to the statistical information of the at least one network element, where the first policy includes a policy corresponding to the first service. The method according to claim 1, wherein the first service includes calling a service of a second network element, and the method further comprises: At least one candidate network element serving the first service is obtained, wherein the at least one candidate network element includes the second network element, and the at least one network element includes the at least one candidate network element. The method according to claim 2, wherein the first message includes information of the at least one candidate network element, the information of the at least one candidate network element is used to indicate at least one of a type, a service range, and slice information of the at least one candidate network element, and obtaining the at least one candidate network element includes: Sending a second message, where the second message includes information about the at least one candidate network element; At least one piece of identification information is received, where the at least one piece of identification information corresponds one-to-one with the at least one candidate network element, and the at least one piece of identification information is determined based on information of the at least one candidate network element. The method according to any one of claims 1 to 3, wherein obtaining the first information comprises: A third message is sent to the data analysis network element, where the third message includes an analysis identification ID and is used to request acquisition of the first information. The method according to any one of claims 1 to 4, wherein the statistical information of the at least one network element includes one or more of the following: The rate and/or frequency at which the at least one network element invokes a service within the first duration; Prediction information of the rate and/or frequency at which the at least one network element is called within the first duration; or, The first time information is used to indicate the first duration. The method according to claim 5, wherein the first information further includes one or more of the following: Signaling storm prediction information; The analysis ID corresponding to the first information. The method according to any one of claims 1 to 6, wherein the first service includes a terminal device registration service, and the first policy includes one or more of the following policies: The time interval for the terminal device to retry registration; The policy for invoking the service of the first network element. The method according to any one of claims 1 to 6, wherein the first service includes invoking a service of a second network element, and the first policy includes one or more of the following policies: selecting a policy for the second network element; a policy for invoking a service of the second network element; The policy for invoking the first network element service. The method according to any one of claims 1 to 8, wherein the first message includes a recommendation identifier, and the recommendation identifier is a service ID requested for recommendation. The method according to claim 9, wherein the first message further includes: the service scope of the first network element; identification information of the first network element or identification information of the set to which the first network element belongs; Network slice information of the first network element. The method according to claim 10, wherein the first message further includes: Identification information of the at least one candidate network element. A communication method, comprising: Sending a first message to a third network element, where the first message is used to request recommendation of a policy corresponding to the first service; Receive a first policy from the third network element, the first policy including a policy corresponding to the first service, the first policy being determined based on statistical information of at least one network element, the at least one network element being related to the first service, the statistical information including information of the at least one network element calling a service and/or information of the at least one network element's service being called. The method according to claim 12 is characterized in that the first message includes a recommendation identifier, and the recommendation identifier is a service ID requested for recommendation. The method according to claim 13, wherein the first message further includes: the service scope of the first network element; identification information of the first network element or identification information of the set to which the first network element belongs; Network slice information of the first network element. The method according to claim 14, wherein the first service includes invoking a service of a second network element, and the first message further includes: The information of the at least one candidate network element is used to indicate at least one of the type, service range and slice information of the at least one candidate network element, and the at least one candidate network element includes the second network element. The method according to claim 15, wherein the first message further includes: Identification information of the at least one candidate network element. The method according to any one of claims 12 to 16, wherein the first service includes invoking a service of a second network element, and the first policy includes one or more of the following policies: selecting a policy for the second network element; a policy for invoking a service of the second network element; The policy for invoking the first network element service. The method according to any one of claims 12 to 16, wherein the first service includes a terminal device registration service, and the first policy includes one or more of the following policies: The time interval for the terminal device to retry registration; The policy for invoking the service of the first network element. The method according to claim 18, further comprising: Sending registration policy information to the terminal device, where the registration policy information is used to indicate a time interval for the terminal device to retry registration. A communication method, comprising: receiving a third message, where the third message is used to request first information, where the first information includes statistical information of at least one network element, where the statistical information includes information about a service being called by the at least one network element and/or information about a service being called by the at least one network element; Sending the first information according to original data information obtained from multiple data sources; The multiple data sources include a network management system, and the original data information is used to indicate one or more of the following: load information of at least one of the data sources, signaling storm prediction information, or device-level flow control strategy; The multiple data sources include a first core network element, and the original data information is used to indicate one or more of the following: One or more of a rate, a success rate, or a failure rate of service invocation by the first core network element; one or more of a rate at which a service of the first core network element is invoked, a success rate, or a failure rate; a service type of the first core network element and/or a proportion of the service type of the first core network element in multiple service types; the load and status of the first core network element; Behavior information of terminal devices. A communication device, comprising: a transceiver module, configured to receive a first message from a first network element, wherein the first message is used to request recommendation of a policy corresponding to a first service; a processing module, configured to obtain first information, where the first information includes statistical information of at least one network element, the statistical information including information about the at least one network element invoking a service and/or information about the at least one network element's service being invoked, the at least one network element including the first network element; The transceiver module is further configured to send a first policy to the first network element according to the statistical information of the at least one network element, where the first policy includes a policy corresponding to the first service. The apparatus according to claim 21, wherein the first service includes calling a service of a second network element, and the processing module is further configured to: At least one candidate network element serving the first service is obtained, wherein the at least one candidate network element includes the second network element, and the at least one network element includes the at least one candidate network element. The apparatus according to claim 22, wherein the first message includes information of the at least one candidate network element, the information of the at least one candidate network element is used to indicate at least one of a type, a service range, and slice information of the at least one candidate network element, and the transceiver module is specifically configured to: Sending a second message, where the second message includes information about the at least one candidate network element; At least one piece of identification information is received, where the at least one piece of identification information corresponds one-to-one with the at least one candidate network element, and the at least one piece of identification information is determined based on information of the at least one candidate network element. The device according to any one of claims 21 to 23, wherein the transceiver module is specifically configured to: A third message is sent to the data analysis network element, where the third message includes an analysis identification ID and is used to request acquisition of the first information. The apparatus according to any one of claims 21 to 24, wherein the statistical information of the at least one network element includes one or more of the following: The rate and/or frequency at which the at least one network element invokes a service within the first duration; Prediction information of the rate and/or frequency at which the at least one network element is called within the first duration; or, The first time information is used to indicate the first duration. The apparatus according to claim 25, wherein the first information further comprises one or more of the following: Signaling storm prediction information; The analysis ID corresponding to the first information. The apparatus according to any one of claims 21 to 26, wherein the first service includes a terminal device registration service, and the first policy includes one or more of the following policies: The time interval for the terminal device to retry registration; The policy for invoking the service of the first network element. The apparatus according to any one of claims 21 to 26, wherein the first service includes invoking a service of a second network element, and the first policy includes one or more of the following policies: selecting a policy for the second network element; a policy for invoking a service of the second network element; The policy for invoking the first network element service. The device according to any one of claims 21 to 28 is characterized in that the first message includes a recommendation identifier, and the recommendation identifier is a service ID requested for recommendation. The apparatus according to claim 29, wherein the first message further comprises: the service scope of the first network element; identification information of the first network element or identification information of the set to which the first network element belongs; Network slice information of the first network element. The apparatus according to claim 30, wherein the first message further comprises: Identification information of the at least one candidate network element. A communication device, comprising: A processing module, configured to determine a first message, wherein the first message is used to request recommendation of a policy corresponding to a first service; A transceiver module is used to send the first message to a third network element and receive a first policy from the third network element, where the first policy includes a policy corresponding to the first service. The first policy is determined based on statistical information of at least one network element, and the at least one network element is related to the first service. The statistical information includes information about the at least one network element calling a service and/or information about the at least one network element's service being called. The device as described in claim 32 is characterized in that the first message includes a recommendation identifier, and the recommendation identifier is a service ID requested for recommendation. The apparatus according to claim 33, wherein the first message further comprises: the service scope of the first network element; identification information of the first network element or identification information of the set to which the first network element belongs; Network slice information of the first network element. The apparatus according to claim 34, wherein the first service includes invoking a service of a second network element, and the first message further includes: The information of the at least one candidate network element is used to indicate at least one of the type, service range and slice information of the at least one candidate network element, and the at least one candidate network element includes the second network element. The apparatus according to claim 35, wherein the first message further comprises: Identification information of the at least one candidate network element. The apparatus according to any one of claims 32 to 36, wherein the first service includes invoking a service of a second network element, and the first policy includes one or more of the following policies: selecting a policy for the second network element; a policy for invoking a service of the second network element; The policy for invoking the first network element service. The apparatus according to any one of claims 32 to 36, wherein the first service includes a terminal device registration service, and the first policy includes one or more of the following policies: The time interval for the terminal device to retry registration; The policy for invoking the service of the first network element. The device according to claim 38, wherein the transceiver module is further configured to: Sending registration policy information to the terminal device, where the registration policy information is used to indicate a time interval for the terminal device to retry registration. A communication device, comprising: a transceiver module, configured to receive a third message and send first information based on raw data information obtained from multiple data sources, wherein the third message is used to request first information, wherein the first information includes statistical information of at least one network element, the statistical information including information about the at least one network element calling a service and/or information about the at least one network element's service being called; the multiple data sources include a network management system, and the raw data information is used to indicate one or more of the following: load information of at least one of the data sources, signaling storm prediction information, or a device-level flow control policy; The multiple data sources include a first core network element, and the original data information is used to indicate one or more of the following: One or more of a rate, a success rate, or a failure rate of service invocation by the first core network element; one or more of a rate at which a service of the first core network element is invoked, a success rate, or a failure rate; a service type of the first core network element and/or a proportion of the service type of the first core network element in multiple service types; the load and status of the first core network element; Behavioral information of terminal devices; A processing module is used to determine the first information. A communication device, characterized in that the communication device includes a processor and a memory, the memory is used to store a computer program, and the processor is used to execute the computer program stored on the memory, so that the communication device performs the method according to any one of claims 1 to 11; or, the processor is used to execute the computer program stored on the memory, so that the communication device performs the method according to any one of claims 12 to 19; or, the processor is used to execute the computer program stored on the memory, so that the communication device performs the method according to claim 20. A chip system, characterized in that the chip system includes: a processor and an interface, the processor is used to call and run instructions from the interface, when the processor executes the instructions, implements the method according to any one of claims 1 to 11; or, when the processor executes the instructions, implements the method according to any one of claims 12 to 19, or, when the processor executes the instructions, implements the method according to claim 20. A computer-readable storage medium, characterized in that the computer-readable storage medium is used to store a computer program, which, when the computer program is run on a computer, causes the computer to perform the method according to any one of claims 1 to 11, or, when the computer program is run on a computer, causes the computer to perform the method according to any one of claims 12 to 19, or, when the computer program is run on a computer, causes the computer to perform the method according to claim 20. A computer program product, characterized in that the computer program product includes a computer program, which, when run on a computer, causes the computer to perform the method according to any one of claims 1 to 11; or, when run on a computer, causes the computer to perform the method according to any one of claims 12 to 19; or, when run on a computer, causes the computer to perform the method according to claim 20.