Communication method and apparatus

Abstract

Disclosed in the present application are a communication method and an apparatus. The method comprises: a network storage function network element receives a registration request from a first network element, the first network element being used for storing CAG information, the registration request comprising a first network function configuration file, the first network function configuration file comprising identification information of the first network element and further comprising at least one piece of information among first information and second information, the first information indicating the CAG information managed by the first network element, and the second information indicating a service area managed by the first network element; the network storage function network element saves the first network function configuration file; and the network storage function network element sends a registration response to the first network element. In the solution, carrying the first information and / or the second information in the network function configuration file can distinguish the first network element from other network elements of the same type, thus helping to improve the accuracy and efficiency of discovering and selecting network elements.

Description

Communication method and device

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of the People's Republic of China on April 2, 2024, with application number 202410397947.4 and application name "A Communication Method and Device", the entire contents of which are incorporated by reference into this application. Technical Field

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

[0004] In a public network integrated-non-public network (PNI-NPN), a closed access group (CAG) mechanism is introduced to restrict the access of terminal devices. On the one hand, a CAG cell broadcasts one or more CAG information (such as a CAG identifier (ID)) that it supports. Each CAG information can identify a group of terminal devices. Only the terminal devices in the group are allowed to access the corresponding CAG cell (such as sending a registration request), while other terminal devices are not allowed to access the corresponding CAG cell. On the other hand, the allowed CAG information of the terminal device is stored in the network element of the network. When a terminal device requests access to the CAG cell (such as receiving a registration request sent by the terminal device), the allowed CAG information of the terminal device is obtained from the network element and a decision is made based on the information whether to allow the terminal device to access (i.e., perform access control).

[0005] However, there may be multiple network elements in the existing network responsible for storing CAG information, and the allowed CAG information of the terminal device may only be stored on some of these network elements. However, the parameters used for network element discovery and selection (such as network element type, service type, etc.) of these multiple network elements are the same, so the problem of failure to obtain CAG information due to incorrect network element discovery and selection often occurs, resulting in failure of the terminal device to access the network. Summary of the Invention

[0006] The present application provides a communication method and apparatus for improving the accuracy of network element discovery and selection, thereby increasing the success rate of terminal devices accessing the network.

[0007] In a first aspect, a communication method is provided, which is applied to a network storage function network element. Unless otherwise specified, the "network element" in this application can refer to the network element itself, or a component in the network element (for example, a processor, a chip, or a chip system, etc.), or a logical module or software that can implement all or part of the network element functions. The method includes: the network storage function network element receives a registration request from a first network element; wherein the first network element is used to store closed access group (CAG) information, the registration request includes a first network function configuration file, the first network function configuration file includes identification information of the first network element, and also includes at least one of first information and second information, the first information indicating CAG information managed by the first network element, and the second information indicating a service area managed by the first network element; the network storage function network element stores the first network function configuration file; and the network storage function network element sends a registration response to the first network element.

[0008] In the above scheme, when the first network element registers with the network storage function network element, it carries the first information and / or the second information in the network function configuration file. The first information and / or the second information can distinguish the first network element from other network elements of the same type, which helps to improve the accuracy and efficiency of network element discovery and selection.

[0009] In one possible design, a network storage function network element receives a service discovery request from a second network element; the network storage function network element sends a service discovery response to the second network element, where the service discovery response includes a first network function configuration file; wherein the service discovery request includes at least one CAG information, and the at least one CAG information belongs to the CAG information indicated by the first information; and / or, the service discovery request includes at least one service area identifier, and the service area indicated by the at least one service area identifier belongs to the service area indicated by the second information. The service area identifier is, for example, a tracking area identity (TAI).

[0010] In this design method, the second network element carries CAG information and / or service area identifier in the service discovery request, so that the network storage function network element can match and feedback the network function configuration file based on the CAG information and / or service area identifier, thereby improving the accuracy and efficiency of network element discovery and selection.

[0011] In one possible design, the first network function configuration file also includes third information, and the third information indicates the terminal device identifier managed by the first network element. The terminal device identifier is, for example, a generic public subscription identifier (GPSI).

[0012] In this way, different network elements that manage the same CAG information and / or the same service area can be distinguished based on the third information, which can further improve the efficiency and accuracy of network element discovery and selection.

[0013] In a possible design, the service discovery request further includes at least one terminal device identifier, and the at least one terminal device identifier belongs to the terminal device identifier indicated by the third information, wherein the terminal device identifier is, for example, GPSI.

[0014] In this way, combined with the terminal device identification discovery and selection of network elements, a network element can be uniquely identified in scenarios where different network elements manage the same CAG information and / or manage the same service area, which can further improve the efficiency and accuracy of network element discovery and selection.

[0015] In one possible design, the network storage function network element also receives at least one terminal device identifier from the first network element, and the at least one terminal device identifier is used to identify the terminal device corresponding to the CAG information stored in the first network element; the network storage function network element updates the at least one terminal device identifier to the first network function configuration file.

[0016] In this way, different network elements that manage the same CAG information and / or manage the same service area can be distinguished based on at least one terminal device identifier, which can further improve the efficiency and accuracy of network element discovery and selection.

[0017] In one possible design, the service discovery request also includes a first terminal device identifier, and the first terminal device identifier is stored in the first network function configuration file.

[0018] In this way, combined with the terminal device identification discovery and selection of network elements, a network element can be uniquely identified in scenarios where different network elements manage the same CAG information and / or manage the same service area, which can further improve the efficiency and accuracy of network element discovery and selection.

[0019] In one possible design, the network storage function network element also receives a service discovery request from the second network element; the network storage function network element sends a service discovery response to the second network element, the service discovery response indicates that the service discovery failed, and the service discovery response includes a reason value, which indicates the reason for the service discovery failure; wherein, the service discovery request includes at least one CAG information, and the at least one CAG information does not belong to the CAG information corresponding to any network function configuration file stored in the network storage function network element; and / or, the service discovery request includes at least one service area identifier, and the service area indicated by the at least one service area identifier does not belong to the service area corresponding to any network function configuration file stored in the network storage function network element.

[0020] In this design method, the second network element carries CAG information and / or service area identifier in the service discovery request. The network storage function network element matches the network function configuration file based on the CAG information and / or service area identifier, and indicates the service discovery failure and reason value when the match fails, thereby improving the reliability of the solution.

[0021] In one possible design, the second network element mentioned above may be a network exposure function (NEF) network element or an access and mobility management function (AMF) network element.

[0022] In one possible design, the service discovery request is a first service discovery request, and at least one CAG information is the CAG information of the CAG cell to which the terminal device is allowed to access. The network storage function network element also receives a second service discovery request from a third network element, and the second service discovery request includes the first CAG information, and the first CAG information is the CAG information of the CAG cell to which the terminal device accesses; the network storage function network element sends a second service discovery response to the third network element, and the second service discovery response includes the first network function configuration file, and the first CAG information belongs to the CAG information indicated by the first information. Optionally, the second network element is NEF, and the third network element is AMF.

[0023] It can be seen that the technical solution of the embodiment of the present application can be applied in different network element discovery scenarios, and the solution has a wide range of adaptability.

[0024] In one possible design, the first information includes: at least one CAG information range, where the first network element manages CAG information within the at least one CAG information range; or at least one CAG information set, where the first network element manages CAG information within the at least one CAG information set. Of course, the above is merely an example and is not intended to be limiting.

[0025] In one possible design, the third information includes: at least one terminal device identification range, where the first network element manages terminal device identifications within the at least one terminal device identification range; or at least one terminal device identification set, where the first network element manages terminal device identifications within the at least one terminal device identification set. Of course, the above is merely an example and is not limited thereto.

[0026] In a second aspect, a communication method is provided, which is applied to a first network element. Unless otherwise specified, the "network element" in this application can refer to the network element itself, or a component in the network element (for example, a processor, a chip, or a chip system, etc.), or a logical module or software that can realize all or part of the network element functions. The method includes: the first network element sends a registration request to a network storage function network element; wherein the first network element is used for CAG information, and the registration request includes a first network function configuration file, and the first network function configuration file includes identification information of the first network element, and also includes at least one of the first information and the second information, the first information indicates the CAG information managed by the first network element, and the second information indicates the service area managed by the first network element; the first network element receives a registration response from the network storage function network element.

[0027] In one possible design, the first network function configuration file also includes third information, and the third information indicates the terminal device identifier managed by the first network element.

[0028] In one possible design, the first network element also receives at least one CAG information from the second network element; the first network element stores at least one CAG information.

[0029] In one possible design, the first network element can also receive at least one terminal device identifier from the second network element, and the at least one terminal device identifier is used to identify the terminal device corresponding to at least one CAG information; the first network element sends at least one terminal device identifier to the network storage function network element.

