Wireless communication method, terminal device and network device

Abstract

The embodiment of the invention relates to a communication method, terminal equipment and network equipment, which can meet the requirement that the terminal equipment performs a series of actions with relatively low time delay. The method comprises: a terminal device receiving first information, the first information being used for indicating at least one piece of slice information supported by a target cell; and the terminal device determines target slice information based on the at least one piece of slice information.

Description

[0001] This application is a divisional application of the patent application filed on July 8, 2022, with application number 202080093860.8 and application name “Wireless Communication Method, Terminal Device and Network Device”. Technical Field

[0002] The present application relates to the field of communications, and in particular to a wireless communication method, terminal equipment and network equipment. Background Art

[0003] The new radio (NR) system (also called 5G system, 5G network) has high requirements for latency. For example, ultra-reliable and low-latency (uRLLC) scenarios (such as autonomous driving, remote surgery, industrial control, etc.) need to support ultra-low latency of 1ms.

[0004] When a terminal device performs certain actions, such as accessing a cell, it also needs to access the cell with a low latency. Therefore, how a terminal device can perform certain actions (such as accessing a cell) with a low latency is an urgent problem to be solved. Summary of the invention

[0005] The embodiments of the present application provide a wireless communication method, terminal device, and network device, which can meet the requirements of the terminal device to perform a series of actions with a lower delay.

[0006] In a first aspect, a method for wireless communication is provided, the method comprising: a terminal device receiving first information, where the first information is used to indicate at least one slice information supported by a target cell;

[0007] The terminal device determines target slice information based on the at least one slice information.

[0008] In a second aspect, a method for wireless communication is provided, the method comprising: a network device sends first information to a terminal device, the first information being used to indicate at least one slice information supported by a target cell.

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

[0010] Specifically, the terminal device includes a functional module for executing the method in the above-mentioned first aspect or its various implementation modes.

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

[0012] Specifically, the network device includes a functional module for executing the method in the above-mentioned second aspect or its various implementation modes.

[0013] In a fifth aspect, a terminal device is provided, comprising a processor and a memory, wherein 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 implementation manners.

[0014] In a sixth aspect, a network device is provided, comprising a processor and a memory, wherein 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 implementation manners.

[0015] In a seventh aspect, a chip is provided for implementing the method in any one of the first to second aspects or in each of their implementations.

[0016] Specifically, the chip includes: a processor for calling and running a computer program from a memory, so that a device equipped with the chip executes a method as described in any one of the first to second aspects or in each of their implementations.

[0017] In an eighth aspect, a computer-readable storage medium is provided for storing a computer program, wherein the computer program enables a computer to execute the method of any one of the first to second aspects or any of their implementations.

[0018] In a ninth aspect, a computer program product is provided, comprising computer program instructions, which enable a computer to execute the method in any one of the first to second aspects or their respective implementations.

[0019] In a tenth aspect, a computer program is provided, which, when executed on a computer, enables the computer to execute the method in any one of the first to second aspects or in each of their implementations.

[0020] In the above technical solution, the network device indicates the slice information supported by the target cell to the terminal device, so that the terminal device can quickly obtain the slice information supported by the target cell and determine the target slice information, so that subsequent actions can be performed based on the target slice information with a smaller delay, which can meet the requirements of the terminal device to perform a series of actions with a lower delay. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1 It is a schematic diagram of a communication system architecture according to an embodiment of the present application.

[0022] Figure 2 It is a schematic flowchart of a wireless communication method according to an embodiment of the present application.

[0023] Figure 3 It is a schematic flowchart of a four-step random access process according to an embodiment of the present application.

[0024] Figure 4 It is a schematic flowchart of a two-step random access process according to an embodiment of the present application.

[0025] Figure 5 It is a schematic block diagram of a terminal device according to an embodiment of the present application.

[0026] Figure 6 It is a schematic block diagram of a network device according to an embodiment of the present application.

[0027] Figure 7 It is a schematic block diagram of a communication device according to an embodiment of the present application.

[0028] Figure 8 is a schematic block diagram of a chip according to an embodiment of the present application.

[0029] Fig. 9 It is a schematic block diagram of a communication system according to an embodiment of the present application. Specific embodiments

[0030] The following will describe the technical solutions in the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0031] First, we introduce the application scenario of this application. Figure 1 is a schematic diagram of a communication system suitable for the present application.

[0032] The communication system 100 includes a network device 110 and a terminal device 120. The terminal device 120 communicates with the network device 110 via electromagnetic waves.

[0033] In the present application, the terminal device 120 may include various handheld devices, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to a wireless modem with wireless communication functions, for example, user equipment (UE) defined by the 3rd Generation Partnership Project (3GPP), mobile station (MS), soft terminal, home gateway, set-top box, etc.

[0034] The network device 110 may be a base station defined by 3GPP, for example, a base station (gNB) in a 5G mobile communication system. The network device 110 may also be a non-3GPP access network device, such as an access gateway (AG). The network device 110 may also be a relay station, an access point, an in-vehicle device, a wearable device, and other types of devices.

[0035] Optionally, terminal devices 120 may perform device-to-device (D2D) communication with each other.

[0036] Optionally, the 5G system or 5G network may also be referred to as a New Radio (NR) system or NR network.

[0037] The communication system 100 is only an example, and the communication system applicable to the present application is not limited thereto. For example, the number of network devices and terminal devices included in the communication system 100 may also be other numbers.

[0038] It should be understood that the device with communication function in the network / system in the embodiment of the present application can be referred to as a communication device. Figure 1 Taking the communication system 100 shown as an example, the communication equipment may include a network device 110 and a 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 repeated here. The communication equipment may also include other devices in the communication system 100, such as a network controller, a mobile management entity and other network entities, which is not limited in the embodiments of the present application.

