Method, terminal, network device, management server, medium for service management

Abstract

The present disclosure provides a method for service management based on a terminal, comprising: sending identification information to a network device; the identification information comprising an identification of the terminal; receiving service state information sent by the network device; the service state information comprising valid services to which the terminal subscribes; establishing and storing local service information according to the service state information; the local service information comprising the valid services. The present disclosure also provides a terminal, a network device, a management server and a computer readable medium.

Description

Technical Field

[0001] This disclosure relates to the field of business management technology, and in particular to a business management method, terminal, network device, management server, and computer-readable medium. Background Technology

[0002] Terminals in a communication network can subscribe to different services, and in some cases, it is necessary to manage these services by querying and modifying them.

[0003] However, the current business management method is inconvenient, cumbersome and time-consuming, and cannot achieve batch management of a large number of terminals (such as IoT terminals), and is not applicable to some terminals (such as terminals without voice services or without an operating interface). Summary of the Invention

[0004] This disclosure provides a method for business management, a terminal, a network device, a management server, and a computer-readable medium.

[0005] In a first aspect, embodiments of this disclosure provide a service management method based on a terminal, the method comprising:

[0006] Send identification information to the network device; the identification information includes the identifier of the terminal;

[0007] The system receives service status information sent by the network device; the service status information includes valid services subscribed to by the terminal.

[0008] Based on the business status information, local business information is established and stored; the local business information includes the valid business.

[0009] Secondly, embodiments of this disclosure provide a service management method based on a network device, the method comprising:

[0010] The receiver receives identification information sent by the terminal; the identification information includes the identifier of the terminal.

[0011] The valid services subscribed to by the terminal are determined based on the identification information;

[0012] Send service status information to the terminal; the service status information includes the valid service.

[0013] Thirdly, embodiments of this disclosure provide a business management method based on a management server, the method comprising:

[0014] The system receives local service information sent by the terminal via a dedicated connection; the local service information sent by the terminal includes valid services subscribed to by the terminal.

[0015] Record the valid services of the terminal.

[0016] Fourthly, embodiments of this disclosure provide a terminal, which includes a memory and a processor; the memory stores a computer program that can be executed by the processor, and when the computer program is executed by the processor, it implements any of the business management methods of embodiments of this disclosure.

[0017] Fifthly, embodiments of this disclosure provide a network device including a memory and a processor; the memory stores a computer program executable by the processor, and when the computer program is executed by the processor, it implements any of the service management methods of embodiments of this disclosure.

[0018] Sixthly, embodiments of this disclosure provide a management server, which includes a memory and a processor; the memory stores a computer program that can be executed by the processor, and when the computer program is executed by the processor, it implements any of the business management methods of embodiments of this disclosure.

[0019] In a seventh aspect, embodiments of this disclosure provide a computer-readable medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements any of the business management methods of embodiments of this disclosure.

[0020] In this embodiment, a new service management mechanism is adopted between the terminal and the communication network (core network). The terminal directly records the status of valid services (local service information). Therefore, by modifying the local service information, the terminal can notify the network device to modify the status of its services. Furthermore, the management of information within the terminal does not necessarily require going to a service center, contacting service personnel, using a communication network (such as an app or webpage), or using voice services (such as calling customer service). It can be achieved by directly operating the terminal or controlling the terminal using a management server. Thus, the management of services (such as querying and modifying) in this embodiment is convenient and fast, enabling batch management of a large number of terminals (such as IoT terminals), even when the terminals are not connected to the network (communication network unreachable). Moreover, this embodiment does not have requirements regarding the nature of the terminal; terminals with only data services and no voice services or without an operating interface (such as IoT terminals) can also be implemented. Attached Figure Description

[0021] In the accompanying drawings of the embodiments disclosed herein:

[0022] Figure 1 A flowchart illustrating a method for service management of a terminal provided in this disclosure embodiment;

[0023] Figure 2 A flowchart illustrating a method for service management of a network device provided in this disclosure embodiment;

[0024] Figure 3 A flowchart illustrating a method for business management of a management server, provided as an embodiment of this disclosure;

[0025] Figure 4 A block diagram of a terminal provided in an embodiment of this disclosure;

[0026] Figure 5 A block diagram of a network device provided in an embodiment of this disclosure;

[0027] Figure 6 A block diagram illustrating the composition of a management server provided in an embodiment of this disclosure;

[0028] Figure 7 A block diagram illustrating the composition of a computer-readable medium provided in this disclosure embodiment;

[0029] Figure 8 A schematic diagram of the network architecture in another service management method provided in this disclosure embodiment;

[0030] Figure 9 Signaling diagram of process (1) in another business management method provided in this disclosure embodiment;

[0031] Figure 10 Signaling diagram of process (2) in another business management method provided in this embodiment of the disclosure;

[0032] Figure 11 Signaling diagram of process (3) in another business management method provided in this embodiment of the disclosure;

[0033] Figure 12 Signaling diagram of process (4) in another business management method provided in this embodiment of the disclosure;

[0034] Figure 13 Signaling diagram of process (5) in another business management method provided in this disclosure embodiment. Detailed Implementation

[0035] To enable those skilled in the art to better understand the technical solutions of this disclosure, the following detailed description of the service management method, terminal, network device, management server, and computer-readable medium provided in the embodiments of this disclosure is provided in conjunction with the accompanying drawings.

[0036] The present disclosure will be described more fully below with reference to the accompanying drawings; however, the embodiments shown may be embodied in different forms, and the present disclosure should not be construed as limited to the embodiments set forth below. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will enable those skilled in the art to fully understand the scope of the disclosure.

[0037] The accompanying drawings of the embodiments disclosed herein are provided to further illustrate the embodiments of this disclosure and form part of the specification. They are used together with the detailed embodiments to explain this disclosure and do not constitute a limitation thereof. The above and other features and advantages will become more apparent to those skilled in the art from the description of the detailed embodiments with reference to the accompanying drawings.

