Method, apparatus, network element and medium for subscription update

Abstract

The application discloses a method, device, network element and medium for subscription updating, and belongs to the field of communication technology. The method for subscription updating comprises the following steps: a unified data network element receives a credential successful pushing indication; the credential successful pushing indication is used for indicating that a target service parameter corresponds to a credential which has been successfully pushed to a target terminal; and the unified data network element enables the target service parameter in the subscription of the target terminal.

Description

TECHNICAL FIELD

[0001] The present application belongs to the technical field of communication, and particularly relates to a method and apparatus for subscription update, a network element and a medium. BACKGROUND

[0002] After a terminal is registered to a 5G core network, the terminal can establish a PDU session using a data network name (DNN) and / or a single network slice selection assistance information (S-NSSAI). Some DNNs require secondary authentication, that is, when the terminal establishes a protocol data unit (PDU) session of the DNN, the terminal needs to provide credential information to authenticate the terminal through an authentication server in the DNN. Some S-NSSAIs require network slice authentication (NSSAA), that is, when the terminal requests the S-NSSAI, the terminal needs to provide slice-related credential information to authenticate the S-NSSAI.

[0003] In the related art, a provisioning server (PVS) can send credential information of a service parameter (for example, a credential for secondary authentication of a DNN or a credential for network slice authentication) to a terminal through automatic pushing. Subsequently, the terminal can request the network to use the service parameter. However, if the subscription data of the terminal in the network is not updated in time, the network will still reject the request of the terminal for the service parameter, thereby causing the terminal to be unable to use the corresponding service. SUMMARY

[0004] Embodiments of the present application provide a method and apparatus for subscription update, a network element and a medium, which enable a target service parameter by updating the subscription data of a terminal, to solve the problem of timely updating of the subscription of the terminal in the related art.

[0005] In a first aspect, a method for subscription update is provided, which includes: a unified data network element receiving a credential successful pushing indication; the credential successful pushing indication is used to indicate that a credential corresponding to a target service parameter has been successfully pushed to a target terminal; and the unified data network element enables the target service parameter in the subscription of the target terminal.

[0006] In a second aspect, a device for subscription updating is provided, which comprises: a receiving module configured to receive a credential successful pushing indication; the credential successful pushing indication is used to indicate that a credential corresponding to a target service parameter has been successfully pushed to a target terminal; and an executing module configured to enable the target service parameter in a subscription of the target terminal.

[0007] In a third aspect, a method for subscription updating is provided, which comprises: a server sending a credential successful pushing indication to a unified data network element; and the credential successful pushing indication is used to indicate that a credential corresponding to a target service parameter has been successfully pushed to a target terminal.

[0008] In a fourth aspect, a device for subscription updating is provided, which comprises: a sending module configured to send a credential successful pushing indication to a unified data network element; and the credential successful pushing indication is used to indicate that a credential corresponding to a target service parameter has been successfully pushed to a target terminal.

[0009] In a fifth aspect, a method for subscription updating is provided, which comprises: a network exposure network element acquiring a credential successful pushing indication; and the network exposure network element sending the credential successful pushing indication to a unified data network element; and the credential successful pushing indication is used to indicate that a credential corresponding to a target service parameter has been successfully pushed to a target terminal.

[0010] In a sixth aspect, a device for subscription updating is provided, which comprises: an executing module configured to acquire a credential successful pushing indication; and a sending module configured to send the credential successful pushing indication acquired by the executing module to a unified data network element; and the credential successful pushing indication is used to indicate that a credential corresponding to a target service parameter has been successfully pushed to a target terminal.

[0011] In a seventh aspect, a method for subscription updating is provided, which comprises: a policy control network element acquiring a destination address of a target terminal, the destination address comprising an IP address of the target terminal or a Medium Access Control (MAC) address of the target terminal; the policy control network element determining a second terminal identifier corresponding to the target address; and the policy control network element sending the second terminal identifier to a network exposure network element or a unified data network element; and the second terminal identifier is used to update a subscription of a terminal indicated by the second terminal identifier.

[0012] In an eighth aspect, a device for subscription updating is provided, which comprises: an execution module configured to acquire a destination address of a target terminal, the destination address comprising an IP address of the target terminal or a MAC address of the target terminal; an execution module configured to determine a second terminal identifier corresponding to the target address received by the receiving module; and a transmission module configured to send the second terminal identifier to a network exposure element or a unified data network element, wherein the second terminal identifier is used to update the subscription of the terminal indicated by the second terminal identifier.

[0013] In a ninth aspect, a network-side device is provided, which comprises a processor, a memory, and a program or instruction stored in the memory and executable on the processor, and the program or instruction, when executed by the processor, implements the steps of the method according to the first aspect.

[0014] In a tenth aspect, a network-side device is provided, which is a unified data network element, comprising a processor and a communication interface, wherein: the communication interface is configured to receive a credential successful push indication; the credential successful push indication is used to indicate that a credential corresponding to the target service parameter has been successfully pushed to a target terminal; and the processor is configured to enable the target service parameter in the subscription of the target terminal.

[0015] In an eleventh aspect, a network-side device is provided, which is a server, comprising a processor and a communication interface, wherein: the communication interface is configured to send a credential successful push indication to a unified data network element; and the credential successful push indication is used to indicate that a credential corresponding to the target service parameter has been successfully pushed to a target terminal.

[0016] In a twelfth aspect, a network-side device is provided, which is a network exposure element, comprising a processor and a communication interface, wherein: the processor is configured to acquire a credential successful push indication; and the communication interface is configured to send the credential successful push indication to a unified data network element; and the credential successful push indication is used to indicate that a credential corresponding to the target service parameter has been successfully pushed to a target terminal.

[0017] In a thirteenth aspect, a network-side device is provided, which is a policy control network element, comprising a processor and a communication interface, wherein: the communication interface is configured to receive a destination address of a target terminal from a network exposure element, the destination address comprising an IP address of the target terminal or a MAC address of the target terminal; and the processor is configured to determine a second terminal identifier corresponding to the target address.

[0018] In a fourteenth aspect, a readable storage medium is provided, which stores a program or instruction, and the program or instruction, when executed by a processor, implements the steps of the method according to the first aspect or the steps of the method according to the third aspect.

[0019] In a fifteenth aspect, a chip is provided, the chip comprising a processor and a communication interface, the communication interface and the processor coupled, the processor configured to execute a program or instructions to implement the method of the first aspect, or implement the method of the third aspect, or implement the method of the fifth aspect, or implement the method of the seventh aspect.

[0020] In a sixteenth aspect, a computer program / program product is provided, the computer program / program product stored in a non-transitory storage medium, the program / program product executed by at least one processor to implement the steps of the method of the first aspect, or implement the method of the third aspect, or implement the method of the fifth aspect, or implement the method of the seventh aspect.

[0021] In the embodiments of the present application, after the unified data network element receives the indication of successful pushing of the credential, the target service parameter can be enabled in the subscription of the target terminal, so that the subscription data of the target terminal is updated in time, and then the target terminal can be provided with services according to the terminal service request authorized by the subscription of the target terminal. BRIEF DESCRIPTION OF DRAWINGS

[0022] Figure 1 is a system architecture diagram of a wireless communication system provided by the embodiments of the present application;

[0023] Figure 2 is one of the method flowcharts of the method for updating subscription provided by the embodiments of the present application;

[0024] Figure 3 is another method flowchart of the method for updating subscription provided by the embodiments of the present application;

[0025] Figure 4 is a third method flowchart of the method for updating subscription provided by the embodiments of the present application;

[0026] Figure 5 is a fourth method flowchart of the method for updating subscription provided by the embodiments of the present application;

[0027] Figure 6 is a fifth method flowchart of the method for updating subscription provided by the embodiments of the present application;

[0028] Figure 7 is a sixth method flowchart of the method for updating subscription provided by the embodiments of the present application;

