A communication method and apparatus

Abstract

A communication method and apparatus for implementing the combined deployment and selection of multiple network functions in a 5G architecture, helping to reduce deployment costs and complexity. In the present application, a requesting network function sends a first network function type to a network warehouse function, the network warehouse function receives the first network function type from the requesting network function, the network warehouse function sends an overview of the first network function corresponding to the first network function type to the requesting network function, and the requesting network function receives an overview of the first network function corresponding to the first network function type from the network warehouse function, wherein the overview of the first network function includes a first indication, and the first indication is used to indicate that the first network function is deployed in combination with a second network function, and the network function types of the first network function and the second network function are different.

Description

Technical Field

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

[0002] In the 4G and 5G convergence scenario, 4G network elements and 5G network functions (NFs) can be deployed together, such as the PDN Gateway (PGW) and session management function (SMF), or the network exposure function (NEF) and service capability exposure function (SCEF). Taking the combined deployment of PGW and SMF as an example, when the SMF registers with the network repository function (NRF), it also registers the fully qualified domain name (FQDN) of the merged PGW. When other functions discover the SMF at the NRF, they can find the SMF merged with the PGW by providing the FQDN. By merging 4G network elements and 5G network functions, service interruption can be avoided when terminal devices switch between cells of different standards.

[0003] Existing combined deployment is only used in specific scenarios of 4G and 5G convergence, such as the aforementioned combined deployment of PGW and SMF, and the combined deployment of NEF and SCEF. However, in the current 5G architecture, in order to reduce deployment costs and complexity, there is a need to combine the deployment of multiple 5G network functions.

[0004] Therefore, it is necessary to provide a method for realizing the combined deployment and selection of multiple 5G network functions in the 5G architecture. Summary of the Invention

[0005] The present application provides a communication method and apparatus for realizing the combined deployment and selection of multiple network functions in a 5G architecture, thereby helping to reduce deployment costs and complexity.

[0006] In a first aspect, the present application provides a communication method, including: a network warehouse function receives a first network function type from a requesting network function; the network warehouse function sends a profile of a first network function corresponding to the first network function type to the requesting network function, where the profile of the first network function includes a first indication, and the first indication is used to indicate that the first network function and the second network function are combined / co-located deployment, and the network function types of the first network function and the second network function are different.

[0007] In the above technical solution, the requesting network function requests the network warehouse function for an overview of a first network function of a first network function type. The overview of the first network function includes a first indication, which is used to indicate that the first network function is deployed in combination with the second network function, so that the requesting network function can determine that the first network function is deployed in combination with other network functions. In this way, the requesting network function requests the network warehouse function for a network function deployed in combination with other network functions, which helps to realize the combined deployment of multiple network functions, helps to reduce deployment costs and complexity, and provides a more flexible network function deployment method. Moreover, the communication delay between the first network function and the second network function that are deployed in combination is short, which helps to optimize the service experience of the terminal device.

[0008] In a possible implementation manner, the first indication includes an instance identifier of the second network function.

[0009] In the above technical solution, the requesting network function can directly determine the existence of the second network function deployed in combination with the first network function based on the instance identifier of the second network function in the first indication, which helps the requesting network function to request an overview of the corresponding network function from the network warehouse function based on the instance identifier of the second network function when it needs to discover the network function deployed in combination with the first network function, so that the requesting network function can select the first network function and the second network function deployed in combination.

[0010] In a possible implementation, the method further includes: the network warehouse function receiving an instance identifier of a second network function from a requesting network function; and the network warehouse function sending an overview of the second network function corresponding to the instance identifier of the second network function to the requesting network function.

[0011] In the above technical solution, when the requesting network function needs to discover the second network function from the network repository function, it can request the network repository function for a summary of the second network function corresponding to the instance identifier of the second network function based on the instance identifier of the second network function in the summary of the first network function. Furthermore, the requesting network function can determine the network function type of the second network function to be deployed in conjunction with the first network function based on the summary of the second network function.

[0012] In a possible implementation manner, the first indication further includes a second network function type of the second network function, and the method further includes: the network repository function receiving the second network function type from the requesting network function.

[0013] In the above technical solution, the requesting network function can determine, based on the second network function type in the first network function overview, that the second network function deployed in combination with the first network function corresponds to the second network function type. When the requesting network function needs to select a network function corresponding to the second network function type that is deployed in combination with the first network function, the second network function can be discovered from the network warehouse function.

[0014] In a possible implementation manner, the first indication includes a merge attribute.

[0015] In the above technical solution, the merge attributes in the overviews of the multiple network functions that are deployed in a merged manner are the same, and the network warehouse function can determine the overviews of other network functions that are deployed in a merged manner with the first network function based on the merge attributes in the overview of the first network function. Correspondingly, the requesting network function can determine the merged deployment of the first network function and the second network function based on the merge attributes in the overview of the first network function and the merge attributes in the overview of the second network function. Through this merge attribute, the requesting network function can request the network warehouse function to deploy multiple network functions in a merged manner, that is, the requesting network function can select the first network function and the second network function that are deployed in a merged manner. Moreover, when deploying other new network functions in a merged manner with the first network function, the overview of the new network function can be set to include the same merge attributes, which has better forward compatibility and scalability.

[0016] In a possible implementation manner, the method further includes: the network warehouse function sending a summary of the second network function to the requesting network function, where the summary of the second network function includes the merged attribute.

[0017] In the above technical solution, the network warehouse function can not only send an overview of the first network function to the requesting network function, but also, based on the merging attributes in the overview of the first network function, send an overview of the second network function with the same merging attributes to the requesting network function. The requesting network function does not need to request the network warehouse function again for an overview of the second network function that is merged and deployed with the first network function, which helps to reduce the interactive signaling between the requesting network function and the network warehouse function and simplify the processing on the requesting network function.

[0018] In a possible implementation, the method further includes: the network repository function receiving the merged attributes from the requesting network function and the second network function type from the second network function.

[0019] In the above technical solution, the requesting network function can request an overview of the second network function from the network repository function based on the merge attribute and the second network function type. Accordingly, the network repository function can send an overview of the second network function corresponding to the merge attribute and the second network function type to the requesting network function. When the requesting network function needs to select a network function corresponding to the second network function type to be deployed in combination with the first network function, the second network function can be discovered from the network repository function, which helps reduce unnecessary signaling interactions between the requesting network function and the network repository function.

[0020] In a possible implementation, the method further includes: the network warehouse function receiving a first registration request from the first network function, where the first registration request includes an overview of the first network function; and the network warehouse function sending a first registration success response to the first network function.

[0021] In a possible implementation, it also includes: the network warehouse function receives a second registration request from the second network function, the second registration request includes an overview of the second network function, the overview of the second network function includes a second indication, and the second indication is used to indicate that the second network function is deployed together with the first network function; the network warehouse function sends a second registration success response to the second network function.

[0022] In the above technical solution, when a network function registers with a network warehouse function, an overview of the network function is carried in the registration request, and the overview of the network function includes a merge indication for indicating that the network function is deployed in combination with other network functions. Therefore, when the network warehouse function receives a discovery request from a requesting network function, it can, based on the merge indication in the network function overview, provide feedback to the requesting network function on the overview of other network functions deployed in combination with the network function, or the requesting network function can, based on the merge indication in the network function overview, request the network warehouse function again for an overview of other network functions, thereby providing an implementation method for the requesting network function to request the network warehouse function to merge and deploy multiple network functions when multiple network functions are deployed in combination in a 5G system.

[0023] The above technical solution can provide a general method for discovering merged network functions. Any type of merged network function deployment in the 5G network can be requested for network function discovery through the above technical solution.

[0024] In a possible implementation, it also includes: the network warehouse function receives a merged network function preference indication from the requesting network function, and the merged network function preference indication is used to indicate: when the overview of the network function includes a merge indication, an overview of the network function including the merge indication is sent to the requesting network function; when the overview of the network function does not include a merge indication, an overview of the network function not including the merge indication is sent to the requesting network function.

[0025] In the above technical solution, the requesting network function sends a preferred indication of merging network functions to the network warehouse function. This avoids the situation where the network warehouse function does not provide a network function overview to the requesting network function if the network function overview does not include a merging indication, resulting in the requesting network function failing to request the network function from the network warehouse function and interrupting communication with the terminal device. This helps to improve the success rate of the requesting network function receiving the network function overview, ensuring the service experience of the terminal device.

[0026] In a second aspect, the present application provides a communication method, including: requesting a network function to send a first network function type to a network warehouse function; requesting the network function to receive an overview of a first network function corresponding to the first network function type from the network warehouse function, the overview of the first network function including a first indication, the first indication being used to indicate that the first network function and the second network function are deployed together, and the network function types of the first network function and the second network function are different.

[0027] In a possible implementation manner, the first indication includes an instance identifier of the second network function.

[0028] In a possible implementation, the method further includes: requesting the network function to send an instance identifier of the second network function to the network warehouse function; and requesting the network function to receive an overview of the second network function corresponding to the instance identifier of the second network function from the network warehouse function.

[0029] In one possible implementation, the first indication also includes a second network function type of the second network function, and the method also includes: requesting the network function to determine the combined deployment of the first network function and the second network function based on the second network function type, and sending the second network function type to the network warehouse function.

[0030] In a possible implementation manner, the first indication includes a merge attribute.

[0031] In a possible implementation, the method further includes: requesting the network function to receive an overview of the second network function from the network repository function, wherein the overview of the second network function includes the merged attribute.

[0032] In a possible implementation manner, the method further includes: requesting the network function to send the merged attribute and the second network function type of the second network function to the network repository function.

[0033] In a possible implementation, the method further includes: requesting the network function to determine, based on the merging attributes in the overview of the second network function and the merging attributes in the overview of the first network function, merging the first network function and the second network function to be deployed.

[0034] In a possible implementation, it also includes: requesting the network function to send a merged network function preference indication to the network warehouse function, where the merged network function preference indication is used to indicate: when the overview of the network function includes a merge indication, receiving an overview of the network function including the merge indication from the network warehouse function; when the overview of the network function does not include a merge indication, receiving an overview of the network function including the merge indication from the network warehouse function.

[0035] In a third aspect, the present application provides a communication method, including: a first network function sends a first registration request to a network warehouse function, the first registration request includes an overview of the first network function, the overview of the first network function includes a first indication, the first indication is used to indicate that the first network function and the second network function are deployed together, and the network function types of the first network function and the second network function are different; the first network function receives a first registration success response from the network warehouse function.

[0036] In a fourth aspect, the present application provides a communication method, including: requesting a network function to send a first network function type to a network warehouse function; the network warehouse function receives the first network function type from the requesting network function; the network warehouse function sends an overview of the first network function corresponding to the first network function type to the requesting network function; the requesting network function receives an overview of the first network function corresponding to the first network function type from the network warehouse function; wherein the overview of the first network function includes a first indication, and the first indication is used to indicate that the first network function and the second network function are deployed together, and the network function types of the first network function and the second network function are different.

[0037] The technical effects that can be achieved in any of the second to fourth aspects mentioned above can refer to the description of the beneficial effects in the first aspect mentioned above, and will not be repeated here.

[0038] In a fifth aspect, the present application provides a communication method, including: a network warehouse function receives a first network function type and a second network function type from a requesting network function; the network warehouse function sends a merged network function overview to the requesting network function, where the merged network function overview is an overview of the merged deployment of a first network function corresponding to the first network function type and a second network function corresponding to the second network function type, and the first network function type and the second network function type are different.

