Parameter acquisition method and apparatus, first network function, and second network function

Abstract

The application discloses a parameter acquisition method and device, a first network function and a second network function, and belongs to the technical field of communication. The parameter acquisition method of the application comprises the following steps: a first network function learns configuration parameters of a target service based on a first identifier or a second identifier; the configuration parameters comprise at least one of the following: subscription data of the target service; application data of the target service; network data, session data or service instance data of the target service; gateway information data of the target service; wherein the first identifier is associated with the second identifier, and the first identifier or the second identifier is associated with one or more first communication devices.

Description

Technical Field

[0001] This application belongs to the field of communication technology, specifically relating to a parameter acquisition method, apparatus, first network function, and second network function. Background Technology

[0002] In the Personal Internet of Things (IoT), PIN elements with gateway capabilities (PEGC) take many forms. For example, they can be gateways in smart home scenarios or terminals that interact with wearable devices in wearable device scenarios. The devices behind the gateway can be user equipment (UE), such as smartwatches and mobile phones, or devices that do not have the ability to directly access wireless networks, such as wristbands and headphones.

[0003] In related technologies, 5G networks provide capability openness functions, allowing applications to provide application parameters to the 5G network for storage in the Policy Control Function (PCF) or Unified Data Repository (UDR). The parameters stored in the UDR can notify the PCF to generate corresponding policies.

[0004] In Personal IoT Network (PIN) scenarios, after a user subscribes to a service, the system needs to dynamically configure certain parameters. Therefore, how to dynamically configure parameters for specific applications after a user subscribes to a personal internet service is a problem that urgently needs to be solved by those skilled in the art. Summary of the Invention

[0005] This application provides a parameter acquisition method, apparatus, first network function, and second network function, which can solve the problem of how to dynamically configure parameters for specific applications.

[0006] Firstly, a parameter acquisition method is provided, which includes:

[0007] The first network function obtains the configuration parameters of the target service based on a first identifier or a second identifier; the configuration parameters include at least one of the following:

[0008] The contract data for the target business;

[0009] Application data of the target service;

[0010] The target service's network data, session data, or service instance data;

[0011] The gateway information data of the target service;

[0012] Wherein, the first identifier is associated with the second identifier, and the first identifier or the second identifier is associated with one or more first communication devices.

[0013] Secondly, a parameter acquisition method is provided, which includes:

[0014] The second network function sends configuration parameters for the target service to the first network function based on the first identifier or the second identifier; the configuration parameters include at least one of the following:

[0015] The contract data for the target business;

[0016] Application data of the target service;

[0017] The target service's network data, session data, or service instance data;

[0018] The gateway information data of the target service;

[0019] Wherein, the first identifier is associated with the second identifier, and the first identifier or the second identifier is associated with one or more first communication devices.

[0020] Thirdly, a parameter acquisition device is provided, the device comprising:

[0021] The acquisition module is used to obtain the configuration parameters of the target service based on a first identifier or a second identifier; the configuration parameters include at least one of the following:

[0022] The contract data for the target business;

[0023] Application data of the target service;

[0024] The target service's network data, session data, or service instance data;

[0025] The gateway information data of the target service;

[0026] Wherein, the first identifier is associated with the second identifier, and the first identifier or the second identifier is associated with one or more first communication devices.

[0027] Fourthly, a parameter acquisition device is provided, the device comprising:

[0028] The sending module is configured to send configuration parameters of a target service to a first network function based on a first identifier or a second identifier; the configuration parameters include at least one of the following:

[0029] The contract data for the target business;

[0030] Application data of the target service;

[0031] The target service's network data, session data, or service instance data;

[0032] The gateway information data of the target service;

[0033] Wherein, the first identifier is associated with the second identifier, and the first identifier or the second identifier is associated with one or more first communication devices.

[0034] Fifthly, a first network function is provided, the terminal including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect.

[0035] Sixthly, a first network function is provided, including a processor and a communication interface; wherein the communication interface is used to obtain configuration parameters of a target service based on a first identifier or a second identifier; the configuration parameters include at least one of the following:

[0036] The contract data for the target business;

[0037] Application data of the target service;

[0038] The target service's network data, session data, or service instance data;

[0039] The gateway information data of the target service;

[0040] Wherein, the first identifier is associated with the second identifier, and the first identifier or the second identifier is associated with one or more first communication devices.

[0041] In a seventh aspect, a second network function is provided, the network-side device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the second aspect.

[0042] Eighthly, a second network function is provided, including a processor and a communication interface; wherein the communication interface is used to send configuration parameters of a target service to a first network function based on a first identifier or a second identifier; the configuration parameters include at least one of the following:

[0043] The contract data for the target business;

[0044] Application data of the target service;

[0045] The target service's network data, session data, or service instance data;

[0046] The gateway information data of the target service;

[0047] Wherein, the first identifier is associated with the second identifier, and the first identifier or the second identifier is associated with one or more first communication devices.

[0048] In a ninth aspect, a parameter acquisition system is provided, comprising: a first network function and a second network function, wherein the first network function is available for performing the steps of the method described in the first aspect, and the first network function is available for performing the steps of the method described in the second aspect.

[0049] In a tenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or implement the steps of the method described in the second aspect.

[0050] Eleventhly, a chip is provided, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run programs or instructions to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

[0051] In a twelfth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the steps of the method as described in the first aspect, or to implement the steps of the method as described in the second aspect.

[0052] In this embodiment of the application, the first network function obtains the configuration parameters of the target service of the communication device associated with the first identifier and / or the second identifier based on the first identifier and / or the second identifier associated with the first identifier. Then, the first network function can effectively support the application of the target service based on the obtained configuration parameters of the target service, thereby ensuring the normal operation of the target service subscribed by the user. Attached Figure Description

[0053] Figure 1 This is a schematic diagram of a wireless communication system to which embodiments of this application can be applied;

[0054] Figure 2 This is one of the flowcharts illustrating the parameter acquisition method provided in the embodiments of this application;

[0055] Figure 3 This is a schematic diagram of the interaction flow of the parameter acquisition method provided in the embodiments of this application;

[0056] Figure 4 This is a second flowchart illustrating the parameter acquisition method provided in the embodiments of this application;

[0057] Figure 5This is one of the structural schematic diagrams of the parameter acquisition device provided in the embodiments of this application;

[0058] Figure 6 This is a second schematic diagram of the parameter acquisition device provided in the embodiments of this application;

[0059] Figure 7 This is a schematic diagram of the structure of the communication device provided in the embodiments of this application;

[0060] Figure 8 This is a schematic diagram of the network-side device provided in the embodiments of this application. Detailed Implementation

[0061] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0062] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0063] It is worth noting that the technologies described in this application are 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 this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description; however, these technologies can also be applied to communication systems other than NR system applications, such as 6th generation (6G) radio communication systems. th Generation 6G communication system.

[0064] Personal IoT Network (PIN):

[0065] A PIN is a group consisting of at least one PIN element (PINE), where at least one PIN element is a terminal (User Equipment, UE). PIN elements communicate with each other. Two PIN elements can communicate through a direct connection between them or indirectly through a communication network.

[0066] A PIN element can be a 3GPP device (e.g., UE) or a non-3GPP device. A non-3GPP device refers to a device that does not use 3GPP-defined credentials, does not support 3GPP-defined NAS protocols, or does not support 3GPP access technologies (such as 3G / 4G / 5G air interface technologies) but only supports non-3GPP access technologies (such as WiFi, fixed network, Bluetooth, etc.).

[0067] A PIN can contain one or more PIN Elements With Gateway Capability (PEGCs). These PIN elements can communicate directly with each other or via PEGCs. PEGCs can also facilitate communication between these PIN elements and other devices or application servers outside the PIN. The PEGC device can be of various types; for example, it could be a gateway in a smart home scenario or a mobile phone acting as a gateway for wearable devices.

[0068] Figure 1 This is a schematic diagram of a wireless communication system to which the embodiments of this application can be applied. Figure 1 The wireless communication system shown includes a terminal 11 and a network-side device 12. The terminal 11 can be a mobile phone, tablet computer, laptop computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, vehicle-mounted device (VUE), pedestrian terminal (PUE), smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. It should be noted that the specific type of terminal 11 is not limited in the embodiments of this application.

