CN115942390A

CN115942390A - Slice information reporting method and device, terminal equipment and network equipment

Info

Publication number: CN115942390A
Application number: CN202110955103.3A
Authority: CN
Inventors: 谢芳; 黄学艳
Original assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Current assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Priority date: 2021-08-19
Filing date: 2021-08-19
Publication date: 2023-04-07

Abstract

The application discloses a slice information reporting method and device, terminal equipment and network equipment, wherein the method comprises the following steps: the terminal equipment reports slice related information to the network equipment, wherein the slice related information comprises at least one of the following information: information related to a reselection procedure, information related to a random access procedure.

Description

Slice information reporting method and device, terminal equipment and network equipment

Technical Field

The present application relates to the field of wireless communication technologies, and in particular, to a slice information reporting method and apparatus, a terminal device, and a network device.

Background

Network slicing (referred to as slicing) is an on-demand networking method, which allows operators to separate multiple virtual end-to-end networks on a unified infrastructure. Different slices can be used for services with different attributes, for example, mobile broadband services, internet of vehicles services, internet of things services, and the like can respectively use respective dedicated slices.

When the network deploys the slice, the slice cannot be deployed very accurately because the network does not know the slice-related information of the terminal device.

Disclosure of Invention

In order to solve the above technical problem, embodiments of the present invention provide a slice information reporting method and apparatus, a terminal device, a network device, a chip, and a computer-readable storage medium.

The slice information reporting method provided by the embodiment of the application comprises the following steps:

the terminal device reports slice-related information to the network device, wherein the slice-related information includes at least one of the following: information related to a reselection procedure, information related to a random access procedure.

the method comprises the following steps that network equipment receives slice related information reported by terminal equipment, wherein the slice related information comprises at least one of the following information: information related to a reselection procedure, information related to a random access procedure.

The slice information reporting device provided by the embodiment of the application is applied to terminal equipment, and the device comprises:

a sending unit, configured to report slice-related information to a network device, where the slice-related information includes at least one of the following: information related to a reselection procedure, information related to a random access procedure.

The slice information reporting device provided by the embodiment of the application is applied to network equipment, and the device comprises:

a receiving unit, configured to receive slice-related information reported by a terminal device, where the slice-related information includes at least one of the following: information related to a reselection procedure, information related to a random access procedure.

The terminal device provided by the embodiment of the application comprises: the device comprises a processor and a memory, wherein the memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory and executing any one of the slice information reporting methods.

The network device provided by the embodiment of the application comprises: the device comprises a processor and a memory, wherein the memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory and executing any one of the slice information reporting methods.

The chip provided by the embodiment of the application comprises: and the processor is used for calling and running the computer program from the memory so that the equipment provided with the chip executes any one of the methods.

The computer-readable storage medium provided by the embodiment of the present application is used for storing a computer program, and the computer program enables a computer to execute any one of the methods.

In the technical scheme of the embodiment of the application, the terminal device reports the slice-related information acquired by the terminal device to the network device, so that the network device can be helped to reasonably configure the configuration information related to the slice.

Drawings

FIG. 1 is a schematic diagram of an application scenario of an embodiment of the present application;

fig. 2 is a schematic flowchart of a method for reporting slice information according to an embodiment of the present disclosure;

fig. 3 is a first schematic structural diagram of a slice information reporting apparatus according to an embodiment of the present disclosure;

fig. 4 is a structural configuration diagram of a second device for reporting slice information according to an embodiment of the present disclosure;

fig. 5 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

fig. 6 is a schematic structural diagram of a chip of an embodiment of the present application.

Detailed Description

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

Fig. 1 is a schematic diagram of an application scenario of an embodiment of the present application.

As shown in fig. 1, communication system 100 may include a terminal device 110 and a network device 120. Network device 120 may communicate with terminal device 110 over the air. Multi-service transport is supported between terminal device 110 and network device 120.

It should be understood that the embodiment of the present application is only illustrated as the communication system 100, but the embodiment of the present application is not limited thereto. That is to say, the technical solution of the embodiment of the present application can be applied to various communication systems, for example: a Long Term Evolution (LTE) System, a LTE Time Division Duplex (TDD), a Universal Mobile Telecommunications System (UMTS), an Internet of Things (Internet of Things, ioT) System, a narrowband Internet of Things (NB-IoT) System, an enhanced Machine-Type communication (eMTC) System, a 5G communication System (also called New Radio, NR) communication System), or a future communication System, etc.

In communication system 100 shown in fig. 1, network device 120 may be an access network device that communicates with terminal device 110. An access network device may provide communication coverage for a particular geographic area and may communicate with terminal devices 110 (e.g., UEs) located within the coverage area.

The Network device 120 may be an evolved Node B (eNB or eNodeB) in a Long Term Evolution (Long Term Evolution, LTE) system, or a Next Generation Radio Access Network (NG RAN) device, or a base station (gNB) in an NR system, or a wireless controller in a Cloud Radio Access Network (CRAN), or the Network device 120 may be a relay station, an Access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, or a Network device in a Public Land Mobile Network (PLMN) for future Evolution, or the like.