[0039] In the above technical solution, the requesting network function requests an overview of a merged network function of a first network function type and a second network function type from the network warehouse function. This overview is an overview of the combined deployment of a first network function corresponding to the first network function type and a second network function corresponding to the second network function type. This enables the combined deployment of multiple network functions, and the requesting network function can request an overview of the merged network function, thereby helping to reduce deployment costs and complexity and providing a more flexible network function deployment method. Furthermore, the communication latency between the combined deployed first and second network functions is short, helping to optimize the service experience of terminal devices.

[0040] In a possible implementation, it also includes: the network warehouse function receives a third registration request from the merged network function, the third registration request includes a merged network function overview, the merged network function overview includes a first network function type and a second network function type; the network warehouse function sends a third registration success response to the merged network function.

[0041] In the above technical solution, when the merged network function registers with the network warehouse function, the registration request carries an overview of the merged network function, and the overview of the merged network function includes the network function types of the multiple network functions deployed in the merged network function. When the requesting network function discovers the merged network function from the network warehouse function, it can discover the merged network function with the multiple network function types in the overview of the merged network function, and provide an implementation method for the requesting network function to request the network warehouse function to merge the network functions when multiple network functions are merged and deployed in a 5G system. The above technical solution can provide a general method for discovering merged deployed network functions, and any type of merged deployment of network functions in the 5G network can be discovered by the requesting network function through the above technical solution.

[0042] In a possible implementation, the merged network function summary further includes an instance identifier corresponding to both the first network function and the second network function.

[0043] In a sixth aspect, the present application provides a communication method, including: requesting a network function to send a first network function type and a second network function type to a network warehouse function; requesting the network function to receive a merged network function overview from the network warehouse function, the merged network function overview being an overview of the merged deployment of a first network function corresponding to the first network function type and a second network function corresponding to the second network function type, and the first network function type and the second network function type are different.

[0044] In a possible implementation, the merged network function summary further includes an instance identifier corresponding to both the first network function and the second network function.

[0045] In a seventh aspect, the present application provides a communication method, including: the merged network function sends a third registration request to the network warehouse function, the third registration request includes a merged network function overview, the merged network function overview is an overview of the merged deployment of a first network function corresponding to a first network function type and a second network function corresponding to a second network function type, and the first network function type and the second network function type are different; the merged network function receives a third registration success response from the network warehouse function.

[0046] In an eighth aspect, the present application provides a communication method, including: a requesting network function sends a first network function type and a second network function type to a network warehouse function; the network warehouse function receives the first network function type and the second network function type from the requesting network function, and the network warehouse function sends a merged network function overview to the requesting network function; the requesting network function receives the merged network function overview from the network warehouse function; wherein the merged network function overview is an overview of the merged deployment of the first network function corresponding to the first network function type and the second network function corresponding to the second network function type, and the first network function type and the second network function type are different.

[0047] The technical effects that can be achieved in any of the sixth to eighth aspects mentioned above can refer to the description of the beneficial effects in the fifth aspect mentioned above, and will not be repeated here.

[0048] In the ninth aspect, an embodiment of the present application provides a communication device, which has the function of implementing the network warehouse function in the first aspect or any possible implementation of the first aspect, or the function of requesting the network function in the second aspect or any possible implementation of the second aspect, or the function of the first network function in the third aspect or any possible implementation of the third aspect, or the function of requesting the network function in the fifth aspect or any possible implementation of the fifth aspect, or the function of merging network functions in the sixth aspect or any possible implementation of the sixth aspect, or the function of the network warehouse function in the seventh aspect or any possible implementation of the seventh aspect.

[0049] The functions of the above-mentioned communication device can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules, units or means corresponding to the above-mentioned functions.

[0050] In one possible implementation, the structure of the device includes a processing unit and a transceiver unit, wherein the processing unit is configured to support the device in executing the function of the network warehouse function in the first aspect or any possible implementation of the first aspect, or the function of requesting a network function in the second aspect or any possible implementation of the second aspect, or the function of the first network function in the third aspect or any possible implementation of the third aspect, or the function of requesting a network function in the fifth aspect or any possible implementation of the fifth aspect, or the function of merging network functions in the sixth aspect or any possible implementation of the sixth aspect, or the function of the network warehouse function in the seventh aspect or any possible implementation of the seventh aspect. The transceiver unit is used to support communication between the device and other communication devices. For example, when the device is the network warehouse function in the first aspect or any possible implementation of the first aspect, it can receive a first network function type from the requesting network function and send a summary of the first network function corresponding to the first network function type to the requesting network function. The communication device may also include a storage module, which is coupled to the processing unit and stores program instructions and data necessary for the device. As an example, the processing unit may be a processor, the communication module may be a transceiver, and the storage module may be a memory. The memory may be integrated with the processor or may be provided separately from the processor.

[0051] In another possible implementation, the structure of the device includes a processor and may also include a memory. The processor is coupled to the memory and can be used to execute computer program instructions stored in the memory to cause the device to perform the method of the first aspect or any possible implementation of the first aspect, or the method of the second aspect or any possible implementation of the second aspect, or the method of the third aspect or any possible implementation of the third aspect, or the method of the fifth aspect or any possible implementation of the fifth aspect, or the method of the sixth aspect or any possible implementation of the sixth aspect, or the method of the seventh aspect or any possible implementation of the seventh aspect. Optionally, the device also includes a communication interface, and the processor is coupled to the communication interface. When the device is a device, the communication interface can be a transceiver or an input / output interface; when the device is a chip included in the device, the communication interface can be the chip's input / output interface. Optionally, the transceiver can be a transceiver circuit, and the input / output interface can be an input / output circuit.

[0052] In the tenth aspect, an embodiment of the present application provides a chip system, comprising: a processor, the processor being coupled to a memory, the memory being used to store programs or instructions, and when the program or instructions are executed by the processor, the chip system implements the method of the above-mentioned first aspect or any possible implementation of the first aspect, or implements the method of the above-mentioned second aspect or any possible implementation of the second aspect, or implements the method of the above-mentioned third aspect or any possible implementation of the third aspect, or implements the method of the above-mentioned fifth aspect or any possible implementation of the fifth aspect, or implements the method of the above-mentioned sixth aspect or any possible implementation of the sixth aspect, or implements the method of the above-mentioned seventh aspect or any possible implementation of the seventh aspect.

[0053] Optionally, the chip system further includes an interface circuit for transmitting interactive code instructions to the processor.

[0054] Optionally, there may be one or more processors in the chip system, and the processor may be implemented in hardware or software. When implemented in hardware, the processor may be a logic circuit, an integrated circuit, etc. When implemented in software, the processor may be a general-purpose processor implemented by reading software code stored in a memory.

[0055] Optionally, the chip system may include one or more memories. The memory may be integrated with the processor or provided separately from the processor. For example, the memory may be a non-transient processor, such as a read-only memory (ROM), which may be integrated with the processor on the same chip or provided on separate chips.

[0056] In the eleventh aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program or instruction stored thereon. When the computer program or instruction is executed, the computer executes the method of the first aspect or any possible implementation of the first aspect, or executes the method of the second aspect or any possible implementation of the second aspect, or executes the method of the third aspect or any possible implementation of the third aspect, or executes the method of the fifth aspect or any possible implementation of the fifth aspect, or executes the method of the sixth aspect or any possible implementation of the sixth aspect, or executes the method of the seventh aspect or any possible implementation of the seventh aspect.

[0057] In the twelfth aspect, an embodiment of the present application provides a computer program product. When a computer reads and executes the computer program product, the computer executes the method in the first aspect or any possible implementation of the first aspect, or executes the method in the second aspect or any possible implementation of the second aspect, or executes the method in the third aspect or any possible implementation of the third aspect, or executes the method in the fifth aspect or any possible implementation of the fifth aspect, or executes the method in the sixth aspect or any possible implementation of the sixth aspect, or executes the method in the seventh aspect or any possible implementation of the seventh aspect.

[0058] In a thirteenth aspect, an embodiment of the present application provides a communication system, which includes a network warehouse function for executing the method in the first aspect or any possible implementation of the first aspect, a request network function for executing the method in the second aspect or any possible implementation of the second aspect, and a first network function for executing the method in the third aspect or any possible implementation of the third aspect. Alternatively, the communication system includes a request network function for executing the method in the fifth aspect or any possible implementation of the fifth aspect, a merge network function for executing the method in the sixth aspect or any possible implementation of the sixth aspect, and a network warehouse function for executing the method in the seventh aspect or any possible implementation of the seventh aspect.

[0059] The technical effects that can be achieved in any of the above-mentioned aspects 9 to 13 can refer to the description of the beneficial effects in the above-mentioned first aspect or fifth aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0060] Figure 1 A schematic diagram of a communication system architecture provided for this application;

[0061] Figure 2 A flowchart of a network function registration process provided as an example in this application;

[0062] Figure 3 A schematic diagram of a network function discovery process provided as an example in this application;

[0063] Figure 4 A flowchart of another network function discovery process provided by this application as an example;

[0064] Figure 5 A flowchart of a network function registration and discovery process provided as an example in this application;

[0065] Figure 6This is a schematic diagram of the structure of a communication device exemplarily provided in this application;

[0066] Figure 7 This is a schematic diagram of the structure of another communication device provided as an example in this application. DETAILED DESCRIPTION

[0067] The embodiments of the present application will be described in detail below with reference to the accompanying drawings.

[0068] Figure 1 A schematic diagram of a mobile communication network architecture is shown by way of example, which includes terminal equipment, access network equipment, access and mobility management functions, session management functions, user plane functions, policy control functions, network slice selection functions, network slice specific authentication and authorization functions, network warehouse functions, network data analysis functions, unified data management functions, unified data storage functions, authentication service functions, network capability exposure functions, terminal wireless capability management functions, binding support functions, application functions, and a data network (DN) connected to the operator's network.

[0069] For example, the terminal device accesses the wireless network through the access node at the current location. The terminal device can send service data to the data network and receive service data from the data network through the access network device and the user plane function.

[0070] The access and mobility management function is mainly used for the attachment, mobility management, tracking area update process, etc. of terminal devices in the mobile network. In the 5G communication system, the access and mobility management function can be the access and mobility management function (AMF). In future communication systems (such as 6G communication systems), the access and mobility management function can still be AMF, or it can have other names, which is not limited in this application.

[0071] The session management function is primarily used for session management in mobile networks, such as session establishment, modification, and release. Specific functions include allocating Internet Protocol addresses to terminal devices and selecting user plane functions that provide message forwarding capabilities. In 5G communication systems, the session management function may be a session management function (SMF). In future communication systems (such as 6G communication systems), the session management function may still be SMF, or may have other names, which are not limited in this application.

[0072] The user plane function is mainly used to process user messages, such as forwarding and billing. In the 5G communication system, the user plane function can be the user plane function (UPF). In future communication systems (such as 6G communication systems), the user plane function can still be UPF, or it can have other names, which is not limited in this application.

[0073] Policy control function, including policy control function, charging policy control function, quality of service (QoS) control, etc. In 5G communication systems, the policy control function can be a policy control function (PCF). In future communication systems (such as 6G communication systems), the policy control function can still be PCF, or it can have other names, which is not limited in this application.

[0074] The network slice selection function is mainly used to select a suitable network slice for the service of the terminal device. In the 5G communication system, the network slice selection function can be a network slice selection function (NSSF). In future communication systems (such as 6G communication systems), the network slice selection function can still be NSSF, or it can have other names, which is not limited by this application.

[0075] The network slice-specific authentication and authorization function (NSSAAF) is mainly used to authenticate and authorize terminal devices to access specific network slices.

[0076] The network repository function is mainly used to provide registration and discovery of network functions or services provided by network functions. In 5G communication systems, the network repository function can be a network repository function (NRF). In future communication systems (such as 6G communication systems), the network repository function can still be NRF, or it can have other names, which are not limited by this application.