[0030] In a third aspect, a communication method is provided, which is applied to a second network element. Unless otherwise specified, the "network element" in this application can refer to the network element itself, a component in the network element (for example, a processor, a chip, or a chip system), or a logical module or software that can implement all or part of the network element functions. The method includes: the second network element sends a service discovery request to a network storage function network element, the service discovery request including at least one CAG information and / or at least one service area identifier; and the second network element receives a service discovery response from the network storage function network element.

[0031] In one possible design, the service discovery response includes a first network function configuration file, the first network function configuration file includes identification information of the first network element, and at least one of first information and second information, the first information indicates CAG information managed by the first network element, and the second information indicates a service area managed by the first network element.

[0032] The service discovery request includes at least one CAG information, and at least one CAG information belongs to the CAG information indicated by the first information; and / or the service discovery request includes at least one service area identifier, and the service area indicated by at least one service area identifier belongs to the service area indicated by the second information.

[0033] In one possible design, the first network function configuration file also includes third information, and the third information indicates the terminal device identifier managed by the first network element.

[0034] In one possible design, the service discovery request also includes at least one terminal device identifier, and the at least one terminal device identifier belongs to the terminal device identifier indicated by the third information.

[0035] In one possible design, the first network function configuration file also includes at least one terminal device identifier.

[0036] In one possible design, the service discovery request also includes a first terminal device identifier, and the first terminal device identifier is stored in the first network function configuration file.

[0037] In one possible design, the service discovery response indicates that the service discovery failed, and the service discovery response includes a reason value, where the reason value indicates a reason for the service discovery failure;

[0038] In which, the service discovery request includes at least one CAG information, and the at least one CAG information does not belong to the CAG information corresponding to any network function configuration file stored in the network storage function network element; and / or, the service discovery request includes at least one service area identifier, and the service area indicated by the at least one service area identifier does not belong to the service area corresponding to any network function configuration file stored in the network storage function network element.

[0039] In one possible design, the service discovery request includes at least one service area identifier. The at least one service area identifier may come from a terminal device, for example, the terminal device reports the at least one service area identifier in a registration request. In this way, the second network element can obtain the at least one service area identifier and discover network elements based on the at least one service area identifier.

[0040] In a fourth aspect, a communication method is provided, which is applied to a network storage function network element. Unless otherwise specified, the "network element" in this application can refer to the network element itself, or a component in the network element (for example, a processor, a chip, or a chip system, etc.), or a logical module or software that can implement all or part of the network element function. The method includes: the network storage function network element receives a service discovery request from a second network element, the service discovery request including at least one CAG information and / or at least one service area identifier; and the network storage function network element sends a service discovery response to the second network element.

[0041] In a fifth aspect, a communication device is provided, which includes a module, unit or means for executing the method described in the first aspect or any possible design of the first aspect.

[0042] Exemplarily, the device may include:

[0043] a transceiver module configured to receive a registration request from a first network element; wherein the first network element is configured to store CAG information, the registration request including a first network function configuration file, the first network function configuration file including identification information of the first network element and at least one of first information and second information, the first information indicating CAG information managed by the first network element, and the second information indicating a service area managed by the first network element;

[0044] A processing module, configured to save a first network function configuration file;

[0045] The transceiver module is further configured to send a registration response to the first network element.

[0046] In a sixth aspect, a communication device is provided, which includes a module, unit or means for executing the method described in the second aspect or any possible design of the second aspect.

[0047] Exemplarily, the device may include:

[0048] A transceiver module is used to send a registration request to a network storage function network element; wherein the first network element is used for CAG information, the registration request includes a first network function configuration file, the first network function configuration file includes identification information of the first network element, and also includes at least one of the first information and the second information, the first information indicates the CAG information managed by the first network element, and the second information indicates the service area managed by the first network element; and receive a registration response from the network storage function network element.

[0049] In a seventh aspect, a communication device is provided, which includes a module, unit or means for executing the method described in the third aspect or any possible design of the third aspect.

[0050] Exemplarily, the device may include:

[0051] The transceiver module is used to send a service discovery request to the network storage function network element, where the service discovery request includes at least one CAG information and / or at least one service area identifier; and receive a service discovery response from the network storage function network element.

[0052] In an eighth aspect, a communication device is provided, which includes a module, unit or means for executing the method described in the fourth aspect or any possible design of the fourth aspect.

[0053] Exemplarily, the device may include:

[0054] The transceiver module is configured to receive a service discovery request from a second network element, where the service discovery request includes at least one CAG information and / or at least one service area identifier; and send a service discovery response to the second network element.

[0055] In a ninth aspect, a communication device is provided, comprising at least one processor; and a communication interface communicatively connected to the at least one processor; the at least one processor executes instructions stored in a memory, thereby causing the method described in the first aspect or any possible design of the first aspect to be executed, or causing the method described in the second aspect or any possible design of the second aspect to be executed, or causing the method described in the third aspect or any possible design of the third aspect to be executed, or causing the method described in the fourth aspect or any possible design of the fourth aspect to be executed.

[0056] In the tenth aspect, a computer-readable storage medium is provided, wherein the storage medium stores a computer program or instructions. When the computer program or instructions are executed, the method described in the first aspect or any possible design of the first aspect is executed, or the method described in the second aspect or any possible design of the second aspect is executed, or the method described in the third aspect or any possible design of the third aspect is executed, or the method described in the fourth aspect or any possible design of the fourth aspect is executed.

[0057] In the eleventh aspect, a computer program product is provided, comprising instructions that, when run on a computer, cause the method described in the first aspect or any possible design of the first aspect to be executed, or the method described in the second aspect or any possible design of the second aspect to be executed, or the method described in the third aspect or any possible design of the third aspect to be executed, or the method described in the fourth aspect or any possible design of the fourth aspect to be executed.

[0058] In the twelfth aspect, a communication system is provided, comprising a communication device described in at least one of the above-mentioned aspects from the fifth to the eighth aspects.

[0059] For the specific designs and beneficial effects of the second to twelfth aspects mentioned above, reference can be made to the corresponding designs and beneficial effects in the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0060] Figure 1 is an architecture diagram of a home gNB (HgNB);

[0061] FIG2 is a schematic diagram of the application function (AF) provisioning process;

[0062] FIG3 is a schematic diagram of the registration process of a visited user equipment (UE);

[0063] Figure 4 is an example diagram of the network element registration process;

[0064] FIG5 is an example diagram of a network element discovery and selection process;

[0065] FIG6 is a network architecture of a communication system applicable to an embodiment of the present application;

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

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

[0068] Figures 9A to 9B, 10A to 10B, and 11A to 11B are example diagrams of several specific network element selection processes provided in embodiments of the present application;

[0069] FIG12 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0070] FIG13 is a schematic structural diagram of another communication device provided in an embodiment of the present application;

[0071] FIG14 is a schematic diagram of the structure of a chip provided in an embodiment of the present application. DETAILED DESCRIPTION

[0072] The following first introduces the concepts of some technical terms involved in the embodiments of this application:

[0073] 1) The multiple involved in the embodiments of the present application refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent three situations: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. In addition, it should be understood that although the terms first, second, etc. may be used to describe each object in the embodiments of the present invention, these objects should not be limited to these terms. These terms are only used to distinguish each object from each other.

[0074] The terms "including" and "having" and any variations thereof mentioned in the description of the embodiments of the present application are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include other steps or units that are not listed, or may optionally include other steps or units that are inherent to these processes, methods, products or devices. It should be noted that in the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or design schemes. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a concrete way.

[0075] 2) Home small base station (home gNB, HgNB).

[0076] Base stations (such as next-generation NodeBs (gNBs)) are deployed in some areas with poor coverage, such as indoor areas. Users can deploy HgNBs to increase signal coverage in indoor areas. The architecture of HgNBs in the fifth-generation (5G) communication system is the same as that of ordinary base stations. In addition, HgNB gateways (GWs) can be deployed in the network. As shown in Figure 1, which is a diagram of the HgNB architecture, the HgNB GW is located between the HgNB and the access and mobility management function (AMF). From the perspective of the HgNB, the HgNB GW is equivalent to the AMF, and from the perspective of the AMF, the HgNB GW is equivalent to the HgNB. In order to avoid too many HgNBs connected to the AMF, the HgNB GW can be used as a convergence point for management.

[0077] It can be understood that HgNB is a type of Femto base station.

[0078] 3) Closed access group (CAG).

[0079] In the non-public network (NPN) topic, the CAG mechanism is introduced to restrict user equipment (UE) from accessing the public network integrated-non-public network (PNI-NPN) of the non-standalone network. The network can configure CAG information (such as CAG identifier (ID)) to the radio access network (RAN). The RAN will broadcast the CAG ID in the CAG cell. The UE will save the CAG information list (information list), which contains the UE's allowed CAG ID (i.e., the CAG ID that the UE can use to access the network). When the UE receives the RAN broadcast, if the CAG ID broadcast by the RAN is the same as the CAG ID in the CAG information list saved by the UE, the UE can select the cell for access. It can be understood that the non-public network of the non-standalone network can also be called a non-standalone private network.

