Business identification conversion, information configuration method, device and communication equipment

Abstract

The embodiment of the present invention discloses a service identifier conversion, information configuration method, device and communication equipment, which belongs to the field of communication technology. The specific implementation scheme includes: obtaining a first service identifier of an application service; sending the first service identifier to a slice service platform, and the slice service platform determines the target service identifier corresponding to the first service identifier; wherein the target service identifier is a unique identifier of the application service in the slice network; receiving the target service identifier from the slice service platform. According to this scheme, the terminal can obtain the unique identifier of the application service in the slice network with the help of the slice service platform, so that even if the identifiers of the application service in the terminal and the slice network are different, the terminal can complete the mapping of the application service to the slice network, thereby obtaining the service of the slice network.

Description

Technical Field

[0001] The present invention belongs to the field of communication technology, and in particular relates to a service identification conversion, information configuration method, device and communication equipment. Background Art

[0002] Network slicing is a new capability defined in the communication system. It is a logical "dedicated network" that provides end-to-end services based on unified network facilities. In network slicing, the identification of application services can be determined using preset rules. However, in the terminal, the identification of the same application service can have different definitions on different terminal operating systems. As a result, the identification of the same application service in the terminal and the slice network may be different, resulting in the terminal being unable to complete the mapping of the application service to the slice network and unable to obtain the services of the slice network. Summary of the invention

[0003] The purpose of the embodiments of the present invention is to provide a service identifier conversion, information configuration method, device and communication equipment to solve the current problem that the terminal cannot complete the mapping of application services to slice networks due to different identifiers of the same application service in the terminal and the slice network.

[0004] In order to solve the above-mentioned technical problems, the present invention is achieved as follows:

[0005] In a first aspect, an embodiment of the present invention provides a method for converting a service identifier, which is executed by a terminal, and the method includes:

[0006] Obtaining a first service identifier of an application service;

[0007] Sending the first service identifier to the slice service platform, and the slice service platform determining the target service identifier corresponding to the first service identifier; wherein the target service identifier is a unique identifier of the application service in the slice network;

[0008] Receive the target business identifier from the slice service platform.

[0009] Optionally, the method further includes:

[0010] Receive configuration information from a network side device; wherein the configuration information includes: a mapping relationship between a slice identifier and a service identifier group of the application service;

[0011] The sending of the first service identifier to the slicing service platform includes:

[0012] If the service identification group does not include the first service identification, the first service identification is sent to the slice service platform.

[0013] Optionally, the method further includes:

[0014] In the case where the service identification group includes the first service identification, the slice network corresponding to the application service is determined according to the slice identification corresponding to the first service identification.

[0015] Optionally, the service identification group includes at least one of the following:

[0016] The target service identifier;

[0017] Multiple second service identifiers; wherein the multiple second service identifiers are service identifiers of the application service in different terminal operating systems.

[0018] In a second aspect, an embodiment of the present invention provides a method for converting a service identifier, which is performed by a slice service platform, and the method includes:

[0019] receiving a first service identifier of an application service from a terminal;

[0020] Determine a target service identifier corresponding to the first service identifier; wherein the target service identifier is a unique identifier of the application service in the slice network;

[0021] The target service identifier is sent to the terminal.

[0022] Optionally, the method further includes:

[0023] Acquire multiple second service identifiers; wherein the multiple second service identifiers are service identifiers of the application service in different terminal operating systems;

[0024] Recording a mapping relationship between the target service identifier and the plurality of second service identifiers;

[0025] The step of determining the target service identifier corresponding to the first service identifier includes:

[0026] According to the mapping relationship, a target service identifier corresponding to the first service identifier is determined.

[0027] In a third aspect, an embodiment of the present invention provides an information configuration method, which is performed by a network side device, and the method includes:

[0028] Send configuration information to the terminal;

[0029] The configuration information includes: a mapping relationship between a slice identifier and a service identifier group of an application service; the service identifier group includes at least one of the following:

[0030] Target service identifier; wherein the target service identifier is a unique identifier of the application service in the slice network;