[0077] The network data analysis function can collect data from various network functions, such as the policy control function, session management function, user plane function, access management function, and application function (through the network capability exposure function), and perform analysis and prediction. In the 5G communication system, the network data analysis function can be the network data analysis function (NWDAF). In future communication systems (such as 6G communication systems), the network data analysis function can still be NWDAF, or it can have other names, which is not limited by this application.

[0078] The unified data management function is mainly used to manage the contract information of terminal devices. In the 5G communication system, the unified data management function can be a unified data management (UDM) function. In future communication systems (such as 6G communication systems), the unified data management function can still be the UDM function, or it can have other names, which is not limited by this application.

[0079] The unified data storage function is mainly used to store structured data information, including contract information, policy information, and network data or business data defined in a standard format. In the 5G communication system, the unified data storage function can be a unified data repository (UDR) function. In future communication systems (such as 6G communication systems), the unified data storage function can still be a UDR function, or it can have other names, which is not limited by this application.

[0080] The authentication service function is mainly used to perform security authentication on terminal devices. In 5G communication systems, the authentication service function can be an authentication server function (AUSF). In future communication systems (such as 6G communication systems), the authentication service function can still be AUSF, or it can have other names, which is not limited by this application.

[0081] The network capability exposure function can controllably expose some network functions to applications. In 5G communication systems, the network capability exposure function can be NEF. In future communication systems (such as 6G communication systems), the network capability exposure function can still be NEF, or it can have other names, which are not limited by this application.

[0082] The terminal radio capability management function is used to store and manage the radio capabilities of terminal devices within the network. In 5G communication systems, the terminal radio capability management function can be the terminal radio capability management function (UCMF). In future communication systems (such as 6G communication systems), the terminal radio capability management function can still be UCMF, or it can have other names, which are not limited by this application.

[0083] The binding support function is used to maintain the correspondence between the protocol (Internet Protocol, IP) addresses and service functions of the interconnected user networks. In the 5G communication system, the binding support function can be a binding support function (BSF). In future communication systems (such as 6G communication systems), the binding support function can still be BSF, or it can have other names, which is not limited by this application.

[0084] The application function can provide service data of various applications to the control plane function of the operator's communication network, or obtain network data information and control information from the control plane function of the communication network. In the 5G communication system, the application function can be an application function (AF). In future communication systems (such as 6G communication systems), the application function can still be AF, or it can have other names, which is not limited by this application.

[0085] Data networks are primarily used to provide data transmission services to terminal devices. Data networks can be private networks, such as local area networks (LANs), public data networks (PDNs), such as the Internet, or proprietary networks deployed by operators, such as those configured with IP multimedia corenetwork subsystem (IMS) services.

[0086] It should be noted that in the embodiments of the present application, functions may also be referred to as network elements, network functions, functional entities, devices, etc. For example, the access and mobility management function may also be referred to as an access and mobility management network element, an access and mobility management network function, or an access and mobility management functional entity, etc. The names of the various functions are not limited in this application. Those skilled in the art may replace the names of the aforementioned functions with other names while still performing the same functions, and all such changes fall within the scope of protection of this application.

[0087] For the convenience of description, the access and mobility management network element, session management function, network slice selection function, network slice specific authentication and authorization function, network warehouse function, and binding support function can be abbreviated as AMF, SMF, NSSF, NSSAAF, NRF, and BSF respectively.

[0088] Combine Figure 1 The mobile communication network architecture shown exemplarily, the present application provides a combined deployment scenario. In this combined deployment scenario, multiple network functions can be deployed in a combined manner (combined deployment can also be called unified deployment, which can be expressed as combined / co-located deployment in English), such as combining network function 1 and network function 2. When the combined deployed network function 1 acts as a client and needs to call the service provided by network function 2 as a server, network function 1 can give priority to the combined deployed network function 2, which helps to reduce communication complexity and communication delay. For requesting network functions, such as network function 3, when selecting network function 1 and network function 2, you can also choose the combined deployed network function 1 and network function 2.

[0089] For example, the combined deployment of network function 1 and network function 2 can be understood as follows:

[0090] a. Network function 1 and network function 2 are deployed in a combined network function (or entity, device, etc.), where the combined network function can simultaneously implement the functions of network function 1 and network function 2. For example, network function 1 and network function 2 share a processor. In another example, network function 1 and network function 2 each implement their respective functions using different processors within a network element.

[0091] b. Network function 1 and network function 2 are physically deployed together, but they belong to different network elements. For example, network function 1 and network function 2 can be two different network elements, but they are deployed in the same computer room.

[0092] The following two scenarios are provided as examples based on specific applications:

[0093] For example, in scenario 1, network function 1 is SMF, network function 2 is BSF, and network function 3 is AMF. SMF1 and BSF1 are deployed together, and BSF2 is deployed separately (that is, it is not deployed together with SMF1). When SMF1 needs to call the service of BSF, it can give priority to BSF1 instead of BSF2. Since SMF1 and BSF1 are deployed together, SMF1 calls BSF1, which can effectively reduce communication complexity and communication latency compared to SMF1 calling BSF2. When AMF needs to select SMF, it can choose the deployed SMF1 together. Later, when AMF needs to select BSF, it can also choose BSF1 deployed together with SMF1.

[0094] For another example, in scenario 2, network function 1 is NSSF, network function 2 is NSSAAF, and network function 3 is AMF. NSSF1 and NSSAAF1 are deployed together, and NSSAAF2 is deployed separately (that is, it is not deployed together with NSSF1). When NSSF1 needs to call the service of NSSAAF, it can give priority to NSSAAF1 instead of NSSAAF2. Since NSSF1 and NSSAAF1 are deployed together, NSSF1 calling NSSAAF1 can effectively reduce communication complexity and communication delay compared to NSSF1 calling NSSAAF2. When AMF needs to select NSSF, it can choose the merged NSSF1. Then, when AMF needs to select NSSAAF, it can also choose NSSAAF1 deployed together with NSSF1.

[0095] The present application provides a communication method, which is applicable to the above-mentioned combined deployment scenario, wherein the combined deployment scenario includes multiple network functions that are combined and deployed, and the network function types of any two network functions in the combined and deployed multiple network functions are different. Furthermore, the multiple network functions that are combined and deployed may include a first network function and one or more other network functions. In the present application, the other network functions that are combined and deployed with the first network function may be referred to as other network functions. Exemplarily, the one or more other network functions may include a second network function, or include a second network function and a third network function, or include a second network function, a third network function, ..., an Nth network function, where N is greater than or equal to 4.

[0096] This application may specifically include a registration process and a discovery process. Figure 2 The following is an example of a registration flow chart illustrating how to register a profile of a network function deployed in a merged manner with an NRF. For ease of description, the first network function deployed in a merged manner is used as an example.

[0097] Step 201: A first network function sends a first registration request to an NRF.

[0098] The first registration request includes an overview of the first network function, and the overview of the first network function includes a merge indication (which may be referred to as a first indication), wherein the first indication may be used to indicate the presence of one or more other network functions deployed in combination with the first network function. Exemplarily, when the first network function and the second network function are deployed in combination, the first indication may be used to indicate the presence of the second network function deployed in combination with the first network function. Further exemplarily, when the first network function, the second network function, and the third network function are deployed in combination, the first indication may be used to indicate the presence of the second network function and the third network function deployed in combination with the first network function.

[0099] Based on the different contents of the first instruction, it can be implemented in the following two ways.

[0100] In one implementation method, the first indication may include the instance identifiers (NF Instance ID) of one or more other network functions deployed in combination with the first network function. The one or more instance identifiers are used to indicate the existence of one or more other network functions deployed in combination with the first network function.

[0101] In implementation manner 1, the first indication may further include a network function type corresponding to an instance identifier of one or more other network functions deployed in combination with the first network function.

[0102] The explanation is that when the first network function registers with the NRF, only the instance identifier of the other network function deployed in conjunction with the first network function is carried in the first indication, and the instance identifier of the other network function does not indicate the corresponding network function type. After requesting an overview of the first network function, the requesting network function can only determine the existence of the other network function deployed in conjunction with the first network function, but cannot determine the network function type of the other network function. Therefore, the first indication can further carry the network function type corresponding to the instance identifier of the other network function.

[0103] Exemplarily, when a second network function is deployed in combination with a first network function, the first indication may include an instance identifier of the second network function and a network function type corresponding to the instance identifier of the second network function (which may be referred to as the second network function type), indicating that a network function corresponding to the second network function type and the instance identifier of the second network function exists and is deployed in combination with the first network function. Furthermore, when a third network function is deployed in combination with the first network function, the first indication may also include an instance identifier of the third network function and a network function type corresponding to the instance identifier of the third network function (which may be referred to as the third network function type), indicating that a network function corresponding to the third network function type and the instance identifier of the third network function exists and is deployed in combination with the first network function.

[0104] In a second implementation mode, the first indication may include a merge attribute, and the merge attribute may be used to indicate the existence of one or more other network functions deployed in combination with the first network function.

[0105] In this application, the merged attributes in the overviews of multiple network functions deployed in a merged manner are the same. For example, when a first network function and a second network function are deployed in a merged manner, the merged attributes in the overview of the first network function are the same as the merged attributes in the overview of the second network function. When the first network function, the second network function, and the third network function are deployed in a merged manner, the merged attributes in the overview of the first network function, the merged attributes in the overview of the second network function, and the merged attributes in the overview of the third network function are the same.

[0106] In other words, one merge attribute can be used to identify multiple network functions deployed in a merged manner. If the merge attributes in the overviews of two or more network functions are the same, it indicates that the two or more network functions are deployed in a merged manner.

[0107] For example, the merge attribute can be a globally unique string that can be used to represent multiple network functions deployed in a merged manner. For example, if SMF1 and BSF1 are deployed in a merged manner, the corresponding merge attribute can be smfbsf123456; if SMF2 and BSF2 are deployed in a merged manner, the corresponding merge attribute can be smfbsf345678.

[0108] Exemplarily, the merged attributes may be multiple dot-separated character strings, which may include but are not limited to network function names, deployment location information, data center information, etc. For example, if SMF1 and BSF1 are deployed together, the corresponding merged attribute may be smfbsf32.pudong.shanghai; or if SMF2 and BSF2 are deployed together, the corresponding merged attribute may be dc56.beijing.

[0109] It should be added that in the above-mentioned implementation method 1 and implementation method 2, the overview of the first network function may include not only the first indication, but also the network element information and service information of the first network function. Among them, the network element information of the first network function includes the instance identifier of the first network function, the network function type (which may be called the first network function type), the slice identifier, the network data name, the IP address, the priority, the capacity, the load and the location information of the service, etc. The service information of the first network function includes the service name, version information, the service instance identifier, the priority of the service, the capacity of the service and the load of the service, etc. The overview of the first network function is used to provide information when the client selects and accesses the first network function, such as the IP address when accessing the first network function.

[0110] Step 202: The NRF sends a first registration success response to the first network function.

[0111] Exemplarily, after storing the overview of the first network function, the NRF may send a first registration success response to the first network function, where the first registration success response is used to indicate that the overview of the first network function has been successfully registered.

[0112] It should be noted that, among one or more other network functions deployed in combination with the first network function, any other network function registers an overview of the network function with the NRF, such as the second network function registers an overview of the second network function with the NRF, or the third network function registers an overview of the third network function with the NRF, which can all be implemented by participating in the implementation method of the first network function registering the overview of the first network function with the NRF in the above embodiment, and will not be repeated here.

[0113] In the registration process described above, the network function may include a merge indication in the network function's overview and register the network function's overview with the NRF, where the merge indication indicates the network function to be deployed in combination with the network function. Furthermore, in the discovery process, the requesting network function may discover the first network function and / or the second network function from the NRF based on the merge indication in the network function's overview.

