A slice information reporting method and device, a terminal device, and a network device

Abstract

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

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and in particular to a method and apparatus for reporting slice information, a terminal device, and a network device. Background Technology

[0002] Network slicing (or simply slicing) is an on-demand networking method that allows operators to create multiple virtual end-to-end networks on a unified infrastructure. Different types of services can use different slices; for example, mobile broadband services, connected vehicle services, and Internet of Things (IoT) services can each use their own dedicated slices.

[0003] When deploying network slices, the network does not know the slice-related information of the terminal devices, which makes it impossible to deploy slices very accurately. Summary of the Invention

[0004] To address the aforementioned technical problems, embodiments of the present invention provide a method and apparatus for reporting slice information, a terminal device, a network device, a chip, and a computer-readable storage medium.

[0005] The slice information reporting method provided in this application includes:

[0006] 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 the reselection process and information related to the random access process.

[0007] The slice information reporting method provided in this application includes:

[0008] The network device receives slice-related information reported by the terminal device, wherein the slice-related information includes at least one of the following: information related to the reselection process and information related to the random access process.

[0009] The slice information reporting device provided in this application embodiment is applied to a terminal device, and the device includes:

[0010] The sending unit is used to report slice-related information to the network device, wherein the slice-related information includes at least one of the following: information related to the reselection process and information related to the random access process.

[0011] The slice information reporting device provided in this application embodiment is applied to a network device, and the device includes:

[0012] The receiving unit is used to receive slice-related information reported by the terminal device, wherein the slice-related information includes at least one of the following: information related to the reselection process and information related to the random access process.

[0013] The terminal device provided in this application includes a processor and a memory. The memory is used to store computer programs, and the processor is used to call and run the computer programs stored in the memory to execute any of the above-described slice information reporting methods.

[0014] The network device provided in this application includes a processor and a memory. The memory is used to store computer programs, and the processor is used to call and run the computer programs stored in the memory to execute any of the above-described slice information reporting methods.

[0015] The chip provided in this application includes a processor for calling and running a computer program from a memory, causing a device on which the chip is installed to perform any of the methods described above.

[0016] The computer-readable storage medium provided in this application embodiment is used to store a computer program that causes a computer to execute any of the methods described above.

[0017] In the technical solution of this application embodiment, the terminal device reports the slice-related information it has acquired to the network device, thereby helping the network device to reasonably configure the configuration information related to the slice. Attached Figure Description

[0018] Figure 1 This is a schematic diagram illustrating an application scenario of an embodiment of this application;

[0019] Figure 2 This is a flowchart illustrating the slice information reporting method provided in an embodiment of this application;

[0020] Figure 3 This is a schematic diagram of the structural composition of the slice information reporting device provided in the embodiments of this application. Figure 1 ;

[0021] Figure 4 This is a schematic diagram of the structural composition of the slice information reporting device provided in the embodiments of this application. Figure 2 ;

[0022] Figure 5 This is a schematic structural diagram of a communication device provided in an embodiment of this application;

[0023] Figure 6 This is a schematic structural diagram of the chip according to an embodiment of this application. Detailed Implementation

[0024] The technical solutions of the embodiments of this application will now be described with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0025] Figure 1 This is a schematic diagram of an application scenario according to an embodiment of this application.

[0026] like Figure 1 As shown, the communication system 100 may include a terminal device 110 and a network device 120. The network device 120 can communicate with the terminal device 110 via an air interface. Multi-service transmission is supported between the terminal device 110 and the network device 120.

[0027] It should be understood that the embodiments of this application are only illustrated by way of example with communication system 100, but the embodiments of this application are not limited thereto. That is to say, the technical solutions of the embodiments of this application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Internet of Things (IoT) system, Narrow Band Internet of Things (NB-IoT) system, enhanced Machine-Type Communications (eMTC) system, 5G communication system (also known as New Radio (NR) communication system), or future communication systems, etc.

[0028] exist Figure 1 In the communication system 100 shown, network device 120 may be an access network device that communicates with terminal device 110. The access network device can provide communication coverage for a specific geographical area and can communicate with terminal device 110 (e.g., UE) located within that coverage area.

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

[0030] Terminal device 110 can be any terminal device, including but not limited to terminal devices that are connected to network device 120 or other terminal devices via wired or wireless connections.

[0031] For example, the terminal device 110 may refer to an access terminal, user equipment (UE), user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device. The access terminal may be a cellular phone, cordless phone, Session Initiation Protocol (SIP) phone, IoT device, satellite handheld terminal, Wireless Local Loop (WLL) station, Personal Digital Assistant (PDA), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, in-vehicle device, wearable device, terminal device in a 5G network, or terminal device in a future evolved network, etc.

[0032] Terminal device 110 can be used for device-to-device (D2D) communication.

[0033] The wireless communication system 100 may further include a core network device 130 that communicates with the base station. This core network device 130 may be a 5G core network (5G Core, 5GC) device, such as an Access and Mobility Management Function (AMF), an Authentication Server Function (AUSF), a User Plane Function (UPF), or a Session Management Function (SMF). Optionally, the core network device 130 may also be an Evolved Packet Core (EPC) device for an LTE network, such as a Session Management Function + Core Packet Gateway (SMF+PGW-C) device. It should be understood that SMF+PGW-C can simultaneously implement the functions of both SMF and PGW-C. During network evolution, the aforementioned core network device may also be called by other names, or new network entities may be formed by dividing the core network functions; this embodiment does not limit this.

