Data processing methods, apparatus, electronic devices and computer-readable storage media

By introducing a unified binding function network element backend to store binding information in the mobile network system, the problems of low query efficiency and signaling bandwidth waste caused by multiple binding support function network elements being independent are solved, achieving efficient query and resource saving.

CN116419201BActive Publication Date: 2026-11-17CHINA TELECOM CORP LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202111671710.3
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-12-31
Publication Date
2026-11-17
Estimated Expiration
2041-12-31

AI Technical Summary

Technical Problem

In mobile network systems, the independent operation of multiple binding support function network elements leads to problems such as low query efficiency and wasted signaling bandwidth.

Method used

A unified binding function network element backend is adopted to store and manage the binding information of multiple binding function network element frontends. The binding information can be accessed through a single binding function network element frontend, avoiding traversing or subscribing to multiple network elements.

Benefits of technology

It improved query efficiency, saved broadband resources, and reduced signaling bandwidth waste.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116419201B_ABST
    Figure CN116419201B_ABST
Patent Text Reader

Abstract

This disclosure provides a data processing method, system, electronic device, and readable storage medium. A target mobile network includes a first binding function network element front-end, a second binding function network element front-end, and a binding function network element back-end. The method includes: the first binding function network element front-end receiving a target query request for a target user from a first target function network element, the target query request being used to query the address of a second target function network element that has a target binding relationship with the target user, wherein the second target function network element and the target user are bound through the second binding function network element front-end, and the first binding function network element front-end and the second binding function network element front-end are different; the first binding function network element front-end sending the target query request to the binding function network element back-end; and the binding function network element back-end determining the target address of the second target function network element that has a target binding relationship with the target user based on the target query request.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a data processing method and apparatus, electronic device and computer-readable storage medium. Background Technology

[0002] In related technologies, mobile network systems may have multiple binding support function network elements, each independent of the others. Therefore, when querying the function network element corresponding to a user under a certain binding relationship, it may be necessary to traverse and subscribe to all binding support function network elements of the target network system, which may lead to problems such as low query efficiency and wasted signaling bandwidth.

[0003] It should be noted that the information disclosed in the above background section is only used to enhance the understanding of the background of this disclosure. Summary of the Invention

[0004] The purpose of this disclosure is to provide a data processing method, apparatus, electronic device, and computer-readable storage medium that can improve query efficiency and save broadband resources.

[0005] Other features and advantages of this disclosure will become apparent from the following detailed description, or may be learned in part from practice of this disclosure.

[0006] This disclosure provides a data processing method, comprising: a first binding function network element front-end receiving a target query request for a target user from a first target function network element, the target query request being used to query the address of a second target function network element that has a target binding relationship with the target user, wherein the second target function network element is bound to the target user through the second binding function network element front-end, and the first binding function network element front-end is different from the second binding function network element front-end; the first binding function network element front-end sending the target query request to the binding function network element back-end; and the binding function network element back-end determining the target address of the second target function network element that has a target binding relationship with the target user based on the target query request.

[0007] In some embodiments, the first target function network element is a target access and mobility management policy control function network element that provides policies for the access and mobility management of the target user, and the second target function network element is a target session policy control function network element that provides policies for the session of the target user. The target binding relationship is a session management binding relationship. The first binding function network element front-end receives a target query request for the target user from the first target function network element. The target query request is used to query the address of the second target function network element that has a target binding relationship with the target user. The second target function network element is bound to the target user through the second binding function network element front-end. The first binding function network element front-end differs from the second binding function network element front-end and includes: the first binding function... The network element front-end receives a target query request for a target user from the target access and mobility management policy control function network element. The target query request is used to query the address of a target session policy control function network element that has a session management binding relationship with the target user. The target session policy control function network element is bound to the target user through a second binding function network element front-end, and the first binding function network element front-end is different from the second binding function network element front-end. The binding function network element back-end determines the target address of the second target function network element that has a target binding relationship with the target user based on the target query request, including: the binding function network element back-end determines the address of the target session policy control function network element that provides a policy for the target user's session based on the target query request.

[0008] In some embodiments, the target query request carries the target user identifier of the target user; wherein, the binding function network element backend determines the address of the target session policy control function network element that provides policies for the target user's session based on the target query request, including: the address of the target session policy control function network element that provides policies for the target user's session based on the target user identifier.