[0114] Furthermore, based on the different fields included in the first indication in the registration process, two cases are explained below.

[0115] like Figure 3 This application provides an exemplary flowchart of requesting a network function to discover a first network function and a second network function from an NRF when a first indication includes instance identifiers of one or more other network functions deployed in combination with the first network function.

[0116] exist Figure 3 In the process:

[0117] Step 301: Request the network function to send a first network function type to the NRF.

[0118] The first network function type is used to request the network function to request the NRF for an overview of the first network function corresponding to the first network function type. In an optional implementation, the requesting network function may also send a first parameter to the NRF, where the first parameter is a parameter other than the first network function type used to request an overview of the first network function. Exemplarily, the first parameter may include the location information of the terminal device, a slice identifier corresponding to a protocol data unit (PDU) session, a network data name, and the like.

[0119] In an optional implementation, the requesting network function sends a first discovery request to the NRF, where the first discovery request includes a first network function type and a first parameter, and the first discovery request is used to request the network function to request the NRF for an overview of the first network function. In addition, the requesting network function may also carry the first network function type and the first parameter in multiple different requests, respectively, and the multiple different requests are used to request the network function to request the NRF for an overview of the first network function.

[0120] In step 302, the NRF sends a summary of a first network function corresponding to a first network function type to the requesting network function, wherein the summary of the first network function includes a first indication including instance identifiers of one or more other network functions deployed in combination with the first network function.

[0121] In this application, the NRF registers overviews of multiple network functions, and the overview of each network function may include the instance identifier of the network function, the network function type, network element information, and service information. Furthermore, in the case where a certain network function is deployed in combination with other network functions, the overview of the network function may also include a merging indication corresponding to the network function. In this scenario, the merging indication corresponding to the network function may specifically include the instance identifier of the other network functions deployed in combination with the network function, or the instance identifier of the other network functions deployed in combination with the network function and the network function type corresponding to the instance identifier.

[0122] In an optional implementation, after receiving the first network function type sent by the requesting network function, the NRF may determine, based on the first network function type, from the overviews of multiple network functions, an overview of the network function corresponding to the first network function type, i.e., the overview of the first network function. It should be noted that the NRF may have multiple overviews of network functions, each of which has the first network function type.

[0123] In an optional implementation, the NRF may further receive a first parameter from the requesting network function, and based on the first network function type and the first parameter, determine, from the overviews of multiple network functions, an overview of the network function corresponding to both the first network function type and the first parameter, i.e., the overview of the first network function. Similarly, the NRF may have multiple overviews of network functions, whose network function type is the first network function type and supports the first parameter.

[0124] In an optional implementation, the NRF may receive a first discovery request from a requesting network function, where the first discovery request includes a first network function type and a first parameter, and the NRF determines an overview of the first network function corresponding to the first network function type and the first parameter. Alternatively, the NRF may receive multiple requests from the requesting network function, and obtain the first network function type and the first parameter from the multiple requests, and the NRF determines the overview of the first network function corresponding to the multiple requests.

[0125] In the present application, the NRF may determine an overview of one or more first network functions and send the overview of the one or more first network functions to the requesting network function. Furthermore, the NRF may carry the overview of the one or more first network functions in their respective corresponding messages and send them to the requesting network function, or combine them into one message and send it to the requesting network function. In an optional implementation, the NRF may carry the overview of the one or more first network functions in a first discovery response corresponding to the first discovery request, and send the first discovery response to the requesting network function.

[0126] Accordingly, after receiving the overviews of one or more first network functions from the NRF, the requesting network function can select an overview of the first network function and communicate with the first network function based on the overview of the first network function. In an optional implementation, the requesting network function determines whether to select an overview of a network function deployed in combination with other network functions from the overviews of the one or more first network functions based on pre-configuration information. For example, if the requesting network function is pre-configured to select a first network function deployed in combination, the requesting network function can select an overview of the first network function that includes a merging indication (i.e., a first indication) from the overviews of the one or more first network functions.

[0127] After selecting the first network function, the requesting network function may also need to select a second network function. In an optional implementation, the requesting network function obtains an overview of the second network function corresponding to the second network function type from the NRF based on the first indication in the overview of the first network function.

[0128] Based on different information included in the first indication in the overview of the first network function, there may be the following two situations:

[0129] In case A, the overview of the first network function includes instance identifiers of one or more other network functions deployed in combination with the first network function, but does not include network function types corresponding to the instance identifiers of the one or more other network functions.

[0130] In case A, the requesting network function may request an overview of the network function corresponding to the instance identifier of the network function from the NRF based on the instance identifiers of one or more other network functions deployed in combination with the first network function in the overview of the first network function. For details, see Figure 3 Steps 303A to 305A in FIG.

[0131] Step 303A: Request the network function to send one or more network function instance identifiers to the NRF.

[0132] It should be noted here that the requesting network function receives an overview of the first network function from the NRF, and the overview of the first network function includes the instance identifiers of one or more other network functions deployed in combination with the first network function, but the requesting network function is not sure what the network function types corresponding to the instance identifiers of the one or more other network functions are (for details, please refer to the description in the above step 201), so the requesting network function sends the instance identifiers of the one or more network functions (that is, the instance identifiers of the one or more other network functions in the first indication) to the NRF to request an overview corresponding to the instance identifiers of the one or more network functions.

[0133] In one example, the requesting network function may send a first data request to the NRF, where the first data request includes one or more instance identifiers of the network function, and the first data request is used to request the network function to request the NRF for an overview of the network functions corresponding to the one or more instance identifiers of the network function. In another example, the requesting network function may send multiple first data requests to the NRF, and for any first data request, the first data request may include the instance identifier of the network function corresponding to the first data request, and the first data request is used to request the network function to request the NRF for an overview of the network function corresponding to the instance identifier of the network function in the first data request.

[0134] Step 304A: The NRF sends an overview of the network functions corresponding to one or more instance identifiers of the network functions to the requesting network function.

[0135] The NRF may determine, based on the instance identifiers of one or more network functions (i.e., the instance identifiers of one or more other network functions in the first indication), the summary of the network function corresponding to each of the one or more network function instance identifiers, and then send the summary of the one or more network functions to the requesting network function. Exemplarily, the summary of the network function may also include a merge indication.

[0136] Exemplarily, when the first network function and the second network function are deployed in combination, the overview of the second network function may also include a merge indication (which may be referred to as a second indication), where the second indication may specifically include an instance identifier of the first network function, or include the instance identifier of the first network function and the first network function type.

[0137] Exemplarily, when the first network function, the second network function, and the third network function are deployed in a combined manner, the second indication in the overview of the second network function may specifically include the instance identifier of the first network function, the instance identifier of the third network function, or the instance identifier of the first network function and the first network function type, as well as the instance identifier of the third network function and the network function type corresponding to the instance identifier of the third network function (which may be referred to as the third network function type). The overview of the third network function may also include a combined indication (which may be referred to as the third indication), and the third indication may specifically include the instance identifier of the first network function and the instance identifier of the second network function, or the instance identifier of the first network function and the first network function type, the instance identifier of the second network function, and the network function type corresponding to the instance identifier of the second network function (which may be referred to as the second network function type).

[0138] In addition, the overview of the second network function may further include network element information, service information, etc. of the second network function. The overview of the third network function may further include network element information, service information, etc. of the third network function.

[0139] In one example, the NRF receives a first data request from a requesting network function, the first data request including one or more instance identifiers of the network functions, and the NRF sends a first data response corresponding to the first data request to the requesting network function, the first data response including an overview of the network functions corresponding to the instance identifiers of the one or more network functions. In another example, the NRF receives multiple first data requests from the requesting network function, any one of which may include an instance identifier of the network function corresponding to the first data request, and the NRF sends a first data response corresponding to the first data request to the requesting network function, the first data response including an overview of the network function corresponding to the instance identifier of the network function in the first data request.

[0140] Step 305A: The requesting network function determines a summary of a second network function corresponding to a second network function type from the summary of the network functions corresponding to the instance identifiers of the one or more network functions.

[0141] After receiving the overview of one or more network functions from the NRF, the requesting network function can determine the network function type of the one or more network functions deployed in combination with the first network function, and then the requesting network function can select an overview of the network function with a network function type of the second network function type (i.e., an overview of the second network function) from the overviews of the one or more network functions based on the second network function type.

[0142] Based on the example of steps 303A to 305A above, the first, second, and third network functions are deployed together, and the first, second, and third network functions correspond to profile 1, profile 2, and profile 3, respectively. The requesting network function can obtain profile 1 of the first network function from the NRF, where profile 1 includes instance identifier 2 of the second network function and instance identifier 3 of the third network function. For example, if the requesting network function needs to obtain a profile of the network function corresponding to network function type 2 (i.e., profile 2 of the second network function), the requesting network function can send instance identifier 2 and instance identifier 3 to the NRF. The NRF then sends profiles 2 and 3 corresponding to instance identifier 2 and instance identifier 3, respectively, to the requesting network function. Furthermore, profile 2 includes instance identifier 2 and network function type 2 of the second network function, and profile 3 includes instance identifier 3 and network function type 3 of the third network function. After receiving profiles 2 and 3 from the NRF, the requesting network function can determine that the network function type in profile 2 is network function type 2, and thus select profile 2.

[0143] In case B, the overview of the first network function includes instance identifiers of one or more other network functions, and network function types corresponding to the instance identifiers of the one or more other network functions.

[0144] In case B, the first network function may request an overview of the second network function corresponding to the second network function type from the NRF based on the instance identifiers of one or more other network functions and the network function types corresponding to the instance identifiers of one or more other network functions. For details, see Figure 3 Step 303B and step 304B in .

[0145] Step 303B: The requesting network function sends the instance identifier of the second network function and the second network function type to the NRF.

[0146] The first network function determines the instance identifier of the second network function corresponding to the second network function type based on the instance identifiers of one or more other network functions and the network function types corresponding to the instance identifiers of the one or more other network functions, and sends the instance identifier and the second network function type of the second network function to the NRF.

[0147] In an optional implementation, the first network function may send a second discovery request to the NRF, where the second discovery request includes an instance identifier of the second network function and a second network function type. The second discovery request is used to request the network function to request the NRF for an overview of the second network function corresponding to the instance identifier of the second network function.

[0148] It should be understood that in this step 303B, if the network function type that the requesting network function needs to request is not included in the network function types of one or more other network functions in the overview of the first network function, then the requesting network function may no longer perform an NRF query based on the instance identifier and network function type in the overview of the first network function. This helps to reduce unnecessary signaling interactions between the requesting network function and the network warehouse function.

[0149] In step 304B, the NRF sends an overview of the second network function to the first network function.

[0150] Exemplarily, the NRF may authenticate the requesting network function based on the type of the second network function, and after the authentication is passed, determine the overview of the second network function corresponding to the instance identifier of the second network function, and send the overview of the second network function to the requesting network function. For example, the NRF authorizes the requesting network function with the network function type of AMF to discover the second network function with the network function type of SMF, but does not allow the requesting network function of other network function types to discover the SMF. The NRF determines whether to allow the requesting network function to discover the second network function based on the network function type of the requesting network function and the type of the second network function.

[0151] In an optional implementation, the NRF may send a second discovery response corresponding to the second discovery request to the first network function, where the second discovery response includes an overview of the second network function corresponding to the instance identifier of the second network function in the second discovery request.

