Communication method and communication apparatus

Abstract

A communication method and a communication apparatus are disclosed, relating to the field of communication technology. In this communication method, a network element management function network element can send information about the service network elements participating in the service (a service requested by a terminal) to an interface function network element based on the service type information sent by the interface function network element. Thus, compared to existing solutions, this can effectively reduce the number of network element selection and discovery processes, thereby improving the efficiency of network element discovery and selection, and consequently reducing the time required to complete the terminal-requested service.

Description

Technical Field

[0001] This application relates to the field of communication technology, and more specifically, to a communication method and a communication device. Background Technology

[0002] In existing network architectures, terminal-requested services often require multiple network element discovery and selection processes to complete. Taking a session service as an example, in the protocol data unit (PDU) session establishment process, the access and mobility management function (AMF) requests the network repository function (NRF) to discover the session management function (SMF) and performs SMF selection. The SMF selected by the AMF then requests the policy control function (PCF) from the NRF and performs PCF selection. The SMF selected by the AMF then requests the unified data management (UDM) from the NRF and performs UDM selection. The PDU session establishment process requires these three network element discovery and selection processes to support the completion of the terminal-requested session service.

[0003] However, the above approach may result in the processing time for terminal requests being significantly longer. Therefore, reducing the time required to complete terminal requests is a pressing technical problem that needs to be addressed. Summary of the Invention

[0004] This application provides a communication method and a communication device that can reduce the time required to complete a terminal request.

[0005] In a first aspect, a communication method is provided, comprising: receiving type information of a first service from an interface function network element, wherein the first service is a service requested by a terminal; and sending information of a service network element to the interface function network element, wherein the service network element is a network element participating in the first service.

[0006] The solution described in the first aspect can be executed by a device on the network element management function side. This device can be a network element management function network element, a module within that network element (such as a chip system), or a logical node, logical module, or software capable of implementing all or part of the network element management function's functions. For ease of description, the following description uses a network element management function network element as an example.

[0007] In the above scheme, the network element management function network element sends the information of the network elements participating in the first service to the interface function network element according to the type information of the first service. Compared with the existing scheme, this can effectively reduce the number of times the network element selection and discovery process is performed. For example, it is not necessary for each network element participating in the first service to perform the network element discovery and selection process, thereby improving the efficiency of network element discovery and selection, and thus reducing the time required to complete the service requested by the terminal.

[0008] In some implementations of the first aspect, the service network element includes one or more network elements of different network element types. This allows for the sending of one or more network elements of different network element types participating in the first network element to the interface function network element, thereby reducing the number of network element selection and discovery processes.

[0009] In some implementations of the first aspect, the method further includes: determining the network element for the first service based on the type information of the first service. This allows the network element management function to determine the network element participating in the first service.

[0010] In some implementations of the first aspect, determining the network element for the first service based on the type information of the first service includes: determining the type of network element participating in the first service based on the type information of the first service; and determining the network element for the service based on the type of network element. This allows network element management functions to select appropriate network elements for the first service.

[0011] In some implementations of the first aspect, determining the service network element based on the network element type includes: determining the service network element based on the network element type and the context information of the terminal.

[0012] When the network element management function selects network elements based on the terminal's context information, this can reduce the overhead of the network element management function during network element selection. For example, when the terminal's context information includes information about some network elements in the service network elements, the network element management function does not need to select those specific network elements, but instead selects network elements from the service network elements excluding those specific network elements. This approach can reduce the overhead of the network element management function.

[0013] In some implementations of the first aspect, the network element type includes a first network element type, the terminal's context information includes information about the first network element corresponding to the first network element type, and the service network element includes the first network element. This allows network element management function network elements to avoid performing a network element selection process for the first network element, thereby reducing the overhead of network element management function network elements.

[0014] In some implementations of the first aspect, the network element type includes a second network element type, and the terminal's context information does not include information about the network element corresponding to the second network element type. The method further includes: determining a second network element based on the second network element type, wherein the service network element includes the second network element. This allows the network element management function network element to perform a network element selection process for the second network element, thereby reducing the overhead of the network element management function network element.

[0015] In some implementations of the first aspect, the information of the service network element includes information of a third network element and first information. The first information is used to indicate the information of network elements other than the third network element in the service network element, and the third network element is the target to which the interface function network element sends the first information. In this way, the interface function network element can avoid parsing the first information.

[0016] In some implementations of the first aspect, before receiving the type information of the first service from the interface function network element, the method further includes: receiving information about the first network element from the interface function network element, wherein the service network element includes the first network element. This allows the network element management function network element to avoid performing a network element selection process for the first network element, thereby reducing the overhead of the network element management function network element.

[0017] In some implementations of the first aspect, the first network element is a network element that has already provided services to the terminal. This allows network element management functions to avoid the need for a network element selection process for the first network element, thereby reducing the overhead of the network element management functions.

[0018] In some implementations of the first aspect, the first network element includes an interface function network element. This allows the network element management function network element to avoid performing a network element selection process on the first network element, thereby reducing the overhead of the network element management function network element.

[0019] In some implementations of the first aspect, the method further includes: receiving service characteristic information of a first service from an interface function network element; determining a service network element based on the type information of the first service, including: determining the service network element based on the type information and the service characteristic information of the first service. This allows for the determination of appropriate service network elements.

[0020] Secondly, a communication method is provided, comprising: sending type information of a first service to a network element management function network element, wherein the first service is a service requested by a terminal; and receiving information from a service network element of the network element management function network element, wherein the service network element is a network element participating in the first service.

[0021] The solution described in the second aspect can be executed by a device on the interface function network element side. This device can be an interface function network element itself, a module within the interface function network element (such as a chip system), or a logic node, logic module, or software capable of implementing all or part of the interface function network element's functions. For ease of description, the following description uses an interface function network element as an example.

[0022] For a description of the beneficial effects of the second aspect, please refer to the description of the beneficial effects of the first aspect, which will not be repeated here.

[0023] In some implementations of the second aspect, the service network element includes one or more network elements of different types.

[0024] In some implementations of the second aspect, the information of the service network element includes information of the first network element and first information, wherein the first information is used to indicate information of network elements other than the first network element in the service network element; the method further includes: sending the first information to the first network element according to the information of the first network element.

[0025] In some implementations of the second aspect, the method further includes: sending information about a second network element to a network element management function network element, wherein the service network element includes the second network element.