[0080] In HgNB, since UE access also needs to be restricted, this mechanism can be introduced. A corresponding CAG ID can also be set for the HgNB. Correspondingly, the host UE's subscription data also contains corresponding CAG information. The host UE refers to the UE corresponding to the owner of the HgNB. For example, when a user purchases an HgNB, the operator can configure a CAG ID for the HgNB and update the corresponding CAG information in the host UE's subscription data. When the user deploys the HgNB in ​​their home, the host UE can select the HgNB for access because it has CAG information in its subscription data.

[0081] For HgNB cells, there are three modes to choose from: Close, Open, and Hybrid. When the HgNB is in Close mode, UE access is restricted, and UE access is only allowed if the UE's subscription data contains a CAG ID. When the HgNB is in Open mode, any UE is allowed access. At this time, the HgNB does not broadcast the CAG ID. The UE considers the HgNB cell to be the same as a normal cell and any UE can access it. When the HgNB is in Hybrid mode, the HgNB cell broadcasts the CAG ID. If the UE's subscription data contains the CAG ID, the UE can access the CAG cell and use the services associated with the CAG. If the UE's subscription data does not contain the CAG ID, the UE can access the normal cell, but the UE cannot use the services associated with the CAG.

[0082] 4) CAG management function (CMF).

[0083] In the Femto topic, a provisioning mechanism is introduced, that is, when a user deploys Femto (such as HgNB), the user, as the CAG owner, can dynamically authorize other UEs (which can be called temporary UEs or visitor UEs) to access Femto, so the network needs to save the CAG information corresponding to the temporary UE. Since the home network of the temporary UE may be different from the network where Femto is deployed, the CAG information cannot be directly saved in the unified data management (UDM) network element of the home network. Therefore, CMF is introduced. CMF is deployed in the same network as Femto to save and manage CAG information. CMF will receive and save the CAG information in the AF provisioning process. In the UE registration process, AMF can request the UE's allowed CAG information from CMF.

[0084] It is understandable that CMF is just an exemplary name and can actually be named by other names.

[0085] The above describes some of the concepts involved in the embodiments of the present application. The following describes the technical features involved in the embodiments of the present application:

[0086] 1) AF provisioning process.

[0087] FIG2 is a schematic diagram of the AF provisioning process, which includes the following steps:

[0088] S201. A connection is established between the UE (CAG owner) and the AF / application service (AS). CAG information, such as the CAG ID, is sent to the AS. In addition, the generic public subscription identifier (GPSI) corresponding to the UE that is allowed to access the CAG cell corresponding to the CAG ID can also be sent. For example, a session is established between the UE and the AS, and the CAG ID and GPSI are sent to the AS via the application layer. The AF can share the received information with the AF. It is understood that the AS and AF can be set up independently or together without limitation.

[0089] S202. The AF sends an external parameter configuration request (eg, Nnef_PrameterProvision_Creat / Update request) to the NEF. The request includes the CAG ID and GPSI received in S201.

[0090] S203. Optionally, the NEF may authorize the AF to determine whether the AF is allowed to update the corresponding parameters. If the authorization is passed, the NEF sends an external parameter configuration request (for example, Nnef_PrameterProvision_Creat / Update request) to the CMF. The request includes the CAG ID and GPSI received in S202.

[0091] S204. After saving the CAG ID and GPSI, the CMF sends an external parameter configuration response (e.g., Nnef_PrameterProvision_Creat / Update response) to the NEF, indicating that the CMF has successfully saved the CAG ID.

[0092] 205. The NEF sends an external parameter configuration response (e.g., Nnef_PrameterProvision_Create / Update response) to the AF, indicating that the CMF successfully saved the CAG ID.

[0093] Of course, the above steps are only examples, and the actual AF provisioning process may also include other steps.

[0094] It can be understood that before step S203 (ie, the NEF sends the CAG ID to the CMF), the NEF needs to first perform a network element discovery and selection process to determine to which CMF the CAG ID is sent.

[0095] 2)UE registration process.

[0096] 3 is a schematic diagram of the UE registration process, which includes the following steps:

[0097] S301. UE completes cell selection.

[0098] S302: The UE sends a registration request to the RAN. Optionally, if the UE accesses as a visited UE, the registration request carries indication information, where the indication information indicates that the accessed UE is a visited UE.

[0099] S303. RAN (such as HgNB) selects AMF.

[0100] S304. The RAN sends a registration request to the selected AMF. Optionally, if the RAN supports CAG cells, the registration request additionally carries all CAG IDs broadcast by the base station.

[0101] S305. AMF selects AUSF to execute the security authentication process.

[0102] S306. AUSF, AMF, UDM, visited UE, etc. perform the security authentication process.

[0103] S307. AMF obtains access and mobility subscription data from UDM (e.g., through Nudm_SDM_Get). If GPSI exists in the access and mobility subscription data of the visited UE, UDM provides GPSI to AMF in the access and mobility subscription data.

[0104] S308. Optionally, if the UE carries indication information in the registration request, the AMF decides to perform access control on the CAG cell through the CMF based on the indication in the registration request. The AMF may retrieve the CAG ID stored by the CMF to determine whether to allow the UE to access the CAG cell. For example, the AMF may provide the CMF with the GPSI of the visited UE, and the CMF provides the AMF with the CAG ID associated with the GPSI.

[0105] It is understood that if the CAG ID provided by the RAN is not in the UE's allowed CAG list, the AMF may reject the registration request. If the CAG ID is in the UE's allowed CAG list, the AMF may accept the registration request.

[0106] S309. The AMF sends an N2 message to the RAN. The N2 message includes a NAS message that the RAN needs to forward to the UE. The NAS message includes a registration accept message (N2 message) sent by the AMF to the UE.

[0107] S310. The RAN forwards the registration accept message (NAS message) sent by the AMF to the UE.

[0108] Of course, the above steps are only examples, and the actual registration process may also include other steps. For example, when a visited UE initiates registration due to a change of AMF, it is also necessary to perform a deregistration process on the old AMF.

[0109] It can be understood that in step S308, before the AMF obtains the CAG ID from the CMF, it needs to first perform the network element discovery and selection process to determine which CMF to obtain the CAG ID from.

[0110] 3) Network element registration process.

[0111] Before being discovered and selected, a network element needs to be registered with a network repository function (NRF) network element.

[0112] Figure 4 shows an example of the NE registration process, which includes the following steps:

[0113] S401. When the network element to be registered (such as CMF) is powered on, it sends a registration request to the NRF. The request includes the network function profile (NF profile) to be registered. The NF profile is used to discover and select the network element. The NF profile includes basic information such as the network element type (called network function type (NF type)), network element instance identifier (NF instance ID), network element fully qualified domain name (FQDN) or IP address, name of supported network function service (if applicable) and public land mobile network (PLMN) ID.

[0114] It can be understood that different NF profiles can contain different information depending on the network element. For example, NWDAF can register its supported analytics ID with NRF, and SMF can register its supported slices / data network names (DNN) with NRF.

[0115] S402: After receiving the registration request, the NRF saves the NF profile in the registration request.

[0116] S403. The NRF sends a registration response to the NF, indicating that the registration is completed.

[0117] It can be understood that the parameters in the NF profile registered by the network element to the NRF can be used for discovery and selection of the network element.

[0118] 4) Network element discovery and selection process.

[0119] Figure 5 shows an example of the NE discovery and selection process, which includes the following steps:

[0120] S501. When a network element (such as the NEF in Figure 2 or the AMF in Figure 3) needs to request a service (such as the CMF service), it can send a service discovery request to the NRF. The service discovery request carries parameters such as the network element type and service type.

[0121] S502. After receiving the service discovery request, the NRF authenticates the service discovery request to confirm whether the network element sending the service discovery request can request to call the network element service indicated in the service discovery request (such as the network element service indicated by parameters such as network element type and service type);

[0122] S503. After NRF authentication is completed, if the network element that sent the service discovery request can request to call the network element service, the NF profile (such as the CMF NF profile) requested from the network element that sent the service discovery request is sent. It is understood that the number of NF profiles sent by the NRF can be one or more, that is, the network element discovery result may be one or more network elements.

[0123] After receiving the NF profile, the network element selects the network element to be used based on the received NF profile.

[0124] The above process shows that when a network element discovers another network element, it obtains the NF profile from the NRF based on basic information such as the network element type and service type.

[0125] In actual network deployment, multiple network elements of the same network element type or service type can be deployed at the same time. For example, a first CMF and a second CMF are deployed in the network, and both CMFs have the function of managing and storing CAG information. If the network element is discovered according to the method shown in Figure 5, there will be problems with inaccurate network element discovery and selection, because different CMFs cannot be distinguished based on basic information such as network element type and service type. For example, in the AF provisioning process shown in Figure 2, the NEF selects the CMF that stores CAG information as the first CMF, while in the UE registration process shown in Figure 3, the AMF selects the CMF that obtains CAG information as the second CMF. The CMFs selected by the two network elements are inconsistent, resulting in the AMF being unable to obtain the UE's allowed CAG information from the second CMF, which causes the UE to fail to access the network.