[0029] Figure 8 is one of the structural diagrams of the apparatus for updating subscription provided by the embodiments of the present application;

[0030] Figure 9 is a structural schematic diagram of a device for policy generation provided by an embodiment of the present application;

[0031] Figure 10 is a structural schematic diagram of a device for policy generation provided by an embodiment of the present application;

[0032] Figure 11 is a structural schematic diagram of a device for policy generation provided by an embodiment of the present application;

[0033] Figure 12 is a structural schematic diagram of a communication device provided by an embodiment of the present application;

[0034] Figure 13 is a hardware structural schematic diagram of a network side device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0035] The technical solutions in the embodiments of the present application will be clearly described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, but not all of the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art belong to the scope of protection of the present application.

[0036] The terms "first", "second", and the like in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way can be interchanged under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first", "second" are generally a category, and are not limited to the number of objects, for example, the first object can be one or more. In addition, "and / or" in the specification and claims means at least one of the connected objects, and the character " / " generally represents an "or" relationship between the front and rear associated objects.

[0037] It is worth noting that the technology described in the embodiments of the present application is not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used in the above-mentioned systems and radio technologies, as well as in other systems and radio technologies. The following description describes a New Radio (NR) system for example purposes, and NR terminology is used in most of the following description, but these technologies can also be applied outside the NR system application, such as in a 6th Generation (6G) communication system. th

[0038] Figure 1 A block diagram of a wireless communication system to which the embodiments of the present application can be applied is shown. The wireless communication system includes terminals (e.g., terminal 1 and terminal 2) in a cell, a Radio Access Network (RAN) (e.g., RAN 1 and RAN 2) and a core network. Figure 1 Figure 1

[0039] ​​​Exemplarily, the terminal can also be referred to as a terminal device or a user equipment (UE), and can be a mobile phone, a tablet personal computer (Tablet PC), a laptop computer (Laptop PC) or a notebook computer, a personal digital assistant (PDA), a palm computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile Internet device (MID), an augmented reality (AR) / virtual reality (VR) device, a robot, a wearable device (Wearable Device), a vehicle-mounted device (VUE), a pedestrian terminal (PUE), a smart home (a home device with a wireless communication function, such as a refrigerator, a television, a washing machine, or furniture, etc.), and the like. The wearable device includes a smart watch, a smart bracelet, a smart earphone, smart glasses, smart jewelry (a smart bracelet, a smart necklace, a smart ring, a smart necklace, a smart anklet, a smart necklace, etc.), a smart wristband, smart clothing, a game console, and the like. It should be noted that the specific type of the terminal is not limited in the embodiments of the present application.

[0040] It is worth noting that the wireless access network described in the embodiments of the present application is not limited to the LTE / LTE-A system, but can also be used in other wireless communication systems, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described techniques can be used in the above-mentioned systems and radio technologies, and can also be used in other systems and radio technologies, such as non-3GPP access systems (e.g., WLAN, fixed access system, Bluetooth, etc.). The following description describes the NR system for example purposes, and NR terminology is used in most of the following description, and these techniques can also be applied to applications other than NR system applications, such as 6G communication systems.

[0041] Exemplarily, the core network can include at least one of the following functions or network elements: a session management function (e.g., Session Management Function, SMF), an access and mobility management function (e.g., Access and Mobility Management Function, AMF), a user plane function (e.g., User Port Function, UPF), a policy control function (e.g., Policy Control Function, PCF), a unified data network element, and a network exposure function (e.g., Network Exposure Function, NEF). It should be noted that the above core network functions can be implemented by multiple devices, or multiple core network functions can be implemented by one device, and the embodiments of the present application do not limit this.

[0042] Exemplarily, in the 5G system, the unified data network element can include a unified data management network element (e.g., Unified Data Management, UDM) or a unified data storage network element (Unified Data Repository, UDR). It should be noted that the above unified data network element can also be referred to as a user subscription database.

[0043] It should be noted that the above network element can also be other network elements with the same function or the same type, but the specific name can be different from the above network element name, and the embodiments of the present application do not limit this.

[0044] In the related art, the PVS can send the credential information of the service parameter (such as the credential for secondary authentication of the DNN, or the credential information for network slice authentication) to the terminal in an automatic pushing manner. However, after the PVS successfully automatically pushes the credential information to the terminal, the subscription of the terminal also needs to be updated in time to allow the terminal to use the service parameter. Otherwise, when the terminal requests to access the DNN or the network slice, the network can refuse the request of the terminal. There is currently no effective solution for how to update the subscription of the terminal in time.

[0045] In the technical solution provided in the embodiments of the present application, after receiving the credential successful pushing indication, the unified data network element learns that the credential corresponding to the target service parameter has been successfully pushed to the target terminal, so that the target service parameter can be enabled in the subscription of the target terminal, thereby updating the subscription data of the target terminal in time, and the target terminal can be provided with services according to the terminal service request authorized by the subscription of the target terminal.

[0046] The method, device, network element and medium for updating the subscription provided in the embodiments of the present application will be described in detail in combination with the accompanying drawings and some embodiments and application scenarios.

[0047] The embodiment of the present application provides a method for updating a subscription, as shown in the figure, the method for updating the subscription provided by the embodiment of the present application can comprise the following steps 201 and 202. Figure 2

[0048] Step 201: receiving, by a unified data network element, a credential success pushing indication.

[0049] In the embodiment of the present application, the credential success pushing indication is used to indicate that the credential corresponding to the target service parameter has been successfully pushed to the target terminal.

[0050] In some possible embodiments, the target terminal can be a predetermined or preconfigured terminal. For example, the unified data network element or the communication network preconfigures the target terminal corresponding to the target parameter. The unified data network element can obtain the target terminal corresponding to the target parameter from the local or the communication network.

[0051] In some possible embodiments, the method for updating the subscription provided by the embodiment of the present application can further comprise step 201a.

[0052] Step 201a: receiving, by a unified data network element, a first terminal identifier.

[0053] The target terminal can comprise a terminal indicated by the first terminal identifier.

[0054] Further, the step 201a can comprise the following step 201a1.

[0055] Step 201a1: receiving, by a unified data network element, the first terminal identifier from a network exposure network element.

[0056] In some possible embodiments, the step 201 can comprise the following step 201b.

[0057] Step 201b: receiving, by a unified data network element, the credential success pushing indication from a network exposure network element.

[0058] In some possible embodiments, the credential success pushing indication comprises a target service parameter.

[0059] In some possible embodiments, the credential success pushing indication comprises information for describing the target service parameter.

[0060] In some possible embodiments, the target service parameter comprises at least one of the following: a DNN, an S-NSSAI.

[0061] ​In some possible embodiments, the first terminal identifier comprises at least one of: an IP address of the target terminal, a MAC address of the target terminal, an International Mobile Subscriber Identity (IMSI) of the target terminal, a Subscription Permanent Identifier (SUPI) of the target terminal, a Mobile Station International Service Digital Network (MSISDN) of the target terminal, and a Generic Public Subscription Identifier (GPSI) of the target terminal.

[0062] In some possible embodiments, the indication of successful pushing of the credential further comprises: a credential corresponding to the target service parameter.

[0063] In some possible embodiments, the indication of successful pushing of the credential further comprises a first authentication indication.

[0064] The first authentication indication is used to indicate that the target service parameter needs further authentication.

[0065] The first authentication indication comprises at least one of:

[0066] an indication that secondary authentication is needed for the target service parameter,

[0067] an indication that network slice authentication is needed for the target service parameter.

[0068] In some possible embodiments, the unified data network element can receive the first terminal identifier and the indication of successful pushing of the credential from the server.

[0069] In some possible embodiments, the unified data network element can receive the first terminal identifier and the indication of successful pushing of the credential from the server.

[0070] Step 202: enabling the target service parameter in the subscription of the target terminal by the unified data network element.

