Communication method and apparatus

Abstract

The present application relates to the technical field of communications, and provides a communication method and apparatus, which are used for achieving interaction between an LLOF network element and a service-based instance. The method comprises: a first network element sends a first message to a second network element, and the second network element receives the first message from the first network element. The first message requests to register a first configuration of a first network function to the second network element. The first network element is used for providing link load orchestration, and the first configuration of the first network function comprises information of the first network element. The second network element stores the first configuration. The second network element sends a second message to the first network element, and the first network element receives the second message from the second network element. The second message indicates that the first configuration of the first network function has been successfully registered.

Description

Communication method and device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on March 28, 2024, with application number 202410378498.9 and application name “Communication Method and Device,” the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communications, and in particular to a communication method and device. Background Art

[0003] In the current fifth-generation (5G) mobile communication system, or future mobile communication systems such as 5.5G and 6th-generation (6G) mobile communication systems, the introduction of a link load orchestration function (LLOF) network element is being considered to support the routing of user-level or service-level non-service messages between service-oriented instances and non-service-oriented network elements. In other words, the LLOF network element can decouple the message transmission between non-service-oriented network elements and service-oriented instances, making communication more flexible.

[0004] However, the interaction between LLOF network elements and service-oriented instances is not currently defined, and how to achieve interaction is an issue that needs to be resolved. Summary of the Invention

[0005] The embodiments of the present application provide a communication method and apparatus to implement interaction between an LLOF network element and a service-based instance.

[0006] To achieve the above objectives, this application adopts the following technical solutions:

[0007] In a first aspect, a communication method is provided, comprising: a first network element sending a first message to a second network element, and the second network element receiving the first message from the first network element. The first message requests registration of a first configuration of a first network function with the second network element, the first network element being configured to provide link load orchestration, the first configuration of the first network function including information of the first network element. The second network element saves the first configuration. The second network element sends a second message to the second network element, and the first network element receives the second message from the second network element. The second message indicates that the first configuration of the first network function has been successfully registered.

[0008] It should be understood that the first network element can provide link load orchestration, or provide link load orchestration functions / services, and can specifically be an LLOF network element, or in future communication systems, the LLOF network element can also be replaced by any possible network element, or in other words, any network element that can implement / provide link load orchestration functions / services can be understood as the LLOF network element in the embodiment of the present application. The second network element can support the configuration of the registration network function and the discovery of the network function, such as the NRF network element in the 5GS mentioned above, or in future communication systems, the NRF network element can also be replaced by any possible network element, such as an LLOF network element with the capabilities of an NRF network element, or with the configuration of the registration network function and the ability to discover the network function. The first network function can be any possible network function, such as a service instance.

[0009] From this, it can be seen that the configuration of the first network function (such as the first configuration of NF) includes the information of the first network element (such as LLOF network element). When the first configuration is registered by the first network element to the second network element (such as NRF network element), if the second network element discovers the first network function based on the requester (such as the service-based instance) and provides the first configuration to the requester, the requester can also obtain the information of the first network element through the first configuration, thereby being able to interact with the first network element, that is, realizing the interaction between the LLOF network element and the service-based instance.

[0010] In a possible design scheme, the information of the first network element may include at least one of the following: address information of the first network element, or identification-related information of the first network element.

[0011] Optionally, the address information of the first network element may be the Internet Protocol IP address of the first network element, such as one or more IPv4 addresses, IPv6 addresses, etc.; or, the address information of the first network element may also be the fully qualified domain name FQDN of the first network element; or, the address information of the first network element may also be information used to indicate the address of the first network element, such as an indication cell, and there is no limitation on the specific implementation.

[0012] Optionally, the identification-related information of the first network element may include at least one of the following: information used to identify the set to which the first network element belongs, or information used to identify the first network element. For example, the information used to identify the set to which the first network element belongs may be the identifier of the set, that is, an identifier at the set granularity; the information used to identify the first network element may be the identifier of the first network element, that is, an identifier at the network element / device / instance granularity.

[0013] It can be seen that the information contained in the information of the first network element is mainly used for other network functions to identify and access the first network element, so that the interaction between the first network element (LLOF network element) and other network functions (service instances) can be realized.

[0014] In one possible design, a first network function is registered with a first network element. For example, registering the first network function with the first network element may include the first network element acquiring a second configuration of the first network function. The second configuration may include at least one of the following: an identifier of the first network function, an address of the first network function, or a type of the first network function, so that the first network element can provide link load orchestration for the first network function based on the second configuration.

[0015] Optionally, the method described in the first aspect may further include: the first network element may determine the first configuration of the first network function based on the second configuration of the first network function and the information of the first network element. The first configuration may include all or part of the second configuration. For example, the first network element may replace the information related to the first network function in the second configuration with the information of the first network element, such as replacing the address information of the first network function with the address information of the first network element to obtain the first configuration; or the first network element may also add the information of the first network element to the second configuration to obtain the first configuration. Of course, the first network element may also perform other processing on the second configuration, such as discarding some redundant information related to the first network function in the second configuration, which is not specifically limited.

[0016] In one possible design scheme, the method described in the first aspect further includes: the second network function sends a request message to the second network element, and the second network element receives the request message from the second network function, wherein the request message indicates that the second network function requests to discover a network function that can provide services for the second network function. The second network element can send the first configuration of the first network function to the second network function based on the request message, and the first network function can provide services for the second network function. That is, after the first network element registers its own information with the second network element through the first configuration, if the second network element discovers that the first network function can provide services for the second network function, the second network element can reuse the first configuration and pass the information of the first network element to the second network function. In this way, the second network function can request the first network function to provide services through the first network element.

[0017] Optionally, when the first configuration includes information related to the identifier of the first network element, the method described in the first aspect may further include: the second network function sending information related to the identifier of the first network element to the second network element, and the second network element receiving information related to the identifier of the first network element from the second network function. The second network element sends the configuration of the first network element to the second network function based on the information related to the identifier of the first network element, and the second network function receives the configuration of the first network element returned by the second network element based on the information related to the identifier of the first network element. The configuration of the first network element includes address information of the first network element. In this way, the second network function can request the first network function to provide a service through the first network element based on the address information of the first network element.

[0018] Furthermore, the method of the first aspect may further include: the second network element may select the first network element based on the information used to identify the first network element, that is, the first network element may be directly selected, which can reduce the overhead of selecting the network element. Alternatively, the second network element may select a first network element from a set of network elements based on the information used to identify the set of network elements, where multiple network elements in the set of network elements are capable of providing link load orchestration. That is, the second network element selects a first network element from the set that the second network element deems more suitable, so that the link load orchestration service provided by the first network element can better match the requirements of the second network function.

[0019] Optionally, the second network function can request the first network function to provide services through the first network element, including: the second network function sends a request message to the first network element, and the first network element receives the request message from the second network function, where the request message indicates that the second network function requests the first network function to provide services. In response to the request message, the first network element determines whether the first network element and the second network function belong to the same data center. If the first network element and the second network function belong to the same data center, the first network element provides the first network function's services to the second network function on behalf of the first network function, and accordingly, the second network function obtains the first network function's services through the first network element. Alternatively, if the first network element and the second network function belong to different data centers, the first network element triggers a redirection process.

[0020] Furthermore, the first network element triggers a redirection process, including: the first network element instructs the second network function that redirection is required, and accordingly, the second network function redirects according to the instruction of the first network element. Or; the first network element sends a request message to the third network element, or in other words, the first network element instructs the third network element to act as an agent of the first network function to provide the service of the first network function to the second network function. The request message may indicate that the second network function requests the first network function to provide services. The third network element can provide link load orchestration, such as a link load orchestration function network element. The second network function and the third network element belong to the same data center. In this way, the third network element can provide the service of the first network function to the second network function through the first network element. In addition, the device form / function of the third network element mentioned in this application may be similar to that of the first network element, which can be understood by reference and will not be repeated.

[0021] It can be understood that the redirection process can be used to rediscover the network function that can serve the second network function for the second network function. Due to the hardware isolation that may exist between different DCs, the LLOF and the service instance may not be able to interact, or different DCs may be geographically far apart, resulting in a long delay in the interaction between the LLOF and the service instance, which cannot meet business needs. Therefore, the first network element can rediscover the network function that can serve the second network function for the second network function by triggering the redirection process. For example, the network element corresponding to the network function (such as the LLOF network element) needs to belong to the same DC as the second network element function.

[0022] Furthermore, the method described in the first aspect may further include: the first network element may determine, from a set of network elements to which the first network element belongs, a third network element belonging to the same data center as the second network function, where multiple network elements within the set of network elements are capable of providing link load orchestration. The multiple network elements include the third network element, and the first network function is registered with each of the multiple network elements. In other words, the first network element may determine, from network elements that support link load orchestration, the third network element belonging to the same data center as the second network function, thereby avoiding redundant overhead caused by the first network element traversing network elements that do not support link load orchestration.

[0023] It can also be understood that the embodiments of the present application do not limit the way in which the first network element perceives the data center.

[0024] Furthermore, the method described in the first aspect may further include: the first network element obtaining a third configuration of the first network function, where the third configuration may include information about the third network element, such as identification information and / or address information of the third network element. For example, the first network element may obtain the third configuration from the second network element or locally on the first network element, without specific limitation. The first network element sends the third configuration to the second network function, and the second network function receives the third configuration from the first network element accordingly, so that the second network function can subsequently interact directly with the third network element based on the information from the third network element, without going through the first network element, thereby improving communication efficiency.

[0025] In a possible design scheme, the method described in the first aspect may also include: the second network function sends a request message to the first network element, and accordingly, the first network element receives the request message from the second network function. The request message indicates that the second network function requests to discover a network function that can provide services for the second network function. In response to the request message, the first network element obtains the first configuration of the first network function. The first network element sends the first configuration to the second network function, and the second network function receives the first configuration from the first network element. The first network function can provide services for the second network function. In this way, the second network function requests the first network function to provide services. That is to say, when the first network element has the capabilities of an NRF network element, the second network function can not only request the second network element, but also request the first network element to discover a network function that can provide services for it. The specific selection can be flexibly made according to actual needs.

[0026] Optionally, the first network element obtains the first configuration of the first network function, including: the first network element obtains the first configuration locally from the first network element to avoid communication overhead; or the first network element obtains the first configuration from the second network element. For example, when the first network element does not find a configuration that matches the requirements of the second network function locally, the first network element can send a request message to the second network element, and accordingly, the second network element receives the request message from the first network element, where the request message instructs the second network function to request the discovery of a network function that can provide services for the second network function. The second network element can send the first configuration to the first network element based on the request message, and accordingly, the first network element can receive the first configuration from the second network element, that is, the first configuration that matches the requirements of the second network function can be finally obtained.

[0027] Optionally, the method described in the first aspect may further include: registering the second network function with the first network element. For example, the second network function sends its configuration to the first network element. This allows the first network element to provide link load orchestration not only for the first network function but also for the second network function, thereby improving the efficiency of link load orchestration services.

[0028] It will be understood that the above example uses the first network element providing the first configuration to the second network function, which is not intended to be limiting. For example, when the second network function sends a request message to the first network element, the first network element can also obtain the third configuration of the first network function. The third configuration may include information about the third network element. The third network element provides link load orchestration, such as being able to provide link load orchestration to the first network function. In other words, the first network function can be registered not only with the first network element, but also with the third network element, that is, an NF instance can be registered with multiple LLOF network elements respectively. In this case, the third network element and the second network function may belong to the same data center or different data centers. The first network element can determine whether the third network element and the second network function belong to the same data center, and then trigger the redirection process. Alternatively, the first network element may not make a judgment and only forward the message. The specific implementation is not limited.

[0029] According to a second aspect, a communication method is provided. The method is applied to a first network element, and includes: the first network element sending a first message to a second network element, and receiving a second message from the second network element. The first message requests registration of a first configuration of a first network function with the second network element, the first network element being configured to provide link load orchestration, the first configuration of the first network function including information about the first network element. The second message indicates that the first configuration of the first network function has been successfully registered.

[0030] In a possible design scheme, the information of the first network element may include at least one of the following: address information of the first network element, or identification-related information of the first network element.

[0031] Optionally, the identification-related information of the first network element may include at least one of the following: information used to identify the set to which the first network element belongs, or information used to identify the first network element.

[0032] In one possible design, the first network function registers with the first network element. For example, the first network function registering with the first network element includes the first network element acquiring a second configuration of the first network function. The second configuration includes at least one of the following: an identifier of the first network function, an address of the first network function, or a type of the first network function.

[0033] Optionally, the method described in the second aspect may further include: the first network element may determine the first configuration of the first network function based on the second configuration of the first network function and the information of the first network element.

[0034] In a possible design scheme, the method described in the second aspect may also include: the first network element receives a request message from the second network function, the request message indicating that the second network function requests the first network function to provide services; in response to the request message, the first network element determines whether the first network element and the second network function belong to the same data center; if the first network element and the second network function belong to the same data center, the first network element acts on behalf of the first network function to provide the services of the first network function to the second network function; if the first network element and the second network function belong to different data centers, the first network element triggers a redirection process.

[0035] Optionally, the first network element triggers the redirection process, including: the first network element instructs the second network function that redirection is required; or; the first network element sends a request message to the third network element, the request message instructs the second network function to request the first network function to provide services, the third network element provides link load orchestration, and the second network function and the third network element belong to the same data center.

[0036] Furthermore, the method described in the second aspect may further include: the first network element determining, from a set of network elements to which the first network element belongs, a third network element that belongs to the same data center as the second network function, wherein the plurality of network elements in the set of network elements all provide link load orchestration. For example, the plurality of network elements includes the third network element, and the first network function is registered with each of the plurality of network elements.

[0037] Furthermore, the method described in the second aspect may further include: the first network element obtaining a third configuration of the first network function, wherein the third configuration includes information about the third network element; and the first network element sending the third configuration to the second network function. For example, the first network element obtaining the third configuration of the first network function includes: the first network element obtaining the third configuration from the second network element or locally from the first network element.