[0034] The various functional units in the communication system 100 can also establish connections and communicate with each other through the next generation (NG) interface.

[0035] For example, terminal devices establish air interface connections with access network devices through the NR interface for transmitting user plane data and control plane signaling; terminal devices can establish control plane signaling connections with the AMF through NG interface 1 (N1); access network devices, such as next-generation radio access base stations (gNB), can establish user plane data connections with the UPF through NG interface 3 (N3); access network devices can establish control plane signaling connections with the AMF through NG interface 2 (N2); the UPF can establish control plane signaling connections with the SMF through NG interface 4 (N4); the UPF can interact with the data network for user plane data through NG interface 6 (N6); the AMF can establish control plane signaling connections with the SMF through NG interface 11 (N11); and the SMF can establish control plane signaling connections with the PCF through NG interface 7 (N7).

[0036] Figure 1An exemplary embodiment shows a base station, a core network device, and two terminal devices. Optionally, the wireless communication system 100 may include multiple base station devices, and the coverage area of ​​each base station may include other numbers of terminal devices. This application embodiment does not limit this.

[0037] It should be noted that, Figure 1 This application merely illustrates the system to which this application applies; of course, the methods shown in the embodiments of this application can also be applied to other systems. Furthermore, the terms "system" and "network" are often used interchangeably herein. The term "and / or" in this application merely describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this application generally indicates that the preceding and following related objects have an "or" relationship. It should also be understood that "instruction" mentioned in the embodiments of this application can be a direct instruction, an indirect instruction, or an indication of a related relationship. For example, A instructing B can mean that A directly instructs B, for example, B can be obtained through A; it can also mean that A indirectly instructs B, for example, A instructs C, B can be obtained through C; or it can mean that there is a related relationship between A and B. It should also be understood that "correspondence" mentioned in the embodiments of this application can indicate a direct or indirect correspondence between two things, or an related relationship between two things, or a relationship of instruction and being instructed, configuration and being configured, etc. It should also be understood that the "predefined" or "predefined rules" mentioned in the embodiments of this application can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices), and this application does not limit the specific implementation method. For example, predefined can refer to those defined in a protocol. It should also be understood that in the embodiments of this application, the "protocol" can refer to standard protocols in the field of communication, such as the LTE protocol, the NR protocol, and related protocols applied to future communication systems, and this application does not limit this.

[0038] To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies of the embodiments of this application are described below. The following relevant technologies are optional solutions and can be combined with the technical solutions of the embodiments of this application in any way, and they all fall within the protection scope of the embodiments of this application.

[0039] Network slicing (or simply slicing) is an on-demand networking method that allows operators to create multiple virtual end-to-end networks on a unified infrastructure. Different types of services can use different slices; for example, mobile broadband, connected vehicle, and Internet of Things (IoT) services can each use their own dedicated slices. Currently, operators support slicing on the network side by associating slices with frequency bands, meaning different frequency bands can support different slices.

[0040] To help terminal devices find cells that match their needs more quickly, base stations can broadcast information about slices or slice groups supported by the serving cell and / or neighboring cells, as well as the frequency priority information corresponding to each slice or slice group. For example, the information about a slice or slice group can be its identifier (ID) or index. A slice group includes one or more slices. The concept of slice groups was introduced to mitigate the risk of air interface slice privacy exposure and also to save the overhead of broadcast messages.

[0041] Furthermore, to help terminal devices quickly access high-priority slice services such as low-latency slices, the random access resources of slices or slice groups can be isolated by allocating dedicated preambles or random access opportunity resources. Here, random access opportunity resources refer to random access channel opportunities (RACH Occasion, RO). Alternatively, differentiated priority access for slices or slice groups can be achieved by configuring random access priority parameters (such as power boost parameters, shortened backoff parameters) or configuring two-step random access resources, ensuring faster and higher priority access for low-latency slices.

[0042] The slicing grouping mechanism is implemented on the network side. For example, one possible approach is for the network to group slices with similar Quality of Service (QoS) requirements together. This facilitates the allocation of dedicated preambles, random access opportunities, random access priorities, or two-step random access resources to this group of slices. However, if too many terminal devices in an area (such as one or more cells) request the same slice or slice group, it can lead to an over-concentration of terminal devices on the corresponding frequency, potentially causing congestion in the corresponding cell. In this case, the network should adjust the slice group configuration or the frequency priority corresponding to the slice or slice group to distribute the terminal devices to different frequencies or cells, reducing potential network congestion. Moreover, since terminal devices may support multiple slices, and the slices they actually want to use may differ at different times, if reselection is performed based on the frequency priority of the slice or slice group broadcast by the network, the cell where the terminal device is camped when initiating the slice service may not support that slice service. Slice switching may then be required after the terminal device enters connected state so that it can perform the desired slice service normally.