[0039] It should also be understood that Figure 1 The communication system 100 shown can also be a non-terrestrial communication network (NTN) system, that is, Figure 1 The network device 110 in may be a satellite.

[0040] It should be understood that the terms "system" and "network" are often used interchangeably herein.

[0041] The strong demand for wireless communications in vertical markets is obvious to all. In order to meet the needs of vertical industries for latency, mobility, reliability, location accuracy, etc., RAN needs to enhance how to support vertical industries in the access network. Among them, one way to enhance the access network in supporting vertical industries is to provide lower latency, more targeted, greater flexibility and higher scalability services for multiple services with different needs based on slicing. More specifically, RAN slicing allows application providers to participate in the design, deployment and operation of customized RAN to better support the business of application providers. Therefore, Release 17 (Rel-17) introduced access network enhancements to slicing.

[0042] It should be understood that in the embodiments of the present application, slicing may also be referred to as network slicing.

[0043] To facilitate understanding of the embodiments of the present application, slicing is briefly introduced below.

[0044] In 5G, diverse business needs have different requirements for network speed, performance, security, reliability, latency, etc. For example, enhanced mobile broadband (eMBB) scenarios (such as virtual reality, augmented reality, etc.) have high bandwidth requirements and require xGbps bandwidth. For another example, massive machine type communication (mMTC) scenarios (such as wearable scenarios, smart grids, etc.) need to support massive device access, such as supporting hundreds of millions or billions of ultra-low latency device access. For another example, uRLLC scenarios (such as autonomous driving, remote surgery, industrial control, etc.) need to support ultra-low latency of 1ms. Faced with different scenarios, different requirements and the need for the ultimate experience, slicing came into being. It can flexibly build networks with different characteristics based on 5G scenarios and needs.

[0045] Slicing is a network deployed on physical or virtual infrastructure to support logical isolation of specific network capabilities and network characteristics. It can include a complete end-to-end network including access network, transmission network, core network and application server. Some network functions can also be shared among multiple slices. Slicing can also be any combination of terminal equipment, access network, transmission network, core network and application server.

[0046] Generally, different slices have different network characteristics and are required to be isolated from each other and not affect each other. For example, slices for augmented reality (AR) or virtual reality (VR) services require large bandwidth and low latency; slices for Internet of Things (IOT) services need to support the access of massive terminal devices, but have low bandwidth and no latency requirements.

[0047] Figure 2 It is a schematic flowchart of a wireless communication method 200 according to an embodiment of the present application. Figure 2 The method described above can be executed by a terminal device and a network device. For example, the terminal device can be Figure 1 The terminal device 120 shown in FIG. 1 may be, for example, Figure 1 The network device 110 shown in FIG. Figure 2 As shown, the method 200 may include at least part of the following contents.

[0048] In 210, the terminal device receives first information, where the first information is used to indicate at least one slice information supported by the target cell.

[0049] Accordingly, the network device may send the first information to the terminal device.

[0050] In 220, the terminal device determines target slice information based on at least one slice information.

[0051] Among them, the target cell can be a resident cell or a service cell, and the target slice information is the slice information of the target cell.

[0052] The slice information may include but is not limited to at least one of the following: network slice selection assistance information (NSSAI), slice type (slice type), service type (Service type), slice identifier, target cell identifier, target cell frequency, public land mobile network (public land mobile network, PLMN) identifier, and tracking area (tracking area, TA) identifier.

[0053] Exemplarily, NSSAI may be, for example, single network slice selection assistance information (S-NSSAI), and the identifier of the target cell may be the ID of the target cell, wherein the ID of the target cell may be a cell global identifier (CGI). It should be understood that the CGI mentioned here may be an evolved universal terrestrial radio access network (E-UTRAN) CGI (ECGI), or it may be an NR CGI (NCGI).

[0054] After the terminal device determines the target slice information, it can access the network or perform random access based on the target slice information. For example, the terminal device can access the target cell based on the target slice information.

[0055] In this technical solution, the network device indicates the slice information supported by the target cell to the terminal device, so that the terminal device can quickly obtain the slice information of the target cell, and thus the terminal device can quickly select a suitable cell or resource based on the slice information, avoiding the delay in the terminal device accessing the network and the delay in business services.

[0056] The following will be combined Figure 3 and Figure 4 Briefly introduce the random access process.

[0057] The random access process can usually be triggered by the following events:

[0058] (1) Initial Access

[0059] The terminal device can enter the RRC connected state (RRC_CONNECTED) from the Radio Resource Control (RRC) idle state (RRC_IDLE state).

[0060] (2)RRC Connection Re-establishment procedure

[0061] (3)Handover.

[0062] At this point, the terminal device is in a connected state and needs to establish uplink synchronization with the new cell.

[0063] (4) In RRC_CONNECTED state, when DL or UL data arrives, the uplink is in the "non-synchronised" state (DL or UL data arrival during RRC_CONNECTED when UL synchronisation status is "non-synchronised").

[0064] (5) In the RRC connected state, when uplink data arrives, 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).

[0065] (6)SR failure.

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

[0067] (8) The terminal device transitions from the RRC inactive state (Transition from RRC_INACTIVE).

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

[0069] (10) The terminal device requests other system information (OSI).

[0070] (11) The terminal device needs to perform beam failure recovery.

[0071] In the NR system, two random access methods can be supported: Figure 3 The following briefly describes the four-step random access process based on contention:

[0072] Step 1: The terminal device sends a random access preamble (Preamble, also known as message 1, Msg1) to the network device.

[0073] Among them, the random access preamble may also be called a preamble, a random access preamble sequence, a preamble sequence, etc.

