Method and system for implementing group service capability subscription
Patent Information
- Application Number
- CN202210498039.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-05-09
- Publication Date
- 2026-10-13
- Estimated Expiration
- 2042-05-09
AI Technical Summary
如果把所有的业务签约都集中在UDM上,势必会对UDM存储后台进行频繁的读写操作,对其他业务造成较大的影响
[0025]本公开实施例中,在5GC网络中增加GMCF模块,通过NRF实体、UDM实体发现GMCF模块,用户在GMCF模块上完成业务能力的签约,减少了对UDM实体存储后台的频繁读写操作,增强了运营商和企业客户对业务群组的管控能力。
Smart Images

Figure CN117082484B_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the field of wireless communications, and more particularly to a method and system for implementing group service capability subscription. Background Technology
[0002] 3GPP Release 16 defines new features for 5G LAN (Local Area Network). Operators provide 5G LAN services to vertical industries, such as the Industrial Internet, enterprise offices, and home environments, similar to local area networks or VPN (Virtual Private Network) services. Customers can customize 5G LAN communication groups according to their actual needs. Within these groups, UEs (User Equipment) can communicate with each other via point-to-point or point-to-multipoint communication, including Ethernet and IP communication.
[0003] In the current R16 / R17 5G LAN standards, industry customers dynamically subscribe to 5G VN (Virtual Network) groups through AF (Application Function) / NEF (Network Exposure Function) in UDM (Unified Data Management), or operators statically subscribe to 5G VN (Virtual Network) groups in UDM according to customer needs. When a UE establishes a session, the subscription information is sent from UDM to SMF (Session Management Function) to generate UPF (User Plane Function) forwarding rules, thereby providing the forwarding function of VN group data packets within the campus.
[0004] Currently, based solely on the UDM contract information, operators can only provide data plane forwarding for 5G LAN services, but cannot effectively manage 5G LAN services in real time, such as the number of users in the VN group and the service area.
[0005] As a network capability for industry applications, 5G LAN can be offered to customers for customized subscriptions. At the same time, operators also need to conduct billing, management, and control based on customers' customized needs. If all service contracts are centralized on the UDM (User Device Manager), it will inevitably lead to frequent read and write operations on the UDM storage backend, significantly impacting other services. Summary of the Invention
[0006] One of the technical problems this disclosure aims to solve is to provide a method and system for implementing group service capability subscription, which can reduce frequent read and write operations on the backend of UDM entity storage and enhance the control capabilities of operators and enterprise customers over service groups.
[0007] According to one aspect of this disclosure, a method for implementing group service capability subscription is proposed, comprising: a Network Storage Function (NRF) entity, which determines the corresponding Group Control Function (GMCF) module based on request information from a first Unified Data Management (UDM) entity, and sends relevant information of the GMCF module to the first UDM entity; the first UDM entity, which sends relevant information of the GMCF module to an Application Function (AF) entity or a Network Open Function (NEF) entity; and the GMCF module, which receives user subscription information through the AF entity or the NEF entity.
[0008] In some embodiments, the NRF entity determines the corresponding GMCF module by matching the corresponding GMCF module based on the group information carried in the request information.
[0009] In some embodiments, if an NRF entity finds a GMCF module that has been allocated to a second UDM entity based on group information, it sends the address of the GMCF module to the first UDM entity, wherein the subscription data configured by the first UDM entity and the second UDM entity belongs to the same group.
[0010] In some embodiments, if the NRF entity does not find an assigned GMCF module based on the group information, it selects an available GMCF module and sends the address of the GMCF module to the first UDM entity.
[0011] In some embodiments, group information includes slice information and data network information.
[0012] In some embodiments, the GMCF module registers with the NRF entity through a service-oriented interface.
[0013] In some embodiments, the GMCF module controls the user's services based on the user's subscription information.
[0014] In some embodiments, user subscription information includes the service attribute information that the user has subscribed to.
[0015] According to another aspect of this disclosure, a system for implementing group service capability subscription is also proposed, comprising: a Network Storage Function (NRF) entity configured to determine the corresponding Group Control Function (GMCF) module based on request information from a first Unified Data Management (UDM) entity, and send relevant information of the GMCF module to the first UDM entity; the first UDM entity configured to send relevant information of the GMCF module to an Application Function (AF) entity or a Network Open Function (NEF) entity; and the GMCF module configured to receive user subscription information through the AF entity or the NEF entity.
[0016] In some embodiments, an NRF entity is configured to match the corresponding GMCF module based on the group information carried in the request information.
[0017] In some embodiments, an NRF entity is configured to send the address of a GMCF module to a first UDM entity if a GMCF module already allocated to a second UDM entity is found based on group information, wherein the subscription data configured by the first UDM entity and the second UDM entity belongs to the same group.
[0018] In some embodiments, the NRF entity is configured to select an available GMCF module and send the address of the GMCF module to the first UDM entity if no assigned GMCF module is found based on the group information.
[0019] In some embodiments, group information includes slice information and data network information.
[0020] In some embodiments, the GMCF module is configured to register with an NRF entity via a service-oriented interface.
[0021] In some embodiments, the GMCF module is configured to control a user's services based on the user's subscription information.
[0022] In some embodiments, user subscription information includes the service attribute information that the user has subscribed to.
[0023] According to another aspect of this disclosure, an electronic device is also proposed, comprising: a memory; and a processor coupled to the memory, the processor being configured to execute, based on instructions stored in the memory, a method for implementing group service capability subscription as described above.
[0024] According to another aspect of this disclosure, a non-transitory computer-readable storage medium is also proposed, on which computer program instructions are stored, which, when executed by a processor, implement the method for implementing group service capability subscription as described above.
[0025] In this embodiment of the disclosure, a GMCF module is added to the 5GC network. The GMCF module is discovered through NRF entities and UDM entities. Users complete the subscription of service capabilities on the GMCF module, which reduces the frequent read and write operations on the UDM entity storage backend and enhances the operator's and enterprise customers' control over service groups.
[0026] Other features and advantages of this disclosure will become clear from the following detailed description of exemplary embodiments with reference to the accompanying drawings. Attached Figure Description
[0027] The accompanying drawings, which form part of this specification, illustrate embodiments of this disclosure and, together with the specification, serve to explain the principles of this disclosure.
[0028] This disclosure will become clearer with reference to the accompanying drawings and the following detailed description, wherein:
[0029] Figure 1 A flowchart illustrating some embodiments of the method for implementing group service capability subscription in this disclosure;
[0030] Figure 2 The following are schematic flowcharts illustrating other embodiments of the method for implementing group service capability subscriptions disclosed herein;
[0031] Figure 3 This is a schematic diagram of the structure of some embodiments of the system for implementing group service capability subscriptions disclosed herein; and
[0032] Figure 4 This is a schematic diagram of the structure of some embodiments of the electronic device disclosed herein. Detailed Implementation
[0033] Various exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. It should be noted that, unless otherwise specifically stated, the relative arrangement, numerical expressions, and values of the components and steps set forth in these embodiments do not limit the scope of the present disclosure.
[0034] At the same time, it should be understood that, for ease of description, the dimensions of the various parts shown in the accompanying drawings are not drawn according to actual scale.
[0035] The following description of at least one exemplary embodiment is merely illustrative and is in no way intended to limit this disclosure or its application or use.
[0036] Techniques, methods, and equipment known to those skilled in the art may not be discussed in detail, but where appropriate, such techniques, methods, and equipment should be considered part of the specification.
[0037] In all examples shown and discussed herein, any specific values should be interpreted as merely exemplary and not as limitations. Therefore, other examples of exemplary embodiments may have different values.
[0038] It should be noted that similar labels and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be discussed further in subsequent figures.
[0039] To make the objectives, technical solutions, and advantages of this disclosure clearer, the following detailed description is provided in conjunction with specific embodiments and the accompanying drawings.
[0040] Figure 1 This is a flowchart illustrating some embodiments of the method for implementing group service capability subscriptions disclosed herein.
[0041] In step 110, the NRF (NF Repository Function) entity determines the corresponding GMCF (Group Management Control Function) module based on the request information from the first UDM entity, and sends the relevant information of the GMCF module to the first UDM entity.
[0042] In some embodiments, the 5GC network provides industry customers with a channel for subscribing to group service capabilities through a GMCF module. This GMCF module can be a new functional module added to an existing standard network element, or it can be a newly added network element.
[0043] In some embodiments, the GMCF module registers with the 5GC NRF entity via a service-oriented interface.
[0044] In some embodiments, the NRF entity matches the corresponding GMCF module based on the group information carried in the request information. This request information may include, for example, slice information and data network information.
[0045] In some embodiments, the relevant information of the GMCF module is the address information of the GMCF module.
[0046] In step 120, the first UDM entity sends the relevant information of the GMCF module to the AF entity or the NEF entity.
[0047] In step 130, the GMCF module receives user subscription information through the AF entity or NEF entity.
[0048] In this step, the user signs up for the business attribute information in the GMCF module through the AF entity or NEF entity.
[0049] In some embodiments, user subscription information includes service attribute information that the user has subscribed to. For example, the maximum number of subscribers and their location region.
[0050] In some embodiments, during the business process, the GMCF module manages and controls the business based on the business capability attributes.
[0051] In the above embodiments, a GMCF module is added to the 5GC network. The GMCF module is discovered through NRF entities and UDM entities. Users complete the subscription of service capabilities on the GMCF module, which reduces the frequent read and write operations on the UDM entity storage backend and enhances the operator's and enterprise customers' control over service groups.
[0052] Figure 2 This is a flowchart illustrating some other embodiments of the method for implementing group service capability subscription according to this disclosure. In this embodiment, a GMCF module is deployed in the 5GC network. The GMCF module can be an independent functional module or it can be co-located with other functional modules.
[0053] In step 210, the GMCF module sends a registration request to the NRF entity.
[0054] In some embodiments, after GMCF goes online, it registers with the NRF in the 5GC network through the Nnrf interface service interface. For example, the GMCF module sends an Nnrf_NFManagement_NFRegister_request to the NRF entity, where the registration request includes the GMCF module's configuration information, such as location areas according to network deployment requirements.
[0055] In step 220, the NRF entity saves the configuration information of the GMCF module.
[0056] In step 230, the NRF entity sends a registration response to the GMCF module. For example, the NRF entity sends an Nnrf_NFManagement_NFRegister_response to the GMCF module.
[0057] In step 240, the industry customer signs up for the VN group on the UDM entity through the AF / NEF entity.
[0058] In some embodiments, the basic information of a VN group includes the VN group identifier, group members, group data, etc., wherein the group data includes slices, DNN (Data Network Name), etc.
[0059] In step 250, after the UDM entity completes the signing, it requests the discovery of the GMCF module based on the slice information and data network information. For example, the GMCF module can be discovered based on the slice identifier or the DNN identifier.
[0060] In some embodiments, if an NRF entity matches multiple GMCF modules, it selects one of them. For example, it selects the most matching GMCF module based on the GMCF module's location information, such as selecting the GMCF module closest to the terminal.
[0061] In some embodiments, if an NRF entity finds a GMCF module that has been allocated to a second UDM entity based on group information, it sends the address of the GMCF module to the first UDM entity, wherein the subscription data configured by the first UDM entity and the second UDM entity belongs to the same group.
[0062] For example, a VN group can be distributed across multiple UDM entities, but the information related to the VN group is expected to be stored in a single GMCF module. If the NRF entity discovers, based on the request information from the first UDN entity, that a GMCF module has already been allocated to a VN group of another UDM entity, it will directly return the discovered GMCF module to the first UDM entity.
[0063] In some embodiments, if the NRF entity cannot find an assigned GMCF module based on group information, it selects an available GMCF module. For example, it selects an available GMCF module based on carrier policy and sends the address of the GMCF module to the first UDM entity.
[0064] For example, if the NRF entity does not find an assigned GMCF module based on the request information from the UDM entity, it can select a default registered GMCF module, or send the request information to a higher-level NRF entity for round-robin selection to find a suitable GMCF module. This NRF entity annotates the relationship between the GMCF module, slice, and DNN.
[0065] In step 260, the NRF entity sends the address of the GMCF module to the UDM entity.
[0066] In step 270, the UDM entity sends the address of the GMCF module to the AF / NEF entity.
[0067] In step 280, industry clients directly subscribe to more detailed personalized business capability attributes on the GMCF module through the AF / NEF entity. For example, they can subscribe to information such as the maximum number of users and location regions on the GMCF module.
[0068] In step 290, during the business process, the GMCF module manages and controls the business based on the business capability attributes.
[0069] In the above embodiments, by adding a GMCF module to the 5GC network, industry customers discover the GMCF module through NRF entities and subscribe to group service capabilities through the 5G network service-oriented working mode. The GMCF module controls services based on subscription attributes, enhancing the management and control capabilities of operators and enterprise customers over 5G LAN service groups and expanding the multi-dimensional billing capabilities of industry applications. Operators can utilize this GMCF module to provide more granular control over private networks, offering enterprise customers the option to select and subscribe, enabling unified or flexible group management of various services.
[0070] Figure 3 This is a schematic diagram of the structure of some embodiments of a system for implementing group service capability subscriptions disclosed herein, the system including NRF entity 310, first UDM entity 320 and GMCF module 330.
[0071] NRF entity 310 is configured to determine the corresponding GMCF module based on the request information from the first UDM entity, and send the relevant information of the GMCF module to the first UDM entity.
[0072] In some embodiments, the GMCF module registers with the 5GC NRF entity via a service-oriented interface.
[0073] In some embodiments, NRF entity 310 is configured to match the corresponding GMCF module based on group information carried in the request information. This request information may be, for example, slice information and data network information.
[0074] In some embodiments, NRF entity 310 is configured to send the address of the GMCF module to the first UDM entity if a GMCF module already allocated to the second UDM entity is found based on group information, wherein the subscription data configured by the first UDM entity and the second UDM entity belongs to the same group.
[0075] In some embodiments, NRF entity 310 is configured to select an available GMCF module if no assigned GMCF module is found based on group information, for example, by selecting an available GMCF module based on carrier policy, and send the address of the GMCF module to the first UDM entity.
[0076] In some embodiments, NRF entity 310 is configured to select one of multiple GMCF modules if multiple GMCF modules are matched. For example, the most matching GMCF module is selected based on its location information. For example, the GMCF module closest to the terminal is selected.
[0077] The first UDM entity 320 is configured to send relevant information of the GMCF module to the AF entity or NEF entity 340.
[0078] GMCF module 330 is configured to receive user subscription information via an AF entity or a NEF entity. This includes information such as the maximum number of users a user can subscribe to on the GMCF module and their location region.
[0079] In some embodiments, during the business process, the GMCF module 330 is configured to control the user's business based on the user's subscription information.
[0080] In the above embodiments, a GMCF module is added to the 5GC network. The GMCF module is discovered through NRF entities and UDM entities. Users complete the subscription of service capabilities on the GMCF module, which reduces the frequent read and write operations on the UDM entity storage backend and enhances the operator's and enterprise customers' control over service groups.
[0081] Figure 4 This is a schematic diagram illustrating the structure of some embodiments of the electronic device disclosed herein. When performing the functions of an NRF entity, the electronic device is located within the NRF entity; when performing the functions of a UDM entity, it is located within the UDM entity; and when performing the functions of a GMCF module, it is located within the GMCF module. The electronic module 400 includes a memory 410 and a processor 420. The memory 410 can be a disk, flash memory, or any other non-volatile storage medium. The memory is used to store instructions in the above embodiments. The processor 420 is coupled to the memory 410 and can be implemented as one or more integrated circuits, such as a microprocessor or microcontroller. The processor 420 is used to execute the instructions stored in the memory.
[0082] In some embodiments, the processor 420 is coupled to the memory 410 via a BUS bus 430. The module 400 can also be connected to an external storage system 450 via a storage interface 440 to access external data, and can also be connected to a network or another computer system (not shown) via a network interface 460. Further details are omitted here.
[0083] In this embodiment, by storing data instructions in a memory and then processing the instructions by a processor, it is possible to sign up for group service capabilities through the 5G network service-oriented working mode, thereby enhancing the operator's and enterprise customers' control over service groups and expanding the multi-dimensional billing capabilities of industry applications.
[0084] In other embodiments, a computer-readable storage medium stores computer program instructions that, when executed by a processor, implement the steps of the methods described above. Those skilled in the art will understand that embodiments of this disclosure can be provided as methods, apparatus, or computer program products. Therefore, this disclosure can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this disclosure can take the form of a computer program product embodied on one or more computer-usable non-transitory storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0085] This disclosure is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this disclosure. 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 program instructions. These computer program 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, create a machine for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.
[0086] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium 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.
[0087] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment 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.
[0088] This concludes the detailed description of the present disclosure. To avoid obscuring the concept of the disclosure, some details known in the art have not been described. Those skilled in the art will fully understand how to implement the technical solutions disclosed herein based on the above description.
[0089] While specific embodiments of this disclosure have been described in detail by way of example, those skilled in the art should understand that the examples are for illustrative purposes only and not intended to limit the scope of this disclosure. Those skilled in the art should understand that modifications can be made to the above embodiments without departing from the scope and spirit of this disclosure. The scope of this disclosure is defined by the appended claims.
Claims
1. A method for implementing group service capability signing, comprising: The Network Storage Function (NRF) entity determines the corresponding Group Control Function (GMCF) module based on the request information from the first Unified Data Management (UDM) entity, and sends the relevant information of the GMCF module to the first UDM entity. The first UDM entity sends the relevant information of the GMCF module to the Application Function (AF) entity or the Network Open Function (NEF) entity, wherein the GMCF module receives user subscription information through the AF entity or the NEF entity.
2. The method according to claim 1, wherein, The NRF entity determines the corresponding GMCF module, including: The NRF entity matches the corresponding GMCF module based on the group information carried in the request information.
3. The method according to claim 2, wherein, If the NRF entity finds a GMCF module that has been allocated to the second UDM entity based on the group information, it sends the address of the GMCF module to the first UDM entity, wherein the subscription data configured by the first UDM entity and the second UDM entity belongs to the same group.
4. The method according to claim 2, wherein, If the NRF entity does not find an assigned GMCF module based on the group information, it selects an available GMCF module and sends the address of the GMCF module to the first UDM entity.
5. The method according to claim 2, wherein, The group information includes slice information and data network information.
6. The method according to any one of claims 1 to 5, wherein, The GMCF module registers with the NRF entity through a service-oriented interface.
7. The method according to any one of claims 1 to 5, further comprising: The GMCF module controls the user's services based on the user's subscription information.
8. The method according to any one of claims 1 to 5, wherein, The user contract information includes the service attribute information of the user's contract.
9. A system for implementing group service capability subscription, comprising: The Network Storage Function (NRF) entity is configured to determine the corresponding Group Control Function (GMCF) module based on the request information from the first Unified Data Management (UDM) entity, and send the relevant information of the GMCF module to the first UDM entity. The first UDM entity is configured to send relevant information of the GMCF module to the Application Function (AF) entity or the Network Open Function (NEF) entity. as well as The GMCF module is configured to receive user subscription information through the AF entity or NEF entity.
10. The system according to claim 9, wherein, The NRF entity is configured to match the corresponding GMCF module based on the group information carried in the request information.
11. The system according to claim 10, wherein, The NRF entity is configured to send the address of the GMCF module to the first UDM entity if it finds a GMCF module that has been allocated to the second UDM entity based on the group information, wherein the subscription data configured by the first UDM entity and the second UDM entity belongs to the same group.
12. The system according to claim 10, wherein, The NRF entity is configured to select an available GMCF module and send the address of the GMCF module to the first UDM entity if no assigned GMCF module is found based on the group information.
13. The system according to any one of claims 10 to 12, wherein, The group information includes slice information and data network information.
14. The system according to any one of claims 9 to 12, wherein, The GMCF module is configured to register with the NRF entity through a service interface.
15. The system according to any one of claims 9 to 12, wherein, The GMCF module is configured to control the user's services based on the user's subscription information.
16. The system according to any one of claims 9 to 12, wherein, The user contract information includes the service attribute information of the user's contract.
17. An electronic device comprising: Memory; as well as A processor coupled to the memory, the processor being configured to execute, based on instructions stored in the memory, the method for implementing group service capability subscription as described in any one of claims 1 to 8.
18. A non-transitory computer-readable storage medium having stored thereon computer program instructions that, when executed by a processor, implement the method for implementing group service capability subscription as described in any one of claims 1 to 8.
Citation Information
Patent Citations
Group management method, device and system
CN111901132A
AF influenced PDU session management and subscription procedures
US20180270778A1