Request method, device, apparatus and storage medium

Abstract

Embodiments of the present application provide a request method, device, apparatus and storage medium, wherein the request method comprises: receiving a first request packet sent by a network function entity NF, the first request packet being used for requesting at least two of user registration, requesting to obtain subscription information and requesting target subscription subscription; in response to the first request packet, generating feedback information for the first request packet; and sending the feedback information to the NF. The request method provided by the embodiments of the present application can reduce the number of requests between network elements, and further can reduce the number of message interactions between network elements, and can improve the interface processing performance between network elements.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of communication technology, in particular to a request method, device, apparatus and storage medium. BACKGROUND

[0002] In a communication core network system, a unified data management entity (UDM) is a unified data management entity device, which manages user identifiers, subscription data, authentication data and the like of the core network system. The subscription data of a user is stored in the UDM. In a user registration and session establishment process, a network function entity (NF) registers with the UDM and obtains subscription data from the UDM. After successful obtaining, the NF subscribes to the subscription data of interest, so as to receive a notification from the UDM after data changes.

[0003] In an existing service process, the number of message interactions between network elements is too large, and the processing performance of the UDM is required to be high. Too many message interactions in the service also cause poor processing performance of the network element, resulting in process timeout or exception. SUMMARY

[0004] Embodiments of the present application provide a request method, device, apparatus and storage medium in the field of communication technology, to solve the defect that the number of message interactions between network elements is too large and the processing performance of the UDM is required to be high in the prior art, and to realize the function of improving the internal processing capability of the network element.

[0005] In a first aspect, embodiments of the present application provide a request method applied to a unified data management entity (UDM), and the method comprises:

[0006] receiving a first request packet sent by a network function entity (NF), the first request packet being used to request at least two of user registration, subscription information acquisition and target subscription;

[0007] generating feedback information for the first request packet in response to the first request packet;

[0008] sending the feedback information to the NF.

[0009] Optionally, according to the request method of an embodiment of the present application, the request parameter in the first request packet is located in the packet header of the first request packet.

[0010] Optionally, according to the request method of an embodiment of the present application, the request parameter in the first request packet is located in the body of the first request packet.

[0011] Optionally, according to the request method of one embodiment of the present application, in the case that the first request packet is used at least for requesting user registration and for requesting to obtain subscription information, the feedback information for the first request packet is generated in response to the first request packet, including:

[0012] The user registration request parameter in the first request packet for requesting user registration is parsed, the user registration request parameter is stored into a local database, and the user registration is completed;

[0013] It is judged whether the target subscription request parameter in the first request packet for requesting target subscription is carried;

[0014] If it is determined that the target subscription request parameter is not carried in the first request packet, the subscription information is obtained based on a subscription permanent identifier SUPI, and the feedback information is generated based on the subscription information;

[0015] If it is determined that the target subscription request parameter is carried in the first request packet, the target subscription request parameter is stored into a local database, a target subscription ID is generated, and the feedback information is generated based on the target subscription ID and the subscription information after the subscription information is obtained based on the SUPI.

[0016] In a second aspect, the embodiments of the present application further provide a request method, applied to an NF, and the method comprises:

[0017] A first request packet is sent to a unified data management entity UDM, and the first request packet is used for at least two of requesting user registration, requesting to obtain subscription information and requesting target subscription;

[0018] Feedback information for the first request packet sent by the UDM is received, and the feedback information is generated by the UDM in response to the first request packet.

[0019] Optionally, according to the request method of one embodiment of the present application, the request parameter in the first request packet is located in a packet header of the first request packet.

[0020] Optionally, according to the request method of one embodiment of the present application, the request parameter in the first request packet is located in a body of the first request packet.

[0021] Optionally, according to the request method of one embodiment of the present application, in the case that the first request packet is used for requesting user registration and for requesting to obtain subscription information, the subscription information corresponding to a subscription permanent identifier SUPI is included in the feedback information.

[0022] Optionally, according to the request method of one embodiment of the present application, in the case that the first request packet is used for requesting user registration, requesting to obtain subscription information, and requesting target subscription, the feedback information comprises subscription information corresponding to a subscription permanent identifier (SUPI) and a subscription ID corresponding to a target subscription parameter in the first request packet.

[0023] In a third aspect, the embodiments of the present application further provide a UDM, comprising a memory, a transceiver, and a processor, wherein:

[0024] a memory for storing a computer program; a transceiver for transceiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0025] receiving a first request packet sent by a network function entity (NF), the first request packet being used for at least two of requesting user registration, requesting to obtain subscription information, and requesting target subscription;

[0026] generating feedback information for the first request packet in response to the first request packet;

[0027] sending the feedback information to the NF.

[0028] Optionally, according to the UDM of one embodiment of the present application, the request parameter in the first request packet is located in a packet header of the first request packet.

[0029] Optionally, according to the UDM of one embodiment of the present application, the request parameter in the first request packet is located in a body of the first request packet.

[0030] Optionally, according to the UDM of one embodiment of the present application, in the case that the first request packet is used for at least requesting user registration and requesting to obtain subscription information, the generating of the feedback information for the first request packet in response to the first request packet comprises:

[0031] parsing a user registration request parameter in the first request packet for requesting user registration, storing the user registration request parameter into a local database, and completing the user registration;

[0032] judging whether a target subscription request parameter for requesting target subscription is carried in the first request packet;

[0033] if it is determined that the target subscription request parameter is not carried in the first request packet, obtaining the subscription information based on a subscription permanent identifier (SUPI) and generating the feedback information based on the subscription information;

[0034] If it is determined that the target subscription request parameter is carried in the first request packet, the target subscription request parameter is stored in a local database, a target subscription ID is generated, and after the subscription information is obtained based on the SUPI, the feedback information is generated based on the target subscription ID and the subscription information.

[0035] In a fourth aspect, the embodiments of the present application further provide an NF, comprising a memory, a transceiver, and a processor, wherein:

[0036] The memory is configured to store a computer program; the transceiver is configured to transceive data under the control of the processor; and the processor is configured to read the computer program in the memory and perform the following operations:

[0037] sending a first request packet to a unified data management entity (UDM), the first request packet being used to request at least two of user registration, subscription information acquisition, and target subscription.

[0038] receiving feedback information for the first request packet sent by the UDM, the feedback information being generated by the UDM in response to the first request packet.

[0039] Optionally, in the NF according to an embodiment of the present application, the request parameter in the first request packet is located in a packet header of the first request packet.

[0040] Optionally, in the NF according to an embodiment of the present application, the request parameter in the first request packet is located in a body of the first request packet.

[0041] Optionally, in the NF according to an embodiment of the present application, in the case where the first request packet is used to request user registration and request subscription information acquisition, the feedback information comprises subscription information corresponding to a subscription permanent identifier (SUPI).

[0042] Optionally, in the NF according to an embodiment of the present application, in the case where the first request packet is used to request user registration, request subscription information acquisition, and request target subscription, the feedback information comprises subscription information corresponding to a subscription permanent identifier (SUPI) and a subscription ID corresponding to the target subscription parameter in the first request packet.

[0043] In a fifth aspect, the embodiments of the present application further provide a requesting apparatus, comprising:

[0044] a first receiving unit configured to receive a first request packet sent by a network function entity (NF), the first request packet being used to request at least two of user registration, subscription information acquisition, and target subscription.

[0045] a response unit, configured to generate feedback information for the first request packet in response to the first request packet;

[0046] a first sending unit, configured to send the feedback information to the NF.

[0047] In a sixth aspect, an embodiment of the present application further provides a request device, comprising:

[0048] a second sending unit, configured to send a first request packet to a unified data management entity (UDM), the first request packet being used to request at least two of user registration, subscription information acquisition and target subscription.

[0049] a second receiving unit, configured to receive feedback information for the first request packet sent by the UDM, the feedback information being generated by the UDM in response to the first request packet.

[0050] In a seventh aspect, an embodiment of the present application further provides a processor-readable storage medium, which stores a computer program, the computer program being used to make the processor execute the method in the first aspect or the method in the second aspect.

[0051] The request method, device, apparatus and storage medium provided by the embodiments of the present application can reduce the number of requests between network elements, and further reduce the number of message interactions between network elements, and can improve the interface processing performance between network elements. BRIEF DESCRIPTION OF DRAWINGS

[0052] In order to more clearly illustrate the technical solutions of the embodiments of the present application or the prior art, the following will briefly introduce the drawings needed to be used in the embodiments or prior art description. Obviously, the drawings in the following description are some embodiments of the present application, and those skilled in the art can obtain other drawings according to these drawings without creative labor.

[0053] Figure 1 is a user equipment registration process schematic diagram provided by the embodiments of the present application;

[0054] Figure 2 is a user equipment session process schematic diagram provided by the embodiments of the present application;

[0055] Figure 3 is a network function entity interaction process schematic diagram provided by the embodiments of the present application;

[0056] Figure 4 is one of the request method process schematic diagrams provided by the embodiments of the present application;

[0057] Figure 5 This is a second flowchart illustrating the request method provided in the embodiments of this application;

[0058] Figure 6 This is the third flowchart illustrating the request method provided in the embodiments of this application;

[0059] Figure 7 This is the fourth flowchart illustrating the request method provided in the embodiments of this application;

[0060] Figure 8 This is the fifth flowchart illustrating the request method provided in the embodiments of this application;

[0061] Figure 9 This is the sixth flowchart illustrating the request method provided in the embodiments of this application;

[0062] Figure 10 This is the seventh flowchart illustrating the request method provided in the embodiments of this application;

[0063] Figure 11 This is the eighth flowchart illustrating the request method provided in the embodiments of this application;

[0064] Figure 12 This is a schematic diagram of the UDM structure provided in the embodiments of this application;