[0071] In some possible embodiments, the unified data network element activates the configured target service parameter in the subscription of the target terminal.

[0072] In some possible embodiments, the step 202 can further comprise the following process: storing the target service parameter in the subscription of the target terminal by the unified data network element.

[0073] Optionally, after storing the target service parameters in the target terminal's subscription, the unified data network element can further activate the target service parameters.

[0074] Optionally, the process by which a unified data network element activates target service parameters in the subscription of a target terminal can be considered as follows: the unified data network element first determines the configured target service parameters, and then activates those parameters. It is worth noting that for different users' subscription data, some may have already been configured with service parameters, while others may not. In this scenario, the unified data network element can first determine whether the relevant user's subscription data contains configured service parameters, and then, based on whether the service parameters are configured, perform the corresponding activation or storage action for those parameters.

[0075] In some possible embodiments, the subscription update method provided in this application may further include the following step 203:

[0076] Step 203: The unified data network element determines the Closed Access Group Identifier (CAG) that the target terminal can use based on the target service parameters.

[0077] For example, a unified data network element can determine the CAG that the target terminal can use based on an enabled DNN and / or an enabled S-NSSAI.

[0078] Furthermore, based on step 203, the subscription update method provided in this application embodiment may further include the following step 204:

[0079] Step 204: The unified data network element activates or stores the CAG in the target terminal's subscription.

[0080] For example, for different users' subscription data, some may have a CAG configured, while others may not. Therefore, after determining the CAG that the target terminal can use, the unified data network element will perform the corresponding activation or storage action based on whether the CAG is configured. For example, the unified data network element may directly activate the configured CAG, or it may activate the stored CAG after storing the unconfigured CAG.

[0081] It is worth noting that steps 203 and 204 can occur before or after step 202, and step 204 can also occur simultaneously with step 202. That is, the order of steps 203 and 204 with step 202 is not limited in this application.

[0082] In some possible embodiments, the subscription update method provided in this application may further include the following step 205:

[0083] Step 205: The unified data network element sends the updated subscription of the target terminal to the target terminal.

[0084] Exemplarily, the updated subscription includes at least one of the following:

[0085] enabled DNN,

[0086] enabled S-NSSAI,

[0087] CAG determined based on the enabled DNN and / or the enabled S-NSSAI.

[0088] In an example, the updated subscription includes at least one of the following:

[0089] activated DNN,

[0090] activated S-NSSAI,

[0091] CAG determined based on the activated DNN and / or the activated S-NSSAI.

[0092] Further, based on step 205, in the case of the unified data network element being a UDR, the method for updating the subscription provided by the embodiments of the present application can further include the following step 206:

[0093] Step 206: The UDR sends the updated subscription of the target terminal to the UDM.

[0094] In the method for updating the subscription provided by the embodiments of the present application, after receiving the credential successful pushing indication, the unified data network element can enable the target service parameter in the subscription of the target terminal, so that the subscription data of the target terminal is updated in time, and then the target terminal can be provided with services according to the terminal service request authorized by the subscription of the target terminal.

[0095] The embodiments of the present application provide another method for updating the subscription, which is combined with Figure 2 and Figure 3 As shown in the figures, the method for updating the subscription provided by the embodiments of the present application can include the following steps 301 to 303:

[0096] Step 301: The server sends a credential successful pushing indication to the unified data network element.

[0097] Step 302: The unified data network element receives the credential successful pushing indication.

[0098] Step 303: The unified data network element enables the target service parameter in the subscription of the target terminal.

[0099] It should be noted that the related descriptions of steps 302 and 303 in the present embodiment can refer to the foregoing descriptions, and to avoid repetition, they will not be described here again.

[0100] In some possible embodiments, step 301 above may further include step 301a:

[0101] Step 301a: The server sends the first terminal identifier to the unified data network element.

[0102] In some possible embodiments, step 301a above may further include the following step 301a1:

[0103] Step 301a1: The server sends the first terminal identifier to the unified data network element through the network open network element.

[0104] In some possible embodiments, step 302 above may further include step 302a:

[0105] Step 302a: The unified data network element receives the first terminal identifier.

[0106] In some possible embodiments, step 301 above may further include step 301b:

[0107] Step 301b: The server sends a successful credential push indication to the unified data network element.

[0108] For example, the server sends a successful credential push indication to the unified data network element through the network open network element.

[0109] In the subscription update method provided in this application embodiment, the server sends a successful credential push instruction to the unified data network element, so that after receiving the successful credential push instruction, the unified data network element can enable the target service parameters in the subscription of the target terminal, thereby updating the subscription data of the target terminal in a timely manner, and then providing services to the target terminal according to the terminal service request authorized by the target terminal subscription.

[0110] This application provides another method for contract renewal, combined with... Figure 2 ,like Figure 4 As shown, the subscription update method provided in this application embodiment may include the following step 401:

[0111] Step 401: Successful receipt of credentials by network open element is pushed to the network.

[0112] Step 402: The open network element sends a successful credential push instruction to the unified data network element.

[0113] Step 403: Unified data network element successfully pushed the receipt of credentials.

[0114] Step 404: The unified data network element enables the target service parameters in the target terminal's subscription.

[0115] It should be noted that the related description of steps 403 and 404 in this embodiment can refer to the foregoing description, and details are not described here to avoid repetition.

[0116] In some possible embodiments, the step 401 can further include the following step A1:

[0117] Step A1: The network exposure network element obtains the first terminal identifier.

[0118] In some possible embodiments, the step 402 can further include the following step A2:

[0119] Step A2: The network exposure network element sends the first terminal identifier to the unified data network element.

[0120] In some possible embodiments, the step 403 can further include the following step A3:

[0121] Step A3: The unified data network element receives the first terminal identifier.

[0122] In some possible embodiments, the network exposure network element can receive the first terminal identifier and the credential successful push indication from the server side.

[0123] In some possible embodiments, the step A1 can include the following steps 401a and 401b:

[0124] Step 401a: The network exposure network element obtains the target address of the target terminal and the credential successful push indication.

[0125] The target address of the target terminal includes an IP address of the target terminal or a MAC address of the target terminal.

[0126] For example, the network exposure network element can receive the target address of the target terminal and the credential successful push indication from the server.

[0127] Step 401b: The network exposure network element obtains the second terminal identifier corresponding to the target address of the target terminal.

[0128] For example, in combination with the steps 401a and 401b, the step 402 can include that the network exposure network element sends the second terminal identifier and the credential successful push indication to the unified data network element, and correspondingly, the step 403 can include that the unified data network element receives the second terminal identifier and the credential successful push indication.

[0129] It should be noted that the second terminal identifier can be the same as the first terminal identifier, or can be different from the first terminal identifier, and the embodiments of the present application do not limit this.

[0130] It can be understood that the terminal identifier sent by the network exposure network element to the unified data network element is a second terminal identifier, or the terminal identifier sent by the network exposure network element to the unified data network element can simultaneously include the IP address or the MAC address of the target terminal and the second terminal identifier, and the embodiments of the present application do not limit this.

[0131] In a possible example, the step 401b can include the following steps 401b1 and 401b2.

[0132] Step 401b1: The network exposure network element sends the target address of the target terminal to the policy control network element.

[0133] Step 401b2: The network exposure network element obtains the second terminal identifier corresponding to the target address of the target terminal from the policy control network element.

[0134] In a possible example, the second terminal identifier includes at least one of the following: IMSI of the target terminal, SUPI of the target terminal, MSISDN of the target terminal, and GPSI of the target terminal.

[0135] In a possible example, the network exposure network element sends a policy service request (for example, an Npcf_PolicyAuthorization_Create service request) to the policy control network element, where the policy service request includes the target address (such as an IP address or a MAC address) of the target terminal. After receiving the policy service request, the policy control network element sends a policy service response (for example, an Npcf_PolicyAuthorization_Create service response) to the network exposure network element, and the policy service response includes the second terminal identifier of the target terminal.