[0009] In some embodiments, the target mobile network includes multiple access and mobility management policy control function (AMAC) network elements; wherein, before the first binding function network element front-end receives a target query request for a target user from the target AMAC network element, the method further includes: a registration phase, wherein the target user determines the target AMAC network element from the multiple AMAC network elements so as to provide access and mobility management policies for the target user through the target AMAC network element; the first binding function network element front-end binds the target user's target user identifier with the target AMAC network element to generate first binding information; the first binding function network element front-end sends the first binding information to the binding function network element back-end so that the binding function network element back-end associates and stores the first binding information with the target user identifier.

[0010] In some embodiments, the target mobile network includes multiple session policy control function network elements; wherein, before the first binding function network element front-end receives a target query request for a target user from the target access and mobility management policy control function network element, the method further includes: a session establishment phase, wherein the target user determines the target session policy control function network element from among the multiple session policy control function network elements, so as to provide a session policy for the target user through the target session policy control function network element; the second binding function network element front-end binds the user identifier of the target user with the target session policy control function network element to generate second binding information; the second binding function network element front-end sends the second binding information to the binding function network element back-end, so that the binding function network element associates and stores the second binding information with the target user identifier.

[0011] In some embodiments, the method further includes: the target access and mobility management policy control function network element receiving the address of the target session policy control function network element from the front end of the first binding function network element; based on the address of the target session policy control function network element, the target access and mobility management policy control function network element subscribing to the target session policy control function network element for session information of the target user in the target application; and executing the target policy according to the session information of the target user in the target application.

[0012] This disclosure also provides a target mobile network system, which includes multiple binding function network element front-ends and a binding function network element back-end. The multiple binding function network element front-ends include a first binding function network element front-end and a second binding function network element front-end. A target user binds to a first target function network element through the first binding function network element front-end. The first binding function network element front-end is configured to receive a target query request for the target user from the first target function network element. The target query request is used to query the address of a second target function network element that has a target binding relationship with the target user. The second target function network element is bound to the target user through the second binding function network element front-end. The first binding function network element front-end and the second binding function network element front-end are different. The target query request is then sent to the binding function network element back-end. The binding function network element back-end is configured to determine the target address of the second target function network element that has a target binding relationship with the target user based on the target query request.

[0013] This disclosure provides an electronic device comprising: one or more processors; and a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the data processing method described above.

[0014] This disclosure provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the data processing method as described in any of the preceding embodiments.

[0015] This disclosure provides a computer program product or computer program that includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the data processing method described above.

[0016] The data processing method, system, electronic device, and computer-readable storage medium provided in this disclosure can provide different binding services to users through different binding function network element front-ends, and provide storage services to all binding function network element front-ends through a unified binding function network element back-end. Thus, when a user has a query requirement, regardless of which binding function network element front-end is accessed, the query result can be obtained by pointing to the binding function network element back-end. Through the above method, when querying binding information, the query result can be obtained through any binding function network element front-end, without traversing or subscribing to multiple binding function network elements, improving query efficiency and reducing bandwidth resources.

[0017] It should be understood that the above general description and the following detailed description are merely exemplary and do not limit this disclosure. Attached Figure Description

[0018] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure. It is obvious that the drawings described below are merely some embodiments of this disclosure, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0019] Figure 1 This is a flowchart illustrating a data processing method according to an exemplary embodiment.

[0020] Figure 2 This is a flowchart illustrating a data processing method according to an exemplary embodiment.

[0021] Figure 3 This is a data processing method illustrated according to an exemplary embodiment.

[0022] Figures 4-5 This is a timing diagram illustrating a data processing method according to an exemplary embodiment.

[0023] Figure 6 A schematic diagram of the structure of an electronic device suitable for implementing embodiments of the present disclosure is shown. Detailed Implementation

[0024] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the embodiments set forth herein; rather, they are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the exemplary embodiments to those skilled in the art. The same reference numerals in the drawings denote the same or similar parts, and therefore repeated descriptions of them will be omitted.