[0152] Based on the example of steps 303B and 304B above, the first network function, the second network function, and the third network function are deployed together, and the first network function, the second network function, and the third network function correspond to overview 1, overview 2, and overview 3, respectively. The requesting network function can obtain overview 1 of the first network function from the NRF, where overview 1 includes instance identifier 2 and network function type 2 of the second network function, and instance identifier 3 and network function type 3 of the third network function. For example, the requesting network function needs to obtain the overview of the network function corresponding to network function type 2 (i.e., overview 2 of the second network function). The requesting network function can send instance identifier 2 and network function type 2 to the NRF. Accordingly, the NRF sends overview 2 of network function type 2 corresponding to instance identifier 2 to the requesting network function.

[0153] In this way, the signaling interaction between the requesting network function and the NRF can be reduced, and the rate at which the requesting network function determines the second network function can be increased.

[0154] To better explain the embodiments of the present application, the following examples are given in conjunction with specific scenarios, where the first network function is SMF, the second network function is BSF, SMF and BSF are deployed together, and the requesting network function is AMF.

[0155] During a network element registration process:

[0156] SMF sends a registration request of SMF to NRF. The registration request of SMF includes an overview of SMF, and the overview of SMF includes the instance identifier of BSF (for example, NF Instance ID1). NF Instance ID1 can be used to indicate the existence of a network function deployed in combination with SMF. Furthermore, the overview of SMF also includes network element information of SMF, such as the instance identifier of SMF (for example, NF Instance ID2), the network function type of SMF (for example, SMF type), the location information of the service, the data network name list, the slice list information, etc. The overview of SMF also includes service information of SMF, such as service name, version information, service instance identifier, service priority, service capacity and service load, etc. Accordingly, NRF stores the overview of SMF and sends a registration success response to SMF.

[0157] The BSF sends a registration request of the BSF to the NRF. The registration request of the BSF includes an overview of the BSF. The overview of the BSF includes the instance identifier of the SMF (for example, NF Instance ID2). NF Instance ID2 can be used to indicate the existence of a network function deployed in conjunction with the BSF, and the identifier of the network function is NF Instance ID2. Furthermore, the overview of the BSF also includes the network element information of the BSF, such as the instance identifier of the BSF (for example, NF Instance ID1), the network function type of the BSF (for example, BSF type), the supported IP address list, the supported slice list, etc. The overview of the SMF also includes the service information of the SMF, such as the service name, version information, service instance identifier, service priority, service capacity, and service load, etc. Accordingly, the NRF stores the overview of the BSF and sends a registration success response to the BSF.

[0158] In a network element discovery process:

[0159] During the PDU session establishment process, AMF sends the SMF type (i.e., the first network function type) to NRF. The SMF type is used by AMF to request NRF for an overview of the SMF corresponding to the SMF type (i.e., an overview of the first network function corresponding to the first network function type). In addition, AMF can also send the first parameter for selecting SMF to NRF. The first parameter may include the current location information of the terminal device, the slice instance identifier corresponding to the PDU session, the network data name, etc. Based on the SMF type and the first parameter from AMF, NRF sends an overview of the SMF corresponding to the SMF type and the first parameter to AMF. AMF can establish a PDU session for the terminal device based on the overview of the SMF from NRF.

[0160] Subsequently, when the AMF still needs to select a BSF for maintaining the correspondence between the user IP address and the service network element function, and the pre-configured policy on the AMF requires the selection of a BSF merged with the SMF, the AMF can further send NF Instance ID1 to the NRF based on the overview of the SMF from the NRF. The NF Instance ID1 is used by the AMF to request the NRF for the overview corresponding to the NF Instance ID1. The NRF sends the overview corresponding to the NF Instance ID1 to the AMF. After receiving the overview of the BSF, the AMF determines that the SMF and the BSF are deployed in a merged manner based on the NF Instance ID1 and the network function type of the BSF in the overview of the BSF. The AMF selects the BSF to maintain the correspondence between the user IP address and the service network element function.

[0161] In addition, in another network registration process: the overview of the SMF may further include the network function type (i.e., BSF type) corresponding to the instance identifier of the BSF (i.e., NFInstance ID1). The overview of the BSF may further include the network function type (i.e., SMF type) corresponding to the instance identifier of the SMF (i.e., NFInstance ID2).

[0162] Accordingly, in another network element discovery process:

[0163] During the PDU session establishment process, AMF can send the SMF type to NRF. The SMF type is used by AMF to request NRF for an overview of the SMF corresponding to the SMF type. In addition, AMF can also send the first parameter for selecting SMF to NRF. NRF can send the overview of the SMF corresponding to the SMF type and the first parameter to AMF based on the SMF type and the first parameter from AMF. AMF can establish a PDU session for the terminal device based on the overview of the SMF from NRF.

[0164] Subsequently, when the AMF still needs to select a BSF for maintaining the correspondence between the user IP address and the service network element function, and the pre-configured policy on the AMF requires the selection of a BSF merged with the SMF, the AMF can further determine that the SMF and BSF are deployed in a merged manner based on the NFInstance ID1 and BSF type in the overview of the SMF, and send the NF Instance ID1 and BSF type to the NRF, so that the AMF can request the NRF for an overview of the BSF corresponding to the NF Instance ID1. The NRF sends the overview of the BSF corresponding to the NF InstanceID1 to the AMF. The AMF selects the BSF to maintain the correspondence between the user IP address and the service network element function.

[0165] It can be understood that if the network function type corresponding to the instance identifier (i.e., NF Instance ID1) included in the overview of the SMF does not include the BSF type, the AMF will not trigger a query of the NRF based on the instance identifier and the network function type, which helps to reduce unnecessary signaling interactions between the AMF and the NRF.

[0166] like Figure 4 This application provides an exemplary flow chart of requesting a network function to discover a first network function and a second network function from an NRF when a first indication includes a merge attribute. Figure 4 In the process:

[0167] Step 401: Request the network function to send a first network function type to the NRF.

[0168] The first network function type is used to request the network function to request the NRF for an overview of the first network function corresponding to the first network function type. In an optional implementation, the requesting network function may further send a first parameter to the NRF, where the first parameter is a parameter other than the first network function type used to request the first network function.

[0169] In an optional implementation, the requesting network function sends a first discovery request to the NRF, where the first discovery request includes a first network function type and a first parameter, and the first discovery request is used to request the network function to request the NRF for an overview of the first network function. In addition, the requesting network function may further carry the first network function type and the first parameter in multiple different requests, respectively, and the multiple different requests are used to request the network function to request the NRF for an overview of the first network function.

[0170] For implementations not described in detail in the above step 401, please refer to the description in step 301.

[0171] The NRF registers overviews of multiple network functions. Each overview of a network function may include network element information and service information for that network function. Furthermore, when a network function is deployed in conjunction with other network functions, the overview of that network function may also include a merge indication corresponding to that network function. In this scenario, the merge indication corresponding to the network function may specifically include the merge attributes corresponding to that network function. Network functions corresponding to overviews with the same merge attributes are deployed in conjunction.

[0172] After the NRF receives the first network function type from the requesting network function, the NRF sends a summary of the first network function corresponding to the first network function type to the requesting network function. This can be implemented in two ways:

[0173] In case 1, the NRF may send an overview of the first network function corresponding to the first network function type to the requesting network function, but may not send an overview of one or more other network functions to the requesting network function. Figure 4 Steps 402a to 405a in .

[0174] In step 402a, the NRF sends a summary of a first network function corresponding to the first network function type to the requesting network function, wherein the summary of the first network function includes a first indication, and the first indication includes a merge attribute.

[0175] The NRF sends an overview of the first network function corresponding to the first network function type to the requesting network function based on the first network function type, or based on the first network function type and the first parameter. The determination method can be specifically described in step 302 and will not be repeated here.

[0176] Step 403a: The requesting network function sends the second network function type and the merged attributes in the overview of the first network function to the NRF.

[0177] After receiving the overview of the first network function from the NRF, the requesting network function can send the second network function type and the merged attributes in the overview of the first network function to the NRF when it needs to select a second network function to be deployed in combination with the first network function. The second network function type and the merged attributes are used by the requesting network function to request the NRF to request an overview of the second network function corresponding to the second network function type that also includes the same merged attributes.

[0178] In an optional implementation, the requesting network function may send a third discovery request to the NRF, wherein the third discovery request includes the second network function type and the merged attribute. In addition, the requesting network function may also send the second network function type and the merged attribute to the NRF in two separate requests, which is not limited in this application.

[0179] Step 404a: The NRF sends a summary of the second network function corresponding to the second network function type and having the same merged attributes to the requesting network function.

[0180] In an optional implementation, the NRF may determine that the overviews of the currently registered network functions include overviews with the same merged attributes as those in the overview of the first network function, and further determine from these overviews an overview including a second network function type, i.e., an overview of the second network function. The NRF may also determine that the overviews of the currently registered network functions include overviews of the second network function type, and further determine from these overviews an overview including the same merged attributes as those in the overview of the first network function.

[0181] In an optional implementation, the NRF may send a third discovery response corresponding to the third discovery request to the first network function, wherein the third discovery response includes an overview of the second network function corresponding to the second network function type and having the same merged attributes as in the third discovery request.

[0182] Step 405a: The requesting network function determines to merge and deploy the first network function and the second network function according to the merge attribute in the overview of the first network function and the merge attribute in the overview of the second network function.

[0183] It should be noted that the NRF may determine the overview of one or more first network functions based on the first network function type of the requesting network function. The NRF may send the overview of the one or more first network functions to the requesting network function.

[0184] Accordingly, in one example, the requesting network function may request the NRF for overviews of the second network functions corresponding to each first network function based on the merged attributes in the overviews of each first network function. The requesting network function then determines, based on the merged attributes in the overviews of each first network function and the merged attributes in the overviews of the second network functions corresponding to each first network function, that the network functions corresponding to the overviews with the same merged attributes be deployed in a merged manner. The requesting network function determines overviews of the first network functions and the second network functions corresponding to each first network function for network communication from the overviews of the multiple first network functions and the overviews of the second network functions corresponding to each first network function.

[0185] In another example, the requesting network function may first determine an overview of a first network function from the overviews of multiple first network functions, and then request the NRF for an overview of a second network function corresponding to the first network function based on the merged attributes in the overview of the first network function.

[0186] Based on the example of steps 402a to 405a above, the first, second, and third network functions are deployed in a merged manner. The first, second, and third network functions correspond to Overview 1, Overview 2, and Overview 3, respectively. Overview 1, Overview 2, and Overview 3 all include the same merge attribute 1. After obtaining Overview 1 from the NRF, the requesting network function can obtain Merge Attribute 1 from Overview 1. Furthermore, for example, the requesting network function needs to obtain an overview of a network function corresponding to network function type 2 (i.e., Overview 2 of the second network function). The requesting network function can send Merge Attribute 1 and Network Function Type 2 to the NRF. Accordingly, the NRF can determine, based on Merge Attribute 1 and Network Function Type 2, that the overview also includes Merge Attribute 1 and Overview 2 corresponding to Network Function Type 2, and then send Overview 2 to the requesting network function. Upon receiving Overview 2 from the NRF, the requesting network function determines, based on Merge Attribute 1 in Overview 2 of the second network function and Merge Attribute 1 in Overview 1 of the first network function, that the second network function and the first network function are deployed in a merged manner.

[0187] In case 2, the network warehouse function may send an overview of the first network function corresponding to the first network function type to the requesting network function, and send an overview of one or more other network functions to the requesting network function. Figure 4 Steps 402b to 405b in .

[0188] Step 402b: The NRF sends a summary of the first network function corresponding to the first network function type and a summary of one or more other network functions corresponding to the first network function to the requesting network function.

[0189] The merged attributes in the overviews of one or more network functions corresponding to the first network function are the same as the merged attributes in the overview of the first network function. In a specific implementation, the NRF may determine, based on the merged attributes in the overview of the first network function, overviews of one or more other network functions that also include the merged attributes, and send the overview of the first network function and the overviews of the one or more other network functions to the requesting network function.