[0069] Network-side equipment 12 may include access network equipment or core network equipment. Access network equipment may also be referred to as radio access network equipment, radio access network (RAN), radio access network function, or radio access network unit. Access network equipment may include base stations, WLAN access points, or WiFi nodes, etc. Base stations may be referred to as Node B, evolved Node B (eNB), access point, base transceiver station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), home B node, home evolved B node, Transmitting Receiving Point (TRP), or any other suitable term in the field, as long as the same technical effect is achieved. The base station is not limited to specific technical terms. It should be noted that in this embodiment, only a base station in an NR system is used as an example for description, and the specific type of base station is not limited.Core network equipment may include, but is not limited to, at least one of the following: core network node, core network function, Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), and Binding Support. Functions include BSF, Application Function (AF), Location Management Function (LMF), Enhanced Serving Mobile Location Centre (E-SMLC), and Network Data Analytics Function (NWDAF). It should be noted that this application embodiment only uses core network equipment in the NR system as an example for description, and does not limit the specific type of core network equipment.

[0070] The parameter acquisition method provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0071] Figure 2 This is one of the flowcharts illustrating the parameter acquisition method provided in the embodiments of this application, such as... Figure 2 As shown, the method includes:

[0072] Step 201: The first network function obtains the configuration parameters of the target service based on the first identifier or the second identifier; the configuration parameters include at least one of the following:

[0073] Contract data based on target business;

[0074] Application data based on target business;

[0075] Network data, session data, or service instance data based on the target service;

[0076] Gateway information data based on the target service;

[0077] The first identifier is associated with the second identifier, and the first identifier or the second identifier is associated with one or more first communication devices.

[0078] Specifically, after a user subscribes to a target service, the first network function can obtain the configuration parameters of the target service based on a first identifier or a second identifier. This allows the first network function to effectively support the application of the target service based on the obtained configuration parameters, ensuring the normal operation of the user's subscribed target service. Optionally, the target service can be a PIN service, and the first network function can be a PCF and / or NEF. Optionally, the first identifier is associated with the second identifier, and the first identifier or the second identifier is associated with one or more first communication devices. This allows the first network function to accurately obtain the configuration parameters of the target service corresponding to the communication device associated with the first identifier and / or the second identifier based on the association relationship between the first identifier and / or the second identifier and the first communication device. The communication device can be a PEGC and PIN management terminal (PEMC) in an IoT service scenario, and the configuration parameters include at least one of the following: subscription data, application data, network data, gateway information data, session data, or service instance data.

[0079] For example, the first network function sends a first identifier to the second network function UDR. After receiving the first identifier sent by the first network function, the second network function sends PIN application data to the first network function based on the first identifier. The first network function then obtains the PIN application data from the second network function UDR.

[0080] Optionally, the first identifier can be an internal PIN subscription identifier, used between various functions within the 5G system to associate PIN service parameters. The first network function can use the first identifier to obtain PIN service parameters from the second network function UDR, such as one of the user permanent identifiers (SUbs subscription permanent identifiers, SUPIs) among users represented by various Generic Public Subscription Identifiers (GPSIs). The second identifier is an external PIN subscription identifier, used outside the 5G system to hide the internal PIN subscription identifier, such as one of various GPSIs. When hiding the internal PIN subscription identifier is not required, the external PIN subscription identifier is not needed. Optionally, the first network function can use the first and second identifiers separately within and outside the 5G system to improve communication security; alternatively, it can use either the first or second identifier both within and outside the 5G system to improve efficiency.

[0081] Optionally, the first identifier includes at least one of the following: SUPI; PDU session information; network identifier, session identifier, or service instance identifier of the target service; and identifier of the first communication device.

[0082] Optionally, the second identifier includes at least one of the following: the identifier of the first communication device; GPSI.

[0083] The parameter acquisition method provided in this application embodiment obtains the configuration parameters of the target service of the communication device associated with the first identifier and / or the second identifier based on the first identifier and / or the second identifier associated with the first identifier through the first network function. This enables the first network function to obtain the configuration parameters of the target service. Based on the obtained configuration parameters of the target service, the first network function can effectively support the application of the target service and ensure the normal operation of the target service subscribed by the user.

[0084] In one embodiment, the contract data may include at least one of the following:

[0085] a) The first identifier is used to associate contract data;

[0086] b) A second identifier associated with the first identifier, used to associate contract data;

[0087] c) Protocol Data Unit (PDU) session information, used to indicate the PDU session, which is used to transmit control messages for the target service;

[0088] d) Number of networks, sessions, or service instances of the target service, used to indicate the number of networks, sessions, or service instances of the target service that are allowed;

[0089] e) First instruction information, used to indicate network functions that are permitted to request control of target services from the target network.

[0090] The first identifier and its associated second identifier are used to associate subscription data. For example, when the fifth network function is AF (Automatic Function), the fifth network function associates the first identifier and / or the second identifier with the subscription data. Based on this association, the subscription data can be accurately obtained, ensuring the normal operation of the user's subscribed target service. Optionally, the first indication information can be used to indicate network functions that are allowed to request control of the target service from the 5G network. Optionally, the number of networks for the target service is used to indicate the number of networks that are allowed to be created; the first indication information is used to indicate application functions that are allowed to send configuration parameters of the relevant PIN service to the 5G network.

[0091] In one embodiment, the application data includes at least one of the following:

[0092] a) The first identifier is used to associate application data, or contract data associated with application data;

[0093] b) A second identifier associated with the first identifier, used to associate application data, or contract data associated with the application data;

[0094] c) The network identifier, session identifier, or service instance identifier of the target service;

[0095] d) PDU session information, used to indicate the PDU session, which is used for the network, session or service instance of the target service;

[0096] e) The number of networks, sessions, or service instances of the target service, used to indicate the number of existing or created networks, sessions, or service instances of the target service;

[0097] f) Subnet address, used to indicate the subnet address information of the target service;

[0098] g) Subnet mask, used to indicate the subnet mask information of the target service.

[0099] Specifically, the first identifier and the second identifier associated with the first identifier are used to associate application data or contract data associated with the application data. For example, when the fifth network function is AF, the fifth network function associates the first identifier and / or the second identifier with the application data. Based on the association relationship between the first identifier and / or the second identifier and the application data, the application data can be accurately obtained, ensuring the normal operation of the target business subscribed by the user.

[0100] In one embodiment, network data, session data, or service instance data includes at least one of the following:

[0101] 1) The first identifier is used to associate network data, session data, or service instance data;

[0102] 2) The second identifier associated with the first identifier is used to associate network data, session data, or service instance data;

[0103] 3) The network identifier, session identifier, or service instance identifier of the target service;

[0104] 4) PDU session information, used to indicate the PDU session, which is used for the network, session or service instance of the target service;

[0105] 5) Allowed Quality of Service (QoS) information, used to indicate the QoS information allowed by the target network for data in a network, session, or service instance;

[0106] 6) Second indication information, used to indicate at least one of the PDU session, network, session and service instance, whether to transmit or not transmit control messages of the target service, or to transmit only or not only data packets of the target service;

[0107] 7) The default maximum number of devices that the first communication device can connect to is used to determine the address range or address range size sent to the first communication device.

[0108] The first identifier and the second identifier associated with it are used to associate network data, session data, or service instance data. For example, when the fifth network function is AF (Automatic Function), the fifth network function associates the first identifier and / or the second identifier with network data, session data, or service instance data. Based on this association, the network data, session data, or service instance data can be accurately obtained, ensuring the normal operation of the user's subscribed target service. Optionally, the allowed QoS information is used to indicate the QoS information that the 5G network is allowed to support for the corresponding network data, such as allowed data transmission delay budget and data transmission bandwidth. Optionally, the maximum number of devices that the first communication device can connect to is used to indicate the range of IP addresses that the 5G network determines for the PEGC (Power, Access, and Control) of the communication device. The PEGC allocates IP addresses to connected devices based on the range of IP addresses.

[0109] In one embodiment, the gateway information data includes at least one of the following:

[0110] a) The first identifier is used to associate gateway information data;

[0111] b) A second identifier associated with the first identifier, used to associate gateway information data;

[0112] c) Identification of the first communication device;

[0113] d) The maximum number of devices that the first communication device can connect to, used to determine the address range or address range size to be sent to the first communication device;

[0114] e) QoS information of the first communication device, used to indicate the QoS information of the first communication device for non-3GPP access;

[0115] f) Identification information, used to identify control messages of the target service sent to the first communication device, or control messages of the target service sent by the first communication device.

[0116] The first identifier and the second identifier associated with the first identifier are used to associate gateway information data. For example, when the third network function is SMF, the third network function associates the first identifier and / or the second identifier with the gateway information data. Based on the association relationship between the first identifier and / or the second identifier and the gateway information data, the gateway information data can be accurately obtained, ensuring the normal operation of the target service subscribed by the user.

