CN117501749A

CN117501749A - Method, device, equipment and storage medium for determining RRC establishment cause value

Info

Publication number: CN117501749A
Application number: CN202180099593.XA
Authority: CN
Inventors: 卢飞; 付喆
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2021-10-18
Filing date: 2021-10-18
Publication date: 2024-02-02
Also published as: WO2023065092A1

Abstract

A method, a device, equipment and a storage medium for determining RRC establishment cause value relate to the field of wireless communication. The method is applied to the terminal equipment and comprises the following steps: receiving indication information (501) sent by a network device; determining the radio resource control, RRC, establishment cause value based on indication information (502); the indication information is used for indicating the priority relation between the target service and the slice. The method can determine the RRC establishment cause value based on the priority relation of the target service and the slice.

Description

Method, device, equipment and storage medium for determining RRC establishment cause value

Technical Field

The present invention relates to the field of wireless communications, and in particular, to a method, an apparatus, a device, and a storage medium for determining an RRC establishment cause value.

Background

In order to meet the demands of individual services of wireless communication for delay, mobility, reliability, location accuracy, etc., the radio access network (Radio Access Network, RAN) needs to enhance how multiple services are supported. One way is to provide a service with lower latency, more targeting, greater flexibility and higher scalability for multiple services with different requirements based on network slicing (sliding).

When a UE (User Equipment, terminal Equipment/User Equipment) is configured as an MPS (Multimedia Priority Service ) UE or an MCS (Mission Critical Service, task critical service) UE, RRC (Radio Resource Control ) set by the UE when initiating a service establishes a cause value of high priority, and slices are not considered.

Disclosure of Invention

The embodiment of the application provides a method, a device, equipment and a storage medium for determining an RRC establishment cause value, which can be determined based on the priority relation of a target service and a slice. The technical scheme is as follows:

according to one aspect of the present application, there is provided a method for determining an RRC establishment cause value, applied to a terminal device, the method including:

receiving indication information sent by network equipment;

determining the Radio Resource Control (RRC) establishment cause value based on the indication information;

the indication information is used for indicating the priority relation between the target service and the slice.

According to one aspect of the present application, there is provided a method for determining an RRC establishment cause value, applied to a network device, the method including:

transmitting indication information to a terminal device, wherein the indication information is used for enabling the terminal device to determine the Radio Resource Control (RRC) establishment cause value;

According to an aspect of the present application, there is provided an apparatus for determining an RRC establishment cause value, the apparatus including:

the first receiving module is used for receiving the indication information sent by the network equipment;

a determining module, configured to determine the radio resource control RRC establishment cause value based on the indication information;

a second sending module, configured to send indication information to a terminal device, where the indication information is used to enable the terminal device to determine the radio resource control RRC establishment cause value;

According to an aspect of the present application, there is provided a terminal device comprising: a processor and a transceiver coupled to the processor; wherein,

the transceiver is used for receiving the indication information sent by the network equipment;

the processor is configured to determine the radio resource control RRC establishment cause value based on the indication information;

According to one aspect of the present application, there is provided a network device comprising: a transceiver; wherein,

the transceiver is configured to send indication information to a terminal device, where the indication information is used to enable the terminal device to determine the radio resource control RRC establishment cause value;

According to an aspect of the present application, there is provided a terminal device comprising: the system comprises a processor and a memory, wherein at least one instruction, at least one section of program, a code set or an instruction set is stored in the memory, and the at least one instruction, the at least one section of program, the code set or the instruction set is loaded and executed by the processor to realize the method for determining the RRC establishment cause value.

According to one aspect of the present application, there is provided a network device comprising: the system comprises a processor and a memory, wherein at least one instruction, at least one section of program, a code set or an instruction set is stored in the memory, and the at least one instruction, the at least one section of program, the code set or the instruction set is loaded and executed by the processor to realize the method for determining the RRC establishment cause value.

According to an aspect of the present application, there is provided a computer readable storage medium having stored therein executable instructions loaded and executed by a processor to implement the method of determining an RRC establishment cause value as described in the above aspect.

According to an aspect of the embodiments of the present application, there is provided a chip, where the chip includes programmable logic circuits and/or program instructions, and when the chip is run on a computer device, the chip is configured to implement the method for determining the RRC establishment cause value according to the above aspect.

According to an aspect of the present application, there is provided a computer program product which, when run on a processor of a computer device, causes the computer device to perform the method of determining a cause value for RRC establishment as described in the above aspect.

The technical scheme provided by the embodiment of the application at least comprises the following beneficial effects:

and the network equipment sends the indication information to the terminal equipment, the priority relation between the target service and the slice is indicated through the indication information, and the terminal equipment determines the RRC establishment cause value based on the priority relation. When the target service is prioritized, determining an RRC establishment cause value based on the target service; and when the slice is prioritized, the RRC establishment cause value is determined based on the slice, so that the target service and the slice are fully considered when the RRC establishment cause value is determined, and the network equipment can perform access control based on the slice.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a schematic diagram of a system architecture provided by an exemplary embodiment of the present application;

fig. 2 is a flowchart of a method for determining an RRC establishment cause value according to an exemplary embodiment of the present application;

fig. 3 is a flowchart of a method for determining an RRC establishment cause value according to an exemplary embodiment of the present application;

fig. 4 is a flowchart of a method for determining an RRC establishment cause value according to an exemplary embodiment of the present application;

fig. 5 is a flowchart of a method for determining an RRC establishment cause value according to an exemplary embodiment of the present application;

fig. 6 is a flowchart of a method for determining an RRC establishment cause value according to an exemplary embodiment of the present application;

fig. 7 is a flowchart of a method for determining an RRC establishment cause value according to an exemplary embodiment of the present application;

fig. 8 is a flowchart of a method for determining an RRC establishment cause value according to an exemplary embodiment of the present application;

Fig. 9 is a flowchart of a method for determining an RRC establishment cause value according to an exemplary embodiment of the present application;

fig. 10 is a block diagram of a configuration of an RRC establishment cause value determining apparatus provided in an exemplary embodiment of the present application;

fig. 11 is a block diagram of a configuration of an RRC establishment cause value determining apparatus provided in an exemplary embodiment of the present application;

fig. 12 is a schematic structural diagram of a communication device according to an exemplary embodiment of the present application.

Detailed Description

For the purpose of making the objects, technical solutions and advantages of the present application more apparent, the embodiments of the present application will be described in further detail below with reference to the accompanying drawings.

The network architecture and the service scenario described in the embodiments of the present application are for more clearly describing the technical solution of the embodiments of the present application, and do not constitute a limitation on the technical solution provided in the embodiments of the present application, and those skilled in the art can know that, with the evolution of the network architecture and the appearance of the new service scenario, the technical solution provided in the embodiments of the present application is also applicable to similar technical problems.

Referring to fig. 1, a schematic diagram of a network architecture 100 according to an embodiment of the present application is shown. The network architecture 100 may include: terminal device 10, access network device 20, and core network device 30.

Terminal device 10 may refer to a User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a wireless communication device, a User agent, or a User Equipment. Alternatively, the terminal device 10 may also be a cellular phone, a cordless phone, a session initiation protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a fifth generation mobile communication system (5th Generation System,5GS) or a terminal device in a future evolved Public Land Mobile Network (PLMN), etc., which the embodiments of the present application are not limited to. For convenience of description, the above-mentioned devices are collectively referred to as terminal devices. The number of terminal devices 10 is typically plural, and one or more terminal devices 10 may be distributed within a cell managed by each access network device 20.

The access network device 20 is a device deployed in the access network to provide wireless communication functionality for the terminal device 10. The access network device 20 may include various forms of macro base stations, micro base stations, relay stations, access points, and the like. The names of access network device-capable devices may vary in systems employing different radio access technologies, for example in 5G NR systems, called gndeb or gNB. As communication technology evolves, the name "access network device" may change. For convenience of description, in the embodiment of the present application, the above-mentioned devices for providing the terminal device 10 with the wireless communication function are collectively referred to as an access network device. Alternatively, a communication relationship may be established between the terminal device 10 and the core network device 30 via the access network device 20. Illustratively, in a long term evolution (Long Term Evolution, LTE) system, the access network device 20 may be an evolved universal terrestrial radio network (Evolved Universal Terrestrial Radio Access Network, EUTRAN) or one or more enodebs in EUTRAN; in a 5G NR system, access network device 20 may be a radio access network (Radio Access Network, RAN) or one or more gnbs in the RAN. In the embodiments of the present application, the network device refers to the access network device 20, such as a base station, unless specifically described.