[0026] In some implementations of the second aspect, the second network element is a network element that has already provided services to the terminal.

[0027] In some implementations of the second aspect, the second network element includes an interface function network element.

[0028] In some implementations of the second aspect, the method further includes: sending service characteristic information of the first service to the network element management function network element.

[0029] Thirdly, a communication device is provided, which can be a network element management function network element, or a device or module used to perform network element management function network element, etc.

[0030] One possible implementation is that the communication device may include modules or units corresponding to the methods / operations / steps / actions described in the first aspect, which may be hardware circuits, software, or a combination of hardware circuits and software.

[0031] For example, the communication device includes a transceiver unit and a processing unit.

[0032] Fourthly, a communication device is provided, which may be an interface function network element, or a device or module for performing the functions of an interface function network element.

[0033] One possible implementation is that the communication device may include modules or units corresponding to the methods / operations / steps / actions described in the second aspect, which may be hardware circuits, software, or a combination of hardware circuits and software.

[0034] For example, the communication device includes a transceiver unit and a processing unit.

[0035] Fifthly, a communication device is provided, including a processor configured to, by executing a computer program or instructions, or by logic circuitry, cause the communication device to perform the method described in the first aspect and any possible manner of the first aspect; or to cause the communication device to perform the method described in the second aspect and any possible manner of the second aspect.

[0036] In one possible implementation, the communication device also includes a memory for storing the computer program or instructions.

[0037] In one possible implementation, the communication device also includes a communication interface for inputting and / or outputting signals.

[0038] A sixth aspect provides a communication device including logic circuitry and an input / output interface for inputting and / or outputting signals, the logic circuitry being configured to perform the method described in the first aspect and any possible mode of the first aspect; or, the logic circuitry being configured to perform the method described in the second aspect and any possible mode of the second aspect.

[0039] In a seventh aspect, a computer-readable storage medium is provided, on which a computer program or instructions are stored, which, when executed on a computer, cause the method described in the first aspect and any possible manner of the first aspect to be performed; or cause the method described in the second aspect and any possible manner of the second aspect to be performed.

[0040] Eighthly, a computer program product is provided, comprising instructions that, when executed on a computer, cause the method described in the first aspect and any possible mode of the first aspect to be performed; or cause the method described in the second aspect and any possible mode of the second aspect to be performed.

[0041] A ninth aspect provides a chip or chip system comprising: one or more processors configured to execute computer programs or instructions in the memory, such that the chip or chip system implements the methods of the first aspect and any possible implementation thereof; or, such that the chip or chip system implements the methods of the second aspect and any possible implementation thereof.

[0042] In a tenth aspect, a chip is provided, which is installed in a communication device. The chip includes a processor and a communication interface. The processor reads and executes instructions through the communication interface, causing the communication device to perform the methods of the first aspect and any possible implementation thereof; or, causing the communication device to perform the methods of the second aspect and any possible implementation thereof.

[0043] Eleventhly, a communication system is provided, including an interface function network element and a network element management function network element. The network element management function network element is used to execute the method described in the first aspect, and the interface function network element is used to execute the method described in the second aspect.

[0044] For a description of the beneficial effects of any of the third to eleventh aspects, please refer to the description of the beneficial effects of the first and second aspects, which will not be repeated here. Attached Figure Description

[0045] Figure 1 This is a schematic diagram of a communication system to which embodiments of this application are applicable.

[0046] Figure 2 yes Figure 1 The diagram shows a communication system applied to a network architecture.

[0047] Figure 3 yes Figure 1 The diagram shows a communication system applied to another network architecture.

[0048] Figure 4 This is a schematic diagram of the interaction flow of a communication method according to an embodiment of this application.

[0049] Figure 5 This is a schematic diagram of the interaction flow of another communication method according to an embodiment of this application.

[0050] Figure 6 This is a schematic block diagram of a communication device according to an embodiment of this application.

[0051] Figure 7 This is a schematic block diagram of another communication device according to an embodiment of this application. Detailed Implementation

[0052] To facilitate understanding of the embodiments of this application, the following points will be explained first.

[0053] 1. Unless otherwise stated, "multiple" means two or more. "At least one" means "one or more".

[0054] 2. Unless otherwise specified or in case of logical conflict, the terms and / or descriptions in different embodiments of this application are consistent and can be referenced in each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0055] III. The various numerical designations used in this application are merely for descriptive convenience and are not intended to limit the scope of protection of this application. The magnitude of the serial numbers used in this application does not imply a sequential order of execution; the execution order of each process should be determined by its function and internal logic. For example, the terms "first," "second," "third," "fourth," and other various terminology (if present) in the specification, claims, and drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. Such data can be interchanged where appropriate so that the embodiments described herein can be implemented in a sequence other than that illustrated or described herein.

[0056] Furthermore, any embodiment or design described in this application as "exemplary" or "for example" should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner for ease of understanding.

[0057] IV. The terms “comprising” and “having” and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are expressly listed, but may include other steps or units that are not expressly listed or that are inherent to such process, method, product or device.

[0058] V. In this application, "for indicating" can be understood as "enabling", and "enabling" includes direct enabling and indirect enabling. When describing information for enabling A, it may include whether the information directly enables A or indirectly enables A, but it does not mean that the information necessarily carries A.

[0059] The information that enables the information is called the information to be enabled. In the specific implementation process, there are many ways to enable the information to be enabled, such as, but not limited to, directly enabling the information to be enabled, such as the information to be enabled itself or its index. It can also be indirectly enabled by enabling other information, where there is a relationship between the other information and the information to be enabled. It can also enable only a part of the information to be enabled, while the other parts are known or pre-agreed upon. For example, enabling specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing enabling overhead to some extent. Simultaneously, common parts of various pieces of information can be identified and enabled uniformly to reduce the enabling overhead caused by individually enabling the same information.

[0060] In addition, "instruction" can include direct instruction, indirect instruction, explicit instruction, and implicit instruction. When describing a certain instruction information to indicate A, it can be understood that the instruction information carries A, directly indicates A, or indirectly indicates A.