[0043] On the other hand, if the 2-step or 4-step random access resources or priorities corresponding to a slice or slice group are not configured reasonably, such as a large number of terminal devices being configured with the same random access resources or priorities, it may lead to random access congestion or failure of terminal devices; or conversely, if the same random access resources or priorities are configured for a small number of terminal devices, it will result in a waste of cell resources on the base station side.

[0044] In the early stages of network deployment, operators lack information about the slices that the terminal devices they host support or that initiate services. Therefore, they cannot accurately deploy slices or slice groups, nor can they allocate random access resources appropriately. If a large number of terminal devices record the slice-related information they acquire and report it to the network side, it can help the network side configure appropriate slice support capabilities.

[0045] Based on this, the following technical solutions are proposed in the embodiments of this application. In the technical solutions of the embodiments of this application, the terminal device records slice-related information and reports it to the network device, thereby helping the network device to optimize slice-related configurations.

[0046] To facilitate understanding of the technical solutions of the embodiments of this application, the technical solutions of this application are described in detail below through specific embodiments. The above-mentioned related technologies are optional solutions and can be arbitrarily combined with the technical solutions of the embodiments of this application, all of which fall within the protection scope of the embodiments of this application. The embodiments of this application include at least some of the following contents.

[0047] Figure 2 This is a flowchart illustrating the slice information reporting method provided in this application embodiment, as shown below. Figure 2 As shown, the slice information reporting method includes the following steps:

[0048] 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 the reselection process and information related to the random access process.

[0049] In this embodiment, the terminal device reports slice-related information to the network device, and the network device receives the slice-related information reported by the terminal device.

[0050] In some alternative implementations, the network device is a network management system, a trace collection entity (TCE), or a base station.

[0051] In this embodiment of the application, the slice-related information includes at least one of the following: information related to the reselection process and information related to the random access process. The information related to the reselection process and the information related to the random access process will be described in detail below.

[0052] Information related to the reselection process

[0053] In some alternative implementations, the information related to the reselection process includes at least one of the following:

[0054] The relevant identification information of the slice or slice group used for reselection;

[0055] Frequency information corresponding to the slice or slice group used for reselection;

[0056] Priority information for the frequency corresponding to the slice or slice group used for reselection.

[0057] Here, the slice or slice group used for reselection is the highest priority slice or slice group determined by the terminal device itself, or the slice or slice group selected based on the terminal implementation; or, the slice or slice group used for reselection is a slice or slice group determined by the terminal device based on configuration information, priority information, allowed slice information, 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, priority information, allowed slice information, available slice information, or supported slice information sent by the network device) is carried in a broadcast message, a Radio Resource Control (RRC) release message, or a Non-Access Stratum (NAS) message.

[0058] It should be noted that the slice or slice group used for reselection can be the slice or slice group that the terminal device hopes, plans, requests, or prioritizes to perform during or before reselection, or it can be the slice or slice group determined based on the network side's configuration information, priority messages, allowed slice information, available slice information, or supported slice information.

[0059] In the above scheme, as an example, the relevant identification information of a slice or slice group can be the identifier (ID) corresponding to the slice or slice group, or it can be the index (Index) corresponding to the slice or slice group.

[0060] In the above scheme, as an example, the frequency information corresponding to a slice or slice group can be, for example, f1, f2, and f3. This explanation uses three frequency information points as an example; however, more or fewer frequency information points are also applicable to the technical solution of this application.

[0061] In the above scheme, as an example, the priority information of the frequency corresponding to the slice or slice group is as follows: 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.

[0062] Furthermore, in some optional embodiments, the information related to the reselection process also includes: the frequency point and / or target frequency point where the terminal device camps when the reselection occurs. It should be noted that the reselection can be intra-frequency reselection or inter-frequency reselection. For inter-frequency reselection, relevant parameters include, for example, Thresh. X,HighP Thresh X,HighQ Thresh X,LowP Thresh X,LowQ Thresh Serving,LowP Thresh Serving,LowQ .

[0063] In some alternative implementations, the priority information described above is carried in a broadcast message, an RRC message, or a NAS message.

[0064] Information related to the random access procedure

[0065] In some alternative implementations, the information related to the random access procedure includes at least one of the following:

[0066] Identification information of the slice or slice group related to random access;

[0067] Information about the random access resources used for random access;

[0068] Information on the Reference Signal Receiving Power (RSRP) measured by the terminal equipment;

[0069] Information about the size of data packets measured by the terminal device;

[0070] The buffer information of the logical channel measured by the terminal device.

[0071] It should be noted that the slice or slice group related to random access can be the slice or slice group that the terminal device hopes, plans, requests, or prioritizes to perform when initiating the random access procedure or before initiating random access, or it can be the slice or slice group determined based on the network side's configuration information, priority messages, allowed slice information, available slices, or supported slice information.

[0072] In some alternative implementations, the identification information of the slice or slice group may be, for example, the ID corresponding to the slice or slice group, or the index corresponding to the slice or slice group.

[0073] In some alternative implementations, the information on the random access resources used by the random access includes at least one of the following:

[0074] The first information is used to indicate whether the type of random access is 2-step random access or 4-step random access.