[0136] In the method for updating a subscription provided by the embodiments of the present application, the network exposure network element sends a credential successful push indication to the unified data network element, so that the unified data network element activates a target service parameter in the subscription of the target terminal after receiving the credential successful push indication, thereby updating the subscription data of the target terminal in a timely manner, and further providing services for the target terminal according to a terminal service request authorized by the subscription of the target terminal.

[0137] The embodiments of the present application provide another method for updating a subscription, as shown in Figure 5 The method for updating a subscription provided by the embodiments of the present application can include the following step 501.

[0138] Step 501: The policy control network element obtains a target address of a target terminal.

[0139] The target address of the target terminal includes an IP address of the target terminal or a MAC address of the target terminal.

[0140] In a possible example, the policy control network element can receive the target address of the target terminal and the credential success push indication from the server. Optionally, the policy control network element can receive the target address of the target terminal and the credential success push indication from the server through the network exposure network element.

[0141] Step 502: The policy control network element determines the second terminal identifier corresponding to the target address of the target terminal.

[0142] Step 503: The policy control network element sends the second terminal identifier to the network exposure network element or the unified data network element.

[0143] The second terminal identifier is used to update the subscription of the terminal indicated by the second terminal identifier.

[0144] In a possible example, the second terminal identifier includes at least one of the following: IMSI of the target terminal, SUPI of the target terminal, MSISDN of the target terminal, and GPSI of the target terminal.

[0145] In a possible example, the policy control network element can also send the second terminal identifier to the network exposure network element. The network exposure network element can also send the second terminal identifier and the credential success push indication to the unified data network element, so that the unified data network element updates the subscription data of the terminal indicated by the second terminal identifier according to the second terminal identifier.

[0146] In a possible example, the policy control network element can also send the second terminal identifier to the unified data network element, so that the unified data network element updates the subscription data of the terminal indicated by the second terminal identifier according to the second terminal identifier.

[0147] In the subscription updating method provided in the embodiments of the present application, the policy control network element obtains the target address (i.e., the IP address of the target terminal or the MAC address of the target terminal) of the target terminal and the corresponding second terminal identifier, so that the communication network can update the subscription of the terminal indicated by the second terminal identifier in time.

[0148] It should be noted that the subscription updating methods shown in the above embodiments can be combined with each other in the embodiments of the present application. That is, the subscription updating methods shown in the above embodiments can also be combined with any one or more of the other embodiments shown in the above embodiments in the specific implementation, which will not be described herein again. For example, the subscription updating methods provided in the embodiments shown in the above Figure 4 and Figure 5 After the subscription updating methods provided in the embodiments shown in the above

[0149] The subscription update solution provided by the embodiments of the present application will be exemplarily described below.

[0150] The following examples take the server as the PVS, the unified data network element as the UDM and / or UDR, the network exposure network element as the NEF, the policy control network element as the PCF, and the terminal as the UE as examples for description. It should be noted that the network element names in the following examples are only examples, and other network element names can also be used in actual application, and the embodiments of the present application do not limit this.

[0151] Embodiment one:

[0152] The prerequisite for the embodiment to be executed can be that the service parameters (namely, DNN or S-NSSAI) can be pre-configured in the UE, and the indication of the secondary authentication or NSSAA is required, but the credential is not configured; or the foregoing information can also be pre-configured in the UE. Meanwhile, the DNN or S-NSSAI is not configured in the UDR / UDM.

[0153] Exemplarily, as shown in the following table, the technical solution provided by the embodiment can be implemented through the following steps: Figure 6

[0154] Step S11: The UE establishes a PDU session, and downloads the credential of the DNN or S-NSSAI from the PVS.

[0155] Exemplarily, the UE requests to establish a PDU session using the configured DNN or S-NSSAI, and obtains the PVS address in the process of establishing the session. The UE contacts the PVS indicated by the PVS address, and obtains the credential of the DNN or S-NSSAI.

[0156] Step S12: The PVS sends the UE identifier and the credential of the DNN or S-NSSAI to the UDM of the UE, and sends a successful push indication.

[0157] The UE identifier can include at least one of the following: the IP address of the UE, the MAC address of the UE, the IMSI of the UE, the GPSI of the UE, the MSISDN of the UE, the SUPI of the UE, the SUCI of the UE, or other temporary or permanent identifiers of the UE, or other internal or external identifiers of the UE.

[0158] ​The credential success push indication can include a DNN or S-NSSAI and corresponding credential, or can send a DNN or S-NSSAI and an indication of "secondary authentication required" or "NSSAA required", or send a "DNN requiring secondary authentication" or "S-NSSAI requiring NSSAA" parameter. Meanwhile, the credential success push indication contains the DNN or S-NSSAI.

[0159] It should be noted that this step can be sent by the PVS directly to the UDM, or sent by the PVS to the UDM through the NEF.

[0160] Exemplarily, the PVS can send the UE identifier and the credential success push indication to the NEF using the Nnef_ServiceParameter_Create service. The NEF sends the UE identifier and the credential success push indication to the UDM.

[0161] Step S13: The UDM receives the credential success push indication and stores the DNN or S-NSSAI and the indication of secondary authentication required or NSSAA required in the subscription of the UE.

[0162] Step S14: The UDM can determine the CAG that the UE can use according to the DNN or S-NSSAI, and store the CAG in the subscription of the UE.

[0163] It should be noted that the UDM in this embodiment can be replaced by the UDR.

[0164] In an example, the UDR sends an updated subscription of the UE to the UDM, including a new DNN or S-NSSAI. Further, the updated subscription also includes the CAG determined according to the new DNN or S-NSSAI.

[0165] Optionally, the embodiment scheme can further include:

[0166] Step S15: The UDM sends the updated subscription to the UE.

[0167] The updated subscription includes a new DNN or S-NSSAI. Further, the updated subscription also includes the CAG determined according to the new DNN or S-NSSAI.

[0168] Optionally, the embodiment scheme can further include:

[0169] Step S16: The UE activates the configured DNN or S-NSSAI.

[0170] If the DNN or S-NSSAI is pre-configured in the UE, the corresponding DNN or S-NSSAI will be activated upon receiving an updated subscription. Optionally, the UE may also activate the corresponding CAG information. For example, the UE may mark the DNN, S-NSSAI, or CAG as "activated" or delete the "deactivated" state of the DNN, S-NSSAI, or CAG.

[0171] Alternatively, if the DNN or S-NSSAI is not configured in the UE, the UE stores the corresponding DNN or S-NSSAI after receiving the updated subscription. Optionally, the UE also stores the corresponding CAG information.

[0172] It is worth noting that in actual use, the UE may not need to determine whether the aforementioned information has been configured in advance; that is, after receiving the updated subscription, it may perform the above activation or storage operations.

[0173] Example 2:

[0174] The prerequisite for this embodiment is that the UDR / UDM has pre-configured DNN or S-NSSAI and an indication requiring secondary authentication or NSSAA, but no credential is configured. The UE can pre-configure service parameters (i.e., DNN or S-NSSAI) and an indication requiring secondary authentication or NSSAA, but no credential is configured; or, the UE may not have pre-configured the aforementioned information.

[0175] For example, such as Figure 7 As shown, the technical solution provided in this embodiment can be implemented through the following steps:

[0176] Step S21: The UE establishes a PDU session and downloads the DNN or S-NSSAI credentials from the PVS.

[0177] For a detailed description of the relevant content of this step, please refer to the description in Example 1, which will not be repeated here.

[0178] Step S22: The PVS sends the UE identifier and the DNN or S-NSSAI credential successful push indication to the UE's UDM.

[0179] For a detailed description of the relevant content of this step, please refer to the description in Example 1, which will not be repeated here.