The core network device 30 is a device deployed in the core network, and functions of the core network device 30 are mainly to provide user connection, management of users, and bearer completion of services, and to provide an interface to an external network as a bearer network. For example, core network devices in a 5G NR system may include access and mobility management function (Access and Mobility Management Function, AMF) entities, user plane function (User Plane Function, UPF) entities, and session management function (Session Management Function, SMF) entities, among other devices.

In one example, the access network device 20 and the core network device 30 communicate with each other via some air interface technology, such as an NG interface in a 5G NR system. The access network device 20 and the terminal device 10 communicate with each other via some kind of air interface technology, e.g. Uu interface.

The "5G NR system" in the embodiments of the present application may also be referred to as a 5G system or an NR system, but a person skilled in the art may understand the meaning thereof. The technical solution described in the embodiments of the present application may be applied to an LTE system, a 5G NR system, a subsequent evolution system of the 5G NR system, and other communication systems such as a narrowband internet of things (Narrow Band Internet of Things, NB-IoT) system, which is not limited in this application.

In order to support RAN sliding, NW (Network) indicates supported slice information to UE through broadcast or dedicated information. The specific slice information may be:

frequency priority mapping for each slice (slice- > frequency (ies) - > absolute priority of each of the frequency) (frequency priority mapping per slice (slice- > frequency- > absolute priority per frequency)).

However, in the case where the configuration of MPS/MCS and the configuration of slice coexist or collide, the access network device is required to notify the UE at this time, and MPS/MCS is prioritized or slice is prioritized in the RACH (Random Access Channel ) procedure.

Network based solution is introduced to resolve the issue of prioritization parameter collision with MPS/MCS, i.e., network indicates whether slice override MPS/MCS or MPS/MCS override slice (the present application proposes a network-based solution that solves the problem of priority parameter collision with MPS/MCS, i.e., whether a network indicates whether a slice covers MPS/MCS or MPS/MCS coverage slices).

When a service is initiated by a UE, an NAS (Non Access Stratum, non-Access Stratum) needs to establish RRC connection with an AS (Access Stratum) layer, and the NAS needs to set an RRC establishment cause value according to a service attribute and notify the RRC establishment cause value to the AS layer, but when the UE is configured AS an MPS UE or an MCS UE, the RRC establishment cause value set by the UE when the service is initiated is a high priority (high priority), which is inconsistent with MPS/MCS priority or slice priority indicated by an Access network device in a RACH procedure.

Referring to fig. 2, a flowchart of a method for determining an RRC establishment cause value according to an embodiment of the present application is shown, and the method may be applied to a terminal device of the system architecture shown in fig. 1. The method comprises the following steps.

Step 501: and receiving the indication information sent by the network equipment.

Step 502: the terminal device determines an RRC establishment cause value based on the indication information.

For example, the indication information has a correspondence relationship with the RRC establishment cause value.

The corresponding relation between the indication information and the RRC establishment cause value comprises at least one of the following corresponding relations:

under the condition that the indication information indicates that the target service is better than the slice, the RRC establishment cause value is the target service; or, in case the indication information indicates that the target traffic is better than the slice, the RRC establishment cause value is high priority.

Under the condition that the indication information indicates that the slice is better than the target service, the RRC establishment cause value is that the slice is better than the target service; or, in case the indication information indicates that the slice is better than the target service, the RRC establishment cause value is the calling data service.

Under the condition that the indication information indicates that the slice is better than the target service and the slice requested by the RRC connection accords with the characteristics that the slice is better than the target service, the RRC establishment cause value is that the slice is better than the target service; or under the condition that the indication information indicates that the slice is better than the target service and the slice requested by the RRC connection accords with the characteristic that the slice is better than the target service, the RRC establishment cause value is the calling data service.

Under the condition that the indication information indicates that the slice is better than the target service and the slice requested by the RRC connection does not accord with the characteristic that the slice is better than the target service, the RRC establishment cause value is the target service; or under the condition that the indication information indicates that the slice is better than the target service and the slice requested by the RRC connection does not accord with the characteristic that the slice is better than the target service, the RRC establishment cause value is high priority.

For example, high priority may also be referred to as high priority access (high priority access).

In summary, in the method provided in this embodiment, the network device sends the indication information to the terminal device, and indicates the priority relationship between the target service and the slice through the indication information, and the terminal device determines the RRC establishment cause value based on the priority relationship. When the target service is prioritized, determining an RRC establishment cause value based on the target service; and when the slice is prioritized, the RRC establishment cause value is determined based on the slice, so that the target service and the slice are fully considered when the RRC establishment cause value is determined, and the network equipment can perform access control based on the slice.

Referring to fig. 3, a flowchart of a method for determining an RRC establishment cause value according to an embodiment of the present application is shown, and the method may be applied to a network device of the system architecture shown in fig. 1. The method comprises the following steps.

Step 503: the network device sends indication information to the terminal device, wherein the indication information is used for enabling the terminal device to determine the RRC establishment cause value.

Referring to fig. 4, a flowchart of a method for determining an RRC establishment cause value according to an embodiment of the present application is shown, and the method may be applied to the system architecture shown in fig. 1. The method comprises the following steps.

Step 210: the network device sends indication information to the terminal device.

The indication information is used for enabling the terminal equipment to determine a Radio Resource Control (RRC) establishment cause value;

The target service includes at least one of MPS, MCS (Mission Critical Service ).

That is, the instruction information is used to instruct the target traffic to be prioritized (target traffic to be prioritized over slice), or the slice to be prioritized (slice to be prioritized over target traffic). For example, when the target service is MPS/MCS, the indication information may include "MPS/MCS overrideslice (MPS/MCS takes precedence over slice)" or "sliceoverride MPS/MCS (slice takes precedence over MPS/MCS)".

For example, the indication information may include a specific slice, e.g., the indication information indicates that the first slice is preferred. That is, the slice in the indication information may include a specific S-nsai value (Single Network Slice Selection Assistance Information value ). The indication information may also include a specific slice group, e.g., the indication information indicates that the first slice group is preferred. That is, slices in the indication information may include specific slice group information.

Step 220: the terminal device determines an RRC establishment cause value based on the indication information transmitted by the network device.

The terminal devices include, for example, AS (Access Stratum) and NAS (Non Access Stratum, non-Access Stratum).

In an alternative embodiment: the NAS layer sets an RRC establishment cause value based on the indication information, the NAS sends the set RRC establishment cause value to the AS, and the AS initiates an RRC establishment request to the access network equipment based on the RRC establishment cause value.

In another alternative embodiment: the NAS layer sets an RRC establishment cause value, the NAS sends the set RRC establishment cause value to the AS, the AS changes the RRC establishment cause value based on the indication information, and the AS initiates an RRC establishment request to the access network equipment based on the changed RRC establishment cause value. Illustratively, when the UE is configured as MPS/MCS UE, the NAS sets the RRC establishment cause value to be high priority, or MPS/MCS.

For example, the indication information sent by the network device may be: an RRC establishment cause value set indication or a priority relation indication in RACH (Random Access Channel ).

The RRC establishment cause value setting indication is used to indicate a priority relationship between the target service and the slice in the RRC establishment process.

The priority relation indication in the RACH is used for indicating the priority relation between the target service and the slice in the RACH process.

When the indication information is an RRC establishment cause value setting indication, the RRC establishment cause value setting indication may be sent by the core network device, or the RRC establishment cause value setting indication may be sent by the access network device.

When the indication information is a RACH medium priority relation indication, the RACH medium priority relation indication may be sent by the access network device.

When the indication information is sent by the Access network device, an AS (Access Stratum) of the terminal device can send the indication information to a NAS (Non Access Stratum, non-Access Stratum), and the NAS sets an RRC establishment cause value based on the indication information; the RRC establishment cause value may be changed by the AS based on the indication information after the NAS sets the RRC establishment cause value.

Based on the above description, the following five exemplary embodiments are given:

The core network device sends an RRC establishment cause value setting instruction to the terminal device;