[0061] In this application, the information indicated by the instruction information is called the information to be instructed. In specific implementations, there are many ways to indicate the information to be instructed, such as, but not limited to, directly indicating the information to be instructed, such as the information to be instructed itself or its index. It can also indirectly indicate the information to be instructed by indicating other information, where there is a relationship between the other information and the information to be instructed. It can also indicate only a part of the information to be instructed, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing instruction overhead to some extent. Furthermore, the information to be instructed can be sent as a whole or divided into multiple sub-information pieces, and the sending period and / or timing of these sub-information pieces can be the same or different.

[0062] VI. In this application, "pre-configuration" may include pre-defined terms, such as protocol definitions. These "pre-defined terms" can be implemented by pre-storing corresponding codes, tables, or other means of indicating relevant information in the device (e.g., including various network elements). This application does not limit the specific implementation method.

[0063] VII. The term "storage" or "preservation" in this application can refer to storage in one or more memory devices. These memory devices can be separately configured or integrated into an encoder, decoder, processor, or communication device. Alternatively, some memory devices can be separately configured, while others can be integrated into a decoder, processor, or communication device. The type of memory can be any form of storage medium, and this is not limited.

[0064] 8. The “protocol” involved in this application may refer to standard protocols in the field of communications, such as fourth-generation (4G) network protocols, fifth-generation (5G) network protocols, 5.5G network protocols, and related protocols applied in future communication networks. This application does not limit the scope of the term.

[0065] 9. The arrows or boxes indicated by dashed lines in the schematic diagrams in the accompanying drawings of this application represent optional steps or optional modules.

[0066] 10. Unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can mean A or B. In this application, "and / or" is merely a description of the relationship between the related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. A and B can be singular or plural.

[0067] XI. In this application, "send" and "receive" indicate the direction of signal transmission. For example, "send information to XX" can be understood as the destination of the information being XX, which may include direct transmission via the air interface or indirect transmission by other units or modules via the air interface. "Receive information from YY" can be understood as the source of the information being YY, which may include direct reception from YY via the air interface or indirect reception from YY by other units or modules via the air interface. "Send" can also be understood as the "output" of the chip interface, and "receive" can also be understood as the "input" of the chip interface. In other words, sending and receiving can occur between devices, such as between network devices and terminal devices, or within a device, such as between components, modules, chips, software modules, or hardware modules within the device via a bus, wiring, or interface.

[0068] The following sections describe the communication system, communication method, and communication device.

[0069] Figure 1 This is a schematic diagram of a communication system to which embodiments of this application apply. For example... Figure 1As shown, the communication system includes: network element management function network element 110 and interface function network element 120.

[0070] Network element management element 110 is an entity that performs functions such as network function (NF) registration, NF discovery and selection, and NF management. Network element management element 110 may have different names in different communication networks. For example, it may be a discovery and selection function (DSF) network element (only as an example), or it may be a 5G-defined NRF or a function-enhanced NRF, etc., without limitation.

[0071] Different network elements can complete registration at the network element management function network element 110. That is, different network elements send corresponding registration messages to the network element management function network element 110. The registration message includes, but is not limited to: NF type, supported service type, service characteristic information, NF instance ID, fully qualified domain name (FQDN), NF Internet Protocol (IP) address, names of supported NF services, and public land mobile network (PLMN) identifier (ID).

[0072] The aforementioned service types include, but are not limited to, session services, location services, and sensing services. Session service characteristics include, but are not limited to: data network name (DNN), single-network slice selection assistance information (S-NSSAI), multi-access (MA) PDU session capability information, and capability information. Location service characteristics include, but are not limited to: absolute positioning, relative positioning, and sidelink positioning. Sensing service characteristics include, but are not limited to: speed sensing, distance sensing, and angle sensing.

[0073] Interface function network element 120 is an entity that performs signaling interaction functions between network elements. For example, interface function network element 120 can send information from a terminal to network element management function network element 110; or interface function network element 120 can send information from network element management function network element 110 to other network elements. Interface function network element 120 may have different names in different communication networks. For example, interface function network element 120 may be called AMF, or core network (CN) interface function network element (CN portal function, CPF) (for example only). CPF supports (radio, R) (access network, AN)-CN interface, N1 signaling routing, and N2 signaling routing.

[0074] To reduce the time required to complete a terminal request, the network element management function network element 110 and the interface function network element 120 can exchange information as follows:

[0075] Interface function network element 120 sends the type information of service 1 (or other terms) to network element management function network element 110.

[0076] Correspondingly, network element 110, which is a network element management function, receives the type information of service 1. Service 1 is the service requested by the terminal.

[0077] Network element management function network element 110 sends information about service network element 1 to interface function network element 120. Correspondingly, interface function network element 120 receives information about service network element 1.

[0078] The type information of Service 1 indicates the type of Service 1, such as whether it is a session service, a location service, or a sensing service. The information of Service Network Element 1 includes the identification information or address information of the network elements participating in Service 1. Different types of services correspond to different network elements. For example, network elements participating in session services include AMF, SMF, UDM, and PCF; network elements participating in location services include AMF, location management function (LMF), and UDM; and network elements participating in sensing services include AMF, UDM, and sensing control function (SCF) (used to perform control over sensing services).

[0079] In this embodiment, the network element management function network element 110 can store or retrieve the correspondence between network elements and services. In other words, the correspondence between network elements and services can be determined by the network element management function network element 110 based on the aforementioned registration message. See Table 1 for details. The content shown in Table 1 is for illustrative purposes only and is not intended as a final limitation.

[0080] Table 1

[0081] Types of business Network element types Session services AMF type, UDM type, SMF type, PCF type Location services AMF type, UDM type, LMF type Sensing business AMF type, UDM type, SCF type

[0082] As shown in Table 1:

[0083] The service type is session service, and the network element types participating in the session service include: AMF, PCF, UDM, and SMF. Correspondingly, the network elements participating in the session service include: AMF1 (a specific AMF), PCF1 (a specific PCF), UDM1 (a specific UDM), and SMF1 (a specific SMF).

[0084] The service type is location service, and the network element types participating in the location service include AMF, UDM, and LMF types. Accordingly, the network elements participating in the location service include: AMF1 (a specific AMF), UDM1 (a specific UDM), and LMF1 (a specific LMF).

[0085] The service type is a sensing service, and the network element types participating in the sensing service include AMF, UDM, and SCF types. Correspondingly, the network elements participating in the sensing service include: AMF1 (a specific AMF), UDM1 (a specific UDM), and SCF1 (a specific SCF).

