Wireless communication method, terminal device and network device

Abstract

The embodiment of the present application provides a wireless communication method, a terminal device, and a network device, the method comprising: the terminal device sends first slice related information to the network device; wherein the first slice related information is carried in a random access process; the first slice related information is used to indicate whether the terminal device supports network slicing, and / or the network slices supported by the terminal device. Thus, the service delay of the terminal device can be reduced.

Description

Technical Field

[0001] Embodiments of the present application relate to the field of communications, and more specifically, to wireless communication methods, terminal devices, and network devices. Background Art

[0002] Network slicing is composed of a Radio Access Network (RAN) part and a Core Network (CN) part. For RAN network slicing, after the network device receives Message (Msg) 5, the network device can obtain the network slice information required by the terminal device. However, the network slice required by the terminal device may not be the network slice supported by the network device, or although it is the network slice supported by the network device, this network slice is overloaded. In this case, the network device can only send a Radio Resource Control (RRC) connection release message after receiving Msg 5, causing the terminal device to reselect a suitable cell, thereby resulting in service delay of the terminal device. Summary of the Invention

[0003] Embodiments of the present application provide a wireless communication method, a terminal device, and a network device, thereby reducing the service delay of the terminal device.

[0004] In a first aspect, a wireless communication method is provided. The method includes: a terminal device sending first slice-related information to a network device; wherein, the first slice-related information is carried in a random access process; and the first slice-related information is used to indicate whether the terminal device supports network slicing and / or the network slices supported by the terminal device.

[0005] In a second aspect, a wireless communication method is provided. The method includes: a network device receiving first slice-related information sent by a terminal device; wherein, the first slice-related information is carried in a random access process; and the first slice-related information is used to indicate whether the terminal device supports network slicing and / or the network slices supported by the terminal device.

[0006] In a third aspect, a terminal device is provided for executing the method in the first aspect or its various implementation manners.

[0007] Specifically, the terminal device includes functional modules for executing the method in the first aspect or its various implementation manners.

[0008] In a fourth aspect, a network device is provided for executing the method in the second aspect or its various implementation manners.

[0009] Specifically, the network device includes a functional module for performing the method in the second aspect or its various implementation manners described above.

[0010] In a fifth aspect, a terminal device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the first aspect or its various implementation manners described above.

[0011] In a sixth aspect, a network device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the second aspect or its various implementation manners described above.

[0012] In a seventh aspect, a device is provided for implementing the method in any one of the first aspect to the second aspect or its various implementation manners.

[0013] Specifically, the device includes: a processor, configured to call and run a computer program from a memory, such that a device installed with the device executes the method in any one of the first aspect to the second aspect or its various implementation manners.

[0014] In an eighth aspect, a computer-readable storage medium is provided for storing a computer program, and the computer program causes a computer to execute the method in any one of the first aspect to the second aspect or its various implementation manners.

[0015] In a ninth aspect, a computer program product is provided, including computer program instructions, and the computer program instructions cause a computer to execute the method in any one of the first aspect to the second aspect or its various implementation manners.

[0016] In a tenth aspect, a computer program is provided, which, when running on a computer, causes the computer to execute the method in any one of the first aspect to the second aspect or its various implementation manners.

[0017] Through the technical solution of the first aspect or the second aspect, the network device can obtain the network slice required by the terminal device during the random access process, without waiting until Msg 5 is received to obtain the network slice required by the terminal device. The technical solution provided by this application can reduce the service delay of the terminal device. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 It is a schematic diagram of a communication system architecture provided by an embodiment of this application;

[0019] Figure 2Schematic flowchart of a contention-based random access procedure provided by an embodiment of the present application;

[0020] Figure 3 Interaction flowchart of a wireless communication method provided by an embodiment of the present application;

[0021] Figure 4 Schematic block diagram of a terminal device 400 according to an embodiment of the present application is shown;

[0022] Figure 5 Schematic block diagram of a network device 500 according to an embodiment of the present application is shown;

[0023] Figure 6 Schematic structural diagram of a communication device 800 provided by an embodiment of the present application;

[0024] Figure 7 Schematic structural diagram of a device provided by an embodiment of the present application;

[0025] Figure 8 Schematic block diagram of a communication system 1000 provided by an embodiment of the present application. Detailed implementation manners

[0026] Next, the technical solutions in the embodiments of the present application will be described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. For the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

[0027] Embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced long term evolution (LTE-A) system, New Radio (NR) system, evolved system of NR system, LTE-based access to unlicensed spectrum (LTE-U) system, NR-based access to unlicensed spectrum (NR-U) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), next-generation communication system or other communication systems, etc.

[0028] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technologies, mobile communication systems will not only support traditional communications, but also support, for example, Device to Device (D2D) communication, Machine to Machine (M2M) communication, Machine Type Communication (MTC), and Vehicle to Vehicle (V2V) communication, etc. Embodiments of the present application can also be applied to these communication systems.

[0029] Optionally, the communication system in the embodiments of the present application can be applied to a Carrier Aggregation (CA) scenario, can also be applied to a Dual Connectivity (DC) scenario, and can also be applied to a Standalone (SA) networking scenario.

[0030] The spectrum applied in the embodiments of this application is not limited. For example, the embodiments of this application can be applied to licensed spectrum or unlicensed spectrum.

[0031] Exemplarily, the communication system 100 applied in the embodiments of this application is as Figure 1 shown. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or referred to as a communication terminal, terminal). The network device 110 can provide communication coverage for a specific geographical area and can communicate with terminal devices located within the coverage area.

[0032] Figure 1 Exemplarily, one network device and two terminal devices are shown. Optionally, the communication system 100 may include multiple network devices and the coverage range of each network device may include other numbers of terminal devices. The embodiments of this application do not limit this.

[0033] Optionally, the communication system 100 may further include other network entities such as a network controller and a mobility management entity. The embodiments of this application do not limit this.

[0034] It should be understood that in the embodiments of this application, a device with communication functions in a network / system may be referred to as a communication device. Taking Figure 1 the shown communication system 100 as an example, the communication devices may include the network device 110 and the terminal device 120 with communication functions. The network device 110 and the terminal device 120 may be the specific devices described above and will not be elaborated here; the communication devices may also include other devices in the communication system 100, such as other network entities such as a network controller and a mobility management entity. The embodiments of this application do not limit this.

[0035] It should be understood that the terms "system" and "network" are often used interchangeably in this article. The term " / and" in this article is merely a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this article generally represents an "or" relationship between the associated objects before and after.

[0036] The embodiments of the present application describe various embodiments in combination with a terminal device and a network device, where: The terminal device may also be referred to as a User Equipment (UE), access terminal, user unit, user station, mobile station, mobile device, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device, etc. The terminal device may be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication capabilities, a computing device, or other processing devices connected to a wireless modem, a vehicle-mounted device, a wearable device, and a next-generation communication system. For example, a terminal device in an NR network or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.

[0037] By way of example and not limitation, in the embodiments of the present application, the terminal device may also be a wearable device. A wearable device may also be referred to as a wearable intelligent device, which is a general term for devices developed by applying wearable technologies to intelligentize daily wear, such as glasses, gloves, watches, clothing, and shoes, etc. A wearable device is a portable device that is either directly worn on the body or integrated into the user's clothing or accessories. A wearable device is not only a hardware device but also realizes powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable intelligent devices include those with complete functions and large sizes that can achieve complete or partial functions without relying on a smartphone, such as smart watches or smart glasses, etc., and those that only focus on a certain type of application function and need to cooperate with other devices such as smartphones, such as various smart bracelets and smart jewelry for physical sign monitoring.