secondly, the access network equipment sends an RRC establishment cause value setting instruction to the terminal equipment, and the NAS sets an RRC establishment cause value;

thirdly, the access network equipment sends an RRC establishment cause value setting instruction to the terminal equipment, and the AS changes the RRC establishment cause value;

fourthly, the access network equipment sends a priority relation instruction in the RACH to the terminal equipment, and the NAS sets an RRC establishment cause value;

and fifthly, the access network equipment sends a priority relation indication in the RACH to the terminal equipment, and the AS changes the RRC establishment cause value.

Of course, the method provided in the present application is not limited to the above-described five exemplary embodiments.

And (one) the core network equipment sends an RRC establishment cause value setting instruction to the terminal equipment.

Referring to fig. 5, a flowchart of a method for determining an RRC establishment cause value according to an embodiment of the present application is shown, and the method may be applied to the system architecture shown in fig. 1. The method comprises the following steps.

Step 201: the terminal device sends a registration request to the core network device.

Illustratively, the network device comprises a core network device.

The UE sends a registration request to the AMF (Access and Mobility Management Function, access and mobility management entity), where the registration request carries user information (information of the terminal device) and slice information requested by the terminal device.

The slice information requested in the registration request of step 201 may be the same or different from the slice information requested when the RRC connection is re-established after step 221.

Step 211: the core network device sends a registration acceptance message to the terminal device, wherein the registration acceptance message comprises an RRC establishment cause value setting instruction.

The AMF returns a registration accept message to the UE, which carries an allowed nsai (Network Slice Selection Assistance Information ) and an RRC establishment cause value setting indication, where the RRC establishment cause value setting indication includes MPS/MCS override slice (MPS/MCS takes precedence over slice, i.e., MPS/MCS takes precedence) or slice override MPS/MCS (slice takes precedence over MPS/MCS, i.e., slice takes precedence).

For example, the RRC establishment cause value setting indication may indicate which slice is specific to take precedence, i.e., slice may include a specific S-nsai value (Single Network Slice Selection Assistance Information value ). For example, the RRC establishment cause value setting indication includes a first slice priority. The RRC establishment cause value setting indication may also include a specific slice group, e.g., the RRC establishment cause value setting indication indicates that the first slice group is prioritized. That is, the slice in the RRC establishment cause value setting indication may include specific slice group information, for example, the first slice group preference (first slice group preference over target traffic) is included in the RRC establishment cause value setting indication.

The terminal device determines the RRC establishment cause value based on an RRC establishment cause value setting indication in a registration accept message sent by the core network device. The terminal equipment sets an RRC establishment cause value through the NAS based on the RRC establishment cause value setting instruction in the registration acceptance message, the NAS transmits the RRC establishment cause value to the AS, and the AS initiates an RRC establishment request to the access network equipment based on the RRC establishment cause value.

In an alternative embodiment, in the case that the RRC establishment cause value setting indicates that the target service is better than the slice, the terminal device sets the RRC establishment cause value as the target service; or, in case that the RRC establishment cause value setting indication indicates that the target service is better than the slicing, the terminal device sets the RRC establishment cause value to be of high priority.

In an alternative embodiment, in the case that the RRC establishment cause value setting indicates that the slice is better than the target service, the terminal device sets the RRC establishment cause value as the slice is better than the target service; or, in the case that the RRC establishment cause value setting indicates that the slice is better than the target service, the terminal device sets the RRC establishment cause value as the calling data service.

In an optional embodiment, when the RRC establishment cause value setting indicates that the slice is better than the target service and the slice requested by the RRC connection meets the characteristics of the slice better than the target service, the terminal device sets the RRC establishment cause value as the slice better than the target service; or, when the RRC establishment cause value setting indicates that the slice is better than the target service and the slice requested by the RRC connection meets the characteristics that the slice is better than the target service, the terminal device sets the RRC establishment cause value as the calling data service.

Under the condition that the RRC establishment cause value setting indication indicates that the slice is better than the target service and the slice requested by the RRC connection does not accord with the characteristic that the slice is better than the target service, the terminal equipment sets the RRC establishment cause value as the target service; or when the RRC establishment cause value setting indication indicates that the slice is better than the target service and the slice requested by the RRC connection does not accord with the characteristic that the slice is better than the target service, the terminal equipment sets the RRC establishment cause value as high priority.

For example, the RRC establishment cause value setting indication may also indicate whether each slice meets a slice-over-target traffic characteristic, e.g., the RRC establishment cause value setting indication indicates that the first slice, the second slice, and the third slice are slices of which the slice is better than the target traffic. If the RRC establishment cause value setting indication includes that the slice is better than the target service, and the slice requested by the RRC connection is the slice with the slice better than the target service, the terminal device sets the RRC establishment cause value as the calling data service.

Taking the MPS/MCS as the target service as an example, in step 201 and step 211, the UE is in a connection state (NAS connection) and communicates with the core network device. In step 220, the UE enters an idle state (NAS connection release); when the UE has a service to initiate again and needs to establish the RRC connection, the UE sets the RRC establishment cause value according to the RRC establishment cause value setting indication in step 221 and slice information requested by the RRC connection. When MPS/MCS override slice, the UE sets the RRC establishment cause value as MPS/MCS or high priority; when slice override MPS/MCS and the requested slice meets the "slice override MPS/MCS" feature, the UE sets the RRC establishment cause value to slice override MPS/MCS or MO data (Mobile Originated data, calling data traffic).

Step 230: the terminal device initiates an RRC establishment request to the access network device, wherein the RRC establishment request comprises an RRC establishment cause value.

In summary, in the method provided in this embodiment, when the terminal device sends a registration request to the core network device, the core network device indicates, in a registration accept message sent to the terminal device, a priority relationship between a target service and a slice in an RRC establishment process, and the terminal device determines an RRC establishment cause value based on the priority relationship. When the target service is prioritized, determining an RRC establishment cause value based on the target service; and when the slice is prioritized, the RRC establishment cause value is determined based on the slice, so that the target service and the slice are fully considered when the RRC establishment cause value is determined, and the network equipment can perform access control based on the slice.

And (II) the access network equipment sends an RRC establishment cause value setting instruction to the terminal equipment, and the NAS sets the RRC establishment cause value.

Referring to fig. 6, a flowchart of a method for determining an RRC establishment cause value according to an embodiment of the present application is shown, and the method may be applied to the system architecture shown in fig. 1. The method comprises the following steps.

Step 212: the access network device sends an RRC establishment cause value setting instruction to the terminal.

The RRC establishment cause value setting indication is carried in a system information block SIB or a proprietary signaling message. The dedicated signaling message may be an RRC release message (RRC release message).

And the terminal equipment receives the RRC establishment cause value setting instruction sent by the access network equipment.

Step 213: the terminal device transmits an RRC establishment cause value setting instruction to the non-access layer through the access layer.

The terminal equipment side includes, for example, NAS and AS.

Step 221: the terminal device sets the RRC establishment cause value based on the RRC establishment cause value setting indication through the non-access stratum.

In an optional embodiment, in the case that the RRC establishment cause value setting indicates that the target service is better than the slice, the terminal device sets the RRC establishment cause value to the target service through the non-access stratum; or, in case that the RRC establishment cause value setting indicates that the target service is better than the slice, the terminal device sets the RRC establishment cause value to be high priority through the non-access stratum.

In an optional embodiment, in a case that the RRC establishment cause value setting indicates that the slice is better than the target service, the terminal device sets the RRC establishment cause value to be that the slice is better than the target service through the non-access stratum; or under the condition that the RRC establishment cause value setting indication indicates that the slice is better than the target service, the terminal equipment sets the RRC establishment cause value as the calling data service through the non-access layer.

In an optional embodiment, when the RRC establishment cause value setting indicates that the slice is better than the target service and the slice requested by the RRC connection meets the characteristics of the slice better than the target service, the terminal device sets the RRC establishment cause value to be the slice better than the target service through the non-access stratum; or when the RRC establishment cause value setting indication indicates that the slice is better than the target service and the slice requested by the RRC connection accords with the characteristic that the slice is better than the target service, the terminal equipment sets the RRC establishment cause value as the calling data service through the non-access stratum.