[0074] Specifically, the terminal device can select a physical random access channel (PRACH) resource, which can include time domain resources, frequency domain resources, and code domain resources. Next, the terminal device can send the selected Preamble on the selected PRACH resource. The network device can estimate the transmission delay between it and the terminal device based on the Preamble and calibrate the uplink timing, and can roughly determine the size of the resources required for the terminal device to transmit Message 3 (Msg3).

[0075] Step 2: The network device sends a random access response (Random Access Response, RAR, also known as message 2, Msg2) to the terminal device.

[0076] After the terminal device sends the Preamble to the network device, it can open a RAR window, in which the corresponding Physical Downlink Control Channel (PDCCH) is detected according to the Random Access Radio Network Temporary Identifier (RA-RNTI). If the terminal device detects the PDCCH scrambled by the RA-RNTI, it can obtain the Physical Downlink Shared Channel (PDSCH) scheduled by the PDCCH. The PDSCH includes the RAR corresponding to the Preamble.

[0077] If the RAR returned by the network device is not received within the RAR window, the terminal device may consider that the random access process has failed. It should be understood that both the terminal device and the network device need to uniquely determine the value of RA-RNTI, otherwise the terminal device cannot decode the RAR.

[0078] Optionally, in the embodiment of the present application, the RA-RNTI value can be calculated by the time-frequency position of the Preamble that is clear to both the sender and the receiver. For example, the RA-RNTI associated with the Preamble can be calculated by formula (1):

[0079] RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id (1)

[0080] Among them, s_id is the index of the first orthogonal frequency division multiplexing (Orthogonal Frequency Division Multiplexing, OFDM) symbol of the PRACH resource (0≤s_id<14), t_id is the index of the first time slot of the PRACH resource in a system frame (0≤t_id<80), f_id is the index of the PRACH resource in the frequency domain (0≤f_id<8), and ul_carrier_id is the uplink carrier used to transmit the Preamble (0 indicates NUL carrier, 1 indicates SUL carrier). For FDD, there is only one PRACH resource per subframe, so f_id is fixed to 0.

[0081] In other words, since the time-frequency position of the Preamble sent by the terminal device is determined, the network device also obtains the time-frequency position of the Preamble when decoding the Preamble, and can then know the RA-RNTI that needs to be used in the RAR. When the terminal device successfully receives a RAR (decoded using a determined RA-RNTI), and the Random Access Preamble Identifier (RAPID) in the RAR is the same as the Preamble index sent by the terminal device, it can be considered that the RAR has been successfully received, and the terminal device can stop detecting the PDCCH encrypted with RA-RNTI.

[0082] Step 3: The terminal device sends Msg3.

[0083] 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 code index for verification. After determining that it is its own RAR message, it can generate Msg3 at the RRC layer and send Msg3 to the network device, which needs to carry the identification information of the terminal device.

[0084] Msg3 is mainly used to notify the network device of the triggering event of the random access. For different random access triggering events, the Msg3 sent by the terminal device in step 3 may include different contents.

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

[0086] For another example, for an RRC connection reestablishment scenario, Msg3 may include an RRC connection reestablishment request message (RRC Reestabilshment Request) generated by the RRC layer. In addition, Msg3 may also carry, for example, a Cell Radio Network Temporary Identifier (C-RNTI) and the like.

[0087] For another example, for a handover scenario, Msg3 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, Msg3 may also carry information such as a buffer status report (BSR). For other triggering events such as the arrival of uplink / downlink data, Msg3 may at least include the C-RNTI of the terminal device.

[0088] Step 4: The network device sends a contention resolution message, namely Msg4, to the terminal device.

[0089] The network device sends Msg4 to the terminal device, and the terminal device correctly receives Msg4 to complete contention resolution. For example, in the RRC connection establishment process, Msg4 can carry the RRC connection establishment message.

[0090] Since the terminal device in step 3 can carry its own unique identifier in Msg3, 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 won the contention. Other terminal devices that did not win the contention resolution will re-initiate random access.

[0091] It should be understood that in the embodiment of the present application, there are two ways to resolve contention conflicts:

[0092] Method 1: If the terminal device carries C-RNTI in Msg3, Msg4 can be scheduled with PDCCH scrambled by C-RNTI.

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

[0094] The delay of four-step random access is relatively large, which is not suitable for low-latency and high-reliability scenarios in 5G. Considering the characteristics of low-latency and high-reliability related services, a two-step random access process is proposed. Figure 5 As shown, in the two-step random access process, simply speaking, it is equivalent to combining the first step and the third step of the four-step random access process into the first step of the two-step random access process, and combining the second step and the fourth step of the four-step random access process into the second step of the two-step random access process.

[0095] More specifically, the two-step random access process may include:

[0096] Step 1: The terminal device sends a first message to the network device.

[0097] Among them, the first message can be composed of a Preamble and a payload, the Preamble is a Preamble of a four-step random access, the Preamble is transmitted on a PRACH resource, and the Payload mainly carries the information in Msg3 in the four-step random access. For example, it may include a CCCH SDU, such as corresponding to random access in an RRC idle state, and it may also include a C-RNTI Media Access Control (MAC) control element (CE), such as mainly corresponding to random access in an RRC connected state. The Payload can be carried on an uplink channel, which may be, for example, a Physical Uplink Shared Channel (PUSCH).

[0098] It should be understood that the first message may carry part or all of the information carried in the Preamble and Msg3 in the four-step random access process.

[0099] Step 2: The network device sends a second message to the terminal device.

[0100] If the network device successfully receives the first message sent by the terminal device, it can send a second message to the terminal device. The second message may include part or all of the information carried in Msg2 and Msg4 in the four-step random access process. The names of the first message and the second message are not limited, that is, they can also be expressed as other names. For example, the first message can also be called Msg A, a random access request message or a new Msg1, and the second message can also be called Msg B or a new Msg2.