[0031] Multiple second service identifiers; wherein the multiple second service identifiers are service identifiers of the application service in different terminal operating systems.

[0032] Optionally, the method further includes:

[0033] Obtain the multiple second service identifiers and / or the target service identifier from the slicing service platform.

[0034] In a fourth aspect, an embodiment of the present invention provides a device for converting a service identifier, which is applied to a terminal, and the device includes:

[0035] A first acquisition module, used to acquire a first service identifier of an application service;

[0036] A first sending module, used to send the first service identifier to a slice service platform, and the slice service platform determines a target service identifier corresponding to the first service identifier; wherein the target service identifier is a unique identifier of the application service in the slice network;

[0037] The first receiving module is used to receive the target business identifier from the slice service platform.

[0038] Optionally, the device further comprises:

[0039] A second receiving module is used to receive configuration information from a network side device; wherein the configuration information includes: a mapping relationship between a slice identifier and a service identifier group of the application service;

[0040] The first sending module is specifically used for:

[0041] If the service identification group does not include the first service identification, the first service identification is sent to the slice service platform.

[0042] Optionally, the device further comprises:

[0043] The first determination module is used to determine the slice network corresponding to the application service according to the slice identifier corresponding to the first service identifier when the service identifier group includes the first service identifier.

[0044] Optionally, the service identification group includes at least one of the following:

[0045] The target service identifier;

[0046] Multiple second service identifiers; wherein the multiple second service identifiers are service identifiers of the application service in different terminal operating systems.

[0047] In a fifth aspect, an embodiment of the present invention provides a device for converting a service identifier, which is applied to a slicing service platform, and the device includes:

[0048] A third receiving module, used to receive a first service identifier of an application service from a terminal;

[0049] A second determination module is used to determine a target service identifier corresponding to the first service identifier; wherein the target service identifier is a unique identifier of the application service in the slice network;

[0050] The second sending module is used to send the target service identifier to the terminal.

[0051] Optionally, the device further comprises:

[0052] A second acquisition module is used to acquire multiple second service identifiers; wherein the multiple second service identifiers are service identifiers of the application service in different terminal operating systems;

[0053] A recording module, used for recording the mapping relationship between the target service identifier and the plurality of second service identifiers;

[0054] The second determining module is specifically used for:

[0055] According to the mapping relationship, a target service identifier corresponding to the first service identifier is determined.

[0056] In a sixth aspect, an embodiment of the present invention provides an information configuration device, which is applied to a network side device, and the device includes:

[0057] A third sending module, used to send configuration information to the terminal;

[0058] The configuration information includes: a mapping relationship between a slice identifier and a service identifier group of an application service; the service identifier group includes at least one of the following:

[0059] Target service identifier; wherein the target service identifier is a unique identifier of the application service in the slice network;

[0060] Multiple second service identifiers; wherein the multiple second service identifiers are service identifiers of the application service in different terminal operating systems.

[0061] Optionally, the device further comprises:

[0062] The third acquisition module is used to obtain the multiple second service identifiers and / or the target service identifier from the slicing service platform.

[0063] In the seventh aspect, an embodiment of the present invention provides a communication device, which includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method described in the first aspect, or implements the steps of the method described in the second aspect, or implements the steps of the method described in the third aspect.

[0064] In an eighth aspect, an embodiment of the present invention provides a computer-readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented, or the steps of the method described in the third aspect are implemented.

[0065] In an embodiment of the present invention, by obtaining a first service identifier of an application service, the first service identifier is sent to a slice service platform, and the slice service platform determines a target service identifier corresponding to the first service identifier, which is a unique identifier of the application service in the slice network, and receives the target service identifier from the slice service platform. This allows the terminal to obtain a unique identifier of the application service in the slice network with the help of the slice service platform, so that even if the identifiers of the application service in the terminal and the slice network are different, the terminal can complete the mapping of the application service to the slice network, thereby obtaining the service of the slice network. BRIEF DESCRIPTION OF THE DRAWINGS

[0066] Figure 1 is a schematic diagram of the architecture of a service identifier conversion system in an embodiment of the present invention;