[0086] Based on Table 1, the network element management function network element 110 can determine the types of services that each network element can participate in based on the registration messages of different network elements, thereby enabling the network element management function network element 110 to determine the information of the corresponding network element based on the type of service.

[0087] In summary, network element management function network element 110 sends information about network elements participating in service 1 to interface function network element 120 based on the type information of service 1. Compared to existing solutions, this effectively reduces the number of times network element selection and discovery processes are performed. For example, each network element participating in service 1 does not need to perform network element discovery and selection from the NRF separately, thereby improving the efficiency of network element discovery and selection, and thus reducing the time required to complete the service requested by the terminal.

[0088] One possible implementation is that service network element 1 includes one or more network elements of different network element types. Alternatively, service network element 1 includes all network elements participating in service 1, which may belong to the same network element type or to multiple different network element types, without limitation.

[0089] For example, when service 1 involves a network element type, service network element 1 includes one or more network elements of that network element type.

[0090] For example, when service 1 involves multiple network element types, service network element 1 includes one or more network elements of each of the multiple network element types.

[0091] In summary, when service network element 1 includes one or more network elements of different types, this can help reduce the number of times network element discovery and selection are performed, thereby improving the efficiency of network element discovery and selection, and thus reducing the time required to complete the service requested by the terminal.

[0092] One possible implementation is that service network element 1 is determined by network element management function network element 110 based on the type information of service 1. Alternatively, service network element 1 is determined by network element management function network element 110 based on the type information of service 1 and the association relationship between service network element 1 (the association relationship can be found in Table 1).

[0093] For example, the type information of service 1 indicates that the type of service 1 is a session service. The network element management function network element 110 determines that the network elements participating in the session service (i.e., service network element 1) include AMF1, PCF1, UDM1 and SMF1.

[0094] For example, the type information of service 1 indicates that the type of service 1 is a location service. The network element management function network element 110 determines that the network elements participating in the location service (i.e., service network element 1) include AMF1, UDM1 and LMF.

[0095] One possible implementation is that network element management function network element 110 determines service network element 1 based on the type information of service 1, including:

[0096] The network element types participating in Service 1 are determined based on the type information of Service 1;

[0097] The network element 1 is determined based on the network element type participating in service 1.

[0098] Taking service 1 as a session service as an example, network element management function network element 110 determines that the network element types participating in the session service include: AMF type, PCF type, SMF type, and UDM type. Further, network management function network element 110 determines that the AMF type capable of participating in service 1 is AMF1 (e.g., AMF1 has a low load), the SMF type capable of participating in service 1 is SMF1 (e.g., SMF1 has a low load), the PCF type capable of participating in service 1 is PCF1 (e.g., PCF1 has a low load), and the UDM type capable of participating in service 1 is UDM1 (e.g., UDM1 has a low load).

[0099] Taking service 1 as a location service as an example, network element management function network element 110 determines that the network element types participating in the location service include: AMF type, LMF type, and UDM type. Furthermore, network element management function 110 determines that the AMF type capable of participating in service 1 is AMF1 (e.g., AMF1 has a low load), the LMF type capable of participating in service 1 is LMF1 (e.g., LMF1 has a low load), and the UDM type capable of participating in service 1 is UDM1 (e.g., UDM1 has a low load).

[0100] One possible implementation is that the network element types participating in Service 1 include network element type 1 and network element type 2. The network element corresponding to network element type 1 already provides services to the terminal. The network element corresponding to network element type 2 does not provide services to the terminal.

[0101] For network element type 1, network element management function network element 110 may not need to select a network element. For example, network element management function network element 110 selects network element 1 (network element type is network element type 1) from network elements that have already provided services to the terminal, and service network element 1 includes network element 1.

[0102] For network element type 2, network element management function network element 110 selects network elements. For example, network element management function network element 110 selects network element 2 (network element type is network element type 2) from network elements that have never provided services to the terminal, and service network element 1 includes network element 2.

[0103] One possible implementation is that the network element management function network element 110 determines the service network element 1 based on the network element type participating in service 1, including:

[0104] Service network element 1 is determined based on the network element type participating in service 1 and the context information of the terminal.

[0105] Network element management function element 110 can determine whether to select network element type 1 and network element type 2 based on the terminal's context information. For example, if the terminal's context information includes information about network element 1 (AMF1 and UDM1), network element management function element 110 will not select network element type 1. Conversely, if the terminal's context information does not include information about network element type 2 (such as SMF type) corresponding to network element (such as SMF), network element management function element 110 will determine to select network element type 2. In summary, after network element management function element 110 determines the network element type participating in service 1, it can determine whether to select network element 1 and network element 2 based on the terminal's context information.

[0106] One possible implementation is that when the terminal's context information includes information about network element 1, but network element 1 does not meet the service characteristics of service 1, the network element management function network element 110 can also select network element type 1. That is, it can select network element 4 (a general term for network elements belonging to network element type 1) (the terminal's context information does not include information about network element 4). Network element 4 belongs to network element type 1 and can meet the service characteristics of service 1. In this way, it can support the determination of a suitable service network element.

[0107] When the network element management function network element 110 selects network elements based on the terminal's context information, this can reduce the overhead of the network element management function network element 110 in selecting network elements. For example, when the terminal's context information includes information about some network elements in service network element 1, the network element management function network element 110 does not need to select those network elements, which can reduce the overhead of the network element management function network element 110.

[0108] One possible implementation is that the terminal's context information includes information about the network element corresponding to network element type 1. The network element management function network element 110 determines the network element corresponding to network element type 1 from the terminal's context information, eliminating the need to select the network element (i.e., network element 1) corresponding to network element type 1. Here, service network element 1 includes network element 1, and the terminal's context information includes information about network element 1.

[0109] One possible implementation is that the terminal's context information does not include information about the network element corresponding to network element type 2. The network element management function network element 110 determines the network element corresponding to network element type 2. That is, the network element management function network element 110 determines network element 2 based on network element type 2, and service network element 1 includes network element 2. Here, the terminal's context information does not include information about network element 2.

[0110] One possible implementation is that the information of service network element 1 includes the information of network element 3 and information 1. Information 1 is used to indicate the information of network elements other than network element 3 in service network element 1. Network element 3 is the sending object when interface function network element 120 sends information 1.

[0111] For example, service network element 1 includes network element 1, network element 2 and network element 3, and information 1 includes information of network element 1 and information of network element 2.