[0075] The second information is used to indicate whether the type of random access is a 2-step random access for small packet transmission or a 4-step random access for small packet transmission.

[0076] The third information is used to indicate a dedicated preamble and / or random access opportunity resource; here, the random access opportunity resource may be a RO resource.

[0077] The fourth information is used to indicate the priority information of random access.

[0078] In the above scheme, the priority information of the random access includes at least one of the following: the parameter corresponding to power ramping (powerRampingStepHighPriority) and the parameter corresponding to scaling factor (scalingFactorBI).

[0079] In the above scheme, optionally, when the random access type is two-step random access or two-step random access for small packet transmission, the information related to the random access process includes the RSRP information measured by the terminal device.

[0080] Optionally, the RSRP information may be measured before the terminal device initiates random access.

[0081] Here, the RSRP information measured by the terminal device can be, for example, the RSRP value, or the relationship between the RSRP value and the threshold value configured on the network side (such as the difference or multiple).

[0082] In the above scheme, optionally, when the random access type is a 2-step random access for small packet transmission or a 4-step random access for small packet transmission, the information related to the random access process includes the data volume information measured by the terminal device and / or the buffer information of each logical channel measured by the terminal device.

[0083] Optionally, the packet size information and / or logical channel buffer information may be measured by the terminal device before initiating random access.

[0084] In this embodiment, the terminal device reports slice-related information to the network device based on first configuration information, wherein the first configuration information is used to configure the 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.

[0085] Here, the slice-related information recorded and / or reported by the terminal device may be configured to the terminal device by the network device (such as a network management system, TCE, or base station), or it may be specified by a protocol. Taking the network device configuration method as an example, the network device sends first configuration information to the terminal device, and the first configuration information is used to configure the content of the slice-related information reported by the terminal device.

[0086] In some alternative implementations, the terminal device reports slice-related information to the network device while in a connected state, during the transition to a connected state, in an idle state, or in an inactive state.

[0087] In some alternative implementations, the terminal device reports the slice-related information to the network device via a defined message or random access report.

[0088] In this embodiment of the application, the terminal device may report slice-related information to the network device in the following manner:

[0089] Method 1: The network device sends a first request message to the terminal device; after receiving the first request message from the network device, the terminal device reports slice-related information to the network device; the network device receives the slice-related information reported by the terminal device; wherein, the first request message is used to request the terminal device to report slice-related information.

[0090] This method reports slice-related information based on network device requests.

[0091] Method 2: The terminal device actively reports slice-related information to the network device; the network device receives the slice-related information actively reported by the terminal device.

[0092] This method involves the terminal device proactively reporting slice-related information.

[0093] Method 3: The terminal device sends a first notification message to the network device, and the network device receives the first notification message sent by the terminal device; the network device sends a first request message to the terminal device, and after receiving the first request message sent by the network device, the terminal device reports slice-related information to the network device; the network device receives the slice-related information reported by the terminal device; wherein, the first notification message is used to notify the network device that the terminal device has stored slice-related information; the first request message is used to request the terminal device to report slice-related information.

[0094] This method involves the terminal device informing the network device that it has stored slice-related information, and then reporting the slice-related information upon request from the network device.

[0095] Furthermore, the technical solution of this application embodiment may also include the following: the network device configures a slice configuration based on the slice-related information and sends the slice configuration to the terminal device; the terminal device receives the slice configuration sent by the network device, wherein the slice configuration is determined based on the slice-related information.

[0096] As an optimization scheme, if the network device determines, based on the slice-related information, that the service requests initiated for a specific slice exceed a first threshold and / or the service requests initiated for a specific slice group exceed a second threshold, then the network device performs the following configuration: reduces the number of the specific slices in the slice group.

[0097] As an optimization scheme, if the network device determines, based on the slice-related information, that the service requests initiated for a specific frequency exceed a third threshold, the network device performs the following configuration: based on the slices or slice groups supported by the specific frequency point and the priority information of the specific frequency point, adjusts the priority of the frequency point corresponding to the slice or slice group; adjusts the reselection parameters corresponding to the specific frequency point.

[0098] As an optimization scheme, if the network device determines, based on the slice-related information, that the number of users initiating random access for a specific slice or slice group exceeds a fourth threshold, then the network device performs at least one of the following configurations: increases the number of random access resources corresponding to the specific slice or slice group; adjusts the priority parameters of the random access corresponding to the specific slice or slice group; or adjusts the RSRP threshold corresponding to the specific slice or slice group.

[0099] As an example: if too many service requests are initiated for a certain slice or slice group, the network device will consider optimizing the slice group and reducing the number of popular slices in the same slice group, thereby reducing the number of corresponding requesting terminal devices.

[0100] As an example: If the number of terminal devices requesting a slice on a certain frequency is too large, the network device can readjust the priority of the corresponding frequency points of the slice or slice group by combining the slice and priority information supported by the frequency point. For example, if the highest frequency corresponding to slice or slice group 1 and slice group 2 is f1, the highest frequency of slice or slice group 2 can be adjusted to another frequency f2 to reduce the number of users at f1; the reselection parameters can also be adjusted, such as increasing ThreshX, HighP, ThreshX, and HighQ, so that terminal devices are less likely to reselect to a higher priority frequency point.