Terminal device 110 may be any terminal device including, but not limited to, terminal devices that employ wired or wireless connections with network device 120 or other terminal devices.

For example, the terminal device 110 may refer to an access terminal, user Equipment (UE), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or User Equipment. An access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, an IoT device, a satellite handset, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handset having Wireless communication capability, a computing device or other processing device connected to a Wireless modem, a vehicle mounted device, a wearable device, a terminal device in a 5G network or a terminal device in a future evolution network, etc.

The terminal Device 110 may be used for Device-to-Device (D2D) communication.

The wireless communication system 100 may further include a core network device 130 in communication with the base station, and the core network device 130 may be a 5G core network (5G core,5 gc) device, such as an Access and Mobility Management Function (AMF), an Authentication Server Function (AUSF), a User Plane Function (User uplink Function, SMF), and a Session Management Function (SMF). Alternatively, the Core network device 130 may also be an Evolved Packet Core (EPC) device of the LTE network, for example, a Session Management Function + Core Packet Gateway (SMF + PGW-C) device of the Core network. It is understood that SMF + PGW-C may perform the functions that SMF and PGW-C can perform simultaneously. In the network evolution process, the core network device may also be called by other names, or a new network entity is formed by dividing the functions of the core network, which is not limited in this embodiment of the present application.

The functional units in the communication system 100 may also establish a connection through a next generation Network (NG) interface to implement communication.

For example, the terminal device establishes an air interface connection with the access network device through the NR interface, and is used to transmit user plane data and control plane signaling; the terminal equipment can establish control plane signaling connection with the AMF through an NG interface 1 (N1 for short); an access network device, such as a next generation radio access base station (gNB), may establish a user plane data connection with a UPF through an NG interface 3 (N3 for short); the access network equipment can establish control plane signaling connection with the AMF through an NG interface 2 (N2 for short); the UPF can establish a control plane signaling connection with the SMF through an NG interface 4 (N4 for short); the UPF can interact user plane data with a data network through an NG interface 6 (N6 for short); AMF can establish control plane signaling connection with SMF through NG interface 11 (N11 for short); the SMF may establish a control plane signaling connection with the PCF via NG interface 7 (N7 for short).

Fig. 1 exemplarily shows one base station, one core network device, and two terminal devices, alternatively, the wireless communication system 100 may include a plurality of base station devices and may include other numbers of terminal devices within the coverage area of each base station, which is not limited in this embodiment of the present invention.

It should be noted that fig. 1 illustrates a system to which the present application is applied by way of example, and of course, the method shown in the embodiment of the present application may also be applied to other systems. Further, the terms "system" and "network" are often used interchangeably herein. The term "and/or" herein is merely an association relationship describing an associated object, and means that there may be three relationships, for example, a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship. It should also be understood that "indication" mentioned in the embodiments of the present application may be a direct indication, an indirect indication, or an indication of an association relationship. For example, a indicates B, which may mean that a directly indicates B, e.g., B may be obtained by a; it may also mean that a indicates B indirectly, for example, a indicates C, and B may be obtained by C; it can also mean that there is an association between a and B. It should also be understood that "correspond" mentioned in the embodiments of the present application may mean that there is a direct or indirect correspondence between the two, and may also mean that there is an association relationship between the two, and may also be a relationship of indicating and being indicated, configuring and being configured, and the like. It should also be understood that "predefined" or "predefined rule" mentioned in the embodiments of the present application may be implemented by pre-storing corresponding codes, tables or other manners that can be used to indicate related information in devices (e.g., including terminal devices and network devices), and the present application is not limited to the specific implementation manner thereof. Such as predefined, may refer to what is defined in the protocol. It should also be understood that, in the embodiment of the present application, the "protocol" may refer to a standard protocol in the field of communications, and may include, for example, an LTE protocol, an NR protocol, and a related protocol applied in a future communication system, which is not limited in this application.

For the convenience of understanding of the technical solutions of the embodiments of the present application, the following related technologies of the embodiments of the present application are described below, and the following related technologies may be optionally combined with the technical solutions of the embodiments of the present application as alternatives, and all of them belong to the protection scope of the embodiments of the present application.

Network slicing (referred to as slicing) is an on-demand networking method, which allows operators to separate multiple virtual end-to-end networks on a unified infrastructure. Different slices can be used for services with different attributes, for example, mobile broadband services, internet of vehicles services, internet of things services, and the like can respectively use respective dedicated slices. Currently, the way for an operator to support slicing on the network side is: the slices have an association relationship with the frequency points, i.e. the slices supported by different frequency points may be different.

In order to help the terminal device find a cell matching its own needs more quickly, the base station may broadcast information of slices or slice groups supported by the serving cell and/or the neighboring cell, frequency priority information corresponding to each slice or slice group, for example, an Identification (ID) or an Index (Index) of the slice or slice group. The slice group comprises one or more slices, and the concept of the slice group is introduced to avoid the risk of air interface slice privacy exposure and save the overhead of broadcast messages.