[0101] It should also be understood that Figure 4 It is only a specific implementation of the two-step random access process and should not limit the protection scope of this application.

[0102] In an embodiment of the present application, as an example, the network device may broadcast the first information through system information, so that the terminal device may receive the first information.

[0103] As another example, the network device may send the first information to the terminal device through a random access process. For example, the network device may send the first information to the terminal device through a RAR in a four-step random access process, or the network device may send the first information to the terminal device through a second message in a two-step random access process.

[0104] It should be noted that if the first information is carried in the RAR in the four-step random access process, the format of the RAR carrying the first information may be different from the current RAR format. Further, the network device may use a new RNTI to scramble the RAR to distinguish the existing RAR from the RAR carrying the first information.

[0105] Alternatively, the RAR carrying the first information may include an M-bit distinction field to distinguish the RAR of the present application from the RAR in the prior art, where M is greater than or equal to 1.

[0106] If the first information is carried in the second message in the two-step random access process, the implementation method of the second message may refer to the implementation method of the above RAR, which will not be described here for the sake of brevity.

[0107] In one implementation, the terminal device accesses the network or performs random access based on the target slice information, which may specifically include: the terminal device may determine the target random access parameters corresponding to the target slice information, and then perform random access based on the target random access parameters.

[0108] In a possible embodiment, the terminal device may determine the target random access parameter based on the target slice information and the correspondence between the slice information and the random access parameter.

[0109] Optionally, the first information can also be used to indicate the correspondence between the slice information and the random access parameter. That is, when the network device indicates at least one slice information to the terminal device, it also indicates to the terminal device the random access parameter corresponding to each slice information in the at least one slice information. Alternatively, when the network device indicates the random access parameter to the terminal device, it also indicates to the terminal device at least one slice information corresponding to the random access parameter.

[0110] Optionally, the correspondence between slice information and random access parameters can be preset on the terminal device.

[0111] The random access parameters may include but are not limited to at least one of the following: L1 parameters, L2 parameters, and random access resources. The L1 parameters and L2 parameters are at least one of the parameters in RACH-configCommon, RACH-ConfigDedicated, and RACH-ConfigGeneri, and the random access resources may include at least one of the following: Preamble, PRACH resources, and rsrp-ThresholdSSB.

[0112] After the terminal device determines the target random access parameters, the terminal device can select a random access resource to perform a random access process. For example, if the slicing type indicated by the target slice information is TSC1, and the random access resource corresponding to TSC1 is Preamble5-7, the terminal device can select Preamble5 to initiate a random access process.

[0113] Accordingly, the network device can determine the target slice information determined by the terminal device through random access parameters, or according to the correspondence between the random access parameter parameters and the target slice information, so that the network device can select the corresponding access management function (Access Management Function, AMF) according to the target slice information to establish a service session with the terminal device.

[0114] In another implementation, the terminal device accesses the network or performs random access based on the target slice information, which may include: the terminal device accesses the network or performs random access based on the target slice information and parameters for access control (slicing-specific access control parameters).

[0115] Accordingly, the network device can control the slice information-based access network or random access of the terminal device based on the parameters used for access control.

[0116] It should be noted that if the slicing-specific access control check is required or indicated by the higher layer, the terminal device can also report the result of the access attempt to the higher layer when accessing the network based on the slicing information or performing random access, such as whether the access type is barred.

[0117] Among them, for the target cell, the slicing-specific access control parameters may include at least one of the following parameters: a barring parameter (slicing-specificcellbarred) corresponding to at least one slice information, a unified access control (Unified Access Control, UAC) parameter (slicing-specific uac-BarringInfo) corresponding to at least one slice information, and an access priority parameter corresponding to at least one slice information.

[0118] The bar parameter corresponding to at least one slice information can be understood as: the bar parameter configured for the slicing indicated by at least one slice information; the UAC parameter corresponding to at least one slice information can be understood as: the UAC parameter indicating the slicing indicated by at least one slice information; the access priority parameter corresponding to at least one slice information can be understood as: the parameter used to indicate the priority of the slicing indicated by at least one slice information.

[0119] Optionally, the first information may also be used to indicate a slicing-specific access control parameter.

[0120] It should be understood that in the embodiment of the present application, if the priorities of different slicings are different, the UAC parameters of different slicings may be different and / or the backoff indicator (BI) values ​​used for random access may be different.

[0121] It should also be understood that the embodiments of the present application do not specifically limit the names of the bar parameter, UAC parameter, and access priority parameter. For example, the bar parameter may also be referred to as bar information, the UAC parameter may also be referred to as UAC information, and the access priority parameter may also be referred to as access priority information.

[0122] The BI value specifies the time range that the terminal device needs to wait before resending the Preamble. If the terminal device does not receive the RAR within the RAR window, or none of the RAPIDs in the received RAR matches the preamble index selected by the terminal device, the terminal device can consider that the RAR reception has failed. At this time, the terminal device needs to wait for a period of time before initiating random access. The waiting time can be any random value in the waiting time interval between 0 and the BI value.

[0123] Regarding bar parameters, the bar parameters corresponding to different slice information may be the same or different. That is, the bar parameters corresponding to at least one slice information may be the same, partially the same, or completely different. That is, the network device may set the corresponding bar parameters for each slicing.

[0124] For example, the network device may configure a bar parameter for slicing X. If the bar parameter configured by the network device for slicing X is cell bar for slicing X, it means that the access of the terminal device based on slicing X is barred.