[0101] As an example: if too many random access users are requested for a certain slice or slice group, the network device can increase the corresponding random access resources, including preamble and / or RO resources.

[0102] As an example: if too many terminal devices request a high-priority slice or slice group, the network device adjusts the corresponding random access priority parameters, such as reducing the parameter corresponding to power ramping (powerRampingStepHighPriority) and / or shortening the parameter corresponding to scaling factor (scalingFactorBI).

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

[0104] In the technical solution of this application embodiment, the terminal device records the slice-related information it has obtained and reports it to the network device, which can help the network device configure reasonable slice-related configurations, such as configuring reasonable slice groups, frequency priorities and random access parameters.

[0105] Figure 3 This is a schematic diagram of the structural composition of the slice information reporting device provided in the embodiments of this application. Figure 1 Applied to terminal devices, such as Figure 3 As shown, the slice information reporting device includes:

[0106] The sending unit 301 is used to report slice-related information to the network device, wherein the slice-related information includes at least one of the following: information related to the reselection process and information related to the random access process.

[0107] In some alternative implementations, the information related to the reselection process includes at least one of the following:

[0108] The relevant identification information of the slice or slice group used for reselection;

[0109] Frequency information corresponding to the slice or slice group used for reselection;

[0110] Priority information for the frequency corresponding to the slice or slice group used for reselection.

[0111] In some alternative implementations, the slice or slice group used for reselection is the highest priority slice or slice group determined by the terminal device itself, or the slice or slice group selected based on the terminal implementation; or, the slice or slice group used for reselection is a slice or slice group determined by the terminal device based on the configuration information or priority information or allowed slice information or available slice information or supported slice information sent by the network device.

[0112] In some alternative implementations, the configuration information, priority information, allowed slice information, available slice information, or supported slice information sent by the network device are carried in a broadcast message, an RRC message, or a NAS message.

[0113] In some alternative implementations, the information related to the random access procedure includes at least one of the following:

[0114] Identification information of the slice or slice group related to random access;

[0115] Information about the random access resources used for random access;

[0116] Information on the Reference Signal Received Power (RSRP) measured by the terminal equipment;

[0117] Information about the size of data packets measured by the terminal device;

[0118] The buffer information of the logical channel measured by the terminal device.

[0119] In some alternative implementations, the information on the random access resources used by the random access includes at least one of the following:

[0120] The first information is used to indicate whether the type of random access is 2-step random access or 4-step random access.

[0121] The second information is used to indicate whether the type of random access is a 2-step random access for small packet transmission or a 4-step random access for small packet transmission.

[0122] The third information is used to indicate dedicated preamble and / or random access opportunity resources;

[0123] The fourth information is used to indicate the priority information of random access.

[0124] In some alternative implementations, when the type of random access is two-step random access or two-step random access for small packet transmission, the information related to the random access process includes the RSRP information measured by the terminal device.

[0125] In some alternative implementations, when the type of random access is a 2-step random access for small packet transmission or a 4-step random access for small packet transmission, the information related to the random access process includes the size information of the data packets measured by the terminal device and / or the buffer information of the logical channel measured by the terminal device.

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

[0127] In some alternative implementations, the first configuration information is configured by the network device or defined by the protocol.

[0128] In some optional implementations, the sending unit 301 is configured to report slice-related information to the network device in a connected state, during the transition to a connected state, in an idle state, or in an inactive state.

[0129] In some alternative implementations, the sending unit 301 is configured to report the slice-related information to the network device via a defined message or random access report.

[0130] In some alternative embodiments, the apparatus further includes a receiving unit 302;

[0131] 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; wherein, the first request message is used to request the terminal device to report slice-related information; or...

[0132] The sending unit 301 actively reports slice-related information to the network device; or...

[0133] The sending unit 301 sends a first notification message to the network device, and the receiving unit 302 receives a first request message sent by the network device. The sending unit 301 reports slice-related information to the network device. The first notification message is used to notify the network device that the terminal device has stored slice-related information. The first request message is used to request the terminal device to report slice-related information.

[0134] In some alternative implementations, the receiving unit 302 is used to receive a slice configuration sent by the network device, wherein the slice configuration is determined based on the slice-related information.

[0135] Those skilled in the art should understand that Figure 3 The functions of each unit in the slice information reporting device shown can be understood by referring to the relevant descriptions of the aforementioned method. Figure 3 The functions of each unit in the slice information reporting device shown can be implemented by a program running on a processor or by specific logic circuits.

[0136] Figure 4This is a schematic diagram of the structural composition of the slice information reporting device provided in the embodiments of this application. Figure 2 Applied to network devices, such as Figure 4 As shown, the slice information reporting device includes:

[0137] The receiving unit 401 is used to receive slice-related information reported by the terminal device, wherein the slice-related information includes at least one of the following: information related to the reselection process and information related to the random access process.

[0138] In some alternative implementations, the information related to the reselection process includes at least one of the following:

[0139] The relevant identification information of the slice or slice group used for reselection;