[0025] The features, structures, or characteristics described in this disclosure can be combined in any suitable manner in one or more embodiments. Numerous specific details are provided in the following description to give a thorough understanding of embodiments of this disclosure. However, those skilled in the art will recognize that the technical solutions of this disclosure can be practiced with one or more specific details omitted, or other methods, components, apparatuses, steps, etc., can be employed. In other instances, well-known methods, apparatuses, implementations, or operations are not shown or described in detail to avoid obscuring various aspects of this disclosure.

[0026] The accompanying drawings are merely illustrative of this disclosure, and the same reference numerals in the drawings denote the same or similar parts, thus omitting repeated descriptions of them. Some block diagrams shown in the drawings do not necessarily correspond to physically or logically independent entities. These functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0027] The flowchart shown in the accompanying drawings is merely illustrative and does not necessarily include all content and steps, nor does it require execution in the described order. For example, some steps may be broken down, while others may be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0028] In this specification, the terms “a,” “an,” “the,” “at least one” are used to indicate the presence of one or more elements / components / etc.; the terms “include,” “include,” and “have” are used to indicate an open-ended inclusion and to mean that there may be other elements / components / etc. in addition to the listed elements / components / etc.; the terms “first,” “second,” and “third,” etc., are used only as markings and are not a limitation on the number of objects.

[0029] To better understand the above-mentioned objectives, features and advantages of the present invention, the present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be noted that, unless otherwise specified, the embodiments and features in the embodiments of this application can be combined with each other.

[0030] Before introducing this disclosure, the names involved in this disclosure may be explained.

[0031] PCF: Policy Control Function (PCF)

[0032] AMF: Access and Mobility Management Function.

[0033] AM: Access and Mobility Management

[0034] SMF: Session Management function, network element for session management.

[0035] SM: Session Management, a network element for session management functions.

[0036] UPF: User plane function

[0037] NRF: Network Repository Function

[0038] AM-PCF: Policy control function network element used to provide policies for access and mobility management.

[0039] SM-PCF: Policy control function network element used to provide policies for session management.

[0040] BSF: Binding Support Function, which binds to network elements with supporting functions.

[0041] DNN: datanetworkname, the name of the data network.

[0042] S-NSSAI: Single Network Slice Selection Assistance Information, a parameter in network slicing.

[0043] SUPI: Subscription Permanent Identifier, User Permanent Identifier

[0044] GPSI: Generic Public Subscription Identifier

[0045] MAC address: Media Access Control Address

[0046] IP address: Internet Protocol Address

[0047] NEF: Network Exposure Function

[0048] UDR: Unified Data Repository, a unified data repository function

[0049] 3GPP: 3rd Generation Partnership Project

[0050] AF: Application Function

[0051] Figure 1This is a flowchart illustrating a data processing method according to an exemplary embodiment.

[0052] In some embodiments, the target mobile network may include multiple binding function network element front-ends and a binding function network element back-end, wherein the binding function network element front-end can be used to provide binding services, such as session binding, registration binding, etc. (similar to the binding function services of the binding function network element BSF). This disclosure does not limit which binding services the binding function network element front-end specifically provides.

[0053] In some embodiments, the binding function network element backend can be used to provide storage services for the aforementioned multiple binding function network element frontends, that is, the binding information formed through the aforementioned multiple binding function network element frontends can be stored in the binding function network element backend.

[0054] In some embodiments, the aforementioned plurality of binding function network element front-ends may include a first binding function network element front-end and a second binding function network element front-end, wherein the target user may have already bound to a first target function network element through the first binding function network element front-end.

[0055] The first target functional network element can refer to any functional network element in the target mobile network. This first target functional network element can be a policy control function network element (PCF), a session management function network element (SMF), a user plane function network element (UPF), a network storage function network element (NRF), etc., and this disclosure does not impose any restrictions. For example, the first target functional network element can be a policy control function network element (AM-PCF) used to provide access and mobility management policies for the target user, or a policy control function network element used to provide session management policies for the target user, etc.

[0056] Reference Figure 1 The data processing method provided in this disclosure may include the following steps.

[0057] In step S102, the first binding function network element front-end receives a target query request for the target user from the first target function network element. The target query request is used to query the address of the second target function network element that has a target binding relationship with the target user. The second target function network element and the target user are bound through the second binding function network element front-end. The first binding function network element front-end and the second binding function network element front-end are different.

