CN113596948A

CN113596948A - Information reporting method, information sending method, information selecting method and related equipment

Info

Publication number: CN113596948A
Application number: CN202010367112.6A
Authority: CN
Inventors: 张艳霞; 谢振华
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2020-04-30
Filing date: 2020-04-30
Publication date: 2021-11-02
Anticipated expiration: 2040-04-30
Also published as: WO2021218911A1; CN117793839A; CN113596948B

Abstract

The application discloses an information reporting method, a sending method, a selecting method and related equipment, which belong to the technical field of communication, and the specific scheme comprises the following steps: and sending first slice routing information to an access network side device, wherein the first slice routing information is generated based on slice auxiliary information and is used for the access network side function to select a core network function. This application can make the access network side device easily select the core network function matched with the terminal through the first slice routing information.

Description

Information reporting method, information sending method, information selecting method and related equipment

Technical Field

The present application belongs to the field of communications technologies, and in particular, to an information reporting method, a sending method, a selecting method, and a related device.

Background

Some communication systems (e.g., 5G systems) support Network slices (Network slices), the Network slices supported or desired to be registered by different terminals may differ, and the Network slices supported by different core Network functions may also differ. However, currently, when selecting the core network function for the terminal, the access network device selects the core network function based on the network side information, which results in that the access network device easily selects the core network function that is not matched for the terminal.

Disclosure of Invention

The application provides an information reporting method, an information sending method, an information selecting method and related equipment, which can solve the problem that an access network side function is easy to select a unmatched core network function for a terminal.

In a first aspect, an embodiment of the present application provides an information reporting method, which is applied to a terminal, and includes:

and sending first slice routing information to an access network side device, wherein the first slice routing information is generated based on slice auxiliary information and is used for the access network side function to select a core network function.

In a second aspect, an embodiment of the present application provides an information sending method, which is applied to a core network function, and includes:

performing a sending operation, wherein the sending operation comprises at least one of:

sending slice auxiliary information to a terminal, wherein the slice auxiliary information is used for the terminal to generate first slice routing information to access network side equipment;

and sending second slice routing information to access network side equipment, wherein the second slice routing information is used for the access network side equipment to select core network side equipment according to the second slice routing information and the first slice routing information.

In a third aspect, an embodiment of the present application provides a method for selecting a core network function, which is applied to an access network side device, and includes:

receiving first slice routing information sent by a terminal;

and selecting a core network function according to the first slice routing information.

In a fourth aspect, an embodiment of the present application provides an information reporting apparatus, which is applied to a terminal, and includes:

a sending module, configured to send first slice routing information to an access network-side device, where the first slice routing information is generated based on slice auxiliary information, and is used for the access network-side device to select a core network function.

In a fifth aspect, an embodiment of the present application provides a core network function selection apparatus, which is applied to an access network side device, and includes:

the receiving module is used for receiving first slice routing information sent by a terminal;

and the selection module is used for selecting the core network function according to the first slice routing information.

In a sixth aspect, an embodiment of the present application provides a core network function selection apparatus, which is applied to an access network side device, and includes:

In a seventh aspect, an embodiment of the present application provides a terminal, including: the information reporting method comprises a memory, a processor and a program or an instruction which is stored on the memory and can be run on the processor, wherein the program or the instruction realizes the steps of the information reporting method when being executed by the processor.

In an eighth aspect, an embodiment of the present application provides a core network function, including: a memory, a processor, and a program or instructions stored on the memory and executable on the processor, the program or instructions, when executed by the processor, implementing the steps in the method of information transmission.

In a ninth aspect, an embodiment of the present application provides an access network-side device, including: a memory, a processor, and a program or instructions stored on the memory and executable on the processor, the program or instructions, when executed by the processor, implementing the steps in the core network function selection method.

In a tenth aspect, an embodiment of the present invention provides a readable storage medium, where the readable storage medium stores a program or instructions, and the program or instructions, when executed by a processor, implement the steps in the information reporting method, or the program or instructions, when executed by the processor, implement the steps in the information sending method, or the program or instructions, when executed by the processor, implement the steps in the core network function selection method.

In the embodiment of the application, first slice routing information is sent to an access network side device, wherein the first slice routing information is generated based on slice auxiliary information and is used for the access network side function to select a core network function. Therefore, the access network side equipment can easily select the core network function matched with the terminal through the first slice routing information.

Drawings

Fig. 1 is a block diagram of a network system to which an embodiment of the present application is applicable;

fig. 2 is a flowchart of an information reporting method according to an embodiment of the present application;

fig. 3 is a flowchart of an information sending method according to an embodiment of the present application;

fig. 4 is a flowchart of a core network function selection method according to an embodiment of the present application;

fig. 5 is a schematic diagram of core network selection provided in an embodiment of the present application;

fig. 6 is a structural diagram of an information reporting apparatus according to an embodiment of the present application;

fig. 7 is a structural diagram of another information reporting apparatus according to an embodiment of the present application;

fig. 8 is a structural diagram of an information transmission apparatus according to an embodiment of the present application;

fig. 9 is a structural diagram of another information transmission apparatus provided in an embodiment of the present application;

fig. 10 is a structural diagram of a core network function selection apparatus according to an embodiment of the present application;

fig. 11 is a structural diagram of another core network function selection apparatus according to an embodiment of the present application;

fig. 12 is a block diagram of another core network function selection apparatus according to an embodiment of the present application;

fig. 13 is a block diagram of a terminal according to an embodiment of the present application;

fig. 14 is a block diagram of a network function according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

The terms "comprises," "comprising," or any other variation thereof, in the description and claims of this application, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus. Furthermore, the use of "and/or" in the specification and claims means that at least one of the connected objects, such as a and/or B, means that three cases, a alone, B alone, and both a and B, exist.

In the embodiments of the present application, words such as "exemplary" or "for example" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "e.g.," is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.

Embodiments of the present invention are described below with reference to the accompanying drawings. The information reporting method, the information sending method, the information selecting method and the related equipment provided by the embodiment of the application can be applied to a wireless communication system. The wireless communication system may be a New Radio (NR) system, or other systems, such as: an Evolved Long Term Evolution (LTE) system, a Long Term Evolution (LTE) system, or a subsequent Evolved communication system, etc. Further, the method can be applied to an Unlicensed Band (Unlicensed Band) in the wireless communication system.

Referring to fig. 1, fig. 1 is a structural diagram of a network system to which the embodiment of the present invention is applicable, and as shown in fig. 1, the network system includes a terminal 11, an access network side device 12, and a core network function 13, where the terminal 11 may be a User Equipment (UE) or other terminal side devices, for example: it should be noted that, in the embodiment of the present invention, a specific type of the terminal 11 is not limited, and the terminal may be a terminal-side Device such as a Mobile phone, a Tablet Personal Computer (Tablet Personal Computer), a Laptop Computer (Laptop Computer), a Personal Digital Assistant (PDA), a Mobile Internet Device (MID), a Wearable Device (Wearable Device), or a robot. The Access network side device 12 may be a 4G base station, or a 5G base station, or a later-version base station, or a base station in another communication system, or referred to as a node B, an evolved node B, or a Transmission Reception Point (TRP), or an Access Point (AP), or another vocabulary in the field, and the network device is not limited to a specific technical vocabulary as long as the same technical effect is achieved. In addition, the network device 12 may be a Master Node (MN) or a Secondary Node (SN). It should be noted that, in the embodiment of the present application, only the 5G base station is taken as an example, but the specific type of the access network side device is not limited. In addition, the access network side device may also be referred to as an access network device or an access network function.

The core network functionality 13 may comprise at least one of: mobility Management Entity (MME), Access Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (User Plane Function, UPF), Serving GW (SGW), PDN GateWay (PDN GateWay), Policy Control Function (Policy Control Function, PCF), Policy and Charging Rules Function (Policy and Charging Rules Function, PCRF), Serving GPRS Support Node (Serving GPRS Support Node, SGSN), GateWay GPRS Support Node (GateWay GPRS Support Node, GGSN), wireless Access network device, core network routing Function Node, and the like.

Referring to fig. 2, fig. 2 is a flowchart of an information reporting method provided in an embodiment of the present application, where the method is applied to a terminal, and as shown in fig. 2, the method includes the following steps:

step 201, sending first slice routing information to an access network side device, where the first slice routing information is generated based on slice auxiliary information and is used for the access network side device to select a core network function.

The first slice routing information may be used for assisting the access network side function to select a core network function matching the terminal, for example, the first slice routing information is used for the access network side function to select a core network function supporting a network slice that the terminal desires to register, or is used for the access network side function to select a core network function supporting a network slice allowed by the terminal. For example: the first slice routing information may include index information corresponding to a network slice that the terminal desires to register or allow access.

The first slice routing information may be generated based on the slice auxiliary information, and the first slice routing information may include partial information in the slice auxiliary information, or the first slice routing information may further include information extended based on the slice auxiliary information, and the like. Preferably, the first slice routing information may include index information corresponding to the network slice, so that it may be ensured that the slice information requested to be registered by the terminal is not displayed on an air interface for transmission, and only the index information is transmitted, thereby improving security of reporting the slice routing information.

