Communication method and core network element
By selecting target core network elements that support multiple desired capabilities, the signaling waste and complexity problems caused by the diversity of network element capabilities in the core network element discovery process are solved, and the discovery success rate and system efficiency are improved.
Patent Information
- Application Number
- PCT/CN2023/093606
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-11
- Publication Date
- 2024-11-14
AI Technical Summary
The existing core network element discovery process fails to effectively handle the situation where network elements support multiple capabilities, resulting in discovery failure or signaling waste and increased complexity.
By selecting network elements that support multiple desired capabilities at the same time as the target core network elements, the number of network elements selection is reduced, signaling interaction and complexity is reduced, and the discovery success rate is improved.
It effectively avoids network element discovery failure, reduces signaling waste and operation complexity, and improves system efficiency.
Smart Images

Figure CN2023093606_14112024_PF_FP_ABST
Abstract
Description
Method for communication and core network element Technical Field
[0001] The present application relates to the field of communication technology, and more specifically, to a method for communication and a core network element. Background Art
[0002] With the continuous development of communication technology, core network elements support more and more services, that is, core network elements have more and more capabilities. Related technologies have not yet considered the situation where an element supports multiple capabilities during the core network element discovery process, which may lead to many problems.
[0003] Summary of the Invention
[0004] The present application provides a method for communication and a core network element. The following introduces various aspects involved in the present application.
[0005] In a first aspect, a method for communication is provided, the method comprising: based on at least two of a plurality of expected capabilities, a first core network element selects one or more target core network elements from the network elements to be discovered; wherein the expected capabilities are capabilities that the second core network element expects to subscribe to, and the target core network element supports some or all of the plurality of expected capabilities.
[0006] In a second aspect, a method for communication is provided, comprising: a second core network element sending a first request to a first core network element; wherein the first request is used to indicate a plurality of desired capabilities, and the desired capabilities are capabilities that the second core network element desires to subscribe to.
[0007] According to a third aspect, a method for communication is provided, comprising: determining, by a first core network element, a discovery priority of a third core network element based on first information; wherein the first information is used to indicate capabilities supported by the third core network element.
[0008] In a fourth aspect, a core network network element is provided, which is a first core network network element. The core network network element includes: a selection unit, used to select one or more target core network network elements from the network elements to be discovered based on at least two of a plurality of expected capabilities; wherein the expected capabilities are capabilities that the second core network network element expects to subscribe to, and the target core network element supports some or all of the plurality of expected capabilities.
[0009] In the fifth aspect, a core network network element is provided, which is a second core network network element. The core network network element includes: a second sending unit, used to send a first request to the first core network network element; wherein the first request is used to indicate multiple expected capabilities, and the expected capabilities are the capabilities that the second core network network element expects to subscribe to.
[0010] In the sixth aspect, a core network element is provided which is a first core network element, and the core network element includes: a determination unit for determining the discovery priority of a third core network element based on first information; wherein the first information is used to indicate the capabilities supported by the third core network element.
[0011] In the seventh aspect, a core network element is provided, comprising a processor and a memory, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer program in the memory so that the core network element executes part or all of the steps in the method of the second aspect.
[0012] In an eighth aspect, an embodiment of the present application provides a communication system, which includes the core network element described above. In another possible design, the system may also include other devices that interact with the core network element in the solution provided in the embodiment of the present application.
[0013] In the ninth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program, and the computer program enables the core network network element to execute part or all of the steps in the methods of the above aspects.
[0014] In a tenth aspect, embodiments of the present application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, wherein the computer program is operable to cause a core network element to perform some or all of the steps of the methods described in each of the above aspects. In some implementations, the computer program product may be a software installation package.
[0015] In the eleventh aspect, an embodiment of the present application provides a chip, which includes a memory and a processor. The processor can call and run a computer program from the memory to implement some or all of the steps described in the methods of the above aspects.
[0016] Based on at least two desired capabilities, the first core network element can select a network element that supports both of the desired capabilities as a target core network element. That is, if there is a to-be-discovered network element that supports at least two of the desired capabilities, that core network element can be selected. Compared to selecting appropriate network elements one by one based on only a specific capability, this solution can reduce the number of selected network elements, thereby reducing the number of target core network elements interacting with the second core network element, thereby avoiding signaling waste and reducing complexity. BRIEF DESCRIPTION OF THE DRAWINGS
[0017] FIG1 is a schematic diagram of a network architecture used in an embodiment of the present application.
[0018] FIG2 is an example diagram of a core network element discovery method.
[0019] FIG3 is a schematic flowchart of a method for communication provided in an embodiment of the present application.
[0020] FIG4 is a schematic flowchart of another method for communication provided in an embodiment of the present application.
[0021] FIG5 is a schematic flowchart of another method for communication provided in an embodiment of the present application.
[0022] FIG6 is a schematic flowchart of another method for communication provided in an embodiment of the present application.
[0023] FIG7 is a schematic flowchart of another method for communication provided in an embodiment of the present application.
[0024] FIG8 is a schematic structural diagram of a core network element provided in an embodiment of the present application.
[0025] Figure 9 is a schematic structural diagram of another core network element provided in an embodiment of the present application.
[0026] Figure 10 is a schematic structural diagram of another core network element provided in an embodiment of the present application.
[0027] FIG11 is a schematic structural diagram of a device for communication provided in an embodiment of the present application. DETAILED DESCRIPTION
[0028] The technical solution in this application will be described below with reference to the accompanying drawings.
[0029] Mobile network system architecture
[0030] Figure 1 is a schematic diagram of a network architecture provided by an embodiment of the present application. The network architecture may include terminal equipment, access network (AN) network elements, and core network network elements.
[0031] It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: fifth generation (5G) system or new radio (NR), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), etc. The technical solutions provided in this application can also be applied to future communication systems, such as the sixth generation mobile communication system, satellite communication system, etc.
[0032] The terminal device in the embodiments of the present application may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless core network element, user agent or user device. The terminal device in the embodiments of the present application may refer to a device that provides voice and / or data connectivity to a user and can be used to connect people, objects and machines, such as a handheld device with wireless connection function, a vehicle-mounted device, etc. The terminal device in the embodiments of the present application can be a mobile phone, a tablet computer, a laptop computer, a PDA, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc. Optionally, the UE can be used to act as a base station. For example, the UE can act as a scheduling entity that provides sidelink signals between UEs in vehicle-to-everything (V2X) or device-to-device (D2D). For example, a cellular phone and a car communicate with each other using sidelink signals. The cellular phone and smart home devices communicate without relaying the communication signal through a base station.
[0033] An access network element can be an access network device. This device is used by terminals to wirelessly access the network architecture and is primarily responsible for radio resource management, quality of service (QoS) management, data compression, and encryption on the air interface side. An access network device can also be referred to as a radio access network (RAN) device. For example, an access network device can be a base station. A base station may broadly cover various names as follows, or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), master eNB (MeNB), secondary eNB (SeNB), multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station may be a macro base station, a micro base station, a relay node, a donor node, or the like, or a combination thereof. A base station may also refer to a communication module, modem, or chip used to be set in the aforementioned device or apparatus. A base station may also be a mobile switching center and a device that performs base station functions in D2D, V2X, and machine-to-machine (M2M) communications, a network-side device in a 6G network, or a device that performs base station functions in future communication systems. A base station may support networks with the same or different access technologies. The embodiments of this application do not limit the specific technology and specific device form used by the access network device.
[0034] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move based on the location of the mobile base station. In other examples, a helicopter or drone can be configured to act as a device that communicates with another base station.
[0035] In some deployments, the access network device in the embodiments of the present application may refer to a CU or a DU, or the access network device may include a CU and a DU. The gNB may also include an AAU.
[0036] The types of core network elements may include user plane function (UPF) network element, access and mobility management function (AMF) network element, session management function (SMF) network element, policy control function (PCF) network element, application function (AF), data network (DN), network slice selection function (NSSF), authentication server function (AUSF), unified data management function (UDM), network exposure function (NEF), network repository function (NRF), and network slice-specific authentication and authorization function (NSSAAF). Among them, the UPF network element is mainly responsible for the transmission of user data, and the other network elements can be called control plane function network elements, which are mainly responsible for authentication, authorization, registration management, session management, mobility management, and policy control, etc., to ensure the reliable and stable transmission of user data.
[0037] The UPF network element can be used to forward and receive data from the terminal. For example, the UPF network element can receive service data from the data network and transmit it to the terminal through the access network device; the UPF network element can also receive user data from the terminal through the access network device and forward it to the data network. Among them, the transmission resources allocated and scheduled by the UPF network element for the terminal are managed and controlled by the SMF network element. The bearer between the terminal and the UPF network element may include: the user plane connection between the UPF network element and the access network device, and the establishment of a channel between the access network device and the terminal. Among them, the user plane connection is a QoS flow that can be established between the UPF network element and the access network device to transmit data.
[0038] The AMF network element can be used to manage the terminal's access to the core network, such as terminal location update, network registration, access control, terminal mobility management, terminal attachment and detachment, etc. The AMF network element can also provide control plane storage resources for the session while providing services for the terminal's session, to store the session identifier, the SMF network element identifier associated with the session identifier, etc.
[0039] The SMF network element can be used to select a user plane network element for the terminal, redirect the user plane network element for the terminal, allocate an Internet Protocol (IP) address to the terminal, establish a bearer (also called a session) between the terminal and the UPF network element, modify and release the session, and control QoS.
[0040] The PCF network element is used to provide policies to the AMF network element and the SMF network element, such as QoS policy and slice selection policy.
[0041] The AF network element is used to interact with the 3GPP core network elements to support application-affected data routing, access network exposure functions, and interact with the PCF network elements for policy control.
[0042] A DN can provide data services to users on networks such as IP Multimedia Service (IMS) and the Internet. A DN can contain multiple application servers (ASs) that provide different application services, such as carrier services, Internet access, or third-party services. The ASs can implement AF functions.
[0043] NSSF is used for network slice selection and supports the following functions: selecting the set of network slice instances serving the UE; determining the allowed Network Slice Selection Assistance Information (NSSAI) and, when necessary, determining the mapping to the contracted single-Network Slice Selection Assistance Information (S-NSSAI); determining the configured NSSAI and, when necessary, determining the mapping to the contracted S-NSSAI; determining the set of AMFs that may be used to query the UE, or determining a list of candidate AMFs based on the configuration.
[0044] AUSF is used to receive the request from AMF to authenticate the terminal, request the key from UDM, and then forward the issued key to AMF for authentication processing.
[0045] UDM includes functions such as the generation and storage of user contract data, management of authentication data, and supports interaction with external third-party servers.
[0046] NEF is used for capability exposure. That is, based on NEF, network capabilities can be exported to external networks. External, untrusted applications can access core network data through NEF to ensure network security. NEF can also provide external application QoS capability exposure, event subscription, and AF request distribution.
[0047] The NRF is used to register, manage, and monitor the status of core network elements, enabling automated management of these elements. Upon startup, a core network element must register with the NRF before it can provide services. Registration information may include the core network element's type, address, and service list.
[0048] In addition, some networks (such as 5G networks) have added a network data analytics function (NWDAF) to the core network. Based on NWDAF, data can be collected from various core network elements and network management systems, and big data statistics, analysis, or intelligent data analysis can be performed to obtain network-side analysis or prediction data, thereby assisting various network elements to more effectively control terminal device access based on the data analysis results.
[0049] In some communication systems (such as 5G systems), core network elements may also be referred to as network functions (NFs).
[0050] The network elements in Figure 1 can be network components in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform). It should be noted that the network architecture shown in the above figure is only an example of the network elements included in the entire network architecture. In the embodiments of the present application, the network elements included in the entire network architecture are not limited.
[0051] Those skilled in the art will appreciate that the network architecture shown in FIG1 does not limit the network architecture. In a specific implementation, the network architecture may include more or fewer network elements than shown, or may combine certain network elements. It should be understood that in FIG1 , the AN or RAN is represented by (R)AN.
[0052] Core network element discovery
[0053] A characteristic of some network architectures, such as the 5G network architecture, is a service-based architecture, where core network elements (service providers) can provide specific services and make them available to other network elements (consumers) through defined application programming interfaces (APIs). Core network elements can act as initiators, performing core network element discovery (hereinafter referred to as element discovery), thereby subscribing to the capabilities supported by the service provider and obtaining the services corresponding to those capabilities. Initiators are also called service consumers or service subscribers.
[0054] Before a subscriber wishes to discover a network element, the service provider can register its supported capabilities or services, network element type, address, and other information with the first core network element. Successfully registered core network elements become the network elements to be discovered. The first core network element can control the network element discovery process. That is, if a subscriber wishes to discover a network element, it must interact with the first core network element, which then selects the network element that meets the discovery criteria. The first core network element can include an NRF. That is, the core network element discovery process can be implemented using the NRF.
[0055] The following is an explanation of the network element discovery process of a 5G system with reference to Figure 2. It should be noted that this application does not limit the communication system to which this process is applied, that is, the network element discovery method shown in Figure 2 can be applied to other communication systems.
[0056] The network element discovery method shown in Figure 2 can be implemented by the NF service consumer and the NRF. The method shown in Figure 2 can include steps S210 to S230.
[0057] Step S210: The NF service subscriber sends a discovery request.
[0058] The discovery request may be, for example, an NRF NF discovery request (Nnrf_NFDiscovery_Request).
[0059] By invoking a discovery request, an NF service subscriber can request the discovery of NFs that support the desired capabilities (i.e., the desired NF). This discovery request can be used to indicate the discovery conditions; NFs that meet the discovery conditions will be eligible to provide services to the subscriber. The discovery request can include one or more of the following information: the desired NF service name, the desired NF type, and other information.
[0060] Step S220: NRF authorizes the NF discovery request (Authorize NF Service Discovery).
[0061] The NRF can determine the network elements that meet the discovery request or the network elements that meet the discovery conditions based on the registration information of the NF stored on it.
[0062] In step S230, the NRF sends a response to the discovery request, which may be, for example, a response to the NRF's NF discovery request (Nnrf_NFDiscovery_Request Response).
[0063] Through the response to the discovery request, the NRF can send the address information of the network elements that meet the discovery request to the NF service subscriber.
[0064] With the continuous development of networks, network elements (NEs) support an increasing number of services and possess a growing number of capabilities. The following uses the NEF as an example to introduce the various capabilities that the NEF can possess. First, within the artificial intelligence machine learning system (AIMLsys) project, the NEF introduces QoS monitoring capabilities based on multiple terminal devices. This capability allows the NEF to aggregate the transmission bit rates of multiple terminal devices performing the same task. Furthermore, the NEF compares this aggregated transmission bit rate with a pre-configured threshold to determine whether the sum of the transmission rates of multiple terminal devices exceeds a certain threshold. Furthermore, the NEF can notify third parties of the determination results. Furthermore, the NEF can assist third parties in selecting terminal devices. Based on this capability, the NEF, using the criteria in the third-party request message, can invoke relevant services of other core network elements to collect terminal device information and then select and return qualified terminal devices to the third party.
[0065] The related technology has not yet considered the situation where a network element supports multiple capabilities during the core network element discovery process, which may lead to many problems. For example, if the second core network element expects to subscribe to multiple capabilities, and the first core network element cannot find a single network element that can support all the capabilities that the second core network element expects to subscribe to, the discovery will fail. To prevent the occurrence of discovery failure, the second core network element can only place the multiple capabilities it expects to subscribe to in multiple discovery messages and discover them separately. This will execute multiple discovery processes. This selection method may result in a large number of selected network elements, which will cause the second core network element to interact with more network elements, resulting in signaling waste and increased complexity.
[0066] The following example illustrates the situation where the AF wishes to subscribe to the two capabilities of an NEF. The NRF can select an NEF based on each capability. In this case, an NEF that supports both capabilities may exist, but due to the separate selection, the NRF selects two NEFs, one supporting each capability. This selection requires the AF to interact with two different NEFs to invoke different capabilities. As mentioned above, this leads to wasted signaling and increased operational complexity.
[0067] FIG3 is a schematic flowchart of a method for communication provided in an embodiment of the present application to solve the above-mentioned problem.
[0068] The method shown in FIG3 may be implemented by a first core network element. The first core network element may, for example, be a network element that controls network element discovery, i.e., the first core network element may be responsible for selecting network elements. The first core network element may, for example, be an NRF. The method shown in FIG3 may include step S310.
[0069] Step S310: Based on at least two of the multiple desired capabilities, the first core network element may select one or more target core network elements from the network elements to be discovered.
[0070] The expected capability may be a capability or function that the second core network element expects to subscribe to. Alternatively, the expected capability may be a capability or function requested by the second core network element. It can be seen that the second core network element may be the subscriber, consumer or service requester described above. This application does not limit the type of the second core network element. The second core network element may be of any type described above. For example, the type of the second core network element may be AF, UPF, AMF, SMF, PCF, DN, NSSF, AUSF, UDM or NEF, etc.
[0071] The number of desired capabilities can be multiple. That is, the second core network element can apply to subscribe to multiple capabilities. The multiple desired capabilities can be all capabilities that the second core network device desires to subscribe to.
[0072] The network element to be discovered may be a core network element that can provide services to the second core network element. For example, the network element to be discovered may be a core network element registered with the first core network element.
[0073] A network element to be discovered may support or possess one or more capabilities. Alternatively, a network element to be discovered may support one or more capabilities. For example, if the network element to be discovered is a NEF, the capabilities supported by the network element may include: QoS monitoring capabilities based on multiple terminal devices and / or the ability to assist a third party in selecting a terminal device.
[0074] This application does not limit the capabilities supported by the undiscovered network element. The capabilities supported by the undiscovered network element may depend on the network deployment or development of the undiscovered network element. The undiscovered network element may support all capabilities supported by the network element type, or may only support some capabilities supported by the network element type.
[0075] The first core network element may select a target core network element. The target core network element may be an element selected by the first core network element that meets the desired capabilities. In other words, the target core network element may support some or all of the desired capabilities. Alternatively, the target core network element may be an element that meets the discovery criteria or satisfies the discovery requirements.
[0076] Based on at least two desired capabilities, the first core network element can select a network element that supports both of the desired capabilities as a target core network element. That is, if there is a to-be-discovered network element that supports at least two of the desired capabilities, that core network element can be selected. Compared to selecting appropriate network elements one by one based on only a specific capability, this solution can reduce the number of selected network elements, thereby reducing the number of target core network elements interacting with the second core network element, thereby avoiding signaling waste and reducing complexity.
[0077] For example, the desired capabilities of the second core network element include capability 1, capability 2, and capability 3. In some embodiments, the first core network element may select a target core network element based on capability 1, capability 2, and capability 3. In some embodiments, the first core network element may select a target core network element based on any two of capability 1, capability 2, and capability 3.
[0078] This application does not limit the number of desired capabilities supported by the target core network element. The target core network element may be a network element that supports some or all of the multiple desired capabilities.
[0079] In some embodiments, the selected target core network element may support all desired capabilities. For example, the target core network element may be any network element that individually supports all desired capabilities.
[0080] For ease of understanding, the following description uses the NEF type as an example, with reference to Table 1. As shown in Table 1, the network defines three types of NEFs. NEF1 has capabilities 1, 2, and 3. NEF2 has capability 2. NEF3 has capability 3.
[0081] Table 1
[0082] In the case that NEF1, NEF2 and NEF3 are all registered with the NRF, if the desired capabilities include capability 1, capability 2 and capability 3, the target core network element may be NEF1 that supports all the desired capabilities.
[0083] In some embodiments, the selected target core network element may support some of the expected capabilities. For example, the target core network element may support one of a plurality of expected capabilities. Based on this solution, even if there is no network element that meets all the expected capabilities among the network elements to be discovered, the first core network element may select a target core network element to meet some of the expected capabilities of the second core network element, thereby meeting the needs of the second core network element to a certain extent. Continuing to refer to Table 1, in the case where both NEF2 and NEF3 are registered with NRF, if the expected capabilities include capability 2 and capability 3, one or more target core network elements may include NEF2 and / or NEF3 that support some of the expected capabilities.
[0084] In the case where none of the network elements to be discovered can support multiple desired capabilities individually, the first core network element can select multiple target core network elements from the network elements to be discovered. The multiple target core network elements support all of the multiple desired capabilities. That is, when a single network element cannot support the requested capabilities, multiple target core network elements can be selected. The sum of the capabilities supported by the multiple target core network elements can satisfy all requested capabilities. It is understandable that, even if no network element supports all desired capabilities at the same time, based on the present application, it is still possible to select multiple target core network elements to meet all functional requirements of the second core network element, thereby reducing the probability of network element discovery failure.
[0085] Continuing with Table 1, if both NEF2 and NEF3 are registered with the NRF, and the desired capabilities include capability 2 and capability 3, as shown in Table 1, none of the NEFs registered with the NRF supports both capabilities 2 and 3, the NRF can select multiple target core network elements. These multiple target core network elements may include NEF2 and NEF3. Capability 2 supported by NEF2 and capability 3 supported by NEF3 can together satisfy the desired capabilities of the second core network element, thus avoiding network element discovery failure.
[0086] In some embodiments, the target core network element may be selected in combination with the first rule. The first rule may be related to the first number and the discovery priority of the network element to be discovered.
[0087] The first number may be the number of network elements to be discovered that support the desired capabilities. As an implementation, network elements to be discovered having a larger first number may be preferentially selected. For example, the network elements to be discovered may include a first network element to be selected and a second network element to be selected. The first rule may include: if the first number of the first network elements to be selected is greater than or equal to the first number of the second network elements to be selected, the first network element to be selected may be selected. Alternatively, if the first number of the second network elements to be selected is greater than or equal to the first number of the first network elements to be selected, the second network element to be selected may be selected.
[0088] Continuing with Table 1 as an example, if the desired capabilities include capability 1 and capability 3, the first number of NEF1 is 2, the first number of NEF2 is 0, and the first number of NEF3 is 1. When NEF1, NEF2, and NEF3 are all registered with the NRF, NEF1 has a larger first number among the three NEFs, so NEF1 can be preferentially selected as the target core network element.
[0089] The discovery priority may indicate the probability of the corresponding to-be-discovered network element being preferentially selected. The higher the discovery priority, the greater the probability of the corresponding to-be-discovered network element being selected, that is, the more likely the corresponding to-be-discovered network element is to be selected.
[0090] The discovery priority may be determined by the first core network element. As an implementation, the discovery priority may be determined during the registration process. For example, the discovery priority may be determined based on the first information (e.g., step S410 shown in FIG4 ). The first information may be transmitted during the registration process.
[0091] Taking the determination of the discovery priority of a third core network element as an example, the first information may be used to indicate one or more of the following information about the third core network element: one or more supported capabilities, an address, and a type. The one or more capabilities supported by the third core network element may be information about all capabilities supported by the third core network element. In other words, the first information may be used to indicate all capability information of the third core network element.
[0092] The first information may be a profile. Taking the third core network element as an NEF as an example, the first information may be a NEF profile.
[0093] As an example, the discovery priority may be related to the second number. The second number may be the number of capabilities supported by the to-be-discovered network element. The second number may be determined based on the first information.
[0094] As an implementation, the larger the second number, the higher the discovery priority can be. The larger the second number, the more complete the capabilities of the corresponding to-be-discovered network element. In the case of currently selecting to-be-discovered network elements with a large second number, the following situation may occur: if one or more capabilities that the second core network network element subsequently wishes to subscribe to are supported by the to-be-discovered network element, the second core network network element can continue to receive services from the network element without having to initiate the network element discovery process again, thereby enabling communication interaction and improving system efficiency.
[0095] Continuing with Table 1 as an example, NEF1's second number is 3, NEF2's second number is 1, and NEF3's second number is 1. Since NEF1 has the largest second number, meaning it has more comprehensive capabilities, NEF1 can be given a higher discovery priority, while NEF2 and NEF3 can both be given a lower discovery priority.
[0096] After a first core network element selects one or more target core network elements, the first core network element may send a first indication. The first indication information may be used to indicate information about the selected core network elements. That is, the first indication information may be used to indicate information about the target core network elements. For example, the first indication may be used to indicate one or more of the following information about the one or more target core network elements: identification, type, supported capability information, and address.
[0097] If the first core network element does not select the target core network element, the first indication information may not be sent. Alternatively, the sent first indication information may indicate that "the target core network element is not selected."
[0098] In some embodiments, the method shown in FIG3 may further include step S305 .
[0099] Step S305: The first core network element receives the first request. Correspondingly, the second core network element sends the first request.
[0100] The first request can be used to indicate multiple desired capabilities. In other words, the first request can be a request for a set of capability information. A set of capability information can include multiple desired capability information. A request for a set of capability information can be carried in a single message. For example, a set of capability requests can be carried in a network element discovery request. The first request can be used not only to indicate multiple desired capabilities, but also to indicate the network element types (e.g., NEF) corresponding to the multiple desired capabilities.
[0101] In some embodiments, the first request may be used to request network element discovery. For example, the first request may be carried in a network element discovery request.
[0102] Based on the first request, the second core network element can include multiple desired capabilities in one signaling, that is, can request multiple desired capabilities at the same time. It is understandable that this can reduce the request messages sent by the second core network element, thereby reducing signaling interactions and improving communication efficiency.
[0103] As mentioned above, the first core network element can determine the discovery priority of the third core network element during the registration process. The registration process is described below with reference to FIG5 .
[0104] Figure 5 can be performed by the first core network element and the third core network element. This application does not limit the type of the third core network element. The third core network element can be any element that wishes to register with the first core network element.
[0105] The method shown in FIG. 5 may include steps S510 to S540 .
[0106] Step S510: The third core network element sends first information to the first core network element.
[0107] The first information may be used to indicate capability information of the third core network element. For an introduction to the first information, please refer to the previous text and will not be repeated here. The first information may be carried in a registration request message. The registration request message may be, for example, an Nnrf_NFManagement_NFRegister_request message.
[0108] As described above, the first information can be used to indicate all capability information of the third core network element. When the first core network element obtains all capability information of the third core network element through the first information, the initiator can be guaranteed to find a suitable network element during the network element discovery process.
[0109] When multiple core network elements all wish to register with the first core network element, the multiple core network elements may respectively send corresponding first information.
[0110] Continuing with Table 1, if NEF1, NEF2, and NEF3 all wish to register with the NRF, NEF1, NEF2, and NEF3 can each send corresponding first information to the NRF, thereby registering their corresponding capability information with the NRF. The first information corresponding to NEF1 can include one or more items of information from the row containing NEF1 in Table 1. The first information corresponding to NEF2 can include one or more items of information from the row containing NEF2 in Table 1. The first information corresponding to NEF3 can include one or more items of information from the row containing NEF3 in Table 1.
[0111] Step S520: The first core network element saves the first information of the third core network element.
[0112] The first core network element may further mark the third core network element as an available network element or a valid network element.
[0113] Step S530: Based on the first information, the first core network element may determine the discovery priority of the third core network element.
[0114] Step S540: The first core network element replies to the third core network element that the registration is accepted.
[0115] For ease of understanding, the registration process of NEF1-3 is described in detail below with reference to Table 1 and FIG6 .
[0116] In step S610, NEF1 to NEF3 send their respective registration requests to the NRF and register their capability information with the NRF, wherein the registration request may include an NEF profile.
[0117] For example, step S610 may include steps S611 to S613.
[0118] Step S611: NEF1 sends a registration request (Nnrf_NFManagement_NFRegister_request), which includes an introduction to NEF1.
[0119] Step S612: NEF2 sends a registration request, which includes an introduction of NEF2.
[0120] Step S613: NEF3 sends a registration request, which includes an introduction to NEF3.
[0121] In step S620, after receiving the registration information of each NE, the NRF saves the profile of each NEF. In addition, the NRF can also mark each NE as an available and valid NE.
[0122] NRF can also determine the discovery priority of each NEF based on the NEF profile. As shown in Table 1, because NEF1 has more complete capabilities, NRF can mark NEF1 as a higher discovery priority. That is, the discovery priority of NEF2 and NEF3 is lower than that of NEF1.
[0123] In step S630, the NRF replies to NEF1 to NEF3 respectively that the registration is accepted.
[0124] The registration acceptance may be sent via a registration response (Nnrf_NFManagement_NFRegister_response). That is, step S630 may include steps S631 to S633.
[0125] In step S631, NRF sends a registration response to NEF1 to acknowledge that the registration is accepted.
[0126] In step S632, NRF sends a registration response to NEF2 to indicate that the registration is accepted.
[0127] In step S633, NRF sends a registration response to NEF3 to indicate that the registration is accepted.
[0128] After NEF1-NEF3 complete NRF registration, the NF service consumer can perform network element discovery. Figure 7 is a schematic flow chart of the NF network element discovery process. The method shown in Figure 7 can be performed by the NRF and NEF service consumer. The method shown in Figure 7 may include steps S710 to S740.
[0129] In step S710, the NF service consumer sends a discovery request (Nnrf_NFDiscovery_Request) to the NRF.
[0130] The discovery request may include the NF type desired to be discovered and a set of capability requests (multiple capability information).
[0131] Step S720: The NRF authorizes the discovery request of the NF service consumer.
[0132] In step S730 , the NRF compares the NEF profiles saved in step S620 with the set of capability requests and selects the most appropriate NEF.
[0133] Step S730 may include but is not limited to the following three situations.
[0134] Case 1: When the capabilities requested by the NF service consumer include capability 1, capability 2, and capability 3, the NRF directly returns NEF1 to the NF service consumer with the highest priority.
[0135] Case 2: When the capability requested by the NF service consumer is capability 2, if NEF1 exists, the NRF returns NEF1 to the NF service consumer due to priority; if NEF1 does not exist, the NRF returns NEF2 to the NF service consumer.
[0136] Case 3: When the NF service consumer requests capability 2 and capability 3, and NEF1 does not exist, the NRF can return NEF2 and NEF3 to the requester at the same time, and indicate that NEF2 supports capability 2 and NEF3 supports capability 3.
[0137] In step S740, the NRF sends a discovery request response (Nnrf_NFDiscovery_Request Response) to the NF service consumer.
[0138] The response to the discovery request may include: an indication of the NEF that meets the conditions and capability information corresponding to the NEF that meets the conditions.
[0139] It should be noted that, in some embodiments, a network element may also be referred to as a node.
[0140] The above describes the method embodiment of the present application in detail, and the following describes the device embodiment of the present application in detail. It should be understood that the description of the method embodiment corresponds to the description of the device embodiment, so for parts not described in detail, reference can be made to the previous method embodiment.
[0141] FIG8 is a schematic structural diagram of a core network element 800 provided in an embodiment of the present application. The core network element 800 may be a first core network element and may include a selection unit 810.
[0142] The selection unit 810 is used to select one or more target core network elements from the network elements to be discovered based on at least two of the multiple expected capabilities; wherein the expected capabilities are capabilities that the second core network element expects to subscribe to, and the target core network element supports some or all of the multiple expected capabilities.
[0143] In some embodiments, the first core network element selects one or more target core network elements from the network elements to be discovered, including: when any one of the network elements to be discovered cannot support multiple expected capabilities individually, the first core network element selects multiple target core network elements from the network elements to be discovered; wherein, the multiple target core network elements support multiple expected capabilities.
[0144] In some embodiments, the number of expected capabilities supported by the network elements to be discovered is a first number, and the first core network element selects one or more target core network elements from the network elements to be discovered, including: in combination with the first rule, the first core network element selects one or more target core network elements from the network elements to be discovered; wherein the first rule is related to one or more of the following information: the first number, the discovery priority of the network elements to be discovered.
[0145] In some embodiments, the network element to be discovered includes a first network element to be selected and a second network element to be selected, and the first rule includes: when the first number of the first network elements to be selected is greater than or equal to the first number of the second network elements to be selected, selecting the first network element to be selected; or, when the first number of the second network elements to be selected is greater than or equal to the first number of the first network elements to be selected, selecting the second network element to be selected.
[0146] In some embodiments, the number of capabilities supported by the network element to be discovered is a second number, and the discovery priority is related to the second number.
[0147] In some embodiments, the larger the second number, the higher the discovery priority.
[0148] In some embodiments, the core network element 800 further includes: a first receiving unit, configured to receive a first request from a second core network element; wherein the first request is used to indicate a plurality of desired capabilities.
[0149] In some embodiments, the core network element 800 further includes: a first sending unit, configured to send a first indication; wherein the first indication is configured to indicate one or more of the following information of one or more target core network elements: identification, supported capability information.
[0150] FIG9 is a schematic structural diagram of another core network element 900 provided in an embodiment of the present application. The core network element 900 may be a second core network element and may include a second sending unit 910.
[0151] The second sending unit 910 is used to send a first request to the first core network element; wherein the first request is used to indicate multiple desired capabilities, and the desired capabilities are capabilities that the second core network element desires to subscribe to.
[0152] In some embodiments, one or more target core network elements are selected from the to-be-discovered network elements based on at least two of a plurality of desired capabilities, and the target core network elements support some or all of the plurality of desired capabilities.
[0153] In some embodiments, when any one of the network elements to be discovered cannot support multiple desired capabilities independently, there are multiple target core network elements, and the multiple target core network elements support multiple desired capabilities.
[0154] In some embodiments, the number of expected capabilities supported by the network elements to be discovered is a first number, and one or more target core network elements are selected in combination with a first rule, and the first rule is related to one or more of the following information: the first number, and the discovery priority of the network elements to be discovered.
[0155] In some embodiments, the network element to be discovered includes a first network element to be selected and a second network element to be selected, and the first rule includes: when the first number of the first network elements to be selected is greater than or equal to the first number of the second network elements to be selected, selecting the first network element to be selected; or, when the first number of the second network elements to be selected is greater than or equal to the first number of the first network elements to be selected, selecting the second network element to be selected.
[0156] In some embodiments, the number of capabilities supported by the network element to be discovered is a second number, and the discovery priority is related to the second number.
[0157] In some embodiments, the larger the second number, the higher the discovery priority.
[0158] In some embodiments, the core network element 900 also includes: a second receiving unit, used to receive a first indication sent by the first core network element; wherein the first indication is used to indicate one or more of the following information of one or more target core network elements: identification, supported capability information.
[0159] FIG10 is a schematic structural diagram of another core network element 1000 provided in an embodiment of the present application. The core network element 1000 may be a first core network element. The core network element 1000 may include a determining unit 1010.
[0160] The determining unit 1010 is used to determine the discovery priority of the third core network network element according to the first information; wherein the first information is used to indicate the capabilities supported by the third core network network element.
[0161] In some embodiments, the discovery priority is related to the number of capabilities supported by the third core network element.
[0162] In some embodiments, the greater the number of capabilities supported by the third core network element, the higher the discovery priority.
[0163] In an optional embodiment, the selection unit 810 or the determination unit 1010 may be a processor 1110. The second sending unit 910 may be a transceiver 1130. The core network element 800 or the core network element 1000 may further include a transceiver 1130 and a memory 1120. The core network element 900 may further include a processor 1110 and a memory 1120. This is shown in detail in FIG11.
[0164] Figure 11 is a schematic block diagram of a communication device according to an embodiment of the present application. Dashed lines in Figure 11 indicate that the unit or module is optional. Device 1100 may be used to implement the method described in the above method embodiment. Device 1100 may be a chip, terminal device, access network device, or core network device.
[0165] The device 1100 may include one or more processors 1110. The processor 1110 may support the device 1100 to implement the method described in the method embodiment above. The processor 1110 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.
[0166] The apparatus 1100 may further include one or more memories 1120. The memories 1120 store programs that can be executed by the processor 1110, causing the processor 1110 to perform the methods described in the above method embodiments. The memories 1120 may be independent of the processor 1110 or integrated into the processor 1110.
[0167] The apparatus 1100 may further include a transceiver 1130. The processor 1110 may communicate with other devices or chips via the transceiver 1130. For example, the processor 1110 may transmit and receive data with other devices or chips via the transceiver 1130.
[0168] The present application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to the core network element provided in the present application, and the program enables a computer to execute the method performed by the core network element in each embodiment of the present application.
[0169] The present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to the core network element provided in the present application, and the program causes a computer to execute the method performed by the core network element in each embodiment of the present application.
[0170] The embodiments of the present application also provide a computer program that can be applied to the core network element provided in the embodiments of the present application, and the computer program enables a computer to execute the method performed by the core network element in each embodiment of the present application.
[0171] It should be understood that the terms "system" and "network" in this application can be used interchangeably. In addition, the terms used in this application are only used to explain the specific embodiments of this application and are not intended to limit this application. The terms "first", "second", "third", and "fourth" in the specification and claims of this application and the accompanying drawings are used to distinguish different objects rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions.
[0172] In the embodiments of this application, the term "indication" may refer to a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" may refer to a direct indication of B, e.g., B can obtain information through A; it may refer to an indirect indication of B, e.g., A indicates C, e.g., B can obtain information through C; or it may refer to an association between A and B.
[0173] In the embodiment of the present application, "B corresponding to A" means that B is associated with A and B can be determined based on A. However, it should be understood that determining B based on A does not mean determining B based solely on A, but B can also be determined based on A and / or other information.
[0174] In the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and indication, configuration and configuration, etc.
[0175] In the embodiments of the present application, "pre-definition" or "pre-configuration" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., a terminal device and a network device). The present application does not limit the specific implementation method. For example, pre-definition may refer to information defined in a protocol.
[0176] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communications field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.
[0177] In the embodiments of this application, the term "and / or" is simply a description of the association relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this document generally indicates that the related objects are in an "or" relationship.
[0178] In the embodiments of this application, the term "include" can refer to direct inclusion or indirect inclusion. Alternatively, the term "include" in the embodiments of this application can be replaced with "indicates" or "is used to determine." For example, "A includes B" can be replaced with "A indicates B" or "A is used to determine B."
[0179] In various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.
[0180] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
[0181] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.
[0182] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
[0183] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).
[0184] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.
Claims
1. A method for communication, characterized in that include: Based on at least two of the multiple expected capabilities, the first core network element selects one or more target core network elements from the network elements to be discovered; The expected capabilities are capabilities that the second core network element expects to subscribe to, and the target core network element supports some or all of the multiple expected capabilities.
2. The method according to claim 1, characterized in that: The first core network element selecting one or more target core network elements from the to-be-discovered network elements includes: In a case where any one of the network elements to be discovered cannot support the multiple expected capabilities alone, the first core network element selects multiple target core network elements from the network elements to be discovered; Among them, the multiple target core network elements support the multiple expected capabilities.
3. The method according to claim 1 or 2, characterized in that: The number of the expected capabilities supported by the network elements to be discovered is a first number, and the first core network element selects one or more target core network elements from the network elements to be discovered, including: In combination with the first rule, the first core network element selects one or more target core network elements from the network elements to be discovered; The first rule is related to one or more of the following information: the first number and the discovery priority of the network element to be discovered.
4. The method according to claim 3, characterized in that The network elements to be discovered include a first network element to be selected and a second network element to be selected, and the first rule includes: when the first number of the first network elements to be selected is greater than or equal to the first number of the second network elements to be selected, selecting the first network element to be selected; or, when the first number of the second network elements to be selected is greater than or equal to the first number of the first network elements to be selected, selecting the second network element to be selected.
5. The method according to claim 3 or 4, characterized in that: The number of capabilities supported by the network element to be discovered is a second number, and the discovery priority is related to the second number.
6. The method according to claim 5, characterized in that The larger the second number is, the higher the discovery priority is.
7. The method according to any one of claims 1 to 6, characterized in that The method further comprises: The first core network element receives a first request from the second core network element; The first request is used to indicate the multiple desired capabilities.
8. The method according to any one of claims 1 to 7, characterized in that The method further comprises: The first core network element sends a first instruction; The first indication is used to indicate one or more of the following information of the one or more target core network elements: identification, supported capability information.
9. A method for communication, characterized in that include: The second core network network element sends a first request to the first core network network element; The first request is used to indicate a plurality of expected capabilities, where the expected capabilities are capabilities that the second core network element expects to subscribe to.
10. The method according to claim 9, characterized in that One or more target core network elements are selected from the network elements to be discovered based on at least two of a plurality of desired capabilities, and the target core network elements support part or all of the plurality of desired capabilities.
11. The method according to claim 10, characterized in that In the case that any one of the network elements to be discovered cannot support the multiple desired capabilities independently, there are multiple target core network elements, and the multiple target core network elements support the multiple desired capabilities.
12. The method according to claim 10 or 11, characterized in that: The number of network elements to be discovered that support the expected capabilities is a first number, and one or more target core network elements are selected in combination with a first rule, wherein the first rule is related to one or more of the following information: the first number and the discovery priority of the network elements to be discovered.
13. The method according to claim 12, characterized in that The network elements to be discovered include a first network element to be selected and a second network element to be selected, and the first rule includes: when the first number of the first network elements to be selected is greater than or equal to the first number of the second network elements to be selected, selecting the first network element to be selected; or, when the first number of the second network elements to be selected is greater than or equal to the first number of the first network elements to be selected, selecting the second network element to be selected.
14. The method according to claim 12 or 13, characterized in that The number of capabilities supported by the network element to be discovered is a second number, and the discovery priority is related to the second number.
15. The method according to claim 14, characterized in that The larger the second number is, the higher the discovery priority is.
16. The method according to any one of claims 9 to 15, characterized in that: The method further comprises: The second core network network element receives a first instruction sent by the first core network network element; The first indication is used to indicate one or more of the following information of the one or more target core network elements: identification, supported capability information.
17. A method for communication, characterized in that The method comprises: According to the first information, the first core network network element determines the discovery priority of the third core network network element; The first information is used to indicate the capabilities supported by the third core network element.
18. The method according to claim 17, the method according to claim 2, characterized in that: The discovery priority is related to the number of capabilities supported by the third core network element.
19. The method according to claim 18, characterized in that The greater the number of capabilities supported by the third core network element, the higher the discovery priority.
20. A core network element, characterized in that: The core network element is a first core network element, and the core network element includes: A selection unit, configured to select one or more target core network elements from the network elements to be discovered based on at least two of the multiple expected capabilities; The expected capabilities are capabilities that the second core network element expects to subscribe to, and the target core network element supports some or all of the multiple expected capabilities.
21. The core network element according to claim 20, characterized in that: The first core network element selecting one or more target core network elements from the to-be-discovered network elements includes: In a case where any one of the network elements to be discovered cannot support the multiple expected capabilities alone, the first core network element selects multiple target core network elements from the network elements to be discovered; Among them, the multiple target core network elements support the multiple expected capabilities.
22. The core network element according to claim 20 or 21, characterized in that: The number of the expected capabilities supported by the network elements to be discovered is a first number, and the first core network element selects one or more target core network elements from the network elements to be discovered, including: In combination with the first rule, the first core network element selects one or more target core network elements from the network elements to be discovered; The first rule is related to one or more of the following information: the first number and the discovery priority of the network element to be discovered.
23. The core network element according to claim 22, characterized in that: The network elements to be discovered include a first network element to be selected and a second network element to be selected, and the first rule includes: when the first number of the first network elements to be selected is greater than or equal to the first number of the second network elements to be selected, selecting the first network element to be selected; or, when the first number of the second network elements to be selected is greater than or equal to the first number of the first network elements to be selected, selecting the second network element to be selected.
24. The core network element according to claim 22 or 23, characterized in that: The number of capabilities supported by the network element to be discovered is a second number, and the discovery priority is related to the second number.
25. The core network element according to claim 24, characterized in that: The larger the second number is, the higher the discovery priority is.
26. The core network element according to any one of claims 20 to 25, characterized in that: The core network element also includes: A first receiving unit, configured to receive a first request from the second core network element; The first request is used to indicate the multiple desired capabilities.
27. The core network element according to any one of claims 20 to 26, characterized in that: The core network element also includes: A first sending unit, configured to send a first instruction; The first indication is used to indicate one or more of the following information of the one or more target core network elements: identification, supported capability information.
28. A core network element, characterized in that: The core network element is a second core network element, and the core network element includes: A second sending unit, configured to send a first request to a first core network element; The first request is used to indicate a plurality of expected capabilities, where the expected capabilities are capabilities that the second core network element expects to subscribe to.
29. The core network element according to claim 28, characterized in that: One or more target core network elements are selected from the network elements to be discovered based on at least two of a plurality of desired capabilities, and the target core network elements support part or all of the plurality of desired capabilities.
30. The core network element according to claim 29, characterized in that: In the case that any one of the network elements to be discovered cannot support the multiple desired capabilities independently, there are multiple target core network elements, and the multiple target core network elements support the multiple desired capabilities.
31. The core network element according to claim 29 or 30, characterized in that: The number of network elements to be discovered that support the expected capabilities is a first number, and one or more target core network elements are selected in combination with a first rule, wherein the first rule is related to one or more of the following information: the first number and the discovery priority of the network elements to be discovered.
32. The core network element according to claim 31, characterized in that: The network elements to be discovered include a first network element to be selected and a second network element to be selected, and the first rule includes: when the first number of the first network elements to be selected is greater than or equal to the first number of the second network elements to be selected, selecting the first network element to be selected; or, when the first number of the second network elements to be selected is greater than or equal to the first number of the first network elements to be selected, selecting the second network element to be selected.
33. The core network element according to claim 31 or 32, characterized in that: The number of capabilities supported by the network element to be discovered is a second number, and the discovery priority is related to the second number.
34. The core network element according to claim 33, characterized in that: The larger the second number is, the higher the discovery priority is.
35. The core network element according to any one of claims 28 to 34, characterized in that: The core network element also includes: A second receiving unit, configured to receive a first indication sent by the first core network element; The first indication is used to indicate one or more of the following information of the one or more target core network elements: identification, supported capability information.
36. A core network element, characterized in that: The core network element is a first core network element, and the core network element includes: A determining unit, configured to determine a discovery priority of a third core network network element according to the first information; The first information is used to indicate the capabilities supported by the third core network element.
37. The core network element according to claim 36, characterized in that: The discovery priority is related to the number of capabilities supported by the third core network element.
38. The core network element according to claim 37, characterized in that: The greater the number of capabilities supported by the third core network element, the higher the discovery priority.
39. A core network element, characterized in that: It includes a memory and a processor, the memory is used to store a program, and the processor is used to call the program in the memory so that the core network element executes the method as described in any one of claims 1-19.
40. A device, characterized in that The device comprises a processor, configured to call a program from a memory so as to enable the device to execute the method according to any one of claims 1 to 19.
41. A chip, characterized in that: It comprises a processor, which is used to call a program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 19.
42. A computer-readable storage medium, characterized in that: A program is stored thereon, the program causing a computer to execute the method according to any one of claims 1 to 19.
43. A computer program product, characterized in that The method comprises a program which causes a computer to execute the method according to any one of claims 1 to 19.
44. A computer program, characterized in that The computer program enables a computer to execute the method according to any one of claims 1 to 19.
Citation Information
Patent Citations
Method and device for realizing network capability opening
CN111726381A
Core network entity, base station and method
CN113055944A
Core network assisted service discovery
US20210282003A1
Technique for handling subscription-related capability information stored in a core network domain
WO2023274564A1