[0190] In one example, the NRF may send a first discovery response to the requesting network function, where the first discovery response includes an overview of the first network function and an overview of one or more other network functions. In another example, the overview of the first network function and the overview of the one or more other network functions are respectively carried in respective corresponding messages and sent to the requesting network function.

[0191] Step 403b: The requesting network function determines that the first network function and one or more other network functions are deployed in combination.

[0192] In a specific implementation, after the requesting network function receives the overview of the first network function and the overview of the one or more other network functions, it is determined that the merge attribute in the overview of the first network function is the same as the merge attribute in the overview of the one or more other network functions, and then it is determined that the first network function and the one or more other network functions are deployed in a merged manner.

[0193] Step 404b: The requesting network function determines an overview of a second network function corresponding to the second network function type from overviews of one or more other network functions.

[0194] It should be noted that in the above steps, the NRF may determine the overviews of multiple first network functions based on the first network function type of the requesting network function. In this case, the NRF may send an overview of the first network function and an overview of one or more other network functions corresponding to the first network function to the requesting network function for any one of the multiple first network functions. The requesting network function may determine the network functions corresponding to the overviews with the same merging attributes as merged deployments based on the merging attributes in the received overviews of each network function. The requesting network function then determines the overview of the first network function and the overview of the second network function used for network communication from the overviews of the multiple first network functions and the overviews of the one or more other network functions corresponding to each first network function.

[0195] Taking steps 402b to 404b as an example, in one network function merged deployment, a first network function and a second network function are merged. The first network function is represented as network function 0, corresponding to profile 0; the second network function is represented as network function 1, corresponding to profile 1. Both profiles 0 and 1 include the same merge attribute 1. In another network function merged deployment, the first network function and the second network function are merged. The first network function is represented as network function 2, corresponding to profile 2; the second network function is represented as network function 3, corresponding to profile 3. Both profiles 2 and 3 include the same merge attribute 2. The network function type of network function 0 is the same as that of network function 2, for example, network function type 0. The requesting network function sends network function type 0 to the NRF. Based on network function type 0, the NRF sends profile 0, profile 1, profile 2, and profile 3 to the requesting network function. Accordingly, the requesting network function can determine, based on merge attribute 1 in overview 0 and merge attribute 1 in overview 1, that network function 0 corresponding to overview 0 and network function 1 corresponding to overview 1 are deployed in a merged manner. The requesting network function can determine, based on merge attribute 2 in overview 2 and merge attribute 2 in overview 3, that network function 2 corresponding to overview 2 and network function 3 corresponding to overview 3 are deployed in a merged manner. The requesting network function can select network function 0 corresponding to overview 0 and network function 1 corresponding to overview 1, or it can select network function 2 corresponding to overview 2 and network function 3 corresponding to overview 3.

[0196] To better explain the embodiment of the present application, the following is an example of a specific scenario. The first network function is SMF, the second network function is BSF, SMF and BSF are deployed together, and the requesting network function is AMF. During the network element registration process:

[0197] SMF sends a registration request of SMF to NRF, and the registration request of SMF includes an overview of SMF. The overview of SMF includes the merge attribute a, which is used to indicate the existence of a network function deployed in combination with SMF. Furthermore, the overview of SMF also includes the network element information of SMF, such as the instance identifier of SMF (such as NF Instance ID2), the network function type of SMF (such as SMF type), the location information of the service, the data network name list, the slice list information, etc. The overview of SMF also includes the service information of SMF, such as the service name, version information, service instance identifier, service priority, service capacity and service load, etc. Accordingly, NRF stores the overview of SMF and sends a registration success response to SMF.

[0198] The BSF sends a registration request of the BSF to the NRF. The registration request of the BSF includes an overview of the BSF. The overview of the BSF includes the merge attribute a, which is used to indicate the existence of a network function deployed in combination with the BSF. Furthermore, the overview of the BSF also includes the network element information of the BSF, such as the instance identifier of the BSF (such as NF Instance ID1), the network function type of the BSF (such as the BSF type), the location information of the service, the data network name list, the slice list information, etc. The overview of the BSF also includes the service information of the BSF, such as the service name, version information, service instance identifier, service priority, service capacity and service load, etc. Accordingly, the NRF stores the overview of the BSF and sends a registration success response to the BSF.

[0199] In the above scheme, if SMF, BSF and new NF are subsequently deployed together, the new NF only needs to register the same merge attribute, i.e., merge attribute a, to NRF through the above method, without modifying the overview of SMF and BSF registered on NRF, which has better forward compatibility and scalability.

[0200] Accordingly, in a network element discovery process:

[0201] During the PDU session establishment process, AMF can send the SMF type (i.e., the first network function type) to NRF. The SMF type is used by AMF to request NRF for an overview of the SMF corresponding to the SMF type (i.e., an overview of the first network function corresponding to the first network function type). In addition, AMF can also send the first parameter for selecting SMF to NRF. The first parameter may include the current location information of the terminal device, the slice instance identifier corresponding to the PDU session, the network data name, etc. Based on the SMF type and the first parameter from AMF, NRF sends an overview of the SMF corresponding to the SMF type to AMF. AMF can establish a PDU session for the terminal device based on the overview of the SMF from NRF.

[0202] Subsequently, when the AMF still needs to select a BSF for maintaining the correspondence between the user IP address and the service network element function, and the pre-configured policy requires the selection of a BSF deployed in conjunction with the SMF, the AMF can send the merged attribute a and the BSF type to the NRF based on the overview of the SMF from the NRF. The merged attribute a and the BSF type are used by the AMF to request the NRF for an overview including the merged attribute a and corresponding to the BSF type. Correspondingly, the NRF sends the overview including the merged attribute a and corresponding to the BSF type, i.e., the overview of the BSF, to the AMF. The AMF determines that the SMF and the BSF are deployed in conjunction with each other based on the merged attribute a in the overview of the SMF and the merged attribute a in the overview of the BSF. The AMF selects the BSF to maintain the correspondence between the user IP address and the service network element function.

[0203] In addition, the NRF can not only send the overview of the SMF to the AMF, but also send the overview of the BSF with the same merge attribute a as the overview of the SMF to the AMF. Accordingly, the AMF can determine that the SMF and BSF are deployed in a merged manner based on the merge attribute a in the overview of the SMF and the merge attribute a in the overview of the BSF. The AMF and BSF in this merge deployment function are selected.

[0204] It should be pointed out that the requesting network function may also send a merged network function preference indication to the NRF, and the merged network function preference indication is used to instruct the NRF to give priority to selecting an overview of the network function with the merge indication for the requesting network function. Specifically, the network function preference indication may be used to indicate: when the overview of the network function includes a merge indication, the requesting network function receives an overview of the network function including the merge indication from the NRF; when the overview of the network function does not include a merge indication, the requesting network function receives an overview of the network function not including the merge indication from the NRF. Accordingly, the NRF may also receive a merged network function preference indication sent from the requesting network function, and the merged network function preference indication is used to instruct the NRF to give priority to selecting an overview of the network function with the merge indication for the requesting network function. Specifically, the network function preference indication may be used to indicate: when the overview of the network function includes a merge indication, an overview of the network function including the merge indication is sent to the requesting network function; when the overview of the network function does not include a merge indication, an overview of the network function not including the merge indication is sent to the requesting network function.

[0205] The explanation is that the requesting network function sends the first network function type and the merged network function preference indication to the NRF. The NRF first determines whether there is an overview of the network function corresponding to the first network function type and including the merge indication (i.e., the first indication) in the current network function overview. If so, the NRF can feedback the overview of the network function corresponding to the first network function type and including the merge indication to the requesting network function. In this example, if the NRF determines that there is only an overview of the network function corresponding to the first network function type and not including the merge indication, the NRF can feedback the overview of the network function corresponding to the first network function type and not including the merge indication to the requesting network function.

[0206] In addition, the requesting network function sends the second network function type, the merge indication, and the merged network function preference indication to the NRF. The NRF first determines whether there is an overview of the network function with the second network function type and the merge indication in the current network function overview. If so, the NRF can feedback the overview of the network function corresponding to the second network function type and the merge indication to the requesting network function. In this example, if the NRF determines that there is only an overview of the network function corresponding to the second network function type and not including the merge indication, the NRF can feedback the overview of the network function corresponding to the second network function type and not including the merge indication to the requesting network function.

[0207] In the present application, the requesting network function sends a merged network function preference indication to the NRF, which can be used to instruct the NRF to give priority to the overview of the network function that includes the merge indication, and helps to avoid the problem that when the overview of the network function does not include the merge indication, the NRF does not feedback the overview of the network function to the requesting network function, resulting in communication interruption of the terminal device, and helps to improve the success rate of the requesting network function to the overview of the network function.

[0208] In the above technical solution, the requesting network function requests the network warehouse function for an overview of the first network function having the first network function type, and the overview of the first network function includes a first indication, and the first indication is used to indicate that the first network function is deployed in combination with the second network function, so that the requesting network function can determine that the first network function is deployed in combination with other network functions. In this way, the requesting network function requests the network warehouse function for the network function deployed in combination with other network functions, which helps to realize the combined deployment of multiple network functions, helps to reduce deployment costs and complexity, and provides a more flexible network function deployment method. Moreover, the communication delay between the first network function and the second network function that are deployed in combination is short, which helps to optimize the service experience of the terminal device. The above technical solution can provide a general method for discovering combined deployed network functions, and any type of combined deployment of network functions in the 5G network can be discovered by the requesting network function through the above technical solution.

[0209] This application also provides another registration process, which is different from Figure 2 The first network function registers an overview of the first network function with the NRF. In this application, it can be an overview of the merged network function registering the merged network function with the NRF. For details, see Figure 5 An exemplary registration flow chart is shown.

[0210] Step 501: The merged network function sends a third registration request to the NRF.

[0211] The third registration request includes an overview of the merged network function, which may include the network function types of multiple network functions in the merged network function. The network function types of the multiple network functions are used to indicate that multiple network functions are deployed in a merged network function. For example, if the overview of the merged network function includes a first network function type and one or more other network function types, it indicates that the network functions corresponding to the first network function type and the one or more other network function types are deployed in a merged network function.

[0212] Step 502: The NRF sends a third registration success response to the merged network function. Exemplarily, after storing the overview of the merged network function, the NRF may send the third registration success response to the merged network function, where the third registration success response is used to indicate that the overview of the merged network function has been successfully registered.

[0213] In the present application, the network function types of multiple network functions in the overview of the merged network function can also be understood as a merge indication. The merge indication here is used to indicate that multiple network functions are deployed in the merged network function.

[0214] In the discovery process, the requesting network function may discover the first network function and the second network function from the NRF based on the network function types of the plurality of network functions in the summary of the merged network function.

[0215] Step 503: The requesting network function sends the first network function type and the second network function type to the NRF.

[0216] Among them, the first network function type and the second network function type are used to request the network function to request the NRF to request an overview of the merged network function corresponding to the first network function type and the second network function type, and the multiple network function types in the overview include the first network function type and the second network function type.

[0217] In this application, the requesting network function may also send a second parameter to the NRF, which is a parameter other than the first network function type and the second network function type for determining the overview of the merged network function. Exemplary second parameters include the location information of the terminal device, the network identifier of the service, the slice identifier corresponding to the PDU session, the network data name, etc.

[0218] In an optional implementation, the requesting network function sends a fourth discovery request to the NRF, where the fourth discovery request includes the first network function type, the second network function type, and the second parameter. The fourth discovery request is used to request the network function to request the NRF for an overview of the merged network function corresponding to the first network function type and the second network function type. In addition, the requesting network function may first send the first network function type and the second network function type to the NRF, and then send the second parameter to the NRF, or use other methods.