[0038] This disclosure may be described with reference to plan and / or cross-sectional views using the ideal schematic diagrams of this disclosure. Therefore, the example illustrations may be modified according to manufacturing techniques and / or tolerances.

[0039] Where there is no conflict, the various embodiments of this disclosure and the features thereof in the embodiments may be combined with each other.

[0040] The terminology used in this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the disclosure. The term "and / or" as used in this disclosure includes any and all combinations of one or more of the associated enumerated entries. The singular forms "a" and "the" as used in this disclosure are also intended to include the plural forms, unless the context clearly indicates otherwise. The terms "comprising," "made of," etc., as used in this disclosure specify the presence of the stated feature, integral, step, operation, element, and / or component, but do not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components, and / or groups thereof.

[0041] Unless otherwise specified, all terms used in this disclosure (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art. It will also be understood that terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant art and this disclosure, and will not be interpreted as having an idealized or overly formal meaning, unless expressly so defined in this disclosure.

[0042] This disclosure is not limited to the embodiments shown in the accompanying drawings, but includes modifications to the configuration based on the manufacturing process. Therefore, the areas illustrated in the drawings are schematic, and the shapes of the areas shown illustrate specific shapes of the areas of an element, but are not intended to be limiting.

[0043] With the development of 5G (fifth-generation mobile communication technology) and 6G (sixth-generation mobile communication technology), more and more terminals (such as IoT terminals) can access communication networks (such as 5G networks and 6G networks), and these terminals can sign up for various services within the communication network.

[0044] Therefore, users may need to query, modify, and manage the services they have signed up for on their devices in many situations.

[0045] In some related technologies, users can go to the operator's business hall or contact service personnel, who can then query and modify the signed-up services in the background.

[0046] In other related technologies, users can manage services by operating an app or webpage on the terminal; or they can use the terminal to make a service call and follow the prompts to perform button operations to manage services.

[0047] It is evident that the above business management methods are all inconvenient, especially the methods of going to the business hall or contacting service personnel, which are more cumbersome and time-consuming.

[0048] Moreover, the above business management methods can only manage a "single" terminal; however, with the development of technology, the number of terminals and services has increased dramatically. For example, a user may manage tens or even hundreds of thousands of IoT terminals (such as home appliances, street lights, cameras, electricity meters, water meters, etc.), and there may be tens of thousands of possible services. It is obviously unrealistic to manage so many terminals and services by operating them one by one.

[0049] In addition, some business management methods have specific requirements for terminals and are not applicable to some terminals. For example, if business management is to be carried out by making a service call, the terminal must be able to perform air-to-voice services. If the terminal has only signed up for data services and cannot make calls, it cannot be implemented. Another example is that business management methods that operate on an APP or webpage require the terminal to be able to perform specific operations, which are unusable for terminals without a user interface. However, many terminals, especially IoT terminals such as streetlights, cameras, electricity meters, and water meters, usually do not have voice services or have a user interface.

[0050] Firstly, embodiments of this disclosure provide a service management method based on a terminal.

[0051] The method of this disclosure embodiment is executed by a terminal, which can be any electronic device that can connect to a network device and access a communication network (i.e., a core network, such as a 5G network, a 6G network, etc.), such as a mobile phone, a tablet computer, etc., and especially an Internet of Things terminal, such as a home appliance, a street light, a camera, an electricity meter, a water meter, etc.

[0052] Reference Figure 8 In this embodiment of the disclosure, the terminal accesses the communication network through a network device and can sign up for some services. The method in this embodiment of the disclosure is used to manage the service signing status of the terminal.

[0053] Reference Figure 1 The business management method of this disclosure includes:

[0054] S101. Send identification information to network devices.

[0055] The identification information includes the terminal's identifier.

[0056] S102, Receive service status information sent by network devices.

[0057] The service status information includes valid services signed up for by the terminal.

[0058] S103. Based on the business status information, establish and store local business information.

[0059] Local business information includes valid business transactions.

[0060] In this embodiment of the disclosure, after the terminal connects to the network device (such as when registering with the communication network after powering on), it can add an identifier representing its own identity (such as IMEI) to the identification information (such as a PDU session establishment request message) and send it to the network device; the network device can query the services currently actually subscribed to by the terminal (valid services) based on the terminal's identifier, add the valid services to the service status information (such as a PDU session request acceptance message) and feed it back to the terminal.

[0061] After receiving the service status information, the terminal can parse out its own valid service status, create local service information (such as a service list) that records its own valid services, and store the local service information locally; that is, each terminal records its own valid service status internally.

[0062] It should be understood that the methods of this disclosure may also include other elements.

[0063] For example, the identification information can also be used to establish a request message for a PDU session, which includes other content besides the identification.

[0064] For example, after receiving the identification information, the network device can not only determine the valid service, but also perform other processes to establish a PDU session (including interaction between modules within the network device).

[0065] For example, service status information can also be a PDU session request acceptance message. After receiving this information, in addition to storing local service information, the terminal can also complete other PDU session establishment processes (such as sending a message to the network device to confirm the establishment of the PDU session).

[0066] In this embodiment, a new service management mechanism is adopted between the terminal and the communication network (core network). The terminal directly records the status of valid services (local service information). Therefore, by modifying the local service information, the terminal can notify the network device to modify the status of its services. Furthermore, the management of information within the terminal does not necessarily require going to a service center, contacting service personnel, using a communication network (such as an app or webpage), or using voice services (such as calling customer service). It can be achieved through direct terminal operation or by controlling the terminal using a management server. Thus, the management of services (such as querying and modifying) in this embodiment is convenient and fast, enabling batch management of a large number of terminals (such as IoT terminals), even when the terminals are not connected to the network (communication network unreachable). Moreover, this embodiment does not have requirements regarding the nature of the terminal; terminals with only data services and no voice services or without an operating interface (such as IoT terminals) can also be implemented.

[0067] In some embodiments, the service status information also includes recommended services for the terminal, and the local service information also includes recommended services.

[0068] As one embodiment of this disclosure, the service status information received by the terminal may also include services recommended to the terminal by the network device (recommended services), so that the terminal will also store the recommended services in the local service information (service list).

[0069] In some embodiments, when needed (such as when local business information is created, or when the user performs a certain operation), the terminal may also display recommended services (such as display, voice broadcast, etc.) for the user to choose from.

[0070] In some embodiments, as another way of this disclosure, even if the terminal does not have the function of displaying recommended services (such as when the terminal is a street lamp), it can still store recommended services in local service information. Then, after the terminal sends the local service information to the management server, the recommended services can be displayed on the management server for the user to choose from (detailed explanation follows).

[0071] Therefore, the embodiments of this disclosure can also enable service recommendations, increase the possibility of expanding services, give users more choices, and improve user experience.

[0072] In some embodiments, after establishing and storing local business information (S103), the method further includes:

[0073] S104B1: Receive service change information sent by network devices.

[0074] The business change information includes changes to valid business operations.

[0075] S104B2. Update local business information based on business change information.

[0076] As one embodiment of this disclosure, when a network device detects changes in the status of a terminal's valid services (such as additions, deletions, modifications, or expiration of a valid service), it can add the changes to the valid services to the service change information and send it to the terminal. The terminal can then modify its local service information based on the received service change information (such as deleting the expired valid services) to ensure that the latest valid service status is always recorded in the local service information.

[0077] It should be understood that in some embodiments, the above process can also be triggered if the recommended service changes (such as the launch of a new service). That is, the network device can also add the changes in the recommended service to the service change information, and the terminal will update the recommended service information recorded in the local service information after receiving the service change information.

[0078] In some embodiments, after establishing and storing local business information (S103), the method further includes:

[0079] S104C1, Receive service modification instructions.

[0080] The service modification instruction is used to indicate the modification of valid services in the local service information of the terminal.

[0081] S104C2. Update local business information according to business modification instructions.

[0082] S104C3: Send service modification information to network devices based on the updated local service information.

[0083] The service modification information includes modifications to valid services in the terminal's local service information.

[0084] As one embodiment of this disclosure, the user may also actively send a service modification instruction to the terminal to modify (add, delete, modify, such as adding a recommended service to the valid services) the valid services recorded in the local service information of the terminal; then, the terminal can generate service modification information based on the above modifications and send it to the network device so that the network device can make corresponding modifications (such as subscribing to the above recommended services for the terminal).

[0085] Therefore, in this embodiment of the disclosure, users can directly modify the valid business contracts by operating the terminal, which is convenient and easy to implement.

[0086] Users can modify local business information in various ways; for example, users can operate the terminal directly, or they can control the terminal through a management server (explained later).

[0087] It should be understood that, depending on the terminal's own state when it receives the service modification instruction, the specific way it sends the service modification information to the network device, and the specific way the network device processes the service modification information, can all be different.

[0088] For example, if the terminal is in a connected state when it receives a service modification instruction, it can send a PDU session modification request message to the network device as service modification information, and the network device can obtain the modification of the valid service during the process of modifying the PDU session.

[0089] For example, if the terminal is in an idle state when it receives a service modification instruction, it can send a service request message to the network device as service modification information, and the network device can obtain the modification of the valid service in the service request process.

[0090] In some embodiments, the service status information includes ePCO parameters.

[0091] As one embodiment of this disclosure, the ePCO (extended Protocol Configuration Option) parameter can be used as the service status information for the transmission of valid services.

[0092] Among them, ePCO parameters are usually used to provide additional information for the terminal to connect to the communication network. In this embodiment of the disclosure, parameters that characterize the service status can be added to the ePCO extended parameters. For example, the protocol ID field from FF00H to FFFFH in ePCO can be used to transmit service information. For example, the structure of the service status parameter 0xFF01H can be shown in Table 1 below.

[0093] Table 1. Structure Table of Business Status Parameters

[0094]

[0095] Among them, service name length indicates the length of the service; service name indicates the name of the service; S-NSSAI (Single Network Slice Selection Assistance Information) indication indicates whether slice information is carried; DNN (Data Network Name) indication indicates whether DNN information is carried. If the terminal has multiple slices and DNN access enabled, the DNN indication and S-NSSAI indication flags must be carried. If the terminal has a single DNN or a single slice, the corresponding fields are optional and do not need to be carried. service validity indication indicates the type of service. For example, a value of 0 indicates that the service is a recommended service, and a value of 1 indicates that the service is a valid service.

[0096] It should be understood that in this embodiment of the disclosure, other information about valid services transmitted between the terminal and the network device, such as service change information and service modification information, can also be in the form of ePCO parameters, which will not be described in detail here.

[0097] It should be understood that when using ePCO parameters to transmit services, the specific fields and formats used are not limited to the above forms.

[0098] It should be understood that, in this embodiment of the disclosure, information such as service status information, service change information, and service modification information is not limited to the form of ePCO parameters.

[0099] In some embodiments, after establishing and storing local business information (S103), the method further includes:

[0100] S105A: Sends local business information to the management server through a dedicated connection with the management server.

[0101] And / or,

[0102] S105B receives service modification instructions sent by the management server through a dedicated connection with the management server.

[0103] Among them, the business modification instruction is used to indicate modifications to valid business operations.

[0104] As one embodiment of this disclosure, the terminal can also be managed through a separate "management server".

[0105] Among them, reference Figure 8A management server is a separate server, distinct from network devices (such as the core network). It communicates with multiple subordinate terminals via dedicated connections (such as connections protected by public-private key encryption), enabling direct business management of these terminals without the need for network devices. For example, an enterprise's management server can establish connections with all of the enterprise's IoT terminals and manage their business.

[0106] It should be understood that the above "dedicated connection" refers to a connection other than "the connection between a terminal and a network device in a communication network". However, it does not mean that the dedicated connection cannot pass through the communication network. That is, the dedicated connection can be a direct connection between the management server and the terminal (such as a near-field communication connection) or a connection implemented through the communication network (such as a VPN connection).

[0107] Therefore, after obtaining local service information (including initial establishment and updates), the terminal can send relevant service information to the management server via a dedicated connection, enabling the management server to obtain the latest service status of all its subordinate terminals. Correspondingly, users can also modify the terminal's valid services on the management server, and the management server can send the modifications to the corresponding terminal in the form of service modification commands. The terminal can then update its local service information according to the service modification commands and send the service modification information to the network devices (as in steps S104C1 to S104C3).

[0108] Therefore, in this embodiment of the disclosure, the management server can simultaneously obtain the business information of multiple terminals, thereby enabling the query of massive amounts of business information on the management server, such as querying and filtering based on complex preset conditions; moreover, the management server can also modify the business status of a large number of terminals (such as all terminals filtered by certain conditions) at one time.

[0109] In other words, by establishing a management server, this embodiment of the disclosure can achieve "batch" business management of a massive number of terminals, greatly reducing the workload of business management and significantly increasing the number of manageable terminals.

[0110] Secondly, embodiments of this disclosure provide a service management method based on network devices.

[0111] The method of this disclosure embodiment is executed by a network device that provides communication network (i.e., core network, such as 5G network, 6G network, etc.) services to the terminal and provides the terminal with the services of the services it has subscribed to.

[0112] Reference Figure 8 The network device in this embodiment connects to multiple terminals, and the method in this embodiment is used to manage the subscription status of the terminals.

[0113] Reference Figure 8 The network device in this disclosure may include multiple different modules that work together to provide communication network services.

[0114] Reference Figure 2 The business management method of this disclosure includes:

[0115] S201, Receive identification information sent by the terminal.

[0116] The identification information includes the terminal's identifier.

[0117] S202. Determine the valid services signed up for by the terminal based on the identification information.

[0118] S203. Send service status information to the terminal.

[0119] The business status information includes valid business transactions.

[0120] When a terminal sends out identification information (such as during terminal power-on registration), the network device uses the terminal's identification to query its own records to determine the currently subscribed service (valid service) of the terminal, and adds the valid service to the service status information and sends it to the terminal so that the terminal can establish local service information accordingly.

[0121] In some embodiments, between receiving the identification information sent by the receiving terminal (S201) and sending the service status information to the terminal (S202), the following further step is included:

[0122] S2021. Determine the recommended services for the terminal based on the identification information.

[0123] The business status information also includes recommendation services.

[0124] As one embodiment of this disclosure, the service status information can also determine what services need to be recommended to the terminal based on the terminal's identifier (recommended services), and send the recommended services to the terminal along with the service status information.

[0125] In some embodiments, after sending service status information to the terminal (S203), the method further includes:

[0126] S204A1: In response to changes in the valid services subscribed to by the terminal, send service change information to the terminal.

[0127] The business change information includes changes to valid business operations.

[0128] As one embodiment of this disclosure, when a network device detects a change in the valid services (or recommended services) of a terminal, it can add the corresponding changes to service change information and send it to the terminal so that the terminal can update its local service information.

[0129] In some embodiments, after sending service status information to the terminal (S203), the method further includes:

[0130] S204B1, Receive service modification information sent by the terminal.

[0131] The service modification information includes modifications to valid services in the terminal's local service information.

[0132] S204B1. Valid business that updates records based on business modification information.

[0133] When a terminal modifies its local service information according to a service modification instruction from a user or management server, it sends service modification information indicating the corresponding modification to the network device. The network device then modifies the valid service information of the terminal it has recorded based on the service modification information.

[0134] In some embodiments, the service status information includes ePCO parameters.

[0135] As one embodiment of this disclosure, the above business status information (which may also include business change information, business modification information, etc.) may be in the form of ePCO parameters.

[0136] Thirdly, embodiments of this disclosure provide a business management method based on a management server.

[0137] This disclosure embodiment is executed by a management service, as referred to... Figure 8 The management server communicates with its multiple subordinate terminals through a dedicated connection (such as a connection protected by public and private key encryption) and performs business management on the terminals.

[0138] Reference Figure 3 The business management method of this disclosure includes:

[0139] S301. Receive local service information sent by the terminal through a dedicated connection with the terminal.

[0140] The local service information sent by the terminal includes the valid services subscribed to by the terminal.

[0141] S302, Record the valid services of the terminal.

[0142] After receiving local business information sent by the terminal, the management server can record it for subsequent users to query, modify, etc.

[0143] In some embodiments, after recording the valid services of the terminal (S302), the method further includes:

[0144] S303. Send service modification instructions to the terminal through a dedicated connection.

[0145] The service modification instruction is used to indicate the modification of valid services in the local service information of the terminal.

[0146] The management server can also send service modification instructions to the terminal, so that the terminal can update its local service information according to the service modification instructions, and send service modification information to the network device (as in steps S104C1 to S104C3).

[0147] As previously mentioned, in some embodiments, if the local service information sent by the terminal includes recommended services, the management server can also display the recommended services so that the user can select from them to add services to the terminal and send corresponding service modification instructions to the terminal.

[0148] Fourthly, refer to Figure 4 This disclosure provides a terminal, which includes a memory and a processor; the memory stores a computer program that can be executed by the processor, and when the computer program is executed by the processor, it implements any of the business management methods of this disclosure.

[0149] Fifthly, refer to Figure 5 This disclosure provides a network device including a memory and a processor; the memory stores a computer program that can be executed by the processor, and when the computer program is executed by the processor, it implements any of the service management methods of this disclosure.

[0150] Sixthly, refer to Figure 6 This disclosure provides a management server, which includes a memory and a processor; the memory stores a computer program that can be executed by the processor, and when the computer program is executed by the processor, it implements any of the business management methods of this disclosure.

[0151] Seventh aspect, refer to Figure 7 This disclosure provides a computer-readable medium having a computer program stored thereon, which, when executed by a processor, implements any of the business management methods of this disclosure.

[0152] Among them, the processor is a device with data processing capabilities, including but not limited to the central processing unit (CPU); the memory is a device with data storage capabilities, including but not limited to random access memory (RAM, more specifically SDRAM, DDR, etc.), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), and flash memory (FLASH); the I / O interface (read-write interface) is connected between the processor and the memory, enabling information exchange between the memory and the processor, including but not limited to the data bus (Bus).