[0140] Frequency information corresponding to the slice or slice group used for reselection;

[0141] Priority information for the frequency corresponding to the slice or slice group used for reselection.

[0142] In some alternative implementations, the slice or slice group used for reselection is the highest priority slice or slice group determined by the terminal device itself, or the slice or slice group selected based on the terminal implementation; or, the slice or slice group used for reselection is a slice or slice group determined by the terminal device based on the configuration information or priority information or allowed slice information or available slice information or supported slice information sent by the network device.

[0143] In some alternative implementations, the configuration information, priority information, allowed slice information, available slice information, or supported slice information sent by the network device are carried in a broadcast message, an RRC message, or a NAS message.

[0144] In some alternative implementations, the information corresponding to the random access procedure includes at least one of the following:

[0145] Identification information of the slice or slice group related to random access;

[0146] Information about the random access resources used for random access;

[0147] RSRP information measured by the terminal device;

[0148] Information about the size of data packets measured by the terminal device;

[0149] The buffer information of the logical channel measured by the terminal device.

[0150] In some alternative implementations, the information on the random access resources used by the random access includes at least one of the following:

[0151] The first information is used to indicate whether the type of random access is 2-step random access or 4-step random access.

[0152] The second information is used to indicate whether the type of random access is a 2-step random access for small packet transmission or a 4-step random access for small packet transmission.

[0153] The third information is used to indicate dedicated preamble and / or random access opportunity resources;

[0154] The fourth information is used to indicate the priority information of random access.

[0155] In some alternative implementations, when the type of random access is two-step random access or two-step random access for small packet transmission, the information related to the random access process includes the RSRP information measured by the terminal device.

[0156] In some alternative implementations, when the type of random access is a 2-step random access for small packet transmission or a 4-step random access for small packet transmission, the information related to the random access process includes the size information of the data packets measured by the terminal device and / or the buffer information of the logical channel measured by the terminal device.

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

[0158] In some alternative embodiments, the apparatus further includes: a transmitting unit 402;

[0159] The sending unit 402 sends a first request message to the terminal device, and the receiving unit 401 receives the slice-related information reported by the terminal device; wherein, the first request message is used to request the terminal device to report slice-related information; or...

[0160] The receiving unit 401 receives slice-related information actively reported by the terminal device; or...

[0161] The receiving unit 401 receives a first notification message sent by the 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; wherein, the first notification message is used to notify the network device that the terminal device has stored slice-related information; the first request message is used to request the terminal device to report slice-related information.

[0162] In some alternative embodiments, the apparatus further includes: a configuration unit 403, configured to configure a slice configuration based on the slice-related information, and the sending unit 402 sending the slice configuration to the terminal device.

[0163] In some optional implementations, the configuration unit 403 is configured to perform the following configuration if, based on the slice-related information, it is determined that a service request initiated for a specific slice exceeds a first threshold and / or a service request initiated for a specific slice group exceeds a second threshold:

[0164] Reduce the number of the specific slices in the slice group.

[0165] In some alternative implementations, the configuration unit 403 is configured to perform the following configuration if it is determined, based on the slice-related information, that service requests initiated for a specific frequency exceed a third threshold:

[0166] Based on the slices or slice groups supported by the specific frequency point and the priority information of the specific frequency point, adjust the priority of the frequency points corresponding to the slices or slice groups.

[0167] Adjust the reselection parameters corresponding to the specific frequency point.

[0168] In some alternative implementations, the configuration unit 403 is configured to perform at least one of the following configurations if, based on the slice-related information, the number of users initiating random access to a specific slice or slice group exceeds a fourth threshold:

[0169] Increase the number of random access resources corresponding to the specific slice or slice group;

[0170] Adjust the priority parameters of random access corresponding to the specific slice or slice group;

[0171] Adjust the RSRP threshold corresponding to the specific slice or slice group.

[0172] Those skilled in the art should understand that Figure 4 The functions of each unit in the slice information reporting device shown can be understood by referring to the relevant descriptions of the aforementioned method. Figure 4 The functions of each unit in the slice information reporting device shown can be implemented by a program running on a processor or by specific logic circuits.

[0173] Figure 5 This is a schematic structural diagram of a communication device 500 provided in an embodiment of this application. The communication device can be a terminal device or a network device. Figure 5The communication device 500 shown includes a processor 510, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0174] Optionally, such as Figure 5 As shown, the communication device 500 may further include a memory 520. The processor 510 can retrieve and run computer programs from the memory 520 to implement the methods described in this embodiment.

[0175] The memory 520 can be a separate device independent of the processor 510, or it can be integrated into the processor 510.

[0176] Optionally, such as Figure 5 As shown, the communication device 500 may also include a transceiver 530, and the processor 510 may control the transceiver 530 to communicate with other devices. Specifically, it may send information or data to other devices or receive information or data sent by other devices.

[0177] The transceiver 530 may include a transmitter and a receiver. The transceiver 530 may further include antennas, and the number of antennas may be one or more.

