Communication method and communication apparatus

Abstract

Provided in the present application are a communication method and a communication apparatus. The method comprises: receiving first request information, which comprises a first CAG identity, wherein the first request information is used for requesting the creation or update or deletion of first subscription data of a terminal device that corresponds to the first CAG identity; on the basis of the first CAG identity, determining that the creation or update or deletion of the first subscription data requested by the first request information is not allowed; and sending first response information, which is used for indicating a failure in the creation or update or deletion of the first subscription data requested by the first request information. The present application can improve the accuracy of the creation or update or deletion of subscription data.

Description

Communication methods and communication devices

[0001] This application claims priority to Chinese Patent Application No. 202510078449.8, filed on January 16, 2025, with the China National Intellectual Property Administration, entitled "Communication Method and Communication Device", the entire contents of which are incorporated herein by reference. Technical Field

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

[0003] Closed access group (CAG) technology is a type of public network integrated-non-public network (PNI-NPN) technology primarily used for access control. For example, for a specific cell, only a specific group of users is allowed to access it, thus achieving access control. Another example is in a femtocell (Femto) scenario, a corresponding CAG identity (ID) is assigned to each Femto. When the CAG information included in the subscription data of the UE corresponding to the Femto owner includes the CAG ID of the Femto, the user can select that Femto for access. Currently, the management of subscription data corresponding to CAG parameters is not secure or accurate enough. Summary of the Invention

[0004] This application provides a communication method and a communication device to improve the accuracy of creating, updating or deleting subscription data by verifying whether the creation, updating or deletion of subscription data corresponding to the CAG parameters provided by the requesting party in the terminal device is permitted.

[0005] Firstly, a communication method is provided. This method can be executed by a core network element, or by a module (e.g., a chip or circuit) within a core network element, or by a logical node, logical module, or software capable of implementing all or part of the core network element's functions. This application does not limit the scope of this method. For ease of understanding, the embodiments of this application are described using core network element execution as an example.

[0006] The method includes: receiving first request information, the first request information including a first CAG identifier, the first request information being used to request the creation, update or deletion of first subscription data of a terminal device corresponding to the first CAG identifier; determining, based on the first CAG identifier, that the creation, update or deletion of the first subscription data requested by the first request information is not permitted; and sending first response information, the first response information being used to indicate that the creation, update or deletion of the first subscription data requested by the first request information has failed.

[0007] It is understandable that core network elements can also determine whether to allow the creation, update, or deletion of the first subscription data requested by the first request information based on the first CAG identifier. In other words, core network elements can determine whether to allow the creation, update, or deletion of the first subscription data requested by the first request information based on the first CAG identifier. The specific implementation process for determining whether to allow the creation, update, or deletion of the first subscription data requested by the first request information based on the first CAG identifier can be found in the description of the methods in the second aspect and any possible implementation of the second aspect below, and will not be repeated here.

[0008] Alternatively, in this embodiment of the application, determining that the creation, update, or deletion of the first contract data requested by the first request information is not allowed can also be understood as determining that the creation, update, or deletion of the first contract data requested by the first request information is refused. In this case, determining that the creation, update, or deletion of the first contract data requested by the first request information is refused can be understood as refusing to create, update, or delete the first contract data corresponding to the first CAG identifier in the terminal device.

[0009] Based on the above scheme, the core network element can determine, according to the first CAG identifier in the first request information, that the creation, updating, or deletion of subscription data corresponding to the first CAG identifier in the terminal device requested by the first request information is not permitted. Therefore, when the requester of the first request information provides CAG parameters, the core network element can further verify whether the subscription data corresponding to the CAG parameter is allowed to be created, updated, or deleted, and thus determine whether the creation, updating, or deletion of subscription data requested by the first request information is permitted. If the creation, updating, or deletion of subscription data requested by the first request information is not permitted, a failure to create, update, or delete the subscription data corresponding to the first CAG identifier is reported. Therefore, the accuracy of creating, updating, or deleting subscription data can be improved.

[0010] In conjunction with the first aspect, in some implementations of the first aspect, the core network element is a Network Open Function (NEF) network element. Receiving the first request information includes: receiving the first request information from the first application function (AF) network element; determining, based on the first CAG identifier, that the creation, update, or deletion of the first subscription data requested by the first request information is not permitted, including: matching the first CAG identifier with preset configuration information to determine that the creation, update, or deletion of the first subscription data requested by the first request information is not permitted; and sending the first response information includes: sending the first response information to the first AF network element.

[0011] For example, the preset configuration information includes conditions for creating, updating, or deleting subscription data on a terminal device. Specifically, the preset configuration information includes one or more CAG identifiers, where the subscription data corresponding to the one or more CAG identifiers is allowed to be created, updated, or deleted, and / or, the subscription data corresponding to the one or more CAG identifiers is not allowed to be created, updated, or deleted. Wherein, "the subscription data corresponding to the one or more CAG identifiers is allowed to be created, updated, or deleted" can be understood as meaning that the subscription data corresponding to the one or more CAG identifiers is allowed to be created, updated, or deleted; "the subscription data corresponding to the one or more CAG identifiers is not allowed to be created, updated, or deleted" can be understood as meaning that the subscription data corresponding to the one or more CAG identifiers is not allowed to be created, updated, or deleted.

[0012] For example, the preset configuration information includes one or more CAG identifiers whose corresponding contract data is allowed to be created, updated, or deleted. In this case, matching the first CAG identifier with the preset configuration information includes: matching the first CAG identifier with the one or more CAG identifiers; if the first CAG identifier does not belong to the one or more CAG identifiers, it is determined that the creation, updating, or deletion of the first contract data requested by the first request information is not allowed. It can be understood that matching the first CAG identifier with the one or more CAG identifiers, and determining that the creation, updating, or deletion of the first contract data requested by the first request information is allowed when the first CAG identifier belongs to the one or more CAG identifiers.

[0013] For example, if the preset configuration information includes one or more CAG identifiers whose corresponding contract data is not allowed to be created, updated, or deleted, then matching the first CAG identifier with the preset configuration information includes: matching the first CAG identifier with the one or more CAG identifiers; if the first CAG identifier belongs to the one or more CAG identifiers, it is determined that the creation, update, or deletion of the first contract data requested by the first request information is not allowed. It can be understood that matching the first CAG identifier with the one or more CAG identifiers, if the first CAG identifier does not belong to the one or more CAG identifiers, it is determined that the creation, update, or deletion of the first contract data requested by the first request information is allowed.

[0014] For example, among the multiple CAG identifiers included in the preset configuration information, some CAG identifiers correspond to contract data that can be created, updated, or deleted, while others correspond to contract data that cannot be created, updated, or deleted. In this case, matching the first CAG identifier with the preset configuration information includes: matching the first CAG identifier with the multiple CAG identifiers; when the contract data corresponding to the portion of CAG identifiers to which the first CAG identifier belongs is not allowed to be created, updated, or deleted, it is determined that the creation, update, or deletion of the first contract data requested by the first request information is not allowed; or, when the contract data corresponding to the portion of CAG identifiers to which the first CAG identifier does not belong is allowed to be created, updated, or deleted, it is determined that the creation, update, or deletion of the first contract data requested by the first request information is not allowed.

[0015] Based on the above scheme, the NEF network element can match the first CAG identifier with preset configuration information to determine whether the creation, update, or deletion of subscription data requested by the first request information is not allowed. Therefore, the NEF network element can further verify whether the creation, update, or deletion of subscription data corresponding to the first CAG identifier in the terminal device requested by the first request information is allowed, thereby improving the accuracy of creating, updating, or deleting subscription data corresponding to the first CAG identifier in the terminal device.

[0016] In conjunction with the first aspect, in certain implementations of the first aspect, the first request information includes the identifier of the first AF network element, and the preset configuration information includes multiple CAG identifiers and multiple AF network element identifiers. Matching the first CAG identifier with the preset configuration information to determine that the creation, update, or deletion of the first subscription data requested by the first request information is not allowed includes: matching the first CAG identifier with the multiple CAG identifiers, and matching the identifier of the first AF network element with the identifiers of the multiple AF network elements to determine that the creation, update, or deletion of the first subscription data requested by the first request information is not allowed.

[0017] In one example, the subscription data corresponding to the multiple CAG identifiers is allowed to be created, updated, or deleted. In this case, if the identifiers of the multiple AF network elements are allowed to create, update, or delete the subscription data corresponding to the multiple CAG identifiers, then the first CAG identifier and the identifier of the first AF network element are matched with the preset configuration information. It is determined that the creation, update, or deletion of the first subscription data requested by the first request information is not allowed. This can be understood as comparing the first CAG identifier with the multiple CAG identifiers; if the first CAG identifier does not belong to the multiple CAG identifiers, then the creation, update, or deletion of the first subscription data requested by the first request information is not allowed. Alternatively, the identifier of the first AF network element is compared with the identifiers of the multiple AF network elements; if the identifier of the first AF network element does not belong to the identifiers of one or more AF network elements corresponding to the first CAG identifier, then the creation, update, or deletion of the subscription data requested by the first request information is not allowed. Specifically, if the first CAG identifier belongs to one or more CAG identifiers, and the identifier of the first AF network element does not belong to one or more AF network elements corresponding to the first CAG identifier, then the creation, updating, or deletion of the subscription data requested by the first request information is not allowed; or if the identifier of the first AF network element belongs to one or more AF network element identifiers, and the first CAG identifier does not belong to one or more CAG identifiers corresponding to the first AF network element, then the creation, updating, or deletion of the first subscription data requested by the first request information is not allowed. It can be understood that by matching the first CAG identifier with preset configuration information, if the first CAG identifier belongs to one or more CAG identifiers, and the identifier of the first AF network element belongs to one or more AF network elements corresponding to the first CAG identifier, then the creation, updating, or deletion of the first subscription data requested by the first request information is allowed.

[0018] In one example, the subscription data corresponding to the multiple CAG identifiers is not allowed to be created, updated, or deleted. In this case, the multiple AF network elements are not allowed to create, update, or delete the subscription data corresponding to the multiple CAG identifiers. The first CAG identifier, the identifier of the first AF network element, and the preset configuration information are matched to determine that the creation, update, or deletion of the first subscription data requested by the first request information is not allowed. This can be understood as comparing the first CAG identifier with the multiple CAG identifiers; if the first CAG identifier belongs to the multiple CAG identifiers, then the creation, update, or deletion of the first subscription data requested by the first request information is not allowed. Alternatively, the identifier of the first AF network element is compared with the identifiers of the multiple AF network elements; if the identifier of the first AF network element belongs to one or more AF network elements corresponding to the first CAG identifier, then the creation, update, or deletion of the first subscription data requested by the first request information is not allowed. It is understandable that when the first CAG identifier is matched with the preset configuration information, and the first CAG identifier does not belong to one or more CAG identifiers, and the identifier of the first AF network element does not belong to one or more AF network elements corresponding to the first CAG identifier, it is determined that the creation, updating or deletion of the first contract data requested by the first request information is allowed.

[0019] It should be noted that for more detailed examples of the identification of these multiple CAG identifiers and multiple AF network elements, please refer to the description below, which will not be repeated here.

[0020] Based on the above scheme, when the preset configuration information includes multiple CAG identifiers and multiple AF network element identifiers, the core network element can further match the first CAG identifier with the multiple CAG identifiers, and match the first AF network element identifier with the multiple AF network element identifiers, to determine whether the creation, updating, or deletion of the subscription data requested by the first request information is not allowed. Therefore, the NEF network element can further verify whether the creation, updating, or deletion of the subscription data corresponding to the first CAG identifier in the terminal device requested by the first request information is allowed, thereby improving the accuracy of creating, updating, or deleting the subscription data corresponding to the first CAG identifier in the terminal device.

[0021] In conjunction with the first aspect, in certain implementations of the first aspect, the first request information includes the identifier of the first AF network element, and the preset configuration information includes multiple CAG identifiers and the identifiers of one or more AF network elements that are allowed to create, update, or delete the subscription data corresponding to the multiple CAG identifiers. Matching the first CAG identifier with the preset configuration information and determining that the creation, update, or deletion of the first subscription data requested by the first request information is not allowed includes: when the first CAG identifier does not belong to the multiple CAG identifiers or the identifier of the first AF network element does not belong to the identifier of one or more AF network elements corresponding to the first CAG identifier, determining that the creation, update, or deletion of the first subscription data requested by the first request information is not allowed.

[0022] For example, the plurality of CAG identifiers correspond to the identifiers of the plurality of AF network elements. This correspondence includes one or more of the following: a one-to-one correspondence between the plurality of CAG identifiers and the identifiers of the plurality of AF network elements; one of the plurality of CAG identifiers corresponds to the identifiers of at least two of the plurality of AF network elements; or at least two of the plurality of CAG identifiers correspond to the identifier of one of the plurality of AF network elements. In other words, the plurality of CAG identifiers correspond to the identifiers of one or more AF network elements, or the identifiers of the plurality of AF network elements correspond to one or more ACG identifiers.

[0023] In conjunction with the first aspect, in some implementations of the first aspect, the core network element is a Unified Data Management (UDM) network element. Receiving the first request information includes: receiving the first request information from the NEF network element; determining, based on the first CAG identifier, that the creation, update, or deletion of the first subscription data requested by the first request information is not permitted, including: matching the first CAG identifier with the subscription data of the terminal device to determine that the creation, update, or deletion of the first subscription data requested by the first request information is not permitted; and sending the first response information includes: sending the first response information to the NEF network element.

[0024] Based on the above scheme, after receiving the first request information, the UDM network element matches the first CAG identifier with the subscription data of the terminal device, and then determines that the creation, update, or deletion of subscription data requested by the first request information is not allowed. Therefore, the UDM network element verifies whether the subscription data corresponding to the first CAG identifier included in the first request information is allowed to be created, updated, or deleted. In this way, the subscription data will only be created, updated, or deleted if the subscription data corresponding to the first CAG identifier is allowed to be created, updated, or deleted, thereby improving the accuracy of subscription data creation, updating, or deletion.

[0025] In conjunction with the first aspect, in some implementations of the first aspect, the subscription data of the terminal device includes one or more CAG identifiers, and the subscription data corresponding to the one or more CAG identifiers allows creation, updating, or deletion. Matching the first CAG identifier with the subscription data of the terminal device and determining that the creation, updating, or deletion of the first subscription data requested by the first request information is not allowed includes: when the first CAG identifier does not belong to the one or more CAG identifiers, determining that the creation, updating, or deletion of the first subscription data requested by the first request information is not allowed.

[0026] For example, whether the creation, updating, or deletion of subscription data corresponding to one or more CAG identifiers included in the subscription data of the terminal device is permitted can be indicated by indication information. For instance, the indication information may indicate that the creation, updating, or deletion of subscription data corresponding to the one or more CAG identifiers is permitted; or, the indication information may indicate that the creation, updating, or deletion of subscription data corresponding to the one or more CAG identifiers is not permitted; or, for another example, a first indication information may indicate that the creation, updating, or deletion of subscription data corresponding to some of the multiple CAG identifiers is permitted, and a second indication information may indicate that the creation, updating, or deletion of subscription data corresponding to some of the multiple CAG identifiers is not permitted. In other words, the subscription data of the terminal device may also include one or more indication information, which are used to indicate whether the creation, updating, or deletion of subscription data corresponding to the one or more CAG identifiers is permitted.

[0027] In one example, the instruction information indicates that the contractual data corresponding to the one or more CAG identifiers is allowed to be created, updated, or deleted. In this case, the first CAG identifier is matched against the contractual data to determine if the creation, update, or deletion of the first contractual data requested by the first request information is not permitted. This can be understood as comparing the first CAG identifier with the one or more CAG identifiers; if the first CAG identifier does not belong to the one or more CAG identifiers, then the creation, update, or deletion of the first contractual data requested by the first request information is considered not permitted.

[0028] In one example, the indication information indicates that the contract data corresponding to one or more CAG identifiers is not allowed to be created, updated, or deleted. In this case, the first CAG identifier is matched with the contract data to determine that the creation, update, or deletion of the first contract data requested by the first request information is not allowed. This can be understood as comparing the first CAG identifier with the multiple CAG identifiers. If the first CAG identifier belongs to the multiple CAG identifiers, it is considered that the creation, update, or deletion of the first contract data requested by the first request information is not allowed.

[0029] In one example, a first instruction indicates that the contractual data corresponding to some of the multiple CAG identifiers is allowed to be created, updated, or deleted, while a second instruction indicates that the contractual data corresponding to some of the multiple CAG identifiers is not allowed to be created, updated, or deleted. In this case, the first CAG identifier is matched with the contractual data to determine that the creation, update, or deletion of the first contractual data requested by the first request is not permitted. This can be understood as comparing the first CAG identifier with the multiple CAG identifiers. If the first CAG identifier belongs to some of the multiple CAG identifiers indicated by the second instruction, and does not belong to any of the multiple CAG identifiers indicated by the first instruction, then the creation, update, or deletion of the first contractual data requested by the first request is considered not permitted. Alternatively, if the first CAG identifier belongs to some of the multiple CAG identifiers indicated by the first instruction, and does not belong to any of the multiple CAG identifiers indicated by the second instruction, then the creation, update, or deletion of the first contractual data requested by the first request is considered not permitted.

[0030] Based on the above scheme, the UDM network element matches the first CAG identifier with multiple CAG identifiers in the contract data to determine whether the first CAG identifier belongs to the multiple CAG identifiers, and then verifies whether the contract data corresponding to the first CAG identifier included in the first request information is allowed to be created, updated, or deleted. In this way, the contract data will only be created, updated, or deleted if the contract data corresponding to the first CAG identifier is allowed to be created, updated, or deleted, thereby improving the accuracy of contract data creation, updating, or deletion.

[0031] In conjunction with the first aspect, in certain implementations of the first aspect, the first request information includes the identifier of the first AF network element, and the subscription data of the terminal device includes one or more CAG identifiers and the identifiers of one or more AF network elements that allow the creation, updating, or deletion of subscription data corresponding to the one or more CAG identifiers. Matching the first CAG identifier with the subscription data of the terminal device and determining that the creation, updating, or deletion of the first subscription data requested by the first request information is not allowed includes: when the first CAG identifier does not belong to the one or more CAG identifiers or the identifier of the first AF network element does not belong to the identifier of the one or more AF network elements corresponding to the first CAG identifier, determining that the creation, updating, or deletion of the first subscription data requested by the first request information is not allowed.

[0032] Based on the above scheme, the UDM network element can also match the identifier of the first AF network element with the identifiers of one or more AF network elements that are allowed to create, update or delete multiple CAG identifiers in the contract data. In this way, even if the contract data corresponding to the first CAG identifier is allowed to be created, updated or deleted, the UDM network element will further determine whether the first AF network element is allowed to create, update or delete the contract data, thereby improving the accuracy of the creation, update or deletion of the contract data.

[0033] In conjunction with the first aspect, in some implementations of the first aspect, the core network element is a first AF network element, and receiving the first request information includes: receiving the first request information from the terminal device; determining, based on the first CAG identifier, that the creation, update, or deletion of the first subscription data requested by the first request information is not allowed, including: matching the first CAG identifier with preset configuration information to determine that the creation, update, or deletion of the first subscription data requested by the first request information is not allowed; sending the first response information includes: sending the first response information to the terminal device.

