Information transmission method and device, related equipment and storage medium

Abstract

The application discloses an information transmission method and device, related equipment and a storage medium. The method comprises the following steps: a service enabling architecture layer server receives a first request sent by a vertical industry application layer server, the first request being used for requesting to configure a first rule for a terminal; the first rule is configured for the terminal through an application plane interface; and the terminal receives the first rule configured by the service enabling architecture layer server through the application plane interface. In this way, the rule is configured for the terminal through the application plane interface, which can not only reduce the signaling generated in the configuration process, but also reduce the occupation of control channel resources.

Description

Technical Field

[0001] This application relates to the fields of communication technology and computer technology, and in particular to an information transmission method, apparatus, related equipment and storage medium. Background Technology

[0002] As a new generation of communication technology, fifth-generation mobile communication technology (5G) has many advantages such as large bandwidth, low latency, high reliability, high connectivity, and ubiquitous network, thereby promoting the rapid development and transformation of vertical industries, such as the rise of smart healthcare, smart education, and smart agriculture.

[0003] In 5G systems, the Network Exposure Function (NEF) within the 5G core network (5GC) provides secure network capability open application programming interfaces (APIs) to third parties based on the standard RESful interface. In vertical industries, such as... Figure 1 As shown, Application Functions (AFs) can be deployed at the industry application layer and connected to the Network Capability Open API through the N33 interface to use the network capabilities provided by NEF.

[0004] In related technologies, within vertical industry scenarios, users often need to configure UE rule information for User Equipment (UE), such as Access Network Discovery & Selection Policy (ANDSP) and UE Route Selection Policy (URSP). When users configure UE rule information based on NEF, the process is cumbersome, generates excessive signaling, and consumes significant control channel resources. Summary of the Invention

[0005] To address the related technical problems, embodiments of this application provide an information transmission method, apparatus, related devices, and storage medium.

[0006] The technical solution of this application embodiment is implemented as follows:

[0007] This application provides an information transmission method applied to a service-enabled architecture layer server, including:

[0008] Receive a first request sent by the vertical industry application layer server, the first request being used to request the configuration of a first rule for the terminal;

[0009] Configure the first rule for the terminal using the application plane interface.

[0010] The method in the above scheme further includes:

[0011] Verify the first request;

[0012] After successful verification, the first rule is configured for the terminal via the application plane interface.

[0013] In the above scheme, if the terminal has already registered with the service enablement architecture layer server, the first rule is configured for the terminal through the application plane interface.

[0014] The method in the above scheme further includes:

[0015] If the terminal is not registered with the service enablement architecture layer server, the first rule is configured for the terminal through the network interface.

[0016] The method in the above scheme further includes:

[0017] Receive a second request sent by the terminal, the second request being used to request registration, the second request containing the terminal's registration information;

[0018] Save the registration information of the terminal.

[0019] The method in the above scheme further includes:

[0020] Send a response to the second request to the terminal.

[0021] In the above scheme, when configuring the first rule for the terminal through the application plane interface, the method further includes:

[0022] The relevant information of the first rule is sent to the terminal through the application plane interface; the relevant information includes at least one of the following:

[0023] Service-enabled architecture layer server-side identifier;

[0024] Vertical industry application layer server-side identifier;

[0025] First indication information; the first indication information is used to indicate the configuration method of the first rule.

[0026] The method in the above scheme further includes:

[0027] Receive a notification sent by the terminal, the notification being used to notify the server-side of the service enable architecture layer to update the rules of the terminal locally, the notification containing the second rule of the terminal;

[0028] The method in the above scheme further includes:

[0029] A response to sending the notification to the terminal.

[0030] The method in the above scheme further includes:

[0031] Send a second indication message to the terminal; the second indication message indicates that the terminal can use the second rule configured by the non-service enabled architecture layer server, or indicates that the terminal cannot use the second rule configured by the non-service enabled architecture layer server.

[0032] If the second indication information indicates that the terminal can use the second rule configured by the non-service enabled architecture layer server, the terminal sends a notification.

[0033] This application also provides an information transmission method applied to a terminal, including:

[0034] The service enablement architecture layer server receives a first rule configured through the application plane interface; wherein, the first rule is configured by the service enablement architecture layer server based on a first request sent by the vertical industry application layer server; the first request is used to request the configuration of the first rule for the terminal.

[0035] Save the first rule.

[0036] In the above scheme, if the terminal has registered with the service enablement architecture layer server, it receives the first rule configured by the service enablement architecture layer server through the application plane interface.

[0037] The method in the above scheme further includes:

[0038] If the terminal is not registered with the service enabling architecture layer server, it receives the first rule configured by the service enabling architecture layer server through the network interface.

[0039] The method in the above scheme further includes:

[0040] A second request is sent to the service enablement architecture layer server. The second request is used to request registration and includes the registration information of the terminal.

[0041] The method in the above scheme further includes:

[0042] Receive the response to the second request sent by the service enable architecture layer server.

[0043] In the above scheme, when the receiving service enablement architecture layer server configures the first rule through the application plane interface, the method further includes:

[0044] The service enablement architecture layer server receives information related to the first rule sent through the application plane interface; the information includes at least one of the following:

[0045] Service-enabled architecture layer server-side identifier;

[0046] Vertical industry application layer server-side identifier;

[0047] First indication information; the first indication information is used to indicate the configuration method of the first rule.

[0048] The method in the above scheme further includes:

[0049] A notification is sent to the service enablement architecture layer server to update the rules of the terminal on the local side of the service enablement architecture layer server. The notification includes a second rule for the terminal.

[0050] The method in the above scheme further includes:

[0051] Receive the response to the notification sent by the service enable architecture layer server.

[0052] The method in the above scheme further includes:

[0053] The terminal receives a second indication message sent by the service enabling architecture layer server; the second indication message indicates that the terminal can use the second rule configured by the non-service enabling architecture layer server, or indicates that the terminal cannot use the second rule configured by the non-service enabling architecture layer server.

[0054] When the second indication information indicates that the terminal can use the second rule configured by the non-service-enabled architecture layer server, the notification is sent to the service-enabled architecture layer server.

[0055] This application embodiment also provides an information transmission device, disposed on the server side of the service enablement architecture layer, including:

[0056] The first receiving unit is configured to receive a first request sent by the vertical industry application layer server, wherein the first request is used to request the configuration of a first rule for the terminal.

[0057] A configuration unit is used to configure the first rule for the terminal through an application plane interface.

[0058] This application embodiment also provides an information transmission device, disposed on a terminal, including:

[0059] The second receiving unit is configured to receive a first rule configured by the service enablement architecture layer server through the application plane interface; wherein the first rule is configured by the service enablement architecture layer server based on a first request sent by the vertical industry application layer server; the first request is used to request the configuration of the first rule for the terminal.

[0060] A storage unit is used to store the first rule.

[0061] This application also provides a service-enabled architecture layer server, including: a first processor and a first communication interface; wherein...

[0062] The first communication interface is used to receive a first request sent by the vertical industry application layer server, the first request being used to request the configuration of a first rule for the terminal;

[0063] The first processor is configured to use the first communication interface to configure the first rule for the terminal via an application plane interface.

[0064] This application also provides a terminal, including: a second processor and a second communication interface; wherein,

[0065] The second communication interface is used to receive a first rule configured by the service enablement architecture layer server through the application plane interface; wherein, the first rule is configured by the service enablement architecture layer server based on a first request sent by the vertical industry application layer server; the first request is used to request the configuration of the first rule for the terminal;

[0066] The second processor is used to store the first rule.

[0067] This application embodiment also provides a storage medium storing a computer program thereon, wherein when the computer program is executed by a processor, it implements the steps of any method on the server side of the above-described service enable architecture layer, or implements the steps of any method on the terminal side.