[0058] The target binding relationship can refer to a session binding relationship, a registration binding relationship, etc., and this disclosure does not limit it.

[0059] In some embodiments, the binding operation between a target user and different network elements may be implemented through different binding function network element front-ends. For example, the binding of a target user with an access and mobility management policy control function network element during registration may be implemented through a first binding function network element front-end, and the binding of a target user with a session management policy control function network element during session construction may be implemented through a second binding function network element front-end.

[0060] The front-end of the first bound function network element and the front-end of the second bound function network element can be different.

[0061] The second target function network element can refer to any function network element in the target mobile network. The second target function network element can be a policy control function network element (PCF), a session management function network element (SMF), a user plane function network element (UPF), a network storage function network element (NRF), etc. This disclosure does not limit it.

[0062] Step S104: The front end of the first bound function element sends the target query request to the back end of the bound function element.

[0063] Step S106: The binding function network element backend determines the target address of the second target function network element that has a target binding relationship with the target user based on the target query request.

[0064] The technical solution provided in the above embodiments allows for the access of the binding function network element backend, which uniformly stores binding information, to the frontend of a binding function network element when querying the address of the corresponding functional network element of a target user under the target binding relationship. This improves query efficiency and saves bandwidth resources.

[0065] In Release 17 (a protocol version), 3GPP proposed a scenario where the Application Filter (AF) influences a user's Application Mode (AM) policy. Due to the needs of the target application, the AF may request the AM-PCF to modify the target user's policy in that application (e.g., modifying service coverage or user throughput). The AM-PCF needs to subscribe to the SM-PCF to detect the traffic information of the target application in that application (e.g., the start and end of relevant traffic) in order to execute the modified AM policy.

[0066] Based on the above scenario, the AM-PCF needs to quickly locate the SM-PCF responsible for session management of the target application through the BSF. However, the AM-PCF and SM-PCF corresponding to the target user in the network may be registered under different BSFs, and there may be multiple SM-PCFs and multiple BSF network element instances. Therefore, the AM-PCF needs to first query all BSF instance information from the NRF, and then select one or more BSFs that meet the conditions to subscribe to based on the DNN and S-NSSAI supported by the BSF to obtain the address of the SM-PCF. When multiple BSFs in the network support the same DNN and S-NSSAI, the AM-PCF needs to subscribe to multiple BSFs, resulting in inefficiency and wasted signaling bandwidth.

[0067] To address the issue that an AM-PCF may need to subscribe to multiple BSFs to obtain the SM-PCF address, this patent proposes a binding data management method that simplifies the process of an AM-PCF locating its SM-PCF. Each AM-PCF only needs to send a request to the front end of one bound management function network element to obtain the SM-PCF addresses for all sessions. Consumer network elements of other BSFs can also use this method to query binding relationship-related information.

[0068] Figure 2 This is a flowchart illustrating a data processing method according to an exemplary embodiment.

[0069] In this embodiment, the target mobile network may include multiple binding function network element front-ends and one binding function network element back-end. The binding function network element front-end can be used to provide binding services, such as session binding, registration binding, etc. (similar to the binding function services of the original binding function network element BSF). This disclosure does not limit which binding services the binding function network element front-end specifically provides.

[0070] In some embodiments, the binding function network element backend is used to provide storage services for the aforementioned multiple binding function network element frontends, that is, the binding information formed through the aforementioned multiple binding function network element frontends can all be stored in the binding function network element backend.

[0071] In some embodiments, the first target function network element may be a target access and mobility management policy control function network element that provides policies for the access and mobility management of the target user, the second target function network element may be a target session policy control function network element that provides policies for the session of the target user, and the target binding relationship may be a session management binding relationship.

[0072] In some embodiments, the target mobile network may include multiple Access and Mobility Management Policy Control Function (AM-PCF) network elements. The target user can then register and bind via the following method: During the registration phase, the target user identifies a target AM-PCF network element from among the multiple AM-PCF network elements, so that the target AM-PCF network element can provide access and mobility management policies to the target user; the front end of the first binding function network element binds the target user's target user identifier with the target AM-PCF network element to generate first binding information; the front end of the first binding function network element sends the first binding information to the back end of the binding function network element, so that the back end of the binding function network element associates and stores the first binding information with the target user identifier.