[0126] In view of this, a technical solution of an embodiment of the present application is provided. When a network element (such as CMF) in the network used to store CAG information registers with the NRF, it will provide first information (indicating the CAG information managed by the network element) and / or second information (indicating the service area managed by the network element) and other information in the network function configuration file for discovery and selection of the network element. Different network elements of the same type can be distinguished based on the first information and / or the second information, which helps to improve the accuracy of network element discovery and selection, and thereby improve the success rate of terminal devices accessing the network.

[0127] The technical solutions of the embodiments of the present application can be applied to various communication systems, for example: fifth-generation (5G) communication systems, sixth-generation (6G) communication systems or other future evolution systems, or various other wireless communication systems using wireless access technologies, etc., can all adopt the technical solutions of the embodiments of the present application.

[0128] Referring to Figure 6, a network architecture diagram of a communication system applicable to an embodiment of the present application is shown. The network functions and entities included in the system mainly include: terminal equipment (UE), radio access network ((radio) access network, (R)AN) network element, user plane function (UPF) network element, data network (Data Network, DN), access and mobility management function (AMF) network element, session management function (SMF) network element, policy control function (PCF) network element, application function (AF) network element, unified data management (UDM) network element, network exposure function (NEF) network element, network storage function (NRF) network element, network slice selection function (NSSF) network element, authentication server function (AUSF) network element, CMF network element, etc.

[0129] Among them, the terminal equipment (UE) can also be called user equipment, terminal, mobile station, mobile terminal, etc. The terminal can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IOT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearable, smart transportation, smart city, etc. The terminal can be a mobile phone, tablet computer, computer with wireless transceiver function, wearable device, vehicle, drone, helicopter, airplane, ship, robot, robotic arm, smart home device, etc. The embodiments of this application do not limit the specific technology and specific device form adopted by the terminal.

[0130] A radio access network ((radio) access network, (R)AN) network element may also be referred to as an access network device, a wireless access network device, an access network, etc. Specific implementations may include a base station (Base Station), an evolved NodeB (eNodeB), a transmission reception point (TRP), a next generation NodeB (gNB) in a fifth generation mobile communication system, a next generation base station in a sixth generation mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system, etc.; it may also be a module or unit that performs part of the functions of a base station, for example, a centralized unit (CU) or a distributed unit (DU). A radio access network device may be a macro base station, a micro base station, an indoor station, a relay node, a donor node, etc. The embodiments of the present application do not limit the specific technology and specific device form adopted by the radio access network device.

[0131] In one possible scenario, multiple RAN nodes collaborate to assist the terminal in achieving wireless access, and different RAN nodes respectively implement part of the functions of the base station. For example, the RAN node can be a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The CU and DU can be set separately, or they can be included in the same network element, such as a baseband unit (BBU). The RU can be included in a radio frequency device or radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).

[0132] In different systems, CU (or CU-CP and CU-UP), DU or RU may also have different names, but those skilled in the art can understand their meanings. For example, in an open radio access network (O-RAN or open RAN or ORAN) system, CU may also be called O-CU (open CU), DU may also be called O-DU, CU-CP may also be called O-CU-CP, CU-UP may also be called O-CU-UP, and RU may also be called O-RU. For the convenience of description, this application takes CU, CU-CP, CU-UP, DU and RU as examples for description. Any unit of CU (or CU-CP, CU-UP), DU and RU in this application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0133] Data Network (DN): A data network that provides business services to users. Typically, the client is located on a terminal device, and the server is located on the data network. A data network can be a private network, such as a local area network (LAN), an external network not controlled by the operator, such as the Internet, or a proprietary network jointly deployed by operators, such as the network that provides Internet Protocol (IP) Multimedia Core Network Subsystem (IMS) services.

[0134] The following is a brief introduction to the functions of network elements in the core network:

[0135] 1. SMF network element: responsible for user plane network element selection, user plane network element redirection, Internet Protocol (IP) address allocation, bearer establishment, modification and release, and quality of service (QoS) control.

[0136] 2. AMF network element: A core network element, mainly responsible for signaling processing, such as access control, mobility management, attachment and detachment, and gateway selection. When the AMF network element provides services for a session in a terminal device, it will provide control plane storage resources for the session to store the session identifier and the SMF network element identifier associated with the session identifier.

[0137] 3. PCF network element: responsible for policy control decisions, providing policy rules for control plane functions, and flow-based billing control functions.

[0138] 4. UDM network element: Mainly responsible for UE subscription data management, including the storage and management of UE identification, UE access authorization, etc.

[0139] 5. AF network element: It mainly supports interaction with the 3rd Generation Partnership Project (3GPP) core network to provide services, such as influencing data routing decisions, policy control functions, or providing some third-party services to the network side.

[0140] 6. UPF network element: Responsible for forwarding and receiving user data in terminal devices. It can receive user data from the data network and transmit it to the terminal device through the access network equipment. The UPF network element can also receive user data from the terminal device through the access network equipment and forward it to the data network. The transmission resources and scheduling functions provided by the UPF network element to the terminal device are managed and controlled by the SMF network element.

[0141] 7. NEF network element: mainly supports the secure interaction between 3GPP network and third-party applications.

[0142] 8. NRF network element: used to store description information of network function entities and the services they provide, and support functions such as service discovery and network element entity discovery.

[0143] 9. NSSF network element: Mainly responsible for network slice selection, and determines the network slice instance that the UE is allowed to access based on the UE's slice selection auxiliary information, contract information, etc.

[0144] 10. AUSF network element: supports 3GPP and non-3GPP access authentication.

[0145] 11. CMF network element: Responsible for managing and storing CAG information. For example, the CMF receives and stores CAG information during the AF provisioning process. During the UE registration process, the AMF can request the CMF for the UE's permitted CAG information. The CMF can be deployed independently or integrated into other network elements (such as the UDM) without restriction.

[0146] It is understandable that in actual applications, the above network architecture may also include other network elements, and this application does not limit this.

[0147] It should be noted that the names of the various network elements in this application are merely examples, and this application does not exclude the possibility that the network elements may be renamed in the future, or that the functions of the network elements may be merged. As technology evolves, any device or network element that can implement the functions of the aforementioned network elements falls within the scope of protection of this application.

[0148] It should be understood that the interface names between the various network elements in Figure 6 are only examples. In specific implementations, the interface names may be other names, and this application does not specifically limit this. In addition, the names of the messages (or signaling) transmitted between the various network elements are also only examples and do not constitute any limitation on the functions of the messages themselves.

[0149] For ease of description, in this document, each network element may be represented by its corresponding English abbreviation, for example, "AF" represents an application function network element, "SMF" represents a session management function network element, and so on.

[0150] 7 is a flowchart of a communication method provided in an embodiment of the present application. The method can be applied to the communication system shown in FIG6 . The method includes S701 to S703 .

[0151] S701: The first network element sends a registration request, and the NRF receives the registration request.

[0152] The first network element is used to store CAG information. For example, the first network element can be the CMF described above, or can be a UDM, etc. For ease of description, the following description takes the first network element being a CMF as an example.

[0153] The CAG information may be any information that can indicate a CAG, including but not limited to a CAG identifier.

[0154] The registration request is used to request registration of the first network element with the NRF. After the first network element is registered with the NRF, it can be discovered and selected by other network elements. The registration request includes the network function profile (NF profile) of the first network element. The following description uses the first NF profile as an example.

[0155] The first NF profile includes identification information of the first network element. The identification information of the first network element can be any information that can identify the first network element, such as but not limited to NF instance ID, FQDN, or IP address.

[0156] The first NF profile also includes at least one of the first information and the second information. For example, the first NF profile includes the first information, or the first NF profile includes the second information, or the first NF profile includes the first information and the second information.

[0157] The first information indicates CAG information managed by the first network element. It should be understood that the CAG information managed by the first network element here refers to CAG information that the first network element can or is capable of managing. That is, after receiving this CAG information, the first network element can manage and store this CAG information. Whether the first network element stores this CAG information depends on whether the first network element has received this CAG information. In other words, the first network element does not necessarily store all CAG information that it can manage.

[0158] In one possible implementation, the first information may include at least one CAG information range, and the first network element manages CAG information within the at least one CAG information range. For example, the first information includes a CAG ID range, and the first network element manages CAG IDs within the CAG ID range.

[0159] In another possible implementation, the first information may include at least one CAG information set, and the first network element manages the CAG information in the at least one CAG information set. For example, the first information includes a CAG ID set, the set includes at least one CAG ID, and the first network element manages the at least one CAG ID.

[0160] The second information indicates the service area managed by the first network element. It is understood that the service area managed by the first network element refers to the location area where the access network devices (such as HgNB) managed by the first network element are located. Accordingly, the first network element can manage and store CAG information broadcast by the access network devices within the service area managed by the first network element.