[0068] The information transmission method, apparatus, related devices, and storage medium provided in this application embodiment involve a service-enabled architecture layer server receiving a first request sent by a vertical industry application layer server. This first request requests the configuration of a first rule for a terminal. The server then configures the first rule for the terminal via an application plane interface. The terminal receives the first rule configured by the service-enabled architecture layer server through the application plane interface and saves the first rule. The solution provided in this application embodiment allows the service-enabled architecture layer server to configure the first rule for the terminal via the application plane interface after receiving the first request sent by VALS. This simplifies the configuration steps, reduces signaling generated during configuration, and conserves control channel resources. Attached Figure Description

[0069] Figure 1 A schematic diagram of the system architecture for interaction between vertical industries and NEF in related technologies;

[0070] Figure 2 This refers to the UE rule information update process based on NEF in related technologies;

[0071] Figure 3 This is a schematic diagram of the system architecture of the Service Enabler Architecture Layer (SEAL) in related technologies.

[0072] Figure 4 This is a schematic diagram of the system architecture of Network Slice Capability Exposure (NSCE) in related technologies;

[0073] Figure 5 This is a schematic flowchart of the first information transmission method according to an embodiment of this application;

[0074] Figure 6 This is a schematic flowchart of the second information transmission method according to an embodiment of this application;

[0075] Figure 7 This is a schematic flowchart illustrating the method for distributing UE rule information in an application embodiment of this application;

[0076] Figure 8 This is a schematic diagram illustrating the method flow for a UE to register with a SEAL server (SEALS, SEAL Service) in an application embodiment of this application.

[0077] Figure 9 This is a schematic diagram of the method for updating UE rule information in an application embodiment of this application;

[0078] Figure 10 This is a schematic diagram of the structure of the first information transmission device according to an embodiment of this application;

[0079] Figure 11 This is a schematic diagram of the structure of a second type of information transmission device according to an embodiment of this application;

[0080] Figure 12 This is a schematic diagram of the server-side structure of the service enablement architecture layer in an embodiment of this application.

[0081] Figure 13 This is a schematic diagram of the terminal structure according to an embodiment of this application;

[0082] Figure 14 This is a schematic diagram of the information transmission system structure according to an embodiment of this application. Detailed Implementation

[0083] The present application will now be described in further detail with reference to the accompanying drawings and embodiments.

[0084] In related technologies, UE rule information typically refers to rule information pre-configured on the UE or configured via the 5G network. The UE rule information currently defined by the 3rd Generation Partnership Project (3GPP) includes:

[0085] 1) ANDSP, used to allow the UE to select the network to access;

[0086] 2) URSP, used for UE to select the routing of Protocol Data Unit (PDU) sessions.

[0087] 3) Vehicle-to-everything (V2XP) rules, applied to vehicle-to-everything (V2X) application scenarios.

[0088] 4) Short-range service rules (ProSeP, ProSe Policy) are applied to short-range communication application scenarios.

[0089] In practical applications, UE rule information can be pre-configured on the UE or configured by the Policy Control Function (PCF) in 5GC. In related technologies, in vertical industry scenarios, industry users use NEF to update UE rule information. The functions of NEF include:

[0090] 1) Monitoring Capability: The core network monitors specified events of the UE and generates corresponding event notifications to send to third-party networks. This monitoring capability can be used for UE mobility management, such as UE location, reachability, and connection loss events; wherein, reachability indicates that the UE is in a registered state. In practical applications, if the core network does not receive UE registration information within a certain time interval, it can determine that the UE is in an unreachable state, i.e., the UE is not in the service area.

[0091] 2) Pre-configuration capabilities: Third-party networks provide relevant information to the core network through capability openness, such as the UE's expected route and the UE's network requirements, enabling the core network to perform targeted optimizations.

[0092] 3) Policy / Charging Capabilities: Third-party networks issue charging policies, QoS policies, and other policies to the core network through capability opening.

[0093] 4) Analysis report capability: Third-party networks can obtain network analysis reports, such as network performance analysis reports, UE communication reports, and slice performance analysis reports, through capability opening.

[0094] Furthermore, with the application and development of technologies such as network slicing, edge computing, big data, and artificial intelligence (AI) in 5G networks, 5GC can also abstract more capabilities to provide to the industry application layer, such as network slicing services, edge computing services, location services, 5G voice and messaging, and data analysis services.

[0095] like Figure 2 As shown, in a vertical industry scenario, the process of updating UE rule information may include the following steps:

[0096] Step 201a: During the UE registration process, the PCF sends the configured UE rule information to the UE, and then executes step 201b;

[0097] Here, before step 201a, after the UE starts up, it will initiate a registration request to the 5GC through the base station. After receiving the registration request, the 5GC's PCF will respond to the UE's registration request and send the configured second UE rule to the UE through the base station. At the same time, the PCF will also store the UE rule configured for the UE in the UDR.

[0098] Step 201b: PCF sends UE rule information change notification subscription information to the Unified Data Repository (UDR), and then proceeds to step 202;

[0099] The UE rule information change notification subscription information is used to subscribe to UE rule information change notifications.

[0100] Step 202: When it is necessary to update UE rule information, AF creates a UE rule information update request;

[0101] The UE rule information update request is used to update the UE rule information for the UE; the UE rule information update request includes updated UE rule information and AF identifier, etc.

[0102] In practical applications, if it is necessary to update the USRP rule information of the UE for the network slice identifier (which can be expressed as ID in English), the UE rule information update request can also include the UE's identifier and the network slice ID.

[0103] Step 203: The AF sends a UE rule information update request to the NEF via the Network Capability Open API;

[0104] Step 204: After receiving the UE rule information update request, NEF sends the UE rule information update request to Unified Data Management (UDM) to obtain authorization for the UE rule information update request;

[0105] Here, before updating UE rule information via NEF, industry users typically sign contracts with operators to subscribe to 5GC network services; this contract information is stored in UDM. Therefore, NEF can obtain authorization for UE rule information update requests by sending them to UDM.

[0106] Step 205: After receiving the UE rule information update request, UDM performs permission verification on the UE rule information update request;

[0107] Here, UDM uses the stored subscription information to find the corresponding subscription information in the relevant information carried by the UE rule information update request, and then determines the permissions of the UE rule information update request.

[0108] For example, the UDM can determine whether the AF has the authority to configure the first UE rule based on the AF identifier carried in the UE rule information update request. Furthermore, the UDM can also determine whether the UE has subscribed to the network slice based on the UE identifier and network slice identifier carried in the UE rule information update request.

[0109] Step 206: After successful verification, UDM sends a UE rule information update request authorization result to NEF;

[0110] Step 207: After receiving the authorization result of the UE rule information update request, NEF updates the UE rule information in the UDR;

[0111] In practical applications, NEF can configure the UE rule information corresponding to the UE identifier in the UDR as the updated UE rule information based on the UE identifier carried in the UE rule information update request.

[0112] Step 208: After the update is completed, NEF returns a UE rule information request response to AF, and then executes step 209;

[0113] Step 209: The UDR sends a UE rule information change notification to the PCF;

[0114] Here, since the PCF subscribes to UE rule information change notifications from the UDR during the UE registration process, when the UDR detects an update to the UE rule information corresponding to the UE, it will send a UE rule information change notification to the PCF.

[0115] Step 210: After receiving the UE rule information change notification, the PCF determines whether to update the UE rule information;

[0116] In practical applications, PCF can compare the updated UE rules carried in the UE rule information update request with the currently configured UE rules for the UE. If the updated UE rules are the same as the current UE rules, it means that the currently configured UE rules are the latest rules and do not need to be updated. If the updated UE rules are different from the current UE rules, it means that the UE rule information needs to be updated.