[0073] In some embodiments, the target mobile network may include multiple Session Policy Control Function (SM-PCF) network elements. Then, the target user can perform session binding using the following method: During the session establishment phase, the target user determines a target SM-PCF network element from among the multiple SM-PCF network elements, so that the target SM-PCF network element provides a session policy to the target user; the second binding function network element front-end binds the target user's user identifier with the target SM-PCF network element to generate second binding information; the second binding function network element front-end sends the second binding information to the binding function network element back-end, so that the binding function network element associates and stores the second binding information with the target user identifier.

[0074] refer to Figure 2 The above data processing method may include the following steps.

[0075] In step S202, the first binding function network element front-end receives a target query request for the target user from the target access and mobility management policy control function network element. The target query request is used to query the address of the target session policy control function network element that has a session management binding relationship with the target user. The target session policy control function network element and the target user are bound through the second binding function network element front-end. The first binding function network element front-end and the second binding function network element front-end are different.

[0076] Step S204: The front end of the first bound function network element sends the target query request to the back end of the bound function network element.

[0077] Step S206: The binding function network element backend determines the address of the target session policy control function network element that provides policies for the target user's session based on the target query request.

[0078] The target query request can carry the target user's identifier. Then, the backend of the binding function network element can determine the address of the target session policy control function network element that provides policies for the target user's session based on the target user identifier.

[0079] In some embodiments, after the binding function network element backend obtains the address of the target session policy control function network element, it returns the address of the target session policy control function network element to the first binding function network element frontend, and then returns it to the target access and mobility management control function network element.

[0080] In some embodiments, after the target access and mobility management policy control function network element receives the address of the target session policy control function network element from the front end of the first binding function network element, it will subscribe to the target user's session information in the target application based on the address of the target session policy control function network element; so as to execute the target policy according to the target user's session information in the target application.

[0081] Figure 3 This is a data processing method illustrated according to an exemplary embodiment.

[0082] Figure 3 The illustrated embodiment addresses the problem of AM-PCF's inability to quickly obtain SM-PCF addresses in a network topology with multiple BSFs. It proposes a novel binding management function network element architecture, consisting of multiple front-ends and a unified back-end. The front-ends are responsible for receiving and processing service requests, while the back-end stores information related to the binding relationship between PCFs and users / sessions. The functions implemented by this network element include:

[0083] 1. Binding Information: Registration / Modification / Deletion (Taking Registration as an Example)

[0084] (1) The user completes the registration normally and selects an AM-PCF to register with the front end of the binding management function network element; the front end of the binding management function network element sends the binding information (SUPI, AM-PCF) to the unified back end for storage. After receiving the binding information, the back end replies to the front end with a binding identifier, and the front end replies to the AM-PCF.

[0085] (2) The user establishes a session and selects an SM-PCF to register with the front end of the binding management function network element. The input information includes the user's (IP / MAC address, DNN, S-NSSAI, SM-PCF) identification information, etc. The front end of the binding management function network element sends the binding input information to the unified back end for storage. After receiving the binding information, the back end replies to the front end with a binding identifier, which is then replied to the SM-PCF by the front end.

[0086] 2. Binding Information Inquiry

[0087] (1) AM-PCF queries the front end of the binding management function network element for the address of SM-PCF; the front end of the binding management function network element queries the unified back end for the address of SM-PCF and returns the result to AM-PCF.

[0088] (2) SM-PCF queries the AM-PCF address from the front end of the binding management function network element; the front end of the binding management function network element queries the AM-PCF address from the unified back end and returns the result to SM-PCF.

[0089] This method can avoid PCF subscribing to multiple BSF network elements and achieve unified management of session binding related data, enabling AM-PCF and SM-PCF to discover each other more efficiently, while reducing the burden on network elements and network links.

[0090] refer to Figure 3 The above method may include the following steps:

[0091] 1. The user completes the normal registration process and selects an AM-PCF to establish coupling between mobility management and access control policies. Then, the user registers via the binding management function network element front-end. The parameters mainly include the user's SUPI / GPSI and the AM-PCF identifier. The front-end sends the data to a unified back-end for storage and returns a binding identifier.