Further, to help the terminal device to perform high-priority slice services with low latency as soon as possible, the random access resource of a slice or a slice group may be isolated by allocating an exclusive preamble or a random access opportunity resource to the slice or the slice group, where the random access opportunity resource is a random access channel opportunity (RACH occupancy, RO). Or, the slice or slice group may be configured with a random access priority parameter (e.g., a power-up parameter, a shortened backoff parameter), or with 2-step random access resources, so as to implement differentiated priority access of the slice or slice group, and ensure that the low-delay slice is accessed faster and more preferentially.

The grouping mechanism of slices is the implementation on the network side, for example, one possible scheme is that the network groups the slices with similar Quality of Service (QoS) requirements, so as to conveniently allocate a dedicated preamble or random access opportunity resource or random access priority or 2-step random access resource to the group of slices. However, if the number of terminal devices requesting the same slice or slice group in a region (e.g., one or more cells) is too large, the terminal devices residing on the corresponding frequency may be too concentrated, and a cell corresponding to the frequency may be congested. Moreover, since the terminal device may support multiple slices, and the slices actually expected to be used at different times are different, if reselection is performed according to the frequency priority of the slice or the slice group broadcasted by the network side, a cell that resides when initiating the slice service may not support the slice service, and the terminal device may need to perform slice switching after entering a connected state, so that the terminal device can normally perform the desired slice service.

On the other hand, if the 2-step or 4-step random access resources or priorities corresponding to the slices or slice groups are configured unreasonably, if a large number of terminal devices are configured with the same random access resources or priorities, the random access congestion or failure of the terminal devices may be caused; or conversely, if the same random access resource or priority is configured for few terminal devices, the cell resource on the base station side is wasted.

Since the operator does not know the slice-related information of the services supported or initiated by the terminal devices where the operator resides in the early stage of network deployment, slices or slice groups cannot be deployed very accurately and random access resources cannot be allocated reasonably. If a large number of terminal devices record the slice-related information acquired by the terminal devices and report the slice-related information to the network side, the network side can be helped to configure reasonable slice support capability.

Based on this, the following technical solutions of the embodiments of the present application are provided, in which the terminal device records and reports the slice related information to the network device, so that the network device can be helped to optimize the slice related configuration.

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below with specific embodiments. The above related art can be arbitrarily combined with the technical solutions of the embodiments of the present application as alternatives, which all belong to the scope of protection of the embodiments of the present application. The embodiment of the present application includes at least part of the following contents.

Fig. 2 is a schematic flowchart of a method for reporting slice information provided in an embodiment of the present application, and as shown in fig. 2, the method for reporting slice information includes the following steps:

step 201: the terminal device reports slice-related information to the network device, wherein the slice-related information includes at least one of the following: information related to a reselection procedure, information related to a random access procedure.

In the embodiment of the application, the terminal device reports the slice related information to the network device, and the network device receives the slice related information reported by the terminal device.

In some optional embodiments, the network device is a network manager or a Trace Collection Entity (TCE) or a base station.

In an embodiment of the present application, the slice-related information includes at least one of: information related to a reselection procedure, information related to a random access procedure. The information related to the reselection procedure and the information related to the random access procedure are specifically described below.

Information relating to reselection procedures

In some optional embodiments, the information relating to the reselection procedure comprises at least one of:

relevant identification information of the slice or slice group used by reselection;

frequency information corresponding to the slice or slice group reselected for use;

and priority information of the frequency corresponding to the slice or slice group used in reselection.

Here, the slice or slice group used for reselection is a slice or a handover group with the highest priority determined by the terminal device itself, or a slice or a handover group selected based on the terminal implementation; or, the slice or slice group used for reselection is a slice or a switching group determined by the terminal device based on configuration information or priority information or allowable slice information or available slice information or supported slice information sent by the network device. Here, the information sent by the network device (i.e., the configuration information or the priority information or the allowable slice information or the available slice information or the supported slice information sent by the network device) is carried in a broadcast message or a Radio Resource Control (RRC) release message or a non-access stratum (NAS) message.

It should be noted that the slice or the slice group used for reselection may be a slice or a slice group that the terminal device desires, plans, or requests to perform or preferentially performs during reselection or before reselection, or may be a slice or a slice group determined according to configuration information or priority information on the network side, or allowable slice information, or available slice information, or supported slice information.

In the above scheme, the identification information related to the slice or the slice group may be, for example, an Identification (ID) corresponding to the slice or the slice group, or may also be an Index (Index) corresponding to the slice or the slice group.

In the above scheme, as an example, the frequency information corresponding to a slice or a slice group may be f1, f2, and f3, for example. Here, 3 pieces of frequency information are taken as an example for explanation, and a greater or lesser number of pieces of frequency information are also applicable to the technical solution of the present application.

In the above scheme, as an example, the priority information of the frequency corresponding to the slice or slice group, for example, the priority of f1 is higher than the priority of f2, and the priority of f2 is higher than the priority of f3.