[0065] Figure 13 This is a schematic diagram of the structure of the NF provided in the embodiments of this application;

[0066] Figure 14 This is one of the structural schematic diagrams of the request device provided in the embodiments of this application;

[0067] Figure 15 This is the second schematic diagram of the request device provided in the embodiments of this application. Detailed Implementation

[0068] In the embodiments of this application, the term "and / or" describes the relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. The character " / " generally indicates that the preceding and following associated objects have an "or" relationship.

[0069] In the embodiments of this application, the term "multiple" refers to two or more, and other quantifiers are similar.

[0070] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0071] The technical solutions provided in this application can be applied to various systems, especially 5G systems. For example, applicable systems include Global System for Mobile Communication (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA) General Packet Radio Service (GPRS), Long Term Evolution (LTE), LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), Long Term Evolution Advanced (LTE-A), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX), and 5G New Radio (NR). All of these systems include terminal equipment and network equipment. The systems may also include a core network component, such as Evolved Packet System (EPS) and 5G systems (5GS).

[0072] The terminal devices involved in the embodiments of this application can be devices that provide voice and / or data connectivity to users, handheld devices with wireless connectivity, or other processing devices connected to a wireless modem. The names of the terminal devices may differ in different systems; for example, in a 5G system, a terminal device can be called User Equipment (UE). Wireless terminal devices can communicate with one or more core networks (CNs) via a Radio Access Network (RAN). Wireless terminal devices can be mobile terminal devices, such as mobile phones (or "cellular" phones) and computers with mobile terminal devices, for example, portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile devices that exchange voice and / or data with the RAN. Examples include Personal Communication Service (PCS) phones, cordless phones, Session Initiated Protocol (SIP) phones, Wireless Local Loop (WLL) stations, and Personal Digital Assistants (PDAs). Wireless terminal equipment can also be referred to as a system, subscriber unit, subscriber station, mobile station, mobile station, remote station, access point, remote terminal, access terminal, user terminal, user agent, or user device, but is not limited to these terms in the embodiments of this application.

[0073] To facilitate a clearer understanding of the various embodiments of this application, some relevant background knowledge will be introduced as follows.

[0074] In the core network system of communication, the Unified Data Management (UDM) entity stores the user's subscription data. During user registration and session establishment, the Network Function (NF) entity registers with the UDM and obtains the subscription data from the UDM. After successful acquisition, the NF subscribes to the subscription data it is interested in so that it can receive notifications from the UDM when the data changes.

[0075] Figure 1 This is a schematic diagram of the user equipment registration process provided in the embodiments of this application, such as... Figure 1 As shown, during the UE registration process, the Access and Mobility Management Function (AMF) and the UDM exchange messages to enable the UE's registration, acquisition of subscription information, and subscription, including the following steps 1-24:

[0076] Step 1. The UE sends a registration request to the RAN;

[0077] Step 2. RAN selects access and mobility management functions;

[0078] Step 3. The RAN sends a registration request to the new AMF;

[0079] Step 4. The new AMF passes Namf_Communication_UEContext to the old AMF;

[0080] Step 5. The old AMF sends a response, Namf_Communication_UEContext, to the new AMF;

[0081] Step 6. The new AMF sends an authentication request to the UE;

[0082] Step 7. The UE sends an authentication response to the AMF;

[0083] Step 8. Select the Authentication Service Function (AUSF) for the new AMF;

[0084] Step 9. Perform security authentication between the new AMF and AUSF, between the new AMF and UE, and between AUSF and UDM;

[0085] Step 10. The new AMF sends a Namf_Communication_Registration completion notification to the old AMF;

[0086] Step 11. The UE and the new AMF exchange authentication requests or responses;

[0087] Step 12. The new AMF sends N5g_eir_EquipmentIdentityCheck_Get to the Equipment Identity Register (EIR);

[0088] Specifically, the new AMF sends N5g_eir_EquipmentIdentityCheck_Get to the EIR to obtain 5G device identifier registration confirmation;

[0089] Step 13. Select UDM for the new AMF;

[0090] Step 14a. The new AMF sends Nudm_UECM_Registration to the UDM;

[0091] Specifically, the new AMF sends Nudm_UECM_Registration to the UDM to register; Step 14b. The new AMF sends Nudm_SDM_Get to the UDM;

[0092] Specifically, the new AMF sends a Nudm_SDM_Get message to the UDM to obtain the subscription data from the UDM;

[0093] Step 14c. The new AMF sends Nudm_SDM_Subscribe to the UDM;

[0094] Specifically, the new AMF sends Nudm_SDM_Subscribe to the UDM to subscribe to the signed data change subscription;

[0095] Step 14d. UDM sends a Nudm_UECM registration cancellation notification to the old AMF;

[0096] Step 14e. The old AMF sends Nudm_SDM to the UDM to cancel the subscription;

[0097] Step 15. Select the Policy Control Function (PCF) for the new AMF;

[0098] Step 16. The new AMF and PCF negotiate and establish or modify access and mobility policies;

[0099] Step 17. The new AMF sends Nsmf_PDUSession_UpdateSMContext / Nsmf_PDUSession_ReleaseSMContext to the Session Management Function (SMF);

[0100] Specifically, the new AMF sends Nsmf_PDUSession_UpdateSMContext / to the SMF.

[0101] Nsmf_PDUSession_ReleaseSMContext to update or release the corresponding session content;

[0102] Step 18. The Non-3GPP Interworking Function (N3IWF) sends an N2 Access and Mobility Function Mobility Request to the new AMF;

[0103] Step 19. The new AMF sends the N2 Access and Mobility Function Mobility Response to the N3IWF;

[0104] Step 20a. The new AMF sends Nudm_UECM_Registration to the UDM;

[0105] Step 20b. UDM sends a Nudm_UECM_Deregistration notification to the old AMF;

[0106] Step 20c. The old AMF sends Nudm_SDM_Unsubscribe to the UDM;

[0107] Step 21a. The new AMF sends a registration message to the UE;

[0108] Specifically, the new AMF sends a message to the UE to receive registration;

[0109] Step 21b. The new AMF sends the user terminal policy / negotiation establishment to the PCF;

[0110] Specifically, the new AMF sends a message to the PCF to establish user terminal policy / negotiation.

[0111] Step 22. The UE sends a registration completion message to the new AMF;

[0112] Specifically, the UE sends a registration completion message to the new AMF;

[0113] Step 23. The new AMF sends Nudm_SDM_Info to the UDEM;

[0114] Specifically, the new AMF sends Nudm_SDM_Info to the UDEM to obtain configuration information;

[0115] Step 24. The new AMF sends Nudm_UECM_Update to the UDEM;

[0116] Specifically, the new AMF sends Nudm_UECM_Update to the UDEM to obtain update information.

[0117] Figure 2 This is a schematic diagram of the user equipment session flow provided in the embodiments of this application, such as... Figure 2As shown, SMF can register with UDM, obtain subscription data from UDM, and perform subscription data modification and subscription, including the following steps 1-20:

[0118] Step 1. The UE sends a Protocol Data Unit Session Establishment Request to the AMF via the RAN;

[0119] Step 2. Select SMF for AMF;

[0120] Step 3. The AMF sends an Nsmf_PDUSession_CreateSMContext request to the SMF;

[0121] Step 4. SMF and UDM perform registration / contract search and contract update;

[0122] Specifically, SMF and UDM exchange information such as registration / contract retrieval and contract update;

[0123] Step 5. SMF responds to AMF's Nsmf_PDUSession_CreateSMContext;

[0124] Step 6. Perform protocol data unit session authentication or authorization between network elements;

[0125] Step 7a. Select PCF for SMF;

[0126] Step 7b. Session Management Policy Negotiation: Establishing and initializing the session management function involves negotiating and modifying the session policy.

[0127] Step 8. User-facing function selection;

[0128] Step 9. Initialize session management function and modify session management policy / negotiation;

[0129] Step 10a. The SMF sends an N4 session establishment / modification request to the User Plane Function (UPF);

[0130] Step 10b. UPF responds to SMF with an N4 session establishment / modification request;

[0131] Step 11. Passing Namf_Communication_N1N2 messages between AMF and SMF;

[0132] Step 12. The AMF sends an N2 Protocol Data Unit Session Request (NAS msg) to the RAN;

[0133] Step 13. Establishment of access network specific resources (establishment of Accept Protocol Data Unit session);

[0134] Step 14. The RAN sends an N2 protocol data unit session request confirmation to the AMF;

[0135] Among them, the UE sends the first uplink data to the UPF;

[0136] Step 15. The AMF sends an Nsmf_PDUSession_UpdateSMContext request to the SMF;

[0137] Step 16a. The SMF sends an N4 session modification request to the UPF;

[0138] Among them, the UPF sends the downlink data to the UE;

[0139] Step 16b. UPF sends an N4 session modification response to SMF;

[0140] Step 17. The SMF sends an Nsmf_PDUSession_UpdateSMContext response to the AMF;

[0141] Step 18. The SMF sends an Nsmf_PDUSession_SMContext status notification to the AMF;

[0142] Step 19. The SMF sends the IPv6 address configuration to the UPF and UE sequentially;

[0143] Step 20. Cancellation of contract / registration between SMF and UDM.

[0144] Figure 3 This is a schematic diagram of the network function entity interaction process provided in the embodiments of this application, such as... Figure 3 As shown, taking the interaction process between AMF and UDM as an example, the detailed message flow includes the following steps 1-10, where steps 1 and 2 are the network function entity registration process; steps 3-8 are the data acquisition process; and steps 9 and 10 are the subscription process.

[0145] Step 1. AMF requests registration from UDM.

[0146] Specifically, AMF sends a PUT… / {ueId} / registrations / amf-3gpp-access message to UDM, and UDM stores the registration information.