[0034] In conjunction with the first aspect, in some implementations of the first aspect, the preset configuration information includes one or more CAG identifiers, and the contract data corresponding to the one or more CAG identifiers is allowed to be created, updated, or deleted. Matching the first CAG identifier with the preset configuration information and determining that the creation, update, or deletion of the first contract data requested by the first request information is not allowed includes: when the first CAG identifier does not belong to the one or more CAG identifiers, determining that the creation, update, or deletion of the first contract data requested by the first request information is not allowed.

[0035] For example, the preset configuration information includes one or more CAG identifiers, and the subscription data corresponding to these one or more CAG identifiers can be created, updated, or deleted. In this case, matching the first CAG identifier with the preset configuration information includes: matching the first CAG identifier with the one or more CAG identifiers; if the first CAG identifier does not belong to the one or more CAG identifiers, it is determined that the creation, updating, or deletion of the first subscription data requested by the first request information is not allowed. It can be understood that if the first CAG identifier belongs to the one or more CAG identifiers, it is determined that the creation, updating, or deletion of the first subscription data requested by the first request information is allowed.

[0036] For example, the preset configuration information includes one or more CAG identifiers, and the subscription data corresponding to these one or more CAG identifiers is not allowed to be created, updated, or deleted. In this case, matching the first CAG identifier with the preset configuration information includes: matching the first CAG identifier with the one or more CAG identifiers; if the first CAG identifier belongs to the one or more CAG identifiers, it is determined that the creation, update, or deletion of the first subscription data requested by the first request information is not allowed. It can be understood that if the first CAG identifier does not belong to the one or more CAG identifiers, it is determined that the creation, update, or deletion of the first subscription data requested by the first request information is allowed.

[0037] For example, among the multiple CAG identifiers included in the preset configuration information, some CAG identifiers correspond to contract data that can be created, updated, or deleted, while others correspond to contract data that cannot be created, updated, or deleted. In this case, matching the first CAG identifier with the preset configuration information includes: matching the first CAG identifier with the multiple CAG identifiers; when the contract data corresponding to the portion of CAG identifiers to which the first CAG identifier belongs is not allowed to be created, updated, or deleted, it is determined that the creation, update, or deletion of the first contract data requested by the first request information is not allowed; or, when the contract data corresponding to the portion of CAG identifiers to which the first CAG identifier does not belong is allowed to be created, updated, or deleted, it is determined that the creation, update, or deletion of the first contract data requested by the first request information is not allowed.

[0038] Based on the above scheme, the AF network element can match the first CAG identifier with preset configuration information to determine whether the creation, update, or deletion of subscription data requested by the first request information is not allowed. Therefore, the AF network element can further verify whether the creation, update, or deletion of subscription data corresponding to the first CAG identifier in the terminal device requested by the first request information is allowed, thereby improving the accuracy of creating, updating, or deleting subscription data corresponding to the first CAG identifier in the terminal device.

[0039] In conjunction with the first aspect, in some implementations of the first aspect, the first response information includes the reason for the failure of the creation, update, or deletion of the first contractual data requested by the first request information, including the reason that the creation, update, or deletion of the first contractual data requested by the first request information is not allowed.

[0040] Based on the above scheme, when a core network element determines that the creation, update, or deletion of the subscription data requested by the first request information is not allowed, it will also provide feedback to the initiator of the first request information on the reason why the creation, update, or deletion of the subscription data failed.

[0041] Secondly, a communication method is provided. This method can be executed by a core network element, or by a module (e.g., a chip or circuit) within a core network element, or by a logical node, logical module, or software capable of implementing all or part of the core network element's functions. This application does not limit the scope of this method. For ease of understanding, the embodiments of this application are described using core network element execution as an example.

[0042] The method includes: receiving first request information, the first request information including a first CAG identifier, the first request information being used to request the creation, updating, or deletion of first subscription data of a terminal device corresponding to the first CAG identifier; determining, based on the first CAG identifier, permission to execute the creation, updating, or deletion of the first subscription data requested by the first request information; sending second request information, the second request information including the first CAG identifier, the second request information being used to request the creation, updating, or deletion of the first subscription data; or sending first response information, the first response information being used to indicate that the creation, updating, or deletion of the first subscription data requested by the first request information was successful.

[0043] Based on the above scheme, the core network element can determine whether the creation, updating, or deletion of the subscription data corresponding to the first CAG identifier in the terminal device requested by the first request information is permitted, based on the first CAG identifier in the first request information. Therefore, when the requester of the first request information provides CAG parameters, the core network element can further verify whether the CAG parameter allows the creation, updating, or deletion of the corresponding subscription data, and thus determine whether the creation, updating, or deletion of the subscription data requested by the first request information is permitted. If the creation, updating, or deletion of the subscription data requested by the first request information is permitted, a second request will be initiated or feedback will be provided that the creation, updating, or deletion of the subscription data corresponding to the first CAG identifier was successful. Therefore, the accuracy of creating, updating, or deleting subscription data can be improved.

[0044] In conjunction with the second aspect, in some implementations of the second aspect, the core network element is a Network Open Function (NEF) network element. Receiving the first request information includes: receiving the first request information from the first application function (AF) network element; determining, based on the first CAG identifier, whether to allow the creation, update, or deletion of the first subscription data requested by the first request information, including: matching the first CAG identifier with preset configuration information to determine whether to allow the creation, update, or deletion of the first subscription data requested by the first request information; and sending the second request information, including: sending the second request information to the Unified Data Management (UDM) network element.

[0045] For example, the second request information may also include the identifier of the terminal device.

[0046] In conjunction with the second aspect, in some implementations of the second aspect, the first request information includes the identifier of the first AF network element, and the preset configuration information includes multiple CAG identifiers and multiple AF network element identifiers. Matching the first CAG identifier with the preset configuration information to determine whether the creation, update, or deletion of the first subscription data requested by the first request information is permitted includes: matching the first CAG identifier with the multiple CAG identifiers, and matching the identifier of the first AF network element with the identifiers of the multiple AF network elements to determine whether the creation, update, or deletion of the first subscription data requested by the first request information is permitted.

[0047] In conjunction with the second aspect, in some implementations of the second aspect, the first request information includes the identifier of the first AF network element, and the preset configuration information includes multiple CAG identifiers and the identifiers of one or more AF network elements that are allowed to create, update, or delete the subscription data corresponding to the multiple CAG identifiers. Matching the first CAG identifier with the preset configuration information to determine whether to allow the creation, update, or deletion of the first subscription data requested by the first request information is permitted includes: when the first CAG identifier belongs to the multiple CAG identifiers and the identifier of the first AF network element belongs to the identifier of one or more AF network elements corresponding to the first CAG identifier, determining whether to allow the creation, update, or deletion of the first subscription data requested by the first request information is permitted.

[0048] In conjunction with the second aspect, in some implementations of the second aspect, the core network element is a UDM network element. Receiving the first request information includes: receiving the first request information from the NEF network element; determining, based on the first CAG identifier, whether to allow the creation, update, or deletion of the first subscription data requested by the first request information, including: matching the first CAG identifier with the subscription data of the terminal device to determine whether to allow the creation, update, or deletion of the first subscription data requested by the first request information; and sending the first response information includes: sending the first response information to the NEF network element.

[0049] In conjunction with the second aspect, in some implementations of the second aspect, the subscription data of the terminal device includes one or more CAG identifiers, and the subscription data corresponding to the one or more CAG identifiers allows creation, updating or deletion. Matching the first CAG identifier with the subscription data of the terminal device to determine whether the creation, updating or deletion of the first subscription data requested by the first request information is allowed includes: when the first CAG identifier belongs to the one or more CAG identifiers, determining whether the creation, updating or deletion of the first subscription data requested by the first request information is allowed.

[0050] In conjunction with the second aspect, in some implementations of the second aspect, the first request information includes the identifier of the first AF network element, and the subscription data of the terminal device includes one or more CAG identifiers and the identifiers of one or more AF network elements that allow the creation, updating, or deletion of subscription data corresponding to the one or more CAG identifiers. Matching the first CAG identifier with the subscription data of the terminal device to determine whether the creation, updating, or deletion of the first subscription data requested by the first request information is allowed includes: when the first CAG identifier belongs to the one or more CAG identifiers and the identifier of the first AF network element belongs to the identifier of the one or more AF network elements corresponding to the first CAG identifier, determining whether the creation, updating, or deletion of the first subscription data requested by the first request information is allowed.

[0051] In conjunction with the second aspect, in some implementations of the second aspect, the core network element is a first AF network element. Receiving the first request information includes: receiving the first request information from the terminal device; determining, based on the first CAG identifier, whether to allow the creation, update, or deletion of the first subscription data requested by the first request information, including: matching the first CAG identifier with pre-configured information to determine whether to allow the creation, update, or deletion of the first subscription data requested by the first request information; and sending the second request information includes: sending the second request information to the NEF network element.

[0052] In conjunction with the second aspect, in some implementations of the second aspect, the pre-configuration information includes one or more CAG identifiers, and the contract data corresponding to the one or more CAG identifiers is allowed to be created, updated or deleted. Matching the first CAG identifier with the preset configuration information to determine whether the creation, update or deletion of the first contract data requested by the first request information is allowed includes: when the first CAG identifier belongs to the one or more CAG identifiers, determining whether the creation, update or deletion of the first contract data requested by the first request information is allowed.

[0053] The various implementation methods of the second aspect can refer to the various implementation methods of the first aspect mentioned above. The technical effects of the second aspect and its various implementation methods can refer to the technical effects of the first aspect and its various implementation methods. However, the technical effect of the first aspect and its various implementation methods needs to be replaced with "determining that the creation, updating or deletion of contract data requested by the first request information is not allowed" and "determining that the creation, updating or deletion of contract data requested by the first request information is allowed". Other technical effects that are not detailed will not be elaborated in the second aspect.

[0054] Thirdly, a communication apparatus is provided for performing the methods of the first to second aspects and any possible implementation thereof. Specifically, the apparatus may include units and / or modules for performing the methods of the first to second aspects and any possible implementation thereof, such as processing units and / or communication units.

[0055] In one implementation, the device is a core network device. When the device is a core network device, the communication unit can be a transceiver, or an input / output interface; the processing unit can be at least one processor. Optionally, the transceiver can be a transceiver circuit. Optionally, the input / output interface can be an input / output circuit.

[0056] In another implementation, the device is a chip, chip system, circuit, or communication module for core network equipment. When the device is a chip, chip system, or circuit for core network equipment, the communication unit may be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip, chip system, or circuit; the processing unit may be at least one processor, processing circuit, or logic circuit.

[0057] Fourthly, a communication device is provided, the device comprising: at least one processor configured to cause the device to perform the methods of the first to second aspects and any possible implementation thereof.

[0058] Optionally, the at least one processor is configured to execute computer programs or instructions to perform the methods described in the first to second aspects and any possible implementation thereof.

[0059] Optionally, the device further includes a memory for storing the computer program or instructions.

[0060] Optionally, the at least one processor is coupled to a memory for storing the computer program or instructions. The memory may be located externally to the device.

[0061] Optionally, the device also includes a communication interface through which the processor reads instructions from memory. This can be understood as the communication interface being coupled to the processor and used to input computer programs or instructions to the processor, or to output information from the processor.

[0062] Unless otherwise specified, or if the transmission and acquisition / reception operations involved do not contradict their actual function or internal logic in the relevant description, they can be understood as output, input, or other operations, or as transmission and reception operations performed by radio frequency circuits and antennas. This application does not limit them in this regard.

[0063] Fifthly, a computer-readable storage medium is provided that stores a computer program (e.g., program code) or instructions that, when executed on a communication device, cause the communication device to perform the methods described in the first to second aspects and any possible implementation thereof.

[0064] In a sixth aspect, a computer program product containing instructions is provided, which, when run on a computer, causes the computer to perform the methods described in the first to second aspects and any possible implementation thereof.

[0065] In a seventh aspect, a communication system is provided, comprising at least one of the aforementioned core network elements, or application function network elements, unified data management network elements, and network open function network elements. Attached Figure Description

[0066] Figure 1 is a schematic diagram of a system architecture applicable to an embodiment of this application.

[0067] Figure 2 is a schematic diagram of the methods for creating, updating, or deleting contract data.

[0068] Figure 3 is a schematic diagram of a communication method provided in an embodiment of this application.

[0069] Figure 4 is a schematic diagram of another communication method provided in an embodiment of this application.

[0070] Figure 5 is a schematic diagram of another communication method provided in an embodiment of this application.

[0071] Figure 6 is a schematic diagram of another communication method provided in an embodiment of this application.

[0072] Figure 7 is a schematic block diagram of a communication device provided in an embodiment of this application.

[0073] Figure 8 is a schematic block diagram of a communication device provided in an embodiment of this application.

[0074] Figure 9 is a schematic block diagram of a chip system provided in an embodiment of this application. Detailed Implementation

[0075] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0076] Before introducing the scheme of this application, the following points should be noted.

[0077] (1) In this application, the expression " / " is used to indicate that the objects before and after are in an "or" relationship; for example, A / B can mean: A or B. The expression "and / or" is used to indicate that the objects before and after are in a relationship of either "and" or "or"; for example, A and / or B can mean the following: A exists alone, B exists alone, A and B exist simultaneously, where A and B can be single or multiple. "At least one of the following" or similar expressions are used to indicate any combination of the listed items; for example, at least one of A, B and / or C can mean the following: A exists alone, B exists alone, C exists alone, A and B exist simultaneously, B and C exist simultaneously, A and C exist simultaneously, A, B and C exist simultaneously, where A, B, and C can be single or multiple.

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

[0079] (3) In the various embodiments of this application, unless otherwise specified or logically conflicting, the terms and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0080] (4) In this application, "first," "second," and "#1," "#2," and "#A" are merely for descriptive convenience and are used to distinguish objects, and are not intended to limit the scope of the embodiments of this application. They are not used to describe the order or sequence of features. It should be understood that such described objects can be interchanged where appropriate so as to describe solutions other than those in the embodiments of this application.

[0081] (5) In this application, the words “exemplary,” “for example,” etc., are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as an “example” in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the word “example” is intended to present the concept in a concrete manner. In the embodiments of this application, “of,” “corresponding, relevant,” and “corresponding” may sometimes be used interchangeably, and it should be noted that their intended meanings are consistent unless their distinction is emphasized.

[0082] (6) In this application, "instruction" can include direct instruction, indirect instruction, explicit instruction, implicit instruction, etc. When describing an instruction information as indicating A, it can be understood as the instruction information carrying A, carrying the identifier of A, carrying B which is associated with A, carrying the identifier of B which is associated with A, etc. In other words, if the receiving side of an instruction information can determine A based on the instruction information, it can be described as the instruction information indicating A, and the specific method of determination is not limited. When it is understood that the instruction information carries A, "instruction" can be replaced with "includes". In this case, expressions such as "send / receive instruction information, the instruction information indicates A" can be replaced with "send / receive A".

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

[0084] The following describes the communication system to which this application applies.

[0085] The technical solutions provided in this application can be applied to various communication systems, such as 5th generation (5G) or new radio (NR) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, and LTE time division duplex (TDD) systems. The technical solutions provided in this application can also be applied to future communication systems, such as future mobile communication systems. The technical solutions provided in this application can also be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), and Internet of Things (IoT) communication systems. The technical solutions provided in this application can also be applied to non-terrestrial network (NTN) systems such as inter-satellite communication and satellite communication.

[0086] As an example, a satellite communication system includes a satellite base station and terminal equipment. The satellite base station provides communication services to the terminal equipment. Satellite base stations can also communicate with each other. A satellite can act as a base station or as a terminal device. Here, "satellite" can refer to drones, hot air balloons, low-Earth orbit satellites, medium-Earth orbit satellites, high-Earth orbit satellites, etc. "Satellite" can also refer to non-terrestrial base stations or non-terrestrial equipment.

[0087] As an example, V2X communication can include: vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, vehicle-to-pedestrian (V2P) communication, and vehicle-to-network (V2N) communication.

[0088] In a communication system, a device can send signals to or receive signals from another device. These signals can include information, signaling, or data. The device can also be replaced by an entity, network entity, communication equipment, communication module, node, communication node, etc. This application uses a device as an example for description.

[0089] Figure 1 is a schematic diagram of a system architecture 100 applicable to this application. Figure 1 shows a schematic diagram of a non-roaming 5G system architecture (based on a reference point). To facilitate understanding of the embodiments of this application, the system architecture 100 applicable to the embodiments of this application will first be described in detail with reference to Figure 1. The system architecture 100 may specifically include the following network elements:

[0090] 1. User equipment (UE): also known as terminal equipment, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user device.

[0091] The terminal device in this application embodiment can be a device or module that accesses the aforementioned communication system and has corresponding communication functions. The terminal device can include various devices with wireless communication capabilities, which can be used to connect people, objects, machines, etc. The terminal device can be widely applied in various scenarios, such as: cellular communication, D2D, V2X, peer-to-peer, M2M, MTC, IoT, virtual reality (VR), augmented reality (AR), industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery, etc. The terminal device can be a terminal in any of the above scenarios, such as an MTC terminal, an IoT terminal, etc. Terminal equipment can be user equipment (UE), terminal, fixed equipment, mobile station equipment or mobile equipment, subscriber unit, handheld device, vehicle-mounted equipment, wearable device, cellular phone, smartphone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, wireless data card, personal digital assistant (PDA), computer, tablet computer, laptop computer, wireless modem, handset, laptop computer, computer with wireless transceiver capability, smart book, vehicle, satellite, global positioning system (GPS) device, target tracking device, aircraft (e.g., drones, helicopters, multiple helicopters, four helicopters, or airplanes), ship, remote control equipment, smart home device, industrial equipment, transportation vehicle with wireless communication capability, communication module, or roadside unit with terminal function, all conforming to the 3rd generation partnership project (3GPP) standard. A unit (RSU), a terminal device in a 5G network or a terminal device in a future evolved public land mobile network (PLMN), or a device built into the aforementioned device (e.g., a communication module, modem, or chip in the aforementioned device), or other processing devices connected to a wireless modem.

[0092] It should be understood that in certain scenarios, a UE can also be used as a base station. For example, a UE can act as a scheduling entity, providing sidelink signaling between UEs in scenarios such as V2X, D2D, or end-to-end.

[0093] As an example and not a limitation, in this embodiment, the terminal device can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are feature-rich, large in size, and can achieve complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those that focus on a specific type of application function and require the use of other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0094] Furthermore, in this embodiment, the terminal device can also be a terminal device in an IoT system. IoT is an important component of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object interconnection.

[0095] It should be noted that terminal devices and access network devices can communicate with each other using some air interface technology (such as NR or LTE). Terminal devices can also communicate with each other using some air interface technology (such as NR or LTE).

[0096] In this embodiment, the device for implementing the functions of a terminal device, i.e., the terminal device, can be the terminal device itself, or it can be any device capable of supporting the terminal device in implementing the functions, such as a chip system, chip, circuit, or communication module (i.e., a communication module that performs communication functions). This device can be installed in the terminal device. In this embodiment, the chip system can be composed of chips, or it can include chips and other discrete devices. Furthermore, the device can also be configured with program instructions for performing corresponding communication functions.