[0153] Example:

[0154] The following is an exemplary description of the overall process of a business management method according to an embodiment of this disclosure.

[0155] The business management method of this disclosure embodiment is based on reference. Figure 8 Network architecture execution.

[0156] In this context, UE (User Equipment) refers to the terminal for the contracted service in this embodiment of the disclosure, such as an Internet of Things (IoT) terminal.

[0157] (R)AN (Radio Access Network) consists of base stations (such as gNB), controllers, etc., and is used to provide radio coverage and radio access services, thereby connecting the UE to the core network.

[0158] The core network, also known as the network device in this embodiment of the disclosure, connects to the UE via (R)AN and is also connected to the operator's data network (DN), thereby managing services subscribed to by the terminal (subscribed to on the operator's data network).

[0159] The core network can specifically adopt a 5G network architecture, which includes multiple modules (or network elements). The basic functions and relationships of each module are as follows:

[0160] AMF (Access and Mobility Management Function): The AMF is the interface point between the UE and the SMF. It is responsible for RAN connection management and mobility management, as well as UE security and authorization management.

[0161] SMF (Session Management Function): SMF is responsible for managing sessions, including session creation, modification, and release, as well as policies and flow control.

[0162] UPF (User Plane Function): UPF is responsible for handling packet transmission and forwarding, and can execute QoS (Quality of Service) policies.