[0067] Figure 2 is a flow chart of a method for converting a service identifier provided by an embodiment of the present invention;

[0068] Figure 3 is a flow chart of another service identifier conversion method provided by an embodiment of the present invention;

[0069] Figure 4 is a flow chart of an information configuration method provided by an embodiment of the present invention;

[0070] Figure 5 It is a structural schematic diagram of a service identifier conversion device provided by an embodiment of the present invention;

[0071] Figure 6 It is a structural schematic diagram of another service identifier conversion device provided by an embodiment of the present invention;

[0072] Figure 7 is a structural diagram of an information configuration device provided by an embodiment of the present invention;

[0073] Figure 8 It is a structural diagram of a communication device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0074] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0075] The terms "first", "second", etc. in the specification and claims of the present invention are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first", "second", etc. are generally of the same type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally indicates that the objects associated with each other are in an "or" relationship.

[0076] In order to facilitate understanding of the embodiments of the present invention, the following contents are first described.

[0077] In network slicing, one of the identifiers of application services is the application descriptor (hereinafter referred to as AppId), which is defined as OSId+OSAppId in the standard. OSId is currently clearly defined in the standard, but AppId is not. However, in actual terminals, AppId has different definitions on different operating systems. Some are 128 bits, and some are strings in a specific format, which have not yet been unified. In other words, for the same application service, different AppIds may correspond to different terminal operating systems, and the naming rules are customized by the operating system.

[0078] The slice configuration scheme refers to the mapping relationship between one or more services and slices. For example, the mapping relationship can associate services, service identification types, service identification values, slice identification (such as signaling service type (SST) and slice differentiator (SD)), packet data unit (PDU) session and / or PDU corresponding quality of service (QoS) configuration and other elements.

[0079] In a specific example, the terminal identifies and maps the service to the service identification value, and the mapping of the service identification value to the slice identification is configured by the network side device through the User Equipment Routing Selection Policy (URSP) rule.

[0080] Optionally, the network side device can inform the terminal of the current slice configuration scheme through URSP configuration signaling. If a slice service is enabled for an application service and the service identification type is AppID, the network side device can inform the terminal of the AppID value corresponding to the application service, the slice identification corresponding to the AppID, etc. in the URSP configuration signaling.

[0081] When configuring the URSP rule, the network-side device may adopt a standard or custom AppId naming rule, such as Rule A. When the application service runs in the terminal operating system, the AppId naming rule defined by the operating system is adopted, such as Rule B. Since Rule A and Rule B are not unified, the terminal will not be able to match the currently running application service with the AppId configured in the URSP rule, that is, the same application service will have different identifiers in the terminal and the slice network, which will cause the terminal to be unable to complete the mapping of the application service to the slice network.

[0082] In order to solve the problem that the terminal cannot complete the mapping of the application service to the slice network due to the different identifiers of the same application service in the terminal and the slice network, an embodiment of the present invention proposes a service identifier conversion system, and the architecture diagram of the system is as follows Figure 1 As shown, the system includes at least a terminal 11, a slice service platform 12 and a network side device 13.

[0083] Among them, for the application service currently running in the terminal 11, the operating system in the terminal 11 can adopt a custom identification naming rule to obtain the identification of the application service, such as AppId. The terminal 11 can represent multiple terminals with different operating systems. For the service identification defined in different terminal operating systems, it can be recorded as service identification 1, service identification 2, ..., service identification N, where N represents a positive integer.

[0084] The slice service platform 12 can define the identification naming rules or numbering rules of the application service in the slice network, such as the identification of the application service in the slice network is recorded as the target service identification, that is, the target service identification is the unique identification of the application service in the slice network. In addition, when a slice service is opened for an application service in the terminal 11, the identification of the application service can be registered with the slice service platform 12, such as the service identification 1, service identification 2, ..., service identification N of the application service in different terminal operating systems, and stored in the slice service platform 12. The storage method can be the mapping relationship between the service identification of the application service in different terminal operating systems and the target service identification. During the application service registration process, the slice service platform 12 can ensure the uniqueness of the newly registered application service identification by retrieving the registered application service identification.