[0117] In one embodiment, the first network function learns the configuration parameters of the target service based on the first identifier, including:

[0118] The first network function obtains the configuration parameters of the target service from the second network function based on the first identifier.

[0119] Specifically, the first network function can be PCF, the second network function can be UDR, and the first identifier includes at least one of the following: SUPI, PDU session information, network identifier of the target service, session identifier or service instance identifier, and identifier of the first communication device; that is, the first network function can accurately obtain the required configuration parameters of the target service from the second network function based on the first identifier, and then support the application of the target service based on the obtained configuration parameters of the target service, effectively ensuring the normal operation of the target service subscribed by the user.

[0120] For example, a first network function obtains PIN application data from a second network function UDR based on an internal PIN signature identifier, wherein the PIN application data is associated with the aforementioned internal PIN signature identifier. Optionally, the first network function sends the internal PIN signature identifier to the second network function UDR. After receiving the internal PIN signature identifier sent by the first network function, the second network function UDR sends the PIN application data to the first network function based on the internal PIN signature identifier, thereby allowing the first network to obtain the PIN application data from the second network function.

[0121] In one embodiment, the first network function obtains configuration parameters of the target service from the second network function based on the first identifier, including:

[0122] The first network function calls a subscription operation to the second network function; the parameters of the subscription operation include a first identifier;

[0123] The first network function receives the event identifier of the subscription operation sent by the second network function;

[0124] A first network function is associated with an event identifier and a first identifier, or with an event identifier and one or more first communication devices associated with the first identifier;

[0125] The first network function receives the event identifier and the configuration parameters of the target service sent by the second network function.

[0126] Specifically, the first network function can invoke a subscription operation including a first identifier to the second network function. The second network function receives the subscription request carrying the first identifier sent by the first network function and sends an event identifier to the first network function. After receiving the event identifier of the subscription operation sent by the second network function, the first network function associates the event identifier with the first identifier, or associates the event identifier with one or more first communication devices associated with the first identifier. Thus, the first network function can accurately and effectively obtain the configuration parameters of the target service based on the event identifier sent by the second network function.

[0127] For example, a first network function subscribes to events related to an internal PIN subscription identifier from a second network function UDR. These events are used by the second network function UDR to notify the first network function when the PIN application data associated with the internal PIN subscription identifier changes. For instance, when the PIN application data changes, the second network function sends the updated PIN application data and the event identifier to the first network function. Optionally, the subscription is also associated with a user terminal identifier; that is, the first network function receives the event identifier sent by the second network function UDR and associates the event identifier with the terminal identifier.

[0128] In the method described in the above embodiments, the first network function receives an event identifier of a subscription operation sent by the second network function and associates the event identifier with a first identifier, or associates the event identifier with one or more first communication devices associated with the first identifier, thereby enabling the first network function to accurately and effectively obtain the configuration parameters of the target service based on the event identifier sent by the second network function.

[0129] In one embodiment, the first network function obtains configuration parameters of the target service from the second network function based on the first identifier, including:

[0130] The first network function invokes a subscription operation from the first communication device to the second network function; the parameters of the subscription operation include a first identifier;

[0131] The first network function receives the event identifier of the subscription operation sent by the second network function;

[0132] The first network function is associated with the event identifier and the first communication device;

[0133] The first network function receives the event identifier and the configuration parameters of the target service sent by the second network function.

[0134] Specifically, the first network function can invoke a subscription operation including a first identifier to the second network function. The second network function sends an event identifier of the subscription operation to the first network function based on the subscription operation including the first identifier. After receiving the event identifier of the subscription operation sent by the second network function, the first network function associates the event identifier with the first communication device. Thus, the first network function can accurately and effectively obtain the configuration parameters of the target service based on the event identifier sent by the second network function.

[0135] For example, taking the first network function as PCF as an example, the first network function subscribes to the second network function UDR based on the PIN subscription identifier of the communication device PEMC as the SUPI of the communication device PEMC. If the first network function is the SUPI of the PEMC to send the PIN subscription identifier to the second network function UDR, and the second network function UDR returns the event identifier, the first network function can accurately and effectively obtain the configuration parameters of the target service by associating the event identifier with the SUPI.

[0136] In the method described in the above embodiments, the first network function receives an event identifier of a subscription operation sent by the second network function and associates the event identifier with the first communication device, thereby enabling the first network function to accurately and effectively obtain the configuration parameters of the target service based on the event identifier sent by the second network function.

[0137] In one embodiment, when the configuration parameters include application data, the method further includes:

[0138] The first network function sends a user routing policy (URSP) to the first communication device based on application data.

[0139] Specifically, taking PCF as the first network function as an example, UDR (User Dedicated Receiver) sends PIN application data to the first network function. The PIN application data is used by the first network function to generate URSP (Uniform Network Service Request). The URSP is sent to the terminal so that the terminal can establish a PDU session based on the URSP. The PDU session is used to support the transmission of data and signaling for related PIN services, such as Data Network Name (DNN) and Single Network Slice Selection Assist Information (S-NSSAI). After obtaining personal IoT application data from UDR based on a first identifier, the first network function generates URSP based on the obtained application data and sends the URSP to the first communication device to support IoT service applications. This allows the first communication device to perform IoT services normally based on the received URSP. Optionally, the PIN application data includes at least one of the following: the network identifier of the target service, and a mapping between the network identifier of the target service and PDU session information.

[0140] For example, based on subscription, the second network function UDR will send corresponding data and event identifiers to the first network function PCF when the PIN application data and / or PIN authorization data corresponding to the PIN subscription identifier changes. The first network function PCF will then generate URSP for the corresponding SUPI based on the received data and event identifiers.

[0141] In one embodiment, the parameter acquisition method further includes at least one of the following:

[0142] The first network function sends network data, session data, or service instance data to the third network function.

[0143] The first network function determines whether the QoS requested by the first communication device is met or not, based on the allowed QoS information included in network data, session data, or service instance data.

[0144] The first network function sends IP address range information to the third network function based on the default maximum number of devices that the first communication device can connect to, which is included in network data, session data, or business instance data.

[0145] Specifically, after the first network function obtains the configuration parameters of the target service based on the first identifier or the second identifier, it can send network data, session data, or service instance data to the third network function. Optionally, the third network function can be an SMF. Optionally, the first network function can also send IP address range information to the third network function SMF based on the default maximum number of devices that the first communication device can connect to, which is included in the network data, session data, or service instance data. This allows the third network function SMF to allocate a range of IP addresses to the first communication device based on the maximum number of devices that each first communication device can connect to and send it to the first communication device.

[0146] For example, the first network function obtains the maximum number of devices that each communication device's PEGC can connect to from the second network function UDR, and generates an IP address range based on the maximum number information and sends it to the third network function SMF. Optionally, the first network function sends PDU session information or network identifier to the second network function. After receiving the PDU session information or network identifier sent by the first network function, the second network function UDR can send the maximum number of devices that each communication device's PEGC can connect to to the first network function based on the PDU session information or network identifier. Thus, the first network function can obtain the maximum number of devices that each communication device's PEGC can connect to from the second network function UDR. Optionally, the PDU session information includes at least one of the following: Data Network Name (DNN), Single Network Slice Selection Auxiliary Information (S-NSSAI), PDU Session Identifier (ID), and the identifier of the user terminal to which the PDU session belongs.

[0147] In one embodiment, the parameter acquisition method further includes at least one of the following:

[0148] The first network function sends gateway information data to the third network function;

[0149] The first network function sends IP address range information to the third network function based on the maximum number of devices that the first communication device can connect to, as included in the gateway information data.

[0150] Specifically, after the first network function obtains the configuration parameters of the target service based on the first identifier or the second identifier, the first network function can send the gateway information data in the obtained configuration parameters to the third network; the first network function can also send IP address range information to the third network function based on the maximum number of devices that the first communication device can connect to, which is included in the obtained network information data, so that the third network function SMF can send the obtained IP address range to the first communication device.

[0151] For example, taking the first network function as PCF as an example, the second network function UDR sends the maximum number of devices that each communication device can connect to via PEGC to the first network function. This information is used by the first network function to send the maximum number of devices that each communication device can connect to via PEGC to the third network function SMF, or by the first network function generating an IP address range based on the maximum number of devices that each communication device can connect to via PEGC and sending it to the SMF. In other words, after the first network function learns the maximum number of devices that each communication device can connect to via PEGC from the second network function UDR, it sends the maximum number information to the third network function SMF or generates an IP address range based on the maximum number information and sends it to the third network function.