[0125] Of course, the network device can also set the bar parameter corresponding to the slicing information for the terminal device. For example, if the bar parameter configured by the network device is cell bar for non slicing, the network device can bar the terminal device that does not support slicing. That is to say, if the bar parameter is a parameter that prohibits terminal devices that do not support slicing, the network device can prohibit terminal devices that do not support slicing from accessing the network or performing random access. Specifically, when a specific slicing is congested or is about to be congested, the network device can use a proprietary message element (Information Element, IE) (such as cellReservedForOtherUse) to bar the terminal device that does not support slicing. If cellReservedForOtherUse is set to true, the network device can bar the terminal device that does not support slicing.

[0126] Regarding the UAC parameter, the possible values ​​of the UAC parameter can be 0, 1, 2...x. For example, x can be 13 or 11 or other values, which are not limited in the embodiments of the present application. Among them, different values ​​can correspond to different services. For the convenience of description, the value of the UAC parameter is referred to as the threshold value below. Of course, the value of the UAC parameter can also be called an access factor or other names.

[0127] As an example, if the threshold value corresponding to the target slice information is 0, the terminal device can access the network or perform random access.

[0128] As another example, the terminal device may select a random number, and then the terminal device may access the network or perform random access control according to the random number and a threshold value.

[0129] Specifically, if the random number is less than or equal to the threshold value, the terminal device may access the network or perform random access; if the random number is greater than the threshold value, the terminal device may not access the network or perform random access.

[0130] If the terminal device does not access the network or does not perform random access, the terminal device can re-access the network according to the priority of the slicing (for the convenience of description, referred to as target slicing) indicated by the target slicing information and / or the BI value corresponding to the target slicing.

[0131] It should be understood that the term "and / or" in this article is merely a description of the association relationship between associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone.

[0132] For example, the network device indicates two slicing information, which respectively indicate slicing1 and slicing2, where the threshold value of slicing1 is 0.5 and the threshold value of slicing2 is 1. The terminal device determines slicing1 as the target slicing. If the random number randomly selected by the terminal device is 0.3, since 0.3 is less than 0.5, the terminal device can access the network. If the random number randomly selected by the terminal device is 0.9, since 0.9 is greater than 0.5, the terminal device does not access the network.

[0133] For another example, the network device indicates two slicing information, which respectively indicate slicing1 and slicing2, wherein the threshold value of slicing1 is 0.5, and the BI value corresponding to slicing1 is A, the threshold value of slicing2 is 1, and the BI value corresponding to slicing2 is B, and the terminal device determines slicing2 as the target slicing. If the random number randomly selected by the terminal device is 0.3, since 0.3 is less than 1, the terminal device can access the network. If the random number randomly selected by the terminal device is 1.2, since 1.2 is greater than 1, the terminal device does not access the network, and the terminal device can try to access the network again after backing off for B time.

[0134] For another example, the network device indicates two slicing information, which respectively indicate slicing1 and slicing2, wherein the threshold value of slicing1 is 0.5, the priority of slicing1 is H, the threshold value of slicing2 is 1, the priority of slicing2 is L, and the BI values ​​corresponding to slicing1 and slicing2 are both K. The terminal device determines slicing1 as the target slicing. If the random number randomly selected by the terminal device is 0.3, since 0.3 is less than 0.5, the terminal device can access the network. If the random number randomly selected by the terminal device is 1.2, since 1.2 is greater than 0.5, the terminal device does not access the network, and the terminal device can back off for H*K time before trying to access the network.

[0135] Regarding the access priority parameter, the terminal device can determine the priority order of the target slicing in at least one slicing based on the access priority parameter corresponding to at least one slice information. If the target slicing is the sliceing with the highest priority in at least one slicing, the terminal device can access the network or perform random access; if the target slicing is one of the N sliceings with the highest priority in at least one slicing, the terminal device can access the network or perform random access, where N is greater than or equal to 1.

[0136] In the above technical solution, the terminal device accesses the network or performs random access according to the access priority parameter of slicing, which can avoid cell access congestion, so that the terminal device supporting high-priority slicing can access the network first, ensuring the performance of the terminal device.

[0137] Optionally, the terminal device may also determine the target slice information according to the access priority parameter. Exemplarily, the terminal device may determine the slice information indicating the highest priority slicing in at least one slice information according to the access priority parameter, and then determine the slice information as the target slice information.

[0138] Optionally, in an embodiment of the present application, method 200 may further include: the terminal device determines a backoff indicator (BI) value for random access based on the target slice information.

[0139] Optionally, the priority of slicing indicated by the at least one slice information may be inversely proportional to the size of the BI value, that is, the higher the priority of slicing, the smaller the BI value.

[0140] For example, if the priority of the target slicing is the first priority, the terminal device may determine the BI value to be 0; if the priority of the target slicing is the second priority, the terminal device may determine the BI value to be B; if the priority of the target slicing is the third priority, the terminal device may determine the BI value to be A. Among them, B may be less than A.

[0141] Optionally, BI values ​​corresponding to at least some of the slices in the slices indicated by the at least one slice information may be different.

[0142] In this way, if the terminal device fails to access the network or perform random access, the terminal device can re-access the network or perform random access based on the BI value.

[0143] Optionally, method 200 may also include: the terminal device sends second information to the network device, and the second information can be used to indicate slice information supported or selected by the terminal device.

[0144] The second information may be carried in an RRC message. For example, the RRC message may be an RRC connection establishment request message, or the RRC message may be an RRC connection reestablishment request message, or the RRC message may be an RRC connection recovery message.

[0145] Alternatively, the second information may be carried in a random access procedure. Specifically, the second information may be carried in Msg1 or Msg3 in a four-step random access procedure, or the second information may be carried in a second message in a two-step random access procedure.