Under the condition that the RRC establishment cause value setting indication indicates that the slice is better than the target service and the slice requested by the RRC connection does not accord with the characteristic that the slice is better than the target service, the terminal equipment sets the RRC establishment cause value as the target service through a non-access layer; or when the RRC establishment cause value setting indication indicates that the slice is better than the target service and the slice requested by the RRC connection does not accord with the characteristic that the slice is better than the target service, the terminal equipment sets the RRC establishment cause value to be high priority through the non-access stratum.

Taking the MPS/MCS as the target service as an example, when the UE has a service to initiate and needs to establish the RRC connection, the UE sets the RRC establishment cause value according to the RRC establishment cause value setting indication in step 212 and slice information requested by the RRC connection. Illustratively, the RRC establishment cause value in step 212 is sent by the AS to the NAS; when MPS/MCS overrideslice, the UE (NAS) sets the RRC establishment cause value as MPS/MCS or highpriority; when sliceoverride MPS/MCS and the requested slice meets the "sliceoverride MPS/MCS" feature, the UE sets the RRC establishment cause value to sliceoverride MPS/MCS or MO data.

Illustratively, the NAS sends the RRC establishment cause value to the AS.

Illustratively, the terminal device initiates an RRC establishment request to the access network device through the AS, where the RRC establishment request includes the RRC establishment cause value set in step 221.

In summary, in the method provided in this embodiment, the access network device sends the RRC establishment cause value setting indication to the terminal device, and the terminal device determines the RRC establishment cause value based on the priority relationship of the RRC establishment cause value setting indication indicating the priority relationship between the target service and the slice. When the target service is prioritized, determining an RRC establishment cause value based on the target service; and when the slice is prioritized, the RRC establishment cause value is determined based on the slice, so that the target service and the slice are fully considered when the RRC establishment cause value is determined, and the network equipment can perform access control based on the slice.

And thirdly, the access network equipment sends an RRC establishment cause value setting instruction to the terminal equipment, and the AS changes the RRC establishment cause value.

Referring to fig. 7, a flowchart of a method for determining an RRC establishment cause value according to an embodiment of the present application is shown, and the method may be applied to the system architecture shown in fig. 1. The method comprises the following steps.

For example, the RRC establishment cause value setting indication may indicate which slice is specific to take precedence, i.e., slice may include a specific S-nsai value (Single Network Slice Selection Assistance Information value ). For example, the RRC establishment cause value setting indication includes a first slice priority. The RRC establishment cause value setting indication may also include a specific slice group, for example, the RRC establishment cause value setting indication indicates that the first slice group is preferred. That is, the slice in the RRC establishment cause value setting indication may include specific slice group information, for example, the first slice group preference (first slice group preference over target traffic) is included in the RRC establishment cause value setting indication.

Step 224: the terminal device changes the RRC establishment cause value based on the RRC establishment cause value setting indication through the access layer.

In an optional embodiment, in the case that the RRC establishment cause value setting indicates that the target service is better than the slice, the terminal device maintains the RRC establishment cause value as the target service through the access layer; or, in case that the RRC establishment cause value setting indication indicates that the target service is better than slicing, the terminal device maintains the RRC establishment cause value as a high priority through the access layer.

In an optional embodiment, when the RRC establishment cause value setting indicates that the slice is better than the target service, the terminal device changes the RRC establishment cause value to be the slice better than the target service through the access layer; or under the condition that the RRC establishment cause value setting indication indicates that the slice is better than the target service, the terminal equipment changes the RRC establishment cause value into the calling data service through the access layer.

In an optional embodiment, when the RRC establishment cause value setting indicates that the slice is better than the target service and the slice requested by the RRC connection meets the characteristics of the slice better than the target service, the terminal device changes the RRC establishment cause value to be the slice better than the target service through the access layer; or under the condition that the RRC establishment cause value setting indication indicates that the slice is better than the target service and the slice requested by the RRC connection accords with the characteristic that the slice is better than the target service, the terminal equipment changes the RRC establishment cause value into the calling data service through the access layer.

Under the condition that the RRC establishment cause value setting indication indicates that the slice is better than the target service and the slice requested by the RRC connection does not accord with the characteristic that the slice is better than the target service, the terminal equipment changes the RRC establishment cause value into the target service through the access layer; or under the condition that the RRC establishment cause value setting indication indicates that the slice is better than the target service and the slice requested by the RRC connection does not accord with the characteristic that the slice is better than the target service, the terminal equipment changes the RRC establishment cause value into high priority through the access layer.

Taking the MPS/MCS as the target service as an example, when the UE has a service to initiate and needs to establish the RRC connection, the UE sets the RRC establishment cause value according to the RRC establishment cause value setting indication in step 212 and slice information requested by the RRC connection. When the RRC establishment cause value setting indication indicates MPS/MCS overrideslice, the UE (AS) changes the RRC establishment cause value to MPS/MCS or highpriority; when sliceoverride MPS/MCS and the requested slice meets the "sliceoverride MPS/MCS" feature, the AS alters the RRC establishment cause value to sliceoverride MPS/MCS or MO data.

Illustratively, steps 222 and 223 may also be included prior to step 224. Step 222: and the terminal equipment sets the RRC establishment cause value as a target service or high priority through a non-access layer under the condition that the terminal equipment is configured as a target service terminal (MPS UE/MCS UE). Step 223: the terminal device transmits the RRC establishment cause value to the access layer through the non-access layer.

The terminal device initiates an RRC establishment request to the access network device through the AS, where the RRC establishment request includes the modified RRC establishment cause value.

And (IV) the access network equipment sends the priority relation indication in the RACH to the terminal equipment, and the NAS sets the RRC establishment cause value.

Referring to fig. 8, a flowchart of a method for determining an RRC establishment cause value according to an embodiment of the present application is shown, and the method may be applied to the system architecture shown in fig. 1. The method comprises the following steps.

Step 214: the access network device sends a priority relation indication in the RACH to the terminal.

The priority relation indication in RACH is carried in a system information block SIB or a proprietary signaling message. The dedicated signaling message may be an RRC release message (RRC release message).

Illustratively, when the configuration of MPS/MCS and the configuration of the slice coexist or collide, the access network device will inform the UE to take MPS/MCS priority or slice priority in the RACH procedure. The embodiment of the application can determine the RRC establishment cause value through the priority relation between the MPS/MCS and the slice in the RACH process indicated by the access network equipment.

For example, the priority relationship indication in RACH may indicate which slice is specific in priority, i.e., slice may include a specific S-nsai value (Single Network Slice Selection Assistance Information value ). For example, the first slice priority is included in the priority relation indication in RACH. The RACH in priority relation indication may also include a specific slice group, e.g. the RACH in priority relation indication indicates that the first slice group is prioritized. That is, the slices in the priority relation indication in the RACH may include specific slice group information, for example, the first slice group priority (first slice group takes precedence over the target traffic) is included in the priority relation indication in the RACH.

Step 215: the terminal device transmits the priority relation indication in the RACH to the non-access stratum through the access stratum.

Step 225: the terminal device sets an RRC establishment cause value based on the priority relation indication in the RACH through the non-access layer.

In an alternative embodiment, in the case that the priority relation indication indicates that the target service is better than slicing in the RACH, the terminal device sets the RRC establishment cause value as the target service through the non-access stratum; or if the priority relation indication in the RACH indicates that the target service is better than the slicing, the terminal equipment sets the RRC establishment cause value to be high priority through the non-access stratum.

In an alternative embodiment, in the case that the priority relation indication indicates that the slice is better than the target service in the RACH, the terminal device sets the RRC establishment cause value to be that the slice is better than the target service through the non-access stratum; or under the condition that the priority relation indication slice in the RACH is better than the target service, the terminal equipment sets the RRC establishment cause value as the calling data service through the non-access layer.

In an optional embodiment, when the priority relation indication indicates that the slice is better than the target service in the RACH and the slice requested by the RRC connection meets the characteristics of the slice better than the target service, the terminal device sets the RRC establishment cause value to be the slice better than the target service through the non-access stratum; or under the condition that the priority relation indication indicates that the slice is better than the target service and the slice requested by the RRC connection accords with the characteristic that the slice is better than the target service in the RACH, the terminal equipment sets the RRC establishment cause value as the calling data service through the non-access stratum.