[0085] In a specific example, as shown in Table 1 below, the mapping relationship between the service identifier of the application service xxx in different terminal operating systems and the target service identifier may be:

[0086] Table 1

[0087]

[0088] The network side device 13 represents a device in a network with slicing capability. The network side device 13 can perform signaling and data interaction with the terminal 11 through the communication module in the terminal 11. The network side device 13 can obtain the mapping relationship between the service identifier of the above-mentioned application service in different terminal operating systems and the target service identifier from the slicing service platform 12.

[0089] Optionally, during the process of powering on and attaching the terminal 11, the network side device 13 may send configuration information such as URSP rules to the terminal 11. The configuration information may include: a mapping relationship between a slice identifier and a service identifier group of an application service. Taking the URSP rule as an example, the following configuration method may be used:

[0090] 1) Configuration method 1: The mapping relationship between the target service identifier and the slice identifier is configured in the URSP rule, that is, the service identifier group of the application service only includes the target service identifier.

[0091] 2) Configuration method 2: The mapping relationship between all service identifiers and slice identifiers of the application service is configured in the URSP rule, that is, the service identifier group of the application service includes the target service identifier and all values ​​of service identifier 1 to service identifier N. In a specific example, the OS APP ID in the URSP rule is defined as a structure or array, as shown in Table 2 below:

[0092] Table 2

[0093]

[0094] 3) Configuration method 3: Similar to configuration method 2, the mapping relationship between the partial service identifier and the slice identifier of the application service is configured in the URSP rule, that is, the service identifier group of the application service includes the target service identifier and partial values ​​of service identifier 1 to service identifier N. The OS APP ID in the URSP rule is defined as a structure or array.

[0095] Optional, based on Figure 1 The conversion process of the business identifier in the architecture diagram may include:

[0096] S1: When the terminal 11 runs an application service, the operating system in the terminal 11 obtains the AppId of the application service in the current operating system. The AppId must be one of service identifiers 1 to N, which is recorded as service identifier A.

[0097] S2.1: If configured based on the above configuration method 1, the operating system in the terminal 11 passes the service identifier A to the identifier conversion module, and the identifier conversion module sends the service identifier A to the slice service platform 12.

[0098] S2.2: The slicing service platform 12 queries the corresponding target service identifier based on the pre-stored mapping relationship between the service identifier of the application service in different terminal operating systems and the target service identifier, using service identifier A as an index. If the query is successful, the target service identifier corresponding to service identifier A is returned to the identifier conversion module; if the query fails, a query failure instruction is returned.

[0099] S2.3: If the identifier conversion module in the terminal 11 successfully obtains the target service identifier, it returns the obtained target service identifier to the operating system; or, if the obtained query failure instruction is returned, it returns the query failure result to the operating system.

[0100] S2.4: If the operating system in the terminal 11 obtains the target service identifier, it matches the obtained target service identifier with the slice identifier in the URSP rule of the network configuration, maps the application service to the slice network, and sends the data of the application service to the corresponding slice network in subsequent data transmission; or, if a query failure result is obtained, it means that the application service has no corresponding slice service, and the operation ends.

[0101] S3: Alternatively, if configured based on the above configuration method 2, the operating system in the terminal 11 can match the service identifier A with the slice identifier in the URSP rule of the network configuration. If the match is successful, the application service is mapped to the slice network, and the data of the application service is sent to the corresponding slice network in subsequent data transmission; or, if the match is unsuccessful, it means that the application service has no corresponding slice service, and the operation ends.

[0102] S4: Alternatively, if configured based on the above configuration method 3, the operating system in the terminal 11 can match the service identifier A with the slice identifier in the URSP rule of the network configuration. If the match is successful, the application service is mapped to the slice network, and the data of the application service is sent to the corresponding slice network in subsequent data transmission; or, if the match is unsuccessful, execute the above S2.1 to S2.4.

[0103] It should be noted that, in actual applications, the identification conversion module in the terminal 11 may be a separate module, such as an independent App, or may be integrated into an operating system.