[0152] In one embodiment, before the first network function learns the configuration parameters of the target service based on the first identifier or the second identifier, the method further includes:

[0153] The first network function receives service parameters for either the first identifier or the second identifier.

[0154] Optionally, taking NEF as an example, before the first network function learns the configuration parameters of the target service based on the first identifier or the second identifier, the first network function receives service parameters for the first identifier or the second identifier. Optionally, the service parameters include at least one of the following:

[0155] 1) The network identifier, session identifier, or service instance identifier of the target service;

[0156] 2) PDU session information;

[0157] 3) Business operation information, including any one of the following: creation operation, addition operation, release operation, deletion operation, and update operation;

[0158] 4) Identification of the first communication device;

[0159] 5) The maximum number of devices that the first communication device can connect to;

[0160] 6) QoS information of the first communication device, used to indicate the QoS information of the first communication device for non-3GPP access;

[0161] 7) Identification information, used to identify the control message of the target service sent to the first communication device, or the control message of the target service sent by the first communication device.

[0162] For example, taking the first network function as NEF, the first network function receives the PIN service parameters sent by AF, and sends PIN application data and / or the maximum number of devices that each communication device can connect to via PEGC to the second network device UDR based on the PIN service parameters. Optionally, the PIN application data includes at least one of the following: the network identifier of the target service, and a mapping between the network identifier of the target service and PDU session information.

[0163] In one embodiment, after the first network function obtains the configuration parameters of the target service based on the first identifier or the second identifier, the method further includes at least one of the following:

[0164] The first network function sends service parameters to the second network function based on the contract data;

[0165] The first network function sends service parameters to the second network function based on application data.

[0166] Optionally, taking NEF as an example, after the first network function learns the configuration parameters of the target service based on the first identifier or the second identifier, the first network function can send service parameters to the second network function UDR based on the subscription data in the configuration parameters; the first network function can also send service parameters to the second network function UDR based on the application data in the configuration parameters.

[0167] For example, when creating / adding a network, the first network function updates the PIN application data and PIN authorization data to the second network function UDR based on the PIN signing data.

[0168] In one embodiment, after the first network function obtains the configuration parameters of the target service based on the first identifier or the second identifier, the method further includes at least one of the following:

[0169] The first network function determines the service parameters to be sent to the second network function based on the contract data.

[0170] The first network function determines the service parameters to be sent to the second network function based on application data.

[0171] For example, taking the first network function as NEF as an example, the first network function obtains the corresponding PIN subscription data from the second network function UDR based on the external / internal PIN subscription identifier. Based on the subscription AF information in the PIN subscription data, it determines whether the AF can send service parameters to the second network function. If the determination is no, it stops sending service parameters to the second network function.

[0172] When creating / adding a network, the first network function determines whether the number of networks exceeds the limit based on the PIN subscription data. If the limit is exceeded, it stops sending service parameters to the second network function UDR. If the limit is not exceeded, the first network function updates the PIN application data and PIN authorization data to the second network function UDR based on the PIN subscription data.

[0173] In one embodiment, the first network function sends service parameters to the second network function based on subscription data, including at least one of the following:

[0174] When the service parameters indicate the network, session or service instance for creating the target service, the first network function sends the service parameters to the second network function based on the number of networks, sessions or service instances of the target service included in the subscription data.

[0175] The first network function sends service parameters to the second network function based on the first instruction information included in the contract data.

[0176] Specifically, taking NEF as the first network function, when the service parameters indicate the network, session, or service instance for creating the target service, the first network function can send service parameters to the second network function based on the number of networks, sessions, or service instances of the target service included in the subscription data; and / or, the first network function can send service parameters to the second network function based on the first indication information included in the subscription data; wherein, the first indication information is used to indicate the network function that is allowed to request control of the target service from the target network.

[0177] In one embodiment, the first network function sends service parameters to the second network function based on application data, including:

[0178] When the service parameters indicate the network, session, or service instance for creating the target service, the first network function sends the service parameters to the second network function based on the number of application data records.

[0179] Specifically, taking NEF as the first network function, when the service parameters indicate the network, session, or service instance for creating the target service, the first network function can send service parameters to the second network function based on the existing number of networks.

[0180] In one embodiment, the first network function sends PDU session information from application data and PDU session information from network data, session data, or service instance data to the second network function based on service parameters.

[0181] Optionally, the PDU session information includes at least one of the following:

[0182] Data network name: DNN;

[0183] Single network slice selection auxiliary information S-NSSAI;

[0184] PDU Session Identifier ID;

[0185] The identifier of the user terminal to which the PDU session belongs.

[0186] Figure 3 This is a schematic diagram of the interaction flow of the parameter acquisition method provided in this embodiment. The parameter acquisition method provided in this embodiment includes:

[0187] Step 301: The user signs up for a PIN service with the operator, which includes one or more GPSIs and may also include one or more predefined networks.

[0188] According to the agreement, the operator will pre-configure the following information in the PCF for the terminal users represented by each GPSI:

[0189] a) User Routing Policy (URSP) associated with a predefined network;

[0190] b) Internal PIN signing identifier.

[0191] According to the agreement, the operator pre-configures PIN subscription data in the UDR:

[0192] a) External PIN authentication identifier;

[0193] b) Internal PIN signing identifier;

[0194] c) PDU session information;

[0195] d) The number of networks for the target service, i.e., the number of networks under contract, is used to indicate the number of networks that are allowed to be created;

[0196] e) The first instruction information, namely the signed AF information, is used to indicate the network functions that are permitted to request control of the target services from the target network.

[0197] UDR can store the following PIN application data:

[0198] a) Internal PIN signing identifier;

[0199] b) PDU session information;

[0200] UDR can also store the following PIN authorization data:

[0201] a) PDU session information;

[0202] b) Permitted QoS information;

[0203] c) The default maximum number of devices that the first communication device can connect to, i.e., the maximum number of devices that each PIN gateway PEGC can connect to.

[0204] Step 302: The PEMC registers with the 5G system. During the registration process, the PCF subscribes to events from the UDR for the PEMC's SUPI based on the PEMC's PIN subscription identifier. For example, the PCF sends the PIN subscription identifier to the UDR for the PEMC's SUPI, and the UDR returns an event identifier. The PCF associates the event identifier with the SUPI. Based on the subscription, when the PIN application data and / or PIN authorization data corresponding to the PIN subscription identifier changes, the UDR will send the corresponding data and event identifier to the PCF. Based on the received data and event identifier, the PCF generates a URSP for the corresponding SUPI.

[0205] Step 303: The user's PIN gateway PEGC performs the same process as in step 302.

[0206] Step 304: Upon receiving a request from PEMC or PEGC, AF sends PIN management parameters to NEF, including the following information:

[0207] a) External / internal PIN signature;

[0208] b) PDU session information;

[0209] c) Business operation information, including creating / adding networks, releasing / deleting networks, and updating networks;

[0210] d) Permitted QoS information;

[0211] e) The maximum number of devices that can be connected to each PEGC; optionally, this can only be carried when creating / adding a network;

[0212] The NEF obtains the corresponding PIN signing data from the UDR based on the external / internal PIN signing identifier. Based on the signing AF information in the PIN signing data, it determines whether the AF can perform the above operations. If the determination is no, the process stops.

[0213] For creating / adding networks, the NEF determines whether the number of networks exceeds the limit based on the PIN subscription data; if so, the process stops. The NEF updates the PIN application data and PIN authorization data to the UDR based on this data. Based on the subscription, the UDR sends update information to the PCF, which updates the URSP and sends it to the corresponding terminal. The PCF obtains the PIN authorization data from the UDR based on the network ID and sends it to the SMF, or determines whether the QoS requested by the PEGC / PEMC is acceptable based on the PIN authorization data. The SMF allocates an IP range for the PEGC based on the maximum number of devices that each PIN gateway can connect to and sends it to the PEGC.

[0214] Through the above-mentioned configuration and process, when a user requests the AF to create or delete a PIN network through the PEMC, the URSP will be updated, and the PCF will send the updated URSP to each PEGC and PEMC that make up the network, thereby enabling these PEMC / PEGC to establish or release the corresponding PDU sessions to support the PIN network.

[0215] Figure 4 This is a second flowchart illustrating the parameter acquisition method provided in the embodiments of this application. For example... Figure 4 As shown, the method provided in this embodiment includes:

[0216] Step 401: The second network function sends the configuration parameters of the target service to the first network function based on the first identifier or the second identifier; the configuration parameters include at least one of the following:

[0217] Contract data for the target business;

[0218] Application data for the target business;

[0219] Network data, session data, or service instance data of the target service;