[0161] In one possible implementation, the first information may include a service area range. For example, the first information may include a tracking area identity (TAI) range. Similarly, the service area range may be a TAI set or a TAI value range.

[0162] It can be understood that the first information and / or the second information in the first NF profile in the embodiment of the present application can be used to discover and select the first network element.

[0163] Optionally, the first NF profile also includes one or more information such as the NF type of the first network element, the NF instance ID of the first network element, the FQDN or IP address of the first network element, the name of the network function service supported by the first network element and the PLMN ID, which can be used for discovering and selecting the first network element.

[0164] S702: The NRF saves the first NF profile.

[0165] S703: The NRF sends a registration response, and the first network element receives the registration response.

[0166] For example, the registration response indicates that the registration was successful.

[0167] In the above-mentioned S701-S703 scheme, when the first network element registers with the NRF, it additionally provides first information and / or second information for discovery and selection of the first network element. The first information and / or second information can distinguish the first network element from other network elements of the same type, thereby helping to improve the accuracy and efficiency of network element discovery and selection.

[0168] In one possible design, the first NF profile may further include third information, where the third information indicates the terminal device identifier (e.g., GPSI) managed by the first network element. Accordingly, the first network element may manage and store the allowed CAG information of the terminal device indicated by the terminal device identifier managed by the first network element.

[0169] In one possible implementation, the third information may further include at least one terminal device identification range, and the first network element manages terminal device identifications within the at least one terminal device identification range. For example, the first information includes a GPSI range, and the first network element manages terminal device identifications within the GPSI range.

[0170] In another possible implementation, the first information may include at least one terminal device identifier set, and the first network element manages the terminal device identifiers in the at least one terminal device identifier set. For example, the first information includes a terminal device identifier set, the set including at least one terminal device identifier, and the first network element manages the at least one terminal device identifier.

[0171] In this way, different network elements that manage the same CAG information and / or the same service area can be distinguished in combination with the third information, which can further help improve the efficiency and accuracy of network element discovery and selection.

[0172] In one possible design, the NRF may also update the stored NF profile, and the updated information may be used for discovery and selection of the first network element. For example, after the first network element stores the CAG information, the NRF may also receive at least one terminal device identifier (such as at least one GPSI) from the first network element, where the at least one terminal device identifier is used to identify the terminal device corresponding to the CAG information stored in the first network element; the NRF may update the at least one terminal device identifier to the first NF profile, and the at least one terminal device identifier may be used for discovery and selection of the first network element.

[0173] In this way, different network elements that manage the same CAG information and / or the same service area can be distinguished in combination with the terminal device identification, which can further help improve the efficiency and accuracy of network element discovery and selection.

[0174] The following describes the process of discovering and selecting network elements:

[0175] 8 , which shows a communication method provided in an embodiment of the present application. The method can be applied to the communication system shown in FIG6 , and includes S801 to S802:

[0176] S801. The second network element sends a service discovery request to the NRF, and the NRF receives the service discovery request.

[0177] The service discovery request includes at least one CAG information and / or at least one service area identifier.

[0178] The CAG information may be any information that can indicate a CAG, including but not limited to a CAG identifier.

[0179] The service area identifier is used to indicate the service area (the service area may refer to a geographical location), for example, a TAI. At least one CAG information may be reported by a terminal device (such as a host UE) or an access network element (such as an HgNB to which a visited UE belongs) and forwarded to a second network element via other network elements (such as an AF, etc.). At least one service area identifier may be reported by a terminal device (such as a host UE or a visited UE) and forwarded to a second network element via other network elements (such as an HgNB, AF, etc.).

[0180] S802. The NRF sends a service discovery response to the second network element, and the second network element receives the service discovery response.

[0181] Exemplarily, after receiving the service discovery request, the NRF traverses the stored NF profiles to determine whether there is an NF profile that matches the at least one CAG information and / or the at least one service area identifier.

[0182] If so, the NRF sends a service discovery response to the second network element, and the service discovery response carries an NF profile that matches the at least one CAG information and / or the at least one service area identifier. Taking the case where at least one CAG information and / or the at least one service area identifier matches the first NF profile stored by the NRF as an example: at least one CAG information belongs to the CAG information indicated by the first information; and / or, the service discovery request includes at least one service area identifier, and the service area indicated by the at least one service area identifier belongs to the service area indicated by the second information. The service discovery response includes the first NF profile.

[0183] If not, the NRF returns a service discovery response indicating service discovery failure / rejection of service discovery, that is, the service discovery response indicates service discovery failure / service discovery is rejected. The reasons for service discovery failure / service discovery rejection are, for example: at least one CAG information does not belong to the CAG information corresponding to any NF profile saved in the NRF; and / or, the service discovery request includes at least one service area identifier, and the service area indicated by at least one service area identifier does not belong to the service area corresponding to any NF profile saved in the NRF. Among them, the CAG information corresponding to the NF profile refers to the CAG information indicated by the information saved in the NF profile, for example, the CAG information corresponding to the first NF profile is the CAG information indicated by the first information in the first NF profile. The service area corresponding to the NF profile refers to the service area indicated by the information saved in the NF profile, for example, the service area corresponding to the first NF profile is the service area indicated by the second information in the first NF profile. Optionally, the service discovery response may include a reason value, and the reason value indicates the reason for the service discovery failure (service discovery rejection).

[0184] It is understandable that the NF profile of any network element stored by the NRF may include multiple pieces of information for discovering and selecting the network element, but when actually executing the process of discovering the network element, only part of the information may be used to discover the network element, or all of the information may be used to discover the network element, without limitation. For example, when the first NF profile includes the first information and the second information, when the second network element discovers the first network element to the NRF, it may only carry at least one CAG information in the service discovery request (determining the first network element by matching the first information and at least one CAG identifier), or may only carry at least one service area identifier (determining the first network element by matching the second information and at least one service area identifier), or may simultaneously carry at least one CAG information and at least one service area identifier (determining the first network element by matching the first information and at least one CAG identifier, and matching the second information and at least one service area identifier).

[0185] In the above solution, when the second network element sends a service discovery request to the NRF, it additionally provides at least one CAG information and / or at least one service area identifier, so that the NRF can accurately and quickly match the NF profile based on the at least one CAG information and / or at least one service area identifier, thereby improving the accuracy and efficiency of network element discovery and selection.

[0186] In one possible design, in addition to the first information and the second information, the second network element may also discover and select a network element based on more information, such as NF type, name of network function service, PLMN ID, etc.

[0187] Taking into account the situation that different network elements may manage the same CAG information and / or manage the same service area, in a specific example, the first NF profile also includes third information, and the third information indicates the terminal device identifier managed by the first network element. In this way, the second network element can also discover the first network element based on the third information. For example, the service discovery request also includes at least one terminal device identifier, and the at least one terminal device identifier matches the first NF profile, for example, the at least one terminal device identifier belongs to the terminal device identifier indicated by the third information. It can be understood that the third information can be used alone or in combination with the first information and / or the second information mentioned above.

[0188] Taking into account the situation that different network elements may manage the same CAG information and / or manage the same service area, in another specific example, after the first network element saves at least one CAG information, it can send at least one terminal device identifier to the NRF, and the NRF receives the at least one terminal device identifier, which is used to identify the terminal device corresponding to the CAG information saved in the first network element; the NRF updates the at least one terminal device identifier to the first NF profile. In this way, the second network element can also discover the first network element based on the at least one terminal device identifier. For example, the service discovery request also includes the first terminal device identifier, and the first terminal device identifier matches the first NF profile, for example, the first terminal device identifier is saved in the first NF profile. It can be understood that at least one terminal device identifier can be used alone or in combination with the first information and / or second information mentioned above.

[0189] It can be understood that the method shown in FIG8 is applicable to a variety of scenarios.

[0190] In different scenarios, the second network element may be different.

[0191] Taking the AF provisioning scenario as an example: the second network element mentioned above can be NEF, and the NEF can use the method of S801 to S802 to discover and select CMF, and then save the received CAG information to the selected CMF.

[0192] Taking the UE registration scenario as an example: the second network element can be AMF, and the AMF can use the method of S801 to S802 to discover and select CMF, and then obtain CAG information from the selected CMF for controlling the access of the terminal device.

[0193] In different scenarios, the information content carried in the service discovery request can be the same or different.

[0194] Take the AF provisioning scenario as an example: the second network element (such as NEF) sends a first service discovery request to the NRF, and the NRF receives the first service discovery request. The first service discovery request carries at least one CAG information, and the at least one CAG information is the CAG information of the CAG cell that the terminal device is allowed to access (for example, the allowed CAG information of the visited UE, reported by the host UE); the NRF sends a first service discovery response to the second network element, and the second service discovery response includes the first NF profile. The first CAG information belongs to the CAG information indicated by the first information.