Under the condition that the priority relation indication indicates that the slice is better than the target service and the slice requested by the RRC connection does not accord with the characteristic that the slice is better than the target service in the RACH, the terminal equipment sets the RRC establishment cause value as the target service through a non-access stratum; or under the condition that the priority relation indication indicates that the slice is better than the target service and the slice requested by the RRC connection does not accord with the characteristic that the slice is better than the target service in the RACH, the terminal equipment sets the RRC establishment cause value as high priority through the non-access stratum.

Taking the target service AS an example of MPS/MCS, the AS sends the indication of the priority relation in the RACH in the step 214 to the NAS; when MPS/MCS overrideslice, NAS sets the RRC establishment cause value as MPS/MCS or highpriority; when sliceoverride MPS/MCS and the requested slice meets the "sliceoverride MPS/MCS" feature, the NAS sets the RRC establishment cause value to sliceoverride MPS/MCS or MO data.

Illustratively, the NAS sends the RRC establishment cause value to the AS.

Illustratively, the terminal device initiates an RRC establishment request to the access network device through the AS, where the RRC establishment request includes the RRC establishment cause value set in step 225.

In summary, in the method provided in this embodiment, the access network device sends the priority relation indication in the RACH to the terminal device, and indicates the priority relation between the target service and the slice through the priority relation indication in the RACH, and the terminal device determines the RRC establishment cause value based on the priority relation. When the target service is prioritized, determining an RRC establishment cause value based on the target service; and when the slice is prioritized, the RRC establishment cause value is determined based on the slice, so that the target service and the slice are fully considered when the RRC establishment cause value is determined, and the network equipment can perform access control based on the slice.

Fig. 9 is a flowchart illustrating a method for determining an RRC establishment cause value according to an embodiment of the present application, which may be applied to the system architecture shown in fig. 1. The method comprises the following steps.

Step 228: the terminal device changes the RRC establishment cause value based on the priority relation indication in the RACH through the access layer.

In an alternative embodiment, in the case that the priority relation indication indicates that the target service is better than the slice in the RACH, the terminal device maintains the RRC establishment cause value as the target service through the access layer; or, in the case that the priority relation indication indicates that the target service is better than the slice in the RACH, the terminal device maintains the RRC establishment cause value as a high priority through the access layer.

In an alternative embodiment, in the case that the priority relation indication indicates that the slice is better than the target service in the RACH, the terminal device changes the RRC establishment cause value to be that the slice is better than the target service through the access layer; or under the condition that the priority relation indication slice in the RACH is better than the target service, the terminal equipment changes the RRC establishment cause value into the calling data service through the access layer.

In an optional embodiment, when the priority relation indication indicates that the slice is better than the target service in the RACH and the slice requested by the RRC connection meets the characteristics of the slice better than the target service, the terminal device changes the RRC establishment cause value to be the slice better than the target service through the access layer; or under the condition that the priority relation indication indicates that the slice is better than the target service and the slice requested by the RRC connection accords with the characteristic that the slice is better than the target service in the RACH, the terminal equipment changes the RRC establishment cause value into the calling data service through the access layer.

When the priority relation indication indicates that the slice is better than the target service and the slice requested by the RRC connection does not accord with the characteristic that the slice is better than the target service, the terminal equipment maintains the RRC establishment cause value as the target service through the access layer; or under the condition that the priority relation indication in the RACH indicates that the slice is better than the target service and the slice requested by the RRC connection does not accord with the characteristic that the slice is better than the target service, the terminal equipment maintains the RRC establishment cause value to be high priority through the access layer.

Taking the target service as an MPS/MCS as an example, when the UE is configured as the MPS/MCS, the NAS sets the RRC establishment cause value as the MPS/MCS or the highpriority; when MPS/MCS overrideslice, AS maintains RRC establishment cause value AS MPS/MCS or highpriority ccess; when sliceoverride MPS/MCS and the requested slice meets the "sliceoverride MPS/MCS" feature, the AS changes the RRC establishment cause value to sliceoverride MPS/MCS or MO data.

Illustratively, steps 226 and 227 may also be included prior to step 228. Step 226: and the terminal equipment sets the RRC establishment cause value as a target service or high priority through a non-access layer under the condition that the terminal equipment is configured as a target service terminal (MPS UE/MCS UE). Step 227: the terminal device transmits the RRC establishment cause value to the access layer through the non-access layer.

Fig. 10 is a block diagram illustrating a configuration of an apparatus for determining an RRC establishment cause value according to an exemplary embodiment of the present application, where the apparatus may be implemented as a terminal device or as a part of a terminal device, and the apparatus includes:

a first receiving module 302, configured to receive indication information sent by a network device;

a determining module 301, configured to determine the radio resource control RRC establishment cause value based on the indication information;

In an optional embodiment, the determining module 301 is configured to determine, based on the indication information, that the RRC establishment cause value is the target service, where the indication information indicates that the target service is better than the slice;

or, the determining module 301 is configured to determine, based on the indication information, that the RRC establishment cause value is high priority, if the indication information indicates that the target service is better than the slice.

In an optional embodiment, the determining module 301 is configured to determine, based on the indication information, that the RRC establishment cause value is that the slice is better than the target service, if the indication information indicates that the slice is better than the target service;

Or, the determining module 301 is configured to determine, based on the indication information, that the RRC establishment cause value is a calling data service, if the indication information indicates that the slice is better than the target service.

In an optional embodiment, the determining module 301 is configured to determine, based on the indication information, that the RRC establishment cause value is that the slice is better than the target service, where the indication information indicates that the slice is better than the target service and that the slice requested by the RRC connection meets a slice-better-than-target service characteristic;

the determining module 301 is configured to determine, based on the indication information, that the RRC establishment cause value is a calling data service, when the indication information indicates that the slice is better than the target service and that the slice requested by the RRC connection meets a slice-better-than-target service feature.

In an optional embodiment, the terminal device side includes an access layer and a non-access layer, and the apparatus further includes:

a transmitting module 304, configured to transmit the indication information to the non-access stratum through the access stratum;

the determining module 301 is configured to set, by the non-access stratum, the RRC establishment cause value based on the indication information.

In an optional embodiment, the determining module 301 is configured to set, by the non-access stratum, the RRC establishment cause value to the target service if the indication information indicates that the target service is better than the slice;

or, the determining module 301 is configured to set, by the non-access stratum, the RRC establishment cause value to be high priority if the indication information indicates that the target service is better than the slice.

In an optional embodiment, the determining module 301 is configured to set, by the non-access stratum, the RRC establishment cause value to be that the slice is better than the target service, if the indication information indicates that the slice is better than the target service;

or, the determining module 301 is configured to set, by using the non-access stratum, the RRC establishment cause value to be a calling data service if the indication information indicates that the slice is better than the target service.

In an optional embodiment, the determining module 301 is configured to set, when the indication information indicates that the slice is better than the target service and the slice requested by the RRC connection meets a slice-better-than-target service feature, the RRC establishment cause value to be the slice better than the target service through the non-access stratum;

The determining module 301 is configured to set, by using the non-access layer, the RRC establishment cause value to be a calling data service when the indication information indicates that the slice is better than the target service and the slice requested by the RRC connection meets a slice-better-than-target service feature.

In an alternative embodiment, the terminal device side includes an access layer and a non-access layer; the apparatus further comprises:

the determining module 301 is configured to set, when the terminal device is configured as the target service terminal, the RRC establishment cause value to be the target service or high priority through the non-access stratum;

a transmitting module 304, configured to transmit, to the access layer through the non-access layer, the RRC establishment cause value;

the determining module 301 is configured to change, by the access layer, the RRC establishment cause value based on the indication information.

In an optional embodiment, the determining module 301 is configured to maintain, by the access layer, the RRC establishment cause value as the target service if the indication information indicates that the target service is better than the slice;

or, the determining module 301 is configured to maintain, by the access layer, the RRC establishment cause value to be high priority if the indication information indicates that the target service is better than the slice.

In an optional embodiment, the determining module 301 is configured to, if the indication information indicates that the slice is better than the target service, change, by the access layer, the RRC establishment cause value to be that the slice is better than the target service;

or, the determining module 301 is configured to change, by the access layer, the RRC establishment cause value to be a calling data service if the indication information indicates that the slice is better than the target service.