[0220] Gateway information data for the target service;

[0221] The first identifier is associated with the second identifier, and the first identifier or the second identifier is associated with one or more first communication devices.

[0222] Optionally, the contract data includes at least one of the following:

[0223] The first identifier is used to associate contract data;

[0224] A second identifier associated with the first identifier is used to associate contract data;

[0225] Protocol Data Unit (PDU) session information is used to indicate a PDU session, which is used to transmit control messages for the target service.

[0226] The number of networks, sessions, or service instances for the target service indicates the number of networks, sessions, or service instances for the target service that are allowed to be created.

[0227] The first instruction information is used to indicate network functions that are permitted to request control of the target services from the target network.

[0228] Optionally, the application data includes at least one of the following:

[0229] The first identifier is used to associate application data, or contract data associated with application data;

[0230] The second identifier associated with the first identifier is used to associate application data, or contract data associated with the application data;

[0231] The network identifier, session identifier, or service instance identifier of the target service;

[0232] PDU session information is used to indicate a PDU session, which is a network, session, or service instance used to carry the target service.

[0233] The number of networks, sessions, or service instances of the target service is used to indicate the number of existing or created networks, sessions, or service instances of the target service.

[0234] Subnet address, used to indicate the subnet address information of the target service;

[0235] Subnet mask, used to indicate the subnet mask information of the target service.

[0236] Optionally, network data, session data, or service instance data include at least one of the following:

[0237] The first identifier is used to associate network data, session data, or business instance data;

[0238] The second identifier associated with the first identifier is used to associate network data, session data, or service instance data;

[0239] The network identifier, session identifier, or service instance identifier of the target service;

[0240] PDU session information is used to indicate a PDU session, which is a network, session, or service instance used to carry the target service.

[0241] Allowed QoS information is used to indicate the QoS information that the target network is allowed to support for data in the network, session, or service instance;

[0242] The second instruction information is used to instruct at least one of the PDU session, network, session and service instance to transmit or not transmit control messages of the target service, or to transmit or not transmit data packets of the target service.

[0243] The default maximum number of devices that the first communication device can connect to is used to determine the address range or address range size sent to the first communication device.

[0244] Optionally, the gateway information data includes at least one of the following:

[0245] The first identifier is used to associate gateway information data;

[0246] The second identifier, associated with the first identifier, is used to associate gateway information data;

[0247] The identifier of the first communication device;

[0248] The maximum number of devices that the first communication device can connect to is used to determine the address range or address range size sent to the first communication device.

[0249] The QoS information of the first communication device is used to indicate the QoS information of the first communication device for non-3GPP access.

[0250] Identification information is used to identify control messages of a target service sent to the first communication device, or control messages of a target service sent by the first communication device.

[0251] Optionally, the first identifier includes at least one of the following: a permanent identifier for the subscribed user (SUPI); PDU session information; a network identifier, session identifier, or service instance identifier for the target service; and an identifier for the first communication device.

[0252] The second identifier includes at least one of the following: the identifier of the first communication device; or the General Public User Identifier (GPSI).

[0253] Optionally, the second network function sends configuration parameters of the target service to the first network function based on the first identifier or the second identifier, including:

[0254] The second network function receives the subscription operation called by the first network function; the parameters of the subscription operation include the first identifier;

[0255] The second network function sends an event identifier for the subscription operation to the first network function;

[0256] When the configuration parameters of the target service change, the second network function sends an event identifier and the configuration parameters of the target service to the first network function.

[0257] Optionally, the parameter acquisition method also includes:

[0258] The second network function receives service parameters sent by the first network function.

[0259] Optionally, the parameter acquisition method also includes:

[0260] The second network function receives PDU session information from application data sent by the first network function, as well as PDU session information from network data, session data, or service instance data.

[0261] Optionally, the business parameters include at least one of the following:

[0262] The network identifier, session identifier, or service instance identifier of the target service;

[0263] PDU session information;

[0264] Business operation information, including any one of the following: create operation, add operation, release operation, delete operation, and update operation;

[0265] The identifier of the first communication device;

[0266] The maximum number of devices that the first communication device can connect to;

[0267] The QoS information of the first communication device is used to indicate the QoS information of the first communication device for non-3GPP access.

[0268] Identification information is used to identify control messages of the target service sent to the first communication device, or control messages of the target service sent by the first communication device.

[0269] Optionally, the PDU session information includes at least one of the following:

[0270] Data network name: DNN;

[0271] Single network slice selection auxiliary information S-NSSAI;

[0272] PDU Session Identifier ID;

[0273] The identifier of the user terminal to which the PDU session belongs.

[0274] The parameter acquisition method provided in this application can be executed by a virtual device. This application uses the example of a virtual device executing the parameter acquisition method to illustrate the parameter acquisition device provided in this application.

[0275] Figure 5 This is one of the structural schematic diagrams of the parameter acquisition device provided in the embodiments of this application, such as... Figure 5 As shown, the parameter acquisition device includes:

[0276] The acquisition module 501 is used to obtain the configuration parameters of the target service based on the first identifier or the second identifier; the configuration parameters include at least one of the following:

[0277] Contract data for the target business;

[0278] Application data for the target business;

[0279] Network data, session data, or service instance data of the target service;

[0280] Gateway information data for the target service;

[0281] The first identifier is associated with the second identifier, and the first identifier or the second identifier is associated with one or more first communication devices.

[0282] Optionally, the contract data includes at least one of the following:

[0283] The first identifier is used to associate contract data;

[0284] A second identifier associated with the first identifier is used to associate contract data;

[0285] Protocol Data Unit (PDU) session information is used to indicate a PDU session, which is used to transmit control messages for the target service.

[0286] The number of networks, sessions, or service instances of the target service is used to indicate the number of networks, sessions, or service instances allowed for the target service.

[0287] The first instruction information is used to indicate network functions that are permitted to request control of the target services from the target network.

[0288] Optionally, the application data includes at least one of the following:

[0289] The first identifier is used to associate application data, or contract data associated with application data;

[0290] The second identifier associated with the first identifier is used to associate application data, or contract data associated with the application data;

[0291] The network identifier, session identifier, or service instance identifier of the target service;

[0292] PDU session information is used to indicate a PDU session, which is used for the network, session, or service instance of the target service.

[0293] The number of networks, sessions, or service instances of the target service is used to indicate the number of existing or created networks, sessions, or service instances of the target service.

[0294] Subnet address, used to indicate the subnet address information of the target service;

[0295] Subnet mask, used to indicate the subnet mask information of the target service.

[0296] Optionally, network data, session data, or service instance data include at least one of the following:

[0297] The first identifier is used to associate network data, session data, or business instance data;

[0298] The second identifier associated with the first identifier is used to associate network data, session data, or service instance data;

[0299] The network identifier, session identifier, or service instance identifier of the target service;

[0300] PDU session information is used to indicate a PDU session, which is used for the network, session, or service instance of the target service.

[0301] Allowed QoS information, used to indicate the QoS information allowed by the target network for data in a network, session, or service instance;

[0302] The second instruction information is used to instruct at least one of the PDU session, network, session and service instance to transmit or not transmit control messages of the target service, or to transmit or not transmit data packets of the target service.

[0303] The default maximum number of devices that the first communication device can connect to is used to determine the address range or address range size sent to the first communication device.

[0304] Optionally, the gateway information data includes at least one of the following:

[0305] The first identifier is used to associate gateway information data;

[0306] The second identifier, associated with the first identifier, is used to associate gateway information data;

[0307] The identifier of the first communication device;

[0308] The maximum number of devices that the first communication device can connect to is used to determine the address range or address range size sent to the first communication device.

[0309] The QoS information of the first communication device is used to indicate the QoS information of the first communication device for non-3GPP access.

[0310] Identification information is used to identify control messages of a target service sent to the first communication device, or control messages of a target service sent by the first communication device.

[0311] Optionally, the first identifier includes at least one of the following: a permanent identifier for the subscribed user (SUPI); PDU session information; a network identifier, session identifier, or service instance identifier for the target service; and an identifier for the first communication device.

[0312] The second identifier includes at least one of the following: the identifier of the first communication device; or the General Public User Identifier (GPSI).

[0313] Optionally, the acquisition module 501 is used to obtain the configuration parameters of the target service from the second network function based on the first identifier.

[0314] Optionally, the acquisition module 501 is used to invoke a subscription operation to the second network function; the parameters of the subscription operation include a first identifier;

[0315] Receive the event identifier of the subscription operation sent by the second network function;

[0316] Associated event identifier and first identifier, or associated event identifier and one or more first communication devices associated with the first identifier;