[0038] In one possible design scheme, the method described in the second aspect may also include: the first network element receives a request message from the second network function, the request message instructing the second network function to request to discover a network function that can provide services for the second network function; in response to the request message, the first network element obtains a first configuration of the first network function, and the first network function can provide services for the second network function; the first network element sends the first configuration to the second network function.

[0039] Optionally, the second network function is registered with the first network element.

[0040] Optionally, the first network element obtains the first configuration of the first network function, including: the first network element obtains the first configuration from the second network element or the first network element locally.

[0041] It can be understood that the technical effects of the method described in the second aspect can also refer to the relevant introduction of the method described in the first aspect above, and will not be repeated here.

[0042] According to a third aspect, a communication method is provided. The method is applied to a second network element, and includes: the second network element receiving a first message from a first network element, saving a first configuration, and then sending a second message to the second network element. The first message requests registration of a first configuration of a first network function with the second network element, the first network element providing link load orchestration, the first configuration including information about the first network element. The second message indicates successful registration of the first configuration.

[0043] In a possible design scheme, the information of the first network element includes at least one of the following: address information of the first network element, or identification-related information of the first network element.

[0044] Optionally, the identification-related information of the first network element includes at least one of the following: information used to identify the set to which the first network element belongs, or information used to identify the first network element.

[0045] In one possible design scheme, the method described in the third aspect may also include: the second network element receives a request message from the second network function, the request message indicating that the second network function requests to discover a network function that can provide services for the second network function; the second network element sends the first configuration of the first network function to the second network function based on the request message, and the first network function can provide services for the second network function.

[0046] Optionally, in the case where the first configuration includes identification-related information of the first network element, the method described in the third aspect may further include: the second network element receives identification-related information of the first network element from the second network function; the second network element sends the configuration of the first network element to the second network function based on the identification-related information of the first network element, and the configuration of the first network element includes the address information of the first network element.

[0047] Furthermore, the method described in the third aspect may also include: the second network element may select the first network element based on the information used to identify the first network element; or; the second network element may select the first network element in the network element set based on the information used to identify the network element set, and multiple network elements in the network element set can provide link load orchestration.

[0048] In one possible design scheme, the method described in the third aspect may also include: the second network element receives a request message from the first network element, the request message indicating that the second network function requests to discover a network function that can provide services for the second network function; the second network element sends the first configuration of the first network function to the first network element based on the request message, and the first network function can provide services for the second network function.

[0049] It can be understood that the technical effects of the method described in the third aspect can also refer to the relevant introduction of the method described in the first aspect above, and will not be repeated here.

[0050] In a fourth aspect, a communication method is provided, which is applied to a second network function and includes: the second network function sending a request message to a second network element, and receiving a first configuration of a first network function returned by the second network element in response to the request message. The request message indicates that the second network function is requesting to discover a network function that can provide services to the second network function, that the first network function can provide services to the second network function, that the first configuration includes information about the first network element, and that the first network element provides link load orchestration. In this manner, the second network function requests the first network function to provide services through the first network element.

[0051] In a possible design scheme, the information of the first network element includes at least one of the following: address information of the first network element, or identification-related information of the first network element.

[0052] Optionally, the identification-related information of the first network element includes at least one of the following: information used to identify the set to which the first network element belongs, or information used to identify the first network element.

[0053] Furthermore, in the case where the first configuration includes identification-related information of the first network element, the method described in the fourth aspect may further include: the second network function sending the identification-related information of the first network element to the second network element; the second network function receiving the configuration of the first network element returned by the second network element based on the identification-related information of the first network element, where the configuration of the first network element includes the address information of the first network element. On this basis, the second network function requests the first network function to provide a service through the first network element, including: the second network function requesting the first network function to provide a service through the first network element based on the address information of the first network element.

[0054] Furthermore, the second network function sends identification-related information of the first network element to the second network element, including: the second network function sends information used to identify the first network element to the second network element; or, the second network function sends information used to identify the network element set to the second network element.

[0055] In one possible design scheme, the second network function requests the first network function to provide services through the first network element, including: the second network function sends a request message to the first network element, where the request message instructs the second network function to request the first network function to provide services; the second network function obtains the services of the first network function through the first network element proxy service discovery, or the second network function redirects according to the instructions of the first network element.

[0056] It can be understood that the technical effects of the method described in the fourth aspect can also refer to the relevant introduction of the method described in the first aspect above, and will not be repeated here.

[0057] In a fifth aspect, a communication method is provided, which is applied to a second network function. The method includes: the second network function sends a request message to a first network element, and receives a first configuration of the first network function from the first network element. The request message indicates that the second network function requests discovery of a network function that can provide services to the second network function, the first network element provides link load orchestration, and the first network function is capable of providing services to the second network function. In this manner, the second network function requests the first network function to provide services.

[0058] In one possible design, the method of aspect 5 may further include: registering the second network function with the first network element. For example, registering the second network function with the first network element includes: the second network function sending a configuration of the second network function network element to the first network element.

[0059] It can be understood that the technical effects of the method described in the fifth aspect can also refer to the relevant introduction of the method described in the first aspect above, and will not be repeated here.

[0060] In a sixth aspect, a communication method is provided, the method comprising: a first network element sending a first message to a second network element, the second network element receiving the first message from the first network element. The first network element provides link load orchestration, and the first message requests that the configuration of the first network element be registered with the second network element. The second network element saves the configuration of the first network element. The second network element sends a second message to the second network element, and the first network element receives the second message from the second network element. The second message indicates that the configuration of the first network element has been successfully registered.

[0061] It should be understood that the first network element can provide link load orchestration, or provide link load orchestration / service, and can specifically be an LLOF network element, or in future communication systems, the LLOF network element can also be replaced by any possible network element, or in other words, any network element that can implement / provide link load orchestration / service can be understood as the LLOF network element in the embodiment of the present application. The second network element can support the configuration of the registration network function and the discovery of the network function, such as the NRF network element in the 5GS mentioned above, or in future communication systems, the NRF network element can also be replaced by any possible network element, such as an LLOF network element with the capabilities of an NRF network element, or with the configuration of the registration network function and the ability to discover the network function. The first network function can be any possible network function, such as a service instance.

[0062] Therefore, the first network element can directly register its configuration with the second network element, and the registration is successful. Other network functions (such as service-based instances) can discover the first network element through the second network element and obtain the configuration of the first network element, thereby being able to interact with the first network element. In other words, interaction between the LLOF network element and the service-based instance is realized.

[0063] In one possible design, the method described in aspect 6 further includes: the second network function sends a request message to the second network element, and the second network element receives the request message from the second network function, the request message instructing the second network function to request discovery of a network function that can provide services for the second network function. The second network element can send the configuration of the first network element to the second network function based on the request message, and the second network function receives the configuration of the first network element from the second network element. The first network element can provide link load orchestration for the first network function, and the first network function can provide services for the second network function. In this way, the second network function requests the first network function to provide services through the first network element.

[0064] In one possible design scheme, the method described in aspect 6 may further include: the second network function sends a request message to the first network element, and accordingly, the first network element receives the request message from the second network function. The request message indicates that the second network function requests to discover a network function that can provide services for the second network function. In response to the request message, the first network element obtains the configuration of the first network element. The first network element sends the configuration of the first network element to the second network function, and the second network function receives the configuration of the first network element from the first network element. The first network element can provide link load orchestration for the first network function, and the first network function can provide services for the second network function. In this way, the second network function requests the first network function to provide services through the first network element.

[0065] In a seventh aspect, a communication method is provided, applied to a first network element, the method comprising: the first network element sending a first message to a second network element, and the second network element receiving the first message from the first network element. The first network element provides link load orchestration, and the first message requests that a configuration of the first network element be registered with the second network element. The first network element receives a second message from the second network element. The second message indicates that the configuration of the first network element has been successfully registered.

[0066] In an eighth aspect, a communication method is provided, applied to a second network element, the method comprising: the second network element receiving a first message from a first network element. The first network element provides link load orchestration, and the first message requests that the configuration of the first network element be registered with the second network element. The second network element stores the configuration of the first network element. The second network element sends a second message to the second network element. The second message indicates that the configuration of the first network element has been successfully registered.

[0067] In a ninth aspect, a communication method is provided, which is applied to a second network function and includes: the second network function sending a request message to a second network element, and receiving a configuration of a first network element returned by the second network element in response to the request message. The request message indicates that the second network function is requesting to discover a network function capable of providing services to the second network function, that the first network element is capable of providing link load orchestration for the first network function, and that the first network function is capable of providing services to the second network function. In this manner, the second network function requests the first network function to provide services through the first network element.

[0068] In a tenth aspect, a communication method is provided, which is applied to a second network function, the method comprising: the second network function sending a request message to a first network element, and receiving a first network element configuration from the first network element. The request message indicates that the second network function is requesting to discover a network function that can provide services to the second network function, that the first network element can provide link load orchestration for the first network function, and that the first network function can provide services to the second network function. In this manner, the second network function requests the first network function to provide services through the first network element.

[0069] In an eleventh aspect, a communication device is provided, comprising a module for executing the method described in any one of the first to tenth aspects.

[0070] In one possible design solution, the communication device described in the eleventh aspect may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver may be used for the communication device described in the eleventh aspect to communicate with other communication devices.

[0071] In one possible design, the communication device described in the eleventh aspect may further include a memory. The memory may be integrated with the processor or provided separately. The memory may be used to store instructions related to the method of any one of the first to tenth aspects.

[0072] In an embodiment of the present application, the communication device described in the eleventh aspect may be a network device, or a chip (system) or other parts or components that can be set in the network device, or a device that includes the network device.

[0073] It can be understood that the technical effects of the device described in the eleventh aspect can also refer to the relevant introduction of the method in any of the first to tenth aspects above, and will not be repeated here.

[0074] In a twelfth aspect, a communication device is provided, comprising: a processor coupled to a memory, the processor configured to execute instructions stored in the memory, so that the communication device executes the method described in any one of the first to tenth aspects.

[0075] In one possible design solution, the communication device described in aspect 12 may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver may be used for the communication device described in aspect 12 to communicate with other communication devices.

[0076] In an embodiment of the present application, the communication device described in aspect 12 may be the network device described in any one of aspects 1 to 10, or a chip (system) or other parts or components that may be set in the network device, or a device that includes the network device.

[0077] In addition, the technical effects of the communication device described in the twelfth aspect can refer to the technical effects of the methods described in any one of the first to tenth aspects, and will not be repeated here.

[0078] In the thirteenth aspect, a communication device is provided, comprising: a processor and a memory; the memory is used to store instructions, and when the processor executes the instructions, the communication device executes the method described in any one of the first to tenth aspects.

[0079] In one possible design solution, the communication device described in the thirteenth aspect may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver may be used for the communication device described in the tenth aspect to communicate with other communication devices.

[0080] In an embodiment of the present application, the communication device described in aspect 13 may be the network device described in any one of aspects 1 to 10, or a chip (system) or other parts or components that may be set in the network device, or a device that includes the network device.

[0081] In addition, the technical effects of the communication device described in the thirteenth aspect can refer to the technical effects of the methods described in any one of the first to tenth aspects, and will not be repeated here.

[0082] In a fourteenth aspect, a chip is provided, comprising: a controller and an interface circuit, wherein the controller is used to interact with other devices through the interface circuit to execute the method described in any one of aspects one to ten.

[0083] According to a fifteenth aspect, a communication system is provided, wherein the communication system includes a network element for executing the method according to the first aspect, or the communication system includes a network element for executing the method according to the sixth aspect.

[0084] In the sixteenth aspect, a computer-readable storage medium is provided, which includes a computer program or instruction stored therein, and when the computer program or instruction is executed, the method described in any one of the first to tenth aspects is executed.

[0085] In the seventeenth aspect, a computer program product is provided, comprising a computer program or instructions, which, when executed, enables the method described in any one of the first to tenth aspects to be executed. BRIEF DESCRIPTION OF THE DRAWINGS

[0086] Figure 1 is a schematic diagram of the 5G system architecture;

[0087] FIG2 is a schematic diagram of the LLOF architecture;

[0088] Figure 3 is a schematic diagram of the process of network element registration;

[0089] Figure 4 is a schematic diagram of the process of network element discovery;

[0090] FIG5 is a schematic diagram of the architecture of a communication system provided in an embodiment of the present application;

[0091] FIG6 is a flow chart of a communication method according to an embodiment of the present application;

[0092] FIG7 is a second flow chart of the communication method provided in an embodiment of the present application;

[0093] FIG8 is a third flow chart of the communication method provided in an embodiment of the present application;

[0094] FIG9 is a fourth flow chart of a communication method according to an embodiment of the present application;

[0095] FIG10 is a first structural diagram of a communication device provided in an embodiment of the present application;

[0096] FIG11 is a second structural diagram of the communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0097] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as wireless network (Wi-Fi) systems, vehicle to everything (V2X) communication systems, device-to-device (D2D) communication systems, Internet of Vehicles communication systems, fourth-generation (4G) mobile communication systems, such as long-term evolution (LTE) systems, world-wide interoperability for microwave access (WiMAX) communication systems, fifth-generation (5G) mobile communication systems, such as new radio (NR) systems, and future communication systems, such as 5.5G and sixth-generation (6G) mobile communication systems.

[0098] For ease of understanding, the technical terms involved in this application are first introduced below.

[0099] 1. 5GS:

[0100] Figure 1 is a schematic diagram of the 5GS architecture. As shown in Figure 1, the 5GS includes an access network (AN) and a core network (CN), and may also include terminals.