[0163] AUSF (Authentication Server Function): AUSF is responsible for managing authentication and security policies, as well as handling session establishment with other networks. It can also store UE security information, such as keys and authentication vectors.

[0164] UDM (Unified Data Management): UDM is used to manage all user data, including user configurations, user policies, and access permissions.

[0165] PCF (Policy Control Function): PCF is responsible for policy control, including target QoS policy, bandwidth allocation policy, access control, etc. PCF can interact with other modules such as UDM and UDR to obtain the necessary information to execute policy control.

[0166] NSSF (Network Slice Selection Function): The NSSF is responsible for network slice selection. Based on the UE's needs and network conditions, it selects a suitable network slice for the UE and also coordinates the operation between SMF and AMF.

[0167] NEF (Network Exposure Function): As an interface for 5G networks, NEF allows application developers to expose network resources through APIs. NEF provides applications with a unified way to access network resources. The text on the connections between different modules indicates the type of the corresponding interface, such as the connection between UE and (R)AN via Uu (air interface).

[0168] Under different circumstances, the business management method of this disclosure embodiment can enter different processes.

[0169] Process (1): UE initiates registration to obtain the list of PCFs.

[0170] This process (1) is used when the UE inserts the SIM card and starts up normally: After the UE starts up, it will initiate a registration process with the communication network. The PCF will send the UE's signed service (valid service) and recommended service (recommended service) to the SMF. The SMF will send the service (service) information to the UE through the AMF and the base station via the ePCO parameter. The UE will parse the ePCO parameter to obtain the service set (local service information) and store it locally.