[0317] Receive the event identifier and the configuration parameters of the target service sent by the second network function.

[0318] Optionally, the acquisition module 501 is used to call a subscription operation from the first communication device to the second network function; the parameters of the subscription operation include a first identifier;

[0319] Receive the event identifier of the subscription operation sent by the second network function;

[0320] Associate the event identifier and the first communication device;

[0321] Receive the event identifier and the configuration parameters of the target service sent by the second network function.

[0322] Optionally, the acquisition module 501 is also used to send the User Equipment Routing Policy (URSP) to the first communication device based on the application data.

[0323] Optionally, the acquisition module 501 is also used to send network data, session data or service instance data to the third network function;

[0324] Based on the allowed QoS information included in network data, session data, or service instance data, determine whether the QoS requested by the first communication device is satisfied or not.

[0325] Based on the default maximum number of devices that the first communication device can connect to, which is included in network data, session data, or business instance data, IP address range information is sent to the third network function.

[0326] Optionally, the acquisition module 501 is also used to send gateway information data to the third network function;

[0327] Based on the maximum number of devices that the first communication device can connect to, which is included in the gateway information data, IP address range information is sent to the third network function.

[0328] Optionally, the acquisition module 501 is also used to receive service parameters for the first identifier or the second identifier.

[0329] Optionally, the acquisition module 501 is also used to send service parameters to the second network function based on the contract data;

[0330] Based on application data, service parameters are sent to the second network function.

[0331] Optionally, the acquisition module 501 is also used to determine, based on the contract data, the service parameters to be sent to the second network function;

[0332] Based on the application data, determine the service parameters to be sent to the second network function.

[0333] Optionally, when the service parameters indicate the network, session, or service instance for creating the target service, the acquisition module 501 is also used to send service parameters to the second network function based on the number of networks, sessions, or service instances of the target service included in the subscription data.

[0334] Based on the first instruction information included in the contract data, service parameters are sent to the second network function.

[0335] Optionally, when the service parameters indicate the network, session, or service instance for creating the target service, the acquisition module 501 is used to send the service parameters to the second network function based on the number of records in the application data.

[0336] Optionally, the acquisition module 501 sends PDU session information from application data and PDU session information from network data, session data or service instance data to the second network function based on service parameters.

[0337] Optionally, the business parameters include at least one of the following:

[0338] The network identifier, session identifier, or service instance identifier of the target service;

[0339] PDU session information;

[0340] Business operation information, including any one of the following: create operation, add operation, release operation, delete operation, and update operation;

[0341] The identifier of the first communication device;

[0342] The maximum number of devices that the first communication device can connect to;

[0343] The QoS information of the first communication device is used to indicate the QoS information of the first communication device for non-3GPP access.

[0344] Identification information is used to identify control messages of a target service sent to the first communication device, or control messages of a target service sent by the first communication device.

[0345] Optionally, the PDU session information includes at least one of the following:

[0346] Data network name: DNN;

[0347] Single network slice selection auxiliary information S-NSSAI;

[0348] PDU Session Identifier ID;

[0349] The identifier of the user terminal to which the PDU session belongs.

[0350] Figure 6 This is a second schematic diagram of the parameter acquisition device provided in the embodiments of this application. Figure 6 As shown, the parameter acquisition device provided in this embodiment includes:

[0351] The sending module 601 is used to send configuration parameters of a target service to a first network function based on a first identifier or a second identifier; the configuration parameters include at least one of the following:

[0352] Contract data for the target business;

[0353] Application data for the target business;

[0354] Network data, session data, or service instance data of the target service;

[0355] Gateway information data for the target service;

[0356] The first identifier is associated with the second identifier, and the first identifier or the second identifier is associated with one or more first communication devices.

[0357] Optionally, the contract data includes at least one of the following:

[0358] The first identifier is used to associate contract data;

[0359] A second identifier associated with the first identifier is used to associate contract data;

[0360] Protocol Data Unit (PDU) session information is used to indicate a PDU session, which is used to transmit control messages for the target service.

[0361] The number of networks, sessions, or service instances for the target service indicates the number of networks, sessions, or service instances for the target service that are allowed to be created.

[0362] The first instruction information is used to indicate network functions that are permitted to request control of the target services from the target network.

[0363] Optionally, the application data includes at least one of the following:

[0364] The first identifier is used to associate application data, or contract data associated with application data;

[0365] The second identifier associated with the first identifier is used to associate application data, or contract data associated with the application data;

[0366] The network identifier, session identifier, or service instance identifier of the target service;

[0367] PDU session information is used to indicate a PDU session, which is a network, session, or service instance used to carry the target service.

[0368] The number of networks, sessions, or service instances of the target service is used to indicate the number of existing or created networks, sessions, or service instances of the target service.

[0369] Subnet address, used to indicate the subnet address information of the target service;

[0370] Subnet mask, used to indicate the subnet mask information of the target service.

[0371] Optionally, network data, session data, or service instance data include at least one of the following:

[0372] The first identifier is used to associate network data, session data, or business instance data;

[0373] The second identifier associated with the first identifier is used to associate network data, session data, or service instance data;

[0374] The network identifier, session identifier, or service instance identifier of the target service;

[0375] PDU session information is used to indicate a PDU session, which is a network, session, or service instance used to carry the target service.

[0376] Allowed QoS information is used to indicate the QoS information that the target network is allowed to support for data in the network, session, or service instance;

[0377] The second instruction information is used to instruct at least one of the PDU session, network, session and service instance to transmit or not transmit control messages of the target service, or to transmit or not transmit data packets of the target service.

[0378] The default maximum number of devices that the first communication device can connect to is used to determine the address range or address range size sent to the first communication device.

[0379] Optionally, the gateway information data includes at least one of the following:

[0380] The first identifier is used to associate gateway information data;

[0381] The second identifier, associated with the first identifier, is used to associate gateway information data;

[0382] The identifier of the first communication device;

[0383] The maximum number of devices that the first communication device can connect to is used to determine the address range or address range size sent to the first communication device.

[0384] The QoS information of the first communication device is used to indicate the QoS information of the first communication device for non-3GPP access.

[0385] Identification information is used to identify control messages of a target service sent to the first communication device, or control messages of a target service sent by the first communication device.

[0386] Optionally, the first identifier includes at least one of the following: a permanent identifier for the subscribed user (SUPI); PDU session information; a network identifier, session identifier, or service instance identifier for the target service; and an identifier for the first communication device.

[0387] The second identifier includes at least one of the following: the identifier of the first communication device; or the General Public User Identifier (GPSI).

[0388] Optionally, the parameter acquisition device further includes a receiving module for receiving a call subscription operation for a first network function; the parameters of the subscription operation include a first identifier;

[0389] Send an event identifier for the subscription operation to the first network function;

[0390] When the configuration parameters of the target service change, an event identifier and the configuration parameters of the target service are sent to the first network function.

[0391] Optionally, the receiving module is used to receive service parameters sent by the first network function.

[0392] Optionally, the receiving module is used to receive PDU session information in application data sent by the first network function, as well as PDU session information in network data, session data, or service instance data.

[0393] Optionally, the business parameters include at least one of the following:

[0394] The network identifier, session identifier, or service instance identifier of the target service;

[0395] PDU session information;

[0396] Business operation information, including any one of the following: create operation, add operation, release operation, delete operation, and update operation;

[0397] The identifier of the first communication device;

[0398] The maximum number of devices that the first communication device can connect to;

[0399] The QoS information of the first communication device is used to indicate the QoS information of the first communication device for non-3GPP access.

[0400] Identification information is used to identify control messages of the target service sent to the first communication device, or control messages of the target service sent by the first communication device.

[0401] Optionally, the PDU session information includes at least one of the following:

[0402] Data network name: DNN;

[0403] Single network slice selection auxiliary information S-NSSAI;

[0404] PDU Session Identifier ID;

[0405] The identifier of the user terminal to which the PDU session belongs.

[0406] The virtual device in this application embodiment can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal, or other devices besides a terminal. For example, the terminal can include, but is not limited to, the type of terminal 11 listed above; other devices can be servers, network attached storage (NAS), etc., and this application embodiment does not specifically limit the types.

[0407] The virtual device provided in this application embodiment can achieve... Figures 2 to 4 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0408] Figure 7 This is a schematic diagram of the structure of the communication device provided in the embodiments of this application, such as... Figure 7 As shown, the communication device 700 includes a processor 701 and a memory 702. The memory 702 stores programs or instructions that can run on the processor 701. For example, when the communication device 700 performs a first network function, the program or instructions executed by the processor 701 implement the various steps of the parameter acquisition method embodiment described above, and achieve the same technical effect. When the communication device 700 performs a second network function, the program or instructions executed by the processor 701 implement the various steps of the parameter acquisition method embodiment described above, and achieve the same technical effect. To avoid repetition, this will not be repeated here.