[0180] Step S23: UDM receives the successful push indication of the credential and activates the DNN or S-NSSAI in the UE's subscription.

[0181] Step S24: The UDM can determine the CAG that the UE can use according to the DNN or S-NSSAI, store the CAG in the UE subscription, or directly activate the corresponding CAG.

[0182] It should be noted that the UDM in the embodiment can be replaced by the UDR.

[0183] In an example, the UDR sends the updated subscription of the UE to the UDM, including the new DNN or S-NSSAI. Further, the updated subscription also includes the CAG determined according to the new DNN or S-NSSAI.

[0184] Optionally, the embodiment scheme can further include:

[0185] Step S25: The UDM sends the updated subscription to the UE.

[0186] Optionally, the embodiment scheme can further include:

[0187] Step S26: The UE activates the configured DNN or S-NSSAI.

[0188] Steps S25-S26 can refer to the description of steps S15-S16 in the above embodiment one.

[0189] In addition, it should be noted that if in step S12 in the above embodiment one and step S22 in embodiment two: the UE identifier received by the NEF is the IP address and / or MAC address of the UE, the NEF can also query the internal identifier of the UE corresponding to the IP address, such as GPSI, IMSI, SUPI, MSISDN or SUCI, from the PCF first.

[0190] In an example, the NEF sends the Npcf_PolicyAuthorization_Create service request to the PCF, wherein the Npcf_PolicyAuthorization_Create service request includes the IP address and / or MAC address of the UE, and the PCF sends the Npcf_PolicyAuthorization_Create service response to the NEF, which contains the IMSI of the UE. The NEF sends the IMSI of the UE and the credential success push indication to the UDR / UDM.

[0191] It should be noted that the method for updating the subscription provided in the embodiments of the present application can be executed by the device for updating the subscription, or a control module in the device for updating the subscription for executing the method for updating the subscription. In the embodiments of the present application, the device for updating the subscription is taken as an example to illustrate the device for updating the subscription provided in the embodiments of the present application.

[0192] The device for updating the subscription provided in the embodiments of the present application can include a transmission module 601 and an execution module 602, where: Figure 8

[0193] The transmission module 601 is configured to receive a credential success pushing indication, and the credential success pushing indication is used to indicate that the credential corresponding to the target service parameter has been successfully pushed to the target terminal.

[0194] In some possible embodiments, the credential success pushing indication includes the target service parameter.

[0195] In some possible embodiments, the target service parameter includes at least one of the following: a DNN and an S-NSSAI.

[0196] In some possible embodiments, the transmission module 601 is further configured to receive a first terminal identifier, and the target terminal includes a terminal indicated by the first terminal identifier.

[0197] In some possible embodiments, the first terminal identifier includes at least one of the following: an IP address of the target terminal, a MAC address of the target terminal, an IMSI of the target terminal, a SUPI of the target terminal, an MSISDN of the target terminal, and a GPSI of the target terminal.

[0198] In some possible embodiments, the credential success pushing indication further includes the credential corresponding to the target service parameter.

[0199] In some possible embodiments, the credential success pushing indication further includes a first authentication indication.

[0200] In some possible embodiments, the first authentication indication includes at least one of the following:

[0201] an indication that secondary authentication is required for the target service parameter,

[0202] an indication that network slice authentication is required for the target service parameter.

[0203] In some possible embodiments, the execution module 602 is specifically configured to activate and / or store the target service parameter in the subscription of the target terminal. ​

[0204] In some possible embodiments, the execution module 602 is further configured to determine the CAG that the target terminal can use based on the target service parameters.

[0205] In some possible embodiments, the execution module 602 is also configured to activate or store the aforementioned CAG in the subscription of the target terminal.

[0206] In some possible embodiments, the transmission module 601 is also configured to send the updated subscription of the target terminal to the target terminal.

[0207] In some possible embodiments, the transmission module 601 is also configured to send the updated subscription of the target terminal to the UDM.

[0208] In some possible embodiments, the updated contract described above includes at least one of the following:

[0209] Enabled DNN,

[0210] Enabled S-NSSAI,

[0211] CAG determined based on enabled DNN and / or enabled S-NSSAI.

[0212] In some possible embodiments, the transmission module 601 is specifically configured to: receive a successful credential push indication from a network open element.

[0213] In some possible embodiments, the transmission module 601 is specifically used to: receive a first terminal identifier from a network open element.

[0214] In the subscription update device provided in this application embodiment, after receiving the successful credential push instruction, the device can know that the credential corresponding to the target service parameter has been successfully pushed to the target terminal based on the successful credential push instruction. At this time, the device can enable the target service parameter in the subscription of the target terminal, thereby updating the subscription data of the target terminal in a timely manner, and then providing services to the target terminal according to the terminal service request authorized by the target terminal subscription.

[0215] This application provides a device for contract renewal, such as... Figure 9 As shown, the subscription update device may include: a transmission module 701, wherein:

[0216] The transmission module 701 is used to send a successful credential push indication to the unified data network element; the successful credential push indication is used to indicate that the credential corresponding to the target service parameter has been successfully pushed to the target terminal.

[0217] In some possible embodiments, the successful credential delivery indication includes target service parameters.

[0218] In some possible embodiments, the target service parameter includes at least one of the following: a DNN, an S-NSSAI.

[0219] In some possible embodiments, the transmission module 701 is further configured to send, to the unified data network element, a first terminal identifier; and the target terminal includes a terminal indicated by the first terminal identifier.

[0220] In some possible embodiments, the first terminal identifier includes at least one of the following: an IP address of the target terminal, a MAC address of the target terminal, an IMSI of the target terminal, a SUPI of the target terminal, an MSISDN of the target terminal, and a GPSI of the target terminal.

[0221] In some possible embodiments, the credential success pushing indication further includes a credential corresponding to the target service parameter.

[0222] In some possible embodiments, the credential success pushing indication further includes a first authentication indication.

[0223] The first authentication indication is used to indicate that the target service parameter needs further authentication.

[0224] The first authentication indication includes at least one of the following:

[0225] an indication that secondary authentication is required for the target service parameter,

[0226] an indication that network slice authentication is required for the target service parameter.

[0227] In some possible embodiments, the transmission module 701 is specifically configured to send, to the network exposure network element, the credential success pushing indication.

[0228] In some possible embodiments, the transmission module 701 is specifically configured to send, to the unified data network element, the first terminal identifier through the network exposure network element.

[0229] In the device for subscription updating provided in the embodiments of the present application, the device sends, to the unified data network element, the credential success pushing indication, so that the unified data network element enables the target service parameter in the subscription of the target terminal after receiving the credential success pushing indication, thereby updating the subscription data of the target terminal in a timely manner, and further providing services for the target terminal according to the terminal service request authorized by the subscription of the target terminal.

[0230] A device for subscription updating provided in the embodiments of the present application, as shown in Figure 10 The device for subscription updating can include an execution module 801 and a transmission module 802, where:

[0231] The execution module 801 is configured to acquire a credential successful push indication; the transmission module 802 is configured to send the credential successful push indication acquired by the execution module 801 to a unified data network element; and the credential successful push indication is used to indicate that a credential corresponding to a target service parameter has been successfully pushed to a target terminal.

[0232] In some possible embodiments, the credential successful push indication comprises the target service parameter.

[0233] In some possible embodiments, the target service parameter comprises at least one of a DNN and an S-NSSAI.

[0234] In some possible embodiments, the credential successful push indication further comprises the credential corresponding to the target service parameter.

[0235] In some possible embodiments, the credential successful push indication further comprises a first authentication indication.

[0236] The first authentication indication comprises at least one of the following:

[0237] an indication that secondary authentication is required for the target service parameter,

[0238] an indication that network slice authentication is required for the target service parameter.