[0171] Reference Figure 9 The process of procedure (1) may specifically include:

[0172] Step 1: The UE initiates a PDU session establishment request message (identification information).

[0173] The PDU Session Establiment Request initiated by the UE contains parameters such as NAS Head, PDU SessionType, 5GSM Capacity, and Extended Protocol Configuration Options (EPCO), which can be carried through custom parameters in the EPCO.

[0174] Step 2: AMF sends a PDU session establishment message to SMF.

[0175] AMF receives a session establishment request message carrying ePCO parameters through the N1 interface, and forwards the session establishment request message to SMF through Nsmf_PDUSession_CreateSMContext Request. The parameters carried in ePCO remain unchanged.

[0176] Step 3: SMF sends a PDU session policy creation message to PCF

[0177] SMF forwards the request message to PCF via Npcf_SMPolicyControl_Create Request.

[0178] Step 4: PCF processes the Npcf_SMPolicyControl_CreateRequest message and returns a response message. After receiving the Npcf_SMPolicyControl_CreateRequest message from the N7 interface, PCF retrieves service information from the database based on IMSI, DNN, and slices. This information includes the names of currently subscribed services (valid services) and recommended services (recommended services), which are stored in two array parameters: enableservice and recommendedservice. These array parameters can contain one or more service names.

[0179] Then, send an Npcf_SMPolicyControl_Create Response message to SMF, carrying the name of the currently active service and the name of the recommended service to SMF.

[0180] Step 5: SMF decodes the service information and sends it to UPF.

[0181] The SMF receives the service information returned by the PCF and sends a PFCP Session EstablishmentRequest message to the UPF.

[0182] Step 6: UPF completes the service name setting and returns a response message to SMF.

[0183] UPF receives the service name from the PFCP Session Establishment Request message through the N4 interface, completes the function settings based on the service name in the media plane, and returns a PFCP SessionEstablishment Response message to SMF.