[0409] This application embodiment also provides a first network function, including a processor and a communication interface. The processor is used to obtain configuration parameters of a target service based on a first identifier or a second identifier. The configuration parameters include at least one of the following: subscription data of the target service; application data of the target service; network data, session data, or service instance data of the target service; and gateway information data of the target service. The first identifier is associated with the second identifier, and the first identifier or the second identifier is associated with one or more first communication devices. This first network function embodiment corresponds to the above-described first network function side method embodiment. All implementation processes and methods of the above method embodiments can be applied to this first network function embodiment and can achieve the same technical effects.

[0410] This application embodiment also provides a second network function, including a processor and a communication interface. The communication interface is used to send configuration parameters of a target service to a first network function based on a first identifier or a second identifier. The configuration parameters include at least one of the following: subscription data of the target service; application data of the target service; network data, session data, or service instance data of the target service; and gateway information data of the target service. The first identifier is associated with the second identifier, and the first identifier or the second identifier is associated with one or more first communication devices. This second network function embodiment corresponds to the above-described second network function side method embodiment. All implementation processes and methods of the above method embodiments can be applied to this second network function embodiment and can achieve the same technical effects.

[0411] Figure 8 This is a schematic diagram of the network-side device provided in the embodiments of this application, such as... Figure 8 As shown, the network-side device 800 includes a processor 801, a network interface 802, and a memory 803. The network interface 802 is, for example, a common public radio interface (CPRI).

[0412] Specifically, the network-side device 800 of this embodiment further includes: instructions or programs stored in a memory 803 and executable on a processor 901, wherein the processor 801 calls the instructions or programs in the memory 803 to execute... Figure 5 or Figure 6 The methods executed by each module shown achieve the same technical effect, and to avoid repetition, they will not be described in detail here.

[0413] This application embodiment also provides a parameter acquisition system, including: a first network function and a second network function, wherein the first network function can be used to execute the steps of the parameter acquisition method described above, and the second network function can be used to execute the steps of the parameter acquisition method described above.

[0414] This application also provides a readable storage medium, which can be non-transient or non-volatile. The readable storage medium stores a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described parameter acquisition method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0415] The processor is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0416] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described parameter acquisition method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0417] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0418] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described parameter acquisition method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0419] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples, embodiments, and implementations may be combined in other examples.

[0420] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0421] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A method for obtaining parameters, characterized in that, include: The first network function obtains the configuration parameters of the target service based on the first identifier or the second identifier; the configuration parameters include the application data of the target service. Wherein, the first identifier is associated with the second identifier, the first identifier or the second identifier is associated with one or more first communication devices, and the first identifier and the second identifier are associated with the same first communication device; The first identifier includes at least one of the following: a permanent identifier for a subscribed user (SUPI); PDU session information; a network identifier, session identifier, or service instance identifier for the target service; and an identifier for the first communication device.

2. The parameter acquisition method according to claim 1, characterized in that, The configuration parameters also include at least one of the following: The contract data for the target business; The target service's network data, session data, or service instance data; The gateway information data of the target service.

3. The parameter acquisition method according to claim 2, characterized in that, The contract data includes at least one of the following: The first identifier is used to associate the contract data; A second identifier associated with the first identifier is used to associate the contract data; Protocol Data Unit (PDU) session information is used to indicate a PDU session, which is used to transmit control messages for the target service. The number of networks, sessions, or service instances of the target service is used to indicate the number of networks, sessions, or service instances of the target service that are allowed. The first instruction information is used to indicate that network functions that allow requests to be made to the target network to manipulate the target service are permitted.

4. The parameter acquisition method according to claim 2, characterized in that, The application data includes at least one of the following: The first identifier is used to associate the application data, or the contract data associated with the application data; A second identifier associated with the first identifier is used to associate the application data, or the contract data associated with the application data; The network identifier, session identifier, or service instance identifier of the target service; PDU session information is used to indicate a PDU session, which is used for the network, session, or service instance of the target service. The number of networks, sessions, or service instances of the target service is used to indicate the number of existing or created networks, sessions, or service instances of the target service. Subnet address, used to indicate the subnet address information of the target service; Subnet mask, used to indicate the subnet mask information of the target service.

5. The parameter acquisition method according to claim 2, characterized in that, The network data, session data, or service instance data includes at least one of the following: The first identifier is used to associate the network data, session data, or service instance data; The second identifier associated with the first identifier is used to associate the network data, session data, or service instance data. The network identifier, session identifier, or service instance identifier of the target service; PDU session information is used to indicate a PDU session, which is used for the network, session, or service instance of the target service. Allowed Quality of Service (QoS) information, used to indicate the QoS information allowed by the target network for data in the network, session, or service instance; The second indication information is used to indicate at least one of the PDU session, the network, the session and the service instance to transmit or not transmit the control message of the target service, or to transmit or not transmit the data packet of the target service. The default maximum number of devices that the first communication device can connect to is used to determine the address range or address range size sent to the first communication device.

6. The parameter acquisition method according to claim 2, characterized in that, The gateway information data includes at least one of the following: The first identifier is used to associate the gateway information data; A second identifier associated with the first identifier is used to associate the gateway information data; The identifier of the first communication device; The maximum number of devices that the first communication device can connect to is used to determine the address range or address range size sent to the first communication device. The QoS information of the first communication device is used to indicate the QoS information of the first communication device for non-3GPP access. Identification information is used to identify control messages of the target service sent to the first communication device, or control messages of the target service sent by the first communication device.

7. The parameter acquisition method according to any one of claims 2 to 6, characterized in that, The second identifier includes at least one of the following: the identifier of the first communication device; or the General Public User Identifier (GPSI).

8. The parameter acquisition method according to any one of claims 2 to 6, characterized in that, The first network function, based on the first identifier, learns the configuration parameters of the target service, including: The first network function obtains the configuration parameters of the target service from the second network function based on the first identifier.

9. The parameter acquisition method according to claim 7, characterized in that, The first network function, based on the first identifier, learns the configuration parameters of the target service, including: The first network function obtains the configuration parameters of the target service from the second network function based on the first identifier.

10. The parameter acquisition method according to claim 8, characterized in that, The first network function obtains the configuration parameters of the target service from the second network function based on the first identifier, including: The first network function invokes a subscription operation to the second network function; the parameters of the subscription operation include the first identifier; The first network function receives the event identifier of the subscription operation sent by the second network function; The first network function is associated with the event identifier and the first identifier, or associated with the event identifier and one or more first communication devices associated with the first identifier; The first network function receives the event identifier and the configuration parameters of the target service sent by the second network function.

11. The parameter acquisition method according to claim 8, characterized in that, The first network function obtains the configuration parameters of the target service from the second network function based on the first identifier, including: The first network function invokes a subscription operation from the first communication device to the second network function; the parameters of the subscription operation include the first identifier; The first network function receives the event identifier of the subscription operation sent by the second network function; The first network function is associated with the event identifier and the first communication device; The first network function receives the event identifier and the configuration parameters of the target service sent by the second network function.

12. The parameter acquisition method according to any one of claims 1 to 6, 9 to 11, characterized in that, When the configuration parameters include the application data, the method further includes: Based on the application data, the first network function sends a User Equipment Routing Policy (URSP) to the first communication device.

13. The parameter acquisition method according to any one of claims 2 to 6, 9 to 11, characterized in that, The method further includes at least one of the following: The first network function sends the network data, session data, or service instance data to the third network function; The first network function determines whether the QoS requested by the first communication device is satisfied or not, based on the allowed QoS information included in the network data, session data, or service instance data. The first network function sends IP address range information to the third network function based on the default maximum number of devices that the first communication device can connect to, which is included in the network data, session data, or service instance data.

14. The parameter acquisition method according to any one of claims 2 to 6, 9 to 11, characterized in that, The method further includes at least one of the following: The first network function sends the gateway information data to the third network function; The first network function sends IP address range information to the third network function based on the maximum number of devices that the first communication device can connect to, which is included in the gateway information data.

15. The parameter acquisition method according to any one of claims 2 to 6, 9 to 11, characterized in that, Before the first network function obtains the configuration parameters of the target service based on the first identifier or the second identifier, the method further includes: The first network function receives service parameters for the first identifier or the second identifier.