[0117] Step 211: After determining that the UE rule information needs to be updated, the PCF sends a UE rule information update request to the Access and Mobility Management Function (AMF);

[0118] Step 212: After receiving the UE rule information update request, the AMF sends the updated UE rules to the UE through the Wireless Access Network (RAN);

[0119] Specifically, the AMF can send updated UE rules to the UE through the base station.

[0120] Step 213: After receiving the first UE rule issued by the AMF, the UE sends a UE rule update result feedback to the AMF;

[0121] Step 214: After receiving the UE rule update result feedback sent by the UE, the AMF sends a response of UE rule information update request to the PCF.

[0122] On the other hand, in related technologies, a SEAL architecture has been proposed to standardize the process of enabling vertical industry applications through 5G networks. For example... Figure 3As shown, in the SEAL architecture, SEAL functional entities are deployed towards the Vertical Application Layer (VAL). VAL includes the VAL Customer (VALC) and VAL Service (VALS); the SEAL functional entities include the SEAL Customer (SEALC) and SEALS. VALC and SEALC are deployed on the UE. SEALS can access the 5G network through a network interface to perform functions such as network configuration and network information collection. SEALC and SEALS communicate through an application plane interface (i.e., the SEAL-UU interface). The SEAL-UU interface can be carried on the 5G network user plane or on other independent network systems, such as the IP Multimedia Subsystem (IMS). Furthermore, SEAL provides APIs (which can be called northbound APIs) for VAL, including SEAL-C and SEAL-S, enabling VAL to use network services through SEAL, thereby enabling broader industry applications.

[0123] Currently, SEAL can provide services to vertical industries including group management, configuration management, location management, identifier management, security management, and network resource management. Among related technologies, to provide NSCE services to vertical industries, an NSCE architecture based on the SEAL architecture is proposed, enabling these industries to autonomously enable, configure, monitor performance, and analyze data on network slices using NEF. Specifically, for example... Figure 4 As shown, in the NSCE architecture, NSCE functional entities are deployed for VALC and VALS, including the NSCE server (NSCES, NSCE Service) and the NSCE client (NSCEC, NSCECustomer). The NSCEC interacts with the NSCES through the NSCE-UU interface, which is carried on the 5G network user plane. The NSCEC can provide NSCE services to the VALC through the NSCE-C interface. The VALS interacts with the NSCES through the NSCE-S interface. The NSCES can act as an AF, interacting with the 5G network's NEF through the N33 interface to interact with 5GC functions such as PCF; alternatively, the NSCES can directly interact with the PCF through the N5 interface. The NSCES can also interact with the OAM system through NSCE-Operation Administration and Maintenance (OAM) to achieve functions such as network slicing capability configuration, performance monitoring, and fault supervision.

[0124] In practical applications, especially in vertical industry scenarios, users often need to configure rules for UEs (User Equipment). For example, URSP (Universal Network Slice Configuration and Service) is a core rule for configuring and managing network slices for UEs. It is generated during the process of subscribing to network slices and instructs the UE to place service data on the corresponding slice. When an industry user has subscribed to multiple network slices, they need to dynamically adjust the slice the UE accesses based on the resource usage of each slice to achieve load balancing and ensure network resources for high-priority UEs. In other words, the industry user needs to configure corresponding URSPs for the UE to instruct how the UE should place service data on multiple slices. Furthermore, when an industry user subscribes to a high-level membership service for a specific application, the URSP for that application on the UE needs to be adjusted to ensure that the UE can access higher-level network resources when running that application. Therefore, to meet the need for configuring rules for UEs, industry users can configure rules based on NEF (Network Provider Framework), specifically in the following two ways:

[0125] 1) Industry users based on Figure 1 The architecture shown interacts directly with NEF through the AF deployed at the industry application layer to configure corresponding rules for the UE.

[0126] 2) Industry users based on Figure 3 or Figure 4 The architecture shown involves SEALS or NSCES acting as the AF to interact with NEF in order to configure the corresponding rules for the UE.

[0127] However, both of these methods require interaction between the AF and NEF to configure rules for the UE via the network interface. Figure 2 As shown in the flowchart of AF and NEF interaction, the UE rule configuration process is lengthy and cumbersome. When industry users need to configure a large number of rules for the UE in a short period of time, or when the frequency of rule configuration is high, a large amount of signaling will be generated within the 5GC, between the 5GC and RAN, and between the RAN and the UE, thus affecting network operating efficiency. Furthermore, the above-mentioned UE rule configuration process is all performed in the control plane, which consumes control channel resources between the RAN and the UE. Since radio resources are very precious, control channel resources are limited to ensure data channel resources for application data transmission. If a large number of rules are configured for the UE in a short period of time, or when the frequency of rule configuration is high, a large amount of control channel resources will be consumed, which will affect the network performance of other service processes, such as increasing the processing latency of other control commands that the 5GC needs to send to the UE.

[0128] Based on this, in various embodiments of this application, Figure 3In the architecture shown, SEALS responds to VALS's request to configure rules for the terminal by configuring rules for the terminal through the application plane interface. This simplifies the configuration process, thereby reducing signaling and also reducing the occupation of control channel resources.

[0129] This application provides an information transmission method applied to SEALS, such as... Figure 5 As shown, it includes the following steps:

[0130] Step 501: Receive the first request sent by VALS, the first request being used to request the configuration of a first rule for the terminal;

[0131] Step 502: Configure the first rule for the terminal through the application plane interface.

[0132] The first request can be sent by a user in a vertical industry via VALS; the SEALS can receive the first request sent by VALS through the SEAL-S interface.

[0133] In practical applications, before step 501, after the terminal completes network registration (which can be understood as network access) on the SEALS, the SEALS can receive requests sent by the terminal to realize the terminal's registration on the SEALS.

[0134] Specifically, in one embodiment, the method may further include:

[0135] Receive a second request sent by the terminal, the second request being used to request registration, the second request containing the terminal's registration information;

[0136] Save the registration information of the terminal.

[0137] The registration information may include the terminal's identifier and configured terminal rules; the terminal's identifier may specifically include a mobile phone number, Internet Protocol (IP) address, Media Access Control (MAC) address, International Mobile Subscriber Identity (IMSI), International Mobile Equipment Identity (IMEI), Permanent Equipment Identity (PEI), etc.

[0138] In practical applications, after completing network registration, when a terminal needs to register with SEALS, it can send a second request to SEALS through an application plane interface, such as the SEAL-UU interface. Upon receiving the second request, SEALS can save the terminal's registration information carried in the request to complete the terminal's registration, indicating successful registration.

[0139] In practical applications, there may be scenarios where terminal registration fails, such as insufficient local storage space in SEALS preventing the saving of registration information, incorrect number of bits or format of the terminal identifier, or the terminal identifier being duplicated with the terminal identifier stored locally in SEALS, meaning the terminal has already been registered with SEALS.

[0140] Since there are two possibilities—successful registration and failed registration—SEALS can also respond to the second request sent by the terminal to notify the terminal of the registration result.

[0141] Based on this, in one embodiment, the method may further include:

[0142] Send a response to the second request to the terminal.

[0143] The response to the second request is used to notify the terminal whether the registration was successful or failed.

[0144] In practical applications, before SEALS responds to the first request sent by VALS and configures the first rule for the terminal, it can verify the first request to confirm the permissions corresponding to the first request.

[0145] Based on this, in one embodiment, the method may further include:

[0146] Verify the first request;

[0147] After successful verification, the first rule is configured for the terminal via the application plane interface.

[0148] The first request may include information such as the VALS identifier, the terminal identifier, and the first rule.