[0184] Step 7: SMF carries the service name through the ePCO field

[0185] SMF encapsulates the service name received from the Npcf_SMPolicyControl_Create Response message into the ePCO field of the Namf_Communication_N1N2MessageTransfer Request message.

[0186] Step 8: The AMF sends the service name to the UE via the N1 interface.

[0187] After receiving the ePCO parameters through the N1 interface, the AMF sends the PDU Session Establiment Accept message (service status information) to the UE.

[0188] Therefore, after receiving the session request acceptance message, the UE can decode the ePCO parameters to obtain the UE's service set (local service information); the UE stores the service set and provides an interface to present it, and users can view, import, export and other functions of the service set through a web page.

[0189] Process (2): Service information update initiated by PCF

[0190] This process (2) is used when the core network discovers changes in the service status: When the PCF meets the service trigger update conditions, the PCF actively initiates a service update for the UE. The trigger update conditions may include: the services subscribed to by the UE in the PCF have changed, including the addition, deletion and modification of subscribed services; the services recommended to the UE in the PCF have changed, including the addition, deletion and modification of recommended services.

[0191] Reference Figure 10 The process of procedure (2) may specifically include:

[0192] Step 1: PCF sends the Namf_Communication_N1N2MessageTransfer message to AMF.

[0193] The Namf_Communication_N1N2MessageTransfer message includes SUPI, UE service information, and notification target address. The UE service information includes the UE's changed subscribed service and the name of the recommended service.

[0194] Step 2: Core network triggers service request process

[0195] If the UE is in an idle state and is reachable from the base station (the UE enters an idle state due to being in a static state for a long time), the AMF sends a Network Triggered Service Request: If the AMF fails to page the UE, the AMF sends a Namf_Communication_N1N2TransferFailureNotification message to the PCF to notify the UE that the service information cannot be delivered to the UE; if the AMF successfully pages the UE, the UE initiates a service request process.

[0196] Step 3: AMF sends service information to UE

[0197] If the UE is in a connected state, the AMF will transparently transmit the UE's service information (service change information) received from the PCF to the UE (Delivery of Service).

[0198] Step 4: UE returns the service set update result.

[0199] When the UE receives the service information, it updates its local service set and returns the update result (Result of the Delivery of Service) to the AMF.

[0200] Step 5: Namf_N1MessageNotify message to PCF

[0201] AMF receives the service set update result returned by UE and subscribes to PCF. It uses Namf_N1MessageNotify to forward the UE's response to PCF. PCF processes the push status and update time of UR service in the database. The push status is "completed" and the update time is the current system time.

[0202] Process (3): UE connection state changes service information

[0203] This process (3) is used when the UE's service set is modified by a service modification instruction from the user or management server, and the UE is in a connected state: When the UE is in a connected state, if the user modifies the service name in the service set on the UE, the UE triggers the PDU session modification process, carries the new service name to the PCF through the ePCO parameter, and updates the new service name in the UPF.

[0204] Reference Figure 11 The process of procedure (3) may specifically include:

[0205] Step 1: PDU Session Modification Request

[0206] If a UE discovers that its service has been modified and it is in a connected state, it will send a PDU session modification request (service modification information) to the AMF to modify the established PDU session. This message carries the ePCO parameter containing the new service name.

[0207] Step 2: Nsmf_PDUSession_UpdateSMContext

[0208] When the AMF receives a PDU Session Modification Request, it generates an Nsmf_PDUSession_UpdateSMContext message based on its content. This message contains the service name and other SMcontext information that needs to be updated, such as QoS Flows that need to be added or deleted, and network slices that need to be modified.

[0209] Step 3: Npcf_SMPolicyControl_Update Request

[0210] SMF sends an Npcf_SMPolicyControl_Update Request message to PCF, which carries the new service name.

[0211] Step 4: Npcf_SMPolicyControl_Update Response

[0212] After receiving the Npcf_SMPolicyControl_Update Request, PCF extracts the service name, updates it in the database, and generates an Npcf_SMPolicyControl_Update Response message, which is sent to SMF for further processing. This message contains the new service information.

[0213] Step 5: Response of Nsmf_PDUSession_UpdateSMContext

[0214] SMF transmits the new service name to AMF via the ePCO field carried in the Response of Nsmf_PDUSession_UpdateSMContext.

[0215] Step Six: N2 Session Request

[0216] AMF encapsulates the ePCO field into a NAS message and sends it to the base station via an N2 Session Request message.

[0217] Step 7: PDU Session Modification Command

[0218] After receiving the N2 Session Request message, the base station sends the NAS message to the UE via the PDU SessionModification Command. The UE parses the ePCO parameters and extracts the new service name.

[0219] Step 8: PDU Session Modification Command Ack

[0220] If the UE determines that the new name matches the name modified by the user, it will reply with a PDU Session Modification Command Ack message. The PDU Session Modification Command Ack message carries the result of the UE successfully setting the new service and related parameters.

[0221] Step Nine: N2 NAS Uplink Transfer

[0222] The base station sends the result of the UE successfully setting up a new service to the AMF via the N2 NAS uplinktransfer message, using NAS layer information.

[0223] Step 10: Nsmf_PDUSession_UpdateSMContext Request

[0224] AMF sends an Nsmf_PDUSession_UpdateSMContext Request message to SMF, which contains the new service name.

[0225] Step 11: Nsmf_PDUSession_UpdateSMContext Response

[0226] After receiving the Nsmf_PDUSession_UpdateSMContext Request message, the SMF stores the new service name of the UE and replies with the Nsmf_PDUSession_UpdateSMContext Response message to the AMF.

[0227] Step 12: N4 Session Modification Request

[0228] SMF constructs an N4 Session Modification Request message containing new service information and sends it to UPF.