[0104] See also Figure 2 , Figure 2 is a flow chart of a method for converting a service identifier provided by an embodiment of the present invention. The method is executed by a terminal. The terminal may be specifically as follows Figure 1 As described in the examples. Figure 2 As shown, the method comprises the following steps:

[0105] Step 21: Obtain the first service identifier of the application service.

[0106] In this embodiment, the first service identifier represents the identifier of the application service in the current terminal operating system, which is determined based on the identifier naming rule defined by the current terminal operating system.

[0107] Step 22: Send the first business identifier to the slice service platform, and the slice service platform determines the target business identifier corresponding to the first business identifier.

[0108] The target service identifier is the unique identifier of the application service in the slice network. When determining the target service identifier corresponding to the first service identifier, the slice service platform can query the corresponding target service identifier based on the pre-stored mapping relationship between the service identifier and the target service identifier of the application service in different terminal operating systems, using the first service identifier as an index.

[0109] Step 23: Receive the target business identifier from the slice service platform.

[0110] The service identifier conversion method of the embodiment of the present invention obtains the first service identifier of the application service, sends the first service identifier to the slice service platform, and the slice service platform determines the target service identifier corresponding to the first service identifier, which is the unique identifier of the application service in the slice network, and receives the target service identifier from the slice service platform. The terminal can obtain the unique identifier of the application service in the slice network with the help of the slice service platform, so that even if the identifiers of the application service in the terminal and the slice network are different, the terminal can complete the mapping of the application service to the slice network, thereby obtaining the service of the slice network.

[0111] Optionally, the conversion method in the embodiment of the present invention may further include:

[0112] The terminal receives configuration information from the network side device; wherein the configuration information includes: a mapping relationship between a slice identifier and a service identifier group of an application service. It is understandable that in this embodiment, the network side device can be configured using configuration method 1, configuration method 2 or configuration method 3 as described above.

[0113] Further, the above step 22 may include: when the service identification group does not include the first service identification, that is, when the mapping relationship configured by the network side device does not include the mapping relationship between the slice identification and the first service identification, the first service identification is sent to the slice service platform, so that the slice service platform determines the target service identification corresponding to the first service identification and sends it to the terminal. In this way, the terminal can complete the mapping of the corresponding application service to the slice network according to the obtained target service identification, thereby obtaining the service of the slice network.

[0114] Alternatively, when the service identification group includes a first service identification, the terminal can determine the slice network corresponding to the application service based on the slice identification corresponding to the first service identification, thereby completing the mapping of the application service to the slice network, and thus obtaining the service of the slice network.

[0115] Optionally, the service identification group of the application service in the above mapping relationship may include at least one of the following:

[0116] Target business identifier;

[0117] Multiple second service identifiers; wherein the multiple second service identifiers are service identifiers of the application service in different terminal operating systems.

[0118] See also Figure 3 , Figure 3 is a flowchart of another method for converting a service identifier provided by an embodiment of the present invention. The method is executed by a slicing service platform. The slicing service platform may be specifically as follows Figure 1 As described in the examples. Figure 3 As shown, the method comprises the following steps:

[0119] Step 31: Receive a first service identifier of an application service from a terminal.

[0120] In this embodiment, the first service identifier represents the identifier of the application service in the current terminal operating system, which is determined based on the identifier naming rule defined by the current terminal operating system.

[0121] Step 32: Determine the target service identifier corresponding to the first service identifier.

[0122] The target service identifier is the unique identifier of the application service in the slice network. When determining the target service identifier corresponding to the first service identifier, the slice service platform can query the corresponding target service identifier based on the pre-stored mapping relationship between the service identifier and the target service identifier of the application service in different terminal operating systems, using the first service identifier as an index.

[0123] Step 33: Send the target service identifier to the terminal.

[0124] The service identifier conversion method of the embodiment of the present invention receives the first service identifier of the application service from the terminal, determines the target service identifier corresponding to the first service identifier, and sends the target service identifier to the terminal, so that the terminal can obtain the unique identifier of the application service in the slice network with the help of the slice service platform, so that even if the identifiers of the application service in the terminal and the slice network are different, the terminal can complete the mapping of the application service to the slice network, thereby obtaining the service of the slice network.