Further, in some optional embodiments, the information related to the reselection process further includes: and when reselection occurs, the frequency point where the terminal equipment resides and/or the target frequency point. It should be noted that the reselection may be intra-frequency reselection or inter-frequency reselection, where for inter-frequency reselection, relevant parameters of inter-frequency reselection include: thresh _X,HighP ，Thresh _X,HighQ ，Thresh _X,LowP ，Thresh _X,LowQ ，Thresh _Serving,LowP ，Thresh _Serving,LowQ 。

In some optional embodiments, the priority information in the above scheme is carried in a broadcast message, or in an RRC message, or in an NAS message.

Information relating to random access procedure

In some optional embodiments, the random access procedure related information comprises at least one of:

identification information of a related slice or a switching group at the time of random access;

information of random access resources used for random access;

information of Reference Signal Receiving Power (RSRP) measured by the terminal device;

the size information of the data packet measured by the terminal equipment;

and the terminal equipment measures the cache information of the logical channel.

It should be noted that, the slice or the handover group related to random access may be a slice or a handover group that the terminal device desires or plans or requests to perform or preferentially perform when initiating a random access procedure or before initiating the random access, or may be a slice or a handover group determined according to configuration information or priority information of the network side, or allowable slice information, or available slice or supported slice information.

In some optional embodiments, the identification information of the slice or the switch group may be, for example, an ID corresponding to the slice or the switch group, or may also be an index corresponding to the slice or the switch group.

In some optional embodiments, the information of the random access resource used by the random access includes at least one of:

first information for indicating whether a type of random access is 2-step random access or 4-step random access;

second information, the second information being used to indicate whether the type of random access is 2-step random access for packet transmission or 4-step random access for packet transmission;

third information indicating a dedicated preamble and/or random access opportunity resource; here, the random access opportunity resource may be an RO resource;

fourth information indicating priority information of random access.

In the foregoing scheme, the priority information of the random access includes, for example, at least one of: power up (powerrampingstephigihpriority), and backoff (scalingfactor bi).

In the foregoing scheme, optionally, when the type of the random access is 2-step random access or 2-step random access for packet transmission, the information related to the random access procedure includes information of RSRP measured by the terminal device.

Here, optionally, the RSRP information may be measured before the terminal device initiates random access.

Here, the RSRP information measured by the terminal device may be, for example, an RSRP value, or a relationship (e.g., a difference or a multiple) between the RSRP value and a threshold configured on the network side.

In the foregoing scheme, optionally, when the type of the random access is 2-step random access for packet transmission or 4-step random access for packet transmission, the information related to the random access process includes size information (data volume) of a data packet measured by the terminal device and/or cache information of each logical channel measured by the terminal device.

Here, optionally, the size information of the data packet and/or the buffering information of the logical channel may be measured before the terminal device initiates the random access.

In this embodiment, the terminal device reports slice-related information to a network device based on first configuration information, where the first configuration information is used to configure content of the slice-related information reported by the terminal device. In some optional embodiments, the first configuration information is configured by the network device or defined by a protocol.

Here, the content of the slice related information recorded and/or reported by the terminal device may be configured by a network device (such as a network manager or a TCE or a base station) to the terminal device, or may be well-defined by a protocol. Taking a configuration mode of a network device as an example, the network device sends first configuration information to the terminal device, where the first configuration information is used to configure content of slice-related information reported by the terminal device.

In some optional embodiments, the terminal device reports the slice-related information to the network device in a connected state or in a process of transitioning to the connected state or in an idle state or in an inactive state.

In some optional embodiments, the terminal device reports the slice-related information to a network device through a defined message or a random access report.

In the embodiment of the present application, the terminal device may report slice related information to the network device in the following manner:

the method I comprises the following steps: the network equipment sends a first request message to the terminal equipment; after receiving a first request message sent by network equipment, the terminal equipment reports slice related information to the network equipment; the network equipment receives the slice related information reported by the terminal equipment; the first request message is used for requesting the terminal device to report slice-related information.

The mode is to report slice related information based on a network device request.

The second method comprises the following steps: the terminal equipment actively reports slice related information to network equipment; and the network equipment receives the slice related information actively reported by the terminal equipment.

The mode is that the terminal equipment actively reports slice related information.

The third method comprises the following steps: the terminal equipment sends a first notification message to network equipment, and the network equipment receives the first notification message sent by the terminal equipment; the network equipment sends a first request message to the terminal equipment, and the terminal equipment reports slice related information to the network equipment after receiving the first request message sent by the network equipment; the network equipment receives the slice related information reported by the terminal equipment; the first notification message is used for notifying the network device, and the terminal device side has stored slice-related information; the first request message is used for requesting the terminal device to report slice-related information.

The terminal device informs the network device that the terminal device side stores the slice-related information, and then reports the slice-related information under the condition of the network device request.

Further, the technical solution of the embodiment of the present application may further include the following: the network equipment configures slice configuration based on the slice related information and sends the slice configuration to the terminal equipment; and the terminal equipment receives the slice configuration sent by the network equipment, wherein the slice configuration is determined based on the slice related information.