16. The method according to claim 15, characterized in that, After the first network function obtains the configuration parameters of the target service based on the first identifier or the second identifier, the method further includes at least one of the following: The first network function sends the service parameters to the second network function based on the contract data; The first network function sends the service parameters to the second network function based on the application data.

17. The method according to claim 15, characterized in that, After the first network function obtains the configuration parameters of the target service based on the first identifier or the second identifier, the method further includes at least one of the following: Based on the subscription data, the first network function determines to send the service parameters to the second network function; Based on the application data, the first network function determines to send the service parameters to the second network function.

18. The parameter acquisition method according to claim 16, characterized in that, The first network function sends the service parameters to the second network function based on the subscription data, including at least one of the following: When the service parameters indicate the network, session, or service instance for creating the target service, the first network function sends the service parameters to the second network function based on the number of networks, sessions, or service instances of the target service included in the subscription data. The first network function sends the service parameters to the second network function based on the first indication information included in the contract data.

19. The parameter acquisition method according to claim 16, characterized in that, The first network function sends the service parameters to the second network function based on the application data, including: When the service parameters indicate the network, session, or service instance for creating the target service, the first network function sends the service parameters to the second network function based on the number of records of the application data.

20. The parameter acquisition method according to claim 15, characterized in that, The method further includes: Based on the service parameters, the first network function sends the PDU session information in the application data and the PDU session information in the network data, session data or service instance data to the second network function.

21. The parameter acquisition method according to any one of claims 16 to 20, characterized in that, The business parameters include at least one of the following: The network identifier, session identifier, or service instance identifier of the target service; PDU session information; Business operation information, including any one of the following: create operation, add operation, release operation, delete operation, and update operation; The identifier of the first communication device; The maximum number of devices that the first communication device can connect to; The QoS information of the first communication device is used to indicate the QoS information of the first communication device for non-3GPP access. Identification information is used to identify the control message of the target service sent to the first communication device, or the control message of the target service sent by the first communication device.

22. The parameter acquisition method according to any one of claims 1 to 6, 16 to 20, characterized in that, The PDU session information includes at least one of the following: Data network name: DNN; Single network slice selection auxiliary information S-NSSAI; PDU Session Identifier ID; The identifier of the user terminal to which the PDU session belongs.

23. A method for obtaining parameters, characterized in that, include: The second network function sends configuration parameters of the target service to the first network function based on the first identifier or the second identifier; the configuration parameters include application data of the target service. Wherein, the first identifier is associated with the second identifier, the first identifier or the second identifier is associated with one or more first communication devices, and the first identifier and the second identifier are associated with the same first communication device; The first identifier includes at least one of the following: a permanent identifier for a subscribed user (SUPI); PDU session information; a network identifier, session identifier, or service instance identifier for the target service; and an identifier for the first communication device.

24. The parameter acquisition method according to claim 23, characterized in that, The configuration parameters include at least one of the following: The contract data for the target business; The target service's network data, session data, or service instance data; The gateway information data of the target service.

25. The parameter acquisition method according to claim 24, characterized in that, The contract data includes at least one of the following: The first identifier is used to associate the contract data; A second identifier associated with the first identifier is used to associate the contract data; Protocol Data Unit (PDU) session information is used to indicate a PDU session, which is used to transmit control messages for the target service. The number of networks, sessions, or service instances of the target service is used to indicate the number of networks, sessions, or service instances of the target service that are allowed to be created. The first instruction information is used to indicate that network functions that allow requests to be made to the target network to manipulate the target service are permitted.

26. The parameter acquisition method according to claim 24, characterized in that, The application data includes at least one of the following: The first identifier is used to associate the application data, or the contract data associated with the application data; A second identifier associated with the first identifier is used to associate the application data, or the contract data associated with the application data; The network identifier, session identifier, or service instance identifier of the target service; PDU session information is used to indicate a PDU session, which is used to carry the network, session, or service instance of the target service. The number of networks, sessions, or service instances of the target service is used to indicate the number of existing or created networks, sessions, or service instances of the target service. Subnet address, used to indicate the subnet address information of the target service; Subnet mask, used to indicate the subnet mask information of the target service.

27. The parameter acquisition method according to claim 24, characterized in that, The network data, session data, or service instance data includes at least one of the following: The first identifier is used to associate the network data, session data, or service instance data; The second identifier associated with the first identifier is used to associate the network data, session data, or service instance data. The network identifier, session identifier, or service instance identifier of the target service; PDU session information is used to indicate a PDU session, which is used to carry the network, session, or service instance of the target service. Allowed Quality of Service (QoS) information, used to indicate the QoS information that the target network is allowed to support for data in the network, session, or service instance; The second indication information is used to indicate at least one of the PDU session, the network, the session and the service instance to transmit or not transmit the control message of the target service, or to transmit or not transmit the data packet of the target service. The default maximum number of devices that the first communication device can connect to is used to determine the address range or address range size sent to the first communication device.

28. The parameter acquisition method according to claim 24, characterized in that, The gateway information data includes at least one of the following: The first identifier is used to associate the gateway information data; A second identifier associated with the first identifier is used to associate the gateway information data; The identifier of the first communication device; The maximum number of devices that the first communication device can connect to is used to determine the address range or address range size sent to the first communication device. The QoS information of the first communication device is used to indicate the QoS information of the first communication device for non-3GPP access. Identification information is used to identify control messages of the target service sent to the first communication device, or control messages of the target service sent by the first communication device.

29. The parameter acquisition method according to any one of claims 23 to 28, characterized in that, The second identifier includes at least one of the following: the identifier of the first communication device; or the General Public User Identifier (GPSI).

30. The parameter acquisition method according to any one of claims 23 to 28, characterized in that, The second network function sends configuration parameters of the target service to the first network function based on the first identifier or the second identifier, including: The second network function receives a call subscription operation from the first network function; the parameters of the subscription operation include the first identifier; The second network function sends the event identifier of the subscription operation to the first network function; When the configuration parameters of the target service change, the second network function sends the event identifier and the configuration parameters of the target service to the first network function.

31. The parameter acquisition method according to any one of claims 24 to 28, characterized in that, The method further includes: The second network function receives the service parameters sent by the first network function.

32. The parameter acquisition method according to claim 31, characterized in that, The method further includes: The second network function receives PDU session information from the application data sent by the first network function, as well as PDU session information from the network data, session data, or service instance data.

33. The parameter acquisition method according to claim 31, characterized in that, The business parameters include at least one of the following: The network identifier, session identifier, or service instance identifier of the target service; PDU session information; Business operation information, including any one of the following: create operation, add operation, release operation, delete operation, and update operation; The identifier of the first communication device; The maximum number of devices that the first communication device can connect to; The QoS information of the first communication device is used to indicate the QoS information of the first communication device for non-3GPP access. Identification information is used to identify control messages of the target service sent to the first communication device, or control messages of the target service sent by the first communication device.

34. The parameter acquisition method according to any one of claims 23 to 28 and 32, 33, characterized in that, The PDU session information includes at least one of the following: Data network name: DNN; Single network slice selection auxiliary information S-NSSAI; PDU Session Identifier ID; The identifier of the user terminal to which the PDU session belongs.

35. A parameter acquisition device, characterized in that, include: The acquisition module is used to obtain the configuration parameters of the target service based on a first identifier or a second identifier; the configuration parameters include the application data of the target service. Wherein, the first identifier is associated with the second identifier, the first identifier or the second identifier is associated with one or more first communication devices, and the first identifier and the second identifier are associated with the same first communication device; The first identifier includes at least one of the following: a permanent identifier for a subscribed user (SUPI); PDU session information; a network identifier, session identifier, or service instance identifier for the target service; and an identifier for the first communication device.

36. A parameter acquisition device, characterized in that, include: The sending module is used to send configuration parameters of a target service to a first network function based on a first identifier or a second identifier; the configuration parameters include application data of the target service. Wherein, the first identifier is associated with the second identifier, the first identifier or the second identifier is associated with one or more first communication devices, and the first identifier and the second identifier are associated with the same first communication device; The first identifier includes at least one of the following: a permanent identifier for a subscribed user (SUPI); PDU session information; a network identifier, session identifier, or service instance identifier for the target service; and an identifier for the first communication device.

37. A first network function, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the parameter acquisition method as described in any one of claims 1 to 22.

38. A second network function, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the parameter acquisition method as described in any one of claims 23 to 34.

39. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions, which, when executed by a processor, implement the parameter acquisition method as described in any one of claims 1-22, or implement the steps of the parameter acquisition method as described in any one of claims 23 to 34.

Images