[0097] 2. Radio Access Network ((R)AN): Used to provide network access functionality to authorized users in a specific area, and can use transmission tunnels of different quality according to user level, service requirements, etc. (R)AN network elements can manage radio resources, provide access services to terminal devices, and thus complete the forwarding of control signals and user data between terminal devices and the core network. (R)AN can also be understood as a base station in a traditional network.

[0098] For example, the access network device in this application embodiment can be any kind of communication device with wireless transceiver function for communicating with user equipment. The access network device includes, but is not limited to, an evolved Node B (eNB) or 5G, such as NR, a gNB in ​​the system, or a transport point (TRP or TP), one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, or it can also be a network node constituting a gNB or transport point, such as a baseband unit (BBU) or a distributed unit (DU), etc.

[0099] The term "base station" can broadly encompass or replace various names listed below, such as: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitter point, master station, auxiliary station, motor slide retainer (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, micro base station, relay node, donor node, or a combination thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. Base stations can also be mobile switching centers, devices that perform base station functions in D2D, V2X, and M2M communications, network-side devices in future networks, and devices that perform base station functions in future communication systems. Base stations can support networks using the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the network equipment.

[0100] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0101] In some deployments, a gNB may include a centralized unit (CU) and a dedicated unit (DU). The gNB may also include an active antenna unit (AAU). The CU implements some of the gNB's functions, and the DU implements others. For example, the CU handles non-real-time protocols and services, implementing the functions of the radio resource control (RRC) and packet data convergence protocol (PDCP) layers. The DU handles physical layer protocols and real-time services, implementing the functions of the radio link control (RLC), media / medium access control (MAC), and physical (PHY) layers. The AAU implements some physical layer processing functions, radio frequency processing, and related functions of the active antenna. Since RRC layer information ultimately becomes PHY layer information, or is derived from PHY layer information, in this architecture, higher-layer signaling, such as RRC layer signaling, can also be considered as being sent by the DU, or by the DU+AAU. It is understood that access network equipment can be one or more of the following: CU nodes, DU nodes, and AAU nodes. Furthermore, a CU can be classified as an access network device in the radio access network (RAN) or as an access network device in the core network (CN); this application does not impose any limitations on this classification.

[0102] 3. Access and Mobility Management Function (AMF): Primarily used for mobility management and access management. Specifically, the AMF can be used to implement functions of the Mobility Management Entity (MME) other than session management, such as legitimacy monitoring or access authorization (or authentication).

[0103] For example, RAN equipment can support different radio access technologies. Currently, there are two types of radio access technologies: 3GPP access technologies (e.g., those used in 3rd generation (3G), 4th generation (4G), or 5G systems) and non-3GPP access technologies. 3GPP access technologies refer to access technologies that conform to 3GPP standards and specifications. For example, in 5G systems, access network equipment is called a next-generation node base station (gNB) or RAN equipment. Non-3GPP access technologies can include air interface technologies such as access points (APs) in Wireless Fidelity (WiFi), Worldwide Interoperability for Microwave Access (WiMAX), and Code Division Multiple Access (CDMA). RAN equipment can allow terminal equipment and the 3GPP core network to interconnect using non-3GPP technologies.

[0104] RAN equipment is responsible for functions such as radio resource management, quality of service (QoS) management, data compression, and encryption on the air interface side. AN equipment provides access services to terminal devices, thereby completing the forwarding of control signals and user data between the terminal devices and the core network.

[0105] RAN equipment may include, but is not limited to: macro base stations, micro base stations (also known as small stations), radio network controllers (RNCs), Node Bs (NBs), base station controllers (BSCs), base transceiver stations (BTSs), home base stations (e.g., home evolved Node Bs, or home Node Bs (HNBs)), baseband units (BBUs), access points (APs), wireless relay nodes, wireless backhaul nodes, transmission points (TPs), or transmission and reception points (TRPs) in WiFi systems. It may also be gNBs or transmission points (TRPs or TPs) in 5G (e.g., NR) systems, one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, or network nodes constituting gNBs or transmission points, such as distributed units (DUs), or base stations in next-generation 6G communication systems. This application does not limit the specific technology or equipment form used in the RAN equipment embodiments.

[0106] 4. Session Management Function (SMF): Primarily used for session management, allocation and management of Internet Protocol (IP) addresses for terminal devices, selection of manageable user plane functions, policy control, or endpoints for billing function interfaces, and downlink data notification, etc.

[0107] 5. User Plane Function (UPF): Used for packet routing and forwarding, or quality of service (QoS) processing of user plane data. UPF is specifically divided into intermediate-UPF (I-UPF) and anchor-UPF (A-UPF). I-UPF connects to the access network RAN, while A-UPF is the UPF for session anchors, also known as PDU session anchors (PSA).

[0108] 6. Data Network (DN): A network used to provide data transmission, such as the Internet. In the architecture of this application embodiment, the PSA connects to a remote DN, and the L-PSA can connect to a local DN.

[0109] 7. Authentication server function (AUSF): mainly used for user authentication, etc.

[0110] 8. Policy control function (PCF): A unified policy framework used to guide network behavior, providing policy rule information to control plane functional network elements (such as AMF, SMF, etc.).

[0111] 9. Unified Data Management (UDM): Used to handle user identification, access authentication, registration, or mobility management, etc.

[0112] 10. Application Function (AF): Primarily supports interaction with the 3rd Generation Partnership Project (3GPP) core network to provide services. This includes influencing data routing decisions, policy control functions, or providing third-party services to the network side. It can be understood as a third-party server, such as an application server on the Internet, providing relevant business information, including providing the PCF with service quality requirements information corresponding to the service, and sending user plane data information of the service to the PSA-UPF. The AF can be a content provider (CP).

[0113] 11. Network slice selection function (NSSF): Used to select network slices.

[0114] 12. Network Exposure Function (NEF) element: This element exposes the capabilities of each network element (NF) and transforms internal and external information. For example, it can be used in edge computing scenarios.

[0115] 13. Network Repository Function (NRF) element: Supports the registration and discovery of network functions, enabling network functions (NFs) to discover each other and communicate through the application programming interface (API).

[0116] In this system architecture, the N1 interface serves as the reference point between the terminal device and the AMF; the N2 interface serves as the reference point between the (R)AN and the AMF, used for sending non-access stratum (NAS) messages; the N3 interface serves as the reference point between the (R)AN and the I-UPF, used for transmitting user plane data; the N4 interface serves as the reference point between the SMF and the PSA-UPF, used for transmitting information such as tunnel identification information for the N3 connection, data buffer indication information, and downlink data notification messages; and the N6 interface serves as the reference point between the UPF and the DN, used for transmitting user plane data.

[0117] It should be understood that the system architecture of Figure 1 applied to the embodiments of this application is only an example of a network architecture described from the perspective of a reference point architecture. The network architecture applicable to the embodiments of this application is not limited to this. Any network architecture that can realize the functions of the above-mentioned network elements is applicable to the embodiments of this application.

[0118] It should be noted that the interface names between the various network elements in Figure 1 are just examples. In actual implementations, the interface names may be different, and this application does not specifically limit them. Furthermore, this application does not exclude the possibility that the various core network elements may be co-located as technology evolves.

[0119] It should be noted that the names of the various network elements (such as AMF, UDM, AF, etc.) included in Figure 1 are merely examples and do not limit the functions of the network elements themselves. In 5G networks and other future networks, the aforementioned network elements may also have other names, and this application embodiment does not specifically limit them. For example, in 6G networks, some or all of the aforementioned network elements may use the terminology from 5G, or may use other names, etc. This is explained uniformly here and will not be repeated below. In addition, it should be understood that the names of the messages (or signaling) transmitted between the aforementioned network elements are also merely examples and do not limit the functions of the messages themselves.

[0120] To facilitate understanding of the solutions in the embodiments of this application, the terminology that may be involved in the embodiments of this application will be briefly introduced below.

[0121] (1) Closed Access Group (CAG)

[0122] CAG is a mechanism used to restrict user equipment access to a specific network. The CAG mechanism allows a specific group of users to access one or more closed access cells, and only user equipment that is allowed to access the network can access the network through the CAG cell.

[0123] A CAG ID identifies a subscribed user group, which can access one or more CAG cells associated with that CAG ID. CAG cells broadcast their supported CAG IDs in broadcast messages. For example, a CAG cell might broadcast supported CAG IDs as CAG ID1, CAG ID2, and CAG ID5. User equipment (UE) locally stores a list of allowed CAGs, such as CAG ID1, CAG ID2, CAG ID3, and CAG ID4. Based on the broadcast message and the allowed CAG list, the UE determines whether a received CAG ID is in the allowed CAG list. If the received CAG ID is in the allowed CAG list, the UE believes it can access the services of that CAG cell and therefore requests access to the network device corresponding to that CAG cell. For example, if the UE receives CAG ID1 and CAG ID2, and since CAG ID1 and CAG ID2 are included in the allowed CAG list, the UE can access that CAG cell.

[0124] In Femto scenarios, CAG technology can also be introduced for access control. For example, operators can configure a CAG ID corresponding to the Femto. The subscription data of the user device corresponding to the Femto will then include the corresponding CAG information, which includes the CAG ID of the Femto. Thus, when a user purchases and deploys a Femto in their home, the user device can access the Femto because its subscription data includes the CAG information. When there are visitors at home, the user device's subscription data can also be modified to allow the visitor's device to access the Femto. After the visitor leaves, the visitor's corresponding CAG parameter can be deleted.

[0125] Figure 2 is a schematic diagram of method 200 for creating, updating, or deleting contract data. As shown in Figure 2, method 200 includes the following steps.

[0126] S210 and AF network elements send request information #1 to NEF network elements.

[0127] Correspondingly, the NEF network element receives request information #1 from the AF network element.

[0128] The request information #1 includes parameter #1, which consists of UE ID, AF network element ID, and CAG ID #1. The UE ID identifies the UE, the AF network element ID identifies the AF, and the CAG ID #1 identifies a specific CAG. The request information #1 is used to request the creation, updating, or deletion of subscription data corresponding to CAG ID #1 in the terminal device.

[0129] Optionally, parameter #1 may also include valid time information.

[0130] S220 and NEF network elements verify whether the AF network element is authorized to provide parameters based on request information #1.

[0131] When the AF network element provides parameters and initiates a request to create, update, or delete subscription data corresponding to CAG ID#1 in the provided parameters, the NEF network element needs to verify whether the AF network element is authorized to provide parameters. Upon verification that the AF is authorized to provide parameters, the NEF network element initiates a request to the UDM network element, thereby enabling the creation, updating, or deletion of the aforementioned subscription data. The subscription data includes CAG information, which includes the CAG ID that allows terminal devices to access the service. Verifying whether the AF network element is authorized to provide parameters can be understood as the NEF network element verifying whether it is authorized to call the service to create, update, or delete subscription data.

[0132] In one implementation, the AF network element sends request message #1 to the NEF network element to request the creation of the aforementioned subscription data. At this point, the NEF network element verifies whether the AF network element is authorized to provide parameters. If the AF network element is authorized to provide parameters, the NEF network element sends request message #2 to the UDM network element to request the creation of the aforementioned subscription data; if the AF network element is not authorized to provide parameters, the NEF network element sends a response message to the AF network element indicating that the creation of the aforementioned subscription data failed.

[0133] In one implementation, the AF network element sends request message #1 to the NEF network element to request the update of the aforementioned subscription data. At this point, the NEF network element verifies whether the AF network element is authorized to provide parameters. If the AF network element is authorized to provide parameters, the NEF network element sends request message #2 to the UDM network element to request the update of the aforementioned subscription data; if the AF network element is not authorized to provide parameters, the NEF network element sends a response message to the AF network element indicating that the update of the aforementioned subscription data failed.

[0134] In one implementation, the AF network element sends request message #1 to the NEF network element to request the deletion of the aforementioned subscription data. At this point, the NEF network element verifies whether the AF network element is authorized to provide parameters. If the AF network element is authorized to provide parameters, the NEF network element sends request message #2 to the UDM network element to request the deletion of the aforementioned subscription data; if the AF network element is not authorized to provide parameters, the NEF network element sends a response message to the AF network element indicating that the deletion of the aforementioned subscription data failed.

[0135] Based on the results of NEF network element verification, the following describes the subsequent steps executed by the NEF network element in cases one and two.

[0136] Scenario 1: NEF network element verification AF network element is not authorized to provide parameters, including the following steps S221a, as detailed below.

[0137] S221a, NEF network element sends response information #1 to AF network element.

[0138] Correspondingly, the AF network element receives response information #1 from the NEF network element.

[0139] Response information #1 indicates that the creation, updating, or deletion of the contract data failed.

[0140] In one implementation, if request message #1 requests the creation of the subscription data, and the NEF network element verifies that the AF network element is not authorized to provide parameters, response message #1 indicates that the creation of the subscription data has failed.

[0141] In one implementation, if request message #1 requests to update the subscription data, and the NEF network element verification AF network element is not authorized to provide parameters, response message #1 indicates that updating the subscription data has failed.

[0142] In one implementation, if request message #1 requests the deletion of the subscription data, then when the NEF network element verification AF network element is not authorized to provide parameters, response message #1 indicates that the deletion of the subscription data has failed.

[0143] Scenario 2: NEF network element verification AF network element is authorized to provide parameters, including the following steps S222a to S222f, as detailed below.

[0144] S222a, NEF network element sends request information #2 to UDM network element.

[0145] Correspondingly, the UDM network element receives request information #2 from the NEF network element.

[0146] The request information includes the UE ID and CAG ID#1, and the request information #2 is used to request the creation, update or deletion of the subscription data.

[0147] In one implementation, when the NEF network element verifies that the AF network element is authorized to provide parameters, the NEF network element sends request information #2 to the UDM network element to request the creation of the aforementioned subscription data. At this time, the UDM network element will further obtain the UE's subscription data to determine whether to create the subscription data based on the CAG ID #1 in the request information #2.

[0148] In one implementation, when the NEF network element verifies that the AF network element is authorized to provide parameters, the NEF network element sends request information #2 to the UDM network element to request the update of the aforementioned subscription data. At this time, the UDM network element will further obtain the UE's subscription data to determine whether to update the subscription data based on the CAG ID #1 in the request information #2.

[0149] In one implementation, when the NEF network element verifies that the AF network element is authorized to provide parameters, the NEF network element sends request information #2 to the UDM network element to request the deletion of the aforementioned subscription data. At this time, the UDM network element will further obtain the UE's subscription data to determine whether to delete the subscription data based on the CAG ID #1 in the request information #2.

[0150] Furthermore, the UDM network element determines the aforementioned subscription data based on the UE ID in request information #2, and the subsequent steps are as follows:

[0151] S222b and UDM network elements send query information to UDR network elements.

[0152] Correspondingly, the UDR network element receives query information from the UDM.

[0153] The query information includes the UE ID, which is used to request the aforementioned subscription data.

[0154] Specifically, the UDR network element determines the subscription data of the UE corresponding to the UE ID based on the UE ID, then searches for the corresponding record in the stored subscription data. After finding the corresponding subscription data, it further sends the subscription data to the UDM network element, that is, it executes step S222c.

[0155] The S222c and UDR network elements send subscription data to the UDM network element.

[0156] Correspondingly, the UDM network element receives subscription data from the UDR network element.

[0157] After the UDM network element receives the subscription data, it will compare the CAG ID#1 in the request information #2 with the subscription data, that is, execute step S222d.

[0158] S222d and UDM network elements determine whether to create, update, or delete the contract data based on CAG ID#1.

[0159] Specifically, the decision to create, update, or delete the contract data is based on whether the CAG information in the contract data includes the CAG ID#1.

[0160] In one implementation, if request information #2 requests the creation of the contract data, the UDM network element will match CAG ID #1. If the contract data includes CAG ID #1, it is assumed that the contract data corresponding to CAG ID #1 already exists, and the creation of the contract data for CAG ID #1 can be considered a failure. If the contract data does not include CAG ID #1, the contract data corresponding to CAG ID #1 can be created directly, and in this case, the creation of the contract data for CAG ID #1 is considered successful.

[0161] In one implementation, if request information #2 requests an update to the subscription data, the UDM network element will match CAG ID #1. If the subscription data includes CAG ID #1, it is considered that the subscription data corresponding to CAG ID #1 can be updated. For example, updating the validity period of the subscription data corresponding to CAG ID #1 is considered a successful update. If the subscription data does not include CAG ID #1, it is considered that the subscription data corresponding to CAG ID #1 cannot be updated.

[0162] In one implementation, if request information #2 requests the deletion of the subscription data, the UDM network element will match CAG ID #1. If the subscription data includes CAG ID #1, it is considered that the subscription data corresponding to CAG ID #1 can be deleted. For example, if the subscription data corresponding to CAG ID #1 is deleted, then it is considered that the subscription data corresponding to CAG ID #1 has been successfully deleted. If the subscription data does not include CAG ID #1, it is considered that the subscription data corresponding to CAG ID #1 cannot be deleted.

[0163] For example, when the UDM network element determines to create, update, or delete the subscription data, it will create, update, or delete the subscription data corresponding to the CAG ID in the UE. Optionally, the UDM network element sends an update request to the UDR network element, which includes the created, updated, or deleted subscription data. The UDR network element then saves the created, updated, or deleted subscription data. This update request can be a "Nudr_DM_Update request".

[0164] Furthermore, the UDM network element reports back to the NEF network element whether the creation, update, or deletion of the subscription data was successful, i.e., step S222e is executed.

[0165] The S222e and UDM network elements send response information #2 to the NEF network element.

[0166] Correspondingly, the NEF network element receives response information #2 from the UDM network element.

[0167] In one implementation, if the UDM element determines to create, update, or delete the subscription data based on CAG ID#1, then the response information #1 is used to indicate that the creation, update, or deletion of the subscription data was successful.

[0168] In one implementation, if the UDM element determines, based on CAG ID#1, not to create, update, or delete the subscription data, then the response information #1 is used to indicate that the creation, update, or deletion of the subscription data has failed.

[0169] After the NEF network element receives the response information #2, it will further report back to the AF network element whether the creation, update or deletion of the subscription data was successful, that is, execute step S222f.

[0170] S222f and NEF network elements send response information #3 to AF network elements.

[0171] Correspondingly, the AF network element receives response information #3 from the NEF network element.

[0172] The response message #1 indicates that the creation, updating, or deletion of the subscription data was successful; or the response message #1 indicates that the creation, updating, or deletion of the subscription data failed.

[0173] Method 200 in Figure 2 verifies whether the requesting AF network element is authorized to provide parameters, thereby determining whether it can create, update, or delete subscription data corresponding to the CAG parameters provided by the AF network element in the terminal device, and thus enabling the creation, updating, or deletion of subscription data. However, the above method only verifies whether the AF network element has the authority to provide parameters, without further verifying the parameters provided by the AF network element. This reduces the accuracy of creating, updating, or deleting subscription data. For example, the AF network element passes verification, but the subscription data corresponding to the provided CAG ID#1 may not actually be allowed to be created, updated, or deleted. If the subscription data corresponding to CAG ID#1 is created, updated, or deleted without verifying only whether the AF network element is authorized, the user will be unable to access the network correctly.