[0147] Step 2. UDM responds to AMF's registration request and provides feedback on the response result.

[0148] The response results include: 2a. "204" No content; 2b. "201" Creation completed; 2c. "403" Request forbidden.

[0149] Step 3. AMF obtains the signed Network Slice Selection Assistance Information (NSSAI) from UDM.

[0150] Specifically, AMF sends the Get… / {supi} / nssai message to UDM.

[0151] Step 4. UDM responds to AMF's request to obtain contracted slice information and provides feedback on the response result.

[0152] The response results include: 4a. "200" Complete (Network slice selection auxiliary information); 4b. "404" Request failed.

[0153] Step 5. AMF obtains the signed access data information from UDM.

[0154] Specifically, AMF sends Get… / {supi} / am-data to UDM.

[0155] Step 6. UDM responds to AMF's request for obtaining contract information and provides feedback on the response result.

[0156] The response results include: 6a. "200" Complete (Access and mobile subscription data); 6b. "404" Request failed.

[0157] Step 7. AMF obtains the data of the selected SMF from UDM.

[0158] Specifically, AMF sends Get… / {supi} / smf-select-data to UDM.

[0159] Step 8. UDM responds to the request to obtain the SMF from the AMF and provides the response result.

[0160] The response results include: 8a. "200" Complete (session management function selects subscription data); 8b. "404" Request failed.

[0161] Step 9. AMF carries the resource ID to sign up for data subscription.

[0162] Specifically, AMF sends POST… / {supi} / sdm-subscriptions(SdmSubscription) to UDM.

[0163] Step 10. UDM responds to AMF's request to obtain a subscription and provides the response result.

[0164] The response results include: 10a. "201" Creation Complete (SdmSubscription); 10b. "404" Request Failed; 10c. "501" Not Completed.

[0165] In the UE registration and session processes, both the AMF / SMF interact with the UDM, including registering with the UDM, obtaining subscription data, and subscribing to subscription data changes. This results in an excessive number of interactions between the NF and the UDM. For example, in a single user registration process, the AMF interacts with the UDM five times. This places high demands on the UDM's processing performance when multiple users access the network; otherwise, it can cause timeouts or errors. Furthermore, all NFs subscribe to the UDM using the same message for subscription data changes. When subscription data changes in the UDM, the UDM needs to distinguish the subscribing network element based on its temporary ID (instanceid) to determine whether to send a notification message. This results in additional processing within the UDM, impacting its performance.

[0166] To overcome the above-mentioned deficiencies, embodiments of this application provide a request method, device, setting, and storage medium. The request method, device, setting, and storage medium provided in embodiments of this application will be described exemplarily below.

[0167] Figure 4 This is one of the flowcharts illustrating the request method provided in the embodiments of this application, such as... Figure 4 As shown, this application embodiment provides a request method, the execution subject of which can be a unified data management entity UDM, the method includes steps 400-420.

[0168] Step 400. Receive a first request packet sent by a network function entity (NF). The first request packet is used to request at least two of the following: requesting user registration, requesting to obtain subscription information, and requesting a target subscription.

[0169] Specifically, in this embodiment of the application, the UDM can receive a first request packet sent by the NF. The request packet contains multiple requests, mainly used for:

[0170] Requesting user registration and requesting to obtain contract information; or

[0171] Requesting user registration and requesting target subscription; or

[0172] Requesting contract information and requesting target contract subscription; or

[0173] Request user registration, request to obtain contract information, and request target contract subscription.

[0174] Specifically, the first request packet is mainly used to request user registration and request to obtain contract information. The request information for requesting the target contract subscription can be implemented by receiving request information sent separately by NF.

[0175] Specifically, the first request packet is mainly used to request user registration and target subscription. The request information for requesting subscription information can be obtained by receiving additional request information sent by NF.

[0176] Specifically, the first request packet is mainly used to request the acquisition of contract information and to request the target contract subscription. The request information for requesting user registration can be implemented by receiving additional request information sent by NF.

[0177] In this application embodiment, the method of sending the additional request information is not limited.

[0178] Step 410. In response to the first request packet, generate feedback information for the first request packet.

[0179] Specifically, in this embodiment of the application, after the UDM receives the first request packet sent by the NF, it can parse the request parameters in the first request packet, perform corresponding response actions on each parsed request parameter, and generate feedback information for the first request packet.

[0180] Specifically, the response action here can be implemented based on the parsed request parameters;

[0181] For example, if the parsed request parameters include parameters for requesting user registration, then the registration information is stored in the local database to complete the user registration;

[0182] For example, if the parsed request parameters include parameters for requesting subscription information, then the subscription information is obtained based on the Subscription Permanent Identifier (SUPI), and the corresponding feedback information for the first request packet includes this subscription information.

[0183] For example, if the parsed request parameters include parameters for requesting a target subscription, then the relevant information of the subscription resource is stored in the local database to complete the target subscription. Correspondingly, the feedback information for the first request packet may include the subscription ID.

[0184] Specifically, UDM can store information such as the ID of the subscribed resource and the NotifyUri in a local database.

[0185] The subscription resource ID can be used to distinguish different subscription resources.

[0186] For example, if the subscription data requested includes subscriptions to network slice selection assistance information (NSSAI) and internal group IDs, then the IDs of the two subscription resources can be dc01 and ig02, respectively, where dc01 and ig02 can be determined according to the actual situation.

[0187] NotifyUri can be a callback URI, which is invoked by the UDM when the subscribed resource changes, thereby notifying the subscriber of the relevant data changes.

[0188] Step 420. Send feedback information to NF.

[0189] Specifically, in this embodiment of the application, after the UDM generates feedback information for the first request packet, it can send feedback information to the NF. The feedback information may include one or more of the following: subscription information, subscription information, and subscription ID.

[0190] The request method provided in this application embodiment can, under multiple business requirements, request at least two of the following through a single first request packet: user registration, request to obtain contract information, and request target subscription. NF and UDM only need to exchange one pair of messages to complete multiple functions, which can reduce the number of interactions and improve the processing performance between interfaces.

[0191] The request method provided in this application embodiment can reduce the number of requests between network elements by receiving a first request packet for at least two of the following requests: requesting user registration, requesting to obtain contract information, and requesting target contract subscription. This can reduce the number of message interactions between network elements and improve the interface processing performance between network elements.

[0192] Optionally, the request parameters in the first request packet are located in the header of the first request packet.

[0193] Specifically, at least two of the following can be achieved through a GET request: requesting user registration, requesting to obtain contract information, and requesting target contract subscription. That is, the request parameters in the first request packet can be set in the header of the first request packet.

[0194] Specifically, Figure 5 This is a second flowchart illustrating the request method provided in this application embodiment, such as... Figure 5 As shown, taking the establishment of a session between Network Function Service (NF) and Unified Data Management Entity (UDM) via GET message as an example, the detailed process is shown in steps 500-520 below.

[0195] Step 500. UDM receives the NF's Get message for obtaining the contract data.

[0196] Specifically, UDM receives the GET… / {supi} / am-data message from NF, where the parameter can be: Amf3GppAccessRegistration+SdmSubscription. Step 510. Respond to the request.

[0197] Specifically, UDM can parse the message header to obtain the relevant request parameters.

[0198] Specifically, if the first request packet is used to request registration, the obtained request parameters include the Amf3GppAccessRegistration parameter; or

[0199] If the first request packet is used to request a subscription to data services, the request parameters obtained include SdmSubscription-related parameters; or

[0200] In the case where the first request packet is used to request registration and to request a subscription to data, the request parameters obtained include the Amf3GppAccessRegistration parameter and SdmSubscription related parameters.

[0201] Specifically, if the parsed message header contains Amf3GppAccessRegistration for requesting registration, the UDM can register the UE while obtaining the subscription information based on SUPI;

[0202] Specifically, if the parsed message header contains SdmSubscription-related parameters for requesting subscription data, the UDM can obtain subscription information based on SUPI while storing the relevant parameter information of the subscription resource in the local database to complete the subscription of the target subscription data.

[0203] The relevant parameters for subscribing to resources may include: the ID of the subscribed resource and the NotifyUri.

[0204] Specifically, if the parsed message header contains the Amf3GppAccessRegistration parameter for requesting registration and the SdmSubscription parameter for requesting subscription data, the UDM can obtain subscription information based on SUPI, register the UE, store the relevant parameter information of the subscription resource in the local database, complete the subscription of the target subscription data, and generate a subscription ID.

[0205] Step 520. UDM reports the response execution status to NF.

[0206] Specifically, after the UDM responds to the request parameters in the request message sent by the NF, the response execution status reported back by the UDM to the NF may include any one of the following steps 521-523:

[0207] Step 521. If UDM has completed the response to all request parameters, it will return a response completion code "200"; or

[0208] Step 522. If UDM cannot respond to any of the request parameters, it will return a response failure code "404"; or

[0209] Step 523. If UDM only completes the response for part of the request parameters, it will return the response incomplete code "501".

[0210] Upon successful completion of the response, the feedback data may include: contract data and subscription information.

[0211] For example, the request parameters of the request message sent by the NF include Amf3GppAccessRegistration and SdmSubscription. If the UDM completes the response to Amf3GppAccessRegistration and SdmSubscription, that is, completes UE registration based on Amf3GppAccessRegistration and completes subscription data subscription based on SdmSubscription, then the response success code "200" is returned. If the UDM cannot respond to Amf3GppAccessRegistration or SdmSubscription, then the response failure code "404" is returned. If the UDM completes the response to Amf3GppAccessRegistration but does not complete the response to SdmSubscription, that is, completes UE registration based on Amf3GppAccessRegistration but does not complete subscription data subscription based on SdmSubscription, then the response incomplete code "501" is returned.