[0149] In practical applications, before configuring the first rule for the terminal via SEALS, industry users typically sign a contract with an operator to subscribe to 5GC network services. The contract information can be stored on a specific authentication server, such as a Business Support System (BSS) or an OAM system. Therefore, SEALS can verify the first request sent by the industry user via VALS through the authentication server. This application embodiment does not limit the method of verifying the first request.

[0150] For example, SEALS uses the VALS identifier carried in the first request and, through contract-related information in the authentication server, can determine whether the VALS has the authority to request the configuration of the first rule for the terminal; if SEALS determines that the VALS has the authority, the verification passes. Otherwise, the verification fails.

[0151] For example, SEALS uses the terminal identifier carried in the first request and, through contract-related information in the authentication server, can determine whether a first rule can be configured for the terminal. For instance, if the first request is used to request URSP configuration for the terminal, the first request also carries the identifier of the network slice corresponding to the first rule. In this case, SEALS uses the terminal identifier and, through contract-related information in the authentication server, can determine whether the terminal has subscribed to the network slice. If SEALS determines that the terminal has subscribed to the network slice, it means that URSP can be configured for the terminal, i.e., the verification passes; otherwise, it means the verification fails.

[0152] For example, SEALS can use the terminal identifier and the first rule carried in the first request to determine whether VALS has repeatedly requested to configure the first rule for the terminal, that is, whether the rule currently configured on the terminal is the same as the first rule. If SEALS determines that VALS has not repeatedly requested to configure the first rule for the terminal, the verification passes; otherwise, the verification fails.

[0153] After successful verification, SEALS can determine how to configure the first rule for the terminal based on whether the terminal is registered with SEALS.

[0154] Specifically, in one embodiment, if the terminal has already registered with the SEALS, the first rule is configured for the terminal through the application plane interface.

[0155] In practical applications, SEALS can use the terminal identifier carried in the first request to search for a matching terminal identifier in its locally stored terminal registration information. If SEALS finds a matching terminal identifier, it indicates that the terminal has been registered with SEALS. At this point, SEALS can configure the first rule for the terminal through the application plane interface between SEALS and the terminal, the SEAL-UU interface. In this process, since the SEAL-UU interface is carried on the network user plane or on other independent network systems, such as IMS, configuring the first rule for the terminal through the application plane interface avoids the significant control channel resource consumption that would occur if the first rule were configured through the network interface, thus saving control channel resources.

[0156] In practical applications, if SEALS cannot find a terminal identifier that matches the terminal identifier carried in the first request locally, it means that the terminal is not registered with SEALS. In this case, SEALS can configure the first rule for the terminal through the network interface.

[0157] Specifically, in one embodiment, if the terminal is not registered with the SEALS, the first rule is configured for the terminal via a network interface.

[0158] Here, for terminals not registered with SEALS, SEALS can access them via a network interface, such as the N33 interface, and based on... Figure 2 The method flow shown configures the first rule for the terminal; wherein, the network interface is carried on the network control plane.

[0159] In practical applications, when SEALS configures the first rule for a terminal through the network interface or application plane interface, it can also send relevant information about the first rule to the terminal so that the terminal can query it as needed.

[0160] Based on this, in one embodiment, when configuring the first rule for the terminal through an application plane interface, the method may further include:

[0161] The relevant information of the first rule is sent to the terminal through the application plane interface; the relevant information includes at least one of the following:

[0162] SEALS logo;

[0163] VALS identifier;

[0164] First indication information; the first indication information is used to indicate the configuration method of the first rule.

[0165] The first indication information may indicate that the first rule is configured by SEALS.

[0166] Here, in the scenario where SEALS configures URSP for the terminal, the first rule can also carry the network slice service provider identifier so that the terminal can determine the network slice service provider corresponding to the configured URSP.

[0167] In practical applications, for terminals already registered with SEALS, there are scenarios where rules need to be configured for the terminals without SEALS. For example, network operators can configure rules directly through BSS or OAM systems based on the needs of industry users. In these scenarios, before configuring rules for the terminals, industry users typically negotiate with the network operator to determine whether to allow the terminals to use rules configured outside of SEALS. Here, "non-SEALS" includes entities other than SEALS capable of configuring rules for the terminals, such as the network operator. The network operator can then send the negotiation results to SEALS, enabling SEALS to send corresponding instructions to the terminals.

[0168] Based on this, in one embodiment, the method may further include:

[0169] Send a second indication message to the terminal; the second indication message indicates that the terminal can use the second rule configured without SEALS, or indicates that the terminal cannot use the second rule configured without SEALS.

[0170] If the second indication information indicates that the terminal can use a second rule configured without SEALS, the terminal receives a notification sent by the terminal.

[0171] In practical applications, if industry users and network operators agree that terminals are not allowed to use the second rule configured by non-SEALS, then SEALS can send a second instruction to the terminal to instruct the terminal not to use the second rule configured by the non-service-enabled architecture layer server.

[0172] If industry users and network operators agree to allow terminals to use a second rule not configured by SEALS, then SEALS can send a second instruction to the terminal to indicate that the terminal can use the second rule configured by the non-service enablement architecture layer server.

[0173] Here, in a scenario where terminals are allowed to use a second rule not configured by SEALS, SEALS can receive a notification sent by the terminal to update the locally stored terminal rules.

[0174] Based on this, in one embodiment, the method may further include:

[0175] Receive a notification sent by the terminal, the notification being used to notify the updating of the rules of the terminal locally in SEALS, the notification containing the second rule of the terminal;

[0176] Update the rules of the local terminal using the second rule.

[0177] In practical applications, when a terminal registered with SEALS detects that a non-SEALS provider has configured a second rule for the terminal, the terminal will send a notification to SEALS to inform SEALS to update the local terminal rules using the second rule contained in the notification.

[0178] In practical applications, after SEALS completes the rule update for the local terminal, it can also respond to notifications sent by the terminal.

[0179] Based on this, in one embodiment, the method may further include:

[0180] A response to sending the notification to the terminal.

[0181] The notification response is used to notify the terminal that the local terminal's rules have been updated.

[0182] Accordingly, embodiments of this application also provide an information transmission method, applied to a terminal, such as... Figure 6 As shown, it includes the following steps:

[0183] Step 601: Receive the first rule configured by SEALS through the application plane interface; wherein, the first rule is configured by the SEALS based on a first request sent by VALS; the first request is used to request the configuration of the first rule for the terminal;

[0184] Step 602: Save the first rule.

[0185] In practical applications, before step 601, after the terminal completes network registration (which can be understood as accessing the network), it can send a request to SEALS to register on SEALS.

[0186] Specifically, in one embodiment, the method may further include:

[0187] A second request is sent to the SEALS, the second request being used to request registration, and the second request containing the terminal's registration information.

[0188] In practical applications, after a terminal accesses the network, when the terminal needs to register with SEALS, it can send a second request to SEALS through the application plane interface, SEAL-UU interface, to request registration with SEALS.

[0189] In one embodiment, the method may further include:

[0190] Receive a response to the second request sent by SEALS.

[0191] In practical applications, the terminal can receive the response to the second request sent by SEALS through the SEAL-UU interface to determine whether the registration was successful or failed.

[0192] In practical applications, depending on whether the terminal is registered with SEALS, the terminal can receive the first rule configured by SEALS in different ways.

[0193] Specifically, in one embodiment, if the terminal has already registered with the SEALS, it receives a first rule configured by the SEALS through the application plane interface.

[0194] Here, assuming the terminal is already registered with SEALS, the terminal can receive the first rule configured by SEALS through the application plane interface. Specifically, the terminal can receive the first rule issued by SEALS through the SEAL-UU interface via the RAN. The SEAL-UU interface can be carried on the network user plane or on other independent network systems. This reduces the occupation of control channel resources on the network control plane and simplifies the configuration process, thereby significantly reducing the amount of signaling.