[0092] 2. The user initiates the normal session establishment process, selects an SM-PCF to establish the coupling of session-related policies, and then registers the binding through the binding management function network element front-end. Key parameters include the DNN, S-NSSAI, and SM-PCF identifiers. The front-end sends the data to a unified back-end for storage and returns a binding identifier.

[0093] 3. AF (Application Function) writes AM strategy-related modification requests to UDR (Unified Data Repository) through NEF.

[0094] 4. The UDR notifies the AM-PCF that the parameters related to the AM policy have changed.

[0095] 5. The AM-PCF sends a subscription request to the front-end of the binding management function network element to query the address of the SM-PCF. The main parameters include the user's SUPI / GPSI, DNN, S-NSSAI, etc. The front-end passes these parameters to the back-end for querying.

[0096] 6. The backend of the binding management function network element returns the query results to AM-PCF through the frontend.

[0097] 7. AM-PCF subscribes to SM-PCF, detects the start and stop of relevant application traffic, and makes relevant AM policy decisions.

[0098] The above data processing method can be used Figure 4 and Figure 5 The timing diagram shown will be explained and illustrated in detail.

[0099] Figures 4-5 This is a timing diagram illustrating a data processing method according to an exemplary embodiment.

[0100] 1. The user initiates the normal registration process and selects a PCF to establish AM policy coupling.

[0101] 2. AM-PCF initiates a binding relationship registration request to the front end of the binding management function network element, including parameters such as user SUPI / GPSI and PCF identity identifier.

[0102] 3. Binding Management Function: The network element front-end sends the binding information to a unified back-end for storage.

[0103] 4. The backend returns a binding identifier to the frontend.

[0104] 5. The front end returns an AM-PCF registration success message and a binding identifier.

[0105] 6. AM-PCF sends a subscription message to UDR to subscribe to information related to AM policies in the user's subscription data.

[0106] 7. The user initiates the session establishment process normally and selects a PCF to establish SM policy coupling.

[0107] 8. SM-PCF initiates a binding relationship registration request to the front end of the binding management function network element, and the process is the same as AM-PCF.

[0108] 9. AF writes AM policy-related data into UDR via NEF.

[0109] 10. UDR notifies AM-PCF that the data related to the subscribed AM policy has changed.

[0110] 11. AM-PCF sends a subscription request to the front end of the binding management function network element to query the address of SM-PCF. The parameters include user SUPI / GPSI, DNN, S-NSSAI and other information.

[0111] 12. The front end of the binding management function network element sends the input information of the query to the back end to perform SM-PCF address query.

[0112] 13. The backend will pass the SM-PCF address obtained from the query to the frontend.

[0113] 14. The front end sends the query results to AM-PCF.

[0114] 15. AM-PCF subscribes to SM-PCF to detect the start and stop of business traffic for user-specific applications.

[0115] 16. SM-PCF detects the application's business traffic.

[0116] 17. SM-PCF notifies AM-PCF that the application has started accessing services.

[0117] 18. AM-PCF, combined with the AM policy information written by AF, begins to make decisions on the AM policy.

[0118] Note: The binding management network element front-ends receiving network element registration / subscription / requests in steps 2, 8, and 11 do not need to be the same network element. Data synchronization is performed between the binding management function network element back-ends in the network. That is, a request is sent to any binding management network element front-end in the network.

[0119] In the current network architecture, the AM-PCF needs to obtain the network element registration information of the BSF through the NRF, and subscribe to qualified BSFs through the DNN and S-NSSAI supported by the BSF to obtain the address of the AM-PCF. When multiple BSFs support the same DNN and S-NSSAI, an AM-PCF needs to subscribe to multiple BSFs, resulting in inefficiency and wasted signaling bandwidth.

[0120] The method proposed in this embodiment manages session binding-related data through a unified binding management function network element backend. An AM-PCF only needs to subscribe to any binding management function network element frontend, enabling the AM-PCF to quickly query the address of the SM-PCF.

[0121] The above embodiments can achieve the following beneficial effects:

[0122] 1. The network element functions of BSF are divided into binding management function network element front-end and back-end. The front-end is responsible for signaling interaction with other network elements, and the back-end is responsible for storing the binding information between users / sessions and PCF.

[0123] 2. An AM-PCF only needs to subscribe to one binding management function network element front-end, without having to subscribe to and query multiple BSF network elements. This enables the AM-PCF to obtain the address of the SM-PCF more efficiently, while also reducing signaling messages in the network and avoiding inefficiency and waste of signaling bandwidth.