[0112] One possible implementation is that information 1 is carried in a network element container, or in other words, information 1 is in the form of a network element container. Alternatively, the embodiments of this application do not limit the form of information 1.

[0113] In this embodiment, the interface function network element 120 can also send information about network element 1 to the network element management function network element 110. This allows the network element management function network element 110 to store the information about network element 1 in the terminal's context information.

[0114] One possible implementation is that network element 1 includes interface function network element 120. In this way, network element management function network element 110 can avoid performing a network element selection process for network element 1, thereby reducing the overhead of network element management function network element 110.

[0115] In this embodiment, the interface function network element 120 can also send service characteristic information of service 1 to the network element management function network element 110. The service characteristic information of service 1 can be used by the network element management function network element 110 to determine service network element 1. In this way, it can support the determination of a suitable service network element.

[0116] Taking service 1 as a session service as an example, the service characteristic information of service 1 includes DNN1 and S-NSSAI1. When the network element management function element 110 determines that the network element type participating in service 1 includes SMF type, the network element management function element 110 determines and selects SMF1 that supports DNN1 and S-NSSAI1 based on the service characteristic information of service 1. In this way, it can support the determination of the appropriate service network element.

[0117] Taking service 1 as a location-based service as an example, the service characteristic information of service 1 includes side-link location. When the network element management function network element 110 determines that the network element type participating in service 1 includes LMF type, the network element management function network element 110 determines and selects LMF1 that supports side-link location based on the service characteristic information of service 1. In this way, it can support the determination of the appropriate service network element.

[0118] Figure 1The communication system shown can be applied to the following systems or scenarios: Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, Open Radio Access Network (O-RAN), Universal Mobile Telecommunication System (UMTS), 5G systems or future communication systems, and non-terrestrial network (NTN) systems such as inter-satellite communication and satellite communication. Satellite communication systems include satellite base stations and terminal equipment. Satellite base stations provide communication services to terminal equipment. Satellite base stations can also communicate with terrestrial base stations. Furthermore, satellites can function as both base stations and terminal equipment. Satellites can refer to non-terrestrial base stations or non-terrestrial equipment such as drones, hot air balloons, low-Earth orbit (LEO) satellites, medium-Earth orbit (MEO) satellites, and high-Earth orbit (HEO) satellites.

[0119] Figure 1 The technical solution disclosed in the communication system is applicable to both homogeneous and heterogeneous network scenarios, and there are no restrictions on the transmission points. It can be a multi-point collaborative transmission between macro base stations, micro base stations, and macro base stations, and it is applicable to both FDD and TDD systems. Figure 1 The technical solution revealed by the communication system shown is applicable not only to low-frequency scenarios, but also to high-frequency scenarios, terahertz, optical communication, etc. Figure 1 The technical solution revealed by the communication system shown can also be applied to macro and micro scenarios composed of base stations of different forms in communication networks. For example, the base station can be a satellite, an air balloon station, a drone station, etc. Figure 1 The technical solution revealed by the communication system shown is also suitable for scenarios where both wide-coverage base stations and small-coverage base stations exist simultaneously. Figure 1 The technical solution revealed by the communication system can be applied to scenarios with high reliability requirements, such as ports, industrial manufacturing, transportation, and coal mines.

[0120] The following text is about Figure 1 The network architecture used in the communication system shown is described.

[0121] Figure 2 yes Figure 1 The diagram illustrates a communication system applied to a network architecture. (As shown...) Figure 2 As shown, the network architecture includes:

[0122] 1. AMF. The AMF is primarily responsible for the following functions: mobility management, access authentication / authorization, receiving relevant signaling from access network equipment (such as next generation (NG) 2 interface signaling), completing the user registration process, and forwarding SM signaling. Optionally, the AMF can also be used to transmit user policies between terminal equipment and PCF, and receive non-access stratum (NAS) signaling (mobility management (MM) signaling and session management (SM) signaling) from terminal equipment.

[0123] 2. SMF. SMF is mainly used for session management, IP address allocation and management of terminal devices, selection of manageable user plane functions, policy control and charging function interface endpoints, downlink data notification, and completion of processes related to PDU session establishment, release, and update.

[0124] 3. PCF. PCF is responsible for user policy management, including both mobility-related policies and PDU session-related policies, such as QoS policies.

[0125] 4. Unified Data Repository (UDR). The UDR mainly includes the following functions: 1) UDM stores or reads subscription data; 2) PCF stores or reads policy data; 3) Stores or reads exposed data.

[0126] The UDR and the NF accessing it share the same PLMN, meaning that the Nudr interface is an internal interface of the PLMN within the same network.

[0127] 5. UDM. UDM mainly includes the following functions: unified data management, support for authentication trust letter processing in 3GPP authentication and key negotiation mechanisms, user identity processing, access authorization, registration and mobility management, subscription management and SMS management, etc.

[0128] 6. Application Function (AF). AF includes the following functions: interacting with the 3GPP core network to provide services, including: interaction with NEF, policy architecture interaction, etc.

[0129] 7. User Plane Function (UPF). The UPF acts as the interface with the data network, performing functions such as user plane data forwarding, session / flow-based billing and statistics, and bandwidth limiting. This includes packet routing and forwarding, as well as QoS processing for user plane data.

[0130] 8. (R)AN. (R)AN can manage radio resources and provide access services for terminal devices.

[0131] 9. Data Network (DN). DN provides services from carriers, the Internet, or third-party services, including servers. The server side implements video source encoding, rendering, etc.

[0132] In the above description, the network element can be a network component in a hardware device, a software function running on dedicated hardware, or a virtualization function instantiated on a platform (e.g., a cloud platform). The network element can be divided into one or more services; furthermore, services that exist independently of network functions may also exist. Instances of the network element, instances of services included in the network element, or instances of services that exist independently of network functions can all be referred to as service instances.

[0133] Figure 2 In this context, Npcf, Nudr, Nudm, Naf, Namf, and Nsmf are the service interfaces provided by PCF, UDR, UDM, AF, AMF, and SMF, respectively, and are used to call the corresponding service operations.

[0134] Figure 3 yes Figure 1 The diagram illustrates a communication system applied to a different network architecture. (See attached diagram.) Figure 3 As shown, the network architecture includes:

[0135] 1. CPF. CPF supports (R)AN-CN interface, N1 signaling routing and N2 signaling routing.

[0136] 2. AMF. AMF is responsible for the following functions: mobility management and access authentication / authorization.