[0195] In practical applications, for scenarios where the terminal is not registered with SEALS, the terminal can receive the first rule configured by SEALS through the network interface.

[0196] Specifically, in one embodiment, the method may further include:

[0197] If the terminal is not registered with the SEALS, it receives the first rule configured by the SEALS through the network interface.

[0198] For example, the terminal can receive the first rule issued by SEALS through the network interface carried on the network control plane via the RAN.

[0199] In practical applications, when a terminal receives the first rule configured by SEALS through the application plane interface or network interface, it can also receive relevant information about the first rule sent by SEALS, so as to query the configured first rule later.

[0200] Specifically, in one embodiment, when receiving the first rule configured by the service enablement architecture layer server through the application plane interface, the method may further include:

[0201] The service enablement architecture layer server receives information related to the first rule sent through the application plane interface; the information includes at least one of the following:

[0202] SEALS logo;

[0203] VALS identifier;

[0204] First indication information; the first indication information is used to indicate the configuration method of the first rule.

[0205] In practical applications, terminals already registered with SEALS can receive rules not configured by SEALS. For rules not configured by SEALS, the terminal can receive indication information sent by SEALS to determine whether the non-SEALS-configured rule can be used.

[0206] Based on this, in one embodiment, the method may further include:

[0207] The terminal receives a second indication message sent by the SEALS; the second indication message indicates that the terminal can use a second rule not configured by the SEALS, or indicates that the terminal cannot use a second rule not configured by the SEALS.

[0208] When the second indication information indicates that the terminal can use a second rule configured without SEALS, the notification is sent to SEALS.

[0209] Here, in a scenario where the second instruction information indicates that the terminal can use the second rule configured outside of SEALS, the terminal can send a notification to SEALS to update the terminal's local rules in SEALS.

[0210] Based on this, in one embodiment, the method may further include:

[0211] A notification is sent to the SEALS to notify the client to update the rules of the client locally on the SEALS, and the notification includes a second rule for the client.

[0212] In practical applications, when a terminal that has registered with SEALS is detected to have a second rule configured for the terminal by a non-SEALS provider, a notification can be sent to SEALS, enabling SEALS to update the rules of the local terminal using the second rule contained in the notification.

[0213] In practical applications, a terminal can determine the object to which rules are configured by the channel type it receives the rules from. For example, a terminal can receive rules configured by 5GC through a control channel. Additionally, the terminal can determine the configuration method of the rules by the relevant information carried by the rules, such as instruction information, and thus determine the object to which the rules are configured, including both SEALS and non-SEALS rules.

[0214] Based on this, in one embodiment, the method may further include:

[0215] Receive a response to the notification sent by SEALS.

[0216] In practical applications, the terminal can receive responses to notifications sent by SEALS through the SEAL-UU interface to confirm the completion of rule updates for the local SEALS terminal.

[0217] The information transmission method provided in this application embodiment involves the SEALS receiving a first request sent by the VALS, the first request being used to request the configuration of a first rule for a terminal; configuring the first rule for the terminal through an application plane interface; and the terminal receiving the first rule configured by the SEALS through the application plane interface and saving the first rule. The solution provided in this application embodiment, after receiving the first request sent by the VALS, configures the first rule for the terminal through the application plane interface. This simplifies the configuration steps, reduces signaling generated during the configuration process, and also saves control channel resources.

[0218] The present application will be further described in detail below with reference to application examples.

[0219] based on Figure 3 The SEALS architecture shown in this application example proposes a method for distributing UE rule information, such as... Figure 7 As shown, it includes the following steps:

[0220] Step 701: VALS sends a UE rule information update request (i.e., the first request) to SEALS through the SEAL-S interface (also known as the northbound interface);

[0221] The UE rule information update request includes at least information such as UE identifier, UE rule and VALS identifier; the UE rule information update request is used to request the issuance of UE rules to the terminal.

[0222] In practical applications, before step 701, after completing the 5G network registration, the UE will also initiate a registration request to the SEALS, such as... Figure 8 As shown, the following steps may be included:

[0223] Step 801: The UE establishes a connection to the SEALS, and then proceeds to step 802;

[0224] Here, after the UE establishes a connection with SEALS, it can communicate with SEALS through the SEALS-UU interface.

[0225] Step 802: The UE sends a registration request to the SEALS;

[0226] The registration request carries registration information, which includes at least one of the following: UE identifier and configured UE rule information; the UE identifier may include mobile phone number, IP address, MAC address, IMSI, IMEI, PEI, etc.

[0227] Step 803: After receiving the registration request (i.e., the second request) sent by the UE, SEALS saves the UE's registration information and sends a response to the UE registration request to notify the UE whether the registration was successful or failed.

[0228] In practical applications, when SEALS saves the UE's registration information, it may be unable to do so due to insufficient local storage space. In this case, SEALS notifies the UE of registration failure through the UE registration request response.

[0229] If SEALS can successfully save the UE's registration information, it will notify the UE of successful registration through the response to the UE registration request.

[0230] Step 702: After receiving the UE rule information update request sent by VALS, SEALS authenticates the UE rule information update request.

[0231] Specifically, the authentication of the permissions may include verifying the permissions of the VALS, verifying the subscription information of the UE, and verifying whether the VALS has repeatedly configured the UE rules.

[0232] In practical applications, SEALS can verify VALS permissions and UE subscription information through authentication servers, such as BSS or OAM.

[0233] For example, since the authentication server stores subscription information, SEALS can determine through the authentication server whether VALS has the authority to update UE rules and whether it has the authority to configure UE rules for the UE.

[0234] For example, when the UE rule is URSP, SEALS can determine through the authentication server whether the UE has subscribed to the network slice corresponding to the URSP; if the UE has subscribed to the corresponding network slice, SEALS can determine that it can configure URSP for the UE; if the UE has not subscribed to the corresponding network slice, SEALS can determine that it cannot configure URSP for the UE.

[0235] Additionally, SEALS can verify whether VALS has duplicate UE rules by comparing the UE rules on the current UE with the UE rules in the UE rule information update request. If they are different, the verification is successful; if they are the same, it means that the UE rules on the current UE are the latest UE rules, and the verification fails.

[0236] Step 703: After successful verification, SEALS determines the method for distributing the corresponding UE rule information based on whether the UE is registered with SEALS.

[0237] Here, SEALS searches for matching information from the locally stored registration information based on the UE identifier in the UE rule information update request. If SEALS can find matching information, it means that the UE has registered with SEALS; if it cannot find matching information, it means that the UE has not registered with SEALS.

[0238] Step 704: For UEs already registered with SEALS, SEALS sends UE rules to the terminal through an application plane interface, such as the SEAL-UU interface; the SEAL-UU interface can be carried on the network user plane; for UEs not registered with SEALS, SEALS sends UE rules to the terminal through a network interface carried on the network control plane, such as the N33 interface.

[0239] In practical applications, for UEs that have already registered with SEALS, the distribution of UE rules may not go through SEALS. For example, network operators may update rules directly through BSS or OAM according to the needs of industry users. Therefore, the UE will also send the distributed rules to SEALS so that SEALS can update the UE rules stored locally.

[0240] Specifically, such as Figure 9 As shown, the method flow for notifying SEALS of UE rule update events includes the following steps:

[0241] Step 901: After a UE that has registered with SEALS detects that a UE rule (i.e., the second rule) has been issued by a non-SEALS UE, proceed to step 902.

[0242] Step 902: The UE sends a UE rule update notification (i.e., a notification) to the SEALS;