[0125] Optionally, the conversion method in the embodiment of the present invention may further include:

[0126] The slicing service platform obtains multiple second service identifiers; wherein the multiple second service identifiers are service identifiers of the application service in different terminal operating systems;

[0127] The slice service platform records the mapping relationship between the target business identifier and multiple second business identifiers.

[0128] Furthermore, the above step 32 may include: the slice service platform determines the target service identifier corresponding to the first service identifier according to the mapping relationship between the recorded target service identifier and multiple second service identifiers. Thus, with the help of the recorded mapping relationship, the slice service platform can quickly obtain the unique identifier of the application service in the slice network.

[0129] See also Figure 4 , Figure 4 is a flowchart of an information configuration method provided by an embodiment of the present invention, the method is executed by a network side device, and the network side device can be specifically as follows Figure 1 As described in the examples. Figure 4 As shown, the method comprises the following steps:

[0130] Step 41: Send configuration information to the terminal.

[0131] The configuration information includes: a mapping relationship between a slice identifier and a service identifier group of an application service; the service identifier group includes at least one of the following:

[0132] Target service identifier; wherein the target service identifier is a unique identifier of the application service in the slice network;

[0133] Multiple second service identifiers; wherein the multiple second service identifiers are service identifiers of the application service in different terminal operating systems.

[0134] Optionally, the network side device can obtain the multiple second service identifiers and / or the target service identifiers from the slicing service platform to implement the configuration of the terminal.

[0135] The information configuration method of an embodiment of the present invention can enable the terminal to obtain a unique identifier of an application service in a slice network by sending configuration information to the terminal. Therefore, even if the identifiers of the application service in the terminal and the slice network are different, the terminal can complete the mapping of the application service to the slice network, thereby obtaining the service of the slice network.

[0136] See also Figure 5 , Figure 5 is a schematic diagram of a structure of a service identifier conversion device provided by an embodiment of the present invention, the device is applied to a terminal, such as Figure 5 As shown, the service identifier conversion device 50 includes:

[0137] A first acquisition module 51, used to acquire a first service identifier of an application service;

[0138] A first sending module 52 is used to send the first service identifier to the slice service platform, and the slice service platform determines the target service identifier corresponding to the first service identifier; wherein the target service identifier is a unique identifier of the application service in the slice network;

[0139] The first receiving module 53 is used to receive the target business identifier from the slice service platform.

[0140] Optionally, the service identifier conversion device 50 further includes:

[0141] A second receiving module is used to receive configuration information from a network side device; wherein the configuration information includes: a mapping relationship between a slice identifier and a service identifier group of the application service;

[0142] The first sending module 52 is specifically used for:

[0143] If the service identification group does not include the first service identification, the first service identification is sent to the slice service platform.

[0144] Optionally, the service identifier conversion device 50 further includes:

[0145] The first determination module is used to determine the slice network corresponding to the application service according to the slice identifier corresponding to the first service identifier when the service identifier group includes the first service identifier.

[0146] Optionally, the service identification group includes at least one of the following:

[0147] The target service identifier;

[0148] Multiple second service identifiers; wherein the multiple second service identifiers are service identifiers of the application service in different terminal operating systems.

[0149] It is understandable that the service identifier conversion device 50 of the embodiment of the present invention can achieve the above Figure 2 The various processes of the method embodiment shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0150] See also Figure 6 , Figure 6 is a schematic diagram of a structure of a service identifier conversion device provided by an embodiment of the present invention, and the device is applied to a slicing service platform, such as Figure 6 As shown, the service identifier conversion device 60 may include:

[0151] The third receiving module 61 is used to receive a first service identifier of an application service from a terminal;

[0152] A second determination module 62 is used to determine a target service identifier corresponding to the first service identifier; wherein the target service identifier is a unique identifier of the application service in the slice network;

[0153] The second sending module 63 is configured to send the target service identifier to the terminal.