[0195] Take the UE registration scenario as an example (in order to distinguish it from the second network element in the AF provisioning scenario, the second network element in the UE registration scenario is referred to as the third network element): the third network element (such as AMF) sends a second service discovery request to the NRF, and the NRF receives the second service discovery request. The second service discovery request carries the first CAG information, and the first CAG information is the CAG information of the CAG cell accessed by the terminal device; the NRF sends a second service discovery response to the third network element, and the second service discovery response includes the first NF profile. The first CAG information belongs to the CAG information indicated by the first information.

[0196] It is understood that the NF profile stored in the NRF in the method embodiment shown in FIG8 can be implemented by the method shown in FIG7 or by other methods (for example, pre-configuring the CMF NF profile in the NRF). In other words, the method shown in FIG8 can be implemented independently of the method shown in FIG7.

[0197] The various implementations of this application can be implemented separately or in combination with each other without limitation.

[0198] The following are some specific examples combining AF provisioning scenarios and UE registration scenarios:

[0199] Example 1: When registering with the CMF, the CAG ID range managed by the CMF is saved in the NRF, and the NEF / AMF selects the CMF based on the CAG ID.

[0200] 9A is a schematic diagram of a process of an NEF discovering a CMF according to an embodiment of the present application, which includes the following steps:

[0201] S901A: The CMF sends a registration request to the NRF, which carries the CAG ID range managed by the CMF (corresponding to the first information above). This step corresponds to S701 above.

[0202] In one possible implementation, different CMFs manage different CAG ID ranges, meaning only one CMF can be selected based on the CAG ID. In another possible implementation, different CMFs can manage the same CAG ID range, meaning multiple CMFs can be selected based on the CAG ID. In this case, after saving the CAG information, the CMF can update the GPSI received from the NEF. For details, see S908A to S909A.

[0203] S902A: The NRF returns a registration response to the CMF. This step corresponds to S703 above.

[0204] S903A. The AF sends an external parameter configuration request to the NEF, which carries the CAG ID to be saved (such as the allowed CAG ID of the temporary UE). Optionally, the external parameter configuration request also carries the GPSI of the UE corresponding to the CAG ID to be saved.

[0205] This step can refer to the previous S201.

[0206] S904A: NEF sends a service discovery request to NRF, and NRF receives the service discovery request, which carries the CAG ID to be saved. This step corresponds to S801 above.

[0207] NRF can determine the NF profile (or CMF) based on the CAG ID carried in the service discovery request.

[0208] S905A: The NRF sends a service discovery response, and the NEF receives the service discovery response. The response carries the NF profile determined by the NRF, and the identification information in the NF profile indicates the CMF. This step may correspond to S802 above.

[0209] S906A. The NEF selects a CMF according to the NF profile and sends an external parameter configuration request to the selected CMF. The request carries the CAG ID to be saved.

[0210] It can be understood that if there is only one CMF indicated by the service discovery response, the unique CMF is selected and the external parameter configuration request is sent to the CMF; if there are multiple CMFs indicated by the service discovery response, one CMF is selected from them and the external parameter configuration request is sent to it.

[0211] S907A: After saving the CAG ID, the CMF returns an external parameter configuration response to the NEF. The NEF returns the external parameter configuration response to the AF. The external parameter configuration response indicates that the CAG ID is saved successfully.

[0212] Optionally, in S908A, the CMF sends the GPSI of the UE corresponding to the CAG ID to be saved (e.g., the GPSI carried in the external parameter configuration request in S903A) received from the NEF to the NRF. The NRF updates the NF profile corresponding to the CMF with this GPSI. Subsequently, when the NRF discovers the CMF, it can determine the unique CMF based on the CAG ID and GPSI.

[0213] Optionally, S909A, NRF returns an update response to CMF, indicating that the NF profile has been updated.

[0214] Of course, the above steps are only examples, and the actual AF provisioning process may include more or fewer steps.

[0215] 9B , which is a schematic diagram of a process for an AMF to discover a CMF according to an embodiment of the present application, includes the following steps:

[0216] S901B. The UE (such as a visited UE) sends a registration request to the access network device (such as an HgNB), and the HgNB receives the registration request.

[0217] For example, the visited UE receives the broadcast information sent by the HgNB, determines that the CAG ID in the broadcast information is the same as the CAG ID stored in the visited UE, and then sends a registration request to the HgNB.

[0218] S902B. HgNB sends a registration request to AMF. AMF receives the registration request, which carries the CAG ID corresponding to the HgNB (e.g., the CAG ID broadcast by the HgNB in ​​the CAG cell).

[0219] S903B. AMF selects AUSF to execute the security authentication process.

[0220] S904B. AMF sends a subscription data acquisition request to UDM to request the UE's subscription data.

[0221] S905B. UDM returns the UE's subscription data to AMF.

[0222] S906B: The AMF sends a service discovery request to the NRF to request the CMF. This step corresponds to S801 above.

[0223] In one possible implementation, each CMF manages a separate CAG ID. The AMF can then carry the CAG ID in the service discovery request, and the NRF can discover the unique CMF based on the CAG ID. In another possible implementation, corresponding to the method of updating the GPSI in the NF profile in S908A-S909A above, the AMF can carry the CAG ID and GPSI in the service discovery request, and the NRF can discover the unique CMF based on the CAG ID and GPSI.

[0224] S907B. NRF sends a service discovery response to AMF.

[0225] It is understood that if the NRF successfully selects the CMF (eg, matches the NF profile), the service discovery response may carry the NF profile corresponding to the selected CMF. This step may correspond to S802 above.

[0226] If NRF fails to select CMF (e.g., no NF profile is matched), the service discovery response indicates that the service discovery failed / the service discovery was rejected.

[0227] S908B. AMF obtains the UE's allowed CAG information (such as CAG ID) from CMF, and decides whether to authorize UE access based on the obtained CAG information.

[0228] S909B. Optionally, if the AMF in S908B cannot obtain the UE's allowed CAG information from the CMF, or if the selection of the CMF in S906B-S907B fails, the AMF may reject the UE's registration request and return a registration reject message to the UE.

[0229] Of course, the above steps are only some examples, and the actual UE registration process may also include more or fewer steps.

[0230] In the scheme given in Figure 9A above, the NEF selects the CMF for storing the CAG information based on the CAG ID. In the scheme given in Figure 9B above, the AMF selects the CMF for obtaining the CAG information based on the CAG ID. This allows the NEF and AMF to select the same CMF, thereby improving the accuracy of network element discovery and selection and improving the success rate of UE registration with the network.

[0231] Example 2: When registering with the CMF, the CAG ID range and GPSI range managed by the CMF are saved in the NRF. The NEF / AMF selects the CMF based on the CAG ID and GPSI.

[0232] 10A is a schematic diagram of a process of an NEF discovering a CMF according to an embodiment of the present application, which includes the following steps:

[0233] S1001A: The CMF sends a registration request to the NRF. The registration request carries the CAG ID range (corresponding to the first information above) and GPSI range (corresponding to the third information above) managed by the CMF. When different CMFs manage the same CAG ID, the GPSI ranges managed by different CMFs are different. This step corresponds to S701 above.

[0234] S1002A: The NRF returns a registration response to the CMF. This step corresponds to S703 above.

[0235] S1003A: The AF sends an external parameter configuration request to the NEF. The external parameter configuration request carries the CAG ID to be saved and the GPSI of the UE corresponding to the CAG ID.

[0236] This step can refer to the previous S201.

[0237] S1004A: NEF sends a service discovery request to NRF. NRF receives the service discovery request, which carries the CAG ID and GPSI received in S1003A. This step corresponds to S801 above.

[0238] NRF can determine a unique NF profile (or a unique CMF) based on the CAG ID and GPSI carried in the service discovery request.

[0239] S1005A: The NRF sends a service discovery response, and the NEF receives the service discovery response. The response carries the NF profile determined by the NRF, and the identification information in the NF profile indicates the CMF. This step may correspond to S802 above.

[0240] S1006A: NEF selects a CMF based on the NF profile and sends an external parameter configuration request to the selected CMF. The request carries the CAG ID and GPSI received in S1003A.

[0241] S1007A: After saving the CAG ID and GPSI received in S1003A, the CMF returns an external parameter configuration response to the NEF. The NEF returns an external parameter configuration response to the AF. The external parameter configuration response indicates that the CAG ID has been saved successfully.

[0242] Of course, the above steps are only examples, and the actual AF provisioning process may include more or fewer steps.

[0243] 10B is a schematic diagram of a process of discovering a CMF by an AMF according to an embodiment of the present application, including the following steps:

[0244] S1001B. The UE (such as a visited UE) sends a registration request to the access network device (such as an HgNB), and the HgNB receives the registration request.

[0245] For example, the visited UE receives the broadcast information sent by the HgNB, determines that the CAG ID in the broadcast information is the same as the CAG ID stored in the visited UE, and then sends a registration request to the HgNB.

[0246] S1002B. HgNB sends a registration request to AMF. AMF receives the registration request, which carries the CAG ID corresponding to the HgNB (e.g., the CAG ID broadcast by the HgNB in ​​the CAG cell).