[0137] 3. SMF. See also... Figure 2 The relevant description in the document.

[0138] 4. PCF. See also... Figure 2 The relevant description in the document.

[0139] 5. UDR. See also Figure 2 The relevant description in the document.

[0140] 6. UDM. See also Figure 2 The relevant description in the document.

[0141] 7. AF. See also Figure 2 The relevant description in the document.

[0142] 8. UPF. See also Figure 2 The relevant description in the document.

[0143] 9. (R)AN. See also: Figure 2 The relevant description in the document.

[0144] 10. DN. See also Figure 2 The relevant description in the document.

[0145] Figure 3 In this context, Npcf, Nudr, Nudm, Naf, Namf, and Nsmf are the service interfaces provided by PCF, UDR, UDM, AF, AMF, and SMF, respectively, and are used to call the corresponding service operations.

[0146] Figure 2 and Figure 3 The names shown for each network element are merely names and do not limit the function of the network element itself. In 5G networks and other future networks, the above-mentioned network elements may also have other names, and this application embodiment does not specifically limit them.

[0147] Figure 2 and Figure 3 The network structure shown is for illustrative purposes only. Figure 2 and Figure 3 The network structure shown may also include other network elements not mentioned, such as authentication server function (AUSF) and network element function (NEF).

[0148] Furthermore, the term "network element" used in this document can also be referred to as a network function instance, NF, device, apparatus, or module, etc., and this application does not specifically limit its usage. Additionally, the above naming conventions are defined solely for the purpose of distinguishing different functions and should not constitute any limitation. This application does not preclude the possibility of using other naming conventions in 5G networks and other future networks. The interface names between the aforementioned network elements are merely examples; in specific implementations, the interface names may differ, and no specific limitations are imposed. Furthermore, the names of the messages (or signaling) transmitted between the aforementioned network elements are also merely examples and do not constitute any limitation on the function of the messages themselves.

[0149] The following text combines Figure 4 and Figure 5 The interaction between interface function network element 120 and network element management function network element 110 is further described. Among them, Figure 4 The method shown is applied to Figure 2 In the network architecture shown, Figure 5 The method shown is applied to Figure 3 The network architecture shown.

[0150] Figure 4 This is a schematic diagram of the interaction flow of a communication method according to an embodiment of this application. Taking DSF110 as the network element management function network element 110 and AMF120 as the interface function network element 120 as an example. Figure 4 As shown, the method includes:

[0151] S401. The terminal sends the type information of Service 1 to the AMF120. Correspondingly, the AMF120 receives the type information of Service 1.

[0152] For example, the terminal sends a Nonaccess Stratum (NAS) message to the AMF120. The NAS message includes the N1 SM container and the type information for Service 1. A description of the N1 SM container can be found in existing standards. The type information for Service 1 indicates that Service 1 is a session service.

[0153] In this embodiment, before S401, the terminal first accesses the network or registers with the network. During the terminal's network access process, the access network device selects AMF120 for the terminal, AMF120 selects UDM150 for the terminal, and AMF120 sends the identifiers of AMF120, UDM140, and the terminal to DSF110. DSF110 stores the terminal's context information, which includes the identifiers of AMF120 and UDM140.

[0154] S402, AMF120 sends the type information of Service 1 to DSF110. Correspondingly, DSF110 receives the type information of Service 1.

[0155] For example, AMF120 sends a discovery request message to DSF110, which includes the type information of service 1 and the identifier of the terminal.

[0156] S403 and DSF110 send information about service network element 1 to AMF120. Correspondingly, AMF120 receives information about service network element 1.

[0157] For example, DSF110 sends a discovery response message to AMF120, which includes information about service network element 1. Specifically, DSF110 determines the information of service network element 1 based on the type information of service 1; a detailed description can be found in [link to relevant documentation]. Figure 1 The description will not be repeated here.

[0158] The information for service network element 1 includes information from SMF130 and information 1. The information from SMF130 includes its address or identification information. Information 1 can be a container, thus AMF120 does not need to parse its contents. Information 1 includes information from UDM140, PCF150, and AMF120. UDM140, PCF150, and AMF120 are determined by DSF110 based on the type information of service 1.

[0159] After the DSF110 selects SMF130 and PCF150, it stores the identification information of SMF130 and PCF150 in the terminal's context information.

[0160] S404 and AMF120 send Information 1 and the terminal's identifier to SMF130. Correspondingly, SMF130 receives Information 1 and the terminal's identifier.

[0161] For example, AMF120 sends a CreateSMContext message to SMF130 based on the information from SMF130. The CreateSMContext message includes the N1 SM container, information 1, and the identifier of the terminal.

[0162] S405 and SMF130 obtain the contract information for Service 1 from UDM140.

[0163] For example, SMF130 interacts with UDM140 based on the information from UDM140 in Message 1, thereby obtaining the contract information for Service 1. The specific interaction process can be found in existing standards.

[0164] S406 and SMF130 obtain the policy information for Service 1 from PCF150.

[0165] For example, SMF130 interacts with PCF150 based on the information from PCF150 in Info1, thereby obtaining the policy information for Service 1. The specific interaction process can be found in existing standards.

[0166] After S406, other steps in the session establishment process are executed, such as SMF130 configuring UPF and SMF130 sending N2 SM info information to RAN via AMF120.

[0167] Figure 4 The content shown is only a part of the complete session service. For details, please refer to the description in the existing standards, which will not be repeated here.

[0168] pass Figure 4The method shown in this application embodiment can support reducing the number of times the network element discovery and selection process is performed, thereby improving the efficiency of network element discovery and selection, and thus reducing the time required to complete the service requested by the terminal.

[0169] Figure 5 This is a schematic diagram of the interaction flow of another communication method according to an embodiment of this application. Taking DSF110 as the network element management function network element 110 and CPF120 as the interface function network element 120 as an example. Figure 5 As shown, the method includes:

[0170] S501, the terminal sends the type information of service 1 to the CPF120. Correspondingly, the CPF120 receives the type information of service 1.

[0171] For example, the terminal sends a NAS message to the CPF120. The NAS message includes the N1 SM container and the type information for service 1. A description of the N1 SM container can be found in existing standards. The type information for service 1 indicates that service 1 is a session service.