[0101] The terminal may be a terminal with transceiver functions, or a chip or chip system that can be provided in the terminal. The terminal may also be referred to as user equipment (UE), access terminal, subscriber unit, user station, mobile station (MS), mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device. The terminal in the embodiments of the present application can be a mobile phone, a cellular phone, a smart phone, a tablet computer, a wireless data card, a personal digital assistant (PDA), a wireless modem, a handset, a laptop computer, a machine type communication (MTC) terminal, a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, a vehicle-mounted terminal, a road side unit (RSU) with terminal function, etc. The terminal of the present application may also 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.

[0102] The AN implements access-related functions, providing network access for authorized users and determining transmission links of varying quality for user data based on user level and service requirements. The AN forwards control signals and user data between terminals and the CN. The AN may include access network equipment, also known as radio access network (RAN) equipment.

[0103] The CN is primarily responsible for maintaining mobile network subscription data and providing terminal functions such as session management, mobility management, policy management, and security authentication. The CN primarily includes all or part of the following functions: user plane function (UPF), authentication server function (AUSF), access and mobility management function (AMF), session management function (SMF), network slice selection function (NSSF), network exposure function (NEF), network repository function (NRF), policy control function (PCF), unified data management (UDM), unified data repository (UDR), and application function (AF).

[0104] As shown in Figure 1, the UE accesses the 5G network through the RAN equipment. The UE communicates with the AMF through the N1 interface (referred to as N1); the RAN communicates with the AMF through the N2 interface (referred to as N2); the RAN communicates with the UPF through the N3 interface (referred to as N3); the SMF communicates with the UPF through the N4 interface (referred to as N4), and the UPF accesses the data network (DN) through the N6 interface (referred to as N6). In addition, the control plane functions such as AUSF, AMF, SMF, NSSF, NEF, NRF, PCF, UDM, UDR or AF shown in Figure 1 interact using service-based interfaces. For example, the service interface provided by AUSF to the outside world is Nausf; the service interface provided by AMF to the outside world is Namf; the service interface provided by SMF to the outside world is Nsmf; the service interface provided by NSSF to the outside world is Nnssf; the service interface provided by NEF to the outside world is Nnef; the service interface provided by NRF to the outside world is Nnrf; the service interface provided by PCF to the outside world is Npcf; the service interface provided by UDM to the outside world is Nudm; the service interface provided by UDR to the outside world is Nudr; and the service interface provided by AF to the outside world is Naf.

[0105] The RAN device may be a device that provides access to the terminal. For example, the RAN device may include: a next-generation mobile communication system, such as an access network device of 6G, such as a 6G base station, or in the next-generation mobile communication system, the network device may also have other naming methods, which are all included in the protection scope of the embodiments of the present application, and the present application does not impose any restrictions on this. Alternatively, the RAN device may also include 5G, such as a gNB in ​​a new radio (NR) system, or one or a group of (including multiple antenna panels) antenna panels of a base station in 5G, or a network node constituting a gNB, a transmission point (TRP or transmission point, TP) or a transmission measurement function (TMF), such as a baseband unit (BBU), or a centralized unit (CU) or a distributed unit (DU), an RSU with base station function, or a wired access gateway, or a 5G core network. Alternatively, RAN devices may also include access points (APs) in wireless fidelity (WiFi) systems, wireless relay nodes, wireless backhaul nodes, various forms of macro base stations, micro base stations (also known as small stations), relay stations, access points, wearable devices, vehicle-mounted devices, and the like.

[0106] UPF is mainly responsible for user data processing (forwarding, receiving, billing, etc.). For example, UPF can receive user data from the data network (DN) and forward the user data to the terminal through the access network equipment. UPF can also receive user data from the terminal through the access network equipment and forward the user data to the DN. DN refers to the operator network that provides data transmission services to users. For example, the Internet Protocol (IP) Multimedia Service (IMS), the Internet, etc. DN can be an operator's external network or a network controlled by the operator, used to provide business services to the terminal. In the protocol data unit (PDU) session, the UPF directly connected to the DN through N6 is also called the protocol data unit session anchor (PSA).

[0107] AUSF is mainly used to perform terminal security authentication.

[0108] AMF is mainly used for mobility management in mobile networks, such as user location update, user network registration, and user handover.

[0109] The SMF is primarily used for session management in mobile networks, such as session establishment, modification, and release. Specific functions include allocating Internet Protocol (IP) addresses to users and selecting the UPF that provides packet forwarding capabilities.

[0110] PCF primarily supports providing a unified policy framework to control network behavior, providing policy rules to the control layer network functions, and is responsible for obtaining user subscription information related to policy decisions. PCF can provide policies to AMF and SMF, such as quality of service (QoS) policies and slice selection policies.

[0111] NSSF is mainly used to select network slices for terminals.

[0112] NEF is mainly used to support the opening of capabilities and events.

[0113] UDM is mainly used to store user data, such as contract data, authentication / authorization data, etc.

[0114] UDR is mainly used to store structured data, including contract data and policy data, externally exposed structured data, and application-related data.

[0115] AF mainly supports interaction with CN to provide services, such as influencing data routing decisions, policy control functions, or providing some third-party services to the network side.

[0116] The Link Load Orchestration Function (LLOF) network element is used to support transport layer termination of non-serviced interfaces and support routing of user-level or service-level non-serviced messages between serviced instances, such as NF instances (specifically, AMF network elements / SMF network elements), and non-serviced network elements. Non-serviced network elements can be the aforementioned RAN equipment or UPF. The LLOF network element can store UE context, which includes: a context identifier, a routing identifier (optional), a corresponding NF instance identifier (optional), and transport layer information (IP address, port number) of the non-serviced interface. For example, upon receiving a non-serviced message from a non-serviced network element, the LLOF query for the UE context based on the routing identifier (if present) in the message. If a UE context exists and the context contains an NF instance identifier, the LLOF network element sends the message to the NF instance. Otherwise, the LLOF network element determines the NF set corresponding to the destination address / port number based on the destination address / port number information of the message, selects a target NF instance from the NF set, and sends the message to the target NF instance.

[0117] As shown in Figure 2, the current protocol defines that NF instances with the same functionality can be grouped into an NF set. Each NF instance in an NF set can share the same context data, making them interchangeable, such as changing from AMF network element #1 to AMF network element #2. Each NF instance in an NF set can be deployed in different locations, such as different data centers (DCs). Different DCs can be considered hardware-isolated, or they can be deployed in the same DC. Multiple LLOF network elements can also form an LLOF set. LLOF network elements within the same LLOF set can be deployed in the same DC or across DCs, such as LLOF network element #1 deployed in DC #1 and LLOF network element #2 deployed in DC #2, achieving hardware isolation. LLOF network elements within an LLOF set share the UE context. LLOF sets and NF sets have a corresponding relationship, which can be a one-to-one correspondence, or multiple LLOF sets can correspond to one NF set, or one LLOF set can correspond to multiple NF sets. The LLOF set can provide services to the NF set corresponding to the LLOF set. Specifically, the LLOF network elements in the LLOF set can provide services to the NF network elements in the NF set, such as link load orchestration function.

[0118] It is understood that the functions mentioned in the embodiments of the present application can also be expressed as functional network elements or functional entities. For example, UPF can be expressed as UPF network element, AMF can be expressed as AMF network element, SMF can be expressed as SMF network element, PCF can be expressed as PCF network element, and so on, without limitation. In addition, LLOF network element can also be called LLOF instance or LLOF entity, or any other possible naming, which is not limited by the embodiments of the present application.

[0119] 2. NF registration:

[0120] As shown in Figure 3, the current protocol defines the NF service consumer service registration process as follows:

[0121] S301: The NF service consumption entity sends the NF profile to the NRF network element.

[0122] NF configuration is the configuration of the NF service consumer entity itself. NF configuration includes at least one of the following: NF type, NF instance ID, NF set ID, NF address, such as NF fully qualified domain name (FQDN) or IP address, public land mobile network (PLMN) ID, network slice related identifier(s), or endpoint address(es) of instance(s) of each supported service.

[0123] S302, the NRF network element stores the NF configuration of the service consumption entity.

[0124] The NRF network element can store the NF configuration of the service consumption entity and mark the NF configuration as available. That is, the NF configuration of the service consumption entity can be provided to other network elements that request NF configuration from the NRF network element.

[0125] S303, the NRF network element returns confirmation information to the NF service consumption entity.

[0126] The confirmation information may indicate that the NF configuration registration of the NF service consumption entity is successful.

[0127] It should be understood that the NF service consumption entity can be understood as the above-mentioned NF instance, such as AMF, SMF, PCF, UDM, etc. The NF service consumption entity can also be called NF consumption entity or NF service consumer, and the specific naming is not limited.

[0128] 3. NF discovery:

[0129] As shown in Figure 4, the current protocol defines the NF service consumer entity service discovery process as follows:

[0130] S401, the NF service consumption entity sends an NF discovery request (Nnrf_NFDiscovery_request) message to the NRF network element.

[0131] The NF Discovery Request message can be used to request the NRF network element to provide the service information of the NF (such as the SMF network element, PCF network element, UDM network element, etc.) expected by the NF service consumer entity (such as the AMF network element). The NF Discovery Request message may include at least one of the following: the expected NF service name, the NF type of the expected NF instance, or the NF type of the NF consumer.

[0132] S402: The NRF network element authenticates the NF service discovery.

[0133] The NRF network element can decide whether to allow the NF service consumer entity to discover the service it requested. The specific decision policy is not limited. If the NRF network element allows the NF service consumer entity to discover the service it requested, the NRF network element can authorize the NF discovery request message and discover the corresponding NF instance based on the information in the NF discovery request message. For example, if an NF instance that meets the NF service name and NF type of the expected NF instance expected by the NF service consumer entity is found, then the NF discovery is successful. Otherwise, the NRF network element does not authorize the NF discovery request message and the NF discovery fails.

[0134] S403, the NRF network element sends an NF discovery request response (Nnrf_NFDiscovery_request response) message to the NF service consumption entity.

[0135] In the case where the NF discovery is successful, the NF discovery request response message may indicate the configuration of the discovered NF, and in the case where the NF discovery fails, the NF discovery request response message may indicate the NF discovery failure.

[0136] It can be seen that the NF registration and discovery process defined by the current protocol does not involve LLOF network elements and cannot be applied to the scenario of introducing LLOF network elements in future networks. Therefore, how to realize the registration and discovery of LLOF network elements is a problem that needs to be solved.

[0137] In response to the above technical problems, the embodiments of the present application propose the following technical solutions.

[0138] The technical solution in this application will be described below with reference to the accompanying drawings.

[0139] In the embodiment of the present application, "indication" may include direct indication and indirect indication, and may also include explicit indication and implicit indication. The information indicated by a certain information is called information to be indicated. In the specific implementation process, there are many ways to indicate the information to be indicated, such as but not limited to, the information to be indicated can be directly indicated, such as the information to be indicated itself or the index of the information to be indicated. The information to be indicated can also be indirectly indicated by indicating other information, wherein there is an association relationship between the other information and the information to be indicated. It is also possible to indicate only a part of the information to be indicated, while the other parts of the information to be indicated are known or agreed in advance. For example, the indication of specific information can also be achieved by means of the arrangement order of each piece of information agreed in advance (such as specified in the protocol), thereby reducing the indication overhead to a certain extent. At the same time, the common parts of each piece of information can also be identified and indicated uniformly to reduce the indication overhead caused by indicating the same information separately.

[0140] In addition, the specific indication method can also be various existing indication methods, such as but not limited to the above-mentioned indication methods and various combinations thereof. The specific details of the various indication methods can be referred to the prior art and will not be repeated herein. As can be seen from the above, for example, when it is necessary to indicate multiple information of the same type, there may be a situation where the indication methods for different information are different. In the specific implementation process, the required indication method can be selected according to specific needs. The embodiment of the present application does not limit the selected indication method. In this way, the indication method involved in the embodiment of the present application should be understood to cover various methods that can enable the party to be indicated to obtain the information to be indicated.

[0141] It should be understood that the information to be indicated can be sent as a whole or divided into multiple sub-information and sent separately, and the sending period and / or sending time of these sub-information can be the same or different. The specific sending method is not limited in the embodiments of this application. The sending period and / or sending time of these sub-information can be predefined, for example, predefined according to a protocol, or can be configured by the transmitting device by sending configuration information to the receiving device.

[0142] In this application, "sending information" can be understood as one device sending information to another device, or as one logic module within a device sending information to another logic module. For example, "a network device sending information" can be understood as a network device sending information to another device (such as a terminal or other network device), or as logic module 1 within a network device sending information to logic module 2 within the network device.

[0143] In this application, "receiving information" can be understood as one device receiving information from another device, or it can also be understood as a logic module within a device receiving information from another logic module. For example, "a network device receiving information" can be understood as the network device receiving information from another device (such as a terminal or other network device), or it can be understood as logic module 1 in the network device receiving information from logic module 2 in the network device.

[0144] In this application, "sending information to... (e.g., a terminal)" or the related illustrations in the accompanying drawings can be understood as the destination end of the information being the terminal. This can include sending information to the terminal directly or indirectly. "Receiving information from... (e.g., a terminal)" or "receiving information from... (e.g., a terminal)" or "receiving information sent by (e.g., a terminal)", or the related illustrations in the accompanying drawings can be understood as the source end of the information being the terminal, which can include receiving information from the terminal directly or indirectly. The information may be processed as necessary between the source end and the destination end of the information transmission, such as format changes, etc., but the destination end can understand the valid information from the source end. Similar expressions in this application can be understood similarly and will not be repeated here.

[0145] "Pre-definition" or "pre-configuration" can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in the device, and the embodiments of the present application do not limit the specific implementation method. Among them, "saving" can mean saving in one or more memories. The one or more memories can be set separately or integrated in an encoder or decoder, a processor, or a communication device. The one or more memories can also be partially set separately and partially integrated in a decoder, a processor, or a communication device. The type of memory can be any form of storage medium, and the embodiments of the present application do not limit this.

[0146] The "protocol" involved in the embodiments of the present application may refer to a protocol family in the communication field, a standard protocol with a similar protocol family frame structure, or a related protocol used in future communication systems. The embodiments of the present application do not make specific limitations on this.