[0247] S1003B. AMF selects AUSF to execute the security authentication process.

[0248] S1004B. AMF sends a subscription data acquisition request to UDM to request the UE's subscription data.

[0249] S1005B. UDM returns the UE's subscription data to AMF.

[0250] S1006B: The AMF sends a service discovery request to the NRF to request the CMF. This step corresponds to S801 above.

[0251] In one possible implementation, the AMF may carry the CAG ID and GPSI in the service discovery request, and the NRF may discover a unique CMF based on the CAG ID and GPSI.

[0252] S1007B: The NRF sends a service discovery response to the AMF. The service discovery response carries the NF profile corresponding to the selected CMF. This step corresponds to S802 above.

[0253] S1008B. AMF obtains the UE's allowed CAG information from CMF and decides whether to authorize UE access based on the obtained CAG information.

[0254] S1009B. Optionally, if the AMF cannot obtain the UE's allowed CAG information from the CMF in S1008B, the AMF may reject the UE's registration request and return a registration reject message to the UE.

[0255] Of course, the above steps are only some examples, and the actual UE registration process may also include more or fewer steps.

[0256] In the scheme given in Figure 10A above, the NEF selects the CMF for storing the CAG information based on the CAG ID and GPSI. In the scheme given in Figure 10B above, the AMF selects the CMF for obtaining the CAG information based on the CAG ID and GPSI. This allows the NEF and AMF to select the same CMF, thereby improving the accuracy of network element discovery and selection and improving the success rate of UE registration with the network.

[0257] Example 3: When registering with the CMF, the CMF-managed TAI is saved in the NRF. The NEF / AMF selects the CMF based on the TAI. The UE is required to report the TAI during the AF provisioning process.

[0258] 11A is a schematic diagram of a process of an NEF discovering a CMF according to an embodiment of the present application, which includes the following steps:

[0259] S1101A: The CMF sends a registration request to the NRF, which carries the TAI range managed by the CMF (corresponding to the second information mentioned above). This step may correspond to S701 above.

[0260] S1102A: The NRF returns a registration response to the CMF. This step corresponds to S702 above.

[0261] S1103A, the UE (such as the host UE) is connected to the AF, and the UE reports the CAG ID to be saved and the GPSI of the UE (such as the visited UE) corresponding to the CAG ID to be saved to the AF. In addition, during this process, the UE can also report the TAI, which is the TAI corresponding to the location area of ​​the RAN accessed by the UE.

[0262] S1104A: The AF sends an external parameter configuration request to the NEF. The external parameter configuration request carries the CAG ID and TAI received in S1103A.

[0263] S1105A: NEF sends a service discovery request to NRF. NRF receives the service discovery request, which carries the CAG ID and TAI received in S1104A. This step corresponds to S801 above.

[0264] NRF can determine the NF profile (or CMF) based on the TAI carried in the service discovery request.

[0265] S1106A: The NRF sends a service discovery response, and the NEF receives the service discovery response. The response carries the NF profile determined by the NRF, and the identification information in the NF profile indicates the CMF. This step may correspond to S802 above.

[0266] S1107A: NEF selects a CMF based on the NF profile and sends an external parameter configuration request to the selected CMF. The request carries the CAG ID and GPSI received in S1104A.

[0267] S1108A: After saving the CAG ID and GPSI received in S1103A, the CMF returns an external parameter configuration response to the NEF. The NEF returns an external parameter configuration response to the AF. The external parameter configuration response indicates that the CAG ID was saved successfully.

[0268] Of course, the above steps are only examples, and the actual AF provisioning process may include more or fewer steps.

[0269] 11B is a schematic diagram of a process for an AMF to discover a CMF according to an embodiment of the present application, including the following steps:

[0270] S1101B. The UE (such as a visited UE) sends a registration request to the access network device (such as an HgNB), and the HgNB receives the registration request.

[0271] For example, the visited UE receives the broadcast information sent by the HgNB, determines that the CAG ID in the broadcast information is the same as the CAG ID stored in the visited UE, and then sends a registration request to the HgNB.

[0272] S1102B. HgNB sends a registration request to AMF. AMF receives the registration request, which carries the CAG ID and TAI corresponding to the HgNB.

[0273] S1103B: The AMF sends a service discovery request to the NRF to request the CMF. This step corresponds to S801 above.

[0274] In one possible implementation, the AMF may carry the TAI received in S1102B in the service discovery request, and the NRF may discover the CMF based on the TAI.

[0275] It is understandable that in the actual registration process, there may be other steps between S1102B and S1103B (such as AMF selecting AUSF to perform security authentication, obtaining contract data, etc.), which will not be expanded here.

[0276] S1104B: The NRF sends a service discovery response to the AMF. The service discovery response carries the NF profile corresponding to the selected CMF. This step corresponds to S802 above.

[0277] S1105B. AMF obtains the UE's allowed CAG information from CMF and decides whether to authorize UE access based on the obtained CAG information.

[0278] Of course, the above steps are only some examples, and the actual UE registration process may also include more or fewer steps.

[0279] In the scheme given in Figure 11A above, the NEF selects the CMF for storing the CAG information based on the TAI, and in the scheme given in Figure 11B above, the AMF selects the CMF for obtaining the CAG information based on the TAI. This allows the NEF and AMF to select the same CMF, thereby improving the accuracy of network element discovery and selection and improving the success rate of UE registration with the network.

[0280] It can be understood that the above Figures 9A-9B, 10A-10B, and 11A-11B are only some possible examples and are not limited to these.

[0281] The method provided by the embodiment of the present application is described above in conjunction with the accompanying drawings, and the device provided by the embodiment of the present application is described below in conjunction with the accompanying drawings.

[0282] Based on the same technical concept, embodiments of the present application provide a communications device, comprising a module / unit / means for executing the method performed by any device, network element, or entity in the above method embodiments. The module / unit / means may be implemented in software or hardware, or the corresponding software implementation may be executed by hardware.

[0283] For example, referring to FIG12 , a schematic diagram of a communication device according to an embodiment of the present application is provided. The device includes a transceiver module 1201 and a processing module 1202 .

[0284] For example, when the device is located at NRF, the functions of the modules of the device are as follows:

[0285] The transceiver module 1201 is configured to receive a registration request from a first network element, wherein the first network element is configured to store CAG information, the registration request including a first network function configuration file, the first network function configuration file including identification information of the first network element and at least one of first information and second information, the first information indicating CAG information managed by the first network element, and the second information indicating a service area managed by the first network element;

[0286] The processing module 1202 is configured to save the first network function configuration file;

[0287] The transceiver module 1201 is further configured to send a registration response to the first network element.

[0288] Optionally, the transceiver module 1201 may also be configured to receive a service discovery request from a second network element, where the service discovery request includes at least one CAG information and / or at least one service area identifier; and send a service discovery response to the second network element.

[0289] For example, when the device is located in the first network element, the functions of the modules of the device are as follows:

[0290] The transceiver module 1201 is used to send a registration request to a network storage function network element; wherein the first network element is used for CAG information, the registration request includes a first network function configuration file, the first network function configuration file includes identification information of the first network element, and also includes at least one of the first information and the second information, the first information indicates the CAG information managed by the first network element, and the second information indicates the service area managed by the first network element; receive a registration response from the network storage function network element.

[0291] For example, when the device is located in the second network element, the functions of the modules of the device are as follows:

[0292] The transceiver module 1201 is configured to send a service discovery request to a network storage function network element, where the service discovery request includes at least one CAG information and / or at least one service area identifier; and receive a service discovery response from the network storage function network element.

[0293] It should be understood that all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0294] In specific implementation, the above device can have various product forms. Several possible product forms are introduced below.

[0295] As shown in FIG13 , an embodiment of the present application further provides a communication device, including:

[0296] At least one processor 1301; and a communication interface 1303 communicatively connected to the at least one processor 1301; the at least one processor 1301 executes instructions stored in the memory 1302, so that the device performs the method steps in the above method embodiment through the communication interface 1303.

[0297] Optionally, the memory 1302 is located outside the device.

[0298] Optionally, the apparatus includes the memory 1302, the memory 1302 is connected to the at least one processor 1301, and the memory 1302 stores instructions executable by the at least one processor 1301. FIG13 uses dashed lines to indicate that the memory 1302 is optional for the apparatus.

[0299] The processor 1301 and the memory 1302 may be coupled via an interface circuit or may be integrated together, which is not limited here.

[0300] The specific connection medium between the processor 1301, memory 1302, and communication interface 1303 is not limited in the embodiments of the present application. In Figure 13, the processor 1301, memory 1302, and communication interface 1303 are connected via a bus 1304. The bus is represented by a bold line in Figure 13. The connection between other components is only for schematic illustration and is not intended to be limiting. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one bold line is used in Figure 13, but this does not mean that there is only one bus or one type of bus.