[0239] In some possible embodiments, the execution module 801 is further configured to acquire a first terminal identifier; and the transmission module 802 is further configured to send the first terminal identifier to the unified data network element.

[0240] In some possible embodiments, the transmission module 802 is further configured to receive a target address of the target terminal and the credential successful push indication, and the target address comprises an IP address of the target terminal or a MAC address of the target terminal; and the execution module 801 is specifically configured to acquire a second terminal identifier corresponding to the target address.

[0241] In some possible embodiments, the transmission module 802 is further configured to send the target address of the target terminal to a policy control network element; and the transmission module 802 is further configured to receive the second terminal identifier corresponding to the target address from the policy control network element.

[0242] In some possible embodiments, the first terminal identifier comprises at least one of the following: an IP address of the target terminal, a MAC address of the target terminal, an IMSI of the target terminal, a SUPI of the target terminal, an MSISDN of the target terminal, and a GPSI of the target terminal.

[0243] In some possible embodiments, the second terminal identifier includes at least one of the following: an IMSI of the target terminal, a SUPI of the target terminal, an MSISDN of the target terminal, and a GPSI of the target terminal.

[0244] In the device for updating a subscription provided in the embodiments of the present application, the device sends a credential successful pushing indication to a unified data network element, so that the unified data network element enables a target service parameter in a subscription of a target terminal after receiving the credential successful pushing indication, thereby updating subscription data of the target terminal in a timely manner, and further providing a service for the target terminal according to a terminal service request authorized by the subscription of the target terminal.

[0245] The device for updating a subscription provided in the embodiments of the present application can be, for example, as shown in Figure 11 The device for updating a subscription can include a transmission module 901 and an execution module 902, where:

[0246] The execution module 902 is configured to obtain a destination address of a target terminal, where the destination address includes an IP address of the target terminal or a MAC address of the target terminal; the execution module 902 is further configured to determine a second terminal identifier corresponding to the destination address; and the transmission module 901 is further configured to send the second terminal identifier to a network exposure network element or a unified data network element, where the second terminal identifier is used to update a subscription of a terminal indicated by the second terminal identifier.

[0247] In some possible embodiments, the second terminal identifier includes at least one of the following: an IMSI of the target terminal, a SUPI of the target terminal, an MSISDN of the target terminal, and a GPSI of the target terminal.

[0248] In the device for updating a subscription provided in the embodiments of the present application, the device obtains a second terminal identifier corresponding to a destination address (i.e., an IP address of a target terminal or a MAC address of the target terminal) of a target terminal, so that a communication network can update a subscription of a terminal indicated by the second terminal identifier in a timely manner.

[0249] The device for resource allocation of a computing task or the device for policy determination of a computing task in the embodiments of the present application can be a device, a device with an operating system, or an electronic device, and can also be a component in a device, an integrated circuit, or a chip. The device or the electronic device can be a network element, a node device, a server, a Network Attached Storage (NAS), a personal computer (PC), and the like, and the embodiments of the present application are not limited in this regard.

[0250] The device for updating a subscription provided in the embodiments of the present application can achieve the following effects. Figures 2 to 7The method embodiments of the application achieve the various processes and achieve the same technical effects, and thus, details are not repeated here.

[0251] Optionally, as shown in Figure 12 The application also provides a communication device 1000, which includes a processor 1001, a memory 1002, and a program or instruction stored in the memory 1002 and executable on the processor 1001. For example, when the communication device 1000 is a network side device, the program or instruction is executed by the processor 1001 to implement the various processes of the above method embodiments and achieve the same technical effects. To avoid repetition, details are not repeated here.

[0252] The application also provides a network side device, which includes a processor and a communication interface. The network side device embodiment corresponds to the above network side device method embodiment, and the various implementation processes and implementation manners of the above method embodiment can be applied to the network side device embodiment and achieve the same technical effects.

[0253] In an example, the network side device is a unified data network element, which includes a processor and a communication interface. The communication interface is configured to receive a credential success push indication. The credential success push indication is used to indicate that a credential corresponding to a target service parameter has been successfully pushed to a target terminal. The processor is configured to enable the target service parameter in a subscription of the target terminal.

[0254] In some possible examples, the credential success push indication includes the target service parameter.

[0255] In some possible examples, the target service parameter includes at least one of the following: a DNN and an S-NSSAI.

[0256] In some possible examples, the communication interface is further configured to receive a first terminal identifier. The target terminal includes a terminal indicated by the first terminal identifier.

[0257] In some possible examples, the first terminal identifier includes at least one of the following: an IP address of the target terminal, a MAC address of the target terminal, an IMSI of the target terminal, a SUPI of the target terminal, an MSISDN of the target terminal, and a GPSI of the target terminal.

[0258] In some possible examples, the credential success push indication further includes the credential corresponding to the target service parameter.

[0259] In some possible examples, the credential success push indication further includes a first authentication indication.

[0260] The first authentication indication includes at least one of the following:

[0261] an indication for indicating that secondary authentication is required for a target service parameter,

[0262] an indication for indicating that network slice authentication is required for a target service parameter.

[0263] In some possible examples, the processor is specifically configured to activate and / or store the target service parameter in a subscription of the target terminal.

[0264] In some possible examples, the processor is further configured to determine a CAG available to the target terminal according to the target service parameter.

[0265] In some possible examples, the processor is further configured to enable or store the CAG in the subscription of the target terminal.

[0266] In some possible examples, the communication interface is specifically configured to send the updated subscription of the target terminal to the target terminal.

[0267] In some possible examples, the communication interface is specifically configured to send the updated subscription of the target terminal to the UDM.

[0268] In some possible examples, the updated subscription includes at least one of the following:

[0269] an enabled DNN,

[0270] an enabled S-NSSAI,

[0271] a CAG determined based on the enabled DNN and / or the enabled S-NSSAI.

[0272] In some possible examples, the communication interface is specifically configured to receive the credential successful push indication from the network exposure network element.

[0273] In some possible examples, the communication interface is specifically configured to receive the first terminal identifier from the network exposure network element.

[0274] In the unified data network element provided in the examples of the present application, after receiving the credential successful push indication, the unified data network element can learn that the credential corresponding to the target service parameter has been successfully pushed to the target terminal based on the credential successful push indication. At this time, the device can enable the target service parameter in the subscription of the target terminal, so as to update the subscription data of the target terminal in a timely manner, and then provide services for the target terminal according to the terminal service request authorized by the subscription of the target terminal.

[0275] In an example, the network-side device is a server, comprising a processor and a communication interface, wherein the communication interface is configured to send a credential success push indication to a unified data network element; and the credential success push indication is configured to indicate that a credential corresponding to a target service parameter has been successfully pushed to a target terminal.

[0276] In some possible examples, the credential success push indication comprises the target service parameter.

[0277] In some possible examples, the target service parameter comprises at least one of a DNN and an S-NSSAI.

[0278] In some possible examples, the communication interface is further configured to send a first terminal identifier to the unified data network element; and the target terminal comprises a terminal indicated by the first terminal identifier.

[0279] In some possible examples, the first terminal identifier comprises at least one of an IP address of the target terminal, a MAC address of the target terminal, an IMSI of the target terminal, a SUPI of the target terminal, an MSISDN of the target terminal, and a GPSI of the target terminal.

[0280] In some possible examples, the credential success push indication further comprises the credential corresponding to the target service parameter.

[0281] In some possible examples, the credential success push indication further comprises a first authentication indication.

[0282] The first authentication indication is configured to indicate that the target service parameter needs further authentication.

[0283] The first authentication indication comprises at least one of:

[0284] an indication that secondary authentication is needed for the target service parameter,

[0285] an indication that network slice authentication is needed for the target service parameter.

[0286] In some possible examples, the communication interface is specifically configured to send the credential success push indication to a network exposure network element.

[0287] In some possible examples, the communication interface is specifically configured to send the first terminal identifier to the unified data network element through the network exposure network element.