[0178] Optionally, the communication device 500 may specifically be a network device in the embodiments of this application, and the communication device 500 may implement the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0179] Optionally, the communication device 500 may specifically be a mobile terminal / terminal device in the embodiments of this application, and the communication device 500 may implement the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0180] Figure 6 This is a schematic structural diagram of the chip according to an embodiment of this application. Figure 6 The chip 600 shown includes a processor 610, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0181] Optionally, such as Figure 6 As shown, chip 600 may further include memory 620. Processor 610 can retrieve and run computer programs from memory 620 to implement the methods described in this embodiment.

[0182] The memory 620 can be a separate device independent of the processor 610, or it can be integrated into the processor 610.

[0183] Optionally, the chip 600 may also include an input interface 630. The processor 610 can control the input interface 630 to communicate with other devices or chips; specifically, it can acquire information or data sent by other devices or chips.

[0184] Optionally, the chip 600 may also include an output interface 640. The processor 610 can control the output interface 640 to communicate with other devices or chips, specifically, to output information or data to other devices or chips.

[0185] Optionally, the chip can be applied to the network device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0186] Optionally, the chip can be applied to the mobile terminal / terminal device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

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

[0188] It should be understood that the processor in the embodiments of this application may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor described above can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0189] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0190] It should be understood that the above-described memory is exemplary and not a limiting description. For example, the memory in the embodiments of this application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DR RAM), etc. That is to say, the memory in the embodiments of this application is intended to include, but is not limited to, these and any other suitable types of memory.

[0191] This application also provides a computer-readable storage medium for storing computer programs.

[0192] Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0193] Optionally, the computer-readable storage medium can be applied to the mobile terminal / terminal device in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0194] This application also provides a computer program product, including computer program instructions.

[0195] Optionally, the computer program product can be applied to the network device in the embodiments of this application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, they will not be described in detail here.

[0196] Optionally, the computer program product can be applied to the mobile terminal / terminal device in the embodiments of this application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of this application. For the sake of brevity, they will not be described in detail here.

[0197] This application also provides a computer program.

[0198] Optionally, the computer program can be applied to the network device in the embodiments of this application. When the computer program is run on a computer, it causes the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0199] Optionally, the computer program can be applied to the mobile terminal / terminal device in the embodiments of this application. When the computer program is run on a computer, it causes the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0200] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0201] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0202] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0203] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0204] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0205] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0206] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for reporting slice information, characterized in that, The method comprises: The terminal device reports slice-related information to the network device, wherein the slice-related information comprises: information related to a random access procedure; or the slice-related information comprises: information related to a reselection procedure and information related to a random access procedure; wherein The information related to the random access procedure comprises: identification information of a slice group related to random access and information of random access resources used by the random access; and the information of random access resources used by the random access comprises: third information used for indicating a dedicated preamble and / or random access opportunity resources.

2. The method of claim 1, wherein, The information related to the reselection procedure comprises at least one of: related identification information of a slice or a slice group used by reselection; frequency information corresponding to a slice or a slice group used by reselection; priority information of a frequency corresponding to a slice or a slice group used by reselection.

3. The method of claim 2, wherein The slice or slice group used by reselection is a slice or slice group with the highest priority determined by the terminal device itself, or a slice or slice group selected based on terminal implementation; or The slice or slice group used by reselection is a slice or slice 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 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 a radio resource control (RRC) message or a non-access stratum (NAS) message.

5. The method of claim 1, wherein, The information related to the random access procedure further comprises at least one of: information of a reference signal received power (RSRP) measured by the terminal device; size information of a data packet measured by the terminal device; buffer information of a logical channel measured by the terminal device.

6. The method of claim 1, wherein, The information of random access resources used by the random access further comprises at least one of: first information used for indicating whether the type of random access is two-step random access or four-step random access; second information used for indicating whether the type of random access is two-step random access for small packet transmission or four-step random access for small packet transmission; fourth information used for indicating priority information of random access.

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

8. The method of claim 5, wherein, In the case where the type of random access is two-step random access for small packet transmission or four-step random access for small packet transmission, the information related to the random access procedure comprises the size information of the data packet measured by the terminal device and / or the buffer information of the logical channel measured by the terminal device.

9. The method according to any one of claims 1 to 8, characterized in that, The terminal device reports slice-related information to the network device, comprising: The terminal device reports slice-related information to the network device based on first configuration information, wherein the first configuration information is used to configure 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 for the network device or defined by a protocol.

11. The method according to any one of claims 1 to 8, characterized in that, The terminal device reports slice-related information to the network device, including: The terminal device reports slice-related information to the network device in a connected state or in the process of changing to a connected state or in an idle state or in an inactive state.

12. The method according to any one of claims 1 to 8, characterized in that, The terminal device reports slice-related information to the network device, including: The terminal device reports the slice-related information to the network device through a defined message or random access reporting.

13. The method according to any one of claims 1 to 8, characterized in that, The terminal device reports slice-related information to the network device, including: After receiving a first request message sent by the network device, the terminal device reports slice-related information to the network device; wherein the first request message is used to request the terminal device to report slice-related information; or, The terminal device actively reports slice-related information to the network device; or, The terminal device sends a first notification message to the network device, and after receiving a first request message sent by the network device, the terminal device reports slice-related information to the network device; wherein the first notification message is used to notify the network device that the terminal device has stored slice-related information; and the first request message is used to request the terminal device to report slice-related information.