As an optimization scheme, if the network device determines, based on the slice-related information, that a service request initiated for a specific slice exceeds a first threshold and/or that a service request initiated for a specific slice group exceeds a second threshold, the network device performs the following configuration: reducing the number of the particular slices in the set of slices.

As an optimization scheme, if the network device determines, based on the slice-related information, that a service request initiated for a specific frequency exceeds a third threshold, the network device performs the following configuration: based on the slices or switching groups supported by the specific frequency points and the priority information of the specific frequency points, adjusting the priority of the frequency points corresponding to the slices or switching groups; and adjusting reselection parameters corresponding to the specific frequency points.

As an optimization scheme, if the network device determines, based on the slice related information, that the number of users of random access initiated for a specific slice or a slice group exceeds a fourth threshold, the network device performs at least one of the following configurations: increasing the number of random access resources corresponding to the specific slice or slice group; adjusting the priority parameter of random access corresponding to the specific slice or slice group; and adjusting the RSRP threshold corresponding to the specific slice or the slice group.

As an example: if the service request for initiating a certain slice or slice group is excessive, the network equipment considers and optimizes the slice group, and reduces the number of hot slices in the same slice group, namely the number of corresponding request terminal equipment.

As an example: if the number of terminal devices requesting slicing on a certain frequency is too large, the network device may readjust the priority of the corresponding frequency point of the slice or slice group in combination with the slicing and priority information supported by the frequency point. If the highest frequencies corresponding to the slices or slice groups 1 and 2 are both f1, the highest frequency of the slice or slice group 2 can be adjusted to other frequencies f2 to reduce the number of users of f 1; reselection parameters, such as ThreshX, highP, threshX, and HighQ, can also be adjusted to increase, so that the terminal device is less likely to reselect to a frequency point with high priority.

As an example: if the number of random access users requesting a certain slice or slice group is too large, the network device may increase corresponding random access resources, including preamble and/or RO resources.

As an example: if the number of terminal devices requesting a high-priority slice or a slice group is too large, the network device adjusts a priority parameter of a corresponding random access, such as a power down ramping stephighpriority parameter (powerramping stephighpriority) and/or a backoff shortening parameter (scalingfacerbi).

As an example: if the number of terminal devices using the 2-step random access resource corresponding to a certain slice or slice group is too large, the corresponding RSRP threshold value may be raised, or more 2-step random access resources, including preamble and/or RO resources, may be allocated.

In the technical scheme of the embodiment of the application, the terminal device records the slice related information acquired by the terminal device and reports the slice related information to the network device, so that the network device can be helped to configure reasonable slice related configuration, such as configuring a reasonable slice group, frequency priority, random access parameters and the like.

Fig. 3 is a schematic structural composition diagram of a slice information reporting apparatus provided in an embodiment of the present application, which is applied to a terminal device, and as shown in fig. 3, the slice information reporting apparatus includes:

a sending unit 301, configured to report slice-related information to a network device, where the slice-related information includes at least one of the following: information related to a reselection procedure, information related to a random access procedure.

identification information related to the slice or slice group to be reselected;

reselecting frequency information corresponding to the used slice or slice group;

priority information of the frequency corresponding to the slice or slice group to be reselected.

In some optional embodiments, the slice or slice group used for reselection is a slice or a handover group with the highest priority determined by the terminal device itself, or the selected slice or handover group is implemented based on the terminal; or the slice group used for reselection is a slice or a switching group determined by the terminal device based on configuration information or priority information or allowable slice information or available slice information or supported slice information sent by the network device.

In some optional embodiments, the configuration information or the priority information or the allowable slice information or the available slice information or the supported slice information sent by the network device is carried in a broadcast message or an RRC message or an NAS message.

information of random access resources used for random access;

information of Reference Signal Received Power (RSRP) measured by the terminal equipment;

the size information of the data packet measured by the terminal equipment;

second information for indicating whether a type of random access is 2-step random access for packet transmission or 4-step random access for packet transmission;

third information indicating a dedicated preamble and/or a random access opportunity resource;

fourth information indicating priority information of random access.

In some optional embodiments, in case that the type of the random access is 2-step random access or 2-step random access for packet transmission, the information related to the random access procedure includes information of RSRP measured by the terminal device.

In some optional embodiments, in a case that the type of the random access is 2-step random access for packet transmission or 4-step random access for packet transmission, the information related to the random access procedure includes size information of a data packet measured by the terminal device and/or buffer information of a logical channel measured by the terminal device.

In some optional embodiments, the sending unit 301 is configured to report the slice-related information to a network device based on first configuration information, where the first configuration information is used to configure content of the slice-related information reported by the terminal device.

In some optional embodiments, the first configuration information is configured by a network device or defined by a protocol.

In some optional embodiments, the sending unit 301 is configured to report the slice related information to a network device in a connected state or in a process of transitioning to the connected state or in an idle state or in an inactive state.

In some optional embodiments, the sending unit 301 is configured to report the slice-related information to a network device through a defined message or a random access report.

In some optional embodiments, the apparatus further comprises: a receiving unit 302;