[0212] The request method provided in this application embodiment receives a Get message for obtaining contract data, with multiple request parameters carried in the message header. UDM can receive multiple requests from NF by receiving a single message, which can reduce the number of messages received and improve the processing performance between interfaces.

[0213] Optionally, the request parameters in the first request packet are located in the body of the first request packet.

[0214] Specifically, at least two of the following can be achieved through a POST request: requesting user registration, requesting to obtain contract information, and requesting a target contract subscription. In other words, the request parameters in the first request packet can be set in the body of the first request packet.

[0215] Specifically, Figure 6 This is the third flowchart illustrating the request method provided in this application embodiment, such as... Figure 6 As shown, taking the establishment of a session between UDM and NF via Post messages as an example, the detailed process is shown in steps 600-620 below.

[0216] Step 600. UDM receives a POST message from NF requesting the acquisition of subscription data.

[0217] Specifically, UDM receives the POST… / {supi} / am-data message sent by NF, where the parameter can be: Amf3GppAccessRegistration+SdmSubscription.

[0218] Step 610. Respond to the request.

[0219] Specifically, UDM can parse the message body to obtain the relevant request parameters.

[0220] Specifically, if the first request packet is used to request registration, the obtained request parameters include the Amf3GppAccessRegistration parameter; or

[0221] If the first request packet is used to request a subscription to data services, the request parameters obtained include SdmSubscription-related parameters; or

[0222] In the case where the first request packet is used to request registration and to request a subscription data agreement, the obtained request parameters include the Amf3GppAccessRegistration parameter and the SdmSubscription parameter used to request a subscription data agreement.

[0223] Specifically, if the parsed message body contains the Amf3GppAccessRegistration parameter for requesting registration, the UDM can register the UE while obtaining the subscription information based on SUPI;

[0224] Specifically, if the parsed message body contains the SdmSubscription parameter for requesting subscription data, the UDM can obtain subscription information based on SUPI while storing the relevant parameter information of the subscription resource in the local database to complete the subscription of the target subscription data.

[0225] The relevant parameters for subscribing to resources may include: the ID of the subscribed resource and the NotifyUri.

[0226] Specifically, if the parsed message body contains the Amf3GppAccessRegistration parameter for requesting registration and the SdmSubscription parameter for requesting subscription data, the UDM can obtain subscription information based on SUPI, register the UE, store the relevant parameter information of the subscription resource in the local database, complete the subscription of the target subscription data, and generate a subscription ID. The SdmSubscription parameter in the message can be carried in the message body as a JSON string.

[0227] Step 620. UDM reports the response execution status to NF.

[0228] Specifically, after the UDM responds to the request parameters in the request message sent by the NF, the UDM sends feedback on the response execution status to the NF. The feedback on the response execution status sent to the NF may include any one of the following steps 621-623:

[0229] Step 621. If UDM has completed the response to all requested parameters, it will return a response completion code "200"; or

[0230] Step 622. If UDM is unable to respond to any of the request parameters, it will return a failure code "404"; or

[0231] Step 623. If UDM only completes the response for part of the request parameters, it will return the incomplete response code "501".

[0232] Upon completion of the response, the feedback data may include: contract data and subscription information.

[0233] For example, the request parameters of the request message sent by the NF include Amf3GppAccessRegistration and SdmSubscription. If the UDM completes the response to Amf3GppAccessRegistration and SdmSubscription, that is, completes UE registration based on Amf3GppAccessRegistration and completes subscription data subscription based on SdmSubscription, then the response completion code "200" is returned. If the UDM cannot respond to Amf3GppAccessRegistration or SdmSubscription, then the response failure code "404" is returned. If the UDM completes the response to Amf3GppAccessRegistration but does not complete the response to SdmSubscription, that is, completes UE registration based on Amf3GppAccessRegistration but does not complete subscription data subscription based on SdmSubscription, then the response incomplete code "501" is returned.

[0234] The request method provided in this application embodiment can receive multiple requests from the NF by receiving a Post message for obtaining contract data and carrying multiple request parameters in the message body. This reduces the number of messages received and improves the processing performance between interfaces.

[0235] Optionally, if the first request packet is used at least to request user registration and request to obtain contract information, in response to the first request packet, feedback information for the first request packet is generated, including:

[0236] Parse the user registration request parameters in the first request packet used to request user registration, store the user registration request parameters in the local database, and complete the user registration;

[0237] Determine whether the first request packet contains a target subscription request parameter used to request the target subscription;

[0238] If it is determined that the first request packet does not carry the target subscription request parameters, then the subscription information is obtained based on the subscription permanent identifier SUPI, and feedback information is generated based on the subscription information;

[0239] If it is determined that the first request packet carries the target subscription request parameter, the target subscription request parameter is stored in the local database, a target subscription ID is generated, and after obtaining the subscription information based on SUPI, feedback information is generated based on the target subscription ID and the subscription information.

[0240] Specifically, the UDM parses the user registration request parameters in the first request packet used to request user registration, stores the user registration request parameters in the local database, and after completing user registration, it can further determine whether the first request packet carries target subscription request parameters for requesting target subscription. If it is determined that the first request packet does not carry target subscription request parameters, that is, the NF does not need to perform target subscription, then the UDM can obtain subscription information based on the subscription permanent identifier SUPI and generate feedback information based on the subscription information to send back to the NF. If it is determined that the first request packet carries target subscription request parameters, that is, the NF needs to perform target subscription, then the target subscription request parameters can be stored in the local database, a target subscription ID can be generated, and after obtaining subscription information based on SUPI, feedback information can be generated based on the target subscription ID and subscription information to send back to the NF.

[0241] Optionally, Figure 7 This is the fourth flowchart illustrating the request method provided in the embodiments of this application, as follows: Figure 7 As shown, taking the UDM receiving the NF Get message as an example, the detailed process is shown in steps 710-760 below.

[0242] Step 710. UDM receives the NF Get message.

[0243] Specifically, UDM can receive request messages from NF to retrieve subscription data via Get messages.

[0244] Step 720. UDM parses the message header of the GET message to obtain the specific request parameter information.

[0245] Specifically, the parsed request parameters may include:

[0246] The Amf3GppAccessRegistration parameter is used to request registration; or

[0247] The SdmSubscription parameters used to request a subscription to data services; or

[0248] The Amf3GppAccessRegistration parameter is used to request registration, and the SdmSubscription parameter is used to request a subscription to data.

[0249] Step 730.UDM responds with the specific request parameters obtained through parsing.

[0250] Specifically, after the UDM parses the message header to obtain the relevant request parameters, the UDM can store the information about the user equipment carried by the parsed Amf3GppAccessRegistration into the local database, thereby completing the registration of the user equipment in the UDM.

[0251] Step 740.UDM can determine the specific request parameters contained after parsing.

[0252] Specifically, UDM can check whether the message header contains the SdmSubscription parameter. If the SdmSubscription parameter is not present, proceed to step 750; if the SdmSubscription parameter is present, proceed to step 760.

[0253] Step 750.UDM can respond to cases where the parsed data does not contain SdmSubscription-related parameters, and send the response message back to NF.

[0254] Specifically, step 750 may include steps 751 and 752.

[0255] Step 751. UDM queries the user equipment's subscription data.

[0256] Specifically, UDM can query user device subscription data based on SUPI.

[0257] Step 752. The UDM group responds to the NF.

[0258] Specifically, after the UDM queries the user equipment's subscription data based on SUPI, it can assemble the subscription data into a response message, carry the subscription information in the message body, and send it back to the NF.

[0259] Step 760.UDM can respond to cases where the parsed data carries parameters related to SdmSubscription and send the response message back to NF.

[0260] Specifically, step 760 may include steps 761-763.

[0261] Step 761. UDM responds to the parameters related to SdmSubscription.

[0262] Specifically, UDM can store relevant parameter information of subscription resources in a local database, complete the subscription of target contract data, and generate a subscription ID.

[0263] The SdmSubscription parameters may include the ID of the subscribed resource and the NotifyUri.

[0264] Among them, the relevant parameters of the subscribed resources may include key information such as monitoredResourceUris and callbackReference.

[0265] For example, generating a subscription ID could be:

[0266] For subscription requests sent by the same NF (such as an AMF) regarding two different subscribed resources (e.g., network slice selection assistance information (NSSAI) and internal group IDs (internalgroupIDs)), the UDM generates two subscription IDs, AMF01 and AMF02. When the UDM detects changes in the subscription data for the network slice selection assistance information (NSSAI) and internal group IDs (internalgroupIDs), it can directly notify the corresponding AMF of the changes based on the AMF in the subscription IDs. The NF, based on the 01 and 02 in the subscription IDs, clearly knows that the subscription data for the network slice selection assistance information (NSSAI) and internal group IDs (internalgroupIDs) has changed.

[0267] Step 762. UDM queries the user equipment's subscription data.

[0268] Specifically, after UDM completes the subscription of the target subscription data and generates the subscription ID, it can query the subscription data of the user device based on SUPI.

[0269] Step 763. The UDM group responds to the NF.

[0270] Specifically, after UDM queries the user device's subscription data based on SUPI, it can combine the subscription ID and subscription data into a response message, carry the subscription information in the message body, and send it back to NF.

[0271] Optionally, Figure 8 This is the fifth flowchart illustrating the request method provided in the embodiments of this application, as shown below. Figure 8 As shown, taking UDM receiving NF Post messages as an example, the detailed process is shown in steps 810-860 below.

[0272] Step 810. UDM receives the NF Post message.

[0273] Specifically, UDM receives a request message from NF via a POST message to retrieve subscription data.

[0274] Step 820. UDM parses the body of the POST message to obtain the specific request parameters.

[0275] Specifically, the parsed request parameters may include:

[0276] The Amf3GppAccessRegistration parameter is used to request registration; or

[0277] The SdmSubscription parameters used to request a subscription to data services; or

[0278] The Amf3GppAccessRegistration parameter is used to request registration, and the SdmSubscription parameter is used to request a subscription to data.

[0279] Step 830.UDM can respond to the specific request parameters obtained through parsing.

[0280] Specifically, after the UDM parses the message body to obtain the relevant request parameters, the UDM can store the information about the user equipment carried by the parsed Amf3GppAccessRegistration into the local database, thereby completing the registration of the user equipment in the UDM.

[0281] Step 840.UDM can determine the specific request parameters contained after parsing.

[0282] Specifically, UDM can check whether the message body carries the SdmSubscription related parameters.

[0283] If no SdmSubscription related parameters are provided, proceed to step 805; if SdmSubscription related parameters are provided, proceed to step 806.

[0284] Step 850.UDM can respond to cases where the parsed data does not contain SdmSubscription-related parameters, and will send the response message back to NF.

[0285] Specifically, step 850 may include steps 851 and 852.

[0286] Step 851. UDM queries the user equipment's subscription data.

[0287] Specifically, UDM can query user device subscription data based on SUPI.

[0288] Step 852. The UDM group responds to the NF.

[0289] Specifically, after the UDM queries the user equipment's subscription data based on SUPI, it can assemble the subscription data into a response message, carry the subscription information in the message body, and send it back to the NF.

[0290] Step 860.UDM can respond to cases where the parsed data carries parameters related to SdmSubscription and send the response message back to NF.

[0291] Specifically, step 860 may include steps 861-863.

[0292] Step 861. UDM responds to the parameters related to SdmSubscription.

[0293] Specifically, UDM can store relevant parameter information of subscription resources in a local database, complete the subscription of target contract data, and generate a subscription ID.

[0294] The SdmSubscription parameters may include the ID of the subscribed resource and the NotifyUri.

[0295] Among them, the relevant parameters of the subscribed resources may include key information such as monitoredResourceUris and callbackReference.

[0296] For example, generating a subscription ID could be:

[0297] For subscription requests sent by the UDM to the same NF (such as AMF) regarding two different subscribed resources (Network Slice Selection Assistance Information (NSSAI) and Internal Group IDs (internalgroupIDs)), two subscription IDs, AMF01 and AMF02, are generated. When the UDM detects changes in the subscription data for Network Slice Selection Assistance Information (NSSAI) and Internal Group IDs (internalgroupIDs), it can directly notify the corresponding AMF of the changes based on the AMF in the subscription IDs. The NF, based on 01 and 02 in the subscription IDs, clearly knows that the subscription data for Network Slice Selection Assistance Information (NSSAI) and Internal Group IDs (internalgroupIDs) has changed.

[0298] Step 862. UDM queries the user equipment's subscription data.

[0299] Specifically, after UDM completes the subscription of the target subscription data and generates the subscription ID, it can query the subscription data of the user device based on SUPI.

[0300] Step 863. The UDM group responds to the NF.

[0301] Specifically, after UDM queries the user device's subscription data based on SUPI, it can compose a response message with the subscription ID and subscription data. The message body can carry information such as subscription information, subscription ID, and subscription termination duration, and then send it back to NF.

[0302] The request method provided in this embodiment can perform the registration and subscription process simultaneously with obtaining contract data; alternatively, it can perform the acquisition of contract data and the subscription process simultaneously with registration. Both methods can implement all business functions. If the business process does not require a subscription process, the GET message method can be used first, carrying request parameters in the message header; if the business process requires a subscription process, the POST message method can be used first, carrying request parameters in the message body to avoid carrying excessively long parameter information in the message header. In specific application scenarios, the appropriate method can be selected according to actual needs, and no limitation is made here.

[0303] The request method provided in this application embodiment allows the UDM and NF to complete multiple functions in the original registration, subscription data acquisition, and subscription data change subscription process with only one pair of messages exchanged in a single business process. This reduces the number of interactions and improves the processing performance between interfaces. By unifying the process, the NF responsible for subscription data changes is clarified, simplifying unnecessary complex processing within the network element and improving its own processing performance. Simultaneously, by generating a subscription ID, the internal processing flow is improved. The UDM can intuitively perceive the subscribed NF, and when the subscribed subscription information changes, it can directly notify the subscribed NF, optimizing the processing performance within the network element. The performance improvement is particularly significant when a large number of users simultaneously access the core network.

[0304] The request method provided in this application embodiment can reduce the number of requests between network elements by receiving a first request packet for at least two of the following requests: requesting user registration, requesting to obtain contract information, and requesting target contract subscription. This can reduce the number of message interactions between network elements and improve the interface processing performance between network elements.

[0305] Figure 9 This is the sixth flowchart illustrating the request method provided in this application embodiment, as shown below. Figure 9 As shown, the execution entity can be NF. The method includes steps 900 and 910.

[0306] Step 900. Send a first request packet to the Unified Data Management Entity (UDM). The first request packet is used to request at least two of the following: requesting user registration, requesting to obtain contract information, and requesting a target subscription.

[0307] Specifically, in this embodiment of the application, NF sends a first request packet to UDM. The request packet contains multiple requests, mainly for:

[0308] Requesting user registration and requesting to obtain contract information; or

[0309] Requesting user registration and requesting target subscription; or

[0310] Request user registration, request to obtain contract information, and request target contract subscription.

[0311] Specifically, the first request packet is mainly used to request user registration and request to obtain contract information. The request information for requesting the target contract subscription can be implemented by sending a separate request message to the UDM.

[0312] Specifically, the first request packet is mainly used to request user registration and target subscription, while the request information for obtaining subscription information can be implemented by sending a separate request to UDM;

[0313] Specifically, the first request packet is mainly used to request the acquisition of contract information and to request the target contract subscription. The request information for requesting user registration can be implemented by sending a separate request message to the UDM.

[0314] In this application embodiment, the method of sending the additional request information is not limited.

[0315] Step 910. Receive feedback information sent by UDM in response to the first request packet. The feedback information is generated by UDM in response to the first request packet.

[0316] Optionally, NF can be AMF;

[0317] Alternatively, NF can be SMF.

[0318] Specifically, if the first request packet is used to request user registration and request subscription information, the system waits for the UDM to respond to the NF's request, including: obtaining subscription information according to SUPI and registering the UE. After the UDM responds to the NF's request, the NF receives feedback information, which includes subscription information, such as network slicing information.

[0319] Specifically, when the first request packet is used to request user registration and target subscription, the system waits for the UDM to respond to the NF's request, including: registering the UE, storing relevant parameter information of the subscription resources in the local database, completing the subscription of the target subscription data, and generating a subscription ID. After the UDM responds to the NF's request, the NF receives feedback information, which includes target subscription information, such as the subscription ID or subscription duration.

[0320] Specifically, when the first request packet is used to request user registration, request to obtain subscription information, or request a target subscription, the system waits for the UDM to respond to the NF's request. This includes: registering the UE, obtaining subscription information based on the SUPI, storing relevant parameter information of the subscription resource in the local database, completing the subscription of the target subscription data, and generating a subscription ID. After the UDM responds to the NF's request, the NF receives feedback information, which includes: subscription information, such as network slicing information; and target subscription information, such as subscription ID and subscription duration.

[0321] In this application embodiment, the method of receiving additional feedback information received by NF is not limited.

[0322] The subscription ID in the feedback information is generated by UDM based on different NFs and different subscription information. NFs can store the feedback subscription IDs in a local database for use in later interactions.

[0323] The request method provided in this application embodiment can complete multiple functions at once by sending only a first request packet under multiple business requirements. This can be achieved by sending only a first request packet, requesting user registration, requesting to obtain contract information, and requesting target contract subscription. NF and UDM only need to exchange one pair of messages to complete multiple functions, which can reduce the number of interactions and improve the processing performance between interfaces.

[0324] The request method provided in this application embodiment can reduce the number of requests between network elements by sending a first request packet for at least two of the following requests: requesting user registration, requesting to obtain contract information, and requesting target contract subscription. This can reduce the number of message interactions between network elements and improve the interface processing performance between network elements.

[0325] Optionally, the request parameters in the first request packet are located in the header of the first request packet.

[0326] Specifically, at least two of the following can be achieved through a GET request: requesting user registration, requesting to obtain contract information, and requesting target contract subscription. That is, the request parameters in the first request packet can be set in the header of the first request packet.

[0327] Specifically, such as Figure 5 As shown, taking the establishment of a session between Network Function Service (NF) and Unified Data Management Entity (UDM) via GET message as an example, the detailed process is shown in steps 510-520 below.

[0328] Step 500.NF sends a Get message to UDM to retrieve the contract data.

[0329] Specifically, NF sends a GET… / {supi} / am-data message to UDM. The message header may contain relevant request parameters, such as: Amf3GppAccessRegistration+SdmSubscription.

[0330] Specifically, when the first request packet is used to request registration, the request parameters include the Amf3GppAccessRegistration parameter;

[0331] Specifically, when the first request packet is used to request a subscription to data, the request parameters include SdmSubscription-related parameters;

[0332] Specifically, in the case where the first request packet is used to request registration and to request a subscription to data, the request parameters include the Amf3GppAccessRegistration parameter and the SdmSubscription related parameters.

[0333] Step 510. Respond to the request.

[0334] Specifically, when the request parameters include the Amf3GppAccessRegistration parameter, the UDM can register the UE while obtaining the subscription information based on SUPI;

[0335] Specifically, when the request parameters include SdmSubscription related parameters, UDM can obtain the subscription information based on SUPI and store the relevant parameter information of the subscription resource in the local database to complete the subscription of the target subscription data;