[0243] The UE rule update notification carries the issued UE rules.

[0244] Step 903: After receiving the UE rule update notification, SEALS updates the local UE rules;

[0245] Step 904: After the update is completed, SEALS sends a UE rule update notification response to the UE to notify the UE that the update was successful.

[0246] The UE rule information delivery method proposed in this application, based on the SEAL architecture, delivers UE rules to UEs already registered with SEALS through the SEAL-UU interface carried on the user plane. This simplifies the delivery process, significantly reducing signaling volume, and also reduces the occupation of control channel resources, thus saving radio control channel resources.

[0247] To implement the service enablement architecture layer server-side solution of this application embodiment, this application embodiment also provides an information transmission device, which is installed on the service enablement architecture layer server, such as... Figure 10 As shown, the device includes:

[0248] The first receiving unit 1001 is used to receive a first request sent by the vertical industry application layer server, the first request being used to request the configuration of a first rule for the terminal;

[0249] Configuration unit 1002 is used to configure the first rule for the terminal through the application plane interface.

[0250] In one embodiment, the device may further include: a verification unit 1003, configured to verify the first request;

[0251] The configuration unit 1002 is used to configure the first rule for the terminal through the application plane interface after the verification is passed.

[0252] In one embodiment, if the terminal has already registered with the service enablement architecture layer server, the first rule is configured for the terminal through the application plane interface.

[0253] In one embodiment, the configuration unit 1002 is further configured to configure the first rule for the terminal via a network interface when the terminal is not registered with the service enablement architecture layer server.

[0254] In one embodiment, the device may further include: a processing unit 1004; the processing unit 1004 is configured to:

[0255] Receive a second request sent by the terminal, the second request being used to request registration, the second request containing the terminal's registration information;

[0256] Save the registration information of the terminal.

[0257] In one embodiment, the processing unit 1004 is further configured to send a response to the second request to the terminal.

[0258] In one embodiment, the processing unit 1004 is further configured to:

[0259] The relevant information of the first rule is sent to the terminal through the application plane interface; the relevant information includes at least one of the following:

[0260] Service-enabled architecture layer server-side identifier;

[0261] Vertical industry application layer server-side identifier;

[0262] First indication information; the first indication information is used to indicate the configuration method of the first rule.

[0263] In one embodiment, the processing unit 1004 is further configured to:

[0264] Receive a notification sent by the terminal, the notification being used to notify the server-side server of updating the rules of the terminal locally, the notification including the second rule of the terminal;

[0265] Update the rules of the local terminal using the second rule.

[0266] In one embodiment, the processing unit 1004 is further configured to send a response to the notification to the terminal.

[0267] In one embodiment, the processing unit 1004 is further configured to:

[0268] Send a second indication message to the terminal; the second indication message indicates that the terminal can use the second rule configured by the non-service enabled architecture layer server, or indicates that the terminal cannot use the second rule configured by the non-service enabled architecture layer server.

[0269] If the second indication information indicates that the terminal can use the second rule configured by the non-service enabled architecture layer server, the terminal sends a notification.

[0270] In practical applications, the first receiving unit 1001 can be implemented by the communication interface in the information transmission device; the configuration unit 1002, the verification unit 1003 and the processing unit 1004 can be implemented by the communication interface in the information transmission device combined with a processor.

[0271] To implement the terminal-side solution of this application embodiment, this application embodiment also provides an information transmission device, which is installed on the terminal, such as... Figure 11 As shown, the device includes:

[0272] The second receiving unit 1101 is used to receive a first rule configured by the service enabling architecture layer server through the application plane interface; wherein, the first rule is configured by the service enabling architecture layer server based on a first request sent by the vertical industry application layer server; the first request is used to request the configuration of the first rule for the terminal.

[0273] Storage unit 1102 is used to store the first rule.

[0274] In one embodiment, if the terminal has registered with the service enablement architecture layer server, it receives a first rule configured by the service enablement architecture layer server through the application plane interface.

[0275] In one embodiment, the second receiving unit 1101 is further configured to receive a first rule configured by the service enabling architecture layer server through a network interface when the terminal is not registered with the service enabling architecture layer server.

[0276] In one embodiment, the device may further include: a sending unit 1103, configured to send a second request to the service enablement architecture layer server, the second request being used to request registration, the second request containing the registration information of the terminal.

[0277] In one embodiment, the second receiving unit 1101 is further configured to receive a response to the second request sent by the service enable architecture layer server.

[0278] In one embodiment, the second receiving unit 1101 is further configured to:

[0279] The service enablement architecture layer server receives information related to the first rule sent through the application plane interface; the information includes at least one of the following:

[0280] Service-enabled architecture layer server-side identifier;

[0281] Vertical industry application layer server-side identifier;

[0282] First indication information; the first indication information is used to indicate the configuration method of the first rule.

[0283] In one embodiment, the sending unit 1103 is further configured to send a notification to the service enable architecture layer server, the notification being used to notify the server to update the rules of the terminal locally, the notification including a second rule of the terminal.

[0284] In one embodiment, the second receiving unit 1101 is further configured to receive a response to the notification sent by the service enable architecture layer server.

[0285] In one embodiment, the second receiving unit 1101 is further configured to receive second indication information sent by the service enabling architecture layer server; the second indication information indicates that the terminal can use the second rule configured by the non-service enabling architecture layer server, or indicates that the terminal cannot use the second rule configured by the non-service enabling architecture layer server.

[0286] The sending unit 1103 is further configured to send the notification to the service-enabled architecture layer server when the second indication information indicates that the terminal can use the second rule configured by the non-service-enabled architecture layer server.

[0287] In practical applications, the second receiving unit 1101 and the sending unit 1103 can be implemented by the communication interface in the information transmission device; the storage unit 1102 can be implemented by the communication interface in the information transmission device combined with a processor.

[0288] It should be noted that the information transmission device provided in the above embodiments is only illustrated by the division of the above-described program units. In practical applications, the above processing can be assigned to different program units as needed, that is, the internal structure of the device can be divided into different program units to complete all or part of the processing described above. In addition, the information transmission device and the information transmission method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here.

[0289] Based on the hardware implementation of the above program modules, and in order to implement the service enabling architecture layer server-side method of this application embodiment, this application embodiment also provides a service enabling architecture layer server, such as... Figure 12 As shown, the service enabling architecture layer server 1200 includes:

[0290] The first communication interface 1201 is capable of exchanging information with the terminal;

[0291] The first processor 1202 is connected to the first communication interface 1201 to enable information interaction with the terminal and to execute the methods provided by one or more technical solutions on the server side of the above-mentioned service enablement architecture layer when running a computer program.

[0292] The computer program is stored in the first memory 1203.

[0293] Specifically, the first communication interface 1201 is used to receive a first request sent by the vertical industry application layer server, the first request being used to request the configuration of a first rule for the terminal;

[0294] The first processor 1202 is configured to configure the first rule for the terminal through the application plane interface using the first communication interface 1201.

[0295] In one embodiment, the first processor 1202 is further configured to:

[0296] Verify the first request;

[0297] After successful verification, the first rule is configured for the terminal via the application plane interface.

[0298] In one embodiment, if the terminal has already registered with the service enablement architecture layer server, the first rule is configured for the terminal through the application plane interface using the first communication interface 1201.

[0299] In one embodiment, the first processor 1202 is further configured to configure the first rule for the terminal via a network interface using the first communication interface 1201 when the terminal is not registered with the service enablement architecture layer server.

[0300] In one embodiment, the first communication interface 1201 is further configured to receive a second request sent by the terminal, the second request being for requesting registration, and the second request containing the terminal's registration information;

[0301] The first processor 1202 is also used to store the registration information of the terminal.