[0288] In the server provided in the examples of the present application, the server sends a credential successful push indication to the unified data network element, so that the unified data network element enables the target service parameter in the subscription of the target terminal after receiving the credential successful push indication, thereby updating the subscription data of the target terminal in time, and further providing services for the target terminal according to the terminal service request authorized by the subscription of the target terminal.

[0289] In an example, the network-side device is a network exposure network element, comprising a processor and a communication interface, wherein the processor is configured to obtain a credential successful push indication; the communication interface is configured to send the credential successful push indication obtained by the processor to a unified data network element; wherein the credential successful push indication comprises a target service parameter; and the credential successful push indication is used to indicate that the credential corresponding to the target service parameter has been successfully pushed to a target terminal.

[0290] In some possible examples, the credential successful push indication comprises the target service parameter.

[0291] In some possible examples, the target service parameter comprises at least one of a DNN and an S-NSSAI.

[0292] In some possible examples, the credential successful push indication further comprises a credential corresponding to the target service parameter.

[0293] In some possible examples, the credential successful push indication further comprises a first authentication indication.

[0294] The first authentication indication is used to indicate that the target service parameter needs further authentication.

[0295] The first authentication indication comprises at least one of:

[0296] an indication that the target service parameter needs secondary authentication,

[0297] an indication that the target service parameter needs network slice authentication.

[0298] In some possible examples, the processor is further configured to obtain a first terminal identifier; and the communication interface is further configured to send the first terminal identifier to the unified data network element.

[0299] In some possible examples, the communication interface is further configured to receive a target address of the target terminal and the credential successful push indication, wherein the target address comprises an IP address of the target terminal or a MAC address of the target terminal; and the processor is specifically configured to obtain a second terminal identifier corresponding to the target address.

[0300] In some possible examples, the communication interface is further configured to send the target address of the target terminal to a policy control network element; and the communication interface is further configured to receive a second terminal identifier corresponding to the target address from the policy control network element.

[0301] In some possible examples, the first terminal identifier includes at least one of: an IP address of the target terminal, a MAC address of the target terminal, an IMSI of the target terminal, a SUPI of the target terminal, an MSISDN of the target terminal, and a GPSI of the target terminal.

[0302] In some possible examples, the second terminal identifier includes at least one of: an IMSI of the target terminal, a SUPI of the target terminal, an MSISDN of the target terminal, and a GPSI of the target terminal.

[0303] In the network exposure network element provided in the examples of the present application, the network exposure network element sends a credential successful push indication to the unified data network element, so that the unified data network element enables a target service parameter in the subscription of the target terminal after receiving the credential successful push indication, thereby updating the subscription data of the target terminal in a timely manner, and further providing services for the target terminal according to a terminal service request authorized by the subscription of the target terminal.

[0304] In an example, the network-side device is a policy control network element, including a processor and a communication interface, wherein the processor is configured to obtain a destination address of a target terminal, the destination address including an IP address of the target terminal or a MAC address of the target terminal; the processor is further configured to determine a second terminal identifier corresponding to the target address; and the communication interface is further configured to send the second terminal identifier to the network exposure network element or the unified data network element, wherein the second terminal identifier is used to update the subscription of a terminal indicated by the second terminal identifier.

[0305] In some possible examples, the second terminal identifier includes at least one of: an IMSI of the target terminal, a SUPI of the target terminal, an MSISDN of the target terminal, and a GPSI of the target terminal.

[0306] In the policy control network element provided in the examples of the present application, the policy control network element obtains a second terminal identifier corresponding to a target address (i.e., an IP address of a target terminal or a MAC address of the target terminal) of a target terminal, so that the communication network can update the subscription of a terminal indicated by the second terminal identifier in a timely manner.

[0307] The present application also provides a network-side device. As shown in Figure 13 The network-side device of the present application includes a processor 1101, a transceiver 1102, a memory 1103, a network interface 1104, and a bus interface. Figure 13In particular embodiments, the bus architecture can include any number of interconnecting buses and bridges, depending on the specific application of the processor 1101 and the memory 1103 represented by various circuitry linking the processor 1101 and the memory 1103. The bus architecture can also include various other circuitry to link various circuitry, such as peripheral devices, voltage regulators, and power management circuitry, all of which are well known in the art, and thus, need not be further described herein. The bus interface provides an interface to the transceiver 1102. The transceiver 1102 can be a plurality of elements, including a transmitter and a receiver, that provide means for communicating with various other apparatus over a transmission medium. The processor 1101 is responsible for managing the bus architecture and general processing, and the memory 1103 can store data used by the processor 1101 in executing its operations. In addition, the network side device also includes some functional modules that are not shown here and will not be described here.

[0308] In particular, the network side device further includes instructions or programs stored on the memory 1103 and executable on the processor 1101, and the processor 1101 invokes the instructions or programs in the memory 1103 to perform the method performed by each module shown in the method and achieve the same technical effects. To avoid repetition, the details are not described here. Figure 8 or Figure 9 or Figure 10 or Figure 11 The method performed by each module shown in the method and achieve the same technical effects. To avoid repetition, the details are not described here.

[0309] The application embodiment also provides a readable storage medium, the readable storage medium stores programs or instructions, the programs or instructions are executed by the processor to realize each process of the method embodiment of the method of the above-mentioned subscription update, and can achieve the same technical effects. To avoid repetition, the details are not described here.

[0310] The processor is the processor in the terminal described in the above-mentioned embodiments. The readable storage medium includes a computer readable storage medium, such as a computer readable memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, etc.

[0311] The application embodiment further provides a chip, the chip includes a processor and a communication interface, the communication interface and the processor are coupled, the processor is used for running programs or instructions, realizing each process of the method embodiment of the above-mentioned subscription update method, and can achieve the same technical effects. To avoid repetition, the details are not described here.

[0312] It should be understood that the chip mentioned in the application embodiment can also be called a system chip, a system chip, a chip system or a system on chip, etc.

[0313] It should be noted that, in the present document, the terms "comprises", "comprising", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but can include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element proceeded by "comprises... a" does not, without more constraints, exclude the presence of additional identical elements in the process, method, article, or apparatus that comprises the element. Furthermore, it is to be understood that the method and apparatus of the present application can be carried out by more than one process, method, article, or apparatus either simultaneously, concurrently, or with intervening action that are carried out at the same time, in any order, or in an overlapping manner. For example, the described method can be performed in a different order or simultaneously, and the various steps can be combined or omitted, or additional steps can be added, without departing from the scope of the described method. Also, features described with respect to certain examples can be combined in other examples.

[0314] From the above description of the embodiments, it is apparent that the above-described method can be implemented by software and necessary universal hardware platform, of course, it can also be implemented by hardware, but in many cases, the former is a better implementation. Based on such understanding, the technical solutions of the present application can be embodied in the form of computer software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a plurality of instructions for making a terminal (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) execute the method described in various embodiments of the present application.

[0315] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-described specific embodiments, which are merely illustrative rather than restrictive, and those of ordinary skill in the art can make many forms under the inspiration of the present application without departing from the scope of the present application and the scope protected by the claims.

Claims

1. A method of subscription update, characterized by, The method comprises: receiving, by a unified data network element, a credential success push indication from a server or a network exposure network element; the credential success push indication is used to indicate that a credential corresponding to a target service parameter has been successfully pushed to a target terminal; enabling, by the unified data network element, the target service parameter in a subscription of the target terminal; the credential success push indication comprises a first authentication indication; wherein the first authentication indication comprises at least one of: an indication that secondary authentication is required for the target service parameter, an indication that network slice authentication is required for the target service parameter.

2. The method of claim 1, wherein, The credential success push indication further comprises the target service parameter.

3. The method of claim 2, wherein, The target service parameter comprises at least one of: a data network name (DNN) and a single network slice selection assistance information (S-NSSAI).