In addition, the slice auxiliary information may be related information indicating a network slice allowed by the terminal, such as index information corresponding to the network slice allowed by the terminal. It should be noted that the terminal-allowed network slice may be a network slice that the network side (e.g., core network) allows the terminal to register or access.

In the application, the access network side device can easily select the core network function matched with the terminal through the first slice routing information. For example: and selecting the core network function supporting the network slice which the terminal desires to register or allow so as to improve the service performance of the terminal.

As an optional implementation manner, before sending the first slice routing information to the access network-side device, the method further includes:

and receiving the slice auxiliary information sent by the core network function.

It should be noted that the core network function here and the core network function selected by the access network side device may be the same or different core network functions.

It should be noted that, in the present application, the slice auxiliary information sent by the core network function is not limited to be received, for example: the above-mentioned slice side information may also be pre-configured.

As an optional implementation, the slicing assistance information includes at least one of:

the system comprises first slice information and second slice information, wherein the first slice information comprises related information of a network slice, and the second slice information is used for encrypting the content of the first slice routing information.

Wherein the related information of the network slice included in the first slice information may include at least one of:

mapping relation between the network slice and a slice index (slice index-to slice);

a slice index list;

mapping relation between network slice combination and slice combination index (slice index-to-slice combination);

a slice combination index list;

mapping relation between network slice and cell identification;

a cell identity list;

mapping relation between the network slice and the tracking area;

a tracking area identification list;

mapping relation between the network slice and the core network function index;

a core network function index list;

mapping relation between the network slices and the frequency points;

a list of frequency points;

mapping relation between the network slice and the frequency band;

and (4) frequency band lists.

The mapping relationship between the network slice (slice for short) and the slice index (slice index) may include a mapping relationship between at least one network slice and a corresponding slice index, for example: if the network slices allowed by the terminal include a network slice b, a network slice c and a network slice d, the mapping relationships provided by the network side to the terminal are a slice index 2, a slice index 3 and a slice index 4 and the network slice b, and the mapping relationships of the network slice c and the network slice d, that is, the slice index 2, the slice index 3 and the slice index 4 respectively correspond to the network slice b, the network slice c and the network slice d, or the mapping relationships configured for the terminal are { < slice _ b,2>, < slice _ c,3>, < slice _ d,4> }, which can be understood as that slice index 2 corresponds to slice _ b, slice index 3 corresponds to slice _ c, and slice index 4 corresponds to slice _ d.

Optionally, in this application, the mapping relationship between the Network slice and the slice index may be configured according to a Public Land Mobile Network (PLMN), or may be configured according to a Tracking Area (TA), or configured according to a Registration Area (Registration Area), for example: for example, in PLMN1, the mapping relationship between the network slice and the slice index is that the slice index is 1,2,3,4, and 5 respectively corresponds to network slice a, network slice b, network slice c, network slice d, and network slice e. The mapping relationship between the network slice and the slice index under PLMN2 is that the slice index is 2,3,4, and 5 respectively corresponds to network slice b, network slice c, network slice d, and network slice e. Similarly, if the mapping relationship is configured according to TA or RA, for each TA/RA value, the network side configures a mapping relationship between a network slice and a slice index.

The slice index list may include one or more slice indexes, but not corresponding network slice information, from which the first slice routing information may be transmitted when step 201 is performed. Since only the slice index list can be configured and no specific mapping relation is configured, configuration overhead can be saved.

The mapping relationship between the network slice combinations and the slice combination indexes may include a mapping relationship between at least one network slice combination and a corresponding slice index, that is, one index corresponds to one network slice combination. It should be noted that different combinations of network slices, including the number of network slices, may be the same or different. For example: the mapping of the network slice combination supported by the network side and the slice combination index is that a slice combination index 1 corresponds to a network slice a and a network slice b (which may be referred to as slice _ a/slice _ b), a slice combination index 2 corresponds to a network slice a and a network slice c, and a slice combination index 3 corresponds to a network slice c, a network slice combination d, and a network slice e.