[0154] Optionally, the service identifier conversion device 60 further includes:

[0155] A second acquisition module is used to acquire multiple second service identifiers; wherein the multiple second service identifiers are service identifiers of the application service in different terminal operating systems;

[0156] A recording module, used for recording the mapping relationship between the target service identifier and the plurality of second service identifiers;

[0157] The second determining module 62 is specifically used for:

[0158] According to the mapping relationship, a target service identifier corresponding to the first service identifier is determined.

[0159] It is understandable that the service identifier conversion device 60 of the embodiment of the present invention can achieve the above Figure 3 The various processes of the method embodiment shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0160] See also Figure 7 , Figure 7 is a schematic diagram of the structure of an information configuration device provided by an embodiment of the present invention, the device is applied to a network side device, such as Figure 7 As shown, the information configuration device 70 may include:

[0161] The third sending module 71 is used to send configuration information to the terminal;

[0162] The configuration information includes: a mapping relationship between a slice identifier and a service identifier group of an application service; the service identifier group includes at least one of the following:

[0163] Target service identifier; wherein the target service identifier is a unique identifier of the application service in the slice network;

[0164] Multiple second service identifiers; wherein the multiple second service identifiers are service identifiers of the application service in different terminal operating systems.

[0165] Optionally, the information configuration device 70 further includes:

[0166] The third acquisition module is used to obtain the multiple second service identifiers and / or the target service identifier from the slicing service platform.