[0146] Optionally, the slice information supported or selected by the terminal device may belong to at least one slice information indicated by the first information. At this time, the slice information supported or selected by the terminal device may include target slice information.

[0147] Specifically, after receiving the first information, the terminal device obtains at least one slice information supported by the target cell, and then the terminal device selects the slice information supported by itself from the at least one slice information, and then indicates the supported or selected slice information to the network device through the second information. If there is only one slice information supported by the terminal device in the at least one slice information, the terminal device can determine the supported slice information as the target slice information.

[0148] If there are multiple slice information supported by the terminal device in the at least one slice information, the terminal device can send all the multiple slice information to the network device. After receiving the multiple slice information, the network device can select a slice information from the multiple slice information to determine as the target slice information, and then the network device indicates the selected target slice information to the terminal device. Alternatively, the terminal device can select a slice information from the multiple slice information as the target slice information, and indicate the target slice information to the network device through the second information.

[0149] It should be noted that in the embodiment of the present application, the network device may not send the first information to the terminal device, that is, it may not indicate the slice information supported by the target cell to the terminal device. The terminal device reports the slice information supported or selected by itself to the network device through the second information. After receiving the second information, the network device selects the appropriate AMF according to the slice information reported by the terminal device to establish a service session with the terminal device.

[0150] In this case, the slice information supported or selected by the terminal device may not be the slice information supported by the target cell. For example, if the slice information supported or selected by the terminal device indicates that the type of slicing is TSC1, and the resident cell does not support the slicing, the network device can bar the terminal device, and the terminal device can choose other cells to access.

[0151] It should be understood that in the embodiments of the present application, "first" and "second" are only used to distinguish different objects, but do not constitute a limitation on the scope of the embodiments of the present application.

[0152] The preferred embodiments of the present application are described in detail above in conjunction with the accompanying drawings; however, the present application is not limited to the specific details in the above embodiments. Within the technical concept of the present application, a variety of simple modifications can be made to the technical solution of the present application, and these simple modifications all fall within the protection scope of the present application.

[0153] For example, the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, this application will not further explain various possible combinations.

[0154] For another example, the various implementation modes of the present application may be arbitrarily combined, and as long as they do not violate the concept of the present application, they should also be regarded as the contents disclosed in the present application.

[0155] It should be understood that in the various method embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0156] The wireless communication method according to the embodiment of the present application is described in detail above. Figures 5 to 7 , describing a communication device according to an embodiment of the present application, the technical features described in the method embodiment are applicable to the following device embodiments.

[0157] Figure 5 FIG. 3 is a schematic block diagram of a terminal device 300 according to an embodiment of the present application. Figure 5 As shown, the terminal device 300 includes:

[0158] The communication unit 310 is used to receive first information, where the first information is used to indicate at least one slice information supported by the target cell.

[0159] The processing unit 320 is used for the terminal device to determine target slice information based on the at least one slice information.

[0160] Optionally, in an embodiment of the present application, the processing unit 320 is further used to: access the network or perform random access based on the target slice information.

[0161] Optionally, in an embodiment of the present application, the processing unit 320 is specifically used to: determine a target random access parameter corresponding to the target slice information; and perform random access based on the target random access parameter.

[0162] Optionally, in an embodiment of the present application, the first information is also used to indicate a random access parameter corresponding to the at least one slice information, and the processing unit 320 is specifically used to: determine the target random access parameter based on the target slice information and the random access parameter corresponding to the at least one slice information.

[0163] Optionally, in an embodiment of the present application, the target random access parameter includes a random access resource.

[0164] Optionally, in an embodiment of the present application, the processing unit 320 is specifically used to: access the network or perform random access based on the target slice information and parameters for access control.

[0165] Optionally, in this embodiment of the present application, the first information is also used to indicate the parameters used for access control.

[0166] Optionally, in an embodiment of the present application, for the target cell, the parameters used for access control include at least one of the following parameters: a prohibition parameter corresponding to the at least one slice information, a UAC parameter corresponding to the at least one slice information, and an access priority parameter corresponding to the at least one slice information.

[0167] Optionally, in an embodiment of the present application, among the parameters used for access control, the prohibited parameters corresponding to different slice information are different.

[0168] Optionally, in an embodiment of the present application, the processing unit 320 is specifically used to: if the value of the UAC parameter corresponding to the target slice information is 0, access the network or perform random access.

[0169] Optionally, in an embodiment of the present application, the processing unit 320 is specifically used to: select a random number; access the network or perform random access according to the UAC parameters corresponding to the random number and the target slice information.

[0170] Optionally, in an embodiment of the present application, the processing unit 320 is specifically used to: if the random number is less than or equal to the value of the UAC parameter, access the network or perform random access; if the random number is greater than the value of the UAC parameter, do not access the network or do not perform random access.

[0171] Optionally, in an embodiment of the present application, the processing unit 320 is specifically used to: determine the priority order of the target slice information in the at least one slice information according to the access priority parameter corresponding to the at least one slice information; if the target slice information is at least one of the N slice information with the highest priority in the at least one slice information, access the network or perform random access, and N is greater than or equal to 1.

[0172] Optionally, in an embodiment of the present application, the processing unit 320 is further used to: determine a fallback indication BI value for random access based on the target slice information.

[0173] Optionally, in an embodiment of the present application, the priority of the slice indicated by the at least one slice information is inversely proportional to the size of the BI value.

[0174] Optionally, in an embodiment of the present application, BI values ​​corresponding to at least some slices indicated by the at least one slice information are different.

[0175] Optionally, in an embodiment of the present application, the communication unit 310 is specifically used to: receive the first information broadcast by the network device through system information.