[0174] In view of this, embodiments of this application provide a communication method and a communication device to ensure the accuracy of the created, updated or deleted subscription data by verifying whether the creation, updating or deletion of the subscription data corresponding to the provided CAG identifier is allowed when the core network element is allowed to provide a CAG identifier.

[0175] The following describes in detail a communication method provided by an embodiment of this application with reference to Figures 3 to 6.

[0176] Figure 3 is a schematic diagram of a communication method 300 provided in an embodiment of this application. For ease of description, a core network element is used as an example for illustrative purposes. The core network element can be replaced by its constituent components (e.g., a chip, chip system, circuit, or communication module). The method 300 shown in Figure 3 may include the following steps.

[0177] S310. Receive first request information, the first request information including a first closed access group (CAG) identifier, the first request information being used to request the creation, updating, or deletion of first subscription data of the terminal device corresponding to the first CAG identifier.

[0178] In one implementation, the first request information is used to request the creation of the first contract data. In this case, the first request information can be "Nnef_ParameterProvision_Create request".

[0179] In one implementation, the first request information is used to request an update to the first subscription data. In this case, the first request information can be "Nnef_ParameterProvision_update request". Optionally, the first request information also includes a first validity period, which indicates the length of time the first subscription data is valid in the terminal device. This first validity period can be called the first validity time. The validity period of the first subscription data corresponding to the first CAG identifier can be understood as the validity period of the first subscription data corresponding to the first CAG identifier among all subscription data on the terminal device. For example, if the validity period is 1 hour, then within 1 hour, the terminal device can access the CAG cell corresponding to the CAG identifier; after 1 hour, the terminal device cannot access the CAG cell corresponding to the CAG identifier.

[0180] It should be noted that if the first request information does not include a validity period, then when requesting to update the first contract data, if the terminal device's contract data includes the first contract data, the first validity period is considered to be infinite, and the original validity period in the first contract data is updated to this first validity period, or the original validity period in the first contract data is updated to infinite length. Alternatively, it is considered that the first contract data corresponding to the first CAG identifier will not be updated. In this case, updating the first contract data is considered to have failed.

[0181] In one implementation, the first request information is used to request the deletion of the first contract data. In this case, the first request information can be "Nnef_ParameterProvision_Delete request".

[0182] Optionally, if the core network element is a NEF network element, then receiving the first request information includes: receiving the first request information from the first AF network element.

[0183] Optionally, if the core network element is a UDM network element, then receiving the first request information includes: receiving the first request information from the NEF network element.

[0184] Optionally, if the core network element is the first AF network element, then receiving the first request information includes: receiving the first request information from the terminal device.

[0185] S320. Based on the first CAG identifier, it is determined that the creation, update, or deletion of the first contract data requested by the first request information is not permitted.

[0186] Alternatively, in this embodiment of the application, determining that the creation, update, or deletion of the first contract data requested by the first request information is not allowed can also be understood as determining that the creation, update, or deletion of the first contract data requested by the first request information is refused. In this case, determining that the creation, update, or deletion of the first contract data requested by the first request information is refused can be understood as the first contract data corresponding to the first CAG identifier in the terminal device is refused to be created, updated, or deleted.

[0187] In one implementation, if the first request information is used to request the creation of the first contract data, then the core network element determines, based on the first CAG identifier, that it is not allowed to execute the request to create the first contract data requested by the first request information.

[0188] In one implementation, if the first request information is used to request the update of the first contract data, then the core network element determines, based on the first CAG identifier, that it is not allowed to execute the update of the first contract data requested by the first request information.

[0189] In one implementation, if the first request information is used to request the deletion of the first subscription data, then the core network element determines, based on the first CAG identifier, that it is not allowed to execute the deletion of the first subscription data requested by the first request information.

[0190] Optionally, the core network element is a NEF network element. Determining that the creation, update, or deletion of the first subscription data requested by the first request information is not allowed based on the first CAG identifier includes: matching the first CAG identifier with preset configuration information to determine that the creation, update, or deletion of the first subscription data requested by the first request information is not allowed.

[0191] Optionally, the core network element is a UDM network element. Determining that the creation, update, or deletion of the first subscription data requested by the first request information is not allowed based on the first CAG identifier includes: matching the first CAG identifier with the subscription data of the terminal device to determine that the creation, update, or deletion of the first subscription data requested by the first request information is not allowed.

[0192] Optionally, the core network element is the first AF network element. Determining that the creation, update, or deletion of the first subscription data requested by the first request information is not allowed based on the first CAG identifier includes: matching the first CAG identifier with preset configuration information to determine that the creation, update, or deletion of the first subscription data requested by the first request information is not allowed.

[0193] Understandably, core network elements can also determine whether to allow the creation, update, or deletion of the first subscription data requested by the first request information based on the first CAG identifier. In other words, core network elements determine whether to allow the creation, update, or deletion of the first subscription data requested by the first request information based on the first CAG identifier.

[0194] Optionally, the core network element is a NEF network element. Determining whether to allow the creation, update, or deletion of the first subscription data requested by the first request information based on the first CAG identifier includes: matching the first CAG identifier with preset configuration information to determine whether to allow the creation, update, or deletion of the first subscription data requested by the first request information.

[0195] Optionally, the core network element is a UDM network element. Determining whether to allow the creation, update, or deletion of the first subscription data requested by the first request information based on the first CAG identifier includes: matching the first CAG identifier with the subscription data of the terminal device to determine whether to allow the creation, update, or deletion of the first subscription data requested by the first request information.

[0196] Optionally, the core network element is a first AF network element. Determining whether to allow the creation, update, or deletion of the first subscription data requested by the first request information based on the first CAG identifier includes: matching the first CAG identifier with preset configuration information to determine whether to allow the creation, update, or deletion of the first subscription data requested by the first request information.

[0197] S330. Send a first response message, which indicates that the creation, updating or deletion of the first contract data failed.

[0198] Specifically, if the core network element determines that the creation, update, or deletion of the first contract data requested by the first request information is not allowed, the core network element will send a first response information to the requester of the first request information to inform the requester that the creation, update, or deletion of the first contract data has failed.

[0199] In one implementation, the first request information is used to request the creation of the first contract data. When the core network element determines, based on the first CAG identifier, that the creation of the first contract data requested by the first request information is not allowed, the first response information sent is used to indicate that the creation of the first contract data has failed.

[0200] In one implementation, the first request information is used to request the update of the first subscription data. When the core network element determines, based on the first CAG identifier, that the update of the first subscription data requested by the first request information is not allowed, the first response information sent is used to indicate that the update of the first subscription data has failed.

[0201] In one implementation, the first request information is used to request the deletion of the first subscription data. When the core network element determines, based on the first CAG identifier, that the deletion of the first subscription data requested by the first request information is not allowed, the first response information sent is used to indicate that the deletion of the first subscription data has failed.

[0202] For example, the first response information includes the reason for the failure to create, update, or delete the first contract data, such as the reason that the creation, update, or deletion of the first contract data is not permitted.

[0203] Optionally, the core network element is a NEF network element, which sends a first response message, including sending the first response message to the first AF network element. In this case, the first response message can be called "Nnef_ParameterProvision_Create / Update / Delete response".

[0204] Optionally, this core network element is a UDM network element, which sends a first response message, including sending the first response message to the NEF network element. In this case, the first response message can be called a "Nudm_ParameterProvision_Create / Update / Delete response".

[0205] Optionally, the core network element is the first AF network element, which sends the first response information, including sending the first response information to the terminal device. In this case, the first response information can be sent to the terminal device through an application (APP), and the specific sending method depends on the terminal device; this application does not limit this.

[0206] Understandably, if a core network element determines, based on the first CAG identifier, that it is permitted to execute the creation, update, or deletion of the first subscription data requested by the first request information, it sends a second request information, which includes the first CAG identifier, and is used to request the creation, update, or deletion of the first subscription data; or, it sends a first response information, which is used to indicate that the creation, update, or deletion of the first subscription data was successful.

[0207] For example, if the core network element is a NEF network element, then sending the second request information includes sending the second request information to the UDM network element.

[0208] For example, if the core network element is a UDM network element, then sending the first response information includes sending the first response information to the NEF network element.

[0209] For example, if the core network element is the first AF network element, then sending the second request information includes: sending the second request information to the terminal device.

[0210] In this embodiment, the core network element can determine, based on the first CAG identifier in the first request information, that the creation, updating, or deletion of subscription data corresponding to the first CAG identifier in the terminal device requested by the first request information is not permitted. Therefore, when the requester of the first request information provides CAG parameters, the core network element can further verify whether the subscription data corresponding to the CAG parameter is allowed to be created, updated, or deleted, and thus determine whether the creation, updating, or deletion of subscription data requested by the first request information is permitted. If the creation, updating, or deletion of subscription data requested by the first request information is not permitted, a failure to create, update, or delete the subscription data corresponding to the first CAG identifier is reported. Therefore, the accuracy of creating, updating, or deleting subscription data can be improved.

[0211] Figure 4 is a schematic diagram of a communication method 400 provided in an embodiment of this application. For ease of description, an example is given using NEF network elements, a first AF network element, and a UDM network element as core network elements. The first AF network element can be replaced by its components (e.g., a chip, chip system, circuit, or communication module), the NEF network element can be replaced by its components (e.g., a chip, chip system, circuit, or communication module), and the UDM network element can be replaced by its components (e.g., a chip, chip system, circuit, or communication module). Furthermore, the steps described below as being performed by a single execution entity can also be divided into steps performed by multiple execution entities, which can be logically and / or physically separated. The method 400 shown in Figure 4 may include the following steps.

[0212] S410, the first AF network element sends request information #1 to the NEF network element.

[0213] Correspondingly, the NEF network element receives request information #1 from the first AF network element.

[0214] The request information #1 includes a first CAG identifier, which is used to request the creation, updating or deletion of the first contract data corresponding to the first CAG identifier in the terminal device.

[0215] It should be noted that in method 400, request information #1 is an example of the first request information in method 300. That is, in method 400, request information #1 is the aforementioned first request information.

[0216] In this embodiment, the request information #1 includes the identifier of the first AF network element. Upon receiving the request information #1, the NEF network element verifies whether the first AF network element is authorized to provide parameters based on its identifier, or in other words, verifies whether the first AF network element is authorized to invoke the service of creating, updating, or deleting subscription data. If the NEF network element verifies that the first AF network element is not authorized to provide parameters, the NEF network element reports back to the first AF network element that the first AF network element is not authorized to provide parameters. If the NEF network element verifies that the first AF network element is authorized to provide parameters, the NEF network element further determines whether to allow the execution of the creation, updating, or deletion of the first subscription data requested by the request information #1 based on the first CAG identifier. The implementation method of the NEF network element verifying whether the first AF network element is authorized to provide parameters based on its identifier can be found in existing technology or in step S220 above, and will not be repeated here.

[0217] It is understandable that the NEF network element determines whether to allow the creation, update, or deletion of the first subscription data requested by request information #1 based on the first CAG identifier, which occurs after the first AF network element has passed verification. In other words, this application embodiment describes the process using the first AF network element passing verification as an example.

[0218] For a detailed description of the request information #1, please refer to step S310 above, which will not be repeated here.

[0219] S420 and NEF network elements determine whether to allow the execution of the request information #1 to create, update, or delete the first contract data based on the first CAG identifier.

[0220] For example, if request information #1 requests the creation of the first contract data, the NEF network element will determine whether to allow the execution of the creation of the first contract data requested by request information #1 based on the first CAG identifier.

[0221] For example, if request information #1 requests to update the first contractual data, the NEF network element will determine whether to allow the execution of the update of the first contractual data requested by request information #1 based on the first CAG identifier.

[0222] For example, if request information #1 requests the deletion of the first subscription data, the NEF network element will determine whether to allow the deletion of the first subscription data requested by request information #1 based on the first CAG identifier.

[0223] Specifically, the NEF network element matches the first CAG identifier with preset configuration information to determine whether to allow the creation, update, or deletion of the first subscription data requested by request information #1. The preset configuration information includes the conditions for creating, updating, or deleting the subscription data of the terminal device.

[0224] In one implementation, the preset configuration information includes one or more CAG identifiers. Matching the first CAG identifier with the preset configuration information can be understood as comparing the first CAG identifier with the multiple CAG identifiers.

[0225] For example, if the contract data corresponding to the one or more CAG identifiers is allowed to be created, updated, or deleted, then the first CAG identifier is matched with the plurality of CAG identifiers. If the first CAG identifier belongs to the plurality of CAG identifiers, then it is determined that the creation, updating, or deletion of the first contract data requested by request information #1 is allowed. If the first CAG identifier does not belong to the plurality of CAG identifiers, then it is determined that the creation, updating, or deletion of the first contract data requested by request information #1 is not allowed.

[0226] For example, there are 200 CAG IDs, numbered CAG ID 1 to CAG ID 200. Assuming that the contract data corresponding to these 200 CAG IDs can be created, updated, or deleted, and the first CAG ID is CAG ID 1, then if the first CAG ID is among 1 to 200, then the creation, update, or deletion of the first contract data requested by request information #1 is allowed. If the first CAG ID is CAG ID 201, then if the first CAG ID is not among 1 to 200, then the creation, update, or deletion of the first contract data requested by request information #1 is not allowed.

[0227] For example, if the contract data corresponding to one or more CAG identifiers is not allowed to be created, updated, or deleted, then the first CAG identifier is matched with the plurality of CAG identifiers. If the first CAG identifier does not belong to the plurality of CAG identifiers, then it is determined that the creation, updating, or deletion of the first contract data requested by request information #1 is allowed. If the first CAG identifier belongs to the plurality of CAG identifiers, then it is determined that the creation, updating, or deletion of the first contract data requested by request information #1 is not allowed.

[0228] For example, there are 200 CAG IDs, numbered CAG ID 1 to CAG ID 200. Assuming that the contract data corresponding to these 200 CAG IDs is not allowed to be created, updated, or deleted, and the first CAG ID is CAG ID 1, then if the first CAG ID is among 1 to 200, then the creation, update, or deletion of the first contract data requested by request information #1 is not allowed. Assuming that the first CAG ID is CAG ID 201, then if the first CAG ID is not among 1 to 200, then the creation, update, or deletion of the first contract data requested by request information #1 is allowed.

[0229] For example, some of the multiple CAG identifiers are first-type identifiers, and some of the multiple CAG identifiers are second-type identifiers. The contract data corresponding to the first-type identifiers is allowed to be created, updated, or deleted, while the contract data corresponding to the second-type identifiers is not allowed to be created, updated, or deleted. In this case, the first CAG identifier is matched with the multiple CAG identifiers. If the first CAG identifier belongs to the first-type identifier, then it is determined that the creation, updating, or deletion of the first contract data requested by request information #1 is allowed. If the first CAG identifier belongs to the second-type identifier, then it is determined that the creation, updating, or deletion of the first contract data requested by request information #1 is not allowed.

[0230] For example, there are 200 CAG IDs, ranging from CAG ID 1 to CAG ID 200. Assume CAGs with IDs 1-100 are classified as Category 1 identifiers, and CAGs with IDs 101-200 as Category 2 identifiers. Then, the contract data corresponding to CAG IDs with IDs in the range of 1-100 is allowed to be created, updated, or deleted, while the contract data corresponding to CAG IDs with IDs in the range of 101-200 is not allowed to be created, updated, or deleted. If the first CAG ID is CAG ID 1, and the first CAG ID is within the range of 1-100, then the creation, updating, or deletion of the first contract data requested by request information #1 is allowed. If the first CAG ID is CAG ID 110, and the first CAG ID is within the range of 101-200, then the creation, updating, or deletion of the first contract data requested by request information #1 is not allowed.

[0231] In one implementation, the request information #1 includes the identifier of a first AF network element, and the preset configuration information includes one or more CAG identifiers and one or more AF network element identifiers. Matching the first CAG identifier with the preset configuration information to determine whether to allow the creation, update, or deletion of the first subscription data requested by the request information #1 includes: matching the first CAG identifier with the one or more CAG identifiers, and matching the identifier of the first AF network element with the identifiers of the one or more AF network elements to determine whether to allow the creation, update, or deletion of the first subscription data requested by the request information #1.

[0232] Specifically, determining whether to allow the creation, update, or deletion of the first contract data requested by request information #1 includes: determining whether to allow the creation, update, or deletion of the first contract data requested by request information #1; or determining whether to disallow the creation, update, or deletion of the first contract data requested by request information #1.

[0233] In one example, the subscription data corresponding to the one or more CAG identifiers can be created, updated, or deleted, and the identifiers of the one or more AF network elements can be used to create, update, or delete the subscription data corresponding to the multiple CAG identifiers. Matching the first CAG identifier and the identifier of the first AF network element with the preset configuration information can be understood as comparing the first CAG identifier with the one or more CAG identifiers, and comparing the identifier of the first AF network element with the identifiers of the one or more AF network elements. When the first CAG identifier belongs to the one or more CAG identifiers and the identifier of the first AF network element belongs to the identifiers of the one or more AF network elements, it is determined that the creation, updating, or deletion of the first subscription data requested by request information #1 is permitted; when the first CAG identifier does not belong to the one or more CAG identifiers or the identifier of the first AF network element does not belong to the identifiers of the one or more AF network elements, it is determined that the creation, updating, or deletion of the first subscription data requested by request information #1 is not permitted.

[0234] In one example, the subscription data corresponding to the one or more CAG identifiers is not allowed to be created, updated, or deleted, and the identifiers of the one or more AF network elements are not allowed to be created, updated, or deleted. The first CAG identifier and the identifier of the first AF network element are then matched with the preset configuration information. This can be understood as comparing the first CAG identifier with the one or more CAG identifiers, and comparing the identifier of the first AF network element with the identifiers of the one or more AF network elements. If the first CAG identifier does not belong to the one or more CAG identifiers and the identifier of the first AF network element does not belong to the identifier of the one or more AF network elements, then the creation, update, or deletion of the first subscription data requested by request information #1 is allowed; if the first CAG identifier belongs to the one or more CAG identifiers or the identifier of the first AF network element belongs to the identifier of the one or more AF network elements, then the creation, update, or deletion of the first subscription data requested by request information #1 is not allowed.

[0235] In one example, the subscription data corresponding to the one or more CAG identifiers is allowed to be created, updated, or deleted, while the identifiers of the one or more AF network elements are not allowed to be created, updated, or deleted. The first CAG identifier and the identifier of the first AF network element are matched with the preset configuration information. This can be understood as comparing the first CAG identifier with the one or more CAG identifiers, and comparing the identifier of the first AF network element with the identifiers of the one or more AF network elements. If the first CAG identifier belongs to the one or more CAG identifiers and the identifier of the first AF network element does not belong to the identifier of the one or more AF network elements, then the creation, update, or deletion of the first subscription data requested by request information #1 is allowed; if the first CAG identifier does not belong to the one or more CAG identifiers or the identifier of the first AF network element belongs to the identifier of the one or more AF network elements, then the creation, update, or deletion of the first subscription data requested by request information #1 is not allowed.