[0219] Step 504: The NRF sends a summary of the merged network function corresponding to the first network function type and the second network function type to the requesting network function.

[0220] In this application, the NRF can register not only the overview of a single network function, but also the overview of multiple merged network functions. The overview of each merged network function may include the network function type of the multiple network functions deployed in the merged network function, the network element information of the merged network function, and the service information corresponding to the multiple network functions.

[0221] In an optional implementation, the NRF may determine, based on the first network function type and the second network function type requested by the requesting network function, an overview of a merged network function that includes both the first network function type and the second network function type, and send the overview of the merged network function that includes both the first network function type and the second network function type to the requesting network function. In an optional implementation, the NRF may also receive a second parameter sent from the requesting network function, and determine, based on the first network function type, the second network function type, and the second parameter, an overview of the merged network function corresponding to the first network function type and the second network function type.

[0222] In an optional implementation, the NRF may receive a fourth discovery request from the requesting network function, and determine the overview of the corresponding merged network function based on the first network function type, the second network function type, and the second parameter in the fourth discovery request. Alternatively, the NRF may receive multiple requests from the requesting network function, and determine the overview of the corresponding merged network function based on the first network function type, the second network function type, and the second parameter obtained from the multiple requests.

[0223] In an optional implementation, the NRF may carry the summary of the determined merged network function in a fourth discovery response corresponding to the fourth discovery request, and send the fourth discovery response to the requesting network function.

[0224] In the present application, if the NRF fails to determine an overview of the merged network function that includes both the first network function type and the second network function type, the NRF may also send an overview of the first network function corresponding to the first network function type to the requesting network function, and send an overview of the second network function corresponding to the second network function type to the requesting network function.

[0225] The above example only takes the case of requesting the network function to send two function types (i.e., the first network function type and the second network function type) to the NRF as an example. The present application is also applicable to the scenario of requesting the network function to send multiple network function types to the NRF. For example, multiple merged network functions are deployed in the NRF, including merged network function 1 and merged network function 2. The overview of the merged network function 1 includes network function type a, network function type b, and network function type c corresponding to network function 11, network function 12, and network function 13, respectively. The overview of the merged network function 2 includes network function type a and network function type b corresponding to network function 21 and network function 22, respectively. For example, if the AMF sends network function type a, network function type b, and network function type c to the NRF, the NRF can send an overview of the merged network function 1 to the AMF. For example, if the AMF sends network function type a and network function type b to the NRF, the NRF can send an overview of the merged network function 1 and / or the merged network function 2 to the AMF.

[0226] To better explain the embodiment of the present application, the method in the present application is explained below in conjunction with a specific scenario. The first network function is NSSF, the second network function is NSSAAF, NSSF and NSSAAF are deployed together in the merged network function B, and the requesting network function is AMF.

[0227] During a network element registration process:

[0228] The merged network function B sends a registration request for the merged network function B to the NRF. The registration request for the merged network function B includes an overview of the merged network function B. The overview of the merged network function B includes the NSSF type and the NSSAAF type. The NSSF type and the NSSAAF type are used to indicate that the merged network function B has NSSF and NSSAAF deployed in combination. Furthermore, the overview of the merged network function B also includes the network element information of the merged network function B, the service information of the NSSF, and the service information of the NSSAAF. Exemplarily, the network element information of the merged network function B includes the instance identifier (such as NF Instance ID3) corresponding to the first network function and the second network function, service location information, a list of supported slices, a network identifier of the service, etc. The service information of the NSSF includes the service name, service version, IP address of the service, and instance identifier of the service supported by the NSSF. The service information of the NSSAAF includes the service name, service version, IP address of the service, and instance identifier of the service supported by the NSSAAF. Accordingly, the NRF stores the overview of the merged network function B and sends a registration success response to the merged network function B.

[0229] In a network element discovery process:

[0230] The AMF sends the NSSF type and NSSAAF type to the NRF, so that the AMF requests the NRF for an overview of the merged network function B corresponding to the NSSF type and NSSAAF type. In addition, the AMF may also send a second parameter for selecting the merged network function to the NRF. The second parameter may be the location information of the terminal device, a slice identifier, a network identifier, etc. The NRF sends an overview of the merged network function B to the AMF based on the NSSF type, NSSAAF type, and the second parameter from the AMF. The AMF may select the NSSF and NSSAAF based on the overview of the merged network function B from the NRF.

[0231] In the above technical solution, the requesting network function requests the network warehouse function for an overview of the merged network function having the first network function type and the second network function type. The overview is an overview of the merged deployment of the first network function corresponding to the first network function type and the second network function corresponding to the second network function type, thereby realizing the merged deployment of multiple network functions, and the requesting network function can request an overview of the merged network function, thereby helping to reduce deployment costs and complexity and provide a more flexible network function deployment method. Moreover, the communication delay between the merged deployed first network function and the second network function is short, which helps to optimize the service experience of the terminal device. The above technical solution can provide a general method for discovering merged deployed network functions. Any type of merged deployment of network functions in the 5G network can be discovered by the requested network function through the above technical solution.

[0232] Based on the above content and the same idea, Figure 6 and Figure 7 Schematic diagram of the structure of possible communication devices provided in this application. These communication devices can be used to implement the network warehouse function, request network function, first network function, or merge network function in the above method embodiments, thereby also achieving the beneficial effects of the above method embodiments.

[0233] like Figure 6 As shown, the communication device 600 includes a processing unit 601 and a transceiver unit 602 .

[0234] When the communication device 600 is used to implement Figures 2 to 4 The network warehouse function of the related method embodiment is as follows:

[0235] The processing unit 601 is configured to control the transceiver unit 602 to receive a first network function type from a requesting network function;

[0236] The processing unit 601 is used to control the transceiver unit 602 to send an overview of the first network function corresponding to the first network function type to the requesting network function, where the overview of the first network function includes a first indication, and the first indication is used to indicate that the first network function and the second network function are deployed together, and the network function types of the first network function and the second network function are different.

[0237] In a possible implementation manner, the first indication includes an instance identifier of the second network function.

[0238] In a possible implementation, the processing unit 601 is further configured to control the transceiver unit 602 to receive an instance identifier of a second network function from the requesting network function; and to send an overview of the second network function corresponding to the instance identifier of the second network function to the requesting network function.

[0239] In a possible implementation, the first indication further includes a second network function type of the second network function, and the processing unit 601 is further configured to control the transceiver unit 602 to receive the second network function type from the requesting network function.

[0240] In a possible implementation manner, the first indication includes a merge attribute.

[0241] In a possible implementation, the processing unit 601 is further configured to control the transceiver unit 602 to send an overview of the second network function to the requesting network function, where the overview of the second network function includes the merge attribute.

[0242] In a possible implementation, the processing unit 601 is further configured to control the transceiver unit 602 to receive the combined attribute of the requesting network function and the second network function type from the second network function.

[0243] In a possible implementation, the processing unit 601 is further configured to control the transceiver unit 602 to receive a first registration request from the first network function, where the first registration request includes an overview of the first network function; and to send a first registration success response to the first network function.

[0244] In one possible implementation, the processing unit 601 is further used to control the transceiver unit 602 to receive a merged network function preference indication from the requesting network function, where the merged network function preference indication is used to indicate: when the overview of the network function includes a merge indication, the transceiver unit 602 sends an overview of the network function including the merge indication to the requesting network function; when the overview of the network function does not include a merge indication, the transceiver unit 602 sends an overview of the network function that does not include the merge indication to the requesting network function.

[0245] When the communication device 600 is used to implement Figures 2 to 4 When requesting a network function in a related method embodiment:

[0246] The processing unit 601 is configured to control the transceiver unit 602 to send a first network function type to the network warehouse function;

[0247] The processing unit 601 is also used to control the transceiver unit 602 to receive an overview of the first network function corresponding to the first network function type from the network warehouse function, where the overview of the first network function includes a first indication, and the first indication is used to indicate that the first network function and the second network function are deployed together, and the network function types of the first network function and the second network function are different.

[0248] In a possible implementation manner, the first indication includes an instance identifier of the second network function.

[0249] In one possible implementation, the processing unit 601 is further configured to control the transceiver unit 602 to send an instance identifier of the second network function to the network warehouse function; and receive an overview of the second network function corresponding to the instance identifier of the second network function from the network warehouse function.

[0250] In one possible implementation, the first indication also includes a second network function type of the second network function, and the processing unit 601 is further used to determine the combined deployment of the first network function and the second network function based on the second network function type, and control the transceiver unit 602 to send the second network function type to the network warehouse function.

[0251] In a possible implementation manner, the first indication includes a merge attribute.

[0252] In a possible implementation, the processing unit 601 is further configured to control the transceiver unit 602 to receive an overview of the second network function from the network warehouse function, where the overview of the second network function includes a merge attribute.

[0253] In a possible implementation, the processing unit 601 is further configured to control the transceiver unit 602 to send the merged attribute and the second network function type of the second network function to the network repository function.

[0254] In a possible implementation, the processing unit 601 is further configured to determine the merged deployment of the first network function and the second network function according to the merge attribute in the overview of the second network function and the merge attribute in the overview of the first network function.

[0255] In one possible implementation, the processing unit 601 is also used to control the transceiver unit 602 to send a merged network function preference indication to the network warehouse function, and the merged network function preference indication is used to indicate: when the overview of the network function includes a merge indication, the transceiver unit 602 receives an overview of the network function including the merge indication from the network warehouse function; when the overview of the network function does not include a merge indication, the transceiver unit 602 receives an overview of the network function including the merge indication from the network warehouse function.

[0256] When the communication device 600 is used to implement Figures 2 to 4 Related to the method embodiment is the function of the first network function:

[0257] The processing unit 601 is used to control the transceiver unit 602 to send a first registration request to the network warehouse function, where the first registration request includes an overview of the first network function, and the overview of the first network function includes a first indication, where the first indication is used to indicate that the first network function and the second network function are deployed together, and the network function types of the first network function and the second network function are different; and receive a first registration success response from the network warehouse function.

[0258] When the communication device 600 is used to implement Figure 5 The network warehouse function of the related method embodiment is as follows:

[0259] The processing unit 601 is used to control the transceiver unit 602 to receive a first network function type and a second network function type from the requesting network function; and send a merged network function overview to the requesting network function, where the merged network function overview is an overview of the merged deployment of the first network function corresponding to the first network function type and the second network function corresponding to the second network function type, and the first network function type and the second network function type are different.

[0260] In one possible implementation, the processing unit 601 is also used to control the transceiver unit 602 to receive a third registration request from the merged network function, the third registration request including a merged network function overview, the merged network function overview including a first network function type and a second network function type; and send a second registration success response to the merged network function.

[0261] In a possible implementation, the merged network function summary further includes an instance identifier corresponding to both the first network function and the second network function.

[0262] When the communication device 600 is used to implement Figure 5 When requesting a network function in a related method embodiment:

[0263] The processing unit 601 is used to control the transceiver unit 602 to send the first network function type and the second network function type to the network warehouse function; receive a merged network function overview from the network warehouse function, where the merged network function overview is an overview of the merged deployment of the first network function corresponding to the first network function type and the second network function corresponding to the second network function type, and the first network function type and the second network function type are different.

[0264] In a possible implementation, the merged network function summary further includes an instance identifier corresponding to both the first network function and the second network function.

[0265] When the communication device 600 is used to implement Figure 5 Related method embodiments incorporate network functionality when:

[0266] The processing unit 601 is used to control the transceiver unit 602 to send a third registration request to the network warehouse function, where the third registration request includes a merged network function overview, which is an overview of the merged deployment of the first network function corresponding to the first network function type and the second network function corresponding to the second network function type, where the first network function type and the second network function type are different; and receive a third registration success response from the network warehouse function.