[0176] Optionally, in an embodiment of the present application, the communication unit 310 is specifically used to: receive the first information sent by the network device through a random access process.

[0177] Optionally, in an embodiment of the present application, the communication unit 310 is also used to: send second information to the network device, where the second information is used to indicate the slice information supported or selected by the terminal device.

[0178] Optionally, in an embodiment of the present application, the communication unit 310 is specifically used to: send the second information to the network device through a random access process.

[0179] Optionally, in an embodiment of the present application, the second information is carried in the first message in a two-step random access process, or in the first message or the third message in a four-step random access process.

[0180] Optionally, in an embodiment of the present application, the second information is carried in a radio resource control RRC message.

[0181] Optionally, in an embodiment of the present application, the at least one slice information includes at least one of the following: network slice selection auxiliary information NSSAI, slice type, service type, slice identifier, identifier of the target cell, frequency of the target cell, public land mobile network PLMN identifier, and tracking area TA identifier.

[0182] It should be understood that the terminal device 300 may correspond to the terminal device in the method 200 and may implement the corresponding operations of the terminal device in the method 200. For the sake of brevity, it will not be described in detail here.

[0183] Figure 6 FIG. 4 is a schematic block diagram of a network device 400 according to an embodiment of the present application. Figure 6 As shown, the network device 400 includes:

[0184] The communication unit 410 is used to send first information to the terminal device, where the first information is used to indicate at least one slice information supported by the target cell.

[0185] Optionally, in an embodiment of the present application, the network device 400 also includes: a processing unit 420, used to determine the target slice information determined by the terminal device based on the target random access parameters, the target slice information is used for the terminal device to access the network or perform random access, and the at least one slice information includes the target slice information.

[0186] Optionally, in an embodiment of the present application, the first information is also used to indicate a random access parameter corresponding to the at least one slice information, and the random access parameter corresponding to the at least one slice information includes the target random access parameter.

[0187] Optionally, in an embodiment of the present application, the target random access parameter includes a random access resource.

[0188] Optionally, in an embodiment of the present application, the first information is also used to indicate parameters for access control, and the network device 400 also includes: a processing unit 420, used to control the slice information-based access network or random access of the terminal device based on the parameters for access control.

[0189] Optionally, in an embodiment of the present application, for the target cell, the parameters used for access control include at least one of the following parameters: a prohibition parameter corresponding to the at least one slice information, a UAC parameter corresponding to the at least one slice information, and an access priority parameter corresponding to the at least one slice information.

[0190] Optionally, in an embodiment of the present application, among the parameters used for access control, the prohibited parameters corresponding to different slice information are different.

[0191] Optionally, in an embodiment of the present application, the processing unit 420 is also used to: if the prohibition parameter corresponding to the at least one slice information is a parameter that prohibits terminal devices that do not support slicing from accessing the network or performing random access, then the terminal devices that do not support slicing are prohibited from accessing the network or performing random access.

[0192] Optionally, in this embodiment of the present application, the communication unit 410 is specifically used to: broadcast the first information through system information.

[0193] Optionally, in an embodiment of the present application, the communication unit 410 is specifically used to: send the first information to the terminal device through a random access process.

[0194] Optionally, in an embodiment of the present application, the communication unit 410 is also used to: receive second information sent by the terminal device, and the second information is used to indicate slice information supported or selected by the terminal device.

[0195] Optionally, in an embodiment of the present application, the communication unit 410 is specifically used to: receive the second information sent by the terminal device through a random access process.

[0196] Optionally, in an embodiment of the present application, the second information is carried in the first message in a two-step random access process, or in the first message or the third message in a four-step random access process.

[0197] Optionally, in an embodiment of the present application, the second information is carried in a radio resource control RRC message.

[0198] Optionally, in an embodiment of the present application, the at least one slice information includes at least one of the following: network slice selection auxiliary information NSSAI, slice type, service type, slice identifier, identifier of the target cell, frequency of the target cell, public land mobile network PLMN identifier, and tracking area TA identifier.

[0199] It should be understood that the network device 400 may correspond to the network device in the method 200 and may implement corresponding operations of the network device in the method 200. For the sake of brevity, it will not be described in detail here.

[0200] Figure 7 It is a schematic structural diagram of a communication device 500 provided in an embodiment of the present application. Figure 7 The communication device 500 shown includes a processor 510, and the processor 510 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0201] Alternatively, if Figure 7 As shown, the communication device 500 may further include a memory 520. The processor 510 may call and run a computer program from the memory 520 to implement the method in the embodiment of the present application.

[0202] The memory 520 may be a separate device independent of the processor 510 , or may be integrated into the processor 510 .

[0203] Alternatively, if Figure 7 As shown, the communication device 500 may further include a transceiver 530, and the processor 5710 may control the transceiver 530 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices.

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

[0205] Optionally, the communication device 500 may specifically be a network device in an embodiment of the present application, and the communication device 500 may implement corresponding processes implemented by the network device in each method in the embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0206] Optionally, the communication device 500 may specifically be a terminal device of an embodiment of the present application, and the communication device 500 may implement the corresponding processes implemented by the terminal device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0207] Figure 8 It is a schematic structural diagram of the chip of an embodiment of the present application. Figure 8The chip 600 shown includes a processor 610, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0208] Alternatively, if Figure 8 As shown, the chip 600 may further include a memory 620. The processor 610 may call and run a computer program from the memory 620 to implement the method in the embodiment of the present application.

[0209] The memory 620 may be a separate device independent of the processor 610 , or may be integrated into the processor 610 .

[0210] Optionally, the chip 600 may further include an input interface 630. The processor 610 may control the input interface 630 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

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