[0124] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0125] Furthermore, the above figures are merely illustrative of the processes included in the method according to exemplary embodiments of this disclosure and are not intended to be limiting. It is readily understood that the processes shown in the above figures do not indicate or limit the temporal order of these processes. Additionally, it is readily understood that these processes may be executed synchronously or asynchronously, for example, in multiple modules.

[0126] Figure 6 A schematic diagram of the structure of an electronic device suitable for implementing embodiments of the present disclosure is shown. It should be noted that... Figure 6 The electronic device 600 shown is merely an example and should not be construed as limiting the functionality and scope of use of the embodiments disclosed herein.

[0127] like Figure 6 As shown, the electronic device 600 includes a central processing unit (CPU) 601, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage section 608 into a random access memory (RAM) 603. The RAM 603 also stores various programs and data required for the operation of the electronic device 600. The CPU 601, ROM 602, and RAM 603 are interconnected via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0128] The following components are connected to I / O interface 605: an input section 606 including a keyboard, mouse, etc.; an output section 607 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 608 including a hard disk, etc.; and a communication section 609 including a network interface card such as a LAN card, modem, etc. The communication section 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to I / O interface 605 as needed. A removable medium 611, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on drive 610 as needed so that computer programs read from it can be installed into storage section 608 as needed.

[0129] In particular, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a computer-readable storage medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 609, and / or installed from removable medium 611. When the computer program is executed by central processing unit (CPU) 601, it performs the functions defined above in the system of this application.

[0130] It should be noted that the computer-readable storage medium disclosed herein may be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium may be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this application, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable storage medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable storage medium can be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0131] In another aspect, this application also provides a computer-readable storage medium, which may be included in the device described in the above embodiments; or it may exist independently and not assembled into the device. The computer-readable storage medium carries one or more programs, which, when executed by the device, enable the device to perform the following functions: a first binding function network element front-end receives a target query request for a target user from a first target function network element, the target query request being used to query the address of a second target function network element that has a target binding relationship with the target user, wherein the second target function network element is bound to the target user through a second binding function network element front-end, and the first binding function network element front-end is different from the second binding function network element front-end; the first binding function network element front-end sends the target query request to a binding function network element back-end; the binding function network element back-end determines the target address of the second target function network element that has a target binding relationship with the target user based on the target query request.

[0132] According to one aspect of this application, a computer program product or computer program is provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the methods provided in various optional implementations of the above embodiments.

[0133] Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions of the embodiments of this disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) and includes several instructions to cause a computing device (such as a personal computer, server, mobile terminal, or smart device, etc.) to execute the method according to the embodiments of this disclosure, for example... Figure 1 , Figure 2 , Figure 3 , Figure 4 ,or Figure 5 One or more of the steps shown.

[0134] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not claimed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the claims.

[0135] It should be understood that this disclosure is not limited to the detailed structures, drawing arrangements or implementations shown herein; rather, this disclosure is intended to cover various modifications and equivalent arrangements contained within the spirit and scope of the appended claims.

Claims

1. A data processing method, characterized in that, The target mobile network includes multiple binding function network element front-ends and one binding function network element back-end. The multiple binding function network element front-ends include a first binding function network element front-end and a second binding function network element front-end. The target user binds to the first target function network element through the first binding function network element front-end. The method includes: The first binding function network element front end receives a target query request for a target user from the first target function network element. The target query request is used to query the address of a second target function network element that has a target binding relationship with the target user. The second target function network element is bound to the target user through the second binding function network element front end. The first binding function network element front end is different from the second binding function network element front end. The first binding function network element front end sends the target query request to the binding function network element back end; The binding function network element backend determines the target address of the second target function network element that has a target binding relationship with the target user based on the target query request.