[0236] In one example, the subscription data corresponding to the one or more CAG identifiers is not allowed to be created, updated, or deleted, while the identifiers of the one or more AF network elements are allowed to be created, updated, or deleted. The first CAG identifier and the identifier of the first AF network element are matched with the preset configuration information. This can be understood as comparing the first CAG identifier with the one or more CAG identifiers, and comparing the identifier of the first AF network element with the identifiers of the one or more AF network elements. If the first CAG identifier does not belong to the one or more CAG identifiers and the identifier of the first AF network element belongs to the identifier of the one or more AF network elements, then the creation, update, or deletion of the first subscription data requested by request information #1 is allowed; if the first CAG identifier belongs to the one or more CAG identifiers or the identifier of the first AF network element does not belong to the identifier of the one or more AF network elements, then the creation, update, or deletion of the first subscription data requested by request information #1 is not allowed.

[0237] In one example, some of the multiple CAG identifiers are first-class identifiers, and some of the multiple CAG identifiers are second-class identifiers. The subscription data corresponding to the first-class identifiers can be created, updated, or deleted, while the subscription data corresponding to the second-class identifiers cannot be created, updated, or deleted. The identifiers of the one or more AF network elements can be used to create, update, or delete the subscription data corresponding to the multiple CAG identifiers. In this case, when matching the first CAG identifier, the identifier of the first AF network element, and the multiple CAG identifiers, if the first CAG identifier belongs to the first-class identifiers and the identifier of the first AF network element belongs to the identifiers of the one or more AF network elements, then it is determined that the creation, updating, or deletion of the first subscription data requested by request information #1 is permitted. If the first CAG identifier belongs to the second-class identifiers or the identifier of the first AF network element does not belong to the identifiers of the one or more AF network elements, then it is determined that the creation, updating, or deletion of the first subscription data requested by request information #1 is not permitted.

[0238] For example, consider 200 CAG IDs and 4 AF (Automatic AF) element IDs. The 200 CAG IDs are CAG ID 1 to CAG ID 200, and the 4 AF element IDs are AF ID 1 to AF ID 4. Assume CAGs with IDs 1-100 are classified as Category 1 identifiers, and CAGs with IDs 101-200 are classified as Category 2 identifiers. Then, the subscription data corresponding to CAG IDs with IDs in the range 1-100 can be created, updated, or deleted. Similarly, the subscription data corresponding to CAG IDs with IDs 1-4 can be created, deleted, updated, or deleted. However, the subscription data corresponding to CAG IDs with IDs in the range 101-200 cannot be created, updated, or deleted. If the first CAG identifier is CAG ID 1, the first AF network element identifier is AF ID 3, the first CAG identifier is between 1 and 100, and the first AF network element identifier belongs to AF ID 1 to AF ID 4, then it is determined that the creation, updating, or deletion of the first subscription data requested by request information #1 is allowed; if the first CAG identifier is CAG ID 110, the first AF network element identifier is AF ID 6, then the first CAG identifier is between 101 and 200, or the first AF network element identifier does not belong to AF ID 1 to AF ID 4, then it is determined that the creation, updating, or deletion of the first subscription data requested by request information #1 is not allowed.

[0239] In one example, some of the multiple CAG identifiers are first-class identifiers, and some of the multiple CAG identifiers are second-class identifiers. The subscription data corresponding to the first-class identifiers is allowed to be created, updated, or deleted, while the subscription data corresponding to the second-class identifiers is not allowed to be created, updated, or deleted. The identifiers of the one or more AF network elements are not allowed to be used to create, update, or delete the subscription data corresponding to the multiple CAG identifiers. In this case, when matching the first CAG identifier, the identifier of the first AF network element, and the multiple CAG identifiers, if the first CAG identifier belongs to the first-class identifiers and the identifier of the first AF network element does not belong to the identifiers of the one or more AF network elements, then it is determined that the creation, updating, or deletion of the first subscription data requested by request information #1 is allowed. If the first CAG identifier belongs to the second-class identifiers or the identifier of the first AF network element belongs to the identifiers of the one or more AF network elements, then it is determined that the creation, updating, or deletion of the first subscription data requested by request information #1 is not allowed.

[0240] For example, consider 200 CAG IDs and 4 AF (Automatic AF) element IDs. The 200 CAG IDs are CAG ID 1 to CAG ID 200, and the 4 AF element IDs are AF ID 1 to AF ID 4. Assume CAGs with IDs 1-100 are classified as Category 1 identifiers, and CAGs with IDs 101-200 are classified as Category 2 identifiers. Then, the subscription data corresponding to CAG IDs with IDs in the range of 1-100 can be created, updated, or deleted. The subscription data corresponding to CAG IDs with IDs 1-4 cannot be created, deleted, updated, or deleted. The subscription data corresponding to CAG IDs with IDs in the range of 1-200 cannot be created, updated, or deleted. If the first CAG identifier is CAG ID 1, the first AF network element identifier is AF ID 5, the first CAG identifier is between 1 and 100, and the first AF network element identifier does not belong to AF ID 1 to AF ID 4, then it is determined that the creation, updating, or deletion of the first subscription data requested by request information #1 is allowed; if the first CAG identifier is CAG ID 110, the first AF network element identifier is AF ID 3, then the first CAG identifier is between 101 and 200, or the first AF network element identifier belongs to AF ID 1 to AF ID 4, then it is determined that the creation, updating, or deletion of the first subscription data requested by request information #1 is not allowed.

[0241] In one example, some of the multiple CAG identifiers are of type 1, some are of type 2, and the contract data corresponding to the type 1 identifiers is allowed to be created, updated, or deleted, while the contract data corresponding to the type 2 identifiers is not allowed to be created, updated, or deleted. Some of the multiple AF network element identifiers are of type 3, and the AF network element corresponding to the type 3 identifier is allowed to create, update, or delete the contract data corresponding to the CAG identifiers belonging to type 1. Some of the multiple AF network element identifiers are of type 4, and the type 4 identifiers are not allowed to create, update, or delete the contract data corresponding to the CAG identifiers belonging to type 2. In this case, when matching the first CAG identifier, the identifier of the first AF network element, and the multiple CAG identifiers, if the first CAG identifier belongs to type 1 and the identifier of the first AF network element belongs to type 3, then it is determined that the creation, updating, or deletion of the first contract data requested by request information #1 is allowed. If the first CAG identifier belongs to the second type of identifier or the identifier of the first AF network element belongs to the fourth type of identifier, then it is determined that the creation, updating or deletion of the first contract data requested by request information #1 is not allowed.

[0242] For example, there are 200 CAG IDs and 4 AF network element IDs. The 200 CAG IDs are CAG ID 1 to CAG ID 200, and the 4 AF network element IDs are AF ID 1 to AF ID 4. Assume that CAGs with IDs from 1 to 100 are the first type of identifiers, CAGs with IDs from 101 to 200 are the second type of identifiers, AF ID 1 and AF ID 2 belong to the third type of identifiers, and AF ID 3 and AF ID 4 belong to the fourth type of identifiers. Contractual data corresponding to CAG IDs with IDs in the range of 1 to 100 can be created, updated, or deleted. AF ID 1 and AF ID 2 can be created, deleted, updated, or deleted. Contractual data corresponding to CAG IDs with IDs in the range of 1 to 100 cannot be created, updated, or deleted. AF ID 3 and AF ID 4 cannot be created, deleted, updated, or deleted. If the first CAG identifier is CAG ID 1, the first AF network element identifier is AF ID 1, the first CAG identifier is between 1 and 100, and the first AF network element identifier belongs to AF ID 1, then it is determined that the creation, updating, or deletion of the first subscription data requested by request information #1 is allowed; if the first CAG identifier is CAG ID 110, the first AF network element identifier is AF ID 3, then the first CAG identifier is between 101 and 200, or the first AF network element identifier belongs to AF ID 3, then it is determined that the creation, updating, or deletion of the first subscription data requested by request information #1 is not allowed.

[0243] In one example, some of the multiple CAG identifiers are of type 1, some are of type 2, and the contract data corresponding to the type 1 identifiers is allowed to be created, updated, or deleted, while the contract data corresponding to the type 2 identifiers is not allowed to be created, updated, or deleted. Some of the multiple AF network element identifiers are of type 3, and the AF network element corresponding to the type 3 identifier is not allowed to create, update, or delete contract data corresponding to the type 1 CAG identifiers. Some of the multiple AF network element identifiers are of type 4, and the type 4 identifiers are allowed to create, update, or delete contract data corresponding to the type 2 CAG identifiers. In this case, when matching the first CAG identifier, the identifier of the first AF network element, and the multiple CAG identifiers, if the first CAG identifier belongs to type 1 and the identifier of the first AF network element does not belong to type 3, then it is determined that the creation, updating, or deletion of the first contract data requested by request information #1 is allowed. If the first CAG identifier belongs to the second type of identifier or the identifier of the first AF network element does not belong to the fourth type of identifier, then it is determined that the creation, update or deletion of the first contract data requested by request information #1 is not allowed.

[0244] For example, there are 200 CAG IDs and 4 AF network element IDs. The 200 CAG IDs are CAG ID 1 to CAG ID 200, and the 4 AF network element IDs are AF ID 1 to AF ID 4. Assume that CAGs with IDs from 1 to 100 are the first type of identifiers, CAGs with IDs from 101 to 200 are the second type of identifiers, AF ID 1 and AF ID 2 belong to the third type of identifiers, and AF ID 3 and AF ID 4 belong to the fourth type of identifiers. Contractual data corresponding to CAG IDs with IDs in the range of 1 to 100 can be created, updated, or deleted. AF ID 1 and AF ID 2 are not allowed to be created, deleted, updated, or deleted. Contractual data corresponding to CAG IDs with IDs in the range of 1 to 100 are not allowed to be created, updated, or deleted. Contractual data corresponding to CAG IDs with IDs in the range of 101 to 200 are allowed to be created, deleted, updated, or deleted. AF ID 3 and AF ID 4 are allowed to be created, deleted, updated, or deleted. If the first CAG identifier is CAG ID 1, the first AF network element identifier is AF ID 5, the first CAG identifier is between 1 and 100, and the first AF network element identifier does not belong to AF ID 1 and AF ID 2, then it is determined that the creation, updating, or deletion of the first subscription data requested by request information #1 is allowed; if the first CAG identifier is CAG ID 110, the first AF network element identifier is AF ID 1, then the first CAG identifier is between 101 and 200, or the first AF network element identifier does not belong to AF ID 3 and AF ID 4, then it is determined that the creation, updating, or deletion of the first subscription data requested by request information #1 is not allowed.

[0245] In one implementation, the request information #1 includes the identifier of a first AF network element. The preset configuration information includes one or more CAG identifiers and the identifiers of one or more AF network elements that are allowed to create, update, or delete subscription data corresponding to the one or more CAG identifiers. The first CAG identifier is matched with the preset configuration information to determine whether to allow the creation, update, or deletion of the first subscription data requested by the request information #1. This includes: if the first CAG identifier does not belong to the one or more CAG identifiers or the identifier of the first AF network element does not belong to the identifier of the one or more AF network elements corresponding to the first CAG identifier, then it is determined that the creation, update, or deletion of the first subscription data requested by the request information #1 is not allowed; if the first CAG identifier belongs to the one or more CAG identifiers and the identifier of the first AF network element belongs to the identifier of the one or more AF network elements corresponding to the first CAG identifier, then it is determined that the creation, update, or deletion of the first subscription data requested by the request information #1 is allowed.

[0246] For example, the identifier of the one or more AF network elements corresponds to the one or more CAG identifiers. The correspondence between the identifier of the one or more AF network elements and the one or more CAG identifiers includes one or more of the following: a one-to-one correspondence between the identifier of the one or more AF network elements and the one or more CAG identifiers; each identifier of the plurality of AF network elements corresponds to at least two CAG identifiers among the plurality of CAG identifiers; each CAG identifier corresponds to at least two identifiers of the plurality of AF network elements; one CAG identifier corresponds to the identifier of the one or more AF network elements; and one identifier of an AF network element corresponds to the one or more CAG identifiers. In other words, the plurality of CAG identifiers correspond to the identifiers of one or more AF network elements, or the plurality of AF network element identifiers correspond to one or more ACG identifiers.

[0247] For example, multiple CAG identifiers and the identifiers of one or more AF network elements that allow the creation, updating, or deletion of the subscription data corresponding to the multiple CAG identifiers can be understood as allowing the subscription data corresponding to the multiple CAG identifiers to be created, updated, or deleted. In this case, the preset configuration information also includes the identifiers of one or more AF network elements corresponding to the multiple CAG identifiers, and the identifiers of these one or more AF network elements are allowed to create, update, or delete the subscription data corresponding to the multiple CAG identifiers.

[0248] In one implementation, the first CAG identifier is matched with the plurality of CAG identifiers, and the identifier of the first AF network element is matched with the identifiers of the one or more AF network elements. If the first CAG identifier belongs to the plurality of CAG identifiers, and the identifier of the first AF network element belongs to the identifier of the one or more AF network elements corresponding to the first CAG identifier, then it is determined that the creation, updating or deletion of the first contract data requested by the request information #1 is allowed.

[0249] For example, there are 100 CAG IDs and two AF network element IDs that allow the creation, updating, or deletion of the subscription data corresponding to these 100 CAG IDs. The 100 CAG IDs are CAG ID 1 to CAG ID 100, and the two AF network element IDs are AF ID 1 to AF ID 2. The subscription data corresponding to these 100 CAG IDs can be created, updated, or deleted. Assuming the first CAG ID is CAG ID 1 and the first AF network element ID is AF ID 1, then the first CAG ID belongs to the 100 CAG IDs, and the first AF network element ID belongs to either AF ID 1 or AF ID 2. Therefore, it is determined that the creation, updating, or deletion of the first subscription data requested by request information #1 is allowed.

[0250] For another example, consider 100 CAG IDs and the identifiers of two AF network elements that allow the creation, updating, or deletion of the subscription data corresponding to these 100 CAG IDs. The 100 CAG IDs are CAG ID 1 to CAG ID 100, and the two AF network element IDs are AF ID 1 to AF ID 2. The subscription data corresponding to these 100 CAG IDs can be created, updated, or deleted. CAG IDs 1 to 50 correspond to AF ID 1, and CAG IDs 51 to 100 correspond to AF ID 2. Assuming the first CAG identifier is CAG ID 1 and the first AF network element identifier is AF ID 1, then the first CAG identifier belongs to CAG ID 1 to CAG ID 50, and the first AF network element identifier belongs to AF ID 1. Therefore, it is determined that the creation, updating, or deletion of the first subscription data requested by request information #1 is permitted.

[0251] In one implementation, the first CAG identifier is matched with the plurality of CAG identifiers, and the identifier of the first AF network element is matched with the identifiers of the one or more AF network elements. If the first CAG identifier does not belong to the plurality of CAG identifiers, or the identifier of the first AF network element does not belong to the identifier of the one or more AF network elements corresponding to the first CAG identifier, it is determined that the creation, update or deletion of the first contract data requested by the request information #1 is not allowed.

[0252] For example, there are 100 CAG IDs and the identifiers of two AF network elements that allow the creation, updating, or deletion of the contract data corresponding to these 100 CAG IDs. These 100 CAG IDs are CAG ID 1 to CAG ID 100, and the 1 AF network element ID is AF ID 1 to AF ID 2. The contract data corresponding to these 100 CAG IDs can be created, updated, or deleted. Assuming the first CAG identifier is CAG ID 1 and the first AF network element identifier is AF ID 1, then if the first CAG identifier belongs to one of the 100 CAG IDs, or the first AF network element identifier belongs to one of AF ID 1 and AF ID 2, then it is determined that the creation, updating, or deletion of the first contract data requested by request information #1 is allowed.

[0253] In one implementation, the request information #1 includes the identifier of a first AF network element. The preset configuration information includes multiple CAG identifiers and the identifiers of one or more AF network elements that are not allowed to create, update, or delete subscription data corresponding to the multiple CAG identifiers. The first CAG identifier is matched with the preset configuration information to determine whether to allow the creation, update, or deletion of the first subscription data requested by the request information #1. This includes: if the first CAG identifier belongs to the multiple CAG identifiers or the identifier of the first AF network element belongs to the identifier of one or more AF network elements corresponding to the first CAG identifier, it is determined that the creation, update, or deletion of the first subscription data requested by the request information #1 is not allowed; if the first CAG identifier does not belong to the multiple CAG identifiers and the identifier of the first AF network element does not belong to the identifier of one or more AF network elements corresponding to the first CAG identifier, it is determined that the creation, update, or deletion of the first subscription data requested by the request information #1 is allowed.

[0254] Furthermore, based on the determined result, the NEF network element will send different information to different network elements, specifically in the following two cases: Case 1 and Case 2.

[0255] Scenario 1: The NEF network element determines that the request to create, update, or delete the first contract data requested by request information #1 is not allowed. This specifically includes step S421a.

[0256] S421a, NEF network element sends response information #1 to the first AF network element.

[0257] Correspondingly, the first AF network element receives response information #1 from the NEF network element.

[0258] Response information #1 indicates that the creation, updating, or deletion of the first contract data failed.

[0259] It should be noted that in method 400, response information #1 is an example of the first response information in method 300. That is, in method 400, response information #1 is the aforementioned first response information.

[0260] For a detailed description of response information #1, please refer to step S330 above, which will not be repeated here.

[0261] Scenario 2: The NEF network element determines that the request to create, update, or delete the first subscription data requested by request information #1 is permitted. This specifically includes steps S422a to S422d.

[0262] S422a, NEF network element sends request information #2 to UDM network element.

[0263] Correspondingly, the UDM network element receives request information #2 from the NEF network element.

[0264] The request information #2 includes a first CAG identifier, which is used to request the creation, updating or deletion of the first contract data.

[0265] It should be noted that in method 400, request information #2 is an example of the second request information in method 300. That is, in method 400, request information #2 is the aforementioned second request information.

[0266] In one implementation, request message #1 is used to request the creation of the first subscription data. Then, when the NEF network element determines, based on the first CAG identifier, that it is permitted to execute the creation of the first subscription data requested by request message #1, it sends request message #2 to request the creation of the first subscription data. Request message #2 can be referred to as "Nudm_ParameterProvision_Create request".

[0267] In one implementation, request message #1 is used to request an update of the first subscription data. When the NEF network element determines, based on the first CAG identifier, that it is permissible to execute the update of the first subscription data requested by request message #1, it sends request message #2 to request an update of the first subscription data. Request message #2 can be referred to as "Nudm_ParameterProvision_Update request".

[0268] For example, request information #2 also includes a first valid duration. A description of the first valid duration can be found in step S310 above, and will not be repeated here.

[0269] In one implementation, request message #1 is used to request the deletion of the first subscription data. When the NEF network element determines, based on the first CAG identifier, that it is permissible to execute the deletion of the first subscription data requested by request message #1, it sends request message #2 to request the creation of the first subscription data. Request message #2 can be referred to as "Nudm_ParameterProvision_Delete request".

[0270] For example, request information #2 also includes the identifier of the terminal device.

[0271] Furthermore, the UDM network element determines whether to create, update, or delete the first subscription data based on the received request information #2. This specifically includes the following steps:

[0272] The S422b and UDM network elements determine whether to create, update, or delete the first contract data based on the first CAG identifier.