[0336] The relevant parameters for subscribing to resources may include: the ID of the subscribed resource and the NotifyUri.

[0337] Specifically, when the request parameters include the Amf3GppAccessRegistration parameter and the SdmSubscription related parameters, the UDM can obtain the subscription information based on SUPI, register the UE, store the relevant parameter information of the subscription resources in the local database, complete the subscription of the target subscription data, and generate a subscription ID.

[0338] The SdmSubscription parameter can be carried in the message body as a JSON string.

[0339] Step 520.NF receives feedback from UDM on the response execution status.

[0340] Specifically, after the UDM responds to the request parameters in the request message sent by the NF, the NF's receipt of feedback from the UDM on the execution status of the response may include any one of the following steps 521-523:

[0341] Step 521. If UDM has completed the response to all request parameters, it will return a response completion code "200"; or

[0342] Step 522. If UDM cannot respond to any of the request parameters, it will return a response failure code "404"; or

[0343] Step 523. If UDM only completes the response for part of the request parameters, it will return the response incomplete code "501".

[0344] Upon successful completion of the response, the feedback data may include: contract data and subscription information.

[0345] For example, the request parameters of the request message sent by the NF include Amf3GppAccessRegistration and SdmSubscription. If the UDM completes the response to Amf3GppAccessRegistration and SdmSubscription, that is, completes UE registration based on Amf3GppAccessRegistration and subscription of data based on SdmSubscription, then the response success code "200" is returned. If the UDM cannot respond to Amf3GppAccessRegistration or SdmSubscription, then the response failure code "404" is returned. If the UDM completes the response to Amf3GppAccessRegistration but does not complete the response to SdmSubscription, that is, completes UE registration based on Amf3GppAccessRegistration but does not complete subscription of data based on SdmSubscription, then the response incomplete code "501" is returned.

[0346] The request method provided in this application embodiment sends a Get message to obtain contract data, carrying multiple request parameters in the message header. Multiple requests from NF can be sent to UDM through a single message, which reduces the number of messages sent and improves the processing performance between interfaces.

[0347] Optionally, the request parameters in the first request packet are located in the body of the first request packet.

[0348] Specifically, at least two of the following can be achieved through a POST request: requesting user registration, requesting to obtain contract information, and requesting target contract subscription. That is, the request parameters in the first request packet can be set in the body of the first request packet.

[0349] Specifically, such as Figure 6 As shown, taking the establishment of a session between UDM and NF via Post messages as an example, the detailed process is shown in steps 600-620 below.

[0350] Step 600.NF sends a POST message to UDM to retrieve subscription data. The body of the POST message may contain relevant request parameters.

[0351] Specifically, the NF sends a POST… / {supi} / am-data message to the UDM, where the parameter can be: Amf3GppAccessRegistration+SdmSubscription.

[0352] Specifically, when the first request packet is used to request registration, the request parameters include the Amf3GppAccessRegistration parameter; or

[0353] If the first request packet is used to request a subscription to data services, the request parameters include SdmSubscription-related parameters; or

[0354] In the case where the first request packet is used to request registration and to request a subscription to data, the request parameters include the Amf3GppAccessRegistration parameter and the SdmSubscription parameter for requesting a subscription to data.

[0355] Step 610. Respond to the request.

[0356] Specifically, when the request parameters include the Amf3GppAccessRegistration parameter, the NF can register the UE while waiting for the UDM to obtain the subscription information based on the SUPI.

[0357] Specifically, when the request parameters include SdmSubscription related parameters, UDM can obtain the subscription information based on SUPI and store the relevant parameter information of the subscription resource in the local database to complete the subscription of the target subscription data;

[0358] The relevant parameters for subscribing to resources may include: the ID of the subscribed resource and the NotifyUri.

[0359] Specifically, when the request parameters include the Amf3GppAccessRegistration parameter and the SdmSubscription related parameters, the UDM can obtain the subscription information based on SUPI, register the UE, store the relevant parameter information of the subscription resources in the local database, complete the subscription of the target subscription data, and generate a subscription ID.

[0360] The SdmSubscription parameter can be carried in the message body as a JSON string.

[0361] Step 620. UDM reports the response execution status to NF.

[0362] Specifically, after the UDM responds to the request parameters in the request message sent by the NF, the UDM sends feedback on the response execution status to the NF. The feedback on the response execution status sent to the NF may include any one of the following steps 521-523:

[0363] Step 621. If UDM has completed the response to all requested parameters, it will return a response completion code "200"; or

[0364] Step 622. If UDM is unable to respond to any of the request parameters, it will return a failure code "404"; or

[0365] Step 623. If UDM only completes the response for part of the request parameters, it will return the incomplete response code "501".

[0366] Upon completion of the response, the feedback data may include: contract data and subscription information.

[0367] For example, the request parameters of the request message sent by the NF include Amf3GppAccessRegistration and SdmSubscription. If the UDM completes the response to Amf3GppAccessRegistration and SdmSubscription, that is, completes UE registration based on Amf3GppAccessRegistration and completes subscription data subscription based on SdmSubscription, then the response completion code "200" is returned. If the UDM cannot respond to Amf3GppAccessRegistration or SdmSubscription, then the response failure code "404" is returned. If the UDM completes the response to Amf3GppAccessRegistration but does not complete the response to SdmSubscription, that is, completes UE registration based on Amf3GppAccessRegistration but does not complete subscription data subscription based on SdmSubscription, then the response incomplete code "501" is returned.

[0368] The request method provided in this application embodiment sends a Post message to obtain contract data, carrying multiple request parameters in the message body. Multiple request messages from NF can be sent to UDM through a single message, which reduces the number of messages sent and improves the processing performance between interfaces.

[0369] Optionally, when the first request packet is used to request user registration and request to obtain contract information, the feedback information includes contract information corresponding to the contract permanent identifier SUPI.

[0370] Specifically, Figure 10 This is the seventh flowchart illustrating the request method provided in the embodiments of this application, such as... Figure 10 As shown, the detailed process is as follows, steps 1000-1020.

[0371] Step 1000.NF sends a message to UDM requesting to obtain the subscription data, with the message carrying the Amf3GppAccessRegistration parameter.

[0372] The message can be sent using either a GET message or a POST message.

[0373] Step 1010.NF waits for UDM to respond to the request.

[0374] Specifically, UDM can register UEs while obtaining subscription information from SUPI.

[0375] Step 1020.NF receives feedback information from UDM.

[0376] Specifically, the feedback information received by NF includes: subscription information, such as network slicing information, etc.

[0377] The request method provided in this application embodiment allows the NF to complete the original registration and contract data acquisition by exchanging only one pair of messages with the UDM in a single business process, thereby reducing the number of interactions and improving the processing performance between interfaces.

[0378] Optionally, when the first request packet is used to request user registration, request to obtain contract information, and request a target subscription, the feedback information includes contract information corresponding to the permanent contract identifier SUPI, and subscription ID corresponding to the target subscription parameter in the first request packet.

[0379] Specifically, Figure 11 This is the eighth flowchart illustrating the request method provided in this application embodiment, as shown below. Figure 11 As shown, the detailed process is as follows, steps 1100-1120.

[0380] Step 1100.NF sends a message to UDM requesting to obtain subscription data, carrying the Amf3GppAccessRegistration parameter and SdmSubscription related parameters.

[0381] The message can be sent using either a GET message or a POST message.

[0382] Step 1110.NF waits for UDM to respond to the request.

[0383] Specifically, while the UDM can obtain subscription information based on the SUPI, it can also register the UE, store the relevant parameter information of the subscription resources in the local database, complete the subscription of the target subscription data, and generate a subscription ID.

[0384] Step 1120.NF receives feedback information from UDM.

[0385] Specifically, the feedback information received by the NF includes: subscription information, such as network slicing information; and target subscription information, such as subscription duration. The subscription ID received by the NF can be stored in a local database for use in subsequent interactions.

[0386] The request method provided in this application embodiment allows the NF to complete the original registration and subscription data acquisition in a single business process by exchanging only one pair of messages with the UDM. This reduces the number of interactions and improves the processing performance between interfaces. Furthermore, by receiving the subscription ID, the internal processing flow is improved, making it easier to receive notifications when subscription information changes, thus optimizing the processing performance within the network element.

[0387] The request method provided in this application embodiment can reduce the number of requests between network elements by sending a first request packet for at least two of the following requests: requesting user registration, requesting to obtain contract information, and requesting target contract subscription. This can reduce the number of message interactions between network elements and improve the interface processing performance between network elements.

[0388] This application provides a request method and apparatus for completing multiple functions by exchanging a single message under multiple business requirements, reducing the number of interactions and improving the processing performance between interfaces. The method and apparatus are based on the same application concept. Since the methods and apparatus solve problems in similar principles, their implementations can be mutually referenced, and repeated details will not be elaborated further.

[0389] Figure 12 This is a schematic diagram of the structure of the UDM provided in the embodiments of this application, as shown below. Figure 12 As shown, the UDM includes a memory 1220, a transceiver 1200, and a processor 1210.

[0390] Wherein: memory 1220 is used to store computer programs; transceiver 1200 is used to send and receive data under the control of processor 1210; processor 1210 is used to read the computer program in memory 1220 and perform the following operations:

[0391] Receive a first request packet sent by a network function entity (NF), the first request packet being used to request user registration, request to obtain subscription information, and request target subscription;

[0392] In response to the first request packet, generate feedback information for the first request packet;

[0393] Send feedback information to NF.

[0394] Specifically, transceiver 1200 is used to receive and send data under the control of processor 1210.

[0395] The UDM provided in this application embodiment can reduce the number of requests between network elements by receiving a first request packet for at least two of the following requests: requesting user registration, requesting to obtain subscription information, and requesting target subscription. This can reduce the number of message interactions between network elements and improve the interface processing performance between network elements.