[0147] In the embodiments of the present application, descriptions such as "when...", "in the case of...", "if" and "if" all mean that the device will perform corresponding processing under certain objective circumstances. It does not limit the time, nor does it require the device to perform judgment actions when implemented, nor does it mean that there are other limitations.

[0148] In the description of the embodiments of the present application, unless otherwise specified, " / " indicates that the objects associated with each other are in an "or" relationship. For example, A / B can represent A or B. "And / or" in the embodiments of the present application is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. A and B can be singular or plural. In addition, in the description of the embodiments of the present application, unless otherwise specified, "multiple" refers to two or more than two. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple. In addition, in order to facilitate the clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as "first" and "second" are used to distinguish between identical or similar items with basically the same functions and effects. Those skilled in the art will understand that words such as "first" and "second" do not limit the quantity and execution order, and words such as "first" and "second" do not necessarily limit differences. At the same time, in the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or design. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a concrete way for easy understanding.

[0149] The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field will know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0150] To facilitate understanding of the embodiments of the present application, a communication system applicable to the embodiments of the present application is first described in detail using a communication system as an example.

[0151] FIG5 is a schematic diagram of the architecture of a communication system, which mainly includes: a first network element, a second network element, and a first network function.

[0152] The first network element can provide link load orchestration, or provide link load orchestration functions / services, and can specifically be an LLOF network element. Alternatively, in future communication systems, the LLOF network element can also be replaced by any possible network element, or in other words, any network element that can implement / provide link load orchestration functions / services can be understood as the LLOF network element in the embodiment of the present application.

[0153] The second network element may support configuration of the registration network function and discovery of the network function, such as the NRF network element in the 5GS mentioned above, or in future communication systems, the NRF network element may be replaced by any possible network element, such as an LLOF network element that has the capabilities of an NRF network element, or has the capabilities of configuration of the registration network function and discovery of the network function. For example, the second network element may be an LLOF network element of a higher level than the first network element. In this case, the lower-level LLOF network element may initiate registration with the higher-level LLOF network element.

[0154] The first network function can be any possible network function, such as a service instance, for example, it can be the RAN network element, AMF network element, SMF network element, PCF network element, UDM network element / UDR network element in the above-mentioned 5GS, or, in future communication systems, the first network function can also be a service instance in the communication system.

[0155] In this communication system, the configuration of the first network function (such as the first configuration of NF) includes information of the first network element (such as LLOF network element). When the first configuration is registered by the first network element to the second network element (such as NRF network element), if the second network element discovers the first network function based on the requester (such as the service-based instance) and provides the first configuration to the requester, the requester can also obtain the information of the first network element through the first configuration, thereby being able to interact with the first network element, that is, realizing the interaction between the LLOF network element and the service-based instance.

[0156] The communication method and device of the embodiment of the present application are further introduced below in conjunction with the accompanying drawings. It can be understood that the present application uses the network device and the terminal as the execution subject of the interactive schematic as an example for illustration, but the present application does not limit the execution subject of the interactive schematic. For example, the method executed by the network device in the present application can also be executed by a module (such as a chip, a chip system, or a processor) applied to the network device, and can also be implemented by a logical node, a logical module or software that can realize all or part of the functions of the network device; the method executed by the terminal in the present application can also be executed by a module (such as a chip, a chip system, or a processor) applied to the terminal, and can also be implemented by a logical node, a logical module or software that can realize all or part of the functions of the terminal.

[0157] The following method embodiments will specifically introduce the interaction process between the network elements / devices in the above communication system. The communication method provided in the embodiment of the present application can be applied to the above communication system and specifically applied to various scenarios mentioned in the above communication system, which will be described in detail below.

[0158] Figure 6 is a flow chart of a communication method according to an embodiment of the present application. The communication method is applicable to the above communication system and mainly involves interaction between a first network element, a second network element, and a first network function.

[0159] As shown in Figure 6, the process is as follows:

[0160] S601: A first network element sends a first message to a second network element, and the second network element receives the first message from the first network element.

[0161] The first message may request that a first configuration of a first network function (hereinafter referred to as the first configuration) be registered with a second network element. The first message may be an existing message, such as an NF Management NRF Registration Request (Nnrf_NFManagement_NFRegister request) message, or may be any possible message, such as a newly defined message. The specific message type / naming is not limited. For details on how the first network element obtains the first configuration, please refer to the relevant description of S601 and S700 below, which will not be repeated here.

[0162] S602: The second network element saves the first configuration.

[0163] The second network element may save the first configuration by default. Alternatively, the second network element may first verify the first network element, such as verifying whether the first network element is trustworthy. This can be achieved by verifying some information of the first network element that is difficult to tamper with. If the verification is successful, the second network element may determine that the registration is successful, save the first configuration locally, and set the first configuration to an active state, that is, the first configuration is in a state that can be provided to other network functions. Otherwise, the second network element may determine that the registration has failed and discard the first configuration.

[0164] S603: The second network element sends a second message to the first network element, and the first network element receives the second message from the second network element.

[0165] The second message may be a response to the first message, indicating that the first configuration of the first network function has been successfully registered or failed to be registered. The second message may be an existing message, such as an NRF Management Registration Response (Nnrf_NFManagement_NFRegister response) message, or any possible message, such as a newly defined message. The specific message type / naming is not limited.

[0166] The following is a detailed introduction to S601:

[0167] The first configuration may be an NF profile in 5G, or in future networks, the first configuration may also be configured in other names or forms, which is not limited in the embodiments of the present application. The first configuration includes information about the first network element, and may also include relevant information about the first network function. It is understandable that the first configuration may include information about the first network element and relevant information corresponding to one or more network functions registered with the first network element. In other words, the first network element may generate a corresponding first configuration for each network function registered with the first network element, or may generate a first configuration for multiple or all network functions registered with the first network element, which is not limited in the present application. The information of the first network element is mainly used for other network functions to identify and access the first network element, so as to realize the interaction between the first network element (LLOF network element) and other network functions (service instances). For example, the information of the first network element may include at least one of the following: address information of the first network element, or identification-related information of the first network element.

[0168] The address information of the first network element may be any information that can be used to access the first network element. For example, the address information of the first network element may be the IP address of the first network element, such as at least one IPv4 address, IPv6 address, or any address of any possible type or format, with no specific implementation limitation. Alternatively, the address information of the first network element may be the FQDN of the first network element, or any information that can function as an FQDN, with no specific implementation limitation. Alternatively, the address information of the first network element may be information used to indicate the address of the first network element, such as an indication cell, with no specific implementation limitation.

[0169] The identification-related information of the first network element can be any information that can be used to identify the first network element. For example, the identification-related information of the first network element can include at least one of the following: information used to identify the set to which the first network element belongs, or information used to identify the first network element. For example, the information used to identify the set to which the first network element belongs can be the identifier of the set, that is, an identifier at the set granularity. The embodiments of the present application do not limit the specific implementation form of the identifier of the set. Any information that can be used to identify the set can be understood as the identifier of the set in the embodiments of the present application. The set to which the first network element belongs can be referred to as a network element set. Multiple network elements within the network element set can provide link load orchestration, or in other words, the network element set can include multiple LLOF network elements, that is, an LLOF network element set. For specific implementation, please refer to the relevant description of Figure 2 above and will not be repeated here. The information used to identify the first network element can be the identifier of the first network element, that is, an identifier at the network element / device / instance granularity. The embodiments of the present application do not limit the specific implementation form of the identifier of the first network element. Any information that can be used to identify the first network element can be understood as the identifier of the first network element in the embodiments of the present application.

[0170] Optionally, the above-mentioned information of the first network element is some examples and is not intended to be limiting. For example, the information of the first network element may also implicitly or explicitly indicate the DC to which the first network element belongs. For example, the identifier of the first network element includes some fields or information elements, which are DC identifiers or can implicitly indicate DC, that is, implicitly indicate the DC to which the first network element belongs. For another example, the information of the first network element may also carry a DC identifier to display and indicate the DC to which the first network element belongs.

[0171] The relevant information of the first network function may include at least one of the following: the identifier of the first network function, the address of the first network function, or the type of the first network function, etc., so that the first network element can provide link load orchestration for the first network function according to the second configuration of the first network function. For specific implementation, please refer to the relevant introduction in "2. NF registration" above, which will not be repeated here. The embodiment of the present application takes the first configuration including the relevant information of the first network function as an example, but is not intended to be limiting. For example, the first configuration may also include relevant information of other network functions, such as the LLOF network element supports providing link load orchestration services for multiple NFs, and the first configuration correspondingly includes relevant information of each of these multiple NFs.

[0172] In an embodiment of the present application, the first configuration may be a configuration determined based on the second configuration of the first network function (hereinafter referred to as the second configuration) and the information of the first network element. Exemplarily, the second configuration may be an NF configuration (NF profile) in 5G, or in future networks, the second configuration may also be configured in other names or forms, which is not limited by the embodiment of the present application. The second configuration may also include relevant information of the first network function. On this basis, the first configuration may be obtained by replacing the relevant information of the first network function in the second configuration with the information of the first network element, that is, the first configuration may include part of the second configuration. Alternatively, the first configuration may also be obtained by adding the information of the first network element to the second configuration, that is, the first configuration may include all of the second configuration and the information of the first network element.

[0173] It is understood that if the first configuration is obtained by replacing the relevant information of the first network function, then when the servitization instance obtains the first configuration through network element discovery, the servitization instance may not be aware of the existence of the first network element and may still consider the information about the first network element in the first configuration to be relevant information about the first network function. In other words, the servitization instance still believes that it is interacting directly with the first network function, but in reality, because it is using the information of the first network element, it is interacting directly with the first network element and further interacting with the first network function through the proxy of the first network element. Of course, in the above situation, the servitization instance can also be aware of the existence of the first network element and know that it needs to interact with the first network function through the first network element. If the first configuration is obtained by adding the information of the first network element to the second configuration, the first configuration can also indicate the correspondence between the first network element and the first network function, indicating that the first network element provides a proxy service for the first network function. In this way, when the servitization instance obtains the first configuration through network element discovery, the servitization instance can learn from the first configuration that the first network element provides a proxy service for the first network function. In other words, the servitization instance is aware of the existence of the first network element and therefore knows that it needs to interact with the first network function through the first network element.

[0174] In one possible implementation, the first network function may send the second configuration to the first network element for registering with the first network element. If the registration is successful, the first network element may determine the first configuration based on the second configuration and information about the first network element.

[0175] Specifically, the first network function can send the second configuration to the first network element through the registration process, thereby realizing the registration of the first network function to the first network element. For example, the first network function can send a third message carrying the second configuration to the first network element. The third message can be any possible message, such as an existing message, or a newly defined message, such as a service interface message exchanged between the first network function and the first network element, such as an Nllof service message or other protocol type message. The specific message type / naming is not limited. The third message can request the first network function to be registered to the first network element or to the second network element, or to request the second configuration to be registered to the first network element. The first network function can pre-configure the address information of the first network element to send a third message carrying the second configuration to the first network element based on the address information of the first network element.

[0176] In the case where the first network element receives the second configuration, in one possible implementation, the first network element may save the second configuration locally by default, that is, the registration is successful. In another possible implementation, the first network element may determine whether the first network function and the first network element belong to the same DC. For example, the first network element may locally pre-configure information about the DC to which the first network element belongs, such as the correspondence between the identifier of the first network element and the DC identifier, indicating that the first network element belongs to the DC indicated by the DC identifier. The first network element may determine the DC to which the first network function belongs based on the identifier of the first network function in the second configuration. For example, some fields or information elements in the identifier of the first network function are DC identifiers or may implicitly indicate DC. In this way, the first network element may determine whether the first network function and the first network element belong to the same DC based on whether the DC identifier indicated by the identifier of the first network function and the DC identifier corresponding to the identifier of the first network element are the same identifier. For another example, the first network element may locally pre-configure the respective identifiers of one or more network functions that belong to the same DC as the first network element. For example, the identifiers of one or more network functions may belong to the same data structure, so as to implicitly indicate through the data structure that the network functions belonging to the same data structure belong to the same DC, and the network functions belonging to different data structures belong to different DCs. For another example, the identifiers of one or more network functions may be associated with the same DC identifier, so as to explicitly indicate through the DC identifier the network functions belonging to the same DC and to different DCs. In this way, the first network element can determine whether the first network function and the first network element belong to the same DC based on whether the identifier of the first network function belongs to the respective identifiers of the one or more network functions. Of course, the above-mentioned methods of determining the DC are only some examples, and the first network element can also determine whether the first network function and the first network element belong to the same DC in any other possible way, and the specific implementation is not limited. If the first network function and the first network element belong to the same DC, the first network element may save the second configuration locally; otherwise, the first network element will discard the second configuration and the registration will fail.

[0177] It is understood that the determination by the first network element whether the first network function and the first network element belong to the same DC is merely an example and is not intended to be limiting. The first network function may also determine whether the first network function and the first network element belong to the same DC. For example, the first network function may pre-configure the DC identifier of the first network element. If the first network element and the first network function belong to the same DC, the first network function initiates registration with the first network element. Alternatively, when registering a network function with the first network element, the first network element may not consider the DC; network functions belonging to the same or different DCs as the first network element may register with the first network element.

[0178] If registration is successful, the first network element may replace the information related to the first network function in the second configuration with the information of the first network element, such as replacing the address information of the first network function with the address information of the first network element, to obtain the first configuration. Alternatively, the first network element may add the information of the first network element to the second configuration to obtain the first configuration. Of course, the first network element may also perform other processing on the second configuration, such as discarding some redundant information related to the first network function in the second configuration, and the specific implementation is not limited.