[0273] Specifically, the UDM network element first obtains the subscription data of the terminal device based on the terminal device's identifier. Then, it matches the terminal device's subscription data with the first CAG identifier. If the terminal device's subscription data includes the first CAG identifier, the first subscription data corresponding to the first CAG identifier can be created, updated, or deleted. If the terminal device's subscription data does not include the first CAG identifier, it is considered that the first subscription data corresponding to the first CAG identifier cannot be updated or deleted, but the first subscription data can be created. This is because the subscription data corresponding to the first CAG identifier is allowed to be created. Therefore, even if the terminal device's subscription data does not contain the first CAG identifier, the subscription data corresponding to the first CAG identifier can still be created, that is, the first subscription data corresponding to the first CAG identifier can be added to the terminal device's subscription data.

[0274] The implementation method of the UDM network element obtaining the subscription data of the terminal device based on the terminal device's identifier can be referred to steps S222b to S223c above, and will not be repeated here.

[0275] In one implementation, request information #2 is used to request the creation of first subscription data. If the terminal device's subscription data includes the subscription data corresponding to the first CAG identifier, then the UDM will not add the first subscription data corresponding to the first CAG identifier to the terminal device's subscription data; in this case, the creation of the first subscription data is considered to have failed. If the terminal device's subscription data does not include the subscription data corresponding to the first CAG identifier, then the UDM network element adds the first subscription data corresponding to the first CAG identifier to the terminal device's subscription data. That is, in this case, the first CAG identifier is added to the allowed CAG list included in the terminal device's subscription data, and the creation of the first subscription data is considered to have succeeded. Thus, the terminal device can access the CAG cell corresponding to the first CAG identifier.

[0276] In one implementation, request information #2 is used to request an update to the first subscription data. The UDM network element needs to determine whether the subscription data acquired from the terminal device includes the first CAG identifier.

[0277] For example, if the subscription data of the terminal device includes the first CAG identifier, the first subscription data can be updated. For instance, if request information #2 also includes a first validity period, the second validity period in the first subscription data corresponding to the first CAG identifier in the terminal device will be updated to the first validity period. For example, if the second validity period originally corresponding to the first CAG identifier was 1 hour, and the first validity period included in request information #2 is 2 hours, then the UDM will update the second validity period in the first subscription data from 1 hour to 2 hours. As another example, if request information #2 does not include the first validity period, then the UDM network element will update the second validity period corresponding to the first subscription data to an infinite length.

[0278] For example, if the first CAG identifier is not included in the subscription data of the terminal device, the first subscription data cannot be updated, that is, the UDM network element fails to update the first subscription data.

[0279] In one implementation, request information #2 is used to request the deletion of the first subscription data. The UDM network element needs to determine whether the acquired subscription data of the terminal device includes the first CAG identifier. If the terminal device's subscription data includes the first CAG identifier, the first subscription data can be deleted. That is, the first subscription data is deleted from the terminal device's subscription data. If the terminal device's subscription data does not include the first CAG identifier, the first subscription data cannot be deleted, meaning the UDM network element fails to delete the first subscription data.

[0280] The S422c and UDM network elements send response information #2 to the NEF network element.

[0281] Correspondingly, the NEF network element receives response information #2 from the UDM network element.

[0282] Response information #2 indicates whether the creation, updating, or deletion of the first contract data was successful.

[0283] In one implementation, if the UDM element determines to create, update, or delete the first subscription data, then response information #2 is used to indicate that the creation, update, or deletion of the first subscription data was successful.

[0284] For example, response information #2 indicates that the creation of the first subscription data was successful, and the terminal device's subscription data will include this first subscription data. Furthermore, the UDM network element can send the terminal device's subscription data, including the first subscription data, to the UDR network element so that the UDR network element can save it. In this case, response information #2 can be called a "Nudm_ParameterProvision_Create response".

[0285] For example, response information #2 indicates that the update of the first subscription data was successful, and the corresponding validity period in the first subscription data in the terminal device will become the first validity period. Furthermore, the UDM network element can send the updated subscription data of the terminal device to the UDR network element so that the UDR network element can save it. In this case, response information #2 can be called "Nudm_ParameterProvision_Update response".

[0286] For example, response information #2 indicates successful deletion of the first subscription data. In this case, the first subscription data will be deleted from the terminal device, meaning it will no longer be included in the terminal device's subscription data. Furthermore, the UDM network element can send the terminal device's subscription data after the first subscription data has been deleted to the UDR network element, so that the UDR network element can save it. In this case, response information #2 can be called a "Nudm_ParameterProvision_Delete response".

[0287] In one implementation, if the UDM element determines that it will not create, update, or delete the first subscription data, then response information #2 is used to indicate that the creation, update, or deletion of the first subscription data has failed.

[0288] For example, response information #2 includes the reason for the failure to create, update, or delete the first subscription data, such as the first subscription data not being included in the subscription data of the terminal device.

[0289] Furthermore, after receiving the response information #2, the NEF network element will report back to the first AF network element whether the creation, update, or deletion of the first contract data was successful.

[0290] S422d and NEF network elements send response information #3 to the first AF network element.

[0291] Correspondingly, the first AF network element receives response information #3 from the NEF network element.

[0292] Response information #3 is used to indicate whether the creation, updating, or deletion of the first contract data was successful.

[0293] In one implementation, the UDM network element determines whether to create, update, or delete the first subscription data. Response information #2 is used to indicate that the creation, update, or deletion of the first subscription data was successful, and response information #3 is used to indicate that the creation, update, or deletion of the first subscription data was successful.

[0294] For example, response information #3 is used to indicate that the creation of the first contract data was successful. In this case, response information #3 can be called "Nnef_ParameterProvision_Create response".

[0295] For example, response information #3 is used to indicate that the first contract data update was successful. In this case, response information #3 can be called "Nnef_ParameterProvision_Update response".

[0296] For example, response information #3 is used to indicate that the deletion of the first contract data was successful. In this case, response information #3 can be called "Nnef_ParameterProvision_Delete response".

[0297] In one implementation, the UDM network element determines not to create, update, or delete the first subscription data. Response information #2 is used to indicate when the creation, update, or deletion of the first subscription data fails, and response information #3 is used to indicate when the creation, update, or deletion of the first subscription data fails.

[0298] For example, response information #3 includes the reason for the failure to create, update, or delete the first subscription data, such as the first subscription data not being included in the subscription data of the terminal device.

[0299] After receiving response information #3, the first AF network element may optionally save the first CAG identifier. Thus, when the first AF network element receives a request from a terminal device to create, update, or delete the subscription data corresponding to the first CAG identifier, the first AF network element can proactively reject the request based on the saved information.

[0300] In this embodiment, the NEF network element determines whether the subscription data corresponding to the first CAG identifier is allowed to be created, updated, or deleted based on the first CAG identifier provided by the first AF network element, and then determines whether to allow the creation, update, or deletion of the subscription data corresponding to the first CAG identifier in the terminal device requested by request information #1, so as to improve the accuracy of creating, updating, or deleting the subscription data corresponding to the first CAG identifier in the terminal device.

[0301] Figure 5 is a schematic diagram of a communication method 500 provided in an embodiment of this application. For ease of description, the following example uses a UDM network element, a first AF network element, and a NEF network element as core network elements. The first AF network element can be replaced by its components (e.g., a chip, chip system, circuit, or communication module), the NEF network element can be replaced by its components (e.g., a chip, chip system, circuit, or communication module), and the UDM network element can be replaced by its components (e.g., a chip, chip system, circuit, or communication module). Furthermore, the steps described below as being performed by a single execution entity can also be divided into steps performed by multiple execution entities, which can be logically and / or physically separated. The method 500 shown in Figure 5 may include the following steps.

[0302] The S510 and NEF network elements send request information #a to the UDM network element.

[0303] Correspondingly, the UDM network element receives request information #a from the NEF network element.

[0304] In method 500, the request information #a is an example of the first request information in method 300. That is, in method 500, the request information #a is the aforementioned first request information.

[0305] For example, if request information #a requests the creation of the first contractual data, the UDM network element will determine whether to allow the execution of the creation of the first contractual data requested by request information #a based on the first CAG identifier.

[0306] For example, if request information #a requests to update the first contractual data, the UDM network element will determine whether to allow the execution of the update of the first contractual data requested by request information #a based on the first CAG identifier.

[0307] For example, if request information #a requests the deletion of the first subscription data, the UDM network element will determine whether to allow the deletion of the first subscription data requested by request information #a based on the first CAG identifier.

[0308] It should be noted that, in this embodiment, the request information #a includes the identifier of the first AF network element. Before the NEF network element sends the request information #a to the UDM network element, the NEF network element will also receive request information #b from the first AF network element and determine whether the first AF network element is authorized to provide parameters based on the identifier of the first AF network element included in the request information #b. Specifically, this includes steps S501 and S502.

[0309] S501, the first AF network element sends a request message #b to the NEF network element.

[0310] Correspondingly, the NEF network element receives the request information #b from the first AF network element.

[0311] The request information #a is similar to the request information #1 in method 400 above. The relevant description can be found in the description of step S410 in method 400 above, and will not be repeated here.

[0312] S502, NEF network element verification: whether the first AF network element is authorized to provide parameters.

[0313] Specifically, the NEF network element verifies whether the first AF network element is authorized to provide parameters based on its identifier. When the NEF network element verifies that the first AF network element is authorized to provide parameters, it executes step S510 as described above. That is, step S510 occurs when the first AF network element's verification is successful. The implementation method of the NEF network element verifying whether the first AF network element is authorized to provide parameters based on its identifier can be found in existing technology or in step S220 above, and will not be elaborated further here.

[0314] The S520 and UDM network elements determine whether to allow the execution of the request information #a to create, update, or delete the first contract data based on the first CAG identifier.

[0315] In one example, if request information #a is used to request the creation of the first subscription data, and the UDM network element determines, based on the first CAG identifier, that the creation of the first subscription data requested by request information #a is permitted, then the UDM network element adds the first subscription data corresponding to the first CAG identifier to the subscription data of the terminal device. That is, at this time, the first CAG identifier is added to the allowed CAG list included in the terminal device's subscription data. Thus, the terminal device can access the CAG cell corresponding to the first CAG identifier. Conversely, if the UDM network element determines, based on the first CAG identifier, that the creation of the first subscription data requested by request information #a is not permitted, then the UDM network element will not add the first subscription data corresponding to the first CAG identifier to the subscription data of the terminal device.

[0316] In one example, request information #a is used to request an update to the first contractual data. When the UDM network element determines, based on the first CAG identifier, that the update of the first contractual data requested by request information #a is permitted, the first contractual data is updated. For example, if request information #a also includes a first validity period, then the second validity period in the first contractual data corresponding to the first CAG identifier in the terminal device is updated to the first validity period. For instance, if the second validity period originally corresponding to the first CAG identifier was 1 hour, and the first validity period included in request information #a is 2 hours, then the UDM updates the second validity period in the first contractual data from 1 hour to 2 hours. As another example, if request information #a does not include a first validity period, then the UDM network element updates the second validity period corresponding to the first contractual data to 0 hours. When the UDM network element determines, based on the first CAG identifier, that the update of the first contractual data requested by request information #a is not permitted, the UDM network element will not update the first contractual data.

[0317] For a description of the first effective duration, please refer to step S310 above, which will not be repeated here.

[0318] In one example, request message #a is used to request the deletion of the first subscription data. If the UDM network element determines, based on the first CAG identifier, that the creation of the first subscription data requested by request message #a is permitted, then the first subscription data will be deleted from the subscription data of the terminal device. If the UDM network element determines, based on the first CAG identifier, that the deletion of the first subscription data requested by request message #a is not permitted, then the UDM network element will not delete the first subscription data.

[0319] Specifically, the UDM network element matches the first CAG identifier with the subscription data of the terminal device to determine whether to allow the creation, update or deletion of the first subscription data requested by the request information #a.

[0320] For example, the first CAG identifier is matched with the contract data of the terminal device, which can be understood as comparing the first CAG identifier with the contract data of the terminal device.

[0321] In one implementation, the subscription data of the terminal device includes one or more CAG identifiers, and the subscription data corresponding to the one or more CAG identifiers can be created, updated, or deleted. The first CAG identifier is matched with the subscription data of the terminal device to determine whether the creation, update, or deletion of the first subscription data requested by the request information #a is allowed. This includes: if the first CAG identifier does not belong to the plurality of CAG identifiers, it is determined that the creation, update, or deletion of the first subscription data requested by the request information #a is not allowed; if the first CAG identifier belongs to the plurality of CAG identifiers, it is determined that the creation, update, or deletion of the first subscription data requested by the request information #a is allowed.

[0322] Specifically, determining whether to allow the creation, update, or deletion of the first contract data requested by request information #a includes: determining whether to allow the creation, update, or deletion of the first contract data requested by request information #a; or determining whether to disallow the creation, update, or deletion of the first contract data requested by request information #a.

[0323] For example, whether the creation, updating, or deletion of subscription data corresponding to one or more CAG identifiers included in the subscription data of the terminal device is permitted can be indicated by indication information. For instance, the indication information may indicate that the creation, updating, or deletion of subscription data corresponding to the one or more CAG identifiers is permitted; or, the indication information may indicate that the creation, updating, or deletion of subscription data corresponding to the one or more CAG identifiers is not permitted; or, for another example, a first indication information may indicate that the creation, updating, or deletion of subscription data corresponding to some of the multiple CAG identifiers is permitted, and a second indication information may indicate that the creation, updating, or deletion of subscription data corresponding to some of the multiple CAG identifiers is not permitted. In other words, the subscription data of the terminal device may also include one or more indication information, which are used to indicate whether the creation, updating, or deletion of subscription data corresponding to the one or more CAG identifiers is permitted.

[0324] For example, the one or more indication messages are used to indicate whether the subscription data corresponding to the one or more CAG identifiers is allowed to be created, updated, or deleted. The UDM network element can match the first CAG identifier with the plurality of CAG identifiers and the one or more indication messages to determine whether to allow the creation, update, or deletion of the first subscription data requested by the request message #a.

[0325] In one implementation, the indication information is used to indicate that the subscription data corresponding to the one or more CAG identifiers is allowed to be created, updated, or deleted. The first CAG identifier is matched with the subscription data of the terminal device to determine whether the creation, update, or deletion of the first subscription data requested by the request information #a is allowed. This includes: when the first CAG identifier does not belong to the one or more CAG identifiers, determining that the creation, update, or deletion of the first subscription data requested by the request information #a is not allowed; when the first CAG identifier belongs to the one or more CAG identifiers, determining that the creation, update, or deletion of the first subscription data requested by the request information #a is allowed.

[0326] For example, there are 100 CAG IDs, and one instruction message #a. These 100 CAG IDs are CAG ID 1 to CAG ID 100. Suppose that instruction message #a indicates that the contract data corresponding to CAG IDs 1 to CAG ID 100 is allowed to be created, updated, or deleted. If the first CAG ID is CAG ID 1, then the first CAG ID belongs to the 100 CAG IDs indicated by instruction message #a, and therefore, the creation, updating, or deletion of the first contract data requested by instruction message #a is allowed. If the first CAG ID is CAG ID 101, then the first CAG ID belongs to the 100 CAG IDs indicated by instruction message #a, and therefore, the creation, updating, or deletion of the first contract data requested by instruction message #a is not allowed.

[0327] In one implementation, the indication information is used to indicate that the contract data corresponding to the one or more CAG identifiers is not allowed to be created, updated, or deleted. Then, the first CAG identifier is matched against the multiple CAG identifiers. Specifically, if the first CAG identifier does not belong to the one or more CAG identifiers, it is determined that the creation, updating, or deletion of the first contract data requested by request information #a is allowed. If the first CAG identifier belongs to the one or more CAG identifiers, it is determined that the creation, updating, or deletion of the first contract data requested by request information #a is not allowed.

[0328] For example, there are 100 CAG IDs, and one instruction message #a. These 100 CAG IDs are CAG ID 1 to CAG ID 100. Suppose that instruction message #a indicates that the contract data corresponding to CAG IDs 1 to CAG ID 100 cannot be created, updated, or deleted. If the first CAG ID is CAG ID 101, then the first CAG ID does not belong to the 100 CAG IDs indicated by instruction message #a, and therefore, the creation, updating, or deletion of the first contract data requested by instruction message #a is allowed. If the first CAG ID is CAG ID 99, then the first CAG ID belongs to the 100 CAG IDs indicated by instruction message #a, and therefore, the creation, updating, or deletion of the first contract data requested by instruction message #a is not allowed.

[0329] In one implementation, a first instruction indicates that the contractual data corresponding to some of the multiple CAG identifiers is allowed to be created, updated, or deleted, while a second instruction indicates that the contractual data corresponding to some of the multiple CAG identifiers is not allowed to be created, updated, or deleted. In this case, the first CAG identifier is matched with the contractual data to determine that the creation, update, or deletion of the first contractual data requested by the first request information is not allowed. This can be understood as comparing the first CAG identifier with the multiple CAG identifiers. If the first CAG identifier belongs to some of the multiple CAG identifiers indicated by the second instruction information, and does not belong to some of the multiple CAG identifiers indicated by the first instruction information, then the creation, update, or deletion of the first contractual data requested by the first request information is not allowed. Alternatively, if the first CAG identifier belongs to a subset of the multiple CAG identifiers indicated by the first instruction information, and the first CAG identifier does not belong to a subset of the multiple CAG identifiers indicated by the second instruction information, then it is deemed that the creation, updating, or deletion of the first contract data requested by the first request information is not permitted.

[0330] For example, there are 100 CAG IDs, 2 indication messages, where the 100 CAG IDs are CAG ID 1 to CAG ID 100, and the 4 indication messages include indication messages #a to #b. Assume indication message #a indicates that the contract data corresponding to CAG IDs 1 to 50 is allowed to be created, updated, or deleted, and indication message #b indicates that the contract data corresponding to CAG IDs 51 to 100 is not allowed to be created, updated, or deleted. If the first CAG ID is CAG ID 1, then the first CAG ID belongs to the 50 CAG IDs indicated by indication message #a, and therefore the creation, updating, or deletion of the first contract data requested by indication message #a is allowed. If the first CAG ID is CAG ID 78, then the first CAG ID belongs to the 50 CAG IDs indicated by indication message #b, and therefore the creation, updating, or deletion of the first contract data requested by indication message #a is not allowed.

[0331] In one implementation, the request information #a includes the identifier of a first AF network element, and the subscription data of the terminal device includes one or more CAG identifiers, indication information indicating that the subscription data corresponding to the plurality of CAG identifiers can be created, updated, or deleted, and the identifiers of one or more AF network elements that allow the creation, updating, or deletion of the subscription data corresponding to the one or more CAG identifiers. The first CAG identifier is matched with the subscription data of the terminal device to determine whether to allow the creation, updating, or deletion of the first subscription data requested by the request information #a, including: if the first CAG identifier does not belong to the one or more CAG identifiers or the identifier of the first AF network element does not belong to the identifier of the one or more AF network elements corresponding to the first CAG identifier, it is determined that the creation, updating, or deletion of the first subscription data requested by the request information #a is not allowed; if the first CAG identifier belongs to the one or more CAG identifiers and the identifier of the first AF network element belongs to the identifier of the one or more AF network elements corresponding to the first CAG identifier, it is determined that the creation, updating, or deletion of the first subscription data requested by the request information #a is allowed.