In an optional embodiment, the determining module 301 is configured to, when the indication information indicates that the slice is better than the target service and the slice requested by the RRC connection meets a slice-better-than-target service feature, change, by the access layer, the RRC establishment cause value to be that the slice is better than the target service;

the determining module 301 is configured to change, through the access layer, the RRC establishment cause value to be the calling data service when the indication information indicates that the slice is better than the target service and the slice requested by the RRC connection meets a slice-better-than-target service characteristic.

In an alternative embodiment, the network device comprises a core network device, and the apparatus further comprises:

A first sending module 303, configured to send a registration request to the core network device;

a first receiving module 302, configured to receive a registration accept message sent by the core network device, where the registration accept message includes the indication information.

In an alternative embodiment, the network device comprises an access network device, and the apparatus further comprises:

a first receiving module 302, configured to receive the indication information sent by the access network device.

In an alternative embodiment, the indication information is carried in a system information block SIB or a proprietary signaling message.

In an optional embodiment, the indication information includes an RRC establishment cause value setting indication, where the RRC establishment cause value setting indication is used to indicate a priority relationship between the target service and the slice in an RRC establishment procedure;

or, the indication information includes a priority relation indication in a random access channel RACH, where the priority relation indication in the RACH is used to indicate a priority relation between the target service and the slice in the RACH procedure.

In an alternative embodiment, the apparatus further comprises:

a first sending module 303, configured to initiate an RRC establishment request to an access network device, where the RRC establishment request includes the RRC establishment cause value.

In an alternative embodiment, the target service includes at least one of a multimedia priority service MPS, a mission critical service MCS.

Fig. 11 is a block diagram of a configuration of an RRC establishment cause value determining apparatus according to an exemplary embodiment of the present application, where the apparatus may be implemented as a network device or as a part of a network device, and the apparatus includes:

a second sending module 401, configured to send indication information to a terminal device, where the indication information is used to enable the terminal device to determine the radio resource control RRC establishment cause value;

In an optional embodiment, the indication information is used for enabling the terminal device to determine that the RRC establishment cause value is the target service based on the indication information if the indication information indicates that the target service is better than the slice;

or, the indication information is used for enabling the terminal equipment to determine that the RRC establishment cause value is high priority based on the indication information when the indication information indicates that the target service is better than the slice.

In an optional embodiment, the indication information is used for enabling the terminal device to determine, based on the indication information, that the RRC establishment cause value is that the slice is better than the target service, if the indication information indicates that the slice is better than the target service;

or the indication information is used for enabling the terminal equipment to determine the RRC establishment cause value as a calling data service based on the indication information under the condition that the indication information indicates that the slice is better than the target service.

In an optional embodiment, the indication information is used for enabling the terminal device to determine, based on the indication information, that the RRC establishment cause value is that the slice is better than the target service when the indication information indicates that the slice is better than the target service and that the slice requested by the RRC connection meets a slice-better-than-target service characteristic;

or, the indication information is used for enabling the terminal device to determine that the RRC establishment cause value is a calling data service based on the indication information when the indication information indicates that the slice is better than the target service and the slice requested by the RRC connection accords with the slice-better-than-target service feature.

a second receiving module 402, configured to receive a registration request sent by the terminal device;

the second sending module 401 is configured to send a registration accept message to the terminal device, where the registration accept message includes the indication information.

In an alternative embodiment, the network device comprises an access network device;

the second sending module 401 is configured to send the indication information to the terminal device.

A second receiving module 402, configured to receive an RRC establishment request initiated by the terminal device, where the RRC establishment request includes the RRC establishment cause value.

Fig. 12 shows a schematic structural diagram of a communication device (terminal device or network device) according to an exemplary embodiment of the present application, where the communication device includes: a processor 101, a receiver 102, a transmitter 103, a memory 104, and a bus 105.

The processor 101 includes one or more processing cores, and the processor 101 executes various functional applications and information processing by running software programs and modules.

The receiver 102 and the transmitter 103 may be implemented as one communication component, which may be a communication chip, which may be referred to as a transceiver.

The memory 104 is connected to the processor 101 via a bus 105.

The memory 104 may be used to store at least one instruction that the processor 101 is configured to execute to implement the various steps of the method embodiments described above.

Further, the memory 104 may be implemented by any type of volatile or nonvolatile storage device or combination thereof, including but not limited to: magnetic or optical disks, electrically erasable programmable Read-Only Memory (EEPROM), erasable programmable Read-Only Memory (Erasable Programmable Read Only Memory, EPROM), static random access Memory (Static Random Access Memory, SRAM), read-Only Memory (ROM), magnetic Memory, flash Memory, programmable Read-Only Memory (Programmable Read-Only Memory, PROM).

When the communication device is implemented as a terminal device, the processor and the transceiver in the communication device according to the embodiments of the present application may execute steps executed by the terminal device in any of the methods shown in fig. 2 to 9, which are not described herein.

In one possible implementation, when the communication device is implemented as a terminal device,

When the communication device is implemented as a network device, the processor and the transceiver in the communication device according to the embodiments of the present application may execute the steps executed by the network device in any of the methods shown in fig. 2 to 9, which are not described herein again.

In one possible implementation, when the communication device is implemented as a network device,

In an exemplary embodiment, there is also provided a computer readable storage medium having stored therein at least one instruction, at least one program, a code set, or an instruction set, which is loaded and executed by a processor to implement the method for determining an RRC establishment cause value performed by a communication device provided in the above respective method embodiments.

In an exemplary embodiment, a chip is also provided, which includes programmable logic circuits and/or program instructions, for implementing the method for determining the RRC establishment cause value described in the above aspect when the chip is run on a computer device.

In an exemplary embodiment, there is also provided a computer program product, which when run on a processor of a computer device, causes the computer device to perform the method of determining an RRC establishment cause value according to the above aspect.

It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program for instructing relevant hardware, where the program may be stored in a computer readable storage medium, and the storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.

The foregoing description of the preferred embodiments is merely exemplary in nature and is in no way intended to limit the invention, since it is intended that all modifications, equivalents, improvements, etc. that fall within the spirit and scope of the invention.

Claims

A method for determining an RRC establishment cause value, which is applied to a terminal device, the method comprising:

receiving indication information sent by network equipment;

determining the Radio Resource Control (RRC) establishment cause value based on the indication information;

the indication information is used for indicating the priority relation between the target service and the slice.
The method according to claim 1, wherein the determining the radio resource control, RRC, establishment cause value based on the indication information sent by the network device comprises:

determining the RRC establishment cause value as the target service based on the indication information when the indication information indicates that the target service is better than the slice;

or, in case the indication information indicates that the target traffic is better than the slice, determining that the RRC establishment cause value is high priority based on the indication information.
The method according to claim 1, wherein the determining the radio resource control, RRC, establishment cause value based on the indication information sent by the network device comprises:

Determining the RRC establishment cause value as the slice being better than the target service based on the indication information in the case that the indication information indicates that the slice is better than the target service;

or determining the RRC establishment cause value as a calling data service based on the indication information when the indication information indicates that the slice is better than the target service.
The method of claim 3, wherein the determining, based on the indication information, the RRC establishment cause value as the slice being better than the target traffic if the indication information indicates that the slice is better than the target traffic, comprises:

determining that the slice is better than the target service based on the indication information when the indication information indicates that the slice is better than the target service and the slice requested by the RRC connection accords with the characteristics of the slice better than the target service;

and determining that the RRC establishment cause value is a calling data service based on the indication information when the indication information indicates that the slice is better than the target service, including:

and determining the RRC establishment cause value as a calling data service based on the indication information under the condition that the indication information indicates that the slice is superior to the target service and the slice requested by the RRC connection accords with the characteristics that the slice is superior to the target service.
The method of claim 1, wherein the terminal device side includes an access layer and a non-access layer, the method further comprising:

transmitting the indication information to the non-access layer through the access layer;

the determining the radio resource control RRC establishment cause value based on the indication information sent by the network device includes:

setting, by the non-access stratum, the RRC establishment cause value based on the indication information.
The method of claim 5, wherein the setting, by the non-access stratum, the RRC establishment cause value based on the indication information comprises:

setting the RRC establishment cause value as the target service through the non-access stratum under the condition that the indication information indicates that the target service is better than the slice;