[0396] Among them, Figure 12 In this context, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits together, represented by one or more processors (processor 1210) and memory (memory 1220). The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 1200 may be multiple elements, including transmitters and receivers, providing units for communicating with various other devices over transmission media, including wireless channels, wired channels, optical fibers, etc. The processor 1210 is responsible for managing the bus architecture and general processing, and the memory 1220 may store data used by the processor 1210 during operation.

[0397] The processor 1210 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor can also adopt a multi-core architecture.

[0398] Optionally, the request parameters in the first request packet are located in the header of the first request packet.

[0399] Optionally, the request parameters in the first request packet are located in the body of the first request packet.

[0400] Optionally, the processor 1210 is also configured to read the computer program in the memory 1220 and perform the following operations:

[0401] If the first request packet is used at least to request user registration and request to obtain contract information, the user registration request parameters used to request user registration in the first request packet are parsed, the user registration request parameters are stored in the local database, and user registration is completed.

[0402] Determine whether the first request packet contains a target subscription request parameter used to request the target subscription;

[0403] If it is determined that the first request packet does not carry the target subscription request parameters, then the subscription information is obtained based on the subscription permanent identifier SUPI, and feedback information is generated based on the subscription information;

[0404] If it is determined that the first request packet carries the target subscription request parameter, the target subscription request parameter is stored in the local database, a target subscription ID is generated, and after obtaining the subscription information based on SUPI, feedback information is generated based on the target subscription ID and the subscription information.

[0405] The UDM provided in this application embodiment can reduce the number of requests between network elements by receiving a first request packet for at least two of the following requests: requesting user registration, requesting to obtain subscription information, and requesting target subscription. This can reduce the number of message interactions between network elements and improve the interface processing performance between network elements.

[0406] It should be noted that the UDM provided in this application embodiment can implement all the method steps implemented by the method embodiment with UDM as the execution subject, and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0407] Figure 13 This is a schematic diagram of the structure of the NF provided in the embodiments of this application, such as... Figure 13 As shown, NF includes a memory 1320, a transceiver 1300, and a processor 1310.

[0408] Wherein: memory 1320 is used to store computer programs; transceiver 1300 is used to send and receive data under the control of processor 1310; processor 1310 is used to read the computer program in memory 1320 and perform the following operations:

[0409] Send a first request packet to the Unified Data Management Entity (UDM). The first request packet is used to request at least two of the following: requesting user registration, requesting to obtain contract information, and requesting a target subscription.

[0410] Receive feedback information sent by UDM in response to the first request packet. The feedback information is generated by UDM in response to the first request packet.

[0411] Specifically, transceiver 1300 is used to receive and send data under the control of processor 1310.

[0412] The NF provided in this application embodiment can reduce the number of requests between network elements by sending a first request packet for at least two of the following requests: requesting user registration, requesting to obtain subscription information, and requesting target subscription. This can reduce the number of message interactions between network elements and improve the interface processing performance between network elements.

[0413] Among them, Figure 13In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 1310 and memory represented by memory 1320 together. The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 1300 can be multiple components, including transmitters and receivers, providing a unit for communicating with various other devices over a transmission medium, including wireless channels, wired channels, optical fibers, etc. For different user equipment, the user interface 1330 can also be an interface capable of connecting external or internal devices, including but not limited to keypads, displays, speakers, microphones, joysticks, etc.

[0414] The processor 1310 is responsible for managing the bus architecture and general processing, and the memory 1320 can store the data used by the processor 1310 when performing operations.

[0415] Optionally, the processor 1310 may be a CPU (Central Processing Unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a CPLD (Complex Programmable Logic Device), and the processor may also adopt a multi-core architecture.

[0416] The processor executes any of the methods provided in the embodiments of this application by calling a computer program stored in memory, according to the obtained executable instructions. The processor and memory may also be physically separated.

[0417] Optionally, the request parameters in the first request packet are located in the header of the first request packet.

[0418] Optionally, the request parameters in the first request packet are located in the body of the first request packet.

[0419] Optionally, the processor 1310 is also configured to read a computer program from the memory 1320 and perform the following operations:

[0420] When the first request packet is used to request user registration and request to obtain contract information, the feedback information includes contract information corresponding to the contract permanent identifier SUPI.

[0421] Optionally, the processor 1310 is also configured to read a computer program from the memory 1320 and perform the following operations:

[0422] When the first request packet is used to request user registration, request to obtain contract information, and request a target contract subscription, the feedback information includes contract information corresponding to the contract permanent identifier SUPI, and subscription ID corresponding to the target contract subscription parameter in the first request packet.

[0423] The NF provided in this application embodiment can reduce the number of requests between network elements by sending a first request packet for at least two of the following requests: requesting user registration, requesting to obtain subscription information, and requesting target subscription. This can reduce the number of message interactions between network elements and improve the interface processing performance between network elements.

[0424] It should be noted that the NF provided in this embodiment of the invention can implement all the method steps implemented by the method embodiment with NF as the execution subject, and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0425] Figure 14 This is one of the structural schematic diagrams of the request device provided in the embodiments of this application, such as... Figure 14 As shown, the requesting device includes: a first receiving unit 1400, a response unit 1401, and a first sending unit 1402.

[0426] Wherein: the first receiving unit 1400 is used to receive a first request packet sent by the network function entity NF, the first request packet is used to request user registration, request to obtain subscription information and request target subscription;

[0427] The response unit 1401 is used to respond to the first request packet and generate feedback information for the first request packet;

[0428] The first sending unit 1402 is used to send feedback information to NF.

[0429] Specifically, the requesting device can receive a first request packet sent by a network function entity (NF) through a first receiving unit 1400, wherein the first request packet is used to request user registration, request to obtain subscription information, and request target subscription; then, in response to the first request packet, the response unit 1401 can generate feedback information for the first request packet; then, the feedback information can be sent to the NF through a first sending unit 1402.

[0430] The request device provided in this application embodiment can reduce the number of requests between network elements by receiving a first request packet for at least two of the following requests: requesting user registration, requesting to obtain contract information, and requesting target contract subscription. This can reduce the number of message interactions between network elements and improve the interface processing performance between network elements.

[0431] Optionally, the request parameters in the first request packet are located in the header of the first request packet.

[0432] Optionally, the request parameters in the first request packet are located in the body of the first request packet.

[0433] Optionally, the response unit 1401 is also used for:

[0434] If the first request packet is used at least to request user registration and request to obtain contract information, the user registration request parameters used to request user registration in the first request packet are parsed, the user registration request parameters are stored in the local database, and user registration is completed.

[0435] Determine whether the first request packet contains a target subscription request parameter used to request the target subscription;

[0436] If it is determined that the first request packet does not carry the target subscription request parameters, then the subscription information is obtained based on the subscription permanent identifier SUPI, and feedback information is generated based on the subscription information;

[0437] If it is determined that the first request packet carries the target subscription request parameter, the target subscription request parameter is stored in the local database, a target subscription ID is generated, and after obtaining the subscription information based on SUPI, feedback information is generated based on the target subscription ID and the subscription information.

[0438] It should be noted that the request device provided in this embodiment of the invention can implement all the method steps implemented by the method embodiment with UDM as the execution subject, and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0439] Figure 15 This is a second schematic diagram of the structure of the request device provided in the embodiments of this application, as shown below. Figure 15 As shown, the requesting device includes: a second sending unit 1500 and a second receiving unit 1501.

[0440] Wherein: the second sending unit 1500 is used to send a first request packet to the unified data management entity UDM. The first request packet is used to request user registration, request to obtain subscription information, and request target subscription.

[0441] The second receiving unit 1501 is used to receive feedback information sent by UDM in response to the first request packet. The feedback information is generated by UDM in response to the first request packet.

[0442] Specifically, the requesting device can send a first request packet to the Unified Data Management Entity (UDM) through the second sending unit 1500. The first request packet is used to request at least two of the following: requesting user registration, requesting to obtain subscription information, and requesting a target subscription. Subsequently, the second receiving unit 1501 receives feedback information sent by the UDM in response to the first request packet. The feedback information is generated by the UDM in response to the first request packet.

[0443] The request device provided in this application embodiment can reduce the number of requests between network elements by sending a first request packet for at least two of the following requests: requesting user registration, requesting to obtain contract information, and requesting target contract subscription. This can reduce the number of message interactions between network elements and improve the interface processing performance between network elements.

[0444] Optionally, the request parameters in the first request packet are located in the header of the first request packet.

[0445] Optionally, the request parameters in the first request packet are located in the body of the first request packet.

[0446] Optionally, the second receiving unit 1501 is further configured to:

[0447] In the case where the first request packet is used to request user registration and request to obtain contract information, feedback information corresponding to the contract permanent identifier SUPI is received.

[0448] Optionally, the second receiving unit 1501 is further configured to:

[0449] When the first request packet is used to request user registration and request to obtain subscription information, feedback information is received, including subscription information corresponding to the subscription permanent identifier SUPI and subscription ID corresponding to the target subscription parameter in the first request packet.

[0450] It should be noted that the request device provided in this embodiment of the invention can implement all the method steps implemented by the method embodiment with NF as the execution subject, and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0451] It should be noted that the division of units in the embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[0452] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0453] On the other hand, embodiments of this application also provide a processor-readable storage medium storing a computer program for causing a processor to execute the methods provided in the above embodiments, including:

[0454] Receive a first request packet sent by a network function entity (NF), the first request packet being used to request user registration, request to obtain subscription information, and request target subscription;

[0455] In response to the first request packet, generate feedback information for the first request packet;

[0456] Send feedback information to NF.

[0457] On the other hand, embodiments of this application also provide a processor-readable storage medium storing a computer program for causing a processor to execute the methods provided in the above embodiments, including:

[0458] Send a first request packet to the Unified Data Management Entity (UDM). The first request packet is used to request at least two of the following: requesting user registration, requesting to obtain contract information, and requesting a target subscription.

[0459] Receive feedback information sent by UDM in response to the first request packet. The feedback information is generated by UDM in response to the first request packet.

[0460] Processor-readable storage media can be any available medium or data storage device that the processor can access, including but not limited to magnetic storage (e.g., floppy disks, hard disks, magnetic tapes, magneto-optical disks (MOs), etc.), optical storage (e.g., CDs, DVDs, BDs, HVDs, etc.), and semiconductor storage (e.g., ROMs, EPROMs, EEPROMs, non-volatile memory (NAND flash), solid-state drives (SSDs)).

[0461] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage and optical storage) containing computer-usable program code.

[0462] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0463] These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0464] These processors can execute instructions that can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable device for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0465] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A request method, characterized in that, Applied to a unified data management entity (UDM), the method includes: The system receives a first request packet sent by a Network Function Entity (NF). The first request packet is used to request user registration and request to obtain subscription information, and carries user registration request parameters; or, it is used to request user registration, request to obtain subscription information, and request target subscription, and carries user registration request parameters and target subscription request parameters. In response to the first request packet, generate feedback information for the first request packet; Send the feedback information to the NF; The registration and subscription process can be performed simultaneously with the acquisition of contract data, or the acquisition of contract data and subscription process can be performed simultaneously with the registration process. If the subscription process is not required in the business, the GET message method can be used, with multiple request parameters in the message header; if the subscription process is required in the business process, the POST message method can be used, with multiple request parameters in the message body. When the first request packet is used at least to request user registration and to request access to contract information, the step of generating feedback information in response to the first request packet includes: Parse the user registration request parameters in the first request packet used to request user registration, store the user registration request parameters in the local database, and complete the user registration; Determine whether the first request packet carries a target subscription request parameter for requesting the target subscription; If it is determined that the first request packet does not carry the target subscription request parameter, then the subscription information is obtained based on the subscription permanent identifier SUPI, and the feedback information is generated based on the subscription information; If it is determined that the first request packet carries the target subscription request parameter, then the target subscription request parameter is stored in the local database, a target subscription ID is generated, and after obtaining the subscription information based on SUPI, the feedback information is generated based on the target subscription ID and the subscription information.

2. The request method according to claim 1, characterized in that, The request parameters in the first request packet are located in the header of the first request packet.

3. The request method according to claim 1, characterized in that, The request parameters in the first request packet are located in the body of the first request packet.

4. A request method, characterized in that, Applied to NF, the method includes: Send a first request packet to the Unified Data Management Entity (UDM). The first request packet is used to request user registration and request to obtain contract information, and carries user registration request parameters; or, it is used to request user registration, request to obtain contract information and request target contract subscription, and carries user registration request parameters and target contract subscription request parameters. Receive feedback information sent by the UDM in response to the first request packet, wherein the feedback information is generated by the UDM in response to the first request packet; The registration and subscription process can be performed simultaneously with the acquisition of contract data, or the acquisition of contract data and subscription process can be performed simultaneously with the registration process. If the subscription process is not required in the business, the GET message method can be used, with multiple request parameters in the message header; if the subscription process is required in the business process, the POST message method can be used, with multiple request parameters in the message body. When the first request packet is used to request user registration and request to obtain contract information, the feedback information includes contract information corresponding to the contract permanent identifier SUPI; When the first request packet is used to request user registration, request to obtain contract information, and request a target contract subscription, the feedback information includes contract information corresponding to the contract permanent identifier SUPI, and subscription ID corresponding to the target contract subscription parameter in the first request packet.

5. The request method according to claim 4, characterized in that, The request parameters in the first request packet are located in the header of the first request packet.

6. The request method according to claim 4, characterized in that, The request parameters in the first request packet are located in the body of the first request packet.

7. A UDM, comprising a memory, a transceiver, and a processor; characterized in that, A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations: Receive a first request packet sent by a network function entity (NF). The first request packet is used to request user registration and request to obtain subscription information, and carries user registration request parameters. Alternatively, it can be used to request user registration, request to obtain contract information, and request target contract subscription, carrying user registration request parameters and target contract subscription request parameters; In response to the first request packet, generate feedback information for the first request packet; Send the feedback information to the NF; The registration and subscription process can be performed simultaneously with the acquisition of contract data, or the acquisition of contract data and subscription process can be performed simultaneously with the registration process. If the subscription process is not required in the business, the GET message method can be used, with multiple request parameters in the message header; if the subscription process is required in the business process, the POST message method can be used, with multiple request parameters in the message body. When the first request packet is used at least to request user registration and to request access to contract information, the step of generating feedback information in response to the first request packet includes: Parse the user registration request parameters in the first request packet used to request user registration, store the user registration request parameters in the local database, and complete the user registration; Determine whether the first request packet carries a target subscription request parameter for requesting the target subscription; If it is determined that the first request packet does not carry the target subscription request parameter, then the subscription information is obtained based on the subscription permanent identifier SUPI, and the feedback information is generated based on the subscription information; If it is determined that the first request packet carries the target subscription request parameter, then the target subscription request parameter is stored in the local database, a target subscription ID is generated, and after obtaining the subscription information based on SUPI, the feedback information is generated based on the target subscription ID and the subscription information.

8. The UDM according to claim 7, characterized in that, The request parameters in the first request packet are located in the header of the first request packet.

9. The UDM according to claim 7, characterized in that, The request parameters in the first request packet are located in the body of the first request packet.

10. An NF (Network Function), comprising a memory, a transceiver, and a processor; characterized in that, A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations: Send a first request packet to the Unified Data Management Entity (UDM). The first request packet is used to request user registration and request to obtain contract information, and carries user registration request parameters; or, it is used to request user registration, request to obtain contract information and request target contract subscription, and carries user registration request parameters and target contract subscription request parameters. Receive feedback information sent by the UDM in response to the first request packet, wherein the feedback information is generated by the UDM in response to the first request packet; The registration and subscription process can be performed simultaneously with the acquisition of contract data, or the acquisition of contract data and subscription process can be performed simultaneously with the registration process. If the subscription process is not required in the business, the GET message method can be used, with multiple request parameters in the message header; if the subscription process is required in the business process, the POST message method can be used, with multiple request parameters in the message body. When the first request packet is used to request user registration and request to obtain contract information, the feedback information includes contract information corresponding to the contract permanent identifier SUPI; When the first request packet is used to request user registration, request to obtain contract information, and request a target contract subscription, the feedback information includes contract information corresponding to the contract permanent identifier SUPI, and subscription ID corresponding to the target contract subscription parameter in the first request packet.

11. The NF according to claim 10, characterized in that, The request parameters in the first request packet are located in the header of the first request packet.

12. The NF according to claim 10, characterized in that, The request parameters in the first request packet are located in the body of the first request packet.

13. A requesting device, characterized in that, include: The first receiving unit is used to receive a first request packet sent by a network function entity (NF). The first request packet is used to request user registration and request to obtain subscription information, and carries user registration request parameters. Alternatively, it can be used to request user registration, request to obtain contract information, and request target contract subscription, carrying user registration request parameters and target contract subscription request parameters; A response unit is used to generate feedback information for the first request packet in response to the first request packet; The first sending unit is used to send the feedback information to the NF; The registration and subscription process can be performed simultaneously with the acquisition of contract data, or the acquisition of contract data and subscription process can be performed simultaneously with the registration process. If the subscription process is not required in the business, the GET message method can be used, with multiple request parameters in the message header; if the subscription process is required in the business process, the POST message method can be used, with multiple request parameters in the message body. When the first request packet is used at least to request user registration and to request access to contract information, the step of generating feedback information in response to the first request packet includes: Parse the user registration request parameters in the first request packet used to request user registration, store the user registration request parameters in the local database, and complete the user registration; Determine whether the first request packet carries a target subscription request parameter for requesting the target subscription; If it is determined that the first request packet does not carry the target subscription request parameter, then the subscription information is obtained based on the subscription permanent identifier SUPI, and the feedback information is generated based on the subscription information; If it is determined that the first request packet carries the target subscription request parameter, then the target subscription request parameter is stored in the local database, a target subscription ID is generated, and after obtaining the subscription information based on SUPI, the feedback information is generated based on the target subscription ID and the subscription information.

14. A requesting device, characterized in that, include: The second sending unit is used to send a first request packet to the unified data management entity UDM. The first request packet is used to request user registration and request to obtain contract information, and carries user registration request parameters. Alternatively, it can be used to request user registration, request to obtain contract information, and request target contract subscription, carrying user registration request parameters and target contract subscription request parameters; The second receiving unit is configured to receive feedback information sent by the UDM in response to the first request packet, wherein the feedback information is generated by the UDM in response to the first request packet. The registration and subscription process can be performed simultaneously with the acquisition of contract data, or the acquisition of contract data and subscription process can be performed simultaneously with the registration process. If the subscription process is not required in the business, the GET message method can be used, with multiple request parameters in the message header; if the subscription process is required in the business process, the POST message method can be used, with multiple request parameters in the message body. When the first request packet is used to request user registration and request to obtain contract information, the feedback information includes contract information corresponding to the contract permanent identifier SUPI; When the first request packet is used to request user registration, request to obtain contract information, and request a target contract subscription, the feedback information includes contract information corresponding to the contract permanent identifier SUPI, and subscription ID corresponding to the target contract subscription parameter in the first request packet.

15. A processor-readable storage medium, characterized in that, The processor-readable storage medium stores a computer program that causes the processor to perform the method according to any one of claims 1 to 3, or to perform the method according to any one of claims 4 to 6.

Images