[0301] Based on the same technical concept, an embodiment of the present application also provides a chip, see Figure 14, which may include a logic circuit and an input / output interface. Optionally, a memory may also be included. The input / output interface may be used to receive code instructions (the code instructions are stored in the memory, which may be read directly from the memory, or may be read from the memory through other devices) and transmit them to the logic circuit; the logic circuit may be used to run the code instructions to execute the method in the above method embodiment.

[0302] It should be understood that the processors mentioned in the embodiments of the present application can be implemented by hardware or software. When implemented by hardware, the processor can be a logic circuit, an integrated circuit, etc. When implemented by software, the processor can be a general-purpose processor that is implemented by reading software code stored in a memory.

[0303] Exemplarily, the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.

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

[0305] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) can be integrated into the processor.

[0306] It should be noted that the memory described herein is intended to include, but not be limited to, these and any other suitable types of memory.

[0307] Based on the same technical concept, an embodiment of the present application also provides a computer-readable storage medium, which stores a computer program or instruction. When the computer program or instruction is executed by a communication device, the method steps in the above method embodiment are implemented.

[0308] Based on the same technical concept, an embodiment of the present application further provides a computer program product, which includes a computer program or instructions. When the computer program or the instructions are run by a communication device, the method steps in the above method embodiment are executed.

[0309] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0310] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the present application. It should be understood that each flow and / or box in the flow chart and / or block diagram, as well as the combination of the flow chart and / or box in the flow chart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one or more flow charts and / or one or more boxes in the block diagram.

[0311] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0312] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

Claims

1. A communication method, characterized in that: include: The network storage function network element receives a registration request from a first network element; wherein the first network element is used to store closed access group (CAG) information, the registration request includes a first network function configuration file, the first network function configuration file includes identification information of the first network element, and also includes at least one of first information and second information, the first information indicates CAG information managed by the first network element, and the second information indicates a service area managed by the first network element; The network storage function network element stores the first network function configuration file; The network storage function network element sends a registration response to the first network element.

2. The method according to claim 1, wherein The method further comprises: The network storage function network element receives a service discovery request from a second network element; The network storage function network element sends a service discovery response to the second network element, where the service discovery response includes the first network function configuration file; In which, the service discovery request includes at least one CAG information, and the at least one CAG information belongs to the CAG information indicated by the first information; and / or, the service discovery request includes at least one service area identifier, and the service area indicated by the at least one service area identifier belongs to the service area indicated by the second information.

3. The method according to claim 2, wherein The first network function configuration file also includes third information, and the third information indicates the terminal device identifier managed by the first network element.

4. The method according to claim 3, wherein The service discovery request also includes at least one terminal device identifier, and the at least one terminal device identifier belongs to the terminal device identifier indicated by the third information.

5. The method according to claim 2, wherein The method further comprises: The network storage function network element receives at least one terminal device identifier from the first network element, and the at least one terminal device identifier is used to identify the terminal device corresponding to the CAG information stored in the first network element; the network storage function network element updates the at least one terminal device identifier to the first network function configuration file.

6. The method according to claim 5, wherein The service discovery request also includes a first terminal device identifier, and the first terminal device identifier is stored in the first network function configuration file.

7. The method according to claim 1, wherein The method further comprises: The network storage function network element receives a service discovery request from a second network element; The network storage function network element sends a service discovery response to the second network element, where the service discovery response indicates a service discovery failure, and the service discovery response includes a reason value, where the reason value indicates a reason for the service discovery failure; In which, the service discovery request includes at least one CAG information, and the at least one CAG information does not belong to the CAG information corresponding to any network function configuration file stored in the network storage function network element; and / or, the service discovery request includes at least one service area identifier, and the service area indicated by the at least one service area identifier does not belong to the service area corresponding to any network function configuration file stored in the network storage function network element.

8. The method according to any one of claims 2 to 6, wherein: The service discovery request is a first service discovery request, and the at least one CAG information is CAG information of a CAG cell that the terminal device is allowed to access; The method further comprises: The network storage function network element receives a second service discovery request from a third network element, where the second service discovery request includes first CAG information, where the first CAG information is CAG information of the CAG cell accessed by the terminal device; The network storage function network element sends a second service discovery response to the third network element, where the second service discovery response includes the first network function configuration file, and the first CAG information belongs to the CAG information indicated by the first information.

9. The method according to any one of claims 1 to 8, wherein The first information includes: at least one CAG information range, wherein the first network element manages CAG information within the at least one CAG information range; or At least one CAG information set, wherein the first network element manages CAG information in the at least one CAG information set.

10. The method according to claim 3 or 4, characterized in that The third information includes: at least one terminal device identification range, the first network element managing terminal device identifications within the at least one terminal device identification range; or At least one terminal device identification set, the first network element manages the terminal device identifications in the at least one terminal device identification set.

11. The method according to any one of claims 2 to 8, wherein: The service area identifier is a tracking area identifier TAI.

12. The method according to any one of claims 3, 4, 5, 6 and 10, wherein: The terminal device identifier is GPSI.

13. The method according to any one of claims 2 to 7, wherein: The second network element is NEF or AMF.

14. The method according to any one of claims 2 to 8, wherein: The second network element is NEF, and the third network element is AMF.

15. A communication method, characterized in that: include: A first network element sends a registration request to a network storage function network element, wherein the first network element is configured to store closed access group (CAG) information, the registration request including a first network function configuration file, the first network function configuration file including identification information of the first network element and at least one of first information and second information, the first information indicating CAG information managed by the first network element, and the second information indicating a service area managed by the first network element; The first network element receives a registration response from the network storage function network element.

16. The method according to claim 15, wherein The first network function configuration file also includes third information, and the third information indicates the terminal device identifier managed by the first network element.

17. The method according to claim 15 or 16, wherein: The method further comprises: The first network element receives at least one CAG information from the second network element; The first network element stores the at least one CAG information.

18. The method according to claim 17, wherein The method further comprises: The first network element receives at least one terminal device identifier from the second network element, where the at least one terminal device identifier is used to identify the terminal device corresponding to the at least one CAG information; The first network element sends the at least one terminal device identifier to the network storage function network element.

19. A communication method, characterized in that: include: The second network element sends a service discovery request to the network storage function network element, where the service discovery request includes at least one CAG information and / or at least one service area identifier; The second network element receives a service discovery response from the network storage function network element.

20. The method according to claim 19, wherein The service discovery response includes a first network function configuration file, the first network function configuration file includes identification information of the first network element, and at least one of first information and second information, the first information indicating CAG information managed by the first network element, and the second information indicating a service area managed by the first network element; In which, the service discovery request includes the at least one CAG information, and the at least one CAG information belongs to the CAG information indicated by the first information; and / or, the service discovery request includes the at least one service area identifier, and the service area indicated by the at least one service area identifier belongs to the service area indicated by the second information.

21. The method according to claim 20, wherein The first network function configuration file also includes third information, and the third information indicates the terminal device identifier managed by the first network element.

22. The method according to claim 21, wherein The service discovery request also includes at least one terminal device identifier, and the at least one terminal device identifier belongs to the terminal device identifier indicated by the third information.

23. The method of claim 20, wherein: The first network function configuration file also includes at least one terminal device identifier.

24. The method according to claim 23, wherein The service discovery request also includes a first terminal device identifier, and the first terminal device identifier is stored in the first network function configuration file.

25. The method of claim 19, wherein: The service discovery response indicates that the service discovery failed, and the service discovery response includes a reason value, and the reason value indicates a reason for the service discovery failure; In which, the service discovery request includes the at least one CAG information, and the at least one CAG information does not belong to the CAG information corresponding to any network function configuration file stored in the network storage function network element; and / or, the service discovery request includes the at least one service area identifier, and the service area indicated by the at least one service area identifier does not belong to the service area corresponding to any network function configuration file stored in the network storage function network element.

26. The method according to any one of claims 19 to 25, wherein: The service discovery request includes the at least one service area identifier; and the method further includes: The second network element receives the at least one service area identifier from the terminal device.

27. A communication device, characterized in that: The method comprises a module for executing the method according to any one of claims 1 to 14, or comprises a module for executing the method according to any one of claims 15 to 18, or comprises a module for executing the method according to any one of claims 19 to 26.

28. A communication device, characterized in that: The method comprises at least one processor; and a communication interface communicatively connected to the at least one processor; the at least one processor executes instructions stored in a memory, thereby causing the method according to any one of claims 1 to 14 to be executed, or causing the method according to any one of claims 15 to 18 to be executed, or causing the method according to any one of claims 19 to 26 to be executed.

29. A computer-readable storage medium, characterized in that The storage medium stores a computer program or instruction. When the computer program or instruction is executed, the method according to any one of claims 1 to 14 is implemented, or the method according to any one of claims 15 to 18 is implemented, or the method according to any one of claims 19 to 26 is implemented.

30. A computer program product, characterized in that The method comprises instructions which, when executed on a computer, enable the method according to any one of claims 1 to 14 to be implemented, or enable the method according to any one of claims 15 to 18 to be implemented, or enable the method according to any one of claims 19 to 26 to be implemented.

Images