4. The method of claim 1, wherein, The method further comprises: receiving, by the unified data network element, a first terminal identifier; wherein the target terminal comprises a terminal indicated by the first terminal identifier.

5. The method of claim 4, wherein, The first terminal identifier comprises at least one of: an IP address of the target terminal, a MAC address of the target terminal, an international mobile subscriber identity (IMSI) of the target terminal, a subscription permanent identifier (SUPI) of the target terminal, a mobile station integrated services digital network number (MSISDN) of the target terminal, and a general public subscription identifier (GPSI) of the target terminal.

6. The method of claim 1, wherein, The credential success push indication further comprises a credential corresponding to the target service parameter.

7. The method of claim 1, wherein, Enabling, by the unified data network element, the target service parameter in the subscription of the target terminal comprises: storing and / or activating, by the unified data network element, the target service parameter in the subscription of the target terminal.

8. The method of claim 2, wherein, The method further comprises: determining, by the unified data network element, a closed access group identifier (CAG) available to the target terminal according to the target service parameter.

9. The method of claim 1, wherein, The method further comprises: activating or storing, by the unified data network element, the CAG in the subscription of the target terminal.

10. The method according to any one of claims 1 to 9, characterized in that, The method further comprises: sending, by the unified data network element, an updated subscription of the target terminal to the target terminal.

11. The method of claim 10, wherein, In a case where the unified data network element is a unified data repository (UDR), the method further comprises: sending, by the UDR, the updated subscription of the target terminal to a unified data management (UDM).

12. The method of claim 10, wherein, The updated subscription comprises at least one of: an enabled DNN, an enabled S-NSSAI, a CAG determined based on the enabled DNN and / or the enabled S-NSSAI.

13. The method of claim 1, wherein, Receiving, by the unified data network element, the credential success push indication comprises: receiving, by the unified data network element, the credential success push indication from a network exposure network element.

14. The method of claim 4, wherein, Receiving, by the unified data network element, the first terminal identifier comprises: receiving, by the unified data network element, the first terminal identifier from a network exposure network element.

15. A method of subscription update, characterized by, The method comprises: sending, by a server, a credential success push indication to a unified data network element; wherein the credential success push indication is used to indicate that a credential corresponding to a target service parameter has been successfully pushed to a target terminal; the credential success push indication comprises a first authentication indication; wherein the first authentication indication comprises at least one of: an indication that secondary authentication is required for the target service parameter, an indication that network slice authentication is required for the target service parameter. an indication that secondary authentication is required for the target service parameter, an indication that network slice authentication is required for the target service parameter.

16. The method of claim 15, wherein, The credential success push indication further includes the target service parameter.

17. The method of claim 16, wherein, The target service parameter includes at least one of a DNN and an S-NSSAI.

18. The method of claim 15, wherein, The method further includes: The server sends a first terminal identifier to the unified data network element; The target terminal includes a terminal indicated by the first terminal identifier.

19. The method of claim 18, wherein, The first terminal identifier includes at least one of an IP address of the target terminal, a MAC address of the target terminal, an IMSI of the target terminal, a SUPI of the target terminal, an MSISDN of the target terminal, and a GPSI of the target terminal.

20. The method of claim 15, wherein, The credential success push indication further includes a credential corresponding to the target service parameter.

21. The method of claim 15, wherein, The server sends a credential success push indication to the unified data network element, including: The server sends a credential success push indication to the network exposure network element.

22. The method of claim 18, wherein, The server sends a first terminal identifier to the unified data network element, including: The server sends the first terminal identifier to the unified data network element through the network exposure network element.

23. A method of subscription update, characterized by, including: The network exposure network element obtains a credential success push indication; The network exposure network element sends the credential success push indication to the unified data network element; The credential success push indication indicates that a credential corresponding to a target service parameter has been successfully pushed to a target terminal. The credential success push indication includes a first authentication indication. The first authentication indication includes at least one of: an indication that secondary authentication is required for the target service parameter, an indication that network slice authentication is required for the target service parameter.

24. The method of claim 23, wherein, The credential success push indication further includes the target service parameter.

25. The method of claim 24, wherein, The target service parameter includes at least one of a DNN and an S-NSSAI.

26. The method of claim 23, wherein, The credential success push indication further includes a credential corresponding to the target service parameter.

27. The method of claim 24, wherein, The method further includes: The network exposure network element obtains a first terminal identifier; The network exposure network element sends the first terminal identifier to the unified data network element.

28. The method of claim 27, wherein, The network exposure network element obtains a first terminal identifier, including: The network exposure network element receives a target address of the target terminal and a credential success push indication, the target address including an IP address of the target terminal or a MAC address of the target terminal; The network exposure network element obtains a second terminal identifier corresponding to the target address.

29. The method of claim 28, wherein, The network exposure network element obtains a second terminal identifier corresponding to the target address, including: The network exposure network element sends a target address of the target terminal to a policy control network element; The network exposure network element receives a second terminal identifier corresponding to the target address from the policy control network element.

30. The method of claim 28, wherein, The first terminal identifier includes at least one of an IP address of the target terminal, a MAC address of the target terminal, an IMSI of the target terminal, a SUPI of the target terminal, an MSISDN of the target terminal, and a GPSI of the target terminal.

31. The method of claim 29 or 30, wherein, The second terminal identifier comprises at least one of: an IMSI of the target terminal, a SUPI of the target terminal, an MSISDN of the target terminal, and a GPSI of the target terminal.

32. An apparatus for subscription update, the apparatus comprising: Comprising: a receiving module configured to receive a credential success push indication from a server or a network exposure network element, the credential success push indication being used to indicate that a credential corresponding to a target service parameter has been successfully pushed to a target terminal; an executing module configured to activate the target service parameter in a subscription of the target terminal; the credential success push indication comprises a first authentication indication; wherein the first authentication indication comprises at least one of: an indication indicating that secondary authentication is required for the target service parameter, an indication indicating that network slice authentication is required for the target service parameter.

33. An apparatus for subscription update, the apparatus comprising: Comprising: a sending module configured to send a credential success push indication to a unified data network element; wherein the credential success push indication is used to indicate that a credential corresponding to a target service parameter has been successfully pushed to a target terminal; the credential success push indication comprises a first authentication indication; wherein the first authentication indication comprises at least one of: an indication indicating that secondary authentication is required for the target service parameter, an indication indicating that network slice authentication is required for the target service parameter.

34. An apparatus for subscription update, the apparatus comprising: Comprising: an executing module configured to obtain a credential success push indication; a sending module configured to send the credential success push indication obtained by the executing module to a unified data network element; wherein the credential success push indication is used to indicate that a credential corresponding to a target service parameter has been successfully pushed to a target terminal; the credential success push indication comprises a first authentication indication; wherein the first authentication indication comprises at least one of: an indication indicating that secondary authentication is required for the target service parameter, an indication indicating that network slice authentication is required for the target service parameter.

35. A unified data network element, characterized by A processor, a memory, and a program or instructions stored in the memory and executable on the processor, the program or instructions being executed by the processor to implement the steps of the method for updating a subscription according to any one of claims 1 to 14.

36. A server, comprising: A processor, a memory, and a program or instructions stored in the memory and executable on the processor, the program or instructions being executed by the processor to implement the steps of the method for updating a subscription according to any one of claims 15 to 22.

37. A network exposure network element, comprising: A processor, a memory, and a program or instructions stored in the memory and executable on the processor, the program or instructions being executed by the processor to implement the steps of the method for updating a subscription according to any one of claims 23 to 31.

38. A readable storage medium characterized by, A readable storage medium stores a program or instructions, the program or instructions being executed by a processor to implement the method for updating a subscription according to any one of claims 1 to 14, or to implement the method for updating a subscription according to any one of claims 15 to 22, or to implement the method for updating a subscription according to any one of claims 23 to 31.

Images