[0172] In this embodiment, before S501, the terminal first accesses the network or registers with the network. During the process of the terminal accessing the network, the access network device selects CPF120 for the terminal, and DSF110 selects AMF1 and UDM140 for the terminal. DSF110 stores the terminal's context information, which includes the identifiers of AMF1 and UDM140.

[0173] S502, CPF120 sends the type information of Service 1 to DSF110. Correspondingly, DSF110 receives the type information of Service 1.

[0174] For example, CPF120 sends a discovery request message to DSF110, which includes the type information of service 1 and the identifier of the terminal.

[0175] S503 and DSF110 send information about service network element 1 to CPF120. Correspondingly, CPF120 receives information about service network element 1.

[0176] For example, DSF110 sends a discovery response message to CPF120, which includes information about service network element 1. Specifically, DSF110 determines the information of service network element 1 based on the type information of service 1; a detailed description can be found in [link to relevant documentation]. Figure 1 The description will not be repeated here.

[0177] In this embodiment, the information of service network element 1 includes information of SMF130 and information 1. The information of SMF130 includes the address information or identification information of SMF130. Information 1 can be a container, so CPF120 does not need to parse the content of information 1. Information 1 includes information of UDM140, PCF150, and AMF1. UDM140, PCF150, and AMF1 are determined by DSF110 based on the type information of service 1.

[0178] S504 and CPF120 send Information 1 and the terminal identifier to SMF130. Correspondingly, SMF130 receives Information 1 and the terminal identifier.

[0179] For example, CPF120 sends a CreatSMContext message to SMF130 based on the information from SMF130. The CreatSMContext message includes the N1 SM container, information 1, and the identifier of the terminal.

[0180] S505 and SMF130 obtain the contract information for Service 1 from UDM140.

[0181] For example, SMF130 interacts with UDM140 based on the information from UDM140 in Message 1, thereby obtaining the contract information for Service 1. The specific interaction process can be found in existing standards.

[0182] S506 and SMF130 obtain the policy information for Service 1 from PCF150.

[0183] For example, SMF130 interacts with PCF150 based on the information from PCF150 in Info1, thereby obtaining the policy information for Service 1. The specific interaction process can be found in existing standards.

[0184] After S506, other steps in the session establishment process are executed, such as configuring UPF on SMF130 and sending N2 SM info information to the access network device through AMF1.

[0185] Figure 5 The content shown is only a part of the complete session service. For details, please refer to the description in the existing standards, which will not be repeated here.

[0186] pass Figure 5 The method shown in this application embodiment can support reducing the number of times the network element discovery and selection process is performed, thereby improving the efficiency of network element discovery and selection, and thus reducing the time required to complete the service requested by the terminal.

[0187] Finally, the device embodiments of this application will be described.

[0188] To implement the functions in the method provided in this application, both the network element management function network element 110 and the interface function network element 120 may include hardware structures and / or software modules, implementing the above functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular function is implemented in the form of hardware structures, software modules, or a combination of hardware structures and software modules depends on the specific application and design constraints of the technical solution.

[0189] Figure 6 This is a schematic block diagram of a communication device according to an embodiment of this application. The communication device includes a processing circuit 610 and a transceiver circuit 620, which can be interconnected or coupled, for example, interconnected via a bus 630. The communication device can be an interface function network element 120 or a network element management function network element 110.

[0190] Optionally, the communication device may also include a memory 640. The memory 640 includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM), which is used for related instructions and data.

[0191] The processing circuit 610 may be all or part of the processing circuitry in one or more processors, or it may be one or more processors. The processor may be a central processing unit (CPU). If the processing circuit 610 is a CPU, the CPU may be a single-core CPU or a multi-core CPU. The processing circuit 610 may be a signal processor, a chip, or other integrated circuit capable of implementing the methods of this application, or a portion of the circuitry within the aforementioned processor, chip, or integrated circuit that performs processing functions. Additionally, the transceiver circuit 620 may be a transceiver, or an input / output interface. An input / output interface is used for inputting or outputting signals or data and may also be referred to as an input / output circuit.

[0192] When the communication device is interface function network element 120, for example, the processing circuit 610 is used to perform the following operations: send service 1 type information to network element management function network element 110; receive service network element 1 information from network element management function network element 110, etc.

[0193] When the communication device is a network element management function network element 110, for example, the processing circuit 610 is used to perform the following operations: receive service 1 type information from interface function network element 120; send service network element 1 information to interface function network element 120, etc.

[0194] The above description is for illustrative purposes only.

[0195] When the communication device is an interface function network element 120 or a network element management function network element 110, it will be responsible for executing the methods or steps related to the interface function network element 120 or the network element management function network element 110 in the aforementioned method embodiments.

[0196] When the communication device is an interface function network element 120 or a network element management function network element 110, the transceiver circuit 620 can be a transceiver.

[0197] When the communication device is a chip used for interface function network element 120 or network element management function network element 110, the transceiver circuit 620 can be an input / output circuit.

[0198] The above description is merely exemplary. For details, please refer to the content shown in the above method embodiments.

[0199] Figure 6 The implementation of each operation can also be found by referring to... Figures 1 to 5 The corresponding description of the method embodiments shown.

[0200] Figure 7 This is a schematic block diagram of another communication device according to an embodiment of this application. The communication device can be an interface function network element 120 or a network element management function network element 110, used to implement the methods involved in the above embodiments.

[0201] The communication device includes a transceiver unit 710 and a processing unit 720. The transceiver unit 710 and the processing unit 720 will be described exemplarily below.

[0202] The transceiver unit 710 may include a transmitting unit and a receiving unit. The transmitting unit is used to perform the transmitting action of the communication device, and the receiving unit is used to perform the receiving action of the communication device. For ease of description, the transmitting unit and the receiving unit are combined into one transceiver unit in this embodiment. This will be explained uniformly here and will not be repeated later.

[0203] When the communication device is an interface function network element 120, exemplarily, the transceiver unit 710 is used to send service 1 type information to the network element management function network element 110; and to receive service network element 1 information from the network element management function network element 110. The processing unit 720 is used to determine the service 1 type information, etc.

[0204] When the communication device is a network element management function network element 110, for example, the transceiver unit 710 is used to receive the type information of service 1 from the interface function network element 120; send the information of service network element 1 to the interface function network element 120; and the processing unit 720 is used to determine the information of service network element 1, etc.