[0179] The first network element may also send a fourth message to the first network function. The fourth message may respond to the third message mentioned above to indicate the success / failure of the second configuration registration. For example, the fourth message may be any message that may be used for the response, such as an existing message, or a newly defined message, such as a service interface message for interaction between the first network function and the first network element, such as an Nllof service message or other protocol type message. The fourth message may carry various response codes indicating success or failure, such as a response code indicating the success / failure of the second configuration registration. Optionally, there are different response codes for different failure situations. The fourth message may also carry a corresponding error reason value. For example, in the case of registration failure, the fourth message may also carry a reason value to indicate the reason for the registration failure, such as not belonging to the same DC, or other reasons. The specific implementation is not limited. Please refer to the relevant introduction of see clause 5.2.7of 3GPP TS29.500, which will not be repeated here.

[0180] It can also be understood that the successful registration of the first network function to the first network element can also be understood as the first network function being a network function supported by the first network element. In addition, the above is an example of the registration of the first network function to the first network element, which is not intended to be limiting. The first network function can also be registered to other network elements, such as other LLOF network elements. For example, the above-mentioned network element set corresponds to the network function set (such as the above-mentioned NF set) where the first network function is located. The first network function can pre-configure the address information of the network elements in the above-mentioned network element set that provide link load orchestration, such as multiple LLOF network elements, and initiate registration with these network elements respectively; or, the first network function can not only pre-configure the address information of these network elements, but also pre-configure the DCs to which these network elements belong, such as DC identifiers, so as to initiate registration with the network elements that belong to the same DC as the first network function; or, the first network function can also pre-configure the address information of the network elements in the network element set that belong to the same DC as the first network function, and initiate registration with these network elements respectively.

[0181] It will be appreciated that the above method of obtaining the first configuration based on the second configuration and information about the first network element is merely an example and is not intended to be limiting. For example, the first configuration may be pre-configured locally on the first network element, and the first network element may obtain the first configuration locally. For another example, the second configuration may be pre-configured locally on the first network element, and the first network element may obtain the second configuration locally and then determine the first configuration based on the information about the first network element. In other words, in this case, the first network can register with the first network element through pre-configuration, without the need for dynamic registration.

[0182] In summary, the configuration of the first network function (such as the first configuration of NF) includes information of the first network element (such as LLOF network element). When the first configuration is registered to the second network element (such as NRF network element) by the first network element, if the second network element discovers the first network function based on the requester (such as the service-based instance) and provides the first configuration to the requester, the requester can also obtain the information of the first network element through the first configuration, thereby being able to interact with the first network element, that is, realizing the interaction between the LLOF network element and the service-based instance.

[0183] It is understood that after completing S602 or S603, the second network function can obtain the first configuration from the second network element through the network element discovery process, so that the second network function can interact with the first network function through the first network element. In this case, the second network function can request the second network element to perform network element discovery, such as S604-S606 described below, or the second network function can also request the first network element to perform network element discovery, such as S607-S609 described below. In other words, the second network function can not only request the second network element, but also request the first network element to discover network functions that can provide services for it. The specific selection can be flexibly made according to actual needs, which are introduced below.

[0184] As shown in Figure 6, the process is as follows:

[0185] S604: The second network function sends a request message (recorded as request message #1) to the second network element. Correspondingly, the second network element receives the request message #1 from the second network function.

[0186] Request message #1 may instruct the second network function to request the discovery of a network function that can provide a service to the second network function. For example, request message #1 may be an existing message, such as the aforementioned NF discovery request message, and may carry relevant information about the second network function, such as the identifier of the second network function, the name of the NF service desired by the second network function, or the NF type of the NF instance desired by the second network function. For specific implementation, reference may be made to the relevant description of S401 above, which will not be repeated here. Alternatively, request message #1 may be a newly defined message, and the specific message type / name is not limited.

[0187] Optionally, the identifier of the second network function in request message #1 may include fields or information elements that are DC identifiers or may implicitly indicate a DC, that is, implicitly indicate the DC to which the second network function belongs. Alternatively, request message #1 may also carry the identifier of the DC to which the second network function belongs, to explicitly indicate the DC to which the second network function belongs.

[0188] S605 : The second network element sends the first configuration to the second network function according to the request message # 1 . Correspondingly, the second network function receives the first configuration from the second network element.

[0189] The second network element can determine, based on the request message #1, a network function or a set of network functions that can provide services to the second network function, such as a network function or a set of network functions that matches the NF service name expected by the second network function and the NF type of the expected NF instance. The details can also be understood in conjunction with the above-mentioned introduction to S402 and will not be repeated here. For example, the second network element can traverse the configuration of the network function locally stored in the second network element based on the request message #1 to determine the network function that can provide services to the second network function. For the set of network functions, the second network element can also select a network function that can provide services to the second network function from the set of network functions based on policies, such as the priority of the network function, the load level of the network function, etc. The network function determined by the second network element, or the network function selected from the determined set of network functions, is the first network function. The second network element sends the first configuration corresponding to the first network function to the second network function.

[0190] It should be understood that the second network element may not consider the DC when determining the network function that can provide services for the second network function, such as not considering whether the second network element and the network element corresponding to the network function that can provide services for the second network function (such as the LLOF network element) belong to the same DC. In this case, the second network element can use the existing technology to determine the network function that can provide services for the second network function, such as the first network function, so as to provide the first configuration for the second network function. For example, the second network element stores multiple configurations of network functions, and the second network element can select the first configuration from them (the embodiment of the present application does not limit the selection method) and then provide it to the second network function. Alternatively, the configuration of the first network function stored by the second network element is a first configuration. In this case, the second network element can provide the first configuration to the second network function by default.

[0191] Alternatively, the second network element may consider the DC when determining the network function that can provide services for the second network function, such as determining whether the second network element and the network element corresponding to the network function that can provide services for the second network function (such as the LLOF network element) belong to the same DC. Taking the first network function as an example, the second network element may determine whether the first network element and the second network function belong to the same DC. For example, if the above-mentioned request message #1 can implicitly or explicitly indicate the DC to which the second network function belongs, and the information of the first network element can implicitly or explicitly indicate the DC to which the first network element belongs, the second network element may determine whether the first network element and the second network function belong to the same DC. For another example, the second network element may pre-configure the correspondence between the identifier of each network element (LLOF network element) and each network function (NF instance) and the DC identifier, indicating the DC to which each network element and each network function belongs. In this way, the second network element can determine whether the DC identifier corresponding to the identifier of the first network element in the first configuration is the same as the DC identifier corresponding to the identifier of the second network function in the request message #1, thereby determining whether the first network element and the second network function belong to the same DC. Of course, the above methods for determining a DC are merely examples, and the second network element may determine whether the first network element and the second network function belong to the same DC by any possible method, without limitation to the specific implementation. When the first network function is a network function capable of providing services to the second network function, and the first network element and the second network function belong to the same DC, the second network element provides the first configuration to the second network function, such as selecting the first configuration from multiple configurations or providing the first configuration to the second network function by default.

[0192] The second network element may send a response message (denoted as response message #1) carrying the first configuration to the second network function. For example, response message #1 may be an existing message, such as the aforementioned NF discovery response message. For specific implementation, reference may be made to the relevant description of S401 above, which will not be repeated here. Alternatively, response message #1 may also be a newly defined message, and the specific message type / name is not limited in this embodiment of the application.

[0193] It can be seen that the NF discovery process is that the second network element provides the configuration of the discovered first network function, that is, the first configuration, to the second network function requesting NF discovery. Since the configuration of the first network function (that is, the first configuration) contains the information of the first network element, when the first configuration is registered to the second network element by the first network element, if the second network element discovers the first network function in response to the request of the second network function and provides its corresponding first configuration to the second network function, the second network function can obtain the information of the first network element from the first configuration. That is to say, for the solution of the embodiment of the present application, it is different from the prior art in that, when the second network element requests to discover the network function, the second network element obtains not only the information of the discovered first network function, but also the information of the first network element that acts as the agent for the first network function. In this way, the second network function can interact with the first network function through the proxy service of the first network element, that is, execute S606.

[0194] S606: The second network function requests the first network function to provide a service through the first network element.

[0195] The second network function may send a request message (recorded as request message #2) to the first network element. Correspondingly, the first network element may receive request message #2 from the second network function. Request message #2 indicates that the second network function requests the first network function to provide a service. For example, request message #2 may be an existing service-based message, such as a registration request message, a session establishment / modification request message, a subscription request message, etc., or may be a service-based message newly defined in the future. The specific message type / name is not limited in this embodiment of the application.

[0196] For example, the second network function may send request message #2 to the first network element based on the address information of the first network element. The address information of the first network element may be obtained by the second network element function from the received first configuration. Alternatively, if the first configuration does not include the address information of the first network element, the second network function may also obtain the address information of the first network element from the second network element based on the identifier-related information of the first network element in the first configuration.

[0197] Specifically, the second network function may send the identification-related information of the first network element to the second network element, and accordingly, the second network element receives the identification-related information of the first network element from the second network function. The identification-related information of the first network element may be carried in any possible message sent by the second network function to the second network element, and the specific implementation is not limited. The second network element may send the configuration of the first network element to the second network function based on the identification-related information of the first network element, and accordingly, the second network function receives the configuration of the first network element returned by the second network element based on the identification-related information of the first network element.

[0198] Among them, the configuration of the first network element may include identification-related information of the first network element and address information of the first network element. Optionally, it may also include other parameters / information of the first network element. For details, please refer to the relevant introduction of Figure 8 below, which will not be repeated here. The configuration of the first network element may be pre-configured in the second network element, or registered by the first network element to the second network element. For details, please refer to the relevant introduction of Figure 8 below, which will not be repeated here. The second network element may select the first network element based on the identification-related information of the first network element. For example, the second network element may index to the first network element based on the information used to identify the first network element, that is, it may directly select the first network element, which can reduce the overhead of selecting the network element. Alternatively, the second network element may also select the first network element in the above-mentioned network element set based on the information used to identify the network element set, that is, the second network element selects the first network element from the set that the second network element considers to be more suitable, so that the link load orchestration service provided by the first network element can better match the requirements of the second network function. On this basis, the second network element can locally obtain the configuration of the first network element and include the configuration of the first network element in any possible message sent by the second network element to the second network function, thereby transmitting it to the second network function. The specific message type / name is not limited. In this way, the second network function can request the first network function to provide services through the first network element based on the address information of the first network element in the configuration of the first network element, that is, send request message #2 to the first network element.

[0199] It is understood that the embodiment of the present application does not limit the strategy of the second network element in selecting network elements from the network element set. For example, the second network element may select a network element based on priority or randomly. The embodiment of the present application takes the selection of the configuration of the first network element as an example, but this is not a limitation. The second network element may also select the configuration of other network elements other than the first network element from the network element set, such as the configuration of the third network element (LLOF network element) or the configuration of the fourth network element (LLOF network element). In addition, the device form / function of the third network element mentioned in the present application may be similar to that of the first network element, which can be understood by reference and will not be repeated.

[0200] It is also understandable that the second network element may not consider the DC when selecting a network element from the network element set, or may consider the DC. For details, please refer to the above-mentioned related introduction and will not be repeated here. Of course, the second network element may also select the first network element instead for other reasons, such as the failure of the network element originally selected by the second network element (such as the LLOF network element), resulting in the final selection of the first network element and the second network function belonging to different DCs, or there may be other reasons, which are not specifically limited.

[0201] In response to the above-mentioned request message #2, the first network element can determine whether the first network element and the second network function belong to the same data center. The specific principle is similar to the above-mentioned determination of whether the first network element and the first network function belong to the same DC. You can refer to it for understanding and will not repeat it here. It should be understood that if the second network element considers the DC factor by default when selecting the first network function / first network element, then when the first network element receives the above-mentioned request message #2, it does not need to determine whether the first network element and the second network function belong to the same DC, but can directly provide the service of the first network function to the second network function. Alternatively, if the network function set and the network element set where the first network function and the second network function are located are already deployed in the same DC, then when the first network element receives the above-mentioned request message #2, it does not need to determine whether the first network element and the second network function belong to the same DC.

[0202] If the first network element and the second network function belong to the same DC, the first network element provides the first network function's services to the second network function on behalf of the first network function. Correspondingly, the second network function obtains the first network function's services through the first network element. For example, the first network element may forward request message #2 to the first network function. The first network element may then continue to transmit messages related to the services provided by the first network function between the first network function and the second network function until the services provided by the first network function are terminated, such as a registration success message or a session establishment / modification success message.

[0203] If the first network element and the second network function belong to different DCs, the first network element triggers a redirection process, which can be used to re-discover a network function that can serve the second network function for the second network function. It should be understood that due to the hardware isolation that may exist between different DCs, the LLOF and the service instance may not be able to interact, or different DCs may also be geographically far apart, resulting in a long interaction delay between the LLOF and the service instance, which cannot meet business needs. Therefore, the first network element can re-discover a network function that can serve the second network function for the second network function by triggering a redirection process, such as the network element corresponding to the network function (such as the LLOF network element) needs to belong to the same DC as the second network function.

[0204] The redirection process can be executed by the second network function, or can also be executed by the first network element, which are introduced below respectively.

[0205] Method 1: The second network function performs the redirection process.

[0206] The first network element may indicate that the second network function requires redirection. For example, the first network element may send an indication message to the second network function. Alternatively, the indication message may directly indicate that the second network function requires redirection, or may instruct the first network element to deny service, thereby implicitly indicating that the second network function requires redirection through the first network element denying service. Optionally, the indication message may also carry a cause value to indicate the reason for the redirection, such as a different DC or the need to reselect an LLOF network element. Accordingly, the second network function may redirect according to the indication of the first network element, such as by executing S604-S606 again.

[0207] Method 2: The first network element performs the redirection process.

[0208] The first network element may be redirected to a third network element, which is similar to the first network element and can provide link load orchestration, such as an LLOF network element.

[0209] For example, the first network element can determine a third network element that belongs to the same DC as the second network function from a set of network elements (such as multiple network elements). The third network element and the first network element can both belong to the set of network elements, such as multiple network elements in the set of network elements that support link load orchestration (or can provide link load orchestration). It can be understood that since the third network element is similar to the first network element and also needs to provide link load orchestration for the first network function, the first network function also needs to be registered with the third network element in advance. The specific implementation method is similar to the above-mentioned registration of the first network function with the first network element, which can be understood by reference and will not be repeated here. In one possible way, the first network element can locally pre-configure the respective identifiers of one or more network elements belonging to the same DC. For example, the identifiers of these one or more networks can be associated with the same DC identifier to display the network elements belonging to the same DC and those belonging to different DCs through the DC identifier. In this way, the first network element can select from one or more network elements associated with the DC identifier based on the DC identifier of the DC to which the first network function belongs. For example, since network elements in the same network element set can share context, the third network element can share the first network function registered to the third network element with the first network element, so that the first network element can select the third network element from the one or more network elements.

[0210] The first network element can send a request message (recorded as request message #3) to the third network element. Request message #3 can instruct the second network function to request the first network function to provide services. In other words, the first network element can instruct (e.g., by sending request message #3) the third network element to provide the first network function's services to the second network function on behalf of the first network function. Request message #3 can also be understood as instructing the third network element to provide (or open up) the first network function's services to the second network function through the first network element. In other words, the third network element can help forward service-related messages of the first network function, so that corresponding service processes, such as registration processes and session establishment / modification processes, can be executed normally.

[0211] It should be understood that when a third network element provides the services of the first network function to the second network function, the first network element may also participate in the transmission of related messages. For example, the second network function may send a message related to the service process to the first network element, and the first network element may forward the relevant message (such as request message #3 or subsequent messages) to the third network element, which may then forward it to the first network function. The first network function may send a message related to the service process to the third network element, which may then forward the relevant message to the first network element, which may then forward it to the second network function, until the relevant service process is completed.

[0212] Alternatively, when a third network element provides the services of the first network function to the second network function, the first network element may not participate in the transmission of related messages to improve communication efficiency. For example, the first network element may send information about the third network element (such as identification information and / or address information of the third network element) to the second network function, so that the second network function can directly send messages related to the service process to the third network element based on the information of the third network element, which is then forwarded to the first network function by the third network element. Identification information and / or address information of the third network element.

[0213] Specifically, the first network element can obtain the third configuration of the first network function (hereinafter referred to as the third configuration) carrying the information of the third network element, and send the third configuration (such as any possible message carrying the third configuration) to the second network function. Correspondingly, the second network function can receive the third configuration from the first network element and obtain the information of the third network element from it.

[0214] There are various ways for the first network element to obtain the third configuration. For example, similar to the registration of the first network function with the first network element described above, the first network function can also register with a third network element. In this way, the third network element can obtain the third configuration and share the third configuration with network elements within the same network element set, such as the first network element, so that the first network element can also obtain the third configuration. Alternatively, the first network element can proactively obtain the third configuration from the third network element, or obtain the third configuration from another network element (LLOF) that shares the third configuration with the third network element. For another example, the third network element can register the third configuration with the second network element. The specific implementation is similar to the registration of the first configuration with the second network element by the first network element, and can be understood with reference to it, so it will not be further described here. In this way, the first network element can obtain the third configuration from the second network element. For example, the first network element can send any possible message carrying the identifier of the first network function and the identifier of the third network element to the second network element, requesting the second network element to provide the configuration of the first network function related to the third network element, that is, the third configuration. Accordingly, the second network element can return any possible message carrying the third configuration to the first network element upon the request of the first network element.

[0215] It will be understood that the above methods are merely examples and are not intended to be limiting. For example, when the first network element obtains information about the third network element (which can be obtained in the above method), the first network element can send indication information to the second network function, where the indication information can carry information about the third network element, indicating that the second network function needs to be redirected to the third network element.

[0216] The above describes that the second network function requests the second network element to perform network element discovery. The following describes that the second network function requests the first network element to perform network element discovery.

[0217] As shown in Figure 6, the process is as follows:

[0218] S607 , the second network function sends a request message (recorded as request message # 4 ) to the first network element. Correspondingly, the first network element receives the request message # 4 from the second network function.

[0219] Request message #4 instructs the second network function to request the discovery of a network function that can provide a service to the second network function. For example, request message #4 may be an existing message, such as the aforementioned NF discovery request message, and may carry relevant information about the second network function, such as the identifier of the second network function, the NF service name desired by the second network function, or the NF type of the NF instance desired by the second network function. For specific implementation, reference may be made to the relevant description of S401 above, which will not be repeated here. Alternatively, request message #4 may be a newly defined message, and the specific message type / name is not limited.

[0220] Optionally, the identifier of the second network function in request message #4 may include fields or information elements that are DC identifiers or may implicitly indicate a DC, that is, implicitly indicate the DC to which the second network function belongs. Alternatively, request message #4 may also carry the identifier of the DC to which the second network function belongs, to explicitly indicate the DC to which the second network function belongs.

[0221] When the second network function registers with the first network element, the second network function can send a request message #4 to the first network element. In other words, the second network function can request the LLOF network element that serves the second network function to discover a network function that can provide services for the second network function. The registration of the second network function with the first network element can specifically involve the second network function sending the configuration of the second network function network element to the first network element. For specific implementation, please refer to the above-mentioned introduction to the registration of the first network function with the first network element, which will not be repeated here. In other words, the first network element can not only provide link load orchestration for the first network function, but also provide link load orchestration for the second network function, which can improve the service efficiency of providing link load orchestration.

[0222] S608: In response to the request message #4, the first network element obtains the first configuration.

[0223] If the first network element supports the network function selection capability, the first network element performs functions similar to those of the second network element and obtains the first configuration locally from the first network element to avoid communication overhead. For specific implementations, please refer to the description of S605 above and will not be repeated here. If the first network element does not support the network function selection capability, or if the first network element supports the network function selection capability but has not locally discovered a network function that can provide services for the second network function, the first network element may obtain the first configuration from the second network element. For example, the first network element may send a request message (recorded as request message #5) to the second network element, and the second network element accordingly receives request message #5 from the first network element. Request message #5 indicates that the second network function requests to discover a network function that can provide services for the second network function. In this way, the second network element may send the first configuration to the first network element based on request message #5, and the first network element may receive the first configuration from the second network element. In other words, the first network element may ultimately obtain the first configuration that matches the requirements of the second network function. For specific implementations, please refer to the description of S605 above and will not be repeated here.

[0224] S609: The first network element sends a first configuration to the second network function. Correspondingly, the second network function receives the first configuration from the first network element.

[0225] S610: The second network function can request the first network function to provide a service through the first network element.

[0226] It is understood that in S609, the first configuration can be carried in any possible message sent by the first network element to the second network function, and the specific message type / naming is not limited. In addition, the specific implementation of S610 can also refer to the relevant introduction of S606 above, which will not be repeated here.

[0227] It can be understood that the above is an example of the first network element providing the first configuration to the second network function, which is not a limitation. For example, when the second network function sends a request message to the first network element, the first network element can also obtain the third configuration of the first network function. The third configuration may include information about the third network element. The third network element provides link load orchestration, such as being able to provide link load orchestration to the first network function. In this case, the third network element and the second network function may belong to the same DC or different DCs. The first network element can determine whether the third network element and the second network function belong to the same DC, and then trigger the redirection process, or the first network element may not make a judgment and only forward the message, and the specific implementation is not limited. For another example, the second network function may also request network element discovery from the third network element (such as an unregistered LLOF network element).

[0228] The above describes the arrangement process of the communication method provided by the embodiment of the present application in conjunction with Figure 6. The following describes in detail the specific process of the communication method provided by the embodiment of the present application in a specific scenario in conjunction with Figures 7-8.

[0229] Scenario 1:

[0230] Figure 7 is a second flow chart of a communication method provided in an embodiment of the present application. This communication method is applicable to the above-mentioned communication system, and mainly involves the interaction between LLOF network element #1 (such as the first network element), NRF network element (such as the second network element), NFp network element (such as the first network function), and NFc network element (such as the second network function).

[0231] In scenario 1, the NF provisioning entity may first register with the LLOF network element #1, such as by sending the configuration of the NF provisioning entity to the LLOF network element #1. The LLOF network element #1 then registers the address information or identification-related information of the LLOF network element #1 with the NRF network element along with the configuration of the NF provisioning entity. In this way, when the NRF network element discovers the NF provisioning entity based on the NF discovery request message of the NF consuming entity, the NRF network element may provide the address information or identification-related information of the LLOF network element #1 to the NF consuming entity, so that the NF consuming entity can interact with the LLOF network element #1 based on the address information or identification-related information of the LLOF network element #1, so as to trigger the NF provisioning entity to provide corresponding services through the LLOF network element #1.

[0232] Specifically, as shown in FIG7 , the process of the communication method is as follows:

[0233] S700: The NFp network element registers with the LLOF network element #1.

[0234] The NFp network element registers its relevant information (such as the NF configuration #1 of the NFp network element (such as the second configuration mentioned above), or the message format of the future network element) to the LLOF network element #1. The registration process is similar to the above-mentioned NRF registration process. The registered message can be an Nllof service message or other protocol type message. The specific implementation can also refer to the relevant introduction in the above S601, which will not be repeated here.

[0235] It can be understood that S700 is an optional step. For example, LLOF network element #1 can pre-configure NF information supported by LLOF network element #1, such as configuration #1 of NFp network element.

[0236] S701, LLOF network element #1 sends an NF management NRF registration request message to the NRF network element.

[0237] S702, the NRF network element sends an NF management NRF registration response message to the LLOF network element #1.

[0238] In S701, the NF Management NRF Registration Request message may request that the NF Configuration #2 (such as the first configuration described above) of the NFp network element be registered with the NRF network element. NF Configuration #2 may specifically include the address information and / or identification-related information of the LLOF network element #1. The specific implementation of S701-S702 can refer to the relevant description of S601-S602 above and will not be repeated here.

[0239] S703: The NFc network element sends an NF discovery request message #1 to the NRF network element.

[0240] S704: The NRF network element sends an NF discovery response message #1 to the NFc network element.

[0241] In S703-S704, the NF Discovery Request Message #1 instructs the NFc network element to discover the network function that can provide services for the NFc network element. The NF Discovery Response Message can carry the NF Configuration #2. The specific implementation principle can be referred to the relevant introduction of S604-S605 above and will not be repeated here.

[0242] S705: The NFc network element obtains the address information of the LLOF network element #1 from the NRF network element.

[0243] It can be understood that when NF configuration #2 includes the identification-related information of LLOF network element #1 but does not include the address information of LLOF network element #1, the NFc network element can also obtain the address information of LLOF network element #1 from the NRF network element. The specific implementation can also refer to the relevant introduction in the above S606, which will not be repeated here.

[0244] S706: The NFc network element sends an interaction request message #1 to the LLOF network element #1.

[0245] S707: The NFc network element and the NFp network element complete the service-related interaction through the proxy service discovery of the LLOF network element #1.

[0246] S708: LLOF network element #1 sends an interaction response message #1 to the NFc network element.

[0247] In S706-S708, the NFc network element and LLOF network element #1 belong to the same DC. Interaction Request Message #1 requests the NFp network element to provide a service, and Interaction Response Message #1 may indicate the end of the service. The specific implementation of S706-S708 can be referenced in the description of S606 above and will not be repeated here.

[0248] S709: The NFc network element sends an NF discovery request message #2 to the NRF network element.

[0249] S710: The NRF network element sends an NF discovery response message #2 to the NFc network element.

[0250] In S709-S710, the NF discovery request message also instructs the NFc network element to discover the network function that can provide services for the NFc network element. The difference is that the NF discovery request message can carry the NF configuration #3 (such as the third configuration) of NFp, and the NF configuration #3 can include the address information or identification related information of the LLOF network element #2 (such as the third network element mentioned above). NFp can also register with the LLOF network element #2. In this way, the LLOF network element #2 can also register the NF configuration #3 with the NRF network element. The specific implementation is similar to S703-S704, which can be referred to for understanding and will not be repeated here.

[0251] S711: The NFc network element obtains the address information of the LLOF network element #2 from the NRF network element.

[0252] It can be understood that when NF configuration #3 includes the identification-related information of LLOF network element #2 but does not include the address information of LLOF network element #2, the NFc network element can also obtain the address information of LLOF network element #2 from the NRF network element. The specific implementation can also refer to the relevant introduction in the above S606, which will not be repeated here.

[0253] S712: The NFc network element sends an interaction request message #2 to the LLOF network element #2.

[0254] In S712, the NFc network element and LLOF network element #2 belong to different DCs and need to be redirected. At this time, LLOF network element #2 can execute the following S713-S716.

[0255] S713, LLOF network element #2 sends an interaction response message #2 to the NFc network element.

[0256] The interaction response message #2 may indicate that the LLOF network element #2 denies the service and may also carry a reason value, such as not belonging to the same DC. In this case, the NFc network element again sends an NF discovery request message to the NRF network element, such as NF discovery request message #3.

[0257] S714, LLOF network element #2 sends an interaction request message #2 to LLOF network element #1.

[0258] S715: The NFc network element and the NFp network element complete the service-related interaction through the proxy service discovery of the LLOF network element #1 and the LLOF network element #2.

[0259] In S713-S714, LLOF network element #2 can be redirected to LLOF network element #1, i.e., LLOF network element #1 belonging to the same DC as the NFc network element is selected. Interaction response message #2 can indicate the end of service. Optionally, interaction response message #2 can also carry NF configuration #1 of the NFp network element, i.e., providing the address information of LLOF network element #1 to the NFc network element. The specific implementation of S714-S715 can also refer to the relevant description in S606 above and will not be repeated here.

[0260] It can be understood that S713 and S714-S715 can be in an "or" execution relationship.

[0261] Additionally, for NFc network elements, if the NFc network element has previously registered with LLOF network element #3, the NFc network element can also request LLOF network element #3 to discover network functions that can provide services to the NFc network element, such as by sending an NF Discovery Request message to LLOF network element #3. If LLOF network element #3 supports NF selection, LLOF network element #3 can determine whether there are network functions that can serve the NFc network element based on its stored NF configuration. If there are network functions that can serve the NFc network element, such as NFp network elements, LLOF network element #3 directly sends an NF Discovery Response message, which carries NF Configuration #2. If LLOF network element #3 does not support NF selection, such as performing proxy forwarding, or LLOF network element #3 supports NF selection, but LLOF network element #3 determines that there is no network function that can serve the NFc network element based on its own stored NF configuration, then LLOF network element #3 can send an NF discovery request message to the NRF network element and receive an NF discovery response message returned by the NFc network element. The NF discovery response message carries NF configuration #2.

[0262] After obtaining NF configuration #2, LLOF network element #3 can also determine whether LLOF network element #1 and the NFc network element belong to the same DC based on the information about LLOF network element #1 carried in NF configuration #2. If LLOF network element #1 and the NFc network element belong to different DCs, LLOF network element #3 triggers the redirection process. If LLOF network element #1 and the NFc network element belong to the same DC, LLOF network element #3 returns NF configuration #2 to the NFc network element. Alternatively, if LLOF network element #3 does not determine whether LLOF network element #1 and the NFc network element belong to the same DC, LLOF network element #3 returns NFc configuration #2 to the NFc network element by default. In other words, in this case, the NFc network element can be considered to be requesting the NRF network element to discover the NFp network element through LLOF network element #3.

[0263] It can also be understood that the interaction between the NFc network element and the LLOF network element #3 can refer to the relevant introduction of the above S606, which will not be repeated here.

[0264] Figure 8 is a flow chart of the communication method according to an embodiment of the present application. The communication method is applicable to the above communication system, and mainly involves the interaction between the first network element, the second network element, and the first network function.

[0265] As shown in Figure 8, the process is as follows:

[0266] S801: A first network element sends a first message to a second network element, and the second network element receives the first message from the first network element.

[0267] The first message may request that the configuration of the first network element be registered with the second network element. The configuration of the first network element may be used to indicate relevant information of the first network element. For example, the configuration of the first network element may include at least one of the following: identification information of the first network element, or address information of the first network element.

[0268] Optionally, the configuration of the first network element may further include at least one of the following: information about the DC to which the first network element belongs, such as a DC identifier, or capability information of the first network element. The capability information of the first network element is used to indicate which functions the first network element supports, such as supporting one of the following: link load orchestration, discovery of LLOF network elements, discovery of NF instances, or any other possible functions, without limitation to the specific implementation.

[0269] Optionally, the configuration of the first network element may further include information about network functions supported by the first network element. The network functions supported by the first network element may be understood as network functions served by the first network element, that is, the first network element can provide link load orchestration for the network functions. For example, if the network function supported by the first network element is the first network function, the information about the first network function may include at least one of the following: an identifier of the first network function, an address of the first network function, a type of the first network function, or an identifier of the network function set to which the first network function belongs.

[0270] The information of the first network function may be obtained by the first network element through the first network function registering with the first network element. For example, the first network function sends the configuration of the first network function to the first network element. For the specific implementation, please refer to the relevant introduction in S601 above and will not be repeated here. The first network element obtains the information of the first network function from the configuration of the first network function and carries the information of the first network function to the configuration of the first network element. Alternatively, the first network element may also directly carry the configuration of the first network function to the configuration of the first network element. Of course, the information of the first network function is also pre-configured or pre-defined by protocol in the configuration of the first network element.

[0271] In addition, the specific implementation of S801 is similar to that of the above-mentioned S601, which can be understood by reference and will not be repeated here.

[0272] S802: The second network element saves the configuration of the first network element.

[0273] It can be understood that the above methods are only some examples. For example, the configuration of the first network element may not include information about the first network function. The first network element can register the configuration of the first network element and the configuration of the first network function to the second network element respectively, and the second network element can associate and save the configuration of the first network element and the configuration of the first network function.

[0274] S803: The second network element sends a second message to the first network element, and the first network element receives the second message from the second network element.

[0275] The second message indicates that the configuration registration of the first network element is successful. In addition, the specific implementation of S802-S803 is similar to the above S602-S603, which can be understood by reference and will not be repeated here.

[0276] In summary, the first network element can directly register its configuration with the second network element, and the registration is successful. Other network functions (such as or service-based instances) can discover the first network element through the second network element and obtain the configuration of the first network element, thereby being able to interact with the first network element. In other words, interaction between the LLOF network element and the service-based instance is realized.

[0277] It is understood that if the configuration of the first network element is successfully registered, the second network function can obtain the configuration of the first network element from the second network element through the network element discovery process, so as to interact with the first network function through the first network element. In this case, the second network function can request the second network element to perform network element discovery, such as S804-S806 below, or the second network function can also request the first network element to perform network element discovery, such as S807-S809 below, which are described below.

[0278] As shown in Figure 8, the process is as follows:

[0279] S804: The second network function sends a request message to the second network element. Correspondingly, the second network element receives the request message from the second network function.

[0280] The request message may instruct the second network function to request discovery of a network function that can provide services for the second network function. The specific implementation is similar to the above-mentioned request message #1, which can be understood by reference and will not be repeated here.

[0281] S805 , the second network element may send the configuration of the first network element to the second network function according to the request message, and correspondingly, the second network function receives the configuration of the first network element from the second network element.

[0282] The first network function can provide services to the second network function. The second network element can select a network function that can provide services to the second network function, such as the first network function, based on the request message. Unlike the prior art, the second network element can determine to send the configuration of the first network element to the second network function based on the association between the configuration of the first network function and the configuration of the first network element, or based on the fact that the configuration of the first network element contains the configuration of the first network function or information about the first network function. In other words, the association between the configuration of the first network function and the configuration of the first network element, or the inclusion of the configuration of the first network function or information about the first network function in the configuration of the first network element, indicates that the first network element is a network element serving the first network function, or an LLOF network element. Therefore, the second network element can determine to send the configuration of the first network element to the second network function.

[0283] Optionally, the second network element may also send the configuration of the first network function or the information of the first network function to the second network function, such as sending it together with the configuration of the first network element or sending it separately, and the specific implementation is not limited.

[0284] S806: The second network function requests the first network function to provide a service through the first network element.

[0285] In addition, the specific implementation of S805-S806 is similar to the above-mentioned S602-S603, such as the message transmission, redirection process, etc., which can be understood by referring to S602-S603 and will not be repeated here.

[0286] The above describes that the second network function requests the second network element to perform network element discovery. The following describes that the second network function requests the first network element to perform network element discovery.

[0287] As shown in Figure 8, the process is as follows:

[0288] S807 , the second network function sends a request message to the first network element. Correspondingly, the first network element receives the request message from the second network function.

[0289] The request message may instruct the second network function to request discovery of a network function that can provide services for the second network function. The specific implementation is similar to the above-mentioned request message #4, which can be understood by reference and will not be repeated here.

[0290] S808: In response to the request message, the first network element obtains the configuration of the first network element.

[0291] The first network element may perform functions similar to those of the second network element in S805 above. For example, the first network element may determine to send the configuration of the first network element to the second network function based on the association between the configuration of the first network function and the configuration of the first network element, or based on the fact that the configuration of the first network function or information about the first network function is included in the configuration of the first network element. Alternatively, the first network element may also send the configuration of the first network function or information about the first network function to the second network function. Alternatively, the first network element may also obtain the configuration of the first network element from the second network element.

[0292] S809: The first network element sends the configuration of the first network element to the second network function, and the second network function receives the configuration of the first network element from the first network element.

[0293] S810: The second network function requests the first network function to provide a service through the first network element.

[0294] In addition, the specific implementation of S808-S810 is similar to the above-mentioned S608-S610, such as the message transmission, redirection process, etc., which can be understood by referring to S608-S610 and will not be repeated here. In addition, the above is an example of the first network element obtaining its own configuration. When the second network function requests the first network element to perform network function discovery, if the first network element determines that its own configuration is not suitable, such as the first network function indicated in the configuration of the first network element cannot serve the second network function, then the first network element can also provide other more suitable network elements, such as the configuration of the third network element to the second network function. The configuration of the third network element can be provided to the first network element in advance by the third network element, or the first network element can obtain it from the second network element, without specific limitation.

[0295] Scenario 2:

[0296] Figure 9 is a fourth flow chart of a communication method provided in an embodiment of the present application. This communication method is applicable to the above-mentioned communication system, and mainly involves the interaction between LLOF network element #1 (such as the first network element), NRF network element (such as the second network element), NFp network element (such as the first network function), and NFc network element (such as the second network function).

[0297] In scenario 2, LLOF NE #1 can register with the NRF NE, for example by sending its configuration to the NRF NE. In this way, when the NRF NE discovers LLOF NE #1 based on the NF Discovery Request message from the NFc NE, the NRF NE can provide the configuration of LLOF NE #1 to the NFc NE. The NF consumer can interact with LLOF NE #1 based on the address of LLOF NE #1 in its configuration, triggering NFc to provide the corresponding service.

[0298] Specifically, as shown in FIG9 , the process of the communication method is as follows:

[0299] S900: The NFp network element registers with the LLOF network element #1.

[0300] The NFp network element registers its relevant information (such as the NF configuration of the NFp network element (such as the configuration of the first network function mentioned above), or the message format of the future network element) to the LLOF network element #1. The registration process is similar to the above-mentioned NRF registration process. The registered message can be an Nllof service message or other protocol type message. The specific implementation can also refer to the relevant introduction in the above S601, which will not be repeated here.

[0301] It can be understood that S900 is an optional step. For example, LLOF network element #1 can pre-configure NF information supported by LLOF network element #1, such as configuration of NFp network element.

[0302] S901, LLOF network element #1 sends an NF management NRF registration request message to the NRF network element.

[0303] S902, the NRF network element sends an NF management NRF registration response message to the LLOF network element #1.

[0304] In S901, the NF management NRF registration request message can request to register the configuration of LLOF network element #1 (such as the configuration of the first network element mentioned above) with the NRF network element. The specific implementation of the configuration of LLOF network element #1 can refer to the relevant introduction of the configuration of the first network element mentioned above, which will not be repeated here. The specific implementation of S901-S902 can also refer to the relevant introduction of S601-S602 and S801-S802 mentioned above, which will not be repeated here.

[0305] S903: The NFc network element sends an NF discovery request message #1 to the NRF network element.

[0306] S904: The NRF network element sends an NF discovery response message #1 to the NFc network element.

[0307] In S903-S904, the NF Discovery Request Message #1 instructs the NFc network element to discover the network function that can provide services for the NFc network element. The NF Discovery Response Message can carry the configuration of the LLOF network element #1. The specific implementation principle can refer to the relevant introduction of S604-S605 and S804-S805 above and will not be repeated here.

[0308] S905: The NFc network element sends an interaction request message #1 to the LLOF network element #1.

[0309] S906: The NFc network element and the NFp network element complete the service-related interaction through the proxy service discovery of the LLOF network element #1.

[0310] S907, LLOF network element #1 sends an interaction response message #1 to the NFc network element.

[0311] In S905-S907, the NFc network element and LLOF network element #1 belong to the same DC. Interaction Request Message #1 requests the NFp network element to provide a service, and Interaction Response Message #1 may indicate the end of the service. The specific implementation of S906-S907 can be referenced in the above description of S606 and S806 and will not be repeated here.

[0312] S908: The NFc network element sends an NF discovery request message #2 to the NRF network element.

[0313] S909: The NRF network element sends an NF discovery response message #2 to the NFc network element.

[0314] In S908-S909, the NF discovery request message also instructs the NFc network element to discover the network function that can provide services for the NFc network element. The difference is that the NF discovery request message can carry the configuration of the LLOF network element #2. That is, the LLOF network element #2 can also register the configuration of the LLOF network element #2 to the NRF network element. The specific implementation is similar to S901-S902, which can be understood by reference and will not be repeated here.

[0315] S910: The NFc network element sends an interaction request message #2 to the LLOF network element #2.

[0316] In S910, the NFc network element and LLOF network element #2 belong to different DCs and need to be redirected. At this time, LLOF network element #2 can execute the following S911-S913.

[0317] S911, LLOF network element #2 sends an interaction response message #2 to the NFc network element.

[0318] The interaction response message #2 may indicate that the LLOF network element #2 denies the service and may also carry a reason value, such as not belonging to the same DC. In this case, the NFc network element again sends an NF discovery request message to the NRF network element, such as NF discovery request message #3.

[0319] S912, LLOF network element #2 sends an interaction request message #2 to LLOF network element #1.

[0320] S913: The NFc network element and the NFp network element complete the corresponding service interaction through the proxy service discovery of the LLOF network element #1 and the LLOF network element #2.

[0321] In S912-S913, LLOF network element #2 can be redirected to LLOF network element #1, i.e., LLOF network element #1 belonging to the same DC as the NFc network element is selected. Interaction response message #2 can indicate the end of service. Optionally, interaction response message #2 can also carry the configuration of LLOF network element #1 of the NFp network element. The specific implementation of S911-S913 can also refer to the relevant description in S606 above and will not be repeated here.

[0322] It can be understood that S911 and S912-S913 can be in an "or" execution relationship.

[0323] Additionally, for an NFc network element, if the NFc network element has previously registered with LLOF network element #3, the NFc network element may also request LLOF network element #3 to discover network functions that can provide services to the NFc network element, such as by sending an NF discovery request message to LLOF network element #3. If LLOF network element #3 supports NF selection, LLOF network element #3 may determine whether there are network functions that can serve the NFc network element, i.e., network functions that can provide services to the NFc network element, based on the NF information / configuration stored in the LLOF network element configuration, or the NF information / configuration associated with the LLOF network element configuration. If there is a network function that can serve the NFc network element, such as an NFp network element, the LLOF network element #3 directly sends a discovery response message to the NF. The NF discovery response message carries the configuration of the LLOF network element to which the NFp network element is registered, such as the configuration of the LLOF network element #1. The NF discovery response message may also carry information / configuration of the NFp network element, such as carried in the configuration of the LLOF network element #1, or carried in the NF discovery response message independently of the configuration of the LLOF network element #1. If LLOF network element #3 does not support NF selection, such as performing proxy forwarding, or LLOF network element #3 supports NF selection, but LLOF network element #3 determines that there is no network function that can serve the NFc network element based on the NF information / configuration in the LLOF network element configuration stored in itself, or the NF information / configuration associated with the LLOF network element configuration, then LLOF network element #3 can send an NF discovery request message to the NRF network element and receive an NF discovery response message returned by the NFc network element. The NF discovery response message carries the configuration of LLOF network element #1, and optionally, may also carry the information / configuration of the NFp network element.

[0324] Additionally, after obtaining the configuration of LLOF network element #1, LLOF network element #3 can also determine whether LLOF network element #1 and the NFc network element belong to the same DC based on the configuration of LLOF network element #1. If LLOF network element #1 and the NFc network element belong to different DCs, LLOF network element #3 triggers the redirection process. If LLOF network element #1 and the NFc network element belong to the same DC, LLOF network element #3 returns the configuration of LLOF network element #1 to the NFc network element. Alternatively, if LLOF network element #3 does not determine whether LLOF network element #1 and the NFc network element belong to the same DC, LLOF network element #3 returns the configuration of LLOF network element #1 to the NFc network element by default. In other words, in this case, it can be considered that the NFc network element is requesting the NRF network element to discover the NFp network element through LLOF network element #3.

[0325] It can also be understood that the interaction between the NFc network element and the LLOF network element #3 can refer to the relevant introduction of the above S606, which will not be repeated here.

[0326] The communication method provided in the embodiment of the present application is described in detail above in conjunction with Figures 6 to 9. The communication device for executing the communication method provided in the embodiment of the present application is described in detail below in conjunction with Figures 10 and 11.

[0327] Figure 10 is a structural diagram of a communication device according to an embodiment of the present application. As shown in Figure 10 , the communication device 1000 includes a transceiver module 1001 and a processing module 1002. For ease of illustration, Figure 10 only shows the main components of the communication device.

[0328] The communication device 1000 can be applied to the above communication method to implement corresponding functions. For example, the transceiver module 1001 can be used to implement the transceiver function in the above communication method, and the processing module 1002 can be used to implement other functions in the above communication method except the transceiver function.

[0329] Optionally, the transceiver module 1001 may include a sending module (not shown in FIG10 ) and a receiving module (not shown in FIG10 ). The sending module is used to implement the sending function of the communication device 1000 , and the receiving module is used to implement the receiving function of the communication device 1000 .

[0330] Optionally, the communication device 1000 may further include a storage module (not shown in FIG10 ) storing a program or instruction. When the processing module 1002 executes the program or instruction, the communication device 1000 may perform the functions of the method shown in FIG6-FIG9 above.

[0331] It can be understood that the communication device 1000 can be a network device, or a chip (system) or other parts or components that can be set in the network device, or a device that includes a network device, which is not limited in this application.

[0332] In addition, the technical effects of the communication device 1000 can refer to the technical effects of the above-mentioned communication method, which will not be repeated here.

[0333] Figure 11 is a second structural diagram of a communication device provided in an embodiment of the present application. Exemplarily, the communication device may be a terminal, or a chip (system) or other component or assembly that can be provided in a terminal. As shown in Figure 11, the communication device 1100 may include a processor 1101. Optionally, the communication device 1100 may further include a memory 1102 and / or a transceiver 1103. The processor 1101 is coupled to the memory 1102 and the transceiver 1103, such as by a communication bus.

[0334] The following is a detailed introduction to the various components of the communication device 1100 with reference to FIG11 :

[0335] The processor 1101 is the control center of the communication device 1100 and can be a single processor or a collective term for multiple processing elements. For example, the processor 1101 can be one or more central processing units (CPUs), an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application, such as one or more digital signal processors (DSPs) or one or more field programmable gate arrays (FPGAs).

[0336] Optionally, the processor 1101 can execute various functions of the communication device 1100 by running or executing software programs stored in the memory 1102 and calling data stored in the memory 1102, such as executing the communication methods shown in Figures 6 to 9 above.

[0337] In a specific implementation, as an embodiment, the processor 1101 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG11 .

[0338] In a specific implementation, as an embodiment, the communication device 1100 may also include multiple processors, such as the processor 1101 and the processor 1104 shown in FIG11 . Each of these processors may be a single-core processor (single-CPU) or a multi-core processor (multi-CPU). The processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0339] Among them, the memory 1102 is used to store the software program for executing the solution of this application, and the execution is controlled by the processor 1101. The specific implementation method can refer to the above method embodiment and will not be repeated here.

[0340] Alternatively, the memory 1102 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type of dynamic storage device that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, an optical disc storage (including a compact disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory 1102 may be integrated with the processor 1101 or exist independently and be coupled to the processor 1101 via an interface circuit (not shown in FIG. 11 ) of the communication device 1100, which is not specifically limited in this embodiment of the present application.

[0341] Transceiver 1103 is used for communication with other communication devices. For example, if communication device 1100 is a terminal, transceiver 1103 can be used to communicate with a network device or another terminal device. For another example, if communication device 1100 is a network device, transceiver 1103 can be used to communicate with a terminal or another network device.

[0342] Optionally, the transceiver 1103 may include a receiver and a transmitter (not shown separately in FIG11 ), wherein the receiver is used to implement a receiving function, and the transmitter is used to implement a transmitting function.

[0343] Optionally, the transceiver 1103 may be integrated with the processor 1101 or exist independently and be coupled to the processor 1101 through an interface circuit (not shown in FIG. 11 ) of the communication device 1100 . This embodiment of the present application does not specifically limit this.

[0344] It is understandable that the structure of the communication device 1100 shown in FIG11 does not constitute a limitation on the communication device, and an actual communication device may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0345] In addition, the technical effects of the communication device 1100 can refer to the technical effects of the methods described in the above method embodiments, and will not be repeated here.

[0346] It should be understood that the processor in the embodiments of the present application may be a central processing unit (CPU), and the processor may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.

[0347] It should also be understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of random access memory (RAM) are available, such as static RAM (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0348] The above embodiments can be implemented in whole or in part by software, hardware (such as circuits), firmware or any other combination. When implemented using software, the above embodiments can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer program are loaded or executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (such as infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that contains one or more available media sets. The available medium can be a magnetic medium (for example, a floppy disk, a hard disk, a tape), an optical medium (for example, a DVD), or a semiconductor medium. The semiconductor medium can be a solid-state drive.

[0349] It should be understood that the term "and / or" as used herein simply describes a relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A alone, A and B together, or B alone. A and B can be singular or plural. Furthermore, the character " / " as used herein generally indicates an "or" relationship between the associated objects, but it may also indicate an "and / or" relationship. For specific understanding, please refer to the context.

[0350] In this application, "at least one" means one or more, and "plurality" means two or more. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or plural.

[0351] 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.

[0352] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in 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. Professional and technical personnel can 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.

[0353] 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.

[0354] 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.

[0355] 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.

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

[0357] 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 technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a 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 a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0358] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A communication method, characterized in that: The method is applied to a first network element, and the method includes: The first network element sends a first message to the second network element, where the first message requests to register a first configuration of a first network function with the second network element, where the first network element is used to provide link load orchestration, and the first configuration includes information of the first network element; The first network element receives a second message from the second network element, where the second message indicates that the first configuration is successfully registered.

2. The method according to claim 1, characterized in that The information of the first network element includes at least one of the following: address information of the first network element, or identification-related information of the first network element.

3. The method according to claim 2, characterized in that The identification-related information of the first network element includes at least one of the following: information used to identify the set to which the first network element belongs, or information used to identify the first network element.

4. The method according to any one of claims 1 to 3, characterized in that The first network function is registered with the first network element.

5. The method according to claim 4, characterized in that The registration of the first network function with the first network element includes the first network element acquiring a second configuration of the first network function, where the second configuration includes at least one of the following: an identifier of the first network function, an address of the first network function, or a type of the first network function.

6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: The first network element receives a request message from a second network function, where the request message indicates that the second network function requests the first network function to provide a service; In response to the request message, the first network element determines whether the first network element and the second network function belong to the same data center; If the first network element and the second network function belong to the same data center, the first network element provides the service of the first network function to the second network function on behalf of the first network function; If the first network element and the second network function belong to different data centers, the first network element triggers the redirection process.

7. The method according to claim 6, characterized in that The first network element triggers a redirection process, including: The first network element indicates that the second network function needs to be redirected; or; The first network element sends a request message to a third network element, where the request message indicates that the second network function requests the first network function to provide a service, the third network element provides link load orchestration, and the second network function and the third network element belong to the same data center.

8. The method according to claim 7, characterized in that The method further comprises: The first network element obtains a third configuration of the first network function, wherein the third configuration includes information of the third network element; The first network element sends the third configuration to the second network function.

9. The method according to any one of claims 1 to 5, characterized in that The method further comprises: The first network element receives a request message from a second network function, where the request message indicates that the second network function requests to discover a network function that can provide a service for the second network function; In response to the request message, the first network element obtains a first configuration of the first network function, where the first network function is capable of providing a service for the second network function; The first network element sends the first configuration to the second network function.

10. The method according to claim 9, characterized in that The second network function is registered with the first network element.

11. A communication method, characterized in that: The method is applied to a second network element, and the method includes: The second network element receives a first message from a first network element, where the first message requests to register a first configuration of a first network function with the second network element, the first network element provides link load orchestration, and the first configuration includes information of the first network element; The second network element saves the first configuration; The second network element sends a second message to the second network element, where the second message indicates that the first configuration is successfully registered.

12. The method according to claim 11, characterized in that The information of the first network element includes at least one of the following: address information of the first network element, or identification-related information of the first network element.

13. The method according to claim 12, characterized in that The identification-related information of the first network element includes at least one of the following: information used to identify the set to which the first network element belongs, or information used to identify the first network element.

14. The method according to any one of claims 11 to 13, characterized in that The method further comprises: The second network element receives a request message from a second network function, where the request message indicates that the second network function requests to discover a network function that can provide a service for the second network function; The second network element sends the first configuration of the first network function to the second network function according to the request message, so that the first network function can provide services for the second network function.

15. The method according to claim 14, characterized in that In a case where the first configuration includes information related to an identifier of the first network element, the method further includes: The second network element receives identification-related information of the first network element from the second network function; The second network element sends the configuration of the first network element to the second network function according to the identification related information of the first network element, where the configuration of the first network element includes the address information of the first network element.

16. The method according to any one of claims 11 to 13, characterized in that The method further comprises: The second network element receives a request message from the first network element, where the request message indicates that the second network function requests to discover a network function that can provide a service for the second network function; The second network element sends a first configuration of the first network function to the first network element according to the request message, and the first network function can provide a service for the second network function.

17. A communication method, characterized in that: The method is applied to a second network function, and the method includes: The second network function sends a request message to the second network element, where the request message indicates that the second network function requests to discover a network function that can provide a service for the second network function; The second network function receives, by the second network element, a first configuration of the first network function returned according to the request message, where the first network function is capable of providing services for the second network function, the first configuration including information of the first network element, and the first network element provides link load orchestration; The second network function requests the first network function to provide a service through the first network element.

18. The method according to claim 17, characterized in that The information of the first network element includes at least one of the following: address information of the first network element, or identification-related information of the first network element.

19. The method according to claim 18, characterized in that The identification-related information of the first network element includes at least one of the following: information used to identify the set to which the first network element belongs, or information used to identify the first network element.

20. The method according to claim 19, characterized in that In a case where the first configuration includes information related to an identifier of the first network element, the method further includes: The second network function sends the identification-related information of the first network element to the second network element; The second network function receives the configuration of the first network element returned by the second network element according to the identification related information of the first network element, where the configuration of the first network element includes the address information of the first network element; The second network function requests the first network function to provide a service through the first network element, including: The second network function requests the first network function to provide a service through the first network element according to the address information of the first network element.

21. The method according to any one of claims 17 to 20, characterized in that The second network function requests the first network function to provide a service through the first network element, including: The second network function sends a request message to the first network element, where the request message indicates that the second network function requests the first network function to provide a service; The second network function obtains the service of the first network function through the first network element agent service discovery, or the second network function is redirected according to the instruction of the first network element.

22. A communication method, characterized in that: The method is applied to a second network function, and the method includes: The second network function sends a request message to the first network element, where the request message indicates that the second network function requests the first network element to discover a network function that can provide a service for the second network function, wherein the first network element provides link load orchestration; The second network function receives a first configuration of a first network function from the first network element, where the first network function is capable of providing a service for the second network function; The second network function requests the first network function to provide a service.

23. The method according to claim 22, characterized in that The method further comprises: The second network function is registered with the first network element.

24. The method according to claim 23, wherein The second network function registering with the first network element includes: The second network function sends the configuration of the second network function to the first network element.

25. A communication device, characterized in that: The apparatus comprises: a module for performing the method according to any one of claims 1-24.

26. A communication device, characterized in that: The communication device comprises: a processor and a memory; the memory is used to store computer instructions, and when the processor executes the instructions, the communication device executes the method according to any one of claims 1 to 24.

27. A communication system, characterized in that: The system includes at least one of the following: one or more network elements configured to execute the method according to any one of claims 1 to 24.

28. A computer-readable storage medium, characterized in that The computer-readable storage medium comprises a computer program or instructions, which, when executed on a computer, causes the computer to perform the method according to any one of claims 1 to 24.

29. A computer program product, characterized in that The computer program product comprises a computer program or instructions, which, when executed on a computer, causes the computer to perform the method according to any one of claims 1 to 24.

Images