the receiving unit 302 receives a first request message sent by a network device, and the sending unit 301 reports slice-related information to the network device; the first request message is used for requesting the terminal equipment to report slice-related information; alternatively, the first and second electrodes may be,

the sending unit 301 actively reports slice-related information to a network device; alternatively, the first and second liquid crystal display panels may be,

the sending unit 301 sends a first notification message to a network device, the receiving unit 302 receives a first request message sent by the network device, and the sending unit 301 reports slice-related information to the network device; the first notification message is used for notifying the network device, and the terminal device side has stored slice-related information; the first request message is used for requesting the terminal device to report slice-related information.

In some optional embodiments, the receiving unit 302 is configured to receive a slice configuration transmitted by the network device, where the slice configuration is determined based on the slice related information.

Those skilled in the art will understand that the implementation functions of each unit in the slice information reporting apparatus shown in fig. 3 can be understood by referring to the related description of the foregoing method. The functions of the units in the slice information reporting apparatus shown in fig. 3 may be implemented by a program running on a processor, or may be implemented by specific logic circuits.

Fig. 4 is a schematic structural configuration diagram of a slice information reporting apparatus provided in an embodiment of the present application, which is applied to a network device, and as shown in fig. 4, the slice information reporting apparatus includes:

a receiving unit 401, configured to receive slice-related information reported by a terminal device, where the slice-related information includes at least one of the following: information related to a reselection procedure, information related to a random access procedure.

In some optional embodiments, the information corresponding to the random access procedure includes at least one of:

information of random access resources used for random access;

information of RSRP measured by the terminal equipment;

the size information of the data packet measured by the terminal equipment;

third information indicating a dedicated preamble and/or random access opportunity resource;

fourth information indicating priority information of random access.

In some optional embodiments, the apparatus further comprises: a sending unit 402, configured to send first configuration information to the terminal device, where the first configuration information is used to configure content of the slice-related information reported by the terminal device.

In some optional embodiments, the apparatus further comprises: a transmission unit 402;

the sending unit 402 sends a first request message to a terminal device, and the receiving unit 401 receives slice-related information reported by the terminal device; the first request message is used for requesting the terminal equipment to report slice-related information; alternatively, the first and second electrodes may be,

the receiving unit 401 receives slice related information actively reported by the terminal device; alternatively, the first and second liquid crystal display panels may be,

the receiving unit 401 receives a first notification message sent by a terminal device, the sending unit 402 sends a first request message to the terminal device, and the receiving unit 401 receives slice-related information reported by the terminal device; the first notification message is used for notifying the network device, and the terminal device side has stored slice-related information; the first request message is used for requesting the terminal device to report slice-related information.

In some optional embodiments, the apparatus further comprises: a configuring unit 403, configured to configure a slice configuration based on the slice related information, where the sending unit 402 sends the slice configuration to the terminal device.

In some optional embodiments, the configuring unit 403 is configured to, if it is determined, based on the slice related information, that the service request initiated for a specific slice exceeds a first threshold and/or the service request initiated for a specific slice group exceeds a second threshold, configure the following:

reducing the number of the particular slices in the slice group.

In some optional embodiments, the configuring unit 403 is configured to, if it is determined that the service request initiated for the specific frequency exceeds the third threshold based on the slice related information, perform the following configurations:

based on the slices or switching groups supported by the specific frequency points and the priority information of the specific frequency points, adjusting the priority of the frequency points corresponding to the slices or switching groups;

and adjusting reselection parameters corresponding to the specific frequency points.

In some optional embodiments, the configuring unit 403 is configured to, if it is determined, based on the slice-related information, that the number of users for random access initiated for a specific slice or a slice group exceeds a fourth threshold, perform at least one of the following configurations:

increasing the number of random access resources corresponding to the specific slice or slice group;

adjusting the priority parameter of random access corresponding to the specific slice or the slice group;

and adjusting the corresponding RSRP threshold of the specific slice or the slice group.

Those skilled in the art will understand that the implementation functions of each unit in the slice information reporting apparatus shown in fig. 4 can be understood by referring to the related description of the foregoing method. The functions of the units in the slice information reporting apparatus shown in fig. 4 may be implemented by a program running on a processor, or may be implemented by specific logic circuits.

Fig. 5 is a schematic structural diagram of a communication device 500 according to an embodiment of the present application. The communication device may be a terminal device or a network device, and the communication device 500 shown in fig. 5 includes a processor 510, and the processor 510 may call and execute a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in fig. 5, the communication device 500 may further include a memory 520. From the memory 520, the processor 510 can call and run a computer program to implement the method in the embodiment of the present application.

The memory 520 may be a separate device from the processor 510, or may be integrated into the processor 510.

Optionally, as shown in fig. 5, the communication device 500 may further include a transceiver 530, and the processor 510 may control the transceiver 530 to communicate with other devices, and in particular, may transmit information or data to the other devices or receive information or data transmitted by the other devices.

The transceiver 530 may include a transmitter and a receiver, among others. The transceiver 530 may further include one or more antennas.