If the terminal allows the network slice a and the network slice b, the mapping relationship between the network slice combination configured by the network side for the terminal and the slice combination index may include: the slice combination index 1 corresponds to a network slice a and a network slice b, and the slice combination index 2 corresponds to a network slice a and a network slice c, or { < slice _ a, (1,2) >, < slice _ b, (1) >, which means that slice _ a is in a slice combination corresponding to slice index 1 and 2, and slice _ b is in a slice combination corresponding to slice index 1.

If the UE allows the network slice a, the network slice c, and the network slice d, the mapping relationship between the network slice combination configured by the network side for the UE and the slice combination index may include: the slice combination index 1 corresponds to a network slice a and a network slice b, the slice combination index 2 corresponds to a network slice a and a network slice c, and the slice combination index 3 corresponds to a network slice c, a network slice d and a network slice e, or { < slice _ a, (1,2) >, < slice _ c, (2,3) >, < slice _ b, (3) >, which means that slice _ a is in a slice combination corresponding to slice index 1 and 2, slice _ c is in a slice combination corresponding to slice index 2 and 3, and slice _ d is in a slice combination corresponding to slice index 3.

Optionally, in this application, the mapping relationship between the Network slice combination and the slice combination index may be configured according to a Public Land Mobile Network (PLMN), or may be configured according to a Tracking Area (TA), or configured according to a Registration Area (Registration Area).

The slice combination index list may include one or more slice combination indexes, but not corresponding network slice information, from which the first slice routing information may be transmitted when performing step 201. Since only the slice combination index list can be configured and no specific mapping relation is configured, the configuration overhead can be saved.

For example: each index in the slice combination index list corresponds to a particular network slice combination. For example, the mapping relationship of the network slice combination supported by the network side and the slice combination index is that a slice combination index 1 corresponds to a network slice a and a network slice b, a slice combination index 2 corresponds to a network slice a and a network slice c, and a slice combination index 3 corresponds to a network slice c, a network slice d, and a network slice e. If the terminal allows the network slice and the network slice b, the slice combination index list configured by the network side to the terminal comprises at least one of a slice combination index 1 and a slice combination index 2. If the terminal allows the network slice a, the network slice b and the network slice d, the slice combination index list configured by the network side to the UE includes at least one of a slice combination index 1, a slice combination index 2 and a slice combination index 3.

The correspondence between the slice and the cell identifier can be understood as an association between a cell supporting a certain slice and the slice. Each cell may support one or more slices, and a cell supporting the same slice may include one or more cells. For example, a slice may have the following correspondence with a cell: slice _ a corresponds to cell 1, cell 2 and cell 3, slice _ b corresponds to cell 2, cell 3 and cell 4, and slice _ c corresponds to cell 1, cell 2, cell 3 and cell 4. If the terminal is allowed to access slice _ a and slice _ b, the correspondence between the slice and the cell sent to the terminal by the network side may be { < slice _ a, (cell id1, cell id2) >, < slice _ b, (cell id1, cell id3) >, i.e., slice _ a, corresponding to cell id1 and cell id2, i.e., slice _ b, corresponding to cell id1 and cell id 3; or the cell identifier list sent by the network side to the terminal may be { (cell id1, cell id2), (cell id1, cell id3) }; if the terminal is allowed to access slice _ a, slice _ b and slice _ d, the correspondence between the slice and the cell sent by the network side to the terminal may be { < slice _ a, (cell id1, cell id2) >, < slice _ b, (cell id1, cell id3) >, < slice _ d, (cell id3) >, or the cell identification list sent by the network side to the terminal may be { (cell id1, cell id2), (cell id1, cell id3), (cell id3) }.

The cell identification list may include one or more cell identifications but not corresponding network slice information. Since only the slice combination index list can be configured and no specific mapping relation is configured, the configuration overhead can be saved.

The above correspondence between a slice and a tracking area may be understood as an association between a tracking area supporting a certain slice and the slice. Wherein each tracking area may support one or more slices, and a tracking area supporting the same slice may include one or more tracking areas. For example, TA1 supports access of slice _ a and slice _ b, TA2 supports access of slice _ a and slice _ c, and TA3 supports access of slice _ b, slice _ c, and slice _ d, if the terminal is allowed to access slice _ a and slice _ b, the correspondence between the slice sent by the network side to the terminal and the tracking area may be { < slice _ a, (TA1, TA2) >, < slice _ b, (TA1, TA3) >, or the tracking area identification list sent by the network side to the terminal may be { (TA1, TA2), (TA1, TA3) }. If the terminal allows to access slice _ a, slice _ b and slice _ d, the corresponding relation between the slice sent by the network side to the terminal and the tracking area is { < slice _ a, (TA1, TA2) >, < slice _ b, (TA1, TA3) >, < slice _ d, (TA3) >, or the tracking area identification list sent by the network side to the terminal is { (TA1, TA2), (TA1, TA3), (TA3) }.

The above-mentioned correspondence of slices to tracking areas may include one or more tracking area identifications but not corresponding network slice information. Since only the tracking area identification list can be configured and no specific mapping relation is configured, the configuration overhead can be saved.

The mapping relationship between the network slice and the core network function index may include a correspondence relationship between the network slice and the core network function index, where one core network function index may correspond to one slice routing group, and the slice routing group may include at least one core network function, or include at least one core network function set and at least one core network function. Therefore, the core network function index may also be referred to as a slice routing index (slice routing index). Further, the network slice corresponds to the core network function index, which indicates that the core network function in the slice routing group corresponding to the core network function index supports the network slice.

For example: one core network function index may correspond to a slice routing group and may include: < AMFm, …, AMFn > or < AMF SETm, …, AMF SETn >, or corresponding to < AMF SETa, …, AMF SETb, AMFm, …, AMFn, … >, wherein AMF SET represents an AMF SET, and the configuration mode of the slice routing group may be any one of the three modes.

If the terminal allows to access the network slice a and the network slice b, the mapping relationship between the network slice configured for the terminal by the network side and the core network function index may include: the mapping relationship between the network slice a and the core network function index 1 and the core network function index 2 (abbreviated as < slice _ a, (1,2) >), and the mapping relationship between the network slice a and the core network function index 4 (abbreviated as < slice _ b, (4) >) may also be included. The slice routing group corresponding to the core network function index 1 or 2 includes AMFk or AMF SETk, where AMFk or AMF SETk supports the service network slice a, and the meaning of the relationship between the network slice b and the core network function index 4 can be known in the same way. In addition, the core network function index may be a core network function identification.

The core network function index list may include one or more core network function indexes, but does not include corresponding network slice information, and the first slice routing information may be sent according to the core network function indexes when step 201 is executed. The configuration cost can be saved because only the core network function index list can be configured and no specific mapping relation is configured.

The mapping relationship between the network slices and the frequency points may be a mapping relationship between network slices and frequency points that the terminal allows to access. If the slice supported by the network side is slice _ a and slice _ b, and the corresponding frequency points are (FN1, FN2, FN3), (FN4, FN5), if the terminal allows access to slice _ a and slice _ b, the slice auxiliary information provided to the terminal by the network side is { < slice _ a, (FN1, FN2, FN3) >, < slice _ b, (FN4, FN5) >, and different slices may correspond to the same frequency point (frequency number) set.

The frequency point list may include one or more frequency points, but does not include corresponding network slice information, and the configuration cost can be saved because only the frequency point list is configured and no specific mapping relationship is configured.

The mapping relationship between the network slice and the frequency band may be a mapping relationship between a network slice and a frequency band that the terminal allows to access. If the slice supported by the network side is slice _ a, slice _ b, and slice _ c, and the corresponding frequency bands are (FB1, FB2), FB3, (FB1, FB4, FB5), if the UE allows access to slice _ b and slice _ c, the slice auxiliary information provided to the UE by the network side is { < slice _ b, (FB3) >, < slice _ c, (FB1, FB4, FB5) >, and different slices may correspond to the same frequency band (frequency band) set.

The frequency band list may include one or more frequency bands but not corresponding network slice information. Since only the frequency band list can be configured without configuring a specific mapping relation, configuration overhead can be saved.

The information of the second slice information used for encrypting the content of the first slice routing information may be information for encrypting the content actually reported by the first slice routing information, for example: and encrypting first routing information, wherein the first routing information is used for the access network side equipment to select a core network function.

It should be noted that, in the case that the slice assistance information does not include the first slice information, the first slice information may be preconfigured. And under the condition that the auxiliary slicing information does not comprise the second slicing information, the content reported by the terminal is not encrypted, namely the first slicing routing information is the first routing information.

The content of the first slice routing information can be encrypted through the second slice information, so that the security of reporting the routing information is improved, for example, the first routing information is encrypted through the second slice information.

Optionally, in this application, the first slice routing information includes first routing information, where the first routing information is used for the access network side device to select a core network function.

In this embodiment, the first slice routing information may include unencrypted first routing information.

Optionally, the second slice information includes a slice encryption vector.

The second slice information may include one or more slice encryption vectors, and the inclusion of multiple slice encryption vectors may further improve the security of reporting the routing information, because the encryption may be selectively performed, specifically, which one may be negotiated in advance with the access network side device or implicitly indicated, and the like.

Illustratively, the slice encryption vector may be one, i.e. the first routing information is encrypted using the same set of encryption vectors. For example, the terminal reports slice _ a at a time T1, and performs encryption processing using the slice encryption vector. The terminal reports slice _ b at another time T2, or performs encryption processing using the slice encryption vector.

Illustratively, the slice encryption vector may further include slice information, such as slice encryption vector 1 for slice _ a and slice encryption vector 2 for slice _ b. For example, the terminal reports slice _ a at a time T1, and performs encryption processing using the slice encryption vector 1. The terminal reports slice _ b at another time T2, or performs encryption processing using the slice encryption vector 2. It is to be understood that the slice information shown may be a slice, a slice index corresponding to the slice, a slice combination, an index corresponding to the slice combination, etc.

In this embodiment, since the content of the first slice routing information may be encrypted by the slice encryption vector, the security of reporting the routing information is improved, for example, the first routing information is encrypted by the slice encryption vector.

Optionally, the slice encryption vector includes:

a random string and an encrypted string;

wherein the encrypted string is generated based on a key and the random string.

Wherein, the key may be configured in advance.

When a plurality of slice encryption vectors are included, contents contained in different slice encryption vectors may be partially the same, partially different, or completely different, for example: the random strings are different.

In addition, when the terminal reports the routing information, the same set of slice encryption vectors can be used for encryption processing.

Optionally, the slice encryption vector further includes: the first slice information.

In this embodiment, when the terminal reports the routing information, it may use the corresponding slice encryption vector for different routing information, for example: different slice encryption vectors are configured for different routing information in the slice auxiliary information, wherein the random character strings in the different slice encryption vectors can be different.

Optionally, the first slice routing information includes: a slice indication vector, wherein the slice indication vector includes slice encryption information and a random string, wherein the slice encryption information is generated based on the slice encryption vector and first routing information.

The slice encryption information may be generated based on the slice encryption vector and the first routing information, and the slice encryption vector may be used to encrypt the first routing information to obtain the first slice routing information. Such as encrypting the first routing information using the encryption string and the random string, or encrypting the first routing information using only the encryption string.

Optionally, in this application, the first routing information includes one of:

slice index, slice combination index, core network function index.

The slice index, the slice combination index, and the core network function index may be indexes corresponding to network slices, that is, the indexes may determine specific network slices. For example: at least one index of the indexes corresponding to the network slice in the slice auxiliary information is selected, so that the access network side device can select the core network function matched with the terminal, for example, select the core network function that the terminal desires to register.

For example: in the case that the slice auxiliary information includes a mapping relationship between a network slice and a slice index, the first slice routing information provided by the terminal to the access network side device is a slice index (or a slice index list) corresponding to the network slice that the terminal wishes to register. If the mapping relationship between the network slice and the slice index under the PLMN1 configured as the terminal by the core network is that the slice index 1/2 corresponds to the s-network slice 1/2, respectively, and the terminal desires to access the network slice 1, the first slice routing information provided by the terminal is the slice index 1 corresponding to the network slice 1.

Another example is: when the slice auxiliary information includes a mapping relationship between a network slice combination and a slice combination index, the first slice routing information provided by the terminal to the access network side device is a slice combination index corresponding to a slice combination including a network slice that the terminal desires to register. The first slice routing information provided by the terminal to the access network side device may be any slice combination index corresponding to a slice combination containing a network slice to which the terminal desires to access; or all slice combination indexes corresponding to slice combinations including a network slice to which the terminal desires to access. For example, the mapping relationship between the network slice combination and the slice combination index under the PLMN1 configured by the network side for the terminal includes: the slice combination index 1 corresponds to a network slice 1 and a network slice 2, the slice combination index 2 corresponds to a network slice 1 and a network slice3, and if the UE desires to access the network slice 1, the slice routing information provided by the terminal to the access network side device is at least one of the slice combination index 1 and the slice combination index 2.

Another example is: when the slice auxiliary information includes the slice combination index list, the first slice routing information provided by the terminal to the access network side device is a slice combination index corresponding to a network slice combination which the terminal wishes to register. The first slice routing information provided by the terminal to the access network side device may be a slice combination index corresponding to a slice combination that the terminal desires to access, or may be a slice combination index corresponding to all slice combinations that the terminal allows to access. For example, the slice combination index list under PLMN1 configured for the terminal by the network side is slice combination index 1 and slice combination index 2, slice combination index 1 under PLMN1 on the network side corresponds to network slice 1 and network slice 2, slice combination index 2 corresponds to network slice 1 and network slice3, and slice combination index 3 corresponds to network slice3, network slice 4, and network slice 5. The first slice routing information reported by the terminal may include a slice combination index 1 and a slice combination index 2.

Another example is: for the case that the slice auxiliary information includes a mapping relationship between a network slice and a core network function index, the slice routing information provided by the terminal to the access network side device may include a core network function index (e.g., a core network routing function identification list) corresponding to a network slice combination that the terminal wishes to register. If the mapping relationship between the network slice configured for the terminal by the network side and the core network function index is that the network slice a corresponds to the core network function index 1, the core network function index 2 and the core network function index 3, and the network slice b corresponds to the core network function index 2, the core network function index 3 and the core network function index 4, if the terminal wishes to access the network slice a, the first slice routing information reported by the terminal may include at least one of the core network function index 1 and the core network function index 2.

Optionally, the slice auxiliary information further includes an index that does not correspond to a network slice.

The index that does not correspond to the network slice may be an index that is not included in the mapping relationship between the index supported by the network side and the network slice. Such as the mapping of network slices to slice indices, the mapping of network slice combinations to slice combination indices, and the mapping of network slices to core network function indices, which are supported by the network side.

By configuring the index that does not correspond to the network slice, the routing information reported by the terminal may include the index that does not correspond to the network slice, so that an attacker cannot identify the network slice that the terminal desires to register.

Optionally, the first routing information further includes:

indices that do not correspond to a network slice.

The index not corresponding to the network slice may be an index not corresponding to the network slice, or a pre-configured index, or the index not corresponding to the network slice is an index added or generated by the terminal in the first slice routing information for security.

The security of the terminal traffic may be increased by the index that does not correspond to the network slice, because the index that does not correspond to the network slice may make it impossible for an attacker to identify the network slice that the terminal desires to register. However, in the present application, the access network-side device is identifiable because it is clear which indexes correspond to the network slices and which indexes do not correspond to the network slices.

Referring to fig. 3, fig. 3 is a diagram of an information sending method applied to a core network function according to an embodiment of the present application, and as shown in fig. 3, the information sending method includes the following steps:

step 301, performing a sending operation, wherein the sending operation includes at least one of the following:

The above-mentioned slicing assistance information may refer to the corresponding description of the embodiment shown in fig. 2, which is not described herein again.

Wherein, the second slice routing information may also be preconfigured by the access network side.

The second slice routing information may include related information of a network slice supported by the access network side device or the core network function, for example: the index information corresponding to the network slice supported by the access network side equipment or the core network function is included.

Optionally, the slice auxiliary information includes at least one of:

Optionally, the related information of the network slice included in the first slice information includes at least one of:

mapping relation between the network slices and the slice indexes;

a slice index list;

mapping relation between the network slices and the slice combination indexes;

a slice combination index list;

mapping relation between network slice and cell identification;

a cell identity list;

mapping relation between the network slice and the tracking area;

a tracking area identification list;

mapping relation between the network slice and the core network function index;

a core network function index list;

mapping relation between the network slices and the frequency points;

a list of frequency points;

mapping relation between the network slice and the frequency band;

and (4) frequency band lists.

Optionally, the second slice information includes a slice encryption vector.

Optionally, the slice encryption vector includes:

a random string and an encrypted string;

wherein the encrypted string is generated based on a key and the random string.

Optionally, the second slice routing information includes at least one of:

slice indexing;

slice combination indexing;

a core network function index;

the slice decryption vector.

The slice index may be one or more slice indexes, such as a slice index list, the slice combination index may be one or more slice combination indexes, such as a slice combination index list, and the core network function index may be one or more core network function indexes, such as a core network function index list. The frequency point information may be a frequency point list, and the frequency band information may be a frequency band list.

It should be noted that the second slice routing information here includes the same content that the index and the slice auxiliary information include may exist.

The decryption vector may be one or more decryption vectors corresponding to the slice encryption vector in the embodiment shown in fig. 2.

In this embodiment, the index of the core network may enable the access network side device to accurately select a corresponding core network function, and may obtain the routing information reported by the terminal in a preparation manner through the decryption vector.

Optionally, the slice decryption vector includes: a key.

The key may be a key corresponding to the key in the embodiment shown in fig. 2.

Movable, the slice decryption vector further comprises: the first slice information.

Optionally, a part of the slice indexes or the slice combination indexes in the second slice routing information do not correspond to the network slices.

The above-mentioned partial slice index or slice combination index does not correspond to a network slice, which may cause an attack to be unable to accurately identify a network slice that the terminal desires to register, and further, when the access network side device selects a core network function for the terminal, the index that does not correspond to the network slice may be removed.

Optionally, before the sending operation is executed, the method further includes:

receiving slice support information sent by an access network side device, wherein the slice support information is used for generating the slice auxiliary information.

The slice support information may be information of a network slice supported by the access network side device, such as an index corresponding to the network slice supported by the access network side device.

After receiving the slice support information, the core network function may generate slice auxiliary information based on the slice support information, for example, an index in the generated slice auxiliary information corresponds to a network slice supported by the slice support information, or a mapping relationship in the generated slice auxiliary information includes a mapping relationship of network slices supported by the slice support information.

It should be noted that, in the present application, it is also possible not to send slice support information, because in some scenarios, the core network function may determine the network slice supported by the access network-side device by storing the relevant information of the access network-side device in the core network.

In this embodiment, the slice auxiliary information is sent to the terminal and/or the second slice routing information is sent to the access network side device, so that the access network side device can easily select the core network function matched with the terminal.

Referring to fig. 4, fig. 4 is a flowchart of a core network function selection method provided in an embodiment of the present application, where the method is applied to an access network side device, as shown in fig. 4, and includes the following steps:

step 401, receiving first slice routing information sent by a terminal;

step 402, selecting a core network function according to the first slice routing information.

The first slice routing information may refer to the corresponding description of the embodiment shown in fig. 2, which is not described herein again.

The selecting the core network function according to the first slice routing information may be selecting a core network function corresponding to the first slice routing information, that is, a core network function matched with the terminal. For example: core network functions are selected that support network slices that the terminal desires to register with or allow.

For example, the first slice routing information reported by the terminal is a slice index 1, and if the access network side device knows that the terminal wants to access a network slice a corresponding to the slice index, any core network function capable of supporting the network slice a is used as a routing node of the terminal. Or the slice routing information reported by the terminal is the slice index 1 and the slice index 2, and the access network side device knows that the terminal wants to access the network slice and the network slice b corresponding to the slice index 1 and the slice index 2, the access network side device preferentially uses the core network function capable of supporting the network slice a and the network slice b as the routing node of the terminal, or the access network side device uses the core network function supporting part of the network slices in the network slice a and the network slice b as the low-priority routing node of the terminal.

Another example is: the slice routing information reported by the terminal is a slice combination index 1, and if the access network side equipment knows that the terminal wants to access the combination of the network slice a and the network slice b corresponding to the slice combination index 1, any core network function capable of supporting the combination of the network slice a and the network slice b is used as a routing node of the terminal. Or the slice routing information reported by the terminal is the slice combination index 1 and the slice combination index 2, the access network side device knows that the terminal wants to access the combination of the network slice a and the network slice b corresponding to the slice combination index 1 and the slice combination index 2, and the combination of the network slice a and the network slice c, then the access network side device preferentially uses the core network function capable of simultaneously supporting the combination of the network slice a and the network slice b and the combination of the network slice a and the network slice c as the routing node of the terminal, or the access network side device uses the core network routing function node supporting partial combination of the two combinations as the low priority routing node of the terminal.

Another example is: if the slice routing information reported by the terminal is core network function indexes 1 and 2, the access network side device takes any core network function belonging to the slice routing group reported by the terminal as a routing node of the terminal, for example, the slice routing group corresponding to the core network function indexes 1 and 2 includes AMF1 or AMF2, so that AMF1 or AMF2 can be taken as the routing node.

In this embodiment, since the core network function is selected according to the first slice routing information, the access network side device can easily select the core network function matched with the terminal.

Optionally, the first slice routing information includes first routing information, where the first routing information is used for the access network side device to select a core network function

Optionally, the selecting a core network function according to the first slice routing information includes:

and selecting a core network function according to the first routing information and the second slice routing information, wherein the first routing information is acquired based on the first slice routing information.

The second slice routing information may include one or more slice routing information, and different slice routing information is sent by different core network functions, for example: and the plurality of core network functions all send second slice routing information to the access network side equipment.

The selecting a core network function according to the first slice routing information and the second slice routing information may be selecting a core network function corresponding to a network slice to which the first slice routing information and the second slice routing information correspond together. For example, a core network node where the first slice routing information and the second slice routing information intersect is selected.

Optionally, selecting a core network function according to the first routing information and the second slice routing information, including:

and selecting a core network function corresponding to intersection routing information according to the first routing information and the second slice routing information, wherein the intersection routing information is the intersection information of the first slice routing information and the second slice routing information.

The intersection routing information may be an intersection index in the first routing information and the second slice routing information.

The implementation mode can realize that the selected core network function is more matched with the terminal and the access network side equipment.

It should be noted that, in the present application, the selection of the intersection routing information is not limited, and for example: and under the condition that the first routing information and the second slice routing information do not have intersection routing information, selecting a corresponding core network function according to the first routing information.

Optionally, the selecting a core network function according to the first routing information and the second slice routing information includes:

and selecting a core network function according to the second slice routing information and a target index, wherein the target index is an index which is associated with the network slice in the first routing information, and the first routing information comprises an index which is not corresponding to the network slice.

The target index may be an index that is left in the first slice routing information except for an index that does not correspond to the network slice. The above-mentioned index not corresponding to the network slice can be referred to the corresponding description of the embodiment shown in fig. 2.

Optionally, the selecting a core network function according to the second slice routing information and the target index includes:

and selecting a core network function according to target information and the target index, wherein the target information is information which is associated with the network slice in the second slice routing information, and the second slice routing information comprises information which is not associated with the network slice.

The target information may be an index obtained by removing information that is not associated with the network slice from the second slice routing information, for example, an index that is left by removing an index that is not corresponding to the network slice from the second slice routing information.

Optionally, the second slice routing information includes at least one of:

slice indexing;

slice combination indexing;

a core network function index;

the slice decryption vector.

Optionally, the slice decryption vector includes: a key.

Optionally, the first slice routing information includes: a slice indication vector, wherein the slice indication vector includes slice encryption information and a random string, wherein the slice encryption information is generated based on an encryption string and first routing information, the method further comprising:

and decrypting the slice encryption information by using the slice decryption vector and the random character string to obtain the first routing information.

The above decrypting the slice encryption information by using the decryption vector to obtain the first routing information may be directly using a key or decrypting the slice encryption information by using slice decryption information corresponding to the key to obtain the first routing information, where the slice decryption information may be generated based on the key and a random string.

Optionally, the first routing information includes one of:

slice index, slice combination index, core network function index, frequency point information and frequency band information.

Optionally, before selecting a core network function according to the first slice routing information and the second slice routing information, the method further includes:

and receiving the second slice routing information sent by the core network function.

and the slicing support information is sent to a core network, wherein the slicing support information is used for a core network function to generate the slicing auxiliary information.

The above-mentioned slicing support information may refer to the corresponding description of the embodiment shown in fig. 3, which is not described herein again.

In addition, the priority of the core network function can be set, and when the plurality of core network functions are determined according to the first slice routing information, the selection can be performed according to the priority.

For example: the first slice routing information includes a slice index list, for example, the first slice routing information is a slice index (2,3, 7), and the slice index set corresponding to the network slice supported by the AMFa or the AMF SETa is (1,3), and the slice index set corresponding to the network slice supported by the AMFb or the AMF SETb is (1,2,3), and under the influence of no other parameter (for example, the AMF identifier sent by the terminal), the access network side device sets priorities according to how much content included in the intersection of the supported slice index set (such as the second slice routing information) and the first slice routing information, for example, the AMFb or the AMF SETb has a higher priority than the AMFa or the AMF SETa, and the access network side device preferentially selects the AMFb or the AMF SETb to serve the service of the user terminal.

The access network side device may first remove the slice index (e.g., the slice index 7) that does not have the corresponding network slice from the slice routing information, and then perform the above steps.

Or, when the first slice routing information has only one slice index, or only one slice index after removing the slice index without the corresponding network slice, the access network side device may determine which AMF or AMF SET serves the slice index, and select one of the AMF or AMF SET serving the service of the terminal.

Another example is: the first slice routing information includes a slice combination index list. For example, the first slice routing information is a slice combination index (2,3), the set of slice combination indexes corresponding to slices supported by AMFa or AMF SETa is (1,3), the set of slice combination indexes corresponding to slices supported by AMFb or AMF SETb is (1,2,3), and without the influence of other parameters (such as an AMF identifier sent by a terminal), the access network side device sets priorities according to how much content is included in the intersection of the set of supported slice combination indexes and the first slice routing information, for example, the AMFb or AMF SETb has a higher priority than the AMFa or AMF SETa, and the access network side device preferentially selects the AMFb or AMF SETb to serve the traffic of the user terminal.

Another example is: the first slice routing information comprises a core network function index list. For example, the first slice routing information is a core network function index (2,3), the core network function index corresponding to AMFa or AMF SETa is 2, the core network function index corresponding to AMFb or AMF SETb is 3, the access network side device preferentially selects the AMF or AMF SET in the first slice routing information, such as AMFa or AMF SETa and AMFb or AMF SETb, having the same priority without the influence of other parameters (such as the AMF identifier sent by the terminal), and then selects a more suitable AMF or AMF SET to serve the service of the terminal according to other parameters, such as the AMF identifier sent by the terminal.

In the embodiment of the application, the core network function is selected according to the first slice routing information, so that the core network function matched with the terminal can be more easily selected by the access network side function.

The following exemplifies the method provided by the present application by taking the core network function as an example to send the slice auxiliary information to the terminal, as shown in fig. 5, the method includes the following steps:

step 501: and the slice configuration information is acquired by the terminal from the core network function. The slice configuration information may be preconfigured or (re) configured by the core network, such as the slice assistance information shown in fig. 5, where the slice assistance information may be the latest slice-aware cell selection assistance information provided by the core network to the terminal when the terminal successfully accesses the network). Wherein the slice configuration information may be any one of:

the first scheme is as follows: the mapping relationship between the network slice and the slice index (referred to as slice index-to slice mapping relationship). For example, the mapping relationship between the slice index (slice index) supported by the network side and the slice is 1,2,3,4, and 5, which correspond to the network slice (slice _ a, slice _ b, slice _ c, slice _ d, and slice _ e, respectively, and if the terminal allows the slice to be the slice _ b, slice _ c, and slice _ d, the mapping relationship provided by the network side to the UE is the mapping relationship between the slice index (slice index) and the slice _ b, slice _ c, and slice _ d.

The mapping relationship between the slice index and the slice may be configured by per PLMN, or configured by per TA, or configured by per RA. For example, the mapping relationship of slice index-to slice in PLMN1 is that slice index is 1,2,3,4, and 5 corresponds to slice _ a, slice _ b, slice _ c, slice _ d, and slice _ e, respectively. The mapping relationship of slice index-to slice under PLMN2 is that slice index is 2,3,4, and 5 correspond to slice _ b, slice _ c, slice _ d, and slice _ e, respectively. Similarly, if the TA is configured by per TA or per RA, for each TA/RA value, the network side configures a slice index-to slice mapping relationship.

Scheme II: a mapping relationship between a network slice combination and a slice combination index (referred to as a slice index-to-slice combination mapping relationship), where the slice combination index (referred to as a slice index) corresponds to a specific slice combination. For example, the mapping relationship between the slice index and the slice supported by the network side is that 1 slice index corresponds to a network slice a and a network slice b (which may be referred to as slice _ a/slice _ b), 2 slice index corresponds to slice _ a/slice _ c, and 3 slice index corresponds to slice3 slice _ c/slice _ d/slice _ e. If the slice allowed by the UE is slice _ a/slice _ b, the mapping relationship slice index of the slice index-to-slice combination configured by the network side for the UE is 1(slice _ a/slice _ b), and the slice index is 2(slice _ a/slice _ c). If the slice allowed by the UE is slice _ a/slice _ c/slice _ d, the mapping relationship of slice index-to-slice combination configured by the network side for the UE is slice _ a/slice _ b, slice index is 2(slice _ a/slice _ c), and slice index is 3(slice _ c/slice _ d/slice _ e).

The "/" above means a sum.

The mapping relationship between the slice index and the slice may be configured by per PLMN, or configured by per TA, or configured by per RA, where the RA may be composed of one or more TAs.

The third scheme is as follows: a slice combination index list (referred to as slice index list), where the slice index corresponds to a specific slice combination. For example, the mapping relationship between the slice index and the slice supported by the network side is that 1 slice index corresponds to slice _ a/slice _ b,2 slice index corresponds to slice _ a/slice _ c, and 3 slice index corresponds to slice3 slice _ c/slice _ d/slice _ e. If the slice allowed by the terminal is slice _ a/slice _ b, the slice index configured by the network side to the UE is slice index 1/2. If the slice allowed by the terminal is slice _ a/slice _ b/slice _ d, the slice index configured by the network side for the UE is slice index 1/2/3.

And the scheme is as follows: and mapping relation of slice-to-cell ID. One slice may correspond to a plurality of cells, and one cell may correspond to a plurality of slices. For example, if the network side supports the cell ID of slice _ a as 1,2, and 3, the cell ID of slice _ b as 2,3, and 4, and the cell ID of slice _ c as 1,2,3, and 4, if the UE allows slice _ b and slice _ b, the mapping relationship of slice-to-cell ID configured for the UE by the network side includes: { < slice _ a, (1,2,3) >, < slice _ b, (2,3,4) >, < slice _ c, (1,2,3,4) > }. In other words, slice _ a corresponds to cell IDs of 1,2, and 3, and slice _ b corresponds to cell IDs of 2,3, and 4.

Case five: the correspondence of the slice to the tracking area. If tracking area TA1 supports slice _ a and slice _ b, tracking area TA2 supports slice _ a, and tracking area TA3 supports slice _ b and slice _ d. If the UE selects slice _ a, the slice usage information may include a TA corresponding to slice _ a, i.e. (TA1, TA 2); if the UE selects slice _ a and slice _ d, the slice usage information may include a union of TAs corresponding to slice _ a and slice _ d, i.e., (TA1, TA2, TA 3).

Scheme six: mapping relation between the network slice and the core network function index (referred to as mapping relation of slice-to-routing index for short). For example, the network side sets < AMFm, …, AMFn > or < AMF SETm, …, AMF SETn > or < AMF SETa, …, AMF SETb, AMFm, …, AMFn, … > as a slice routing group, the corresponding core network function index (slice routing index) is 1, and so on. If the terminal allows to access slice _ a and slice _ b, the mapping relationship of slice-to-slice routing index configured for the terminal by the network side is { < slice _ a, (1,2) >, < slice _ b, (4) >, where the slice routing index is 1 or 2 and the corresponding slice routing group contains AMFk or AMF SETk, where AMFk or AMF SETk supports service slice _ a, and the meaning of the relationship between slice _ b and slice routing index is 4 can be known in the same way.

The scheme is seven: slice-to-frequency number mapping relationship. If the slice supported by the network side is slice _ a and slice _ b, and the corresponding frequency points are (FN1, FN2, FN3), (FN4, FN5), if the UE allows access to slice _ a and slice _ b, the slice auxiliary information provided to the UE by the network side is { < slice _ a, (FN1, FN2, FN3) >, < slice _ b, (FN4, FN5) >, and different slices may correspond to the same frequency number set.

And the eighth scheme is as follows: and mapping relation of slice-to-frequency band. If the slice supported by the network side is slice _ a, slice _ b, and slice _ c, and the corresponding frequency bands are (FB1, FB2), FB3, (FB1, FB4, FB5), if the UE allows to access slice _ b and slice _ c, the slice auxiliary information provided by the network side to the UE is { < slice _ b, (FB3) >, < slice _ c, (FB1, FB4, FB5) >, and different slices may correspond to the same frequency band set.

Scheme one to scheme eight can be combined, that is, one slice can correspond to a plurality of kinds of information, which can be used in cascade, for example, slice auxiliary information is { slice _ a, (FN1, FN2), (cell id2, cell id5), (slice routing index 1,3), (FB1, FB3) }.

The scheme is nine: similarly to scheme three, the slice assistance information may not include slice information, such as slice assistance information provided to the UE is { (FN1, FN2), (cell id2, cell id5), (slice routing index 1,3), (FB1, FB3) }.

Step 502: the terminal reports first slice routing information to the access network side equipment, and the first slice routing information is used for assisting the access network side equipment in selecting a core network routing function node. The behavior of the terminal reporting the slice routing information is as follows:

for scenario one in step 501: the first slice routing information provided by the terminal to the access network side device is a slice index (list) corresponding to the network slice that the terminal wishes to register. If the slice index-to-slice under the PLMN1 where the terminal is configured by the core network is that slice index 1/2 corresponds to slice 1/2 respectively, and the UE desires to access slice 1, the slice routing information provided by the terminal is that slice index corresponding to slice 1.

For scenario two in step 501: the first slice routing information provided by the terminal to the access network side device is a slice index corresponding to a slice combination including a network slice which the terminal desires to register. The first slice routing information provided by the terminal to the access network side device is a slice index corresponding to any slice combination containing the slice which the UE desires to access; or slice index(s) corresponding to all slice combinations including the slice to which the UE desires to access. For example, the mapping relationship slice index of the slice index-to-slice combination under the PLMN1 configured by the network side for the UE is 1(slice 1/2), slice index is 2(slice 1/3), and if the UE desires to access slice 1, the slice routing information provided by the UE to the RAN is slice index 1, slice index 2, or slice index 1/2.

For scenario three in step 501: the first slice routing information provided by the terminal to the access network side device is a slice index corresponding to a network slice combination which the terminal wishes to register. The first slice routing information provided by the terminal to the first slice routing information may be a slice index corresponding to a slice combination that the terminal desires to access, or a slice corresponding to all slice combinations that the terminal allows to access. For example, the slice index under the PLMN1 configured for the terminal by the network side is slice index 1/2, the slice index under the PLMN1 of the network side is 1 corresponding to slice 1/2, slice index 2 corresponding to slice 1/3, and slice index 3 corresponding to slice3 corresponding to slice 3/4/5. The first slice routing information reported by the terminal is slice index 1/2.

Corresponding to scenario four in step 501: the slice routing information provided by the terminal to the access network side device is a core network routing function identifier (or list) corresponding to the network slice combination which the terminal wishes to register. For example, the mapping relationship between the network slice configured by the network side for the terminal and the core network function index is slice _ a (routing index 1/2/3), slice _ b (routing index 2/3/4), and if the terminal desires to access slice _ a, the slice routing information reported by the UE is core network routing index 1 or 2 or 1/2.

Step 503: and the access network side equipment receives the first slice routing information provided by the terminal and selects a proper core network function. The behavior of the access network side device may include the following:

3.1 for scheme one in step 1: and the access network side equipment preferentially selects a core network node capable of supporting the slice routing reported by the terminal as a routing node. For example, if the slice routing information reported by the terminal is slice index 1, and the RAN knows that the terminal desires to access slice _ a corresponding to slice index 1, it uses any core network function capable of supporting slice _ a as the routing node of the terminal. Or the slice routing information reported by the terminal is slice index 1/2, and the RAN knows that the terminal desires to access slice index 1/2 corresponding slice _ a and slice _ b, then the access network side device preferentially uses the core network function capable of supporting slice _ a and slice _ b as the routing node of the terminal, or the access network side device uses the core network function supporting part of slices as the low-priority routing node of the terminal.

3.2 corresponds to scheme two or scheme three in step 1: and the access network side equipment side preferentially selects a core network function capable of supporting the slice routing reported by the terminal as a routing node. And if the classmatic slice routing information reported by the terminal is 1, the access network side device knows that the terminal wants to access the slice _ a and slice _ b combination corresponding to 1, and then takes any core network function capable of supporting the slice _ a and slice _ b combination as the routing node of the terminal. Or the slice routing information reported by the terminal is slice index 1/2, and the access network side device knows that the terminal desires to access the (slice _ a, slice _ b)/(slice _ a, slice _ c) combination corresponding to slice index 1/2, and then the access network side device preferentially uses the core network function capable of simultaneously supporting the (slice _ a, slice _ b)/(slice _ a, slice _ c) combination as the routing node of the terminal, or the access network side device uses the core network function supporting the combination of partial slices as the low-priority routing node of the terminal.

3.3 corresponds to scheme three in step 1: and the access network side equipment side selects a core network function capable of supporting the slice routing reported by the terminal as a routing node. If the first slice routing information reported by the terminal is routing index 1/2, the access network side device takes any core network function belonging to the slice routing group reported by the terminal as a routing node of the terminal, for example, takes AMF1 or AMF2 as a routing node.

In the embodiment of the application, a terminal may report, to an access network side device, a slice index corresponding to a network slice that the terminal desires to access, or a slice combination index of a slice combination including a network slice that the UE desires to access, or slice indexes or slice combination indexes supported by all terminals;

by the method, the terminal can provide the slice routing information to the access network side equipment so that the access network side equipment can route the terminal information conveniently, meanwhile, the slice information requested to be registered by the terminal is ensured not to be displayed on an air interface for transmission, and the safety of slice routing information reporting is improved.

It should be noted that, in the information reporting method provided in the embodiment of the present application, the execution main body may be an information reporting apparatus, or a control module in the information reporting apparatus, configured to execute the loaded information reporting method. In the embodiment of the present application, an information reporting method executed by an information reporting method device is taken as an example to describe the information reporting method provided in the embodiment of the present application. And in the information sending method provided by the embodiment of the application, the execution main body can be an information sending device or a control module used for executing the loaded information sending method in the information sending device. In the embodiment of the present application, an information sending method performed by an information sending apparatus is taken as an example, and the information sending method provided in the embodiment of the present application is described. In the core network function selection method provided in the embodiment of the present application, the execution main body may be a core network function selection device, or a control module in the core network function selection device, configured to execute the loaded core network function selection method. In the embodiment of the present application, a method for selecting a core network function, which is performed by a core network function selection device to load a core network function, is taken as an example, and the core network function selection method provided in the embodiment of the present application is described.

Referring to fig. 6, fig. 6 is a structural diagram of an information reporting apparatus according to an embodiment of the present application, where the apparatus is applied to a terminal, and as shown in fig. 6, the information reporting apparatus 600 includes:

a sending module 601, configured to send first slice routing information to an access network-side device, where the first slice routing information is generated based on slice auxiliary information, and is used for the access network-side device to select a core network function.

Optionally, as shown in fig. 7, the method further includes:

a receiving module 602, configured to receive the slice auxiliary information sent by the core network function.

Optionally, the slice auxiliary information includes at least one of:

mapping relation between the network slices and the slice indexes;

a slice index list;

mapping relation between the network slices and the slice combination indexes;

a slice combination index list;

mapping relation between network slice and cell identification;

a cell identity list;

mapping relation between the network slice and the tracking area;

a tracking area identification list;

mapping relation between the network slice and the core network function index;

a core network function index list;

mapping relation between the network slices and the frequency points;

a list of frequency points;

mapping relation between the network slice and the frequency band;

and (4) frequency band lists.

Optionally, the second slice information includes a slice encryption vector.

Optionally, the slice encryption vector includes:

a random string and an encrypted string;

wherein the encrypted string is generated based on a key and the random string.

Optionally, the slice encryption vector further includes:

the first slice information.

Optionally, the first slice routing information includes first routing information, where the first routing information is used for the access network side device to select a core network function.

Optionally, the first routing information includes one of:

slice index, slice combination index, core network function index.

Optionally, the first routing information further includes:

indices that do not correspond to a network slice.

The information acquisition apparatus provided in this embodiment of the present application can implement each process in the method embodiment of fig. 2, and for avoiding repetition, details are not repeated here, and a core network function matched with a terminal can be easily selected by an access network side device.

It should be noted that the information reporting apparatus in the embodiment of the present application may be an apparatus, or may also be a component, an integrated circuit, or a chip in a terminal.

Referring to fig. 8, fig. 8 is a structural diagram of an information transmitting apparatus according to an embodiment of the present application, and as shown in fig. 8, an information transmitting apparatus 800 includes:

a sending module 801, configured to perform a sending operation, where the sending operation includes at least one of:

Optionally, the slice auxiliary information includes at least one of:

mapping relation between the network slices and the slice indexes;

a slice index list;

mapping relation between the network slices and the slice combination indexes;

a slice combination index list;

mapping relation between network slice and cell identification;

a cell identity list;

mapping relation between the network slice and the tracking area;

a tracking area identification list;

mapping relation between the network slice and the core network function index;

a core network function index list;

mapping relation between the network slices and the frequency points;

a list of frequency points;

mapping relation between the network slice and the frequency band;

and (4) frequency band lists.

Optionally, the second slice information includes a slice encryption vector.

Optionally, the slice encryption vector includes:

a random string and an encrypted string;

wherein the encrypted string is generated based on a key and the random string.

Optionally, the second slice routing information includes at least one of:

slice indexing;

slice combination indexing;

a core network function index;

the slice decryption vector.

Optionally, the slice decryption vector includes: a key.

Optionally, the slice decryption vector further includes: the first slice information.

Optionally, as shown in fig. 9, the apparatus further includes:

a receiving module 802, configured to receive slice support information sent by an access network-side device, where the slice support information is used to generate the slice auxiliary information.

The information sending apparatus provided in this embodiment of the present application can implement each process in the method embodiment of fig. 3, and for avoiding repetition, details are not repeated here, and a core network function matched with a terminal can be easily selected by an access network side device.

The information sending device in the embodiment of the present application may be a device, or may be a component, an integrated circuit, or a chip in the core network function.

Referring to fig. 10, fig. 10 is a structural diagram of a core network function selection apparatus provided in the present application, which is applied to an access network side device, and as shown in fig. 10, the core network function selection apparatus 1000 includes:

a first receiving module 1001, configured to receive first slice routing information sent by a terminal;

a selecting module 1002, configured to select a core network function according to the first slice routing information.

Optionally, the second slice routing information includes at least one of:

slice indexing;

slice combination indexing;

a core network function index;

the slice decryption vector.

Optionally, the slice decryption vector includes: a key.

Optionally, the first routing information includes one of:

Optionally, as shown in fig. 11, the apparatus further includes:

a second receiving module 1003, configured to receive the second slice routing information sent by the core network function.

Optionally, as shown in fig. 12, the apparatus further includes:

a sending module 1004, configured to send slicing support information to a core network, where the slicing support information is used for a core network function to generate the slicing assistance information.

The core network function selection apparatus provided in this embodiment of the present application can implement each process in the method embodiment of fig. 4, and for avoiding repetition, details are not described here again, and it is possible to enable the access network side device to easily select a core network function that matches the terminal.

It should be noted that the core network function selection apparatus in the embodiment of the present application may be an apparatus, or may be a component, an integrated circuit, or a chip in the access network side device.

Fig. 13 is a schematic hardware structure diagram of a terminal for implementing the embodiment of the present application.

The terminal 1300 includes but is not limited to: a radio frequency unit 1301, a network module 1302, an audio output unit 1303, an input unit 1304, a sensor 1305, a display unit 1306, a user input unit 1307, an interface unit 1308, a memory 1309, a processor 1310, and the like.

Those skilled in the art will appreciate that terminal 1300 may also include a power supply (e.g., a battery) for powering the various components, which may be logically coupled to processor 1310 via a power management system to manage charging, discharging, and power consumption management functions via the power management system. The electronic device structure shown in fig. 13 does not constitute a limitation of the electronic device, and the electronic device may include more or less components than those shown, or combine some components, or arrange different components, and thus, the description is omitted here.

The radio frequency unit 1301 is configured to send first slice routing information to an access network side device, where the first slice routing information is generated based on slice auxiliary information, and is used for the access network side device to select a core network function.

Optionally, before sending the first slice routing information to the access network side device, the radio frequency unit 1301 is further configured to:

Optionally, the slice auxiliary information includes at least one of:

mapping relation between the network slices and the slice indexes;

a slice index list;

mapping relation between the network slices and the slice combination indexes;

a slice combination index list;

mapping relation between network slice and cell identification;

a cell identity list;

mapping relation between the network slice and the tracking area;

a tracking area identification list;

mapping relation between the network slice and the core network function index;

a core network function index list;

mapping relation between the network slices and the frequency points;

a list of frequency points;

mapping relation between the network slice and the frequency band;

and (4) frequency band lists.

Optionally, the second slice information includes a slice encryption vector.

Optionally, the slice encryption vector includes:

a random string and an encrypted string;

wherein the encrypted string is generated based on a key and the random string.

Optionally, the slice encryption vector further includes:

the first slice information.

Optionally, the first routing information includes one of:

slice index, slice combination index, core network function index.

Optionally, the first routing information further includes:

indices that do not correspond to a network slice.

The terminal can enable the access network side equipment to easily select the core network function matched with the terminal.

Optionally, an embodiment of the present application further provides a terminal, including a processor 1310, a memory 1309, and a program or an instruction stored in the memory 1309 and executable on the processor 1310, where the program or the instruction is executed by the processor 1310 to implement each process of the above uplink information reporting method embodiment, and the same technical effect can be achieved, and details are not described here to avoid repetition.

Referring to fig. 14, fig. 14 is a structural diagram of a network function according to an embodiment of the present application, and as shown in fig. 14, the network function 1400 includes: a processor 1401, a transceiver 1402, a memory 1403, and a bus interface, wherein:

in an embodiment where the network function is a core network function:

a transceiver 1402 configured to perform a transmission operation, wherein the transmission operation comprises at least one of:

Optionally, the slice auxiliary information includes at least one of:

mapping relation between the network slices and the slice indexes;

a slice index list;

mapping relation between the network slices and the slice combination indexes;

a slice combination index list;

mapping relation between network slice and cell identification;

a cell identity list;

mapping relation between the network slice and the tracking area;

a tracking area identification list;

mapping relation between the network slice and the core network function index;

a core network function index list;

mapping relation between the network slices and the frequency points;

a list of frequency points;

mapping relation between the network slice and the frequency band;

and (4) frequency band lists.

Optionally, the second slice information includes a slice encryption vector.

Optionally, the slice encryption vector includes:

a random string and an encrypted string;

wherein the encrypted string is generated based on a key and the random string.

Optionally, the second slice routing information includes at least one of:

slice indexing;

slice combination indexing;

a core network function index;

the slice decryption vector.

Optionally, the slice decryption vector includes: a key.

Optionally, before performing the sending operation, the transceiver 1402 is further configured to:

In the embodiment where the network function is an access network side device:

a transceiver 1402, configured to receive first slice routing information sent by a terminal;

a processor 1401, configured to select a core network function according to the first slice routing information.

Optionally, the second slice routing information includes at least one of:

slice indexing;

slice combination indexing;

a core network function index;

the slice decryption vector.

Optionally, the slice decryption vector includes: a key.

Optionally, the first slice routing information includes: a slice indication vector, wherein the slice indication vector comprises slice encryption information and a random string, wherein the slice encryption information is generated based on an encryption string and first routing information, and processor 1401 is further configured to:

Optionally, the first routing information includes one of:

Optionally, before selecting the core network function according to the first routing information and the second slice routing information, the transceiver 1402 is further configured to receive the second slice routing information sent by the core network function.

Optionally, before selecting the core network function according to the first routing information and the second slice routing information, the transceiver 1402 is further configured to send slice support information to the core network, where the slice support information is used by the core network function to generate the slice auxiliary information.

The network function can make the access network side equipment easily select the core network function matched with the terminal.

Wherein the transceiver 1402 is configured to receive and transmit data under the control of the processor 1401, the transceiver 1402 comprising at least two antenna ports.

In fig. 14, the bus architecture may include any number of interconnected buses and bridges, with one or more processors, represented by processor 1401, and various circuits, represented by memory 1403, linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 1402 may be a plurality of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium. For different user devices, the user interface 1404 may also be an interface capable of interfacing with a desired device externally, including but not limited to a keypad, display, speaker, microphone, joystick, etc.

The processor 1401 is responsible for managing a bus architecture and general processing, and the memory 1403 may store data used by the processor 1401 in performing operations.

Preferably, the embodiment of the present application further provides a core network function, which includes a processor 1401, a memory 1403, and a program or an instruction stored in the memory 1403 and capable of being executed on the processor 1401, where the program or the instruction is executed by the processor 1401 to implement each process of the above-mentioned information sending method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not described here again.

Preferably, an embodiment of the present application further provides an access network-side device, including a processor 1401, a memory 1403, and a program or an instruction stored in the memory 1403 and capable of being executed on the processor 1401, where the program or the instruction, when executed by the processor 1401, implements each process of the above-mentioned core network function selection method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not described here again.

The embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of the above-mentioned embodiments of the information reporting method, the information sending method, or the core network function selection method, and can achieve the same technical effect, and in order to avoid repetition, the detailed description is omitted here.

The processor is the processor in the terminal or the network device in the above embodiments. The readable storage medium includes a computer readable storage medium, such as a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and so on.

The embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction to implement each process of the above-mentioned embodiments of the information reporting method, the information sending method, or the core network function selection method, and can achieve the same technical effect, and in order to avoid repetition, the description is omitted here.

It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as system-on-chip, system-on-chip or system-on-chip, etc.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Further, it should be noted that the scope of the methods and apparatus of the embodiments of the present application is not limited to performing the functions in the order illustrated or discussed, but may include performing the functions in a substantially simultaneous manner or in a reverse order based on the functions involved, e.g., the methods described may be performed in an order different than that described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present application.

While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the invention is not limited to the precise embodiments described above, which are meant to be illustrative and not restrictive, and that various changes may be made therein by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.

Claims

1. An information reporting method is applied to a terminal, and is characterized by comprising the following steps:

and sending first slice routing information to the access network side equipment, wherein the first slice routing information is generated based on slice auxiliary information and is used for the access network side equipment to select a core network function.

2. The method of claim 1, wherein before sending the first slice routing information to the access network-side device, the method further comprises:

3. The method of claim 1 or 2, wherein the slicing assistance information comprises at least one of:

4. The method of claim 3, wherein the first slice information comprises information related to the network slice comprising at least one of:

mapping relation between the network slices and the slice indexes;

a slice index list;

mapping relation between the network slices and the slice combination indexes;

a slice combination index list;

mapping relation between network slice and cell identification;

a cell identity list;

mapping relation between the network slice and the tracking area;

a tracking area identification list;

mapping relation between the network slice and the core network function index;

a core network function index list;

mapping relation between the network slices and the frequency points;

a list of frequency points;

mapping relation between the network slice and the frequency band;

and (4) frequency band lists.

5. The method of claim 3, wherein the second slice information comprises a slice encryption vector.

6. The method of claim 5, wherein the slice encryption vector comprises:

a random string and an encrypted string;

wherein the encrypted string is generated based on a key and the random string.

7. The method of claim 6, wherein the slice encryption vector further comprises:

the first slice information.

8. The method of claim 1, wherein the first slice routing information comprises first routing information, wherein the first routing information is used for the access network-side device to select a core network function.

9. The method of claim 6, wherein the first slice routing information comprises: a slice indication vector, wherein the slice indication vector includes slice encryption information and a random string, wherein the slice encryption information is generated based on the slice encryption vector and first routing information.

10. The method of claim 8 or 9, wherein the first routing information comprises one of:

slice index, slice combination index, core network function index.

11. The method of claim 4, wherein the slice assistance information further comprises an index that does not correspond to a network slice.

12. The method of claim 10, wherein the first routing information further comprises:

indices that do not correspond to a network slice.

13. An information sending method is applied to a core network function, and is characterized by comprising the following steps:

14. The method of claim 13, wherein the slicing assistance information comprises at least one of:

15. The method of claim 14, wherein the first slice information comprises information related to the network slice comprising at least one of:

mapping relation between the network slices and the slice indexes;

a slice index list;

mapping relation between the network slices and the slice combination indexes;

a slice combination index list;

mapping relation between network slice and cell identification;

a cell identity list;

mapping relation between the network slice and the tracking area;

a tracking area identification list;

mapping relation between the network slice and the core network function index;

a core network function index list;

mapping relation between the network slices and the frequency points;

a list of frequency points;

mapping relation between the network slice and the frequency band;

and (4) frequency band lists.

16. The method of claim 14, wherein the second slice information comprises a slice encryption vector.

17. The method of claim 16, wherein the slice encryption vector comprises:

a random string and an encrypted string;

wherein the encrypted string is generated based on a key and the random string.

18. The method of claim 17, wherein the slice encryption vector further comprises: the first slice information.

19. The method of claim 13, wherein the second slice routing information comprises at least one of:

slice indexing;

slice combination indexing;

a core network function index;

the slice decryption vector.

20. The method of claim 19, wherein the slice decryption vector comprises: a key.

21. The method of claim 20, wherein the slice decryption vector further comprises: the first slice information.

22. The method of claim 13, wherein a partial slice index or a slice combination index in the second slice routing information does not correspond to a network slice.

23. The method of claim 13, wherein prior to said performing the transmit operation, the method further comprises:

24. A core network function selection method is applied to access network side equipment, and is characterized by comprising the following steps:

receiving first slice routing information sent by a terminal;

25. The method of claim 24, wherein the first slice routing information comprises first routing information, wherein the first routing information is used for the access network-side device to select a core network function.

26. The method of claim 24, wherein the first slice routing information comprises: a slice indication vector, wherein the slice indication vector includes slice encryption information and a random string, wherein the slice encryption information is generated based on the slice encryption vector and first routing information.

27. The method of claim 24, wherein said selecting a core network function based on said first slice routing information comprises:

and selecting a core network function according to first routing information and second slice routing information, wherein the first routing information is acquired based on the first slice routing information.

28. The method of claim 27, wherein selecting a core network function based on the first routing information and the second slice routing information comprises:

29. The method of claim 28, wherein selecting a core network function based on the first routing information and the second slice routing information comprises:

30. The method of claim 29, wherein selecting a core network function based on the second slice routing information and a target index comprises:

31. The method of claim 27, wherein the second slice routing information comprises at least one of:

slice indexing;

slice combination indexing;

a core network function index;

the slice decryption vector.

32. The method of claim 31, wherein the slice decryption vector comprises: a key.

33. The method of claim 31, wherein the first slice routing information comprises: a slice indication vector, wherein the slice indication vector includes slice encryption information and a random string, wherein the slice encryption information is generated based on an encryption string and first routing information, the method further comprising:

34. The method of claim 25, 27 or 33, wherein the first routing information comprises one of:

slice index, slice combination index, core network function index.

35. The method of claim 27, wherein before selecting a core network function based on the first routing information and the second slice routing information, the method further comprises:

36. The method of claim 27, wherein before selecting a core network function based on the first routing information and the second slice routing information, the method further comprises:

and the slicing support information is sent to the core network, wherein the slicing support information is used for the core network function to generate the slicing auxiliary information.

37. An information reporting device is applied to a terminal, and is characterized by comprising:

38. The apparatus of claim 37, wherein the slicing assistance information comprises at least one of:

39. An information transmission apparatus, applied to a core network function, comprising:

a sending module, configured to perform a sending operation, where the sending operation includes at least one of:

40. The apparatus of claim 39, wherein the slicing assistance information comprises at least one of:

41. A core network function selection device is applied to access network side equipment, and is characterized by comprising:

the first receiving module is used for receiving first slice routing information sent by a terminal;

42. The apparatus of claim 41, wherein the selection module is configured to select a core network function based on the first routing information and second slice routing information, wherein the first routing information is obtained based on the first slice routing information.

43. A terminal, comprising: a memory, a processor, and a program or instructions stored on the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the information reporting method according to any one of claims 1 to 12.

44. A core network function, comprising: memory, processor and program or instructions stored on the memory and executable on the processor, which when executed by the processor implement the steps in the method of transmitting information according to any of claims 13 to 23.

45. An access network-side device, comprising: memory, processor and program or instructions stored on the memory and executable on the processor, which when executed by the processor implement the steps in the core network function selection method according to any of claims 24 to 36.

46. A readable storage medium, on which a program or instructions are stored, which when executed by a processor implement the steps in the information reporting method according to any one of claims 1 to 12, or which when executed by a processor implement the steps in the information sending method according to any one of claims 13 to 23, or which when executed by a processor implement the steps in the core network function selecting method according to any one of claims 24 to 36.