[0332] In one example, the first CAG identifier is matched with one or more CAG identifiers, and the identifier of the first AF network element is matched with the identifier of one or more AF network elements. If the first CAG identifier belongs to one or more CAG identifiers, and the identifier of the first AF network element belongs to one or more AF network elements corresponding to the first CAG identifier, then it is determined that the creation, update or deletion of the first contract data requested by the request information #a is allowed.

[0333] For example, there are 100 CAG IDs, each corresponding to one instruction message #a, and the identifiers of two AF network elements that allow the creation, updating, or deletion of the subscription data corresponding to these 100 CAG IDs. These 100 CAG IDs are CAG ID 1 to CAG ID 100, and the one AF network element ID is AF ID 1 to AF ID 2. Instruction message #a indicates that the subscription data corresponding to these 100 CAG IDs is allowed to be created, updated, or deleted. Assuming the first CAG identifier is CAG ID 1 and the first AF network element identifier is AF ID 1, then the first CAG identifier belongs to the 100 CAG IDs, and the first AF network element identifier belongs to either AF ID 1 or AF ID 2. Therefore, it is determined that the creation, updating, or deletion of the first subscription data requested by request message #1 is allowed.

[0334] In one example, the first CAG identifier is matched with one or more CAG identifiers, and the identifier of the first AF network element is matched with the identifiers of one or more AF network elements. If the first CAG identifier does not belong to one or more CAG identifiers, or the identifier of the first AF network element does not belong to the identifier of one or more AF network elements corresponding to the first CAG identifier, it is determined that the creation, updating or deletion of the first contract data requested by the request information #a is not allowed.

[0335] For example, there are 100 CAG IDs, each corresponding to one instruction message #a, and the identifiers of two AF network elements that allow the creation, updating, or deletion of the subscription data corresponding to these 100 CAG IDs. The 100 CAG IDs are CAG ID 1 to CAG ID 100, and the AF network element ID is AF ID 1 to AF ID 2. Instruction message #a indicates that the subscription data corresponding to these 100 CAG IDs is allowed to be created, updated, or deleted. Assuming the first CAG identifier is CAG ID 110 and the first AF network element identifier is AF ID 4, then the first CAG identifier does not belong to any of the 100 CAG IDs, or the first AF network element identifier does not belong to either AF ID 1 or AF ID 2. Therefore, it is determined that the creation, updating, or deletion of the first subscription data requested by request message #a is not permitted.

[0336] In one implementation, the request information #a includes the identifier of a first AF network element, and the subscription data of the terminal device includes one or more CAG identifiers and indication information indicating that the subscription data corresponding to the one or more CAG identifiers is not allowed to be created, updated, or deleted, as well as the identifiers of one or more AF network elements that are not allowed to create, update, or delete the subscription data corresponding to the one or more CAG identifiers. The first CAG identifier is matched with the subscription data of the terminal device to determine whether to allow the creation, update, or deletion of the first subscription data requested by the request information #a, including: when the first CAG identifier belongs to the one or more CAG identifiers or the identifier of the first AF network element belongs to the identifier of the one or more AF network elements corresponding to the first CAG identifier, it is determined that the creation, update, or deletion of the first subscription data requested by the request information #a is not allowed; when the first CAG identifier does not belong to the one or more CAG identifiers and the identifier of the first AF network element does not belong to the identifier of the one or more AF network elements corresponding to the first CAG identifier, it is determined that the creation, update, or deletion of the first subscription data requested by the request information #a is allowed.

[0337] In one implementation, the request information #a includes the identifier of a first AF network element. The subscription data of the terminal device includes one or more CAG identifiers, a first indication indicating that the subscription data corresponding to N CAG identifiers can be created, updated, or deleted, the identifiers of one or more AF network elements that allow the creation, updating, or deletion of the subscription data corresponding to the N CAG identifiers, a second indication indicating that the subscription data corresponding to M CAG identifiers cannot be created, updated, or deleted, and the identifiers of one or more AF network elements that do not allow the creation, updating, or deletion of the subscription data corresponding to the M CAG identifiers. The N CAG identifiers belong to the plurality of CAG identifiers, the M CAG identifiers belong to the plurality of CAG identifiers, and the N CAG identifiers are related to the M CAG identifiers. Each CAG identifier is different. The first CAG identifier is matched with the subscription data of the terminal device to determine whether the creation, update, or deletion of the first subscription data requested by request information #a is allowed. This includes: if the first CAG identifier belongs to the M CAG identifiers or the identifier of the first AF network element does not belong to the identifier of one or more AF network elements corresponding to the M CAG identifiers, then the creation, update, or deletion of the first subscription data requested by request information #a is not allowed; if the first CAG identifier belongs to the N CAG identifiers and the identifier of the first AF network element belongs to the identifier of one or more AF network elements corresponding to the first CAG identifier, then the creation, update, or deletion of the first subscription data requested by request information #a is allowed.

[0338] Optionally, the contract data of the aforementioned terminal device may also include one or more valid durations, each of which corresponds one-to-one with one or more indication messages.

[0339] For example, if one or more indications are valid for one hour, then the validity period for indicating whether the contract data corresponding to one or more CAG IDs is allowed to be created, updated, or deleted is one hour. That is, after one hour, the one or more indications will no longer indicate whether the contract data corresponding to one or more CAG IDs is allowed to be created, updated, or deleted. For example, if indication #1 indicates that the contract data corresponding to CAG IDs 1 to 5 is allowed to be created, updated, or deleted, then after one hour, indication #1 will no longer indicate whether the contract data corresponding to CAG IDs 1 to 5 is allowed to be created, updated, or deleted.

[0340] Furthermore, based on the determined result, the UDM network element sends a response message to the NEF network element, i.e., executes step S530.

[0341] The S530 and UDM network elements send response information #a to the NEF network element.

[0342] Correspondingly, the NEF network element receives the response information #a from the UDM network element.

[0343] In method 500, the response information #a is an example of the first response information in method 300. That is, in method 400, the response information #a is the aforementioned first response information.

[0344] In one implementation, if the UDM element determines that the creation, update, or deletion of the first subscription data requested by request information #a is allowed, then response information #a is used to indicate that the creation, update, or deletion of the first subscription data was successful.

[0345] For example, if the response message #a indicates successful creation of the first subscription data, then the terminal device's subscription data will include this first subscription data. Furthermore, the UDM network element can send the terminal device's subscription data, including the first subscription data, to the UDR network element so that the UDR network element can save it. In this case, the response message #a can be called the "Nudm_ParameterProvision_Create response".

[0346] For example, the response message #a indicates that the update of the first subscription data was successful, and the corresponding validity period in the first subscription data in the terminal device will become the first validity period. Furthermore, the UDM network element can send the updated subscription data of the terminal device to the UDR network element so that the UDR network element can save it. In this case, the response message #a can be called "Nudm_ParameterProvision_Update response".

[0347] For example, the response message #a indicates that the deletion of the first subscription data was successful. The first subscription data will then be deleted from the terminal device, meaning it will no longer be included in the terminal device's subscription data. Furthermore, the UDM network element can send the terminal device's subscription data after the first subscription data has been deleted to the UDR network element so that the UDR network element can save it. In this case, the response message #a can be called the "Nudm_ParameterProvision_Delete response".

[0348] In one implementation, if the UDM element determines that the creation, update, or deletion of the first subscription data requested by request information #a is not allowed, then response information #a is used to indicate that the creation, update, or deletion of the first subscription data has failed.

[0349] For example, the response information #a includes the reason why creating, updating, or deleting the first contract data failed, including reasons that do not allow updating or deleting the first contract data.

[0350] For a detailed description of the response information #a, please refer to step S330 above, which will not be repeated here.

[0351] Furthermore, after receiving the response information #a, the NEF network element sends a response information to the first AF network element, i.e., executes step S540.

[0352] S540 and NEF network elements send response information #b to the first AF network element.

[0353] Correspondingly, the first AF network element receives the response information #b from the NEF network element.

[0354] The response information #b indicates whether the creation, updating, or deletion of the first contract data was successful.

[0355] In one implementation, the UDM network element determines that the creation, updating, or deletion of the first subscription data is permitted. Response information #a is used to indicate that the creation, updating, or deletion of the first subscription data was successful, and response information #b is used to indicate that the creation, updating, or deletion of the first subscription data was successful.

[0356] For example, the response message #b is used to indicate that the creation of the first contract data was successful. In this case, the response message #b can be called "Nnef_ParameterProvision_Create response".

[0357] For example, the response information #b is used to indicate that the first contract data update was successful. In this case, the response information #b can be called "Nnef_ParameterProvision_Update response".

[0358] For example, the response message #b is used to indicate that the deletion of the first contract data was successful. In this case, the response message #b can be called "Nnef_ParameterProvision_Delete response".

[0359] In one implementation, the UDM network element determines that creating, updating, or deleting the first subscription data is not allowed. Response information #a indicates that creating, updating, or deleting the first subscription data failed, and response information #b indicates that creating, updating, or deleting the first subscription data failed. In this case, response information #b includes the reason for the failure to create, update, or delete the first subscription data, which may include disallowing the creation, updating, or deletion of the first subscription data.

[0360] After receiving the response information #b, the first AF network element may optionally save the first CAG identifier. Thus, when the first AF network element receives a request from a terminal device to create, update, or delete the subscription data corresponding to the first CAG identifier, the first AF network element can proactively reject the request from the terminal device based on the saved information.

[0361] In this embodiment, the UDM network element determines, based on the first CAG identifier provided by the first AF network element, whether the subscription data corresponding to the first CAG identifier is allowed to be created, updated, or deleted, and then determines whether to allow the creation, update, or deletion of the subscription data corresponding to the first CAG identifier in the terminal device requested by request information #a, so as to improve the accuracy of creating, updating, or deleting the subscription data corresponding to the first CAG identifier in the terminal device.

[0362] Figure 6 is a schematic diagram of a communication method 600 provided in an embodiment of this application. For ease of description, the following example uses a first AF network element, a terminal device, a NEF network element, and a UDM network element as core network elements. The first AF network element can be replaced by its components (e.g., a chip, chip system, circuit, or communication module); the terminal device can be replaced by its components (e.g., a chip, chip system, circuit, or communication module); the NEF network element can be replaced by its components (e.g., a chip, chip system, circuit, or communication module); and the UDM network element can be replaced by its components (e.g., a chip, chip system, circuit, or communication module). Furthermore, the steps described below as being performed by a single execution entity can also be divided into steps performed by multiple execution entities, which can be logically and / or physically separated. The method 600 shown in Figure 6 may include the following steps.

[0363] S610, The terminal device sends a request message #A to the first AF network element.

[0364] Correspondingly, the first AF network element receives request information #A from the terminal device.

[0365] The request information #A includes a first CAG identifier, which is used to request the creation, updating, or deletion of the first contract data corresponding to the first CAG identifier in the terminal device.

[0366] For example, request information #A may also include the identifier of the terminal device.

[0367] It should be noted that in method 600, the request information #A is an example of the first request information in method 300. That is, in method 600, the request information #A is the aforementioned first request information.

[0368] For a detailed description of the request information #A, please refer to step S310 above, which will not be repeated here.

[0369] After receiving request information #A, the first AF network element will determine whether to allow the creation, update, or deletion of the first contract data requested by request information #A based on the first CAG identifier provided in request information #A. That is, it will execute step S620.

[0370] S620, the first AF network element determines whether to allow the execution of the request information #A to create, update or delete the first contract data based on the first CAG identifier.

[0371] For example, if request information #A requests the creation of the first contractual data, the first AF network element will determine whether to allow the creation of the first contractual data requested by request information #A based on the first CAG identifier.

[0372] For example, if request information #A requests to update the first contractual data, the first AF network element will determine whether to allow the execution of the update of the first contractual data requested by request information #A based on the first CAG identifier.

[0373] For example, if request information #A requests the deletion of the first contract data, the first AF network element will determine whether to allow the deletion of the first contract data requested by request information #A based on the first CAG identifier.

[0374] Specifically, the first AF network element matches the first CAG identifier with preset configuration information to determine whether to allow the creation, update, or deletion of the first subscription data requested by request information #A. The preset configuration information includes the conditions for creating, updating, or deleting the subscription data of the terminal device.

[0375] Specifically, determining whether to allow the creation, update, or deletion of the first contract data requested by request information #A includes: determining whether to allow the creation, update, or deletion of the first contract data requested by request information #A; or determining whether to disallow the creation, update, or deletion of the first contract data requested by request information #A.

[0376] For example, if the preset configuration information includes one or more CAG identifiers, then matching the first CAG identifier with the preset configuration information can be understood as comparing the first CAG identifier with the multiple CAG identifiers.

[0377] In one example, the preset configuration information includes one or more CAG identifiers, and the subscription data corresponding to these one or more CAG identifiers can be created, updated, or deleted. The first CAG identifier is matched against the preset configuration information to determine whether the creation, update, or deletion of the first subscription data requested by request information #A is allowed. This includes: if the first CAG identifier does not belong to the one or more CAG identifiers, determining that the creation, update, or deletion of the first subscription data requested by request information #A is not allowed; if the first CAG identifier belongs to the one or more CAG identifiers, determining that the creation, update, or deletion of the first subscription data requested by request information #A is allowed.

[0378] In one example, the default configuration information includes one or more CAG identifiers whose corresponding contract data is not allowed to be created, updated, or deleted. In this case, the first CAG identifier is matched against the multiple CAG identifiers. If the first CAG identifier does not belong to any of the multiple CAG identifiers, then the creation, update, or deletion of the first contract data requested by request information #A is allowed. If the first CAG identifier belongs to any of the multiple CAG identifiers, then the creation, update, or deletion of the first contract data requested by request information #A is not allowed.

[0379] In one example, the preset configuration information includes multiple CAG identifiers. Q of these CAG identifiers belong to a first category, and P of them belong to a second category. The contract data corresponding to the first category identifiers is allowed to be created, updated, or deleted, while the contract data corresponding to the second category identifiers is not allowed to be created, updated, or deleted. That is, the contract data corresponding to the Q CAG identifiers belonging to the first category is allowed to be created, updated, or deleted, while the contract data corresponding to the P CAG identifiers belonging to the second category is not allowed to be created, updated, or deleted. The Q CAG identifiers are different from the P CAG identifiers. In this case, the first CAG identifier is matched against the multiple CAG identifiers. If the first CAG identifier belongs to the first category, then the creation, updating, or deletion of the first contract data requested by request information #A is allowed. If the first CAG identifier belongs to the second category, then the creation, updating, or deletion of the first contract data requested by request information #A is not allowed.

[0380] For example, there are 200 CAG IDs, ranging from CAG ID 1 to CAG ID 200. Assume CAGs with IDs 1-100 are classified as Category 1 identifiers, and CAGs with IDs 101-200 as Category 2 identifiers. Then, the contract data corresponding to CAG IDs with IDs in the range of 1-100 is allowed to be created, updated, or deleted, while the contract data corresponding to CAG IDs with IDs in the range of 101-200 is not allowed to be created, updated, or deleted. If the first CAG ID is CAG ID 1, and the first CAG ID is within the range of 1-100, then the creation, updating, or deletion of the first contract data requested by request information #A is allowed. If the first CAG ID is CAG ID 110, and the first CAG ID is within the range of 101-200, then the creation, updating, or deletion of the first contract data requested by request information #A is not allowed.

[0381] Furthermore, based on the determined result, the first AF network element will send different information to different devices, specifically in two cases: Case 1 and Case 2.

[0382] Scenario 1: The first AF network element determines that the request to create, update, or delete the first contract data requested by request information #A is not allowed. This specifically includes step S621a.

[0383] S621a, The first AF network element sends response information #A to the terminal device.

[0384] Correspondingly, the NEF network element receives the response information #A from the terminal device.

[0385] The response message #A indicates that the creation, updating, or deletion of the first contract data failed.

[0386] It should be noted that in method 600, the response information #A is an example of the first response information in method 300. That is, in method 600, the response information #A is the aforementioned first response information.

[0387] For a detailed description of the response information #A, please refer to step S330 above, which will not be repeated here.

[0388] Scenario 2: The first AF network element determines that the request to create, update, or delete the first contract data requested by request information #A is permitted. This specifically includes steps S622a and S622g.

[0389] S622a, The first AF network element sends a request message #B to the NEF network element.

[0390] Correspondingly, the NEF network element receives request information #B from the first AF network element.

[0391] The request information #B includes a first CAG identifier, which is used to request the creation, updating, or deletion of the first contract data.

[0392] It should be noted that in method 600, the request information #B is an example of the second request information in method 300 above. That is, in method 600, the request information #B is the aforementioned second request information.

[0393] In one implementation, request message #A is used to request the creation of the first subscription data. When the NEF network element determines, based on the first CAG identifier, that it is permissible to execute the creation of the first subscription data requested by request message #B, it sends request message #B to request the creation of the first subscription data. Request message #B can be referred to as "Nnef_ParameterProvision_Create request".

[0394] In one implementation, request message #A is used to request an update to the first subscription data. When the NEF network element determines, based on the first CAG identifier, that it is permissible to execute the update of the first subscription data requested by request message #A, it sends request message #B to request an update to the first subscription data. Request message #B can be referred to as "Nnef_ParameterProvision_Update request".

[0395] For example, the request information #B also includes a first valid duration. A description of the first valid duration can be found in step S310 above, and will not be repeated here.

[0396] In one implementation, request message #A is used to request the deletion of the first subscription data. When the NEF network element determines, based on the first CAG identifier, that it is permissible to execute the deletion of the first subscription data requested by request message #A, it sends request message #B to request the creation of the first subscription data. Request message #B can be referred to as "Nnef_ParameterProvision_Delete request".

[0397] For example, the request information #B includes the identifier of the terminal device and the identifier of the first AF network element. After receiving the request information #1, the NEF network element verifies whether the first AF network element is authorized to provide parameters based on its identifier, for example, verifying whether the first AF network element is authorized to provide the first ACG identifier. That is, it executes step S622b.

[0398] S622b and NEF network element verification determine whether the first AF network element is authorized to provide the first CAG identifier.

[0399] Specifically, the NEF network element verifies whether the first AF network element is authorized to provide the first CAG identifier based on the identifier of the first AF network element. When the NEF network element verifies that the first AF network element is authorized to provide the first CAG identifier, the NEF network element executes step S622c below. That is, step S622c occurs when the first AF network element verifies that it is authorized.

[0400] When the NEF network element verifies that the first AF network element is not authorized to provide the first CAG identifier, method 600 further includes: the NEF network element sending response information #B to the first AF network element. Accordingly, the first AF network element receives response information #B from the NEF network element, and response information #B does not allow the creation, updating, or deletion of the first subscription data requested by request information #B.

[0401] The implementation method of NEF network element verifying whether the first AF network element is authorized to provide the first CAG identifier based on the identifier of the first AF network element can be found in the prior art or in step S220 above, and will not be repeated here.

[0402] In this application, the following steps are described using the example of NEF network element verifying that the first AF network element is authorized to provide the first CAG, namely, the NEF network element performs step S622c.

[0403] The S622c and NEF network elements send request information #C to the UDM network element.

[0404] Correspondingly, the UDM network element receives request information #C from the NEF network element.

[0405] The request information #C includes a first CAG identifier, and the request information #C is used to request the creation, updating or deletion of the first contract data.

[0406] In one implementation, the request message #C is used to request the creation of the first contract data, and the request message #C can be called "Nudm_ParameterProvision_Create request".