[0229] Step Thirteen: N4 Session Modification Response

[0230] After receiving the N4 Session Modification Request message, the UPF updates the UE's new service information and applies the packet identification rules included in the service information. Simultaneously, it generates an N4 Session Modification Response message for the SMF.

[0231] Process (4): UE changes service information in idle state

[0232] This process (4) is used when the UE's service set is modified by a service modification instruction from the user or management server and the UE is in an idle state: When the UE is in an idle state, if the user modifies the service name in the service set on the UE, the UE initiates a service request process, carrying the ePCO parameter containing the new service name to the PCF. After the PCF processes the request successfully locally, it returns the request to the UE and UPF, ensuring that the new service status takes effect in a timely manner.

[0233] Reference Figure 12 The process of procedure (4) may specifically include:

[0234] Step 1: Service Request

[0235] If a UE discovers that its service has been modified and it is in a connected state, it will trigger a service request process and send a Service Request message (service modification information) to the base station. This message carries information such as the ePCO parameter containing the new service name, the UE identifier, the requested service type, and QoS parameters.

[0236] Step 2: N2 Message (Service Request)

[0237] After receiving the Service Request message, the base station sends an N2 message (Service Request) to the AMF. This message carries information such as the ePCO parameter containing the new service name, the UE identifier, the requested service type, and QoS parameters.

[0238] Step 3: Nsmf_PDUSession_UpdateSMContext_Request

[0239] The AMF then sends an Nsmf_PDUSession_UpdateSMContext_Request message to the SMF, which carries information such as the ePCO parameter containing the new service name, the UE identifier, the requested service type, and QoS parameters.

[0240] Step 4: Npcf_SMPolicyControl_Update Request

[0241] SMF sends an Npcf_SMPolicyControl_Update Request message to PCF, carrying the new service name.

[0242] Step 5: Npcf_SMPolicyControl_Update Response

[0243] PCF parses the new service name, updates the database with the new service name, and responds by constructing an Npcf_SMPolicyControl_Update Response message, which includes the new service name.

[0244] Step Six: Nsmf_PDUSession_UpdateSMContext_Response

[0245] The SMF sends an Nsmf_PDUSession_UpdateSMContext_Response message to the AMF, which contains information such as the determined new service name, UE identifier, and QoS parameters.

[0246] Step 7: N2 Request

[0247] AMF sends an N2 Request message to the base station, requesting the establishment of a data path for the UE, and simultaneously passing the new service through the UE.

[0248] Step 8: RRC connection reconfiguration

[0249] The UE and the base station exchange RRC connection reconfiguration messages, update the resource configuration of the requested service, and pass the new service to the UE for confirmation. If the UE successfully sets the new service, it notifies the base station.

[0250] Step Nine: N2 Request Ack

[0251] After receiving the new service name from the UE, the base station sends an N2 Request Ack message to the AMF, indicating that the data path has been successfully established and the new service name.

[0252] Step 10: Nsmf_PDUSession_UpdateSMContext Request

[0253] After AMF receives the new service name, A sends another Nsmf_PDUSession_UpdateSMContext Request message to SMF. This message contains the new service name and updated information about the current session, such as the IP address of the UPF.

[0254] Step 11: N4 Session Modification Request

[0255] SMF sends an N4 Session Modification Request message to UPF, requesting the establishment of a data path for the session and sending the new service name to UPF.

[0256] Step 12: N4 Session Modification Response

[0257] UPF responds with an N4 Session Modification Response message, confirming that the data path was successfully established and the service name has been updated.

[0258] Step 13: SMF sends an Nsmf_PDUSession_UpdateSMContext Response message to AMF, indicating that the data path has been successfully established and the new service has taken effect.

[0259] Process (5): Management server manages a large number of UEs

[0260] This process (5) is used to manage a large number of UEs (such as IoT UEs) using a dedicated management server: a management server is introduced into the network architecture to manage the services of a large number of UEs. The management server can be accessed by a large number of UEs and can receive and store the service set from the UE. The services of a large number of UEs are queried and presented according to different conditions. A large number of modifications are initiated for the services of UEs that meet certain conditions. Then, the changes to the services are sent to the PCF and UPF through the UE to realize the batch management of a large number of UEs.

[0261] Reference Figure 13 The process of procedure (5) may specifically include:

[0262] Step 1: After the UE is powered on, it initiates a registration process with the core network (such as 5G core network 5GC) in accordance with the process (1). The UE obtains the service set and stores it locally.

[0263] Step Two: The management server generates a public-private key pair using an asymmetric encryption algorithm (such as RSA or ECC). When the UE needs to communicate with the management server, it sends an HTTPS request to the management server, requesting the management server's public key. The UE generates a random password, encrypts the random password using the public key provided by the management server, and then sends the encrypted random password to the management server via the HTTPS connection. After receiving the encrypted random password sent by the UE, the management server decrypts it using its own private key to obtain the original random password. Thus, both the management server and the UE possess the same random password. They use this random password to establish a symmetric encrypted channel (dedicated connection). Subsequent communication between the UE and the management server can be conducted through this symmetric encrypted channel to ensure data confidentiality and integrity.

[0264] Step 3: After the UE locally stores the service set, it sends a registration request message (local service information) to the management server. This message carries parameters including the subscribed service name, recommended service name, IMEI (International Mobile Equipment Identity), GPS parameters, service acquisition time, operating system version, software version, and hardware information. The IMEI is the UE's unique identifier and serves as the basis for the management server to distinguish different UEs. Upon receiving the registration request message, the management server stores the data in its local database and sends a response message to the UE. This response message carries parameters including a result flag, reason value, and time parameters. The management server can actually receive and store a massive amount of UE-related information.