[0302] In one embodiment, the first communication interface 1201 is also used to send a response to the second request to the terminal.

[0303] In one embodiment, the first communication interface is further configured to send information related to the first rule to the terminal via the application plane interface; the information related to the rule includes at least one of the following:

[0304] Service-enabled architecture layer server-side identifier;

[0305] Vertical industry application layer server-side identifier;

[0306] First indication information; the first indication information is used to indicate the configuration method of the first rule.

[0307] In one embodiment, the first communication interface 1201 is further configured to receive a notification sent by the terminal, the notification being configured to update the rules of the terminal locally on the service enable architecture layer server, the notification including the second rule of the terminal;

[0308] The first processor 1202 is also configured to update the rules of the local terminal using the second rule.

[0309] In one embodiment, the first communication interface 1201 is further configured to send a response to the notification to the terminal.

[0310] In one embodiment, the first communication interface 1201 is further configured to:

[0311] Send a second indication message to the terminal; the second indication message indicates that the terminal can use the second rule configured by the non-service enabled architecture layer server, or indicates that the terminal cannot use the second rule configured by the non-service enabled architecture layer server.

[0312] If the second indication information indicates that the terminal can use the second rule configured by the non-service enabled architecture layer server, the terminal sends a notification.

[0313] It should be noted that the specific processing procedures of the first processor 1202 and the first communication interface 1201 can be understood by referring to the above method.

[0314] Of course, in practical applications, the various components in the service enablement architecture layer server are coupled together through bus system 1204. It can be understood that bus system 1204 is used to implement the connection and communication between these components. In addition to the data bus, bus system 1204 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 12 The general labeled all buses as Bus System 1204.

[0315] The first memory 1203 in this embodiment is used to store various types of data to support the operation of the service-enabled architecture layer server 1200. Examples of such data include any computer program used to operate on the service-enabled architecture layer server 1200.

[0316] The methods disclosed in the above embodiments of this application can be applied to the first processor 1202, or implemented by the first processor 1202. The first processor 1202 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware or by instructions in the form of software in the first processor 1202. The first processor 1202 may be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The first processor 1202 can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware decoding processor, or being executed by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, which is located in the first memory 1203. The first processor 1202 reads the information in the first memory 1203 and completes the steps of the aforementioned method in combination with its hardware.

[0317] In an exemplary embodiment, the first device 1200 may be implemented by one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers (MCUs), microprocessors, or other electronic components to perform the aforementioned method.

[0318] Based on the hardware implementation of the above program modules, and in order to implement the terminal-side method of the embodiments of this application, the embodiments of this application also provide a terminal, such as... Figure 13 As shown, the terminal 1300 includes:

[0319] The second communication interface 1301 is capable of exchanging information with the service enablement architecture layer server;

[0320] The second processor 1302 is connected to the second communication interface 1301 to enable information interaction with the service enablement architecture layer server and to execute the methods provided by one or more of the above-mentioned terminal-side technical solutions when running computer programs.

[0321] The computer program is stored in the second memory 1303.

[0322] Specifically, the second communication interface 1301 is used to receive a first rule configured by the service enablement architecture layer server through the application plane interface; wherein, the first rule is configured by the service enablement architecture layer server based on a first request sent by the vertical industry application layer server; the first request is used to request the configuration of the first rule for the terminal.

[0323] The second processor 1302 is used to store the first rule.

[0324] In one embodiment, the second communication interface 1301 is used to receive a first rule configured by the service enablement architecture layer server through the application plane interface when the terminal has registered with the service enablement architecture layer server.

[0325] In one embodiment, the second communication interface 1301 is further configured to receive a first rule configured by the service enabling architecture layer server through a network interface when the terminal is not registered with the service enabling architecture layer server.

[0326] In one embodiment, the second communication interface 1301 is further configured to send a second request to the service enablement architecture layer server, the second request being used to request registration, and the second request containing the registration information of the terminal.

[0327] In one embodiment, the second communication interface 1301 is further configured to receive a response to the second request sent by the service enable architecture layer server.

[0328] In one embodiment, the second communication interface 1301 is further configured to receive information related to a first rule sent by the service enablement architecture layer server through the application plane interface; the information includes at least one of the following:

[0329] Service-enabled architecture layer server-side identifier;

[0330] Vertical industry application layer server-side identifier;

[0331] First indication information; the first indication information is used to indicate the configuration method of the first rule.

[0332] In one embodiment, the second communication interface 1301 is further configured to send a notification to the service enablement architecture layer server, the notification being used to notify the server to update the rules of the terminal locally, the notification including the second rule of the terminal.

[0333] In one embodiment, the second communication interface 1301 is further configured to receive a response to the notification sent by the service enable architecture layer server.

[0334] In one embodiment, the second communication interface 1301 is further configured to:

[0335] The terminal receives a second indication message sent by the service enabling architecture layer server; the second indication message indicates that the terminal can use the second rule configured by the non-service enabling architecture layer server, or indicates that the terminal cannot use the second rule configured by the non-service enabling architecture layer server.

[0336] When the second indication information indicates that the terminal can use the second rule configured by the non-service-enabled architecture layer server, the notification is sent to the service-enabled architecture layer server.

[0337] It should be noted that the specific processing procedures of the second communication interface 1301 and the second processor 1302 can be understood by referring to the above method.

[0338] Of course, in practical applications, the various components in the terminal are coupled together through the bus system 1304. It can be understood that the bus system 1304 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 1304 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, in... Figure 13 The general designated all buses as Bus System 1304.

[0339] The second memory 1103 in this embodiment is used to store various types of data to support the operation of the terminal 1300. Examples of such data include any computer program used to operate on the terminal 1300.

[0340] The methods disclosed in the embodiments of this application can be applied to, or implemented by, the second processor 1302. The second processor 1302 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by the integrated logic circuitry of the hardware or by instructions in the form of software within the second processor 1302. The second processor 1302 may be a general-purpose processor, a DSP, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The second processor 1302 can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, specifically a second memory 1303. The second processor 1302 reads information from the second memory 1303 and, in conjunction with its hardware, completes the steps of the aforementioned method.

[0341] In an exemplary embodiment, terminal 1300 may be implemented by one or more ASICs, DSPs, PLDs, CPLDs, FPGAs, general-purpose processors, controllers, MCUs, microprocessors, or other electronic components to perform the aforementioned method.

[0342] It is understood that the memories (first memory 1203, second memory 1303) in the embodiments of this application can be volatile memory or non-volatile memory, or both. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM); magnetic surface memory can be disk storage or magnetic tape storage. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), SyncLink Dynamic Random Access Memory (SLDRAM), and Direct Rambus Random Access Memory (DRRAM).The memories described in the embodiments of this application are intended to include, but are not limited to, these and any other suitable types of memories.

[0343] To implement the method of the embodiments of this application, the embodiments of this application also provide an information transmission system, such as... Figure 14 As shown, the system includes: SEALS1401 and terminal 1402.

[0344] It should be noted that the specific processing procedures of SEALS1401 and terminal 1402 have been described in detail above and will not be repeated here.

[0345] In an exemplary embodiment, this application also provides a storage medium, namely a computer storage medium, specifically a computer-readable storage medium. For example, it may include a first memory 1203 storing a computer program, which can be executed by the first processor 1202 of the SEALS 1200 to complete the steps described in the aforementioned SEALS-side method. Another example is a second memory 1303 storing a computer program, which can be executed by the second processor 1302 of the terminal 1300 to complete the steps described in the aforementioned terminal-side method. The computer-readable storage medium may be ROM, PROM, EPROM, EEPROM, FRAM, Flash Memory, magnetic surface memory, optical disc, or CD-ROM; the magnetic surface memory may be a disk storage device or a magnetic tape storage device.