[0212] Optionally, the chip can be applied to the terminal device in the embodiments of the present application, and the device can implement the corresponding processes implemented by the terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0213] Optionally, the chip can be applied to the network equipment in the embodiments of the present application, and the device can implement the corresponding processes implemented by the network equipment in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0214] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0215] It should be understood that the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by the hardware integrated logic circuit or software instructions in the processor. The above processor can be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or the hardware and software modules in the decoding processor are combined and performed. The software module can be located in a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, and other mature storage media in the art. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0216] 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 and 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), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

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

[0218] Fig. 9is a schematic block diagram of a communication system 700 provided in an embodiment of the present application. Fig. 9 As shown, the communication system 700 includes a terminal device 710 and a network device 720 .

[0219] Among them, the terminal device 710 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 720 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, they are not repeated here.

[0220] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

[0221] Optionally, the computer-readable storage medium can be applied to the terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0222] 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, they are not repeated here.

[0223] An embodiment of the present application also provides a computer program product, including computer program instructions.

[0224] Optionally, the computer program product can be applied to the 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 terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0225] 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, they are not repeated here.

[0226] The embodiment of the present application also provides a computer program.

[0227] Optionally, the computer program can be applied to the terminal device in the embodiments of the present application. When the computer program runs on the computer, the computer executes the corresponding processes implemented by the terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0228] Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the network device in the various methods in the embodiments of the present application. For the sake of brevity, they are not described here.

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

[0230] 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 aforementioned method embodiments and will not be repeated here.

[0231] In the several embodiments provided in the present 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 only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as 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 mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

[0233] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0234] If the 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. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0235] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A wireless communication method, characterized in that: The method comprises: The terminal device receives first information, where the first information is used to indicate at least one slice information supported by the target cell; The terminal device determines target slice information based on the at least one slice information; The terminal device accesses the network or performs random access based on the target slice information.

2. The method according to claim 1, characterized in that The terminal device accesses a network or performs random access based on the target slice information, including: The terminal device determines a target random access parameter corresponding to the target slice information; The terminal device performs random access based on the target random access parameter.

3. The method according to claim 2, characterized in that The first information is also used to indicate a random access parameter corresponding to the at least one slice information, and the terminal device determines a target random access parameter corresponding to the target slice information, including: The terminal device determines the target random access parameter based on the target slice information and the random access parameter corresponding to the at least one slice information.

4. The method according to claim 2 or 3, characterized in that: The target random access parameter includes a random access resource.

5. The method according to any one of claims 1 to 4, characterized in that The terminal device accesses a network or performs random access based on the target slice information, including: The terminal device accesses the network or performs random access based on the target slice information and the parameters for access control.

6. The method according to claim 5, characterized in that The first information is also used to indicate the parameter used for access control.

7. The method according to claim 5 or 6, characterized in that: For the target cell, the parameters used for access control include at least one of the following parameters: a prohibition parameter corresponding to the at least one slice information, a unified access control UAC parameter corresponding to the at least one slice information, and an access priority parameter corresponding to the at least one slice information.

8. The method according to claim 7, characterized in that The terminal device accesses a network or performs random access based on the target slice information and a parameter for access control, including: If the value of the UAC parameter corresponding to the target slice information is 0, the terminal device accesses the network or performs random access; or, The terminal device selects a random number; The terminal device accesses the network or performs random access according to the random number and the UAC parameter corresponding to the target slice information; or, The terminal device determines, according to the access priority parameter corresponding to the at least one slice information, a priority order of the target slice information in the at least one slice information; If the target slice information is at least one of the N slice information with the highest priority among the at least one slice information, the terminal device accesses the network or performs random access, and N is greater than or equal to 1.

9. The method according to any one of claims 1 to 8, characterized in that The method further comprises: The terminal device determines, according to the target slice information, a fallback indication BI value for random access; Among them, the BI values ​​corresponding to at least some slices indicated by the at least one slice information are different.

10. The method according to any one of claims 1 to 9, characterized in that The method further comprises: The terminal device sends second information to the network device, where the second information is used to indicate the slice information supported or selected by the terminal device.

11. The method according to any one of claims 1 to 10, characterized in that The at least one slice information includes at least one of the following: Network slice selection auxiliary information NSSAI, slice type, service type, slice identifier, identifier of the target cell, frequency of the target cell, public land mobile network PLMN identifier, and tracking area TA identifier.

12. A wireless communication method, characterized in that: The method comprises: The network device sends first information to the terminal device, where the first information is used to indicate at least one slice information supported by the target cell; The network device determines the target slice information determined by the terminal device according to the target random access parameter, the target slice information is used by the terminal device to access the network or perform random access, and the at least one slice information includes the target slice information.

13. The method according to claim 12, characterized in that The first information is also used to indicate the random access parameters corresponding to the at least one slice information, and the random access parameters corresponding to the at least one slice information include the target random access parameters.

14. The method according to claim 12 or 13, characterized in that The target random access parameter includes a random access resource.

15. A terminal device, characterized in that: include: A communication unit, configured to receive first information, where the first information is used to indicate at least one slice information supported by a target cell; A processing unit, configured for the terminal device to determine target slice information based on the at least one slice information; The processing unit is also used for: Based on the target slice information, access the network or perform random access.

16. A network device, characterized in that: include: A communication unit, configured to send first information to a terminal device, where the first information is used to indicate at least one slice information supported by a target cell; A processing unit is used to determine the target slice information determined by the terminal device according to the target random access parameter, the target slice information is used for the terminal device to access the network or perform random access, and the at least one slice information includes the target slice information.

17. A computer-readable storage medium, characterized in that: Used to store a computer program, the computer program causing a computer to execute the method according to any one of claims 1 to 11, or the computer program causing the computer to execute the method according to any one of claims 12 to 14.

Images