[0407] In one implementation, the request message #C is used to request an update to the first contract data. The request message #C can be called "Nudm_ParameterProvision_Update request".

[0408] For example, the request information #C also includes a first valid duration. A description of the first valid duration can be found in step S310 above, and will not be repeated here.

[0409] In one implementation, the request message #C is used to request the deletion of the first contract data. The request message #C can be called "Nudm_ParameterProvision_Delete request".

[0410] For example, the request information #C may also include the identifier of the terminal device.

[0411] Furthermore, the UDM network element determines whether to create, update, or delete the first subscription data based on the received request information #2. This specifically includes the following steps:

[0412] The S622d and UDM network elements determine whether to create, update, or delete the first contract data based on the first CAG identifier.

[0413] The implementation method for the UDM network element to determine whether to create, update, or delete the first contract data based on the first CAG identifier can be found in the description of step S622d above. It is only necessary to replace the request information #2 with the request information #C, which will not be elaborated here.

[0414] The S622e and UDM network elements send response information #C to the NEF network element.

[0415] Correspondingly, the NEF network element receives the response information #C from the UDM network element.

[0416] The response message #C indicates whether the creation, updating, or deletion of the first contract data was successful.

[0417] For a description of response information #C, please refer to the description of response information #2 in step S422c above. Simply replace response information #2 with response information #C. It will not be repeated here.

[0418] Furthermore, after receiving the response information #C, the NEF network element will send feedback to the first AF network element to indicate whether the creation, update, or deletion of the first contract data was successful.

[0419] S622f and NEF network elements send response information #D to the first AF network element.

[0420] Correspondingly, the first AF network element receives the response information #D from the NEF network element.

[0421] The response information #D indicates whether the creation, updating, or deletion of the first contract data was successful.

[0422] For a description of response information #D, please refer to the description of response information #3 in step S422d above. Simply replace response information #3 with response information #C. This will not be repeated here.

[0423] Furthermore, after receiving the response information #C, the first AF network element will send feedback to the terminal device to indicate whether the creation, update, or deletion of the first contract data was successful.

[0424] S622g, the first AF network element sends response information #E to the terminal device.

[0425] Correspondingly, the terminal device receives the response information #E from the first AF network element.

[0426] The response information #E indicates whether the creation, updating, or deletion of the first contract data was successful.

[0427] In one implementation, response message #D is used to indicate that the creation, updating, or deletion of the first contract data was successful, and response message #E is used to indicate that the creation, updating, or deletion of the first contract data was successful.

[0428] In one implementation, response message #D is used to indicate that the creation, updating, or deletion of the first contract data failed, and response message #E is used to indicate that the creation, updating, or deletion of the first contract data failed.

[0429] For example, response information #E includes the reason for the failure to create, update, or delete the first subscription data, such as the first subscription data not being included in the subscription data of the terminal device.

[0430] It should be noted that method 600 also applies to requests #A containing multiple CAG identifiers. When requests #A contain multiple CAG identifiers, the first AF network element will match these multiple CAG identifiers with preset configuration information. For example, if the preset configuration information contains multiple CAG identifiers, and if the multiple CAG identifiers in the preset configuration information are exactly the same as the multiple CAG identifiers in requests #A, then the subsequent steps performed by the first AF network element can refer to steps S620 to S622g above, but it is important to note that the first CAG identifier should be replaced with multiple CAG identifiers. If some CAG identifiers in request information #A are identical to multiple CAG identifiers in the preset configuration information, then when the subscription data corresponding to the multiple CAG identifiers in the preset configuration information is allowed to be created, updated, or deleted, the first AF network element will feed back the different CAG identifiers to the terminal device; if the subscription data corresponding to the multiple CAG identifiers in the preset configuration information is not allowed to be created, updated, or deleted, the first AF network element will feed back the identical CAG identifiers to the terminal device; if some CAG identifiers in the preset configuration information are allowed to be created, updated, or deleted, and some CAG identifiers are not allowed to be created, updated, or deleted, the first AF network element will send one or more CAG identifiers corresponding to the subscription data that is allowed to be created, updated, or deleted to the NEF network element through request information #B, and the first AF network element will send one or more CAG identifiers corresponding to the subscription data that is not allowed to be created, updated, or deleted to the terminal device through response information #A.

[0431] In this embodiment of the application, the first AF network element determines whether the subscription data corresponding to the first CAG identifier is allowed to be created, updated or deleted based on the first CAG identifier provided by the first AF network element, and then determines whether to allow the creation, update or deletion of the subscription data corresponding to the first CAG identifier in the terminal device requested by request information #A, so as to improve the accuracy of creating, updating or deleting the subscription data corresponding to the first CAG identifier in the terminal device.

[0432] The processes illustrated in Figures 3 to 6 above are merely possible implementations of the method provided in this application in different scenarios and should not be construed as limiting this application in any way. Those skilled in the art, based on the same concept, can also apply the above method to the same scenarios using different implementation methods, or they can apply the above method to other scenarios. This application does not limit this.

[0433] It should be understood that in the various embodiments shown above in conjunction with the accompanying drawings, the sequence number of each step does not imply the order of execution. The execution order of each step should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0434] It is understood that the methods and operations implemented by the device (such as the first AF network element, NEF network element, UDM network element, etc.) in the above-described method embodiments can also be implemented by components inside the device (such as chips or circuits).

[0435] The methods provided in the embodiments of this application have been described in detail above with reference to several accompanying drawings. The apparatus provided in the embodiments of this application will now be described with reference to the accompanying drawings. It should be understood that the descriptions of the apparatus embodiments correspond to the descriptions of the method embodiments; therefore, any content not described in detail can be referred to the above method embodiments, and for the sake of brevity, will not be repeated.

[0436] Figure 7 is a schematic diagram of a communication device 1000 provided in an embodiment of this application. The communication device 1000 includes a transceiver unit 1010 and a processing unit 1020. The transceiver unit 1010 can be used to implement corresponding communication functions. The transceiver unit 1010 can also be referred to as a communication interface or a communication unit. The processing unit 1020 can be used to perform processing, such as determining whether to allow the creation, updating, or deletion of the first subscription data requested by the first request information.

[0437] Optionally, the device 1000 may further include a storage unit, which can be used to store instructions and / or data, and the processing unit 1020 can read the instructions and / or data in the storage unit to enable the device to implement the aforementioned method embodiments.

[0438] In one possible design, the device 1000 may correspond to the core network element in method 300 shown in FIG3, the NEF network element in method 400 shown in FIG4, the UDM network element in method 500 shown in FIG5, or the first AF network element in method 600 shown in FIG6, and can be used to implement the steps or processes executed by the core network element, NEF element, UDM element or first AF network element in the above method embodiments. The transceiver unit 1010 can be used to perform transceiver-related operations in the above method embodiments, such as steps S310 and S330 in Figure 3; or one or more of steps S410, S421a, S422a, S422c, and S422d in Figure 4; or one or more of steps S510, S501, S530, and S540 in Figure 5; or one or more of steps S610, S621a, S622a, S622c, and S622e to S622g in Figure 6. The processing unit 1020 can be used to perform processing-related operations in the above method embodiments, or operations other than sending and receiving, such as step S320 in FIG3; or one or more of steps S420 and S422b in FIG4; or one or more of steps S502 and S52 in FIG5; or one or more of steps S620, S622b and S622d in FIG6.

[0439] In a first possible design, the device 1000 can be a core network element in the aforementioned embodiments. The device 1000 can implement the steps or processes corresponding to those performed by the core network element in the above method embodiments. Specifically, the transceiver unit 1010 can be used to perform transceiver-related operations (such as sending and / or receiving data or messages) of the core network element in the above method embodiments, and the processing unit 1020 can be used to perform processing-related operations of the core network element in the above method embodiments, or operations other than transceiver (such as operations other than sending and / or receiving data or messages).

[0440] In one possible implementation, a transceiver unit 1010 is configured to receive first request information, the first request information including a first Closed Access Group (CAG) identifier, the first request information being used to request the creation, updating, or deletion of first subscription data of a terminal device corresponding to the first CAG identifier; a processing unit 1020 is configured to determine, based on the first CAG identifier, that the creation, updating, or deletion of the first subscription data requested by the first request information is not permitted; the transceiver unit 1010 is further configured to send first response information, the first response information being used to indicate that the creation, updating, or deletion of the first subscription data has failed.

[0441] Another possible implementation is as follows: Transceiver unit 1010 is configured to receive first request information, which includes a first Closed Access Group (CAG) identifier, and is used to request the creation, updating, or deletion of first subscription data of a terminal device corresponding to the first CAG identifier; processing unit 1020 is configured to determine, based on the first CAG identifier, whether the creation, updating, or deletion of the first subscription data requested by the first request information is permitted; transceiver unit 1010 is further configured to send second request information, which includes the first CAG identifier, and is used to request the creation, updating, or deletion of the first subscription data; or, send first response information, which indicates that the creation, updating, or deletion of the first subscription data was successful.

[0442] It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0443] It should also be understood that the device 1000 here is embodied in the form of a functional unit. The term "unit" here can refer to an application-specific integrated circuit (ASIC), electronic circuitry, a processor (e.g., a shared processor, a proprietary processor, or a group processor, etc.) and memory for executing one or more software or firmware programs, integrated logic circuitry, and / or other suitable components supporting the described functions. In an alternative example, those skilled in the art will understand that the device 1000 can be specifically the communication device in the above embodiments, and can be used to execute the various processes and / or steps corresponding to the communication device in the above method embodiments; to avoid repetition, these will not be described again here.

[0444] The apparatus 1000 of each of the above schemes has the function of implementing the corresponding steps performed by the core network element in the above method, or has the function of implementing the corresponding steps performed by the NEF network element, the first AF network element, and the UDM network element in the above method. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions; for example, the transceiver unit can be replaced by a transceiver (e.g., the transmitting unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiver), and other units, such as processing units, can be replaced by processors, respectively executing the transceiver operations and related processing operations in each method embodiment.

[0445] In addition, the transceiver unit 1010 may also be a transceiver circuit (for example, it may include a receiving circuit and a transmitting circuit), and the processing unit may be a processing circuit.

[0446] It should be noted that the device in Figure 7 can be the communication equipment in the aforementioned embodiments (such as a core network element, or a NEF network element, a first AF network element, or a UDM network element), or it can be a chip or a chip system, such as a system on a chip (SoC). The transceiver unit can be an input / output circuit or a communication interface; the processing unit is a processor, microprocessor, or integrated circuit integrated on the chip. No limitations are imposed here.

[0447] Figure 8 is a schematic diagram of another communication device 2000 provided in an embodiment of this application. The device 2000 includes a processor 2010, which is coupled to a memory 2020. The memory 2020 is used to store computer programs or instructions and / or data. The processor 2010 is used to execute the computer programs or instructions stored in the memory 2020, or to read the data stored in the memory 2020, in order to execute the methods in the above method embodiments.

[0448] Optionally, there may be one or more processors 2010.

[0449] Optionally, the memory 2020 may be one or more.

[0450] Alternatively, the memory 2020 can be integrated with the processor 2010, or it can be set up separately.

[0451] Optionally, as shown in FIG8, the device 2000 further includes a transceiver 2030 for receiving and / or transmitting signals. For example, the processor 2010 is used to control the transceiver 2030 to receive and / or transmit signals.

[0452] As an example, processor 2010 may have the functions of processing unit 1220 shown in FIG7, memory 2020 may have the functions of storage unit, and transceiver 2030 may have the functions of transceiver unit 1210 shown in FIG7.

[0453] As one approach, the device 2000 is used to implement the operations performed by the communication device (such as a core network element, or NEF element, first AF element, UDM element) in the various method embodiments described above.

[0454] For example, processor 2010 is used to execute computer programs or instructions stored in memory 2020 to implement the relevant operations of the communication device in the various method embodiments above.

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

[0456] It should also be understood that the memory mentioned in the embodiments of this application can be volatile memory and / or non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM includes the following forms: 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 linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0457] 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, or discrete hardware component, the memory (storage module) can be integrated into the processor.

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

[0459] Figure 9 is a schematic diagram of a chip system 3000 provided in an embodiment of this application. The chip system 3000 (or may also be called a processing system) includes logic circuitry 3010 and an input / output interface 3020.

[0460] The logic circuit 3010 can be a processing circuit in the chip system 3000. The logic circuit 3010 can be coupled to a memory unit, calling instructions from the memory unit, enabling the chip system 3000 to implement the methods and functions of the embodiments of this application. The input / output interface 3020 can be an input / output circuit in the chip system 3000, outputting processed information from the chip system 3000, or inputting data or signaling information to be processed into the chip system 3000 for processing.

[0461] As one approach, the chip system 3000 is used to implement the operations performed by the core network element, NEF network element, first AF network element, or UDM network element in the various method embodiments described above.

[0462] For example, logic circuit 3010 is used to implement processing-related operations performed by core network elements, NEF network elements, first AF network elements, or UDM network elements in the above method embodiments; input / output interface 3020 is used to implement transmission and / or reception-related operations performed by core network elements, NEF network elements, first AF network elements, or UDM network elements in the above method embodiments.

[0463] This application also provides a computer program product that, when run on a processor, can implement the multimedia communication method executed by the first network element, IMS AS, or P-CSCF in the above method embodiments, or the multimedia communication method executed by the second network element, MF, or IMS-AGW.

[0464] This application also provides a computer-readable storage medium containing computer instructions that, when executed on a processor, can implement the communication method performed by the core network element, or NEF network element, first AF network element, or UDM network element in the above method embodiments.

[0465] This application also provides a communication system, including at least one of the aforementioned NEF network element, first AF network element, and UDM network element.

[0466] The explanations and beneficial effects of the relevant contents in any of the devices provided above can be found in the corresponding method embodiments provided above, and will not be repeated here.

[0467] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of apparatus or units may be electrical, mechanical, or other forms.

[0468] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. For example, the computer can be a personal computer, a server, or a network device, etc. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state disks, SSDs). For example, the aforementioned available media include, but are not limited to, various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0469] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, Applied to core network elements, including: Receive a first request information, the first request information including a first CAG identifier, the first request information being used to request the creation, updating or deletion of the first contract data of the terminal device corresponding to the first CAG identifier; Based on the first CAG identifier, it is determined that the creation, updating, or deletion of the first contract data requested by the first request information is not permitted; Send a first response message, which indicates that the creation, update or deletion of the first contract data requested by the first request message failed.

2. The method according to claim 1, characterized in that, The core network element is a Network Open Function (NEF) element, and the receiving of the first request information includes: Receive the first request information from the first application function (AF) network element; Based on the first CAG identifier, determining that the creation, updating, or deletion of the first contract data requested by the first request information is not permitted includes: The first CAG identifier is matched with the preset configuration information to determine that the creation, updating or deletion of the first contract data requested by the first request information is not allowed. Send the first response message, including: Send the first response information to the first AF network element.

3. The method according to claim 2, characterized in that, The first request information includes the identifier of the first AF network element, and the preset configuration information includes multiple CAG identifiers and multiple AF network element identifiers. Matching the first CAG identifier with the preset configuration information determines that the creation, updating, or deletion of the first subscription data requested by the first request information is not permitted, including: The first CAG identifier is matched with the plurality of CAG identifiers, and the identifier of the first AF network element is matched with the identifiers of the plurality of AF network elements to determine that the creation, updating or deletion of the first contract data requested by the first request information is not allowed.

4. The method according to claim 2, characterized in that, The first request information includes the identifier of the first AF network element, and the preset configuration information includes multiple CAG identifiers and the identifiers of one or more AF network elements that are allowed to create, update, or delete the subscription data corresponding to the multiple CAG identifiers. Matching the first CAG identifier with preset configuration information to determine that the creation, updating, or deletion of the first contract data requested by the first request information is not allowed, including: If the first CAG identifier does not belong to the plurality of CAG identifiers or the identifier of the first AF network element does not belong to the identifier of one or more AF network elements corresponding to the first CAG identifier, it is determined that the creation, updating or deletion of the first contract data requested by the first request information is not allowed.

5. The method according to claim 1, characterized in that, The core network element is a unified data management (UDM) network element, and the receiving of the first request information includes: Receive the first request information from the NEF network element; Based on the first CAG identifier, determining that the creation, updating, or deletion of the first contract data requested by the first request information is not permitted includes: The first CAG identifier is matched with the subscription data of the terminal device to determine that the creation, updating or deletion of the first subscription data requested by the first request information is not allowed. Send the first response message, including: Send the first response information to the NEF network element.

6. The method according to claim 5, characterized in that, The subscription data of the terminal device includes one or more CAG identifiers. The subscription data corresponding to the one or more CAG identifiers can be created, updated, or deleted. Matching the first CAG identifier with the subscription data of the terminal device and determining that the creation, update, or deletion of the first subscription data requested by the first request information is not allowed includes: If the first CAG identifier does not belong to one or more CAG identifiers, it is determined that the creation, updating or deletion of the first contract data requested by the first request information is not allowed.

7. The method according to claim 5, characterized in that, The first request information includes the identifier of a first AF network element, and the subscription data of the terminal device includes one or more CAG identifiers and the identifiers of one or more AF network elements that are allowed to create, update, or delete the subscription data corresponding to the one or more CAG identifiers. Matching the first CAG identifier with the subscription data of the terminal device to determine that the creation, update, or deletion of the first subscription data requested by the first request information is not allowed includes: If the first CAG identifier does not belong to one or more CAG identifiers or the identifier of the first AF network element does not belong to one or more AF network elements corresponding to the first CAG identifier, it is determined that the creation, updating or deletion of the first contract data requested by the first request information is not allowed.

8. The method according to claim 1, characterized in that, The core network element is the first AF network element, and receiving the first request information includes: Receive the first request information from the terminal device; Based on the first CAG identifier, determining that the creation, updating, or deletion of the first contract data requested by the first request information is not permitted includes: The first CAG identifier is matched with the preset configuration information to determine that the creation, updating or deletion of the first contract data requested by the first request information is not allowed. Send the first response message, including: The first response information is sent to the terminal device.

9. The method according to claim 8, characterized in that, The preset configuration information includes one or more CAG identifiers, and the contract data corresponding to the one or more CAG identifiers can be created, updated, or deleted. Matching the first CAG identifier with the preset configuration information to determine whether the creation, updating, or deletion of the first contract data requested by the first request information is not allowed includes: If the first CAG identifier does not belong to one or more CAG identifiers, it is determined that the creation, updating or deletion of the first contract data requested by the first request information is not allowed.

10. The method according to any one of claims 1-9, characterized in that, The first response information includes the reason why the creation, update, or deletion of the first contract data requested by the first request information failed, and the reason includes that the creation, update, or deletion of the first contract data requested by the first request information is not allowed.

11. A communication device, characterized in that, Includes modules or units for performing the method according to any one of claims 1 to 10.

12. A communication device, characterized in that, The device includes a processor coupled to a memory, the processor being configured to execute a computer program or instructions stored in the memory to cause the communication device to perform the method as described in any one of claims 1 to 10.

13. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions that, when executed on a communication device, cause the communication device to perform the method as described in any one of claims 1 to 10.

14. A computer program product, characterized in that, The computer program product includes a computer program or instructions that, when executed on a communication device, cause the communication device to perform the method as described in any one of claims 1 to 10.

Images