or if the indication information indicates that the target service is better than the slice, setting the RRC establishment cause value to be high priority through the non-access stratum.
The method of claim 5, wherein the setting, by the non-access stratum, of the RRC establishment cause value based on the RRC establishment cause value setting indication comprises:

Setting the RRC establishment cause value to be that the slice is better than the target service through the non-access layer under the condition that the indication information indicates that the slice is better than the target service;

or setting the RRC establishment cause value as a calling data service through the non-access layer under the condition that the indication information indicates that the slice is superior to the target service.
The method of claim 7, wherein setting, by the non-access stratum, the RRC establishment cause value to be the slice better than the target traffic if the indication information indicates that the slice is better than the target traffic, comprises:

setting the RRC establishment cause value to be the slice better than the target service through the non-access layer under the condition that the indication information indicates that the slice is better than the target service and the slice requested by the RRC connection accords with the characteristic that the slice is better than the target service;

and setting, by the non-access stratum, the RRC establishment cause value to be a calling data service, where the indication information indicates that the slice is better than the target service, including:

and setting the RRC establishment cause value as a calling data service through the non-access layer under the condition that the indication information indicates that the slice is superior to the target service and the slice requested by the RRC connection accords with the characteristics that the slice is superior to the target service.
The method according to claim 1, wherein the terminal device side comprises an access layer and a non-access layer;

the determining the radio resource control RRC establishment cause value based on the indication information sent by the network device includes:

setting the RRC establishment cause value as the target service or high priority through the non-access stratum under the condition that the terminal equipment is configured as the target service terminal;

transmitting the RRC establishment cause value to the access stratum through the non-access stratum;

and changing the RRC establishment cause value based on the indication information through the access layer.
The method of claim 9, wherein the modifying the RRC establishment cause value by the access layer based on the RRC establishment cause value setting indication comprises:

maintaining the RRC establishment cause value as the target service through the access layer under the condition that the indication information indicates that the target service is better than the slice;

or, if the indication information indicates that the target service is better than the slice, maintaining the RRC establishment cause value as a high priority through the access layer.
The method of claim 9, wherein the modifying the RRC establishment cause value by the access layer based on the RRC establishment cause value setting indication comprises:

Changing the RRC establishment cause value to be the slice better than the target service through the access layer under the condition that the indication information indicates that the slice is better than the target service;

or, if the indication information indicates that the slice is better than the target service, changing the RRC establishment cause value to be the calling data service through the access layer.
The method of claim 11, wherein, if the indication information indicates that the slice is better than the target traffic, altering, by the access layer, the RRC establishment cause value to be the slice better than the target traffic comprises:

when the indication information indicates that the slice is better than the target service and the slice requested by the RRC connection accords with the characteristics that the slice is better than the target service, changing the RRC establishment cause value to be that the slice is better than the target service through the access layer;

and when the indication information indicates that the slice is better than the target service, changing the RRC establishment cause value to be a calling data service through the access layer, including:

and under the condition that the indication information indicates that the slice is superior to the target service and the slice requested by the RRC connection accords with the characteristics that the slice is superior to the target service, changing the RRC establishment cause value into the calling data service through the access layer.
The method according to any of claims 1 to 4, wherein the network device comprises a core network device, the method further comprising:

sending a registration request to the core network equipment;

the receiving the indication information sent by the network device includes:

and receiving a registration acceptance message sent by the core network equipment, wherein the registration acceptance message comprises the indication information.
The method according to any one of claims 6 to 12, wherein the network device comprises an access network device, and the receiving the indication information sent by the network device comprises:

and receiving the indication information sent by the access network equipment.
The method of claim 14, wherein the indication information is carried in a system information block SIB or a proprietary signaling message.
The method of claim 15, wherein the indication information includes an RRC establishment cause value setting indication, the RRC establishment cause value setting indication indicating a priority relationship between the target traffic and the slice during RRC establishment;

or alternatively, the first and second heat exchangers may be,

the indication information comprises a priority relation indication in a random access channel RACH, wherein the priority relation indication in the RACH is used for indicating the priority relation between the target service and the slice in the RACH process.
The method according to any one of claims 1 to 12, further comprising:

and initiating an RRC establishment request to the access network equipment, wherein the RRC establishment request comprises the RRC establishment cause value.
The method according to any of claims 1 to 12, wherein the target service comprises at least one of a multimedia priority service MPS, a mission critical service MCS.
A method for determining an RRC establishment cause value, which is applied to a network device, the method comprising:

transmitting indication information to a terminal device, wherein the indication information is used for enabling the terminal device to determine the Radio Resource Control (RRC) establishment cause value;

the indication information is used for indicating the priority relation between the target service and the slice.
The method according to claim 19, wherein the indication information is used for enabling the terminal device to determine the RRC establishment cause value as the target service based on the indication information if the indication information indicates that the target service is better than the slice;

or, the indication information is used for enabling the terminal equipment to determine that the RRC establishment cause value is high priority based on the indication information when the indication information indicates that the target service is better than the slice.
The method according to claim 19, wherein the indication information is used for enabling the terminal device to determine, based on the indication information, that the RRC establishment cause value is that the slice is better than the target service, if the indication information indicates that the slice is better than the target service;

or the indication information is used for enabling the terminal equipment to determine the RRC establishment cause value as a calling data service based on the indication information under the condition that the indication information indicates that the slice is better than the target service.
The method according to claim 19, wherein the indication information is used for enabling the terminal device to determine, based on the indication information, that the RRC establishment cause value is that the slice is better than the target service, if the indication information indicates that the slice is better than the target service and that the slice requested by the RRC connection meets a slice-better-than-target service characteristic;

or, the indication information is used for enabling the terminal device to determine that the RRC establishment cause value is a calling data service based on the indication information when the indication information indicates that the slice is better than the target service and the slice requested by the RRC connection accords with the slice-better-than-target service feature.
The method according to any of claims 19 to 22, wherein the network device comprises a core network device, the method further comprising:

receiving a registration request sent by the terminal equipment;

and sending a registration acceptance message to the terminal equipment, wherein the registration acceptance message comprises the indication information.
The method according to any of claims 19 to 22, wherein the network device comprises an access network device, the method further comprising:

and sending the indication information to the terminal equipment.
The method of claim 24, wherein the indication information is carried in a system information block SIB or a proprietary signaling message.
The method of claim 25, wherein the indication information includes an RRC establishment cause value setting indication indicating a priority relationship between the target traffic and the slice during RRC establishment;

or, the indication information includes a priority relation indication in a random access channel RACH, where the priority relation indication in the RACH is used to indicate a priority relation between the target service and the slice in the RACH procedure.
The method according to any of claims 19 to 22, wherein the network device comprises an access network device, the method further comprising:

And receiving an RRC establishment request initiated by the terminal equipment, wherein the RRC establishment request comprises the RRC establishment cause value.
The method according to any of claims 19 to 22, wherein the target service comprises at least one of a multimedia priority service MPS, a mission critical service MCS.
An apparatus for determining an RRC establishment cause value, the apparatus comprising:

the first receiving module is used for receiving the indication information sent by the network equipment;

a determining module, configured to determine the radio resource control RRC establishment cause value based on the indication information;

the indication information is used for indicating the priority relation between the target service and the slice.
The apparatus of claim 29, wherein the means for determining, based on the indication information, the RRC establishment cause value as the target traffic if the indication information indicates that the target traffic is better than the slice;

or the determining module is configured to determine that the RRC establishment cause value is high priority based on the indication information if the indication information indicates that the target service is better than the slice.
The apparatus of claim 29, wherein the means for determining, based on the indication information, that the RRC establishment cause value is that the slice is better than the target traffic if the indication information indicates that the slice is better than the target traffic;

Or the determining module is configured to determine, based on the indication information, that the RRC establishment cause value is a calling data service, if the indication information indicates that the slice is better than the target service.
The apparatus of claim 31, wherein the means for determining, based on the indication information, that the RRC establishment cause value is that the slice is better than the target service if the indication information indicates that the slice is better than the target service and that the slice requested by the RRC connection meets a slice better than target service characteristic;

and the determining module is configured to determine, based on the indication information, that the RRC establishment cause value is a calling data service, when the indication information indicates that the slice is better than the target service and that the slice requested by the RRC connection meets a slice-better-than-target service characteristic.
The apparatus of claim 29, wherein the terminal device side comprises an access layer and a non-access layer, the apparatus further comprising:

the transmission module is used for transmitting the indication information to the non-access layer through the access layer;

the determining module is configured to set, by the non-access stratum, the RRC establishment cause value based on the indication information.
The apparatus of claim 33, wherein the means for setting, by the non-access stratum, the RRC establishment cause value to the target traffic if the indication information indicates that the target traffic is better than the slice;

or the determining module is configured to set, by the non-access stratum, the RRC establishment cause value to be high priority if the indication information indicates that the target service is better than the slice.
The apparatus of claim 33, wherein the means for determining, if the indication information indicates that the slice is better than the target service, sets the RRC establishment cause value by the non-access stratum to be the slice better than the target service;

or the determining module is configured to set, by using the non-access layer, the RRC establishment cause value as a calling data service when the indication information indicates that the slice is better than the target service.
The apparatus of claim 35, wherein the determining module is configured to set, by the non-access stratum, the RRC establishment cause value to be that the slice is better than the target service if the indication information indicates that the slice is better than the target service and the slice requested by the RRC connection meets a slice-better-than-target service characteristic;

The determining module is configured to set, when the indication information indicates that the slice is better than the target service and the slice requested by the RRC connection meets a slice-better-than-target service feature, the RRC establishment cause value to be a calling data service through the non-access stratum.
The apparatus of claim 29, wherein the terminal device side comprises an access layer and a non-access layer; the apparatus further comprises:

the determining module is configured to set, when the terminal device is configured as the target service terminal, the RRC establishment cause value to be the target service or high priority through the non-access stratum;

a transmitting module, configured to transmit, to the access layer through the non-access layer, the RRC establishment cause value;

the determining module is configured to modify, by the access layer, the RRC establishment cause value based on the indication information.
The apparatus of claim 37, wherein the means for maintaining, by the access layer, the RRC establishment cause value as the target traffic if the indication information indicates that the target traffic is better than the slice;

or the determining module is configured to maintain, by the access layer, the RRC establishment cause value to be high priority if the indication information indicates that the target service is better than the slice.
The apparatus of claim 37, wherein the means for determining, if the indication information indicates that the slice is better than the target service, alters the RRC establishment cause value by the access layer to be that the slice is better than the target service;

or the determining module is configured to change, through the access layer, the RRC establishment cause value to be a calling data service if the indication information indicates that the slice is better than the target service.
The apparatus of claim 39, wherein the means for determining, if the indication information indicates that the slice is better than the target service and the requested slice for the current RRC connection meets a slice better than target service characteristic, alters the RRC establishment cause value by the access layer to be the slice better than the target service;

and the determining module is configured to change, through the access layer, the RRC establishment cause value to be the calling data service when the indication information indicates that the slice is better than the target service and the slice requested by the RRC connection meets a slice-better-than-target service characteristic.
The apparatus according to any one of claims 29 to 32, wherein the network device comprises a core network device, the apparatus further comprising:

a first sending module, configured to send a registration request to the core network device;

the first receiving module is configured to receive a registration accept message sent by the core network device, where the registration accept message includes the indication information.
The apparatus of any one of claims 34 to 40, wherein the network device comprises an access network device, the apparatus further comprising:

and the first receiving module is used for receiving the indication information sent by the access network equipment.
The apparatus of claim 42, wherein the indication information is carried in a system information block, SIB, or a proprietary signaling message.
The apparatus of claim 43, wherein the indication information comprises an RRC establishment cause value setting indication indicating a priority relationship of the target traffic to the slice during RRC establishment;

or, the indication information includes a priority relation indication in a random access channel RACH, where the priority relation indication in the RACH is used to indicate a priority relation between the target service and the slice in the RACH procedure.
The apparatus according to any one of claims 29 to 32, further comprising:

and the first sending module is used for initiating an RRC establishment request to the access network equipment, wherein the RRC establishment request comprises the RRC establishment cause value.
The apparatus according to any of claims 29 to 32, wherein the target service comprises at least one of a multimedia priority service MPS, a mission critical service MCS.
An apparatus for determining an RRC establishment cause value, the apparatus comprising:

a second sending module, configured to send indication information to a terminal device, where the indication information is used to enable the terminal device to determine the radio resource control RRC establishment cause value;

the indication information is used for indicating the priority relation between the target service and the slice.
The apparatus of claim 47, wherein the indication information is used to cause the terminal device to determine the RRC establishment cause value as the target traffic based on the indication information if the indication information indicates that the target traffic is better than the slice;

or, the indication information is used for enabling the terminal equipment to determine that the RRC establishment cause value is high priority based on the indication information when the indication information indicates that the target service is better than the slice.
The apparatus of claim 47, wherein the indication information is used to cause the terminal device to determine the RRC establishment cause value as the slice being better than the target traffic based on the indication information if the indication information indicates that the slice is better than the target traffic;

or the indication information is used for enabling the terminal equipment to determine the RRC establishment cause value as a calling data service based on the indication information under the condition that the indication information indicates that the slice is better than the target service.
The apparatus of claim 47, wherein the indication information is used to cause the terminal device to determine the RRC establishment cause value as the slice being better than the target service based on the indication information if the indication information indicates that the slice is better than the target service and that a slice requested by the current RRC connection meets a slice-better-than-target service characteristic;

or, the indication information is used for enabling the terminal device to determine that the RRC establishment cause value is a calling data service based on the indication information when the indication information indicates that the slice is better than the target service and the slice requested by the RRC connection accords with the slice-better-than-target service feature.
The apparatus of any one of claims 47 to 50, wherein the network device comprises a core network device, the apparatus further comprising:

the second receiving module is used for receiving a registration request sent by the terminal equipment;

the second sending module is configured to send a registration accept message to the terminal device, where the registration accept message includes the indication information.
The apparatus of any one of claims 47 to 50, wherein the network device comprises an access network device;

the second sending module is configured to send the indication information to the terminal device.
The apparatus of claim 52, wherein the indication information is carried in a system information block SIB or a proprietary signaling message.
The apparatus of claim 53, wherein the indication information comprises an RRC establishment cause value setting indication indicating a priority relationship of the target traffic and the slice during RRC establishment;

or, the indication information includes a priority relation indication in a random access channel RACH, where the priority relation indication in the RACH is used to indicate a priority relation between the target service and the slice in the RACH procedure.
The apparatus of any one of claims 47 to 50, wherein the network device comprises an access network device, the apparatus further comprising:

and the second receiving module is used for receiving an RRC establishment request initiated by the terminal equipment, wherein the RRC establishment request comprises the RRC establishment cause value.
The apparatus according to any of claims 47 to 50, wherein the target service comprises at least one of a multimedia priority service MPS, a mission critical service MCS.
A terminal device, characterized in that the terminal device comprises: a processor and a transceiver coupled to the processor; wherein,

the transceiver is used for receiving the indication information sent by the network equipment;

the processor is configured to determine the radio resource control RRC establishment cause value based on the indication information;

the indication information is used for indicating the priority relation between the target service and the slice.
A network device, the network device comprising: a transceiver; wherein,

the transceiver is configured to send indication information to a terminal device, where the indication information is used to enable the terminal device to determine the radio resource control RRC establishment cause value;

The indication information is used for indicating the priority relation between the target service and the slice.
A terminal device, characterized in that the terminal device comprises: a processor and a memory, wherein the memory stores at least one instruction, at least one program, a code set, or an instruction set, and the at least one instruction, the at least one program, the code set, or the instruction set is loaded and executed by the processor to implement the method for determining an RRC establishment cause value according to any one of claims 1 to 18 or claims 19 to 28.
A network device, the network device comprising: a processor and a memory, wherein the memory stores at least one instruction, at least one program, a code set, or an instruction set, and the at least one instruction, the at least one program, the code set, or the instruction set is loaded and executed by the processor to implement the method for determining an RRC establishment cause value according to any one of claims 1 to 18 or claims 19 to 28.
A computer readable storage medium having stored therein executable instructions that are loaded and executed by a processor to implement the method of determining an RRC establishment cause value according to any of claims 1 to 18 or claims 19 to 28.
A chip comprising programmable logic or a program, the chip being configured to implement the method of determining an RRC establishment cause value according to any of claims 1 to 18 or claims 19 to 28.