Optionally, the communication device 500 may specifically be a network device in the embodiment of the present application, and the communication device 500 may implement a corresponding process implemented by the network device in each method in the embodiment of the present application, which is not described herein again for brevity.

Optionally, the communication device 500 may specifically be a mobile terminal/terminal device according to this embodiment, and the communication device 500 may implement a corresponding process implemented by the mobile terminal/terminal device in each method according to this embodiment, which is not described herein again for brevity.

Fig. 6 is a schematic structural diagram of a chip of an embodiment of the present application. The chip 600 shown in fig. 6 includes a processor 610, and the processor 610 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in fig. 6, the chip 600 may further include a memory 620. From the memory 620, the processor 610 may call and run a computer program to implement the method in the embodiment of the present application.

The memory 620 may be a separate device from the processor 610, or may be integrated into the processor 610.

Optionally, the chip 600 may further include an input interface 630. The processor 610 may control the input interface 630 to communicate with other devices or chips, and in particular, may obtain information or data transmitted by other devices or chips.

Optionally, the chip 600 may further include an output interface 640. The processor 610 may control the output interface 640 to communicate with other devices or chips, and may particularly output information or data to the other devices or chips.

Optionally, the chip may be applied to the network device in the embodiment of the present application, and the chip may implement the corresponding process implemented by the network device in each method in the embodiment of the present application, and for brevity, details are not described here again.

Optionally, the chip may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the chip may implement the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, and for brevity, details are not described here again.

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

It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The Processor may be a general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off the shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.

It will be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of example, but not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), dynamic Random Access Memory (DRAM), synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), double Data Rate Synchronous Dynamic random access memory (DDR SDRAM), enhanced Synchronous SDRAM (ESDRAM), synchronous link SDRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be understood that the above memories are exemplary but not limiting, for example, the memories in the embodiments of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), direct Rambus RAM (DR RAM), and the like. That is, the memory in the embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

The embodiment of the application also provides a computer readable storage medium for storing the computer program.

Optionally, the computer-readable storage medium may be applied to the network device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the network device in each method in the embodiment of the present application, which is not described herein again for brevity.

Optionally, the computer-readable storage medium may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein again for brevity.

Embodiments of the present application also provide a computer program product, including computer program instructions.

Optionally, the computer program product may be applied to the network device in the embodiment of the present application, and the computer program instructions enable the computer to execute corresponding processes implemented by the network device in the methods in the embodiment of the present application, which are not described herein again for brevity.

Optionally, the computer program product may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in the methods in the embodiment of the present application, which are not described herein again for brevity.

The embodiment of the application also provides a computer program.

Optionally, the computer program may be applied to the network device in the embodiment of the present application, and when the computer program runs on a computer, the computer is enabled to execute a corresponding process implemented by the network device in each method in the embodiment of the present application, and for brevity, details are not described here again.

Optionally, the computer program may be applied to the mobile terminal/terminal device in the embodiment of the present application, and when the computer program runs on a computer, the computer is enabled to execute the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein again for brevity.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one position, or may be distributed on multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A slice information reporting method is characterized in that the method comprises the following steps:

2. The method of claim 1, wherein the information related to the reselection procedure comprises at least one of:

3. The method of claim 2,

the slice or slice group used for reselection is a slice or a switching group with the highest priority determined by the terminal equipment, or the slice or the switching group selected is realized based on the terminal; alternatively, the first and second electrodes may be,

the slice or slice group used for reselection is a slice or a switching group determined by the terminal device based on configuration information or priority information or allowable slice information or available slice information or supported slice information sent by the network device.

4. The method of claim 3, wherein the configuration information or the priority information or the allowable slice information or the available slice information or the supported slice information sent by the network device is carried in a broadcast message or a Radio Resource Control (RRC) message or a non-access stratum (NAS) message.

5. The method according to claim 1, wherein the information related to the random access procedure comprises at least one of:

information of random access resources used for random access;

the size information of the data packet measured by the terminal equipment;

6. The method according to claim 5, wherein the information of the random access resource used by the random access comprises at least one of:

fourth information indicating priority information of random access.

7. The method of claim 5, wherein the information related to the random access procedure comprises information of RSRP measured by the terminal device, in case that the type of random access is 2-step random access or 2-step random access for packet transmission.

8. The method according to claim 5, wherein in case that the type of random access is 2-step random access for packet transmission or 4-step random access for packet transmission, the information related to the random access procedure comprises size information of data packets measured by the terminal device and/or buffer information of logical channels measured by the terminal device.

9. The method according to any one of claims 1 to 8, wherein the reporting, by the terminal device, the slice-related information to the network device includes:

the terminal device reports slice-related information to a network device based on first configuration information, wherein the first configuration information is used for configuring the content of the slice-related information reported by the terminal device.

10. The method of claim 9, wherein the first configuration information is configured by a network device or defined by a protocol.

11. The method according to any one of claims 1 to 8, wherein the reporting, by the terminal device, the slice-related information to the network device includes:

and the terminal equipment reports the slice related information to the network equipment in a connected state or in the process of converting into the connected state or in an idle state or in an inactive state.

12. The method according to any one of claims 1 to 8, wherein the reporting, by the terminal device, the slice-related information to the network device includes:

and the terminal equipment reports the slice related information to network equipment through a defined message or a random access report.

13. The method according to any one of claims 1 to 8, wherein the reporting, by the terminal device, the slice-related information to the network device includes:

after receiving a first request message sent by network equipment, the terminal equipment reports slice related information to the network equipment; the first request message is used for requesting the terminal equipment to report slice related information; alternatively, the first and second liquid crystal display panels may be,

the terminal equipment actively reports slice related information to network equipment; alternatively, the first and second electrodes may be,

the terminal equipment sends a first notification message to network equipment, and reports slice related information to the network equipment after receiving a first request message sent by the network equipment; the first notification message is used for notifying the network device, and the terminal device side has stored slice-related information; the first request message is used for requesting the terminal equipment to report slice-related information.

14. The method according to any one of claims 1 to 8, further comprising:

the terminal device receives the slice configuration sent by the network device, wherein the slice configuration is determined based on the slice related information.

15. A slice information reporting method is characterized in that the method comprises the following steps:

the method comprises the steps that network equipment receives slice related information reported by terminal equipment, wherein the slice related information comprises at least one of the following information: information related to a reselection procedure, information related to a random access procedure.

16. The method of claim 15, wherein the information related to the reselection procedure comprises at least one of:

17. The method of claim 16,

18. The method of claim 17, wherein configuration information or priority information or allowable slice information or available slice information or supported slice information sent by the network device is carried in a broadcast message or in an RRC message or in an NAS message.

19. The method of claim 15, wherein the information corresponding to the random access procedure comprises at least one of:

information of random access resources used for random access;

information of RSRP measured by the terminal equipment;

the size information of the data packet measured by the terminal equipment;

20. The method according to claim 19, wherein the information of the random access resource used by the random access comprises at least one of:

fourth information for indicating priority information of random access.

21. The method of claim 19, wherein the information related to the random access procedure comprises information of RSRP measured by the terminal device, in case that the type of random access is 2-step random access or 2-step random access for packet transmission.

22. The method according to claim 19, wherein in case that the type of random access is 2-step random access for packet transmission or 4-step random access for packet transmission, the information related to the random access procedure comprises size information of the data packet measured by the terminal device and/or buffer information of the logical channel measured by the terminal device.

23. The method according to any one of claims 15 to 22, further comprising:

and the network equipment sends first configuration information to the terminal equipment, wherein the first configuration information is used for configuring the content of the slice-related information reported by the terminal equipment.

24. The method according to any one of claims 15 to 22, wherein the receiving, by the network device, the slice-related information reported by the terminal device includes:

the network equipment sends a first request message to terminal equipment and receives slice related information reported by the terminal equipment; the first request message is used for requesting the terminal equipment to report slice related information; alternatively, the first and second electrodes may be,

the network equipment receives slice related information actively reported by the terminal equipment; alternatively, the first and second liquid crystal display panels may be,

the network equipment receives a first notification message sent by terminal equipment, sends a first request message to the terminal equipment and receives slice related information reported by the terminal equipment; the first notification message is used for notifying the network device, and the terminal device side has stored slice-related information; the first request message is used for requesting the terminal device to report slice-related information.

25. The method according to any one of claims 15 to 22, further comprising:

and the network equipment configures slice configuration based on the slice related information and sends the slice configuration to the terminal equipment.

26. The method of claim 25, wherein the network device configures a slice configuration based on the slice-related information, comprising:

if the network device determines, based on the slice-related information, that a service request initiated for a specific slice exceeds a first threshold and/or that a service request initiated for a specific slice group exceeds a second threshold, the network device performs the following configuration:

reducing the number of the particular slices in the set of slices.

27. The method of claim 25, wherein the network device configures a slice configuration based on the slice-related information, comprising:

if the network device determines that the service request initiated for the specific frequency exceeds a third threshold based on the slice-related information, the network device performs the following configuration:

28. The method of claim 25, wherein the network device configures a slice configuration based on the slice-related information, comprising:

if the network device determines, based on the slice-related information, that the number of users of random access initiated for a specific slice or a slice group exceeds a fourth threshold, the network device performs at least one of the following configurations:

29. A slice information reporting device is applied to a terminal device, and the device comprises:

30. A slice information reporting device is applied to a network device, and the device comprises:

31. A terminal device, comprising: a processor and a memory for storing a computer program, the processor being adapted to invoke and execute the computer program stored in the memory, performing the method of any of claims 1 to 14.

32. A network device, comprising: a processor and a memory for storing a computer program, the processor being configured to invoke and execute the computer program stored in the memory to perform the method of any of claims 15 to 28.

33. A chip, comprising: a processor for calling and running a computer program from a memory so that a device on which the chip is installed performs the method of any of claims 1 to 14, or the method of any of claims 15 to 28.

34. A computer-readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 1 to 14 or the method of any one of claims 15 to 28.