[0265] Step 4: After all UEs to be managed are registered to the management server, data queries can be performed on the management server based on service name, service type (subscribed or recommended), map information, IMEI, etc. For example, the interface provided by the management server can perform large-scale queries for UEs matching conditions such as subscribed services, recommended services, tiled services, and DNN. When map information is loaded on the management server, UEs can be filtered based on GPS parameters according to conditions such as province, city, street, county, neighborhood, and road. UEs with the same longitude and latitude but different altitudes can also be displayed in hierarchical and gradient formats. Due to the large amount of data, all queries can use backend pagination technology, sending data to the frontend in batches according to user selections.

[0266] Step 5: Users can modify the subscribed services of a large number of UEs that meet the selected criteria on the management server interface. After the user completes the settings, the interface will switch to the change progress interface, which displays the current total number of UEs, the number of UEs that were successfully modified, the number of UEs that failed to be modified, etc. Among the UEs that failed to be modified, the reasons for failure can also be queried. The reasons for failure include the domain and failure details. The domain includes the management server, UE, and core network. The failure details are detailed failure information under a specific domain.

[0267] Step Six: The management server backend is configured with a controller that has a queue function. This controller converts the massive number of UEs identified above into batch queues to avoid overloading the management server. The controller performs service changes on the UEs in batches according to the first-in-first-out principle of the queue. That is, it sends a new service set request message (service modification instruction) to the UE through the service set between the UE and the corresponding UE.

[0268] Step 7: After receiving the message, the UE compares the new service name with the service set stored locally. If the comparison results match, the UE returns a response message to the management server through the symmetric encryption channel, carrying a successful change identifier. If the comparison results do not match, the UE modifies the local service set and, depending on whether it is in the connected state or the idle state, performs the above process (3) or process (4) to change the service information. Based on whether the modification of the information in the core network is successful, the UE returns a response message to the management server through the symmetric encryption channel.

[0269] Those skilled in the art will understand that all or some of the steps, systems, and devices disclosed above, as functional modules / units, can be implemented as software, firmware, hardware, or suitable combinations thereof.

[0270] In hardware implementations, the division between functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be executed by several physical components working together.

[0271] Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit (CPU), digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit (ASIC). Such software may be distributed on a computer-readable medium, which may include computer storage media (or non-transitory media) and communication media (or transient media). As is known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technique for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media include, but are not limited to, random access memory (RAM, more specifically SDRAM, DDR, etc.), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory (FLASH) or other disk storage; read-only optical disc (CD-ROM), digital versatile disc (DVD) or other optical disc storage; magnetic cartridges, magnetic tapes, disk storage or other magnetic storage; and any other media that can be used to store desired information and can be accessed by a computer. Furthermore, as is known to those skilled in the art, communication media typically contain computer-readable instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.

[0272] This disclosure has disclosed exemplary embodiments, and although specific terminology has been used, it is for general illustrative purposes only and should not be construed as limiting. In some instances, it will be apparent to those skilled in the art that features, characteristics, and / or elements described in conjunction with particular embodiments may be used alone, or in combination with features, characteristics, and / or elements described in conjunction with other embodiments, unless otherwise expressly indicated. Therefore, those skilled in the art will understand that various changes in form and detail may be made without departing from the scope of this disclosure as set forth by the appended claims.

Claims

1. A business management method, based on a terminal, wherein, The method includes: Send identification information to the network device; the identification information includes the identifier of the terminal; The system receives service status information sent by the network device; the service status information includes valid services subscribed to by the terminal. Based on the business status information, local business information is established and stored; the local business information includes the valid business. Receive a service modification instruction; the service modification instruction is used to indicate the modification of the valid service in the local service information of the terminal; Update the local service information according to the service modification instruction; The terminal sends service modification information to the network device based on the updated local service information; the service modification information includes modifications to the valid services in the terminal's local service information.

2. The method according to claim 1, wherein, The service status information also includes recommended services for the terminal, and the local service information also includes the recommended services.

3. The method according to claim 1, wherein, After establishing and storing the local business information, the following is also included: Receive service change information sent by the network device; the service change information includes changes to the valid service; Update the local business information according to the business change information.

4. The method according to claim 1, wherein, The service status information includes ePCO parameters.

5. The method according to claim 1, wherein, After establishing and storing the local business information, the following is also included: The local business information is sent to the management server through a dedicated connection. And / or, Through a dedicated connection with the management server, the system receives service modification instructions sent by the management server; the service modification instructions are used to indicate modifications to the valid services.

6. A service management method, based on network devices, wherein, The method includes: The receiver receives identification information sent by the terminal; the identification information includes the identifier of the terminal. The valid services subscribed to by the terminal are determined based on the identification information; Send service status information to the terminal; the service status information includes the active service; The terminal receives service modification information; the service modification information includes modifications to the valid service in the terminal's local service information. The valid business information in the record is updated according to the business modification information.

7. The method according to claim 6, wherein, Between the identification information sent by the receiving terminal and the service status information sent to the terminal, the following is also included: The recommended service for the terminal is determined based on the identification information; the service status information also includes the recommended service.

8. The method according to claim 6, wherein, After sending the service status information to the terminal, the method further includes: In response to a change in the valid service subscribed to by the terminal, service change information is sent to the terminal; the service change information includes the change in the valid service.

9. The method according to claim 6, wherein, The service status information includes ePCO parameters.

10. A terminal comprising a memory and a processor; the memory storing a computer program executable by the processor, wherein the computer program, when executed by the processor, implements the business management method according to any one of claims 1 to 5.

11. A network device comprising a memory and a processor; the memory storing a computer program executable by the processor, wherein the computer program, when executed by the processor, implements the service management method according to any one of claims 6 to 9.

12. A computer-readable medium having a computer program stored thereon, which, when executed by a processor, implements the business management method according to any one of claims 1 to 9.

Images