[0205] When the communication device is an interface function network element 120 or a network element management function network element 110, it will be responsible for executing one or more of the methods or steps related to the interface function network element 120 or the network element management function network element 110 in the aforementioned method embodiments.

[0206] Optionally, the communication device further includes a storage unit 730 for storing programs or code for executing the aforementioned methods.

[0207] Figure 7 The transceiver unit in the middle can correspond to Figure 6 The transceiver circuit in the middle, Figure 7 The processing unit in can correspond to Figure 6 The processing circuitry within.

[0208] Figure 6 and Figure 7 The illustrated device embodiment is used to implement Figures 1 to 5 The content described. Figure 6 and Figure 7 The specific execution steps and methods of the device shown can be found in the content described in the foregoing method embodiments.

[0209] This application also provides a chip, including a processor, for calling and executing instructions stored in a memory, causing a communication device on which the chip is installed to perform the methods described in the examples above. The memory may be integrated within the chip or located externally.

[0210] This application also provides another chip, including: an input interface, an output interface, and a processing circuit, wherein the input interface, the output interface, and the processor are connected through an internal connection path, and the processing circuit is used to execute code in memory. When the code is executed, the processing circuit is used to execute the methods in the above examples.

[0211] Optionally, the chip also includes a memory for storing computer programs or code. The input and output interfaces can be independent of each other, or they can be integrated into a single input / output interface.

[0212] The processing circuitry can be all or part of the processing circuitry in one or more processors, or one or more processors.

[0213] This application also provides a processor for coupling with a memory for performing the methods and functions of a network device or terminal device involved in any of the above embodiments.

[0214] In another embodiment of this application, a computer program product containing instructions is provided, which, when run on a computer, enables the implementation of the methods described in the foregoing embodiments.

[0215] This application also provides a computer program that, when run on a computer, enables the implementation of the methods described in the foregoing embodiments.

[0216] In another embodiment of this application, a computer-readable storage medium is provided, which stores a computer program that, when executed by a computer, implements the methods described in the foregoing embodiments.

[0217] It should be understood that in the embodiments of this application, the processor can be a central processing unit (CPU), but it can also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor.

[0218] It should also be understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of random access memory (RAM) are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced synchronous SDRAM (ESDRAM), synchronous linked DRAM (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0219] The above embodiments can be implemented, in whole or in part, by software, hardware, firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more sets of available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. A semiconductor medium can be a solid-state drive.

[0220] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0221] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative; for example, the division of units is merely a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection of devices or units may be electrical, mechanical, or other forms.

[0222] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. If the above functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory, random access memory, magnetic disks, or optical disks.

[0223] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

Claims

1. A communication method, characterized in that, Network elements used for network element management functions include: Receive type information of the first service from the interface function network element, wherein the first service is a service requested by the terminal. Send information about the service network element to the interface function network element, wherein the service network element is the network element participating in the first service.

2. The method according to claim 1, characterized in that, The service network element includes one or more network elements of different types.

3. The method according to claim 1 or 2, characterized in that, The method further includes: The service network element is determined based on the type information of the first service.

4. The method according to claim 3, characterized in that, Determining the service network element based on the type information of the first service includes: The network element type participating in the first service is determined based on the type information of the first service; The service network element is determined based on the network element type.

5. The method according to claim 4, characterized in that, Determining the service network element based on the network element type includes: The service network element is determined based on the network element type and the context information of the terminal.

6. The method according to claim 5, characterized in that, The network element type includes a first network element type, the terminal's context information includes information about the first network element corresponding to the first network element type, and the service network element includes the first network element.

7. The method according to claim 5, characterized in that, The network element type includes a second network element type, and the context information of the terminal does not include information about the network element corresponding to the second network element type. The method further includes: The second network element is determined according to the second network element type, and the service network element includes the second network element.

8. The method according to any one of claims 1 to 7, characterized in that, The information of the service network element includes information of the third network element and first information. The first information is used to indicate the information of network elements other than the third network element in the service network element. The third network element is the sending target when the interface function network element sends the first information.

9. The method according to any one of claims 1 to 8, characterized in that, Before receiving the type information of the first service from the interface function network element, the method further includes: The system receives information from a first network element of the interface function network element, wherein the service network element includes the first network element.

10. The method according to any one of claims 6 to 9, characterized in that, The first network element is a network element that has already provided services to the terminal.

11. The method according to any one of claims 7 to 10, characterized in that, The second network element is a network element that does not provide services to the terminal.

12. The method according to any one of claims 6 to 11, characterized in that, The first network element includes the interface function network element.

13. The method according to any one of claims 3 to 12, characterized in that, The method further includes: Receive service characteristic information of the first service from the interface function network element; Determining the service network element based on the type information of the first service includes: The service network element is determined based on the type information and service characteristic information of the first service.

14. A communication method, characterized in that, Applied to interface function network elements, including: Send the type information of the first service to the network element management function network element, wherein the first service is the service requested by the terminal. The system receives information from the service network element of the network element management function, wherein the service network element is a network element participating in the first service.

15. The method according to claim 14, characterized in that, The service network element includes one or more network elements of different types.

16. The method according to claim 14 or 15, characterized in that, The information of the service network element includes information of the first network element and first information, wherein the first information is used to indicate the information of network elements other than the first network element in the service network element; The method further includes: Based on the information of the first network element, the first information is sent to the first network element.

17. The method according to any one of claims 14 to 16, characterized in that, The method further includes: The information of the second network element is sent to the network element management function network element, and the service network element includes the second network element.

18. The method according to claim 17, characterized in that, The second network element is a network element that has already provided services to the terminal.

19. The method according to claim 17 or 18, characterized in that, The second network element includes the interface function network element.

20. The method according to any one of claims 14 to 19, characterized in that, The method further includes: Send the service characteristic information of the first service to the network element management function network element.

21. A communication device, characterized in that, Includes a processor, the processor being configured to cause the communication device to perform the method of any one of claims 1 to 20 by executing a computer program or instructions, or by using logic circuitry.

22. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions that, when executed on a computer, cause the method of any one of claims 1 to 20 to be performed.

23. A computer program product, characterized in that, It includes instructions that, when executed on a computer, cause the method of any one of claims 1 to 20 to be performed.

24. A communication system, characterized in that, include: A network element management function is used to execute the method according to any one of claims 1 to 13; An interface function network element is used to perform the method according to any one of claims 14 to 20.

Images