[0346] It should be noted that terms such as "first" and "second" are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0347] Furthermore, the technical solutions described in the embodiments of this application can be combined arbitrarily without conflict.

[0348] The above description is merely a preferred embodiment of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. An information transmission method, characterized in that, Applied to the server-side of the service-enabled architecture layer, including: Receive a first request sent by the vertical industry application layer server, the first request being used to request the configuration of a first rule for the terminal; Configure the first rule for the terminal using the application plane interface; The method further includes: Send a second indication message to the terminal; the second indication message indicates that the terminal can use the second rule configured by the non-service enabled architecture layer server, or indicates that the terminal cannot use the second rule configured by the non-service enabled architecture layer server. When the second indication information indicates that the terminal can use the second rule configured on the non-service-enabled architecture layer server, a notification sent by the terminal is received. The notification is used to notify the updating of the terminal's local rules on the service-enabled architecture layer server, and the notification includes the terminal's second rule. Update the rules of the local terminal using the second rule.

2. The method according to claim 1, characterized in that, The method further includes: Verify the first request; After successful verification, the first rule is configured for the terminal via the application plane interface.

3. The method according to claim 1, characterized in that, If the terminal has already registered with the service enablement architecture layer server, configure the first rule for the terminal through the application plane interface.

4. The method according to claim 3, characterized in that, The method further includes: If the terminal is not registered with the service enablement architecture layer server, the first rule is configured for the terminal through the network interface.

5. The method according to claim 3, characterized in that, The method further includes: Receive a second request sent by the terminal, the second request being used to request registration, the second request containing the terminal's registration information; Save the registration information of the terminal.

6. The method according to claim 5, characterized in that, The method further includes: Send a response to the second request to the terminal.

7. The method according to claim 1, characterized in that, When configuring the first rule for the terminal via an application plane interface, the method further includes: The relevant information of the first rule is sent to the terminal through the application plane interface; the relevant information includes at least one of the following: Service-enabled architecture layer server-side identifier; Vertical industry application layer server-side identifier; First indication information; the first indication information is used to indicate the configuration method of the first rule.

8. The method according to claim 1, characterized in that, The method further includes: A response to sending the notification to the terminal.

9. An information transmission method, characterized in that, Applied to terminals, including: The service enablement architecture layer server receives a first rule configured through the application plane interface; wherein the first rule is configured by the service enablement architecture layer server based on a first request sent by the vertical industry application layer server; the first request is used to request the configuration of the first rule for the terminal. Save the first rule; The method further includes: The terminal receives a second indication message sent by the service enabling architecture layer server; the second indication message indicates that the terminal can use the second rule configured by the non-service enabling architecture layer server, or indicates that the terminal cannot use the second rule configured by the non-service enabling architecture layer server. When the second indication information indicates that the terminal can use the second rule configured on the non-service-enabled architecture layer server, the notification is sent to the service-enabled architecture layer server. The notification is used to notify the server to update the rules of the terminal locally on the service-enabled architecture layer server, and the notification includes the second rule of the terminal.

10. The method according to claim 9, characterized in that, If the terminal has already registered with the service enablement architecture layer server, it receives the first rule configured by the application plane interface of the service enablement architecture layer server.

11. The method according to claim 10, characterized in that, The method further includes: If the terminal is not registered with the service enabling architecture layer server, it receives the first rule configured by the service enabling architecture layer server through the network interface.

12. The method according to claim 10, characterized in that, The method further includes: A second request is sent to the service enablement architecture layer server. The second request is used to request registration and includes the registration information of the terminal.

13. The method according to claim 12, characterized in that, The method further includes: Receive the response to the second request sent by the service enable architecture layer server.

14. The method according to claim 9, characterized in that, When receiving the first rule configured by the service-enabled architecture layer server through the application plane interface, the method further includes: The service enablement architecture layer server receives information related to the first rule sent through the application plane interface; the information includes at least one of the following: Service-enabled architecture layer server-side identifier; Vertical industry application layer server-side identifier; First indication information; the first indication information is used to indicate the configuration method of the first rule.

15. The method according to claim 9, characterized in that, The method further includes: Receive the response to the notification sent by the service enable architecture layer server.

16. An information transmission device, characterized in that, include: The first receiving unit is configured to receive a first request sent by the vertical industry application layer server, wherein the first request is used to request the configuration of a first rule for the terminal. A configuration unit is configured to configure the first rule for the terminal via an application plane interface; The device further includes: a processing unit; the processing unit is configured to: Send a second indication message to the terminal; the second indication message indicates that the terminal can use the second rule configured by the non-service enabled architecture layer server, or indicates that the terminal cannot use the second rule configured by the non-service enabled architecture layer server. When the second indication information indicates that the terminal can use the second rule configured on the non-service-enabled architecture layer server, a notification sent by the terminal is received. The notification is used to notify the updating of the terminal's local rules on the service-enabled architecture layer server, and the notification includes the terminal's second rule. Update the rules of the local terminal using the second rule.

17. An information transmission device, characterized in that, include: The second receiving unit is configured to receive a first rule configured by the service enablement architecture layer server through the application plane interface; wherein the first rule is configured by the service enablement architecture layer server based on a first request sent by the vertical industry application layer server; the first request is used to request the configuration of the first rule for the terminal. A storage unit is used to store the first rule; The device further includes: a transmitting unit; The second receiving unit is further configured to receive second indication information sent by the service enabling architecture layer server; the second indication information indicates that the terminal can use the second rule configured by the non-service enabling architecture layer server, or indicates that the terminal cannot use the second rule configured by the non-service enabling architecture layer server. The sending unit is configured to send the notification to the service-enabled architecture layer server when the second indication information indicates that the terminal can use the second rule configured on the non-service-enabled architecture layer server. The notification is used to notify the server to update the rules of the terminal locally on the service-enabled architecture layer server, and the notification includes the second rule of the terminal.

18. A service-enabled architecture layer server, characterized in that, include: A first processor and a first communication interface; wherein... The first communication interface is used to receive a first request sent by the vertical industry application layer server, the first request being used to request the configuration of a first rule for the terminal; The first processor is configured to configure the first rule for the terminal via an application plane interface using the first communication interface; The first communication interface is further configured to send second indication information to the terminal; the second indication information indicates that the terminal can use the second rule configured by the non-service-enabled architecture layer server, or indicates that the terminal cannot use the second rule configured by the non-service-enabled architecture layer server; when the second indication information indicates that the terminal can use the second rule configured by the non-service-enabled architecture layer server, a notification sent by the terminal is received, the notification being used to notify the updating of the terminal's rules on the local server of the service-enabled architecture layer, the notification including the terminal's second rule; The first processor is further configured to update the rules of the local terminal using the second rule.

19. A terminal, characterized in that, include: A second processor and a second communication interface; wherein... The second communication interface is used to receive a first rule configured by the service enablement architecture layer server through the application plane interface; wherein, the first rule is configured by the service enablement architecture layer server based on a first request sent by the vertical industry application layer server; the first request is used to request the configuration of the first rule for the terminal; The second processor is used to store the first rule; The second communication interface is further configured to receive second indication information sent by the service enabling architecture layer server; the second indication information indicates that the terminal can use the second rule configured by the non-service enabling architecture layer server, or indicates that the terminal cannot use the second rule configured by the non-service enabling architecture layer server; when the second indication information indicates that the terminal can use the second rule configured by the non-service enabling architecture layer server, the notification is sent to the service enabling architecture layer server, the notification is used to notify the update of the terminal's local rules on the service enabling architecture layer server, and the notification includes the terminal's second rule.

20. A storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 8, or the steps of the method according to any one of claims 9 to 15.

Images