14. The method according to any one of claims 1 to 8, characterized in that, The method further comprises: The terminal device receives slice configuration sent by the network device, wherein the slice configuration is determined based on the slice-related information.

15. A method for reporting slice information, the method comprising: The method comprises: The network device receives slice-related information reported by the terminal device, wherein the slice-related information includes: information related to a random access process; or the slice-related information includes: information related to a reselection process and information related to a random access process; wherein, The information related to the random access process includes: identification information of a slice group related to the random access and information of random access resources used by the random access; and the information of random access resources used by the random access includes: third information used to indicate dedicated preambles and / or random access opportunity resources.

16. The method of claim 15, wherein, The information related to the reselection process includes at least one of: Related identification information of a slice or a slice group used for reselection; Frequency information corresponding to a slice or a slice group used for reselection; Priority information of a frequency corresponding to a slice or a slice group used for reselection.

17. The method of claim 16, wherein: The slice or slice group used for reselection is a slice or slice group with the highest priority determined by the terminal device itself, or a slice or slice group selected based on terminal implementation; or The slice or slice group used for reselection is a slice or slice 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.

18. The method of claim 17, wherein, The 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 an RRC message or a NAS message.

19. The method of claim 15, wherein, The information corresponding to the random access process further includes at least one of: information of RSRP measured by the terminal device; information of packet size measured by the terminal device; information of buffer of logical channel measured by the terminal device.

20. The method of claim 19, wherein, The information of random access resource used by the random access further includes at least one of: first information, the first information is used to indicate whether the type of random access is 2-step random access or 4-step random access; second information, the second information is used to indicate whether the type of random access is 2-step random access for small packet transmission or 4-step random access for small packet transmission; fourth information, the fourth information is used to indicate priority information of random access.

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

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

23. The method of any one of claims 15-22, wherein, The method further includes: The network device sends first configuration information to the terminal device, wherein the first configuration information is used to configure the content of slice-related information reported by the terminal device.

24. The method of any one of claims 15-22, wherein, The network device receives the slice-related information reported by the terminal device, including: The network device sends a first request message to the terminal device and receives the slice-related information reported by the terminal device; wherein the first request message is used to request the terminal device to report the slice-related information; or, The network device receives the slice-related information reported by the terminal device; or, The network device receives a first notification message sent by the terminal device, sends a first request message to the terminal device, and receives the slice-related information reported by the terminal device; wherein the first notification message is used to notify the network device that the terminal device has stored slice-related information; and the first request message is used to request the terminal device to report the slice-related information.

25. The method of any one of claims 15-22, wherein, The method further includes: The network device configures a slice configuration based on the slice-related information and sends the slice configuration to the terminal device.

26. The method of claim 25, wherein, The network device configures a slice configuration based on the slice-related information, including: If the network device determines 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 based on the slice-related information, the network device performs the following configuration: Reduce the number of the specific slice in the slice group.

27. The method of claim 25, wherein, The network device configures a slice configuration based on the slice-related information, including: If the network device determines that the service request initiated for a specific frequency exceeds a third threshold based on the slice-related information, the network device performs the following configuration: Adjust the priority of the frequency corresponding to the slice or slice group based on the slice or slice group supported by the specific frequency and the priority information of the specific frequency; Adjust the reselection parameter corresponding to the specific frequency.

28. The method of claim 25, wherein, The network device configures a slice configuration based on the slice-related information, including: If the network device determines, based on the slice-related information, that the number of users initiating random access for a specific slice or 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; adjusting the RSRP threshold corresponding to the specific slice or slice group.

29. A slice information reporting apparatus, characterized by comprising: Applied to a terminal device, the apparatus includes: a sending unit configured to report slice-related information to a network device, wherein the slice-related information includes: information related to a reselection process; or the slice-related information includes: information related to a reselection process and information related to a random access process; wherein the information related to the random access process includes: identification information of a slice group related to random access and information of random access resources used for random access; and the information of random access resources used for random access includes: third information used to indicate dedicated preambles and / or random access opportunity resources.

30. A slice information reporting apparatus, characterized by comprising: Applied to a network device, the apparatus includes: a receiving unit configured to receive slice-related information reported by a terminal device, wherein the slice-related information includes: information related to a random access process; or the slice-related information includes: information related to a reselection process and information related to a random access process; wherein the information related to the random access process includes: identification information of a slice group related to random access and information of random access resources used for random access; and the information of random access resources used for random access includes: third information used to indicate dedicated preambles and / or random access opportunity resources.

31. A terminal device, comprising: including: a processor and a memory, the memory being configured to store a computer program, and the processor being configured to invoke and run the computer program stored in the memory to perform the method of any one of claims 1 to 14.

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

33. A chip, characterized by including: a processor configured to invoke and run a computer program from a memory, so that a device in which the chip is installed performs the method of any one of claims 1 to 14, or the method of any one of claims 15 to 28.

34. A computer-readable storage medium, characterized in that, a computer program for storing, the computer program 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.

Images