[0267] like Figure 7 The device 700 provided in an embodiment of the present application is shown. Figure 7 The device shown can be Figure 6 A hardware circuit implementation of the device shown. The device can be applied to the flowchart shown above to perform the functions of the above method embodiment. For ease of explanation, Figure 7 Only the main components of the device are shown.

[0268] Figure 7The illustrated apparatus 700 includes a communication interface 710, a processor 720, and a memory 730, wherein the memory 730 is configured to store program instructions and / or data. The processor 720 may operate in conjunction with the memory 730. The processor 720 may execute program instructions stored in the memory 730. When the instructions or program stored in the memory 730 are executed, the processor 720 is configured to perform the operations performed by the processing unit 601 in the above-described embodiment, and the communication interface 710 is configured to perform the operations performed by the transceiver unit 602 in the above-described embodiment.

[0269] The memory 730 is coupled to the processor 720. In the embodiments of the present application, coupling refers to an indirect coupling or communication connection between devices, units, or modules, which can be electrical, mechanical, or other forms, and is used for information exchange between the devices, units, or modules. At least one of the memories 730 may be included in the processor 720.

[0270] In the embodiments of the present application, the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface. In the embodiments of the present application, when the communication interface is a transceiver, the transceiver may include an independent receiver or an independent transmitter; or a transceiver or communication interface that integrates transceiver functions.

[0271] The device 700 may further include a communication line 740. The communication interface 710, the processor 720, and the memory 730 may be interconnected via the communication line 740; the communication line 740 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus. The communication line 740 may be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, Figure 7 Only one thick line is used in the diagram, but this does not mean that there is only one bus or one type of bus.

[0272] Based on the above content and the same concept, the present application provides a communication device, including a processor and a communication interface, wherein the communication interface is used to receive signals from other communication devices outside the communication device and transmit them to the processor or send signals from the processor to other communication devices outside the communication device, and the processor is used to implement the above through logic circuits or execution code instructions. Figures 2 to 4 The network warehouse function, or the request network function, or the first network function in the related method embodiment; or for implementing the above Figure 5 The network warehouse function, or the request network function, or the function of merging network functions in the related method embodiments.

[0273] Based on the above content and the same concept, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program or instruction, and when the computer program or instruction is executed by a communication device, the above Figures 2 to 4 The network warehouse function, or the request network function, or the first network function in the related method embodiment; or for implementing the above Figure 5 The network warehouse function, or the request network function, or the function of merging network functions in the related method embodiments.

[0274] Based on the above content and the same concept, the present application provides a communication system, including the above Figures 2 to 4 The network warehouse function, the request network function and the first network function in the related method embodiment, or including the above Figure 5 Related method embodiments include a network warehouse function, a request network function, and a merge network function.

[0275] In the present 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 items or plural items. For example, at least one of a, b or c can be represented by: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple. "And / or" describes the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can be represented by: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. In the textual description of the present application, the character " / " generally indicates that the previous and next associated objects are in an "or" relationship; in the formula of the present application, the character " / " indicates that the previous and next associated objects are in a "division" relationship.

[0276] It is understood that the various numbers used in the embodiments of this application are merely for ease of description and are not intended to limit the scope of the embodiments of this application. The order of the sequence numbers of the above-mentioned processes does not necessarily imply a specific order of execution; the order of execution of the processes should be determined by their functions and inherent logic.

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

Claims

1. A communication method, characterized in that: include: The network repository function receives a first network function type from a requesting network function; The network warehouse function sends an overview of the first network function corresponding to the first network function type to the requesting network function, where the overview of the first network function includes a first indication, where the first indication is used to indicate that the first network function is deployed together with the second network function, and the network function types of the first network function and the second network function are different; the first indication includes an instance identifier of the second network function.

2. The method according to claim 1, wherein Also includes: The network warehouse function receives an instance identifier of a second network function from the requesting network function; The network repository function sends a summary of the second network function corresponding to the instance identifier of the second network function to the requesting network function.

3. The method according to claim 2, wherein The first indication further includes a second network function type of the second network function, and the method further includes: The network repository function receives the second network function type from the requesting network function.

4. The method according to claim 1, wherein The first indication includes a merge attribute.

5. The method according to claim 4, wherein Also includes: The network repository function sends a summary of the second network function to the requesting network function, wherein the summary of the second network function includes the merged attribute.

6. The method according to claim 5, wherein Also includes: The network repository function receives the merged attributes from the requesting network function and a second network function type of the second network function.

7. The method according to claim 1, wherein Also includes: The network warehouse function receives a first registration request from the first network function, where the first registration request includes an overview of the first network function; The network warehouse function sends a first registration success response to the first network function.

8. The method according to any one of claims 1 to 7, wherein: Also includes: The network repository function receives a merged network function preference indication from the requesting network function, where the merged network function preference indication is used to indicate that the profiles of network functions having the merged indication are preferably selected for the requesting network function.

9. A communication method, characterized in that: include: requesting the network function to send a first network function type to the network repository function; The requesting network function receives an overview of a first network function corresponding to the first network function type from the network warehouse function, where the overview of the first network function includes a first indication, where the first indication is used to indicate that the first network function is deployed together with a second network function, and that the network function types of the first network function and the second network function are different; the first indication includes an instance identifier of the second network function.

10. The method according to claim 9, wherein Also includes: The requesting network function sends an instance identifier of the second network function to the network warehouse function; The requesting network function receives, from the network repository function, a summary of a second network function corresponding to the instance identifier of the second network function.

11. The method according to claim 10, wherein The first indication further includes a second network function type of the second network function, and the method further includes: The requesting network function sends the second network function type to the network repository function.

12. The method according to claim 11, wherein The method further comprises: The requesting network function determines, according to the second network function type, that the first network function and the second network function are deployed together.

13. The method according to claim 9, wherein The first indication includes a merge attribute.

14. The method according to claim 13, wherein Also includes: The requesting network function receives a summary of the second network function from the network repository function, the summary of the second network function including the merged attribute.

15. The method according to claim 14, wherein Also includes: The requesting network function sends the merged attributes and a second network function type of the second network function to the network repository function.

16. The method according to claim 15, wherein Also includes: The requesting network function determines, based on a merging attribute in the overview of the second network function and a merging attribute in the overview of the first network function, a merging deployment of the first network function and the second network function.

17. The method according to any one of claims 9 to 16, characterized in that Also includes: The requesting network function sends a merged network function preference indication to the network repository function, where the merged network function preference indication is used to indicate that the overview of the network function with the merge indication is preferably selected for the requesting network function.

18. A communication method, characterized in that: include: requesting the network function to send a first network function type to the network repository function; The network warehouse function receives the first network function type from the requesting network function; The network warehouse function sends, to the requesting network function, a summary of a first network function corresponding to the first network function type; The requesting network function receives an overview of a first network function corresponding to the first network function type from the network repository function; wherein, The overview of the first network function includes a first indication, where the first indication is used to indicate that the first network function is deployed in combination with a second network function, and the first network function and the second network function have different network function types; The first indication includes an instance identifier of the second network function.

19. A communication device, characterized in that: include: a processing unit, configured to control the transceiver unit to receive a first network function type from a requesting network function; The processing unit is configured to control the transceiver unit to send an overview of a first network function corresponding to the first network function type to the requesting network function, where the overview of the first network function includes a first indication, where the first indication is used to indicate that the first network function is deployed together with a second network function, and that the network function types of the first network function and the second network function are different; and the first indication includes an instance identifier of the second network function.

20. The device according to claim 19, wherein The processing unit is further configured to control the transceiver unit to receive an instance identifier of a second network function from the requesting network function; and to send a summary of the second network function corresponding to the instance identifier of the second network function to the requesting network function.

21. The device according to claim 20, characterized in that The first indication further includes a second network function type of the second network function, and the processing unit is further configured to control the transceiver unit to receive the second network function type from the requesting network function.

22. The device according to claim 19, wherein The first indication includes a merge attribute.

23. The device according to claim 22, wherein The processing unit is further configured to control the transceiver unit to send a summary of the second network function to the requesting network function, where the summary of the second network function includes the merging attribute.

24. The device according to claim 23, wherein The processing unit is further configured to control the transceiver unit to receive the combined attribute and the second network function type of the second network function from the requesting network function.

25. The device according to claim 19, wherein The processing unit is further configured to control the transceiver unit to receive a first registration request from the first network function, where the first registration request includes an overview of the first network function; and to send a first registration success response to the first network function.

26. The device according to any one of claims 19 to 25, characterized in that The processing unit is further configured to control the transceiver unit to receive a combined network function preference indication from the requesting network function, where the combined network function preference indication is configured to indicate: In a case where the summary of the network function includes a merging indication, the transceiver unit sends the summary of the network function including the merging indication to the requesting network function; In a case where the summary of the network function does not include a merge indication, the transceiver unit sends the summary of the network function excluding the merge indication to the requesting network function.

27. A communication device, characterized in that: include: The processing unit is configured to control the transceiver unit to send the first network function type to the network warehouse function; The processing unit is also used to control the transceiver unit to receive an overview of the first network function corresponding to the first network function type from the network warehouse function, the overview of the first network function including a first indication, the first indication being used to indicate that the first network function is deployed together with the second network function, and the network function types of the first network function and the second network function are different; the first indication includes an instance identifier of the second network function.

28. The device according to claim 27, wherein The processing unit is further configured to control the transceiver unit to send an instance identifier of a second network function to the network warehouse function; and receive an overview of the second network function corresponding to the instance identifier of the second network function from the network warehouse function.

29. The device according to claim 28, wherein The first indication further includes a second network function type of the second network function, and the processing unit is further configured to control the transceiver unit to send the second network function type to the network warehouse function.

30. The device according to claim 29, wherein The processing unit is further configured to determine, based on the second network function type, that the first network function and the second network function are to be deployed together.

31. The device according to claim 27, wherein The first indication includes a merge attribute.

32. The device according to claim 31, wherein The processing unit is further configured to control the transceiver unit to receive an overview of the second network function from the network warehouse function, where the overview of the second network function includes the merge attribute.

33. The device according to claim 32, wherein The processing unit is further configured to control the transceiver unit to send the merged attribute and the second network function type of the second network function to the network warehouse function.

34. The device according to claim 33, wherein The processing unit is further configured to determine, based on a merging attribute in the overview of the second network function and a merging attribute in the overview of the first network function, to merge and deploy the first network function and the second network function.

35. The device according to any one of claims 27 to 34, characterized in that The processing unit is further configured to control the transceiver unit to send a merged network function preferred indication to the network warehouse function, where the merged network function preferred indication is configured to indicate: In a case where the summary of the network function includes a merging indication, the transceiver unit receives the summary of the network function including the merging indication from the network warehouse function; In a case where the summary of the network function does not include a merging instruction, the transceiver unit receives the summary of the network function that does not include the merging instruction from the network warehouse function.

36. A communication device, characterized in that The method comprises a processor and a communication interface, wherein the communication interface is used to receive signals from other communication devices outside the communication device and transmit them to the processor or send signals from the processor to other communication devices outside the communication device, and the processor is used to implement the method as described in any one of claims 1 to 8 or 9 to 17 through a logic circuit or executing code instructions.

37. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program or instruction. When the computer program or instruction is executed by the communication device, the method according to any one of claims 1 to 8 or 9 to 17 is implemented.

38. A computer program product, characterized in that The computer program product comprises a computer program or instructions, and when the computer program or instructions are executed by a communication device, the method according to any one of claims 1 to 8 or 9 to 17 is implemented.

39. A communication system, characterized in that: The communication device comprises the communication device of any one of claims 19 to 26, and the communication device of any one of claims 27 to 35.

Images