[0167] It is understandable that the information configuration device 70 of the embodiment of the present invention can implement the above Figure 4 The various processes of the method embodiment shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0168] Optional, such as Figure 8 As shown, the embodiment of the present invention further provides a communication device 80, including a processor 81, a memory 82, and a program or instruction stored in the memory 82 and executable on the processor 81. For example, when the communication device 80 is a terminal, the program or instruction can be executed by the processor 81 to achieve the above Figure 2The various processes of the method embodiment shown in the figure can achieve the same technical effect; or, when the communication device 80 is a slicing service platform, the program or instruction can be executed by the processor 81 to achieve the above Figure 3 Alternatively, when the communication device 80 is a network side device, the program or instruction can be executed by the processor 81 to achieve the above Figure 4 The various processes of the method embodiment shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0169] An embodiment of the present invention also provides a computer-readable storage medium on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned service identifier conversion method or information configuration method embodiment can be implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0170] Computer readable media include permanent and non-permanent, removable and non-removable media, and can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0171] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0172] The serial numbers of the above embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0173] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for enabling a service classification device (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in each embodiment of the present invention.

[0174] The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principle of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A method for converting a service identifier, characterized in that: Executed by a terminal, the method includes: Acquire a first service identifier of an application service, where the first service identifier is an identifier of the application service in an operating system of the terminal; Sending the first service identifier to the slice service platform, and the slice service platform determining the target service identifier corresponding to the first service identifier; wherein the target service identifier is a unique identifier of the application service in the slice network; Receive the target business identifier from the slice service platform.

2. The method according to claim 1, characterized in that The method further comprises: Receive configuration information from a network side device; wherein the configuration information includes: a mapping relationship between a slice identifier and a service identifier group of the application service; The sending of the first service identifier to the slicing service platform includes: If the service identification group does not include the first service identification, the first service identification is sent to the slice service platform.

3. The method according to claim 2, characterized in that The method further comprises: In the case where the service identification group includes the first service identification, the slice network corresponding to the application service is determined according to the slice identification corresponding to the first service identification.

4. The method according to claim 2, characterized in that: The service identification group includes at least one of the following: The target service identifier; Multiple second service identifiers; wherein the multiple second service identifiers are service identifiers of the application service in different terminal operating systems.

5. A method for converting a service identifier, characterized in that: Executed by a slicing service platform, the method includes: receiving a first service identifier of an application service from a terminal, where the first service identifier is an identifier of the application service in an operating system of the terminal; Determine a target service identifier corresponding to the first service identifier; wherein the target service identifier is a unique identifier of the application service in the slice network; The target service identifier is sent to the terminal.

6. The method according to claim 5, characterized in that The method further comprises: Acquire multiple second service identifiers; wherein the multiple second service identifiers are service identifiers of the application service in different terminal operating systems; Recording a mapping relationship between the target service identifier and the plurality of second service identifiers; The step of determining the target service identifier corresponding to the first service identifier includes: According to the mapping relationship, a target service identifier corresponding to the first service identifier is determined.

7. An information configuration method, characterized in that: The method is performed by a network side device and includes: Send configuration information to the terminal; The configuration information includes: a mapping relationship between a slice identifier and a service identifier group of an application service; the service identifier group includes at least one of the following: Target service identifier; wherein the target service identifier is a unique identifier of the application service in the slice network; Multiple second service identifiers; wherein the multiple second service identifiers are service identifiers of the application service in different terminal operating systems.

8. The method according to claim 7, characterized in that The method further comprises: Obtain the multiple second service identifiers and / or the target service identifier from the slicing service platform.

9. A device for converting a service identifier, characterized in that: Applied to a terminal, the device comprises: A first acquisition module, used to acquire a first service identifier of an application service, where the first service identifier is an identifier of the application service in an operating system of the terminal; A first sending module, used to send the first service identifier to a slice service platform, and the slice service platform determines a target service identifier corresponding to the first service identifier; wherein the target service identifier is a unique identifier of the application service in the slice network; The first receiving module is used to receive the target business identifier from the slice service platform.

10. The device according to claim 9, characterized in that The device also includes: A second receiving module is used to receive configuration information from a network side device; wherein the configuration information includes: a mapping relationship between a slice identifier and a service identifier group of the application service; The first sending module is specifically used for: If the service identification group does not include the first service identification, the first service identification is sent to the slice service platform.

11. The device according to claim 10, characterized in that The device also includes: The first determination module is used to determine the slice network corresponding to the application service according to the slice identifier corresponding to the first service identifier when the service identifier group includes the first service identifier.

12. The device according to claim 10, characterized in that The service identification group includes at least one of the following: The target service identifier; Multiple second service identifiers; wherein the multiple second service identifiers are service identifiers of the application service in different terminal operating systems.

13. A device for converting a service identifier, characterized in that: Applied to a slicing service platform, the device comprises: A third receiving module is used to receive a first service identifier of an application service from a terminal, where the first service identifier is an identifier of the application service in an operating system of the terminal; A second determination module is used to determine a target service identifier corresponding to the first service identifier; wherein the target service identifier is a unique identifier of the application service in the slice network; The second sending module is used to send the target service identifier to the terminal.

14. The device according to claim 13, characterized in that The device also includes: A second acquisition module is used to acquire multiple second service identifiers; wherein the multiple second service identifiers are service identifiers of the application service in different terminal operating systems; A recording module, used for recording the mapping relationship between the target service identifier and the plurality of second service identifiers; The second determining module is specifically used for: According to the mapping relationship, a target service identifier corresponding to the first service identifier is determined.

15. An information configuration device, characterized in that: Applied to a network side device, the device comprises: A third sending module, used to send configuration information to the terminal; The configuration information includes: a mapping relationship between a slice identifier and a service identifier group of an application service; the service identifier group includes at least one of the following: Target service identifier; wherein the target service identifier is a unique identifier of the application service in the slice network; Multiple second service identifiers; wherein the multiple second service identifiers are service identifiers of the application service in different terminal operating systems.

16. The device according to claim 15, characterized in that The device also includes: The third acquisition module is used to obtain the multiple second service identifiers and / or the target service identifier from the slicing service platform.

17. A communication device, characterized in that: It comprises a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method for converting a service identifier as described in any one of claims 1 to 4, or the steps of the method for converting a service identifier as described in claim 5 or 6, or the steps of the information configuration method as described in claim 7 or 8.

18. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, it implements the steps of the service identifier conversion method as described in any one of claims 1 to 4, or the steps of the service identifier conversion method as described in claim 5 or 6, or the steps of the information configuration method as described in claim 7 or 8.

Images