[0038] The network device may be a device for communicating with a mobile device. The network device may be an Access Point (AP) in a WLAN, a Base Transceiver Station (BTS) in GSM or CDMA, a Node B (NB) in WCDMA, an Evolutional Node B (eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and a network device or base station (gNB) in an NR network or a network device in a future evolved PLMN network, etc.

[0039] In an embodiment of the present application, a network device provides services for a cell, and a terminal device communicates with the network device through transmission resources (e.g., frequency domain resources, or spectrum resources) used by the cell. The cell may be a cell corresponding to the network device (e.g., a base station). The cell may belong to a macro base station or a base station corresponding to a small cell. Here, the small cell may include: a metro cell, a micro cell, a picocell, a femto cell, etc. These small cells have the characteristics of small coverage range and low transmission power, and are suitable for providing high-rate data transmission services.

[0040] Before introducing the technical solution of the present application, the four-step random access process, the two-step random access process, and network slicing are introduced below.

[0041] It should be noted that the random access process can usually be triggered by the following events:

[0042] (1) Establishing a wireless connection during initial access. For example, when a terminal device needs to enter the RRC_CONNECTED state from the RRC_IDLE state of Radio Resource Control (RRC), the terminal device can trigger initial access at this time.

[0043] (2) The RRC Connection Re-establishment procedure is used for the terminal device to re-establish a wireless connection after a radio link failure.

[0044] (3) Handover. At this time, the terminal device is in the connected state, and the terminal device needs to establish uplink synchronization with the target cell.

[0045] (4) When downlink data or uplink data arrives in the RRC_CONNECTED state and the uplink is in the "out-of-synchronization" state (DL or UL data arrival during RRC_CONNECTED when UL synchronisation status is "non-synchronised").

[0046] (5) When uplink data arrives in the RRC connected state and there are no available Physical Uplink Control Channel (PUCCH) resources for Scheduling Request (SR) transmission (UL data arrival during RRC_CONNECTED when there are no PUCCH resources for SR available).

[0047] (6) SR failure.

[0048] (7) Request by RRC upon synchronous reconfiguration.

[0049] (8) Transition of the terminal device from the RRC inactive state.

[0050] (9) To establish time alignment at SCell addition.

[0051] (10) The terminal device requests Other System Information (OSI).

[0052] (11) The terminal device needs to perform Beam failure recovery.

[0053] (12) Resume access in the inactive state: RRC Resume Request.

[0054] In the NR system, two types of random access methods can be supported: contention-based random access and non-contention-based random access. The following briefly describes the contention-based four-step random access. As Figure 2 shown, the four-step random access includes:

[0055] Step 1, the terminal device sends a random access preamble (Preamble, i.e., Msg 1) to the network device.

[0056] Among them, the random access preamble can also be called preamble, random access preamble sequence, preamble sequence, etc.

[0057] Specifically, the terminal device can select Physical Random Access Channel (PRACH) resources, which can include time-domain resources, frequency-domain resources, and code-domain resources. The network device sends random access-related parameters to the terminal device through System Information Block (SIB) 1. Among them, the reference signal receiving power (RSRP) threshold (rsrp-ThresholdSSB) for the Synchronization Signal Block (SSB) in the Random Access Common Configuration Information Element (RACH-ConfigCommon IE) is used for the terminal device to select the SSB. The terminal device compares the RSRP measurement results under each SSB with rsrp-ThresholdSSB, and selects the SSB with a measured value higher than the configured threshold for access. If there is no SSB that meets the configured threshold, a random one is selected from all SSBs for access. Each SSB corresponds to a set of random access preamble resources and random access occasion (RO) resources. The terminal device randomly selects from the random access resources based on competition in the selected SSB and sets the Preamble index (PREAMBLE_INDEX) to the selected random access Preamble. The network device can estimate the transmission delay between it and the terminal device based on the Preamble and calibrate the uplink timing accordingly, and can generally determine the resource size required for the terminal device to transmit Msg 3. To enable the network device to more accurately understand the size of Msg 3 to be transmitted and allocate appropriate uplink resources, the Preamble is divided into Preamble group A and Preamble group B. If Preamble group B exists in the random access resources, the terminal device can select the Preamble group according to the size of Msg 3 and the pathloss.

[0058] Step 2: The network device sends a Random Access Response (RAR, i.e., Msg 2) to the terminal device.

[0059] After the terminal device sends a Preamble to the network device, it can open a random access response window (ra-ResponseWindow) and detect the corresponding Physical Downlink Control Channel (PDCCH) according to the Random Access Radio Network Temporary Identifier (RA-RNTI) within this ra-ResponseWindow. If the terminal device detects a PDCCH scrambled with the RA-RNTI, it can obtain the Physical Downlink Shared Channel (PDSCH) scheduled by this PDCCH. Among them, the RAR corresponding to the Preamble is included in this PDSCH.

[0060] The RA-RNTI is calculated based on the time-frequency position of the PRACH that sends the Preamble. Therefore, if multiple terminal devices send Preamble on the same RO, the corresponding RARs are multiplexed in the same Radio Access Control Protocol Data Unit (MAC PDU). If the terminal successfully receives a PDCCH scrambled with the RA-RNTI corresponding to the RO resource that sends the Preamble, and the RAR contains a Random Access Preamble Identifier (RAPID) carried by a MAC sub-PDU (subPDU) that corresponds to the PREAMBLE_INDEX selected in the above Msg 1, then the RAR reception is successful. The terminal can decode to obtain the Timing Advance Command (TAC), the uplink grant resource (UL Grant), and the Temporary Cell Radio Network Temporary Identity (TC-RNTI), and proceed with Msg 3.

[0061] If no PDCCH scrambled with the RA-RNTI corresponding to the RO resource for transmitting the Preamble is received during the operation of the ra-ResponseWindow, or if a PDCCH scrambled with the RA-RNTI is received but the RAR does not contain the MAC subPDU corresponding to the PREAMBLE_INDEX, the RAR reception is considered to have failed in both of the above cases. At this time, if the transmission count of the Preamble does not exceed the maximum transmission count (preambleTransMax) configured by the network, the terminal device needs to retransmit Msg 1. If the transmission count of the Preamble exceeds the maximum transmission count (preambleTransMax) configured by the network, the terminal device reports a random access problem to the upper layer.

[0062] Step 3, the terminal device transmits Msg 3.

[0063] After receiving the RAR message, the terminal device determines whether the RAR is its own RAR message. For example, the terminal device can use the preamble index for verification. After determining that it is its own RAR message, the terminal device can generate Msg 3 at the RRC layer and transmit Msg 3 to the network device, which needs to carry the identification information of the terminal device, etc.

[0064] Among them, Msg 3 is mainly used to notify the network device of the trigger event of this random access. For different random access trigger events, the Msg 3 transmitted by the terminal device in Step 3 can include different contents.

[0065] For example, for the scenario of initial access, Msg 3 can include the RRC connection request message (RRCSetup Request) generated by the RRC layer. In addition, Msg 3 can also carry, for example, the 5G-Serving Temporary Mobile Subscriber Identity (S-TMSI) or random number of the terminal device.

[0066] For another example, for the RRC connection reestablishment scenario, Msg 3 can include the RRC connection reestablishment request message (RRC Reestabilshment Request) generated by the RRC layer. In addition, Msg 3 can also carry, for example, the Cell Radio Network Temporary Identifier (C-RNTI).

[0067] For another example, for a handover scenario, Msg 3 may include an RRC handover confirmation message (RRCHandover Confirm) generated by the RRC layer, which carries the C-RNTI of the terminal device. In addition, Msg 3 may also carry information such as a buffer status report (BSR). For other triggering events, such as the scenario of uplink / downlink data arrival, Msg 3 may at least include the C-RNTI of the terminal device.

[0068] Step 4: The network device sends a contention resolution message, i.e., Msg4, to the terminal device.

[0069] The network device sends Msg 4 to the terminal device, and the terminal device correctly receives Msg 4 to complete contention resolution. For example, during the RRC connection establishment process, the RRC connection establishment message may be carried in Msg 4.

[0070] Since the terminal device in step 3 can carry its unique identifier in Msg 3, the network device will carry the unique identifier of the terminal device in Msg4 in the contention resolution mechanism to specify the terminal device that wins the contention. Other terminal devices that do not win the contention will initiate random access again.

[0071] It should be understood that in the embodiments of this application, there are two ways to resolve contention conflicts:

[0072] Method 1: If the terminal device carries the C-RNTI in Msg 3, then Msg 4 can be scheduled by a PDCCH scrambled with the C-RNTI.

[0073] Method 2: If the terminal device does not carry the C-RNTI in Msg 3, such as in the case of initial access, then Msg 4 can be scheduled by a PDCCH scrambled with the TC-RNTI. At this time, the contention conflict can be resolved by the terminal device receiving the PDSCH of Msg 4, obtaining the contention resolution ID, and determining whether the conflict is resolved by matching the contention resolution ID with the service data unit (SDU) of the common control channel (CCCH) in Msg 3.

[0074] The two-step random access process is being studied in the NR Rel-16 version standardization process. Compared with the four-step random access process in the Rel-15 version, the two-step random access can reduce the latency and also reduce the signaling overhead. The basic steps of the two-step random access determined currently are:

[0075] 1. The terminal sends MsgA to the network, and MsgA transmits Msg1 + Msg3 of the four-step random access;

[0076] 2. The network sends MsgB to the terminal, and MsgB transmits Msg2 + Msg4 of the four-step random access. After the terminal sends MsgA, it opens a receiving window for MsgB and monitors and receives MsgB within this receiving window.

[0077] For the four-step random access process, after the terminal device sends Msg1, it will listen for the PDCCH scrambled by RA-RNTI within the random access response time window (ra-ResponseWindow) to receive the corresponding RAR. If the UE has not received the random access response within this time window, it is considered that the current random access fails, and the terminal device will re-transmit Msg1. When the number of times the terminal device sends Msg1 reaches a certain threshold, the terminal device will indicate to the upper layer that there is a random access problem. The random access response time window starts from the first PDCCH resource (occasion) after the terminal device sends Msg1. The window length of ra-ResponseWindow is configured by the network, and the maximum value supported by ra-ResponseWindow is a window length of 10 ms.

[0078] Similarly, after the terminal device sends MsgA, it will also start a receiving time window for MsgB. The terminal device listens for MsgB from the network within this receiving time window. If the terminal device does not receive MsgB within this receiving window, the terminal device considers that the current random access fails.

[0079] A network slice consists of a Radio Access Network (RAN) part and a Core Network (CN) part. Different network slices have different Network Slice Selection Assistance Information (NSSAI).

[0080] The network's support for network slices depends on carrying data communications belonging to different network slices and different transmission performance requirements (such as reliability, transmission delay, transmission rate, etc.) by different Protocol Data Unit (PDU) sessions.

[0081] For example, the network will carry the Enhance Mobile Broadband (eMBB) and Ultra-Reliable and Low Latency Communication (URLLC) services on different PDU sessions. Each different PDU session may have multiple Quality of Service flows (QoS Flows).

[0082] In the downlink direction, the Service Data Flow (SDF) template of the Non-Access Stratum (NAS) of the core network classifies different data packets from the application layer and maps them to different QoS Flows in different PDU sessions, and sends them to the RAN in different PDU sessions. The RAN maps them to different Data Radio Bearers (DRBs) according to the ID information of the QoS Flow and sends them to the UE over the air interface. Similarly, for uplink data, similar operations can be adopted.

[0083] As described above, for the RAN network slice, after the network device receives Msg 5 (i.e., the first downlink message after the random access process, such as: the RRC connection establishment complete message), the network device can obtain the network slice information required by the terminal device. However, the network slice required by the terminal device may not be the network slice supported by the network device, or although it is the network slice supported by the network device, but this network slice is overloaded. In this case, the network device can only send the RRC Connection Release message after receiving Msg 5, causing the terminal device to reselect a suitable cell, thus resulting in service delay of the terminal device.

[0084] To solve the above technical problems, the present application solves the above technical problems by the terminal device sending information on whether the terminal device supports network slices and / or the network slices supported by the terminal device to the network device during the random access process.

[0085] The technical solution of the present application will be described in detail below through specific embodiments.

[0086] Figure 3 The following is an interaction flowchart of a wireless communication method provided in an embodiment of the present application, and the method includes the following steps:

[0087] Step S310: The terminal device sends first slice-related information to the network device.

[0088] Among them, the first slice-related information is carried in the random access procedure.

[0089] The first slice-related information is used to indicate whether the terminal device supports network slicing, and / or the network slices supported by the terminal device.

[0090] Optionally, the first slice-related information can be sent from the NAS layer of the terminal device to the Access Stratum (AS) layer of the terminal device, or determined by the AS according to service requirements, etc.

[0091] Optionally, the first slice-related information being carried in the random access procedure means that the first slice-related information is directly carried in the random access procedure or indirectly (i.e., implicitly) carried in the random access procedure.

[0092] Exemplarily, the first slice-related information is carried in message Msg 3 or Msg A in the random access procedure. Or, the first slice-related information is additional indication information of Msg 3 or Msg A. These are the cases where the first slice-related information is directly carried in the random access procedure.

[0093] Exemplarily, different first slice-related information corresponds to different random access resources. Or, different first slice-related information corresponds to different Msg 3 sizes or different Msg A sizes in the random access procedure. These are the cases where the first slice-related information is indirectly carried in the random access procedure.

[0094] The following gives an example of the first slice-related information being carried in message Msg 3 or Msg A in the random access procedure:

[0095] Optionally, the first slice-related information is the CCCH identifier in Msg 3 or Msg A, that is, the CCCH identifier corresponding to the CCCH SDU.

[0096] Optionally, the CCCH identifier is the CCCH Logical Channel Identifier (LCID).

[0097] Optionally, the CCCH identifier is related to the information related to the first slice, that is, different information related to the first slice corresponds to different CCCH identifiers. For example: If the information related to the first slice indicates that the terminal device supports network slicing, the CCCH LCID carried in Msg 3 or MsgA is A at this time; if the information related to the first slice indicates that the terminal device does not support network slicing, the CCCH LCID carried in Msg 3 or Msg A is B at this time. If the information related to the first slice indicates that the terminal device supports network slice m, the CCCH LCID carried in Msg 3 or Msg A is C, and if the information related to the first slice indicates that the terminal device supports network slice n, the CCCH LCID carried in Msg 3 or Msg A is D.

[0098] The following is an example for the case where the information related to the first slice is additional indication information in Msg 3 or Msg A:

[0099] Optionally, the additional indication information may be an additional identifier (flag) in Msg 3 or Msg A.

[0100] This flag is used to indicate whether the terminal device supports network slicing. When the flag takes the first value, it means that the terminal device supports network slicing. When the flag takes the second value, it means that the terminal device does not support network slicing. Among them, the first value can be 0 and the second value can be 1. Or, the first value can be 1 and the second value can be 0.

[0101] Or, this flag is used to indicate that the terminal device does not support network slicing, or the flag is used to indicate the identifier of the network slice supported by the terminal device. For example: When the flag takes the value of 0, it means that the terminal device does not support network slicing. When the flag takes the value of m, it means that the terminal device supports network slice m, and when the flag takes the value of n, it means that the terminal device supports network slice n.

[0102] The following is an example for the case where the information related to the first slice is carried in the message Msg 1 or Msg A in the random access process:

[0103] Exemplarily, different information related to the first slice corresponds to different random access resources. Or, different information related to the first slice corresponds to different random access resources in the random access process. These are the cases where the information related to the first slice is indirectly carried in the random access process.

[0104] The following is an example for the case where different information related to the first slice corresponds to different random access resources:

[0105] Optionally, the random access resource includes at least one of the following: the time domain resource, frequency domain resource, code domain resource, and preamble of the PRACH. Among them, the time domain resource and / or frequency domain resource of the PRACH is the RO resource.

[0106] Exemplarily, if the first slice-related information indicates that the terminal device supports network slicing, the RO resource adopted by the terminal device at this time is RO resource 1; if the first slice-related information indicates that the terminal device does not support network slicing, the RO resource adopted by the terminal device at this time is RO resource 2; if the first slice-related information indicates that the terminal device supports network slice m, the RO resource adopted by the terminal device at this time is RO resource 3; if the first slice-related information indicates that the terminal device supports network slice n, the RO resource adopted by the terminal device at this time is RO resource 4.

[0107] Exemplarily, if the first slice-related information indicates that the terminal device supports network slicing, the RO resource adopted by the terminal device at this time is RO resource 1; if the first slice-related information indicates that the terminal device does not support network slicing, the RO resource adopted by the terminal device at this time is RO resource 2.

[0108] Exemplarily, if the first slice-related information indicates that the terminal device supports network slicing, the PRACH frequency domain resource adopted by the terminal device at this time is frequency domain resource 1; if the first slice-related information indicates that the terminal device does not support network slicing, the PRACH frequency domain resource adopted by the terminal device at this time is frequency domain resource 2; if the first slice-related information indicates that the terminal device supports network slice m, the PRACH frequency domain resource adopted by the terminal device at this time is frequency domain resource 3; if the first slice-related information indicates that the terminal device supports network slice n, the PRACH frequency domain resource adopted by the terminal device at this time is frequency domain resource 4.

[0109] Exemplarily, if the first slice-related information indicates that the terminal device supports network slicing, the PRACH code domain resource adopted by the terminal device at this time is code domain resource 1; if the first slice-related information indicates that the terminal device does not support network slicing, the PRACH code domain resource adopted by the terminal device at this time is code domain resource 2; if the first slice-related information indicates that the terminal device supports network slice m, the PRACH code domain resource adopted by the terminal device at this time is code domain resource 3; if the first slice-related information indicates that the terminal device supports network slice n, the PRACH code domain resource adopted by the terminal device at this time is code domain resource 4.

[0110] Exemplarily, if the first slice-related information indicates that the terminal device supports network slicing, the preamble adopted by the terminal device at this time is preamble 1; if the first slice-related information indicates that the terminal device does not support network slicing, the preamble adopted by the terminal device at this time is preamble 2; if the first slice-related information indicates that the terminal device supports network slice m, the preamble adopted by the terminal device at this time is preamble 3; if the first slice-related information indicates that the terminal device supports network slice n, the preamble adopted by the terminal device at this time is preamble 4.

[0111] Exemplarily, if the first slice-related information indicates that the terminal device supports network slicing, the preamble adopted by the terminal device at this time is preamble 1; if the first slice-related information indicates that the terminal device does not support network slicing, the preamble adopted by the terminal device at this time is preamble 2.

[0112] Exemplarily, if the first slice-related information indicates that the terminal device supports network slicing, the terminal device adopts preamble 1 and RO1 at this time; if the first slice-related information indicates that the terminal device does not support network slicing, the terminal device adopts preamble 2 and RO2 at this time; if the first slice-related information indicates that the terminal device supports network slice m, the terminal device adopts preamble 3 and RO3 at this time; if the first slice-related information indicates that the terminal device supports network slice n, the terminal device adopts preamble 4 and RO4 at this time.

[0113] Exemplarily, if the first slice-related information indicates that the terminal device supports network slicing, the terminal device adopts preamble 1 and RO1 at this time; if the first slice-related information indicates that the terminal device does not support network slicing, the terminal device adopts preamble 2 and RO2 at this time.

[0114] The following gives examples for different first slice-related information corresponding to different Msg 3 sizes or different Msg A sizes in the random access process:

[0115] Exemplarily, if the first slice-related information indicates that the terminal device supports network slicing, the terminal device sends Msg 3 of a first length; if the first slice-related information indicates that the terminal device does not support network slicing, the terminal device sends Msg 3 of a second length. Among them, the first length can be 56 bit, the second length can be 48 bit, or the first length can be 48 bit, and the second length can be 56 bit.

[0116] Exemplarily, if useFulResumeID is set to true, an RRC resume procedure is initiated. If the first slice-related information indicates that the terminal device supports network slicing, the terminal device sends an RRC resume request1. Otherwise, if the first slice-related information indicates that the terminal device does not support network slicing, the terminal device sends an RRC resume request. Alternatively, if useFulResumeID is set to true, an RRC resume procedure is initiated. If the first slice-related information indicates that the terminal device does not support network slicing, the terminal device sends an RRC resume request1. Otherwise, if the first slice-related information indicates that the terminal device supports network slicing, the terminal device sends an RRC resume request. Herein, RRC resume request1 and RRC resume request are Msg 3 messages of different sizes.

[0117] It should be noted that in this application, "support" can also be referred to as "requirement", "expectation", "interest", "selection", or "the network slice supported by the UE matches the network slice supported by the network side", etc. For example, the network slice supported by the terminal device can also be referred to as the network slice required by the terminal device, the network slice expected by the terminal device, the network slice interested by the terminal device, or the network slice selected by the terminal device.

[0118] Optionally, the network slice selected by the terminal device refers to the network slice selected by the terminal device from at least one network slice provided by the communication system.

[0119] Optionally, the network slice supported by the terminal device is the network slice with the highest priority selected by the terminal device. Alternatively, the network slice supported by the terminal device is the network slice with the highest priority selected by the terminal device and is also the network slice supported by the network device.

[0120] Optionally, the network slice with the highest priority is the network slice with the highest priority for the terminal device.

[0121] Optionally, the terminal device may determine the network slices supported by the network device based on the second slice-related information broadcast by the network device. The second slice-related information of the network device includes at least one of the following: the identifier of at least one network slice; the priority of at least one network slice; the correspondence between at least one frequency point and at least one network slice; the correspondence between at least one cell and at least one network slice; the frequency point priority of at least one frequency point corresponding to at least one network slice; the cell priority of at least one cell corresponding to at least one network slice; the correspondence between at least one random access resource and at least one network slice; the correspondence between at least one random access parameter value and at least one network slice; the correspondence between at least one random access parameter value and at least one random access resource.

[0122] The following is an explanation of the information included in the second slice-related information:

[0123] Optionally, the identifier of at least one network slice may be the identifier of at least one network slice supported by the above network device, or the identifier of at least one network slice not supported by the network device, or the identifier of the network slices supported by the neighboring cells of the serving cell of the network device, or the identifier of all network slices on the network side.

[0124] Optionally, the priority of at least one network slice may be the priority of at least one network slice supported by the above network device, or the priority of at least one network slice not supported by the network device, or the priority of the network slices supported by the neighboring cells of the serving cell of the network device, or the priority of all network slices on the network side.

[0125] Optionally, the correspondence between at least one frequency point and at least one network slice is: the correspondence between at least one frequency point and at least one network slice supported by the above network device. Or the correspondence between at least one frequency point and at least one network slice not supported by the above network device, or the correspondence between the network slices supported by the neighboring cells of the serving cell of the network device and the frequency points, or the correspondence between at least one frequency point and all network slices.

[0126] Optionally, the correspondence between at least one cell and at least one network slice is: the correspondence between at least one cell and at least one network slice supported by the above network device. Or the correspondence between at least one cell and at least one network slice not supported by the above network device. Or the correspondence between the network slices supported by the neighboring cells of the serving cell of the network device and the cells, or the correspondence between at least one cell and all network slices.

[0127] Optionally, the frequency priority of at least one frequency point corresponding to at least one network slice is: the frequency priority of at least one frequency point corresponding to the network slices supported by the network device. Or the frequency priority of at least one frequency point corresponding to the network slices not supported by the network device, or the frequency priority of at least one frequency point corresponding to the network slices supported by the neighboring cells, or the frequency priority of at least one frequency point corresponding to all network slices on the network side.

[0128] Optionally, the cell priority of at least one cell corresponding to at least one network slice is: the cell priority of at least one cell corresponding to the network slices supported by the network device. Or the cell priority of at least one cell corresponding to the network slices not supported by the network device. Or the cell priority of at least one cell corresponding to the network slices supported by the neighboring cells, or the cell priority of at least one cell corresponding to all network slices on the network side.

[0129] Optionally, the correspondence between at least one random access resource and at least one network slice is: the correspondence between the random access resources and the network slices supported by the above network device. Or the correspondence between the random access resources and the network slices not supported by the network device. Or the correspondence between the random access resources and the network slices supported by the neighboring cells, or the correspondence between all network slices and random access resources.

[0130] Optionally, the correspondence between at least one random access parameter value and at least one network slice is: the correspondence between the random access parameter values and the network slices supported by the above network device. Or the correspondence between the random access parameter values and the network slices not supported by the network device. Or the correspondence between the random access parameter values and the network slices supported by the neighboring cells, or the correspondence between all network slices and random access parameter values.

[0131] Optionally, the correspondence between at least one random access parameter value and at least one random access resource is: the correspondence between the random access resources corresponding to the network slices supported by the network device and the random access parameter values. Or the correspondence between the random access resources corresponding to the network slices not supported by the network device and the random access parameter values. Or the correspondence between the random access resources corresponding to the network slices supported by the neighboring cells and the random access parameter values. Or the correspondence between the random access resources corresponding to all network slices and the random access parameter values.

[0132] Optionally, the identifier of at least one network slice may be the identifier of at least one network slice supported by the above network device. Based on this, the terminal device can determine the network slices supported by the network device. Of course, the identifier of at least one network slice may also be the identifier of at least one network slice not supported by the network device. In this case, when the terminal device has learned the identifiers of all network slices, based on the identifier of at least one network slice not supported by the network device, the network slices supported by the network device can be determined. Alternatively, the identifier of at least one network slice is the identifier of at least one network slice not supported and supported by the above network device, such as the identifiers of all network slices on the network side. Optionally, in this case, the terminal device requires additional indication from the network device to determine the network slices supported by the network device. In addition, the network slice identifier may also be a slice group identifier, a slice category identifier, etc.

[0133] Optionally, the priority of at least one network slice may be the priority of at least one network slice supported by the above network device. Based on this, the terminal device can determine the priority of the network slices supported by the network device. Of course, the priority of at least one network slice may also be the priority of at least one network slice not supported by the network device. In this case, when the terminal device has learned the priorities of all network slices, based on the priority of at least one network slice not supported by the network device, the priority of the network slices supported by the network device can be determined. Alternatively, the priority of at least one network slice is the priority of at least one network slice not supported and supported by the above network device, such as the priorities of all network slices on the network side. Optionally, in this case, the terminal device requires additional indication from the network device to determine the priority of the network slices supported by the network device.

[0134] Optionally, the correspondence between at least one frequency point and at least one network slice is: the correspondence between at least one frequency point and at least one network slice supported by the above network device. When the terminal device obtains this correspondence, it can determine the correspondence between the frequency point and the network slices supported by the network device. Alternatively, the correspondence between at least one frequency point and at least one network slice is: the correspondence between at least one frequency point and at least one network slice not supported by the above network device. In this case, when the terminal device has learned the correspondence between all network slices and frequency points, based on the correspondence between the above at least one frequency point and at least one network slice, the correspondence between at least one frequency point and at least one network slice supported by the above network device can be determined. Alternatively, the correspondence between at least one frequency point and at least one network slice is: the correspondence between at least one frequency point and all network slices. Optionally, in this case, the terminal device requires additional indication from the network device to determine the correspondence between at least one frequency point and the network slices supported by the network device.

[0135] Optionally, the correspondence between at least one cell and at least one network slice is: the correspondence between at least one cell and at least one network slice supported by the above network device. After the terminal device obtains this correspondence, it can determine the correspondence between the cell and the network slice supported by the network device. Alternatively, the correspondence between at least one cell and at least one network slice is: the correspondence between at least one cell and at least one network slice not supported by the above network device. In this case, when the terminal device already knows the correspondence between at least one cell and all network slices, based on the correspondence between at least one cell and at least one network slice not supported by the above network device, it can determine the correspondence between at least one cell and at least one network slice supported by the above network device. Alternatively, the correspondence between at least one cell and at least one network slice is: the correspondence between at least one cell and all network slices. Optionally, in this case, the terminal device needs an additional indication from the network device to determine the correspondence between the cell and the network slice supported by the above network device.

[0136] Optionally, the frequency priorities of at least one frequency point corresponding to at least one network slice are: the frequency priorities of at least one frequency point corresponding to the network slices supported by the network device. Exemplarily, for different network slices, the frequency priorities of at least one frequency point corresponding to them can be the same or different. Based on this, after the terminal device obtains this priority, it can determine the different frequency priorities corresponding to each network slice supported by the network device. Alternatively, the frequency priorities of at least one frequency point corresponding to at least one network slice are: the frequency priorities of at least one frequency point corresponding to the network slices not supported by the network device. Exemplarily, for different network slices, the frequency priorities of at least one frequency point corresponding to them can be the same or different. In this case, when the terminal device already knows the frequency priorities of the frequency points corresponding to all network slices, based on the frequency priorities of at least one frequency point corresponding to the network slices not supported by the above network device, it can determine the frequency priorities of at least one frequency point corresponding to the network slices supported by this network device. Alternatively, the frequency priorities of at least one frequency point corresponding to at least one network slice are: the frequency priorities of at least one frequency point corresponding to all network slices on the network side. Exemplarily, for different network slices, the frequency priorities of at least one frequency point corresponding to them can be the same or different. Optionally, in this case, the terminal device needs an additional indication from the network device to determine the frequency priorities of at least one frequency point corresponding to the network slices supported by the network device.

[0137] Optionally, the cell priority of at least one cell corresponding to at least one network slice is: the cell priority of at least one cell corresponding to the network slice supported by the network device. Alternatively, the cell priority of at least one cell corresponding to at least one network slice is: the cell priority of at least one cell corresponding to the network slice not supported by the network device. In this case, when the terminal device has learned the cell priorities of all cells corresponding to all network slices, based on the cell priorities of at least one cell corresponding to the network slice not supported by the network device, the cell priorities of at least one cell corresponding to the network slice supported by the network device can be determined. Alternatively, the cell priority of at least one cell corresponding to at least one network slice is: the cell priority of at least one cell corresponding to all network slices on the network side. Optionally, in this case, the terminal device requires additional indication from the network device to determine the cell priorities of at least one cell corresponding to the network slice supported by the network device.

[0138] Optionally, the correspondence between at least one random access resource and at least one network slice is: the correspondence between the network slice supported by the network device and the random access resource. Alternatively, the correspondence between at least one random access resource and at least one network slice is: the correspondence between the network slice not supported by the network device and the random access resource. In this case, when the terminal device has learned the correspondence between all network slices and random access resources, based on the correspondence between the network slice not supported by the network device and the random access resource, the correspondence between the network slice supported by the network device and the random access resource can be determined. Alternatively, the correspondence between at least one random access resource and at least one network slice is: the correspondence between all network slices and random access resources. Optionally, in this case, the terminal device requires additional indication from the network device to determine the correspondence between the network slice supported by the network device and the random access resource.

[0139] Optionally, the correspondence between at least one random access parameter value and at least one network slice is: the correspondence between the network slice supported by the network device and the random access parameter value. Alternatively, the correspondence between at least one random access parameter value and at least one network slice is: the correspondence between the network slice not supported by the network device and the random access parameter value. In this case, when the terminal device has learned the correspondence between all network slices and random access parameter values, based on the correspondence between the network slice not supported by the network device and the random access parameter value, the correspondence between the network slice supported by the network device and the random access parameter value can be determined. Alternatively, the correspondence between at least one random access parameter value and at least one network slice is: the correspondence between all network slices and random access parameter values. Optionally, in this case, the terminal device requires additional indication from the network device to determine the correspondence between the network slice supported by the network device and the random access parameter value.

[0140] Optionally, the correspondence between at least one random access parameter value and at least one random access resource is: the correspondence between the random access resource corresponding to the network slice supported by the network device and the random access parameter value. Or, the correspondence between at least one random access parameter value and at least one random access resource is: the correspondence between the random access resource corresponding to the network slice not supported by the network device and the random access parameter value. In this case, when the terminal device has learned the correspondence between the random access resources and the random access parameter values of all network slices, based on the correspondence between the random access resource corresponding to the network slice not supported by the network device and the random access parameter value, the correspondence between the random access resource corresponding to the network slice supported by the network device and the random access parameter value can be determined. Or, the correspondence between at least one random access parameter value and at least one random access resource is: the correspondence between the random access resources and the random access parameter values corresponding to all network slices. Optionally, in this case, the terminal device needs an additional indication from the network device to determine the correspondence between the random access resource corresponding to the network slice supported by the network device and the random access parameter value.

[0141] Optionally, the "correspondence" in this application can be a one-to-one, many-to-one, one-to-many, or many-to-many correspondence.

[0142] Optionally, the identifier of the network slice in this application is any one of the following: NSSAI, Single Network Slice Selection Assistance Information (S-NSSAI), Network Slicing Identity (NSID).

[0143] Optionally, the random access parameter value includes: a backoff parameter value and / or a power modification value. Among them, the power modification value can be a power ramp value or a power slide value.

[0144] Optionally, the backoff parameter value and / or the power ramp parameter value can be an absolute value, or a relative value or an adjustment value.

[0145] Optionally, the backoff parameter value indicates the waiting or interval duration for the next Msg1 or MsgA, that is, the backoff parameter value is backoff, or, it indicates the adjustment value / adjustment factor of the waiting or interval duration for the next transmission of Msg1 or MsgA, that is, the backoff parameter value is backoff factor.

[0146] The power ramping parameter indicates the value by which the power needs to be increased or the increased power value when initiating a random access next time, that is, the power ramping parameter is power ramping, or, indicates the adjustment value / adjustment factor of the value by which the power needs to be increased or the increased power value when initiating a random access next time, that is, the power ramping parameter is power ramping factor.

[0147] In summary, in the present application, the present application enables the terminal device to send information on whether the terminal device supports network slicing and / or the network slices supported by the terminal device to the network device during the random access process, that is, the network device can obtain the network slices required by the terminal device during the random access process, without having to wait until receiving Msg 5 to obtain the network slices required by the terminal device. The technical solution provided by the present application can reduce the service latency of the terminal device.

[0148] After the above step S301, the terminal device can perform subsequent operations, such as random access or cell selection, reselection, etc. This will be described through the following several embodiments:

[0149] Implementable manner 1: The terminal device receives the access control information sent by the network device. Optionally, the terminal device determines the random access result according to the access control information. And / or, the terminal device performs random access according to the access control information. And / or, the terminal device determines the cell selection or cell reselection information according to the access control information. And / or, the terminal device performs cell selection or cell reselection according to the access control information. And / or, the terminal device determines the RRC state according to the access control information.

[0150] Implementable manner 2: The terminal device performs random access according to the first slice-related information.

[0151] Implementable manner 3: The terminal device receives the random access parameter value sent by the network device. The terminal device performs random access according to the random access parameter value.

[0152] The following provides a detailed description of Implementable manner 1:

[0153] Optionally, the access control information is sent by the network device when a first condition is met.

[0154] Optionally, the first condition includes at least one of the following: The terminal device does not support network slicing. The network slices supported by the terminal device are not the network slices supported by the network device. The network slices supported by the terminal device are not the network slices supported by the network device that meet the priority conditions. The number of times the network slices supported by the terminal device are requested reaches a preset threshold. The network slices supported by the terminal device are not the network slices to which the network device wants to access preferentially. The network slices supported by the terminal device are not specific network slices.

[0155] Optionally, in this application, the terminal device not supporting network slicing means that the terminal device does not support any network slicing, or at least one of the network slicing supported by the terminal device does not match the network slicing supported by the network side.

[0156] Optionally, in this application, the preset threshold can be set according to the actual situation, such as being set to 50 or 100, etc.

[0157] Optionally, the access control information is carried in a Radio Resource Control Reject (RRC Reject) message.

[0158] Optionally, the RRC Reject further includes: the reason for the network device to reject the terminal device from performing random access. The reason can be at least one of the following: the terminal device does not support network slicing; the network slicing supported by the terminal device is not the network slicing supported by the network device; the network slicing supported by the terminal device is not the network slicing supported by the network device that meets the priority condition; the number of times the network slicing supported by the terminal device is requested reaches the preset threshold; the network slicing supported by the terminal device is not the network slicing to which the network device wants to access preferentially; the network slicing supported by the terminal device is not a specific network slicing.

[0159] Optionally, the access control information includes at least one of the following: the network slicing supported by the serving cell of the network device; the network slicing supported by the neighboring cell of the serving cell; the identifier of at least one network slicing; the priority of at least one network slicing; the correspondence between at least one frequency point and at least one network slicing; the correspondence between at least one cell and at least one network slicing; the frequency point priority of at least one frequency point corresponding to at least one network slicing; the cell priority of at least one cell corresponding to at least one network slicing; the correspondence between at least one random access resource and at least one network slicing; the correspondence between at least one random access parameter value and at least one network slicing; the correspondence between at least one random access parameter value and at least one random access resource.

[0160] The following is an explanation of the information included in the access control information:

[0161] Optionally, the identifier of at least one network slicing can be the identifier of at least one network slicing supported by the above-mentioned network device, or the identifier of at least one network slicing not supported by the network device, or the identifier of the network slicing supported by the neighboring cell of the serving cell of the network device, or the identifier of all network slicings on the network side.

[0162] Optionally, the priority of at least one network slice can be the priority of at least one network slice supported by the above network device, or the priority of at least one network slice not supported by the network device, or the priority of the network slice supported by the neighboring cell of the serving cell of the network device, or the priority of all network slices on the network side.

[0163] Optionally, the correspondence between at least one frequency point and at least one network slice is: the correspondence between at least one frequency point and at least one network slice supported by the above network device. Or the correspondence between at least one frequency point and at least one network slice not supported by the above network device, or the correspondence between the network slice supported by the neighboring cell of the serving cell of the network device and the frequency point, or the correspondence between at least one frequency point and all network slices.

[0164] Optionally, the correspondence between at least one cell and at least one network slice is: the correspondence between at least one cell and at least one network slice supported by the above network device. Or the correspondence between at least one cell and at least one network slice not supported by the above network device. Or the correspondence between the network slice supported by the neighboring cell of the serving cell of the network device and the cell, or the correspondence between at least one cell and all network slices.

[0165] Optionally, the frequency priority of at least one frequency point corresponding to at least one network slice is: the frequency priority of at least one frequency point corresponding to the network slice supported by the network device. Or the frequency priority of at least one frequency point corresponding to the network slice not supported by the network device, or the frequency priority of at least one frequency point corresponding to the network slice supported by the neighboring cell, or the frequency priority of at least one frequency point corresponding to all network slices on the network side.

[0166] Optionally, the cell priority of at least one cell corresponding to at least one network slice is: the cell priority of at least one cell corresponding to the network slice supported by the network device. Or the cell priority of at least one cell corresponding to the network slice not supported by the network device. Or the cell priority of at least one cell corresponding to the network slice supported by the neighboring cell, or the cell priority of at least one cell corresponding to all network slices on the network side.

[0167] Optionally, the correspondence between at least one random access resource and at least one network slice is: the correspondence between the network slice supported by the above network device and the random access resource. Or the correspondence between the network slice not supported by the network device and the random access resource. Or the correspondence between the network slice supported by the neighboring cell and the random access resource, or the correspondence between all network slices and the random access resource.

[0168] Optionally, the correspondence between at least one random access parameter value and at least one network slice is: the correspondence between the network slices supported by the above network device and the random access parameter value; or the correspondence between the network slices not supported by the network device and the random access parameter value; or the correspondence between the network slices supported by the neighboring cell and the random access parameter value; or the correspondence between all network slices and the random access parameter value.

[0169] Optionally, the correspondence between at least one random access parameter value and at least one random access resource is: the correspondence between the random access resources corresponding to the network slices supported by the network device and the random access parameter value; or the correspondence between the random access resources corresponding to the network slices not supported by the network device and the random access parameter value; or the correspondence between the random access resources corresponding to the network slices supported by the neighboring cell and the random access parameter value; or the correspondence between the random access resources corresponding to all network slices and the random access parameter value.

[0170] Optionally, the random access result determined by the terminal device according to the access control information is RRC Reject.

[0171] Optionally, an exemplary description is given for the random access of the terminal device according to the access control information:

[0172] Example 1: The terminal device obtains the network slices supported by the network device through the access control information. If the terminal device also supports the network slices, based on this, the terminal device carries the relevant information of the network slices to the random access process to re-perform the random access process, such as re-sending Msg 1 or Msg A.

[0173] Example 2: The terminal device obtains the network slices supported by the neighboring cell through the access control information. If the terminal device also supports the network slices, based on this, in the neighboring cell, the terminal device carries the relevant information of the network slices to the random access process to re-perform the random access process, such as re-sending Msg 1 or Msg A.

[0174] Example 3: The terminal device obtains the identifiers of at least one network slice, selects a network slice, and carries the relevant information of the network slice to the random access process to re-perform the random access process.

[0175] Example 4: The terminal device obtains the priorities of at least one network slice, selects a network slice with the highest priority, and carries the relevant information of the network slice to the random access process to re-perform the random access process.

[0176] Example 5: The terminal device obtains the correspondence between at least one frequency point and at least one network slice. The terminal device selects a network slice it supports according to this correspondence, and performs cell selection or reselection measurement at this frequency point, or makes a judgment on cell selection or reselection at this frequency point, or the terminal device carries the relevant information of this network slice into the random access process at the cell corresponding to this frequency point to re-perform the random access process.

[0177] Example 6: The terminal device obtains the correspondence between at least one cell and at least one network slice. The terminal device selects a network slice it supports according to this correspondence, and performs cell selection or reselection measurement at the cell corresponding to this network slice, or makes a judgment on cell selection or reselection at this frequency point, or the terminal device carries the relevant information of this network slice into the random access process at this cell to re-perform the random access process.

[0178] Example 7: The terminal device obtains the frequency point priorities of at least one frequency point corresponding to at least one network slice. The terminal device selects the frequency point with the highest priority. If the network slice corresponding to the frequency point with the highest priority is supported by the terminal device, at the cell corresponding to this frequency point, the terminal device carries the relevant information of this network slice into the random access process to re-perform the random access process.

[0179] Example 8: The terminal device obtains the cell priorities of at least one cell corresponding to at least one network slice. The terminal device selects the cell with the highest priority. If the network slice corresponding to the cell with the highest priority is supported by the terminal device, at this cell, the terminal device carries the relevant information of this network slice into the random access process to re-perform the random access process.

[0180] Example 9: The terminal device obtains the frequency point priorities of at least one frequency point corresponding to at least one network slice. The terminal device selects a slice. According to the at least one frequency point corresponding to this slice and / or the frequency point priorities of at least one frequency point, the terminal device performs cell selection or reselection measurement, or makes a judgment on cell selection or reselection at this frequency point, or carries the relevant information of this network slice into the random access process to re-perform the random access process.

[0181] Example 10: The terminal device obtains the frequency point priorities of at least one frequency point corresponding to at least one network slice. The terminal device selects the slice with the highest priority (such as the one with the highest priority considered by the terminal device or the one with the highest priority indicated by the network). According to the at least one frequency point corresponding to this slice and / or the frequency point priorities of at least one frequency point, the terminal device performs cell selection or reselection measurement, or makes a judgment on cell selection or reselection at this frequency point, or carries the relevant information of this network slice into the random access process to re-perform the random access process.

[0182] Example 11: The terminal device obtains the cell priorities of at least one cell corresponding to at least one network slice. The terminal device selects a slice. According to the at least one cell corresponding to this slice and / or the cell priorities of the at least one cell, the terminal device performs cell selection or reselection measurements, or makes a judgment on cell selection or reselection at this frequency point, or carries the relevant information of this network slice into the random access process to re - execute the random access process.

[0183] Example 12: The terminal device obtains the cell priorities of at least one cell corresponding to at least one network slice. The terminal device selects the slice with the highest priority (such as the one with the highest priority considered by the terminal device or the one with the highest priority indicated by the network). According to the at least one cell corresponding to this slice and / or the cell priorities of the at least one cell, the terminal device performs cell selection or reselection measurements, or makes a judgment on cell selection or reselection at this frequency point, or carries the relevant information of this network slice into the random access process to re - execute the random access process.

[0184] Example 13: The terminal device obtains the correspondence between at least one random access resource and at least one network slice. The terminal device selects a network slice that it supports according to this correspondence, and in the cell corresponding to this random access resource, the terminal device carries the relevant information of this network slice into the random access process to re - execute the random access process.

[0185] Example 14: The terminal device obtains the correspondence between at least one random access resource and at least one network slice. The terminal device determines the corresponding random access resource according to the network slice (the network slice can be determined previously) and the correspondence between the slice and this random access resource, and initiates a random access process using this random access resource. Implicitly carry the relevant information of the network slice to the network.

[0186] Example 15: The terminal device obtains the correspondence between at least one random access parameter value and at least one network slice. The terminal device selects a network slice that it supports according to this correspondence, and in the cell corresponding to this random access parameter value, the terminal device carries the relevant information of this network slice into the random access process to re - execute the random access process.

[0187] Example 16: The terminal device obtains the correspondence between at least one random access parameter value and at least one network slice. The terminal device uses this random access parameter value to execute a random access process according to the network slice (the network slice can be determined previously) and the correspondence between the slice and this random access parameter value.

[0188] Example 17: The terminal device obtains the correspondence between at least one random access parameter value and at least one random access resource. The terminal device selects a random access resource according to the correspondence. If it is determined that the network slice corresponding to the random access resource is supported by the terminal device, in the cell corresponding to the random access resource, the terminal device carries the relevant information of the network slice in the random access process to re - execute the random access process.

[0189] Example 18: The terminal device obtains the correspondence between at least one random access parameter value and at least one random access resource. The terminal device uses the random access parameter value to execute the random access process according to the random access resource (the random access resource can be determined previously) and the correspondence between the random access resource and the random access parameter value.

[0190] It should be noted that the example of the terminal device determining the cell selection or cell reselection information according to the access control information is similar to the terminal device performing random access according to the access control information, and this application will not elaborate on this.

[0191] Optionally, the RRC state determined by the terminal device according to the access control information can be the RRC idle state.

[0192] The following will elaborate on the second implementation method in detail:

[0193] Optionally, the terminal device performs random access using the random access parameter value corresponding to the first slice - related information.

[0194] Optionally, when the terminal device receives multiple sets of random access parameter values, the terminal device selects a set of random access parameter values from the multiple sets of random access parameter values (for example, selects according to the slice information) to perform random access according to this set of random access parameter values. The parameter values can be broadcast / special signaling (such as RRC release) / pre - configured.

[0195] Optionally, the random access parameter values corresponding to different first slice - related information are different. For example: when the first slice - related information indicates that the terminal device supports the network slice, the corresponding random access parameter value is random access parameter value 0; when the first slice - related information indicates that the terminal device does not support the network slice, the corresponding random access parameter value is random access parameter value 1; when the first slice - related information indicates that the terminal device supports network slice m, the corresponding random access parameter value is random access parameter value 2; when the first slice - related information indicates that the terminal device supports network slice n, the corresponding random access parameter value is random access parameter value 3.

[0196] Optionally, if the first condition or the second condition is met, the terminal device performs random access according to the first slice - related information.

[0197] Among them, the first condition is as described above and will not be elaborated here.

[0198] Optionally, the second condition includes at least one of the following: The terminal device supports network slicing. The network slice supported by the terminal device is the network slice supported by the network device. The network slice supported by the terminal device is the network slice supported by the network device that meets the priority condition. The number of times the network slice supported by the terminal device is requested does not reach the preset threshold. The network slice supported by the terminal device is the network slice to which the network device prefers to access. The network slice supported by the terminal device is a specific network slice.

[0199] The following will give a detailed description of Implementation Option 3:

[0200] Optionally, the random access parameter value sent by the network device to the terminal device is determined by the network device according to the first slice-related information. That is, there is a corresponding relationship between the first slice-related information and the random access parameter value.

[0201] Optionally, when the terminal device receives multiple sets of random access parameter values, the terminal device selects a set of random access parameter values from the multiple sets of random access parameter values (for example, according to the slice information) to perform random access according to this set of random access parameter values. The parameter value can be broadcast / special signaling (such as RRC release) / pre-configured.

[0202] Optionally, the random access parameter values corresponding to different first slice-related information are different. For example: when the first slice-related information indicates that the terminal device supports network slicing, the corresponding random access parameter value is random access parameter value 0; when the first slice-related information indicates that the terminal device does not support network slicing, the corresponding random access parameter value is random access parameter value 1; when the first slice-related information indicates that the terminal device supports network slice m, the corresponding random access parameter value is random access parameter value 2; when the first slice-related information indicates that the terminal device supports network slice n, the corresponding random access parameter value is random access parameter value 3.

[0203] Optionally, the terminal device receives indication information sent by the network device, and the indication information is used to indicate or indicate the selected random access parameter value.

[0204] Optionally, when the terminal device receives a set of random access parameter values, the indication information is used to indicate this set of random access parameter values, and the terminal device can directly perform random access according to this set of random access parameter values.

[0205] Optionally, when the terminal device receives at least one set of random access parameter values, the indication information is used to indicate the selection method of using random access parameter values based on slice information. Alternatively, the terminal device may determine the random access parameter values based on slice information and perform random access according to this set of random access parameter values.

[0206] Optionally, when the terminal device receives multiple sets of random access parameter values, the indication information is used to indicate that the terminal device selects one set of random access parameter values from the multiple sets of random access parameter values (e.g., selects according to slice information) to perform random access according to this set of random access parameter values. The parameter values may be broadcast / special signaling (such as RRC release) / pre-configured. Further, the network may further indicate which set of random access parameter values the terminal device uses.

[0207] Optionally, when the terminal device receives at least one set of random access parameter values, the indication information is used to indicate based on which set of random access parameter values the terminal device performs random access.

[0208] Optionally, when the terminal device receives at least one set of random access parameter values and also receives at least one set of random access parameter values broadcast by the network device, the indication information is used to indicate the random access parameter values transmitted in a non-broadcast manner, and the terminal device may perform random access according to this set of random access parameter values. Optionally, when the terminal device receives at least one set of random access parameter values and also receives at least one set of random access parameter values broadcast by the network device, according to slice information, the terminal device determines which set of random access parameter values to use for random access.

[0209] Optionally, the indication information is the value on the reserved bit in the random access process. For example: different values of the reserved bit in the RAR can be used to indicate that the terminal device does not use the above-mentioned random access parameter values or the above-mentioned random access parameter values used.

[0210] Optionally, the random access parameter values are sent by the network device when the first condition or the second condition is met.

[0211] Among them, the first condition and the second condition are as described above and will not be elaborated here.

[0212] In summary, in the present application, through the above implementable manner 1, the network device can perform access control on the terminal device, such as sending an RRC Reject to the terminal device, so as to ensure that the terminal devices supporting the same network slice as the network device can access the network preferentially. Through the above implementable manner 2, different terminal devices can adopt different random access parameter values to ensure that terminal devices with different requirements, such as delay requirements, can access the network. Through the above implementable manner 2, the network device can perform access control on the terminal device, so that different terminal devices can adopt different random access parameter values to ensure that terminal devices with different requirements, such as delay requirements, can access the network.

[0213] As described above in conjunction with Figure 3 , the method embodiments of the present application have been described in detail. Below in conjunction with Figures 4 to 8 , the device embodiments of the present application will be described in detail. It should be understood that the device embodiments correspond to the method embodiments, and similar descriptions can refer to the method embodiments.

[0214] Figure 4 FIG. shows a schematic block diagram of a terminal device 400 according to an embodiment of the present application. As Figure 4 shown, the terminal device 400 includes:

[0215] A communication unit 410, configured to send first slice-related information to a network device. Among them, the first slice-related information is carried in the random access process. The first slice-related information is used to indicate whether the terminal device supports network slicing and / or the network slice supported by the terminal device.

[0216] Optionally, different first slice-related information corresponds to different random access resources. Or, the first slice-related information is carried in Msg 3 or Msg A in the random access process. Or, different first slice-related information corresponds to different Msg 3 sizes or different Msg A sizes in the random access process.

[0217] Optionally, the first slice-related information is the CCCH identifier in Msg 3 or Msg A. Or,

[0218] The first slice-related information is additional indication information of Msg 3 or Msg A.

[0219] Optionally, the CCCH identifier is related to the first slice-related information.

[0220] Optionally, the CCCH identifier is the CCCH LCID.

[0221] Optionally, the communication unit 410 is further configured to receive access control information sent by the network device.

[0222] Optionally, it further includes a processing unit 420 configured to perform at least one of the following:

[0223] Determine a random access result based on the access control information.

[0224] Perform random access based on the access control information.

[0225] Determine cell selection or cell reselection information based on the access control information.

[0226] Perform cell selection or cell reselection based on the access control information.

[0227] Determine the RRC state based on the access control information.

[0228] Optionally, the access control information includes at least one of the following: network slices supported by the serving cell of the network device. Network slices supported by neighboring cells of the serving cell. Identifiers of at least one network slice. Priorities of at least one network slice. Corresponding relationships between at least one frequency point and at least one network slice. Corresponding relationships between at least one cell and at least one network slice. Frequency priorities of at least one frequency point corresponding to at least one network slice. Cell priorities of at least one cell corresponding to at least one network slice. Corresponding relationships between at least one random access resource and at least one network slice. Corresponding relationships between at least one random access parameter value and at least one network slice. Corresponding relationships between at least one random access parameter value and at least one random access resource.

[0229] Optionally, the access control information is sent by the network device when a first condition is met.

[0230] Optionally, the access control information is carried in a Radio Resource Control Reject message.

[0231] Optionally, the Radio Resource Control Reject message further includes: the reason for the network device to reject the terminal device from performing random access.

[0232] Optionally, it further includes: a processing unit 420 configured to perform random access based on first slice-related information.

[0233] Optionally, the processing unit 420 is specifically configured to: perform random access using the random access parameter value corresponding to the first slice-related information.

[0234] Optionally, the processing unit 420 is specifically configured to: if a first condition or a second condition is met, perform random access based on the first slice-related information.

[0235] Optionally, it further includes: a processing unit 420. The communication unit 410 is further configured to receive the random access parameter value sent by the network device. The processing unit 420 is configured to perform random access based on the random access parameter value.

[0236] Optionally, the communication unit 410 is further configured to receive indication information sent by a network device, where the indication information is used to indicate or instruct a selected random access parameter value.

[0237] Optionally, the indication information is a value taken on reserved bits during a random access procedure.

[0238] Optionally, the random access parameter value is sent by the network device when a first condition or a second condition is satisfied.

[0239] Optionally, the first condition includes at least one of the following:

[0240] The terminal device does not support network slicing.

[0241] The network slice supported by the terminal device is not the network slice supported by the network device.

[0242] The network slice supported by the terminal device is not the network slice supported by the network device that meets the priority condition.

[0243] The number of times the network slice supported by the terminal device is requested reaches a preset threshold.

[0244] The network slice supported by the terminal device is not the network slice to which the network device prefers to connect.

[0245] The network slice supported by the terminal device is not a specific network slice.

[0246] Optionally, the second condition includes at least one of the following:

[0247] The terminal device supports network slicing.

[0248] The network slice supported by the terminal device is the network slice supported by the network device.

[0249] The network slice supported by the terminal device is the network slice supported by the network device that meets the priority condition.

[0250] The number of times the network slice supported by the terminal device is requested does not reach a preset threshold.

[0251] The network slice supported by the terminal device is the network slice to which the network device prefers to connect.

[0252] The network slice supported by the terminal device is a specific network slice.

[0253] Optionally, the communication unit 410 is further configured to receive second slice-related information broadcast by a network device. The second slice-related information includes at least one of the following: the identifier of at least one network slice; the priority of at least one network slice; the correspondence between at least one frequency point and at least one network slice; the correspondence between at least one cell and at least one network slice; the frequency point priority of at least one frequency point corresponding to at least one network slice; the cell priority of at least one cell corresponding to at least one network slice; the correspondence between at least one random access resource and at least one network slice; the correspondence between at least one random access parameter value and at least one network slice; the correspondence between at least one random access parameter value and at least one random access resource.

[0254] Optionally, the random access parameter value includes: a backoff parameter value and / or a power ramp parameter value.

[0255] Optionally, the backoff parameter value and / or the power ramp parameter value may be an absolute value, or a relative value or an adjustment value.

[0256] Optionally, the backoff parameter value indicates the waiting or interval duration for the next Msg1 or MsgA, or an adjustment value / adjustment factor indicating the waiting or interval duration for sending the next Msg1 or MsgA. The power ramp parameter indicates the value of the power increase required for the next random access initiation, or an adjustment value / adjustment factor indicating the value of the power increase required for the next random access initiation.

[0257] Optionally, the random access resource includes at least one of the following: a random access preamble, the time-domain resource, frequency-domain resource, and code-domain resource of a physical random access channel.

[0258] Optionally, the network slice supported by the terminal device is the network slice with the highest priority selected by the terminal device. Or, the network slice supported by the terminal device is the network slice with the highest priority selected by the terminal device and is also a network slice supported by the network device.

[0259] Optionally, in some embodiments, the above-mentioned communication unit may be a communication interface or transceiver, or an input / output interface of a communication chip or system-on-chip. The above-mentioned processing unit may be one or more processors.

[0260] It should be understood that the terminal device 400 according to the embodiments of the present application may correspond to the terminal device in the method embodiments of the present application, and the above and other operations and / or functions of each unit in the terminal device 400 respectively implement the corresponding processes of the terminal device in the above method embodiments. For the sake of brevity, they are not described herein again.

[0261] Figure 5FIG. 0 shows a schematic block diagram of a network device 500 according to an embodiment of the present application. As Figure 5 shown, the network device 500 includes:

[0262] A communication unit 510, configured to receive first slice-related information sent by a terminal device. The first slice-related information is carried in a random access procedure. The first slice-related information is used to indicate whether the terminal device supports network slicing and / or the network slices supported by the terminal device.

[0263] Optionally, different first slice-related information corresponds to different random access resources. Alternatively, the first slice-related information is carried in Msg 3 or Msg A in the random access procedure. Alternatively, different first slice-related information corresponds to different Msg 3 sizes or different Msg A sizes in the random access procedure.

[0264] Optionally, the first slice-related information is a CCCH identifier in Msg 3 or Msg A. Alternatively, the first slice-related information is additional indication information in Msg3 or Msg A.

[0265] Optionally, the CCCH identifier is related to the first slice-related information.

[0266] Optionally, the CCCH identifier is a CCCH LCID.

[0267] Optionally, the communication unit 510 is further configured to send access control information to the terminal device.

[0268] Optionally, it further includes at least one of the following: The access control information is used to determine a random access result. The access control information is used for the terminal device to perform random access. The access control information is used to determine cell selection or cell reselection information. The access control information is used for the terminal device to perform cell selection or cell reselection. The access control information is used to determine the RRC state.

[0269] Optionally, the access control information includes at least one of the following: Network slices supported by the serving cell of the network device. Network slices supported by neighboring cells of the serving cell. Identifiers of at least one network slice. Priorities of at least one network slice. Correspondence between at least one frequency point and at least one network slice. Correspondence between at least one cell and at least one network slice. Frequency point priorities of at least one frequency point corresponding to at least one network slice. Cell priorities of at least one cell corresponding to at least one network slice. Correspondence between at least one random access resource and at least one network slice. Correspondence between at least one random access parameter value and at least one network slice. Correspondence between at least one random access parameter value and at least one random access resource.

[0270] Optionally, the access control information is sent by the network device when a first condition is met.

[0271] Optionally, the access control information is carried in a Radio Resource Control Reject message.

[0272] Optionally, the Radio Resource Control Reject message further includes: the reason for the network device to reject the terminal device's random access.

[0273] Optionally, the communication unit 510 is further configured to send a random access parameter value to the terminal device.

[0274] Optionally, the communication unit 510 is further configured to send indication information to the terminal device, where the indication information is used to indicate or indicate the selected random access parameter value.

[0275] Optionally, the indication information is the value on a reserved bit in the random access process.

[0276] Optionally, the random access parameter value is sent by the network device when a first condition or a second condition is met.

[0277] Optionally, the first condition includes at least one of the following: the terminal device does not support network slicing; the network slice supported by the terminal device is not the network slice supported by the network device; the network slice supported by the terminal device is not the network slice supported by the network device that meets the priority condition; the number of times the network slice supported by the terminal device is requested reaches a preset threshold; the network slice supported by the terminal device is not the network slice to which the network device wants to preferentially access; the network slice supported by the terminal device is not a specific network slice.

[0278] Optionally, the second condition includes at least one of the following: the terminal device supports network slicing; the network slice supported by the terminal device is the network slice supported by the network device; the network slice supported by the terminal device is the network slice supported by the network device that meets the priority condition; the number of times the network slice supported by the terminal device is requested does not reach a preset threshold; the network slice supported by the terminal device is the network slice to which the network device wants to preferentially access; the network slice supported by the terminal device is a specific network slice.

[0279] Optionally, the communication unit 510 is further configured to broadcast second slice-related information.

[0280] Among them, the second slice-related information includes at least one of the following: the identifier of at least one network slice; the priority of at least one network slice; the correspondence between at least one frequency point and at least one network slice; the correspondence between at least one cell and at least one network slice; the frequency point priority of at least one frequency point corresponding to at least one network slice; the cell priority of at least one cell corresponding to at least one network slice; the correspondence between at least one random access resource and at least one network slice; the correspondence between at least one random access parameter value and at least one network slice; the correspondence between at least one random access parameter value and at least one random access resource.

[0281] Optionally, the random access parameter value includes: a fallback parameter value and / or a power ramping parameter value.

[0282] Optionally, the fallback parameter value and / or the power ramping parameter value can be an absolute value, or a relative value or an adjustment value.

[0283] Optionally, the fallback parameter value indicates the duration of waiting or interval for the next Msg1 or MsgA, or an adjustment value / adjustment factor indicating the duration of waiting or interval for sending the next Msg1 or MsgA. The power ramping parameter indicates the value of power increase required for the next random access initiation, or an adjustment value / adjustment factor indicating the value of power increase required for the next random access initiation.

[0284] Optionally, the random access resource includes at least one of the following: a random access preamble, the time-domain resource, frequency-domain resource, and code-domain resource of a physical random access channel.

[0285] Optionally, the network slice supported by the terminal device is the network slice with the highest priority selected by the terminal device. Or, the network slice supported by the terminal device is the network slice with the highest priority selected by the terminal device and is also the network slice supported by the network device.

[0286] Optionally, in some embodiments, the above communication unit may be a communication interface or transceiver, or an input / output interface of a communication chip or system-on-chip. The above processing unit may be one or more processors.

[0287] It should be understood that the network device 500 according to the embodiments of the present application may correspond to the network device in the method embodiments of the present application, and the above and other operations and / or functions of each unit in the network device 500 respectively implement the corresponding processes of the network device in the above method embodiments. For the sake of brevity, they are not described herein again.

[0288] Figure 6 It is a schematic structural diagram of a communication device 800 provided by the embodiments of the present application. Figure 6The communication device 800 shown includes a processor 810, and the processor 810 can call and run a computer program from the memory to implement the method in the embodiments of the present application.

[0289] Optionally, as Figure 6 shown, the communication device 800 may further include a memory 820. Among them, the processor 810 can call and run a computer program from the memory 820 to implement the method in the embodiments of the present application.

[0290] Among them, the memory 820 can be a separate device independent of the processor 810, or can be integrated in the processor 810.

[0291] Optionally, as Figure 6 shown, the communication device 800 may further include a transceiver 830. The processor 810 can control the transceiver 830 to communicate with other devices. Specifically, it can send information or data to other devices, or receive information or data sent by other devices.

[0292] Among them, the transceiver 830 can include a transmitter and a receiver. The transceiver 830 may further include antennas, and the number of antennas can be one or more.

[0293] Optionally, the communication device 800 may specifically be the network device in the embodiments of the present application, and the communication device 800 can implement the corresponding processes implemented by the network device in the various methods in the embodiments of the present application. For the sake of brevity, it will not be elaborated here.

[0294] Optionally, the communication device 800 may specifically be the mobile terminal / terminal device in the embodiments of the present application, and the communication device 800 can implement the corresponding processes implemented by the mobile terminal / terminal device in the various methods in the embodiments of the present application. For the sake of brevity, it will not be elaborated here.

[0295] Figure 7 is a schematic structural diagram of the device in the embodiments of the present application. Figure 7 The device 900 shown includes a processor 910, and the processor 910 can call and run a computer program from the memory to implement the method in the embodiments of the present application.

[0296] Optionally, as Figure 7 shown, the device 900 may further include a memory 920. Among them, the processor 910 can call and run a computer program from the memory 920 to implement the method in the embodiments of the present application.

[0297] Among them, the memory 920 can be a separate device independent of the processor 910, or can be integrated in the processor 910.

[0298] Optionally, the device 900 may further include an input interface 930. Among them, the processor 910 may control the input interface 930 to communicate with other devices or chips. Specifically, it may obtain information or data sent by other devices or chips.

[0299] Optionally, the device 900 may further include an output interface 940. Among them, the processor 910 may control the output interface 940 to communicate with other devices or chips. Specifically, it may output information or data to other devices or chips.

[0300] Optionally, the device may be applied to the network device in the embodiments of the present application, and the device may implement the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, details are not described herein again.

[0301] Optionally, the device may be applied to the mobile terminal / terminal device in the embodiments of the present application, and the device may implement the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, details are not described herein again.

[0302] Optionally, the device mentioned in the embodiments of the present application may also be a chip. For example, it may be a system-on-chip, system chip, chip system or system-on-chip.

[0303] Figure 8 is a schematic block diagram of a communication system 1000 provided by the embodiments of the present application. As Figure 8 shown, the communication system 1000 includes a terminal device 1010 and a network device 1020.

[0304] Among them, the terminal device 1010 may be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 1020 may be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, details are not described herein again.

[0305] It should be understood that the processor in the embodiments of the present application may be an integrated circuit chip with signal processing capabilities. In the implementation process, the steps of the above method embodiments can be completed by the integrated logic circuit in the hardware of the processor or the instructions in the form of software. The above processor may 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, discrete hardware components. It can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. The steps of the method disclosed in combination with the embodiments of the present application can be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor. The software module may be located in a mature storage medium in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc. This storage medium is located in the memory, and the processor reads the information in the memory and combines its hardware to complete the steps of the above method.

[0306] It can be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a 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 dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchlink dynamic random access memory (SLDRAM), and direct rambus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include but not be limited to these and any other suitable types of memory.

[0307] It should be understood that the above-mentioned memory is by way of example but not limitation. For example, the memory in the embodiments of the present application can also be a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDR SDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synch link dynamic random access memory (SLDRAM), and a direct rambus random access memory (DR RAM), etc. That is to say, the memory in the embodiments of the present application is intended to include but not be limited to these and any other suitable types of memory.

[0308] The embodiments of the present application also provide a computer-readable storage medium for storing a computer program.

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

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

[0311] The embodiments of the present application also provide a computer program product including computer program instructions.

[0312] Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, it will not be elaborated here.

[0313] Optionally, the computer program product can be applied to the mobile terminal / terminal device in the embodiments 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 various methods of the embodiments of the present application. For the sake of brevity, it will not be elaborated here.

[0314] The embodiments of the present application also provide a computer program.

[0315] Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program runs on the computer, it enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, it will not be elaborated here.

[0316] Optionally, the computer program can be applied to the mobile terminal / terminal device in the embodiments of the present application. When the computer program runs on the computer, it enables the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, it will not be elaborated here.

[0317] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in connection with the embodiments disclosed herein can be implemented in electronic hardware, or in a combination of computer software and electronic hardware. Whether these functions are executed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may use different methods for each specific application to implement the described functions, but such implementation should not be considered to exceed the scope of this application.

[0318] Those skilled in the art can clearly understand that for the convenience and brevity of description, the specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments and will not be elaborated herein.

[0319] In several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is only a logical function division, and there may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed couplings or direct couplings or communication connections to each other can be through some interfaces, and the indirect couplings or communication connections of the devices or units can be in electrical, mechanical, or other forms.

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

[0321] In addition, the functional units in each embodiment of this application can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit.

[0322] When the above-mentioned functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. With such an understanding, the technical solution of this application, in essence, or the part that contributes to the prior art or a part of this 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 for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application. The aforementioned storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard disks, read-only memories (ROMs), random access memories (RAMs), magnetic disks, or optical discs.

[0323] As described above, the above are only specific implementation manners of this application, but the protection scope of this application is not limited thereto. Any person skilled in the art within the technical scope disclosed by this application can easily think of changes or substitutions, which should all be covered by the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

1. A wireless communication method, characterized in that, it includes: A terminal device sends first slice-related information to a network device, including: the terminal device performs random access using a random access parameter value corresponding to the first slice-related information; wherein, the first slice-related information is carried in the random access process; wherein, different first slice-related information corresponds to different random access resources, and different random access resources correspond to different random access parameter values; The first slice-related information is used to indicate the network slices supported by the terminal device; wherein, the random access parameter value includes: a backoff parameter value and / or a power ramp parameter value, and the backoff parameter value and / or the power ramp parameter value includes an absolute value, a relative value or an adjustment value.

2. The method according to claim 1, characterized in that, the first slice-related information is carried in message Msg 3 or Msg A in the random access process; or, different first slice-related information corresponds to different Msg 3 sizes or different Msg A sizes in the random access process.

3. The method according to claim 1, characterized in that, the random access resources include at least one of the following: random access preambles, time domain resources of a physical random access channel, frequency domain resources, and code domain resources.

4. The method according to claim 1, characterized in that, the first slice-related information is further used to indicate the network slices supported by the terminal device.

5. The method according to any one of claims 1-4, characterized in that, it further includes: the terminal device receives access control information sent by the network device.

6. The method according to claim 5, characterized in that, it further includes at least one of the following: the terminal device determines a random access result according to the access control information; the terminal device performs random access according to the access control information; the terminal device determines cell selection or cell reselection information according to the access control information; the terminal device performs cell selection or cell reselection according to the access control information; the terminal device determines the RRC state according to the access control information.

7. The method according to claim 5, characterized in that, the access control information includes at least one of the following: the network slices supported by the serving cell of the network device; the network slices supported by the neighboring cells of the serving cell; identifiers of at least one network slice; priorities of at least one network slice; correspondence relationships between at least one frequency point and at least one network slice; correspondence relationships between at least one cell and at least one network slice; frequency point priorities of at least one frequency point corresponding to at least one network slice; cell priorities of at least one cell corresponding to at least one network slice; correspondence relationships between at least one random access resource and at least one network slice; correspondence relationships between at least one random access parameter value and at least one network slice; correspondence relationships between at least one random access parameter value and at least one random access resource.

8. A wireless communication method, characterized in that, it includes: The network device receives the first slice-related information sent by the terminal device, including: obtaining the first slice-related information during the process that the terminal device performs random access using the random access parameter value corresponding to the first slice-related information; Wherein, the first slice-related information is carried during the random access process, and different first slice-related information corresponds to different random access resources, and different random access resources correspond to different random access parameter values; The first slice-related information is used to indicate the network slice supported by the terminal device; Wherein, the random access parameter value includes: a backoff parameter value and / or a power ramping parameter value, and the backoff parameter value and / or the power ramping parameter value includes an absolute value, a relative value or an adjustment value.

9. The method according to claim 8, characterized in that, the first slice-related information is carried in Msg 3 or Msg A during the random access process; Or, different first slice-related information corresponds to different Msg 3 sizes or different Msg A sizes during the random access process.

10. The method according to claim 8 or 9, characterized in that, further comprising: the network device sends access control information to the terminal device.

11. The method according to claim 10, characterized in that, further comprising at least one of the following: The access control information is used to determine the random access result; The access control information is used for the terminal device to perform random access; The access control information is used to determine information on cell selection or cell reselection; The access control information is used for the terminal device to perform cell selection or cell reselection; The access control information is used to determine the RRC state.

12. The method according to claim 11, characterized in that, the access control information includes at least one of the following: The network slice supported by the serving cell of the network device; The network slice supported by the neighboring cell of the serving cell; The identifier of at least one network slice; The priority of at least one network slice; The correspondence between at least one frequency point and at least one network slice; The correspondence between at least one cell and at least one network slice; The frequency point priority of at least one frequency point corresponding to at least one network slice; The cell priority of at least one cell corresponding to at least one network slice; The correspondence between at least one random access resource and at least one network slice; The correspondence between at least one random access parameter value and at least one network slice; The correspondence between at least one random access parameter value and at least one random access resource.

13. The method according to claim 8 or 9, characterized in that, further comprising: The network device sends a random access parameter value to the terminal device.

14. The method according to claim 8, characterized in that, the first slice-related information is further used to indicate the network slice supported by the terminal device.

15. A terminal device, characterized in that, comprising: A communication unit, configured to send first slice-related information to a network device, including: performing random access using the random access parameter value corresponding to the first slice-related information; Among them, the first slice-related information is carried during the random access process; different first slice-related information corresponds to different random access resources, and different random access resources correspond to different random access parameter values; The first slice-related information is used to indicate the network slice supported by the terminal device; Among them, the random access parameter values include: a fallback parameter value and / or a power ramp parameter value, and the fallback parameter value and / or the power ramp parameter value include an absolute value, a relative value, or an adjustment value.

16. A network device Characterized in that It includes: A communication unit, configured to receive first slice-related information sent by a terminal device, including: obtaining the first slice-related information during the process in which the terminal device performs random access using the random access parameter value corresponding to the first slice-related information; Among them, the first slice-related information is carried during the random access process, and different first slice-related information corresponds to different random access resources, and different random access resources correspond to different random access parameter values; The first slice-related information is used to indicate the network slice supported by the terminal device; Among them, the random access parameter values include: a fallback parameter value and / or a power ramp parameter value, and the fallback parameter value and / or the power ramp parameter value include an absolute value, a relative value, or an adjustment value.

17. A terminal device Characterized in that It includes: A processor and a memory, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method according to any one of claims 1 to 8.

18. A network device Characterized in that It includes: A processor and a memory, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method according to any one of claims 8 to 14.

Images