2. The method according to claim 1, characterized in that, The first target function network element is a target access and mobility management policy control function network element that provides policies for the access and mobility management of the target user; the second target function network element is a target session policy control function network element that provides policies for the session of the target user; and the target binding relationship is a session management binding relationship. Wherein, the first binding function network element front-end receives a target query request for a target user from the first target function network element. The target query request is used to query the address of a second target function network element that has a target binding relationship with the target user. The second target function network element is bound to the target user through the second binding function network element front-end. The first binding function network element front-end and the second binding function network element front-end are different, including: The first binding function network element front-end receives a target query request for a target user from the target access and mobility management policy control function network element. The target query request is used to query the address of a target session policy control function network element that has a session management binding relationship with the target user. The target session policy control function network element is bound to the target user through the second binding function network element front-end. The first binding function network element front-end and the second binding function network element front-end are different. The binding function network element backend determines the target address of the second target function network element that has a target binding relationship with the target user based on the target query request, including: The binding function network element backend determines the address of the target session policy control function network element that provides policies for the target user's session based on the target query request.

3. The method according to claim 2, characterized in that, The target query request carries the target user identifier of the target user; wherein, the address of the target session policy control function network element that provides policies for the target user's session is determined by the binding function network element backend based on the target query request, including: The backend of the binding function network element determines the address of the target session policy control function network element that provides policies for the target user's session based on the target user identifier.

4. The method according to claim 2, characterized in that, The target mobile network includes multiple access and mobility management policy control function network elements; wherein, before the first binding function network element receives a target query request for the target user from the target access and mobility management policy control function network element, the method further includes: During the registration phase, the target user determines the target access and mobility management policy control function network element from among the multiple access and mobility management policy control function network elements, so as to provide the target user with access and mobility management policies through the target access and mobility management policy control function network element; The first binding function network element front-end binds the target user identifier of the target user with the target access and mobility management policy control function network element to generate first binding information; The first binding function network element front end sends the first binding information to the binding function network element back end, so that the binding function network element back end can associate and store the first binding information with the target user identifier.

5. The method according to claim 2, characterized in that, The target mobile network includes multiple session policy control function network elements; wherein, before the first binding function network element receives a target query request for the target user from the target access and mobility management policy control function network element, the method further includes: During the session establishment phase, the target user determines the target session policy control function network element from among the multiple session policy control function network elements, so as to provide the target user with a session policy through the target session policy control function network element; The second binding function network element front-end binds the user identifier of the target user with the target session policy control function network element to generate second binding information; The second binding function network element front end sends the second binding information to the binding function network element back end, so that the binding function network element associates and stores the second binding information with the target user identifier.

6. The method according to claim 2, characterized in that, The first binding function network element front-end receives a target query request for the target user from the first target function network element, including: The target access and mobility management policy control function network element subscribes to and obtains the target policy requirements for the target application from the application function network element; The target access and mobility management policy control function network element generates target policies for the target application according to the policy requirements; The target access and mobility management policy control function network element sends the target query request to the front end of the first binding function network element to determine the address of the target session policy control function network element that provides policies for the session of the target user.

7. The method according to claim 6, characterized in that, The method further includes: The target access and mobility management policy control function network element receives the address of the target session policy control function network element from the front end of the first binding function network element; Based on the address of the target session policy control function network element, the target access and mobility management policy control function network element subscribes to the target user's session information in the target application from the target session policy control function network element; The target policy is executed based on the target user's session information in the target application.

8. A target mobile network system, characterized in that, The target mobile network system includes multiple binding function network element front-ends and one binding function network element back-end. The multiple binding function network element front-ends include a first binding function network element front-end and a second binding function network element front-end. The target user binds to the first target function network element through the first binding function network element front-end. The first binding function network element front-end is configured to receive a target query request for a target user from the first target function network element. The target query request is used to query the address of a second target function network element that has a target binding relationship with the target user. The second target function network element is bound to the target user through the second binding function network element front-end. The first binding function network element front-end is different from the second binding function network element front-end. The target query request is then sent to the binding function network element back-end. The binding function network element backend is used to determine the target address of the second target function network element that has a target binding relationship with the target user based on the target query request.

9. An electronic device, characterized in that, include: Memory; as well as An electronic device coupled to the memory, the electronic device being used to perform the data processing method as described in any one of claims 1-7 based on instructions stored in the memory.

10. A computer-readable storage medium having a program stored thereon that, when executed by a processor, implements the data processing method as described in any one of claims 1-7.

Citation Information

Patent Citations

  • PCF addressing method, device and system

    CN110324911A

  • Policy control function network element selection method, device and system and storage medium

    CN112312539A