Method and apparatus for determining random access resource, communication device and storage medium

Abstract

The application discloses a random access resource determination method and device, communication equipment and a storage medium, and relates to the field of wireless communication. The method is applied to a terminal device, and comprises the following steps: receiving random access configuration information, wherein the random access configuration information is used for indicating that random access resources are allocated according to network slices or objects having a mapping relationship with the network slices; and determining random access resources according to the random access configuration information, wherein the random access resources match a target network slice to be accessed by the terminal device.

Description

[0001] This application is a divisional application of PCT International Patent Application No. PCT / CN2020 / 101963, filed on July 14, 2020, entitled “Method, Device, and Communication Equipment for Determining Random Access Resources” and entering the Chinese national phase as Chinese Patent Application No. 202080099990.2, entitled “Method, Device, and Communication Equipment for Determining Random Access Resources” and Storage Medium. TECHNICAL FIELD

[0002] The present application relates to the field of wireless communication, in particular to a method and device for determining random access resources, a communication equipment, and a storage medium. BACKGROUND

[0003] A terminal device needs to perform random access in scenarios such as sending uplink data, receiving downlink data, and performing tracking area update.

[0004] Random access is divided into two types: collision-based random access and collision-free random access. In the collision-based random access, multiple terminal devices may attempt to access a network on the same random access resource, resulting in random access collision between the terminal devices.

[0005] How to reduce the probability of random access collision when determining random access resources has not been properly addressed by related technologies. SUMMARY

[0006] Embodiments of the present application provide a method and device for determining random access resources, a communication equipment, and a storage medium. A network device sends random access configuration information to a terminal device to indicate the binding relationship between random access resources and network slices, so that the terminal device can select the corresponding random access resource according to the target network slice to be accessed when determining the random access resource according to the random access configuration information, thereby reducing the probability of collision. The technical solution is as follows.

[0007] According to an aspect of the present application, a method for determining random access resources is provided, which is applied to a terminal device and includes the following steps.

[0008] Receiving random access configuration information, the random access configuration information being used to indicate that random access resources are allocated according to network slices or objects having a mapping relationship with the network slices;

[0009] Determining random access resources according to the random access configuration information, the random access resources matching a target network slice to be accessed by the terminal device.

[0010] According to an aspect of the present application, a method for determining random access resources is provided, which is applied to a network device and includes the following steps.

[0011] transmit random access configuration information, the random access configuration information being used to indicate that random access resources are allocated according to network slices or objects having a mapping relationship with the network slices;

[0012] The random access configuration information is used for the terminal device to determine random access resources, and the random access resources match a target network slice to be accessed by the terminal device.

[0013] According to an aspect of the present application, a random access resource determination apparatus is provided, which comprises a receiving module and a determination module.

[0014] The receiving module is configured to receive random access configuration information, the random access configuration information being used to indicate that random access resources are allocated according to network slices or objects having a mapping relationship with the network slices.

[0015] The determination module is configured to determine random access resources according to the random access configuration information, and the random access resources match a target network slice to be accessed by the terminal device.

[0016] According to an aspect of the present application, a random access resource determination apparatus is provided, which comprises a transmitting module.

[0017] The transmitting module is configured to transmit random access configuration information, the random access configuration information being used to indicate that random access resources are allocated according to network slices or objects having a mapping relationship with the network slices.

[0018] The random access configuration information is used for the terminal device to determine random access resources, and the random access resources match a target network slice to be accessed by the terminal device.

[0019] According to an aspect of the present application, a terminal device is provided, which comprises a processor, a transceiver connected to the processor, and a memory for storing executable instructions of the processor, wherein the processor is configured to load and execute the executable instructions to implement the random access resource determination method according to the above aspect.

[0020] According to an aspect of the present application, a network device is provided, which comprises a processor, a transceiver connected to the processor, and a memory for storing executable instructions of the processor, wherein the processor is configured to load and execute the executable instructions to implement the random access resource determination method according to the above aspect.

[0021] According to an aspect of the present application, a computer readable storage medium is provided, the readable storage medium storing executable instructions, the executable instructions being loaded and executed by a processor to implement the method for determining random access resources according to the above aspect.

[0022] According to an aspect of the present application, a computer program product or computer program is provided, the computer program product or computer program comprising computer instructions stored in a computer readable storage medium, the computer instructions being read by a processor of a computer device, and the processor executing the computer instructions to cause the computer device to perform the method for determining random access resources according to the above aspect.

[0023] The technical solutions provided by the embodiments of the present application have at least the following beneficial effects:

[0024] The network device indicates the binding relationship between the random access resources and the network slices by sending the random access configuration information to the terminal device. Since the network device can flexibly allocate the random access resources according to different network slices, such as increasing the size of the random access resources corresponding to the key network slices / popular slice services, or decreasing the size of the random access resources corresponding to the ordinary network slices / less popular slice services, when the terminal device determines the random access resources according to the random access configuration information, the terminal device can select the corresponding random access resources according to the target network slice to be accessed, thereby reducing the probability of collision. BRIEF DESCRIPTION OF DRAWINGS

[0025] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed in the embodiment description will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative effort.

[0026] Figure 1 is a schematic diagram of a MAC PDU provided by an exemplary embodiment of the present application;

[0027] Figure 2 is a schematic diagram of a RAR provided by an exemplary embodiment of the present application;

[0028] Figure 3 is a schematic diagram of random access provided by an exemplary embodiment of the present application;

[0029] Figure 4 is a schematic diagram of data transmission provided by an exemplary embodiment of the present application;

[0030] Figure 5is a schematic diagram of random access resource partitioning based on synchronization signal blocks provided by an example embodiment of the present application.

[0031] Figure 6 is a block diagram of a communication system provided by an example embodiment of the present application.

[0032] Figure 7 is a flowchart of a method of determining random access resources provided by an example embodiment of the present application.

[0033] Figure 8 is a schematic diagram of slicing a preamble domain provided by an example embodiment of the present application.

[0034] Figure 9 is a schematic diagram of determining random access preambles provided by an example embodiment of the present application.

[0035] Figure 10 is a schematic diagram of slicing a random access time-frequency domain provided by an example embodiment of the present application.

[0036] Figure 11 is a schematic diagram of determining random access time-frequency resources provided by an example embodiment of the present application.

[0037] Figure 12 is a flowchart of a method of determining random access resources provided by an example embodiment of the present application.

[0038] Figure 13 is a block diagram of a device for determining random access resources provided by an example embodiment of the present application.

[0039] Figure 14 is a block diagram of a device for determining random access resources provided by an example embodiment of the present application.

[0040] Figure 15 is a block diagram of a communication device provided by an example embodiment of the present application. DETAILED DESCRIPTION

[0041] To make the objectives, technical solutions, and advantages of the present application clearer, the embodiments of the present application will be described in further detail below with reference to the drawings.

[0042] First, the terms involved in the embodiments of the present application will be briefly introduced.

[0043] Random access procedure:

[0044] A terminal device needs to perform random access in scenarios such as uplink data transmission, downlink data reception, and tracking area update. Random access is divided into two types: collision-based random access procedure and collision-free random access procedure.

[0045] In a collision-based random access procedure, a terminal device transmits msg1 using a common random access preamble on a random access time-frequency resource (RACH Occasion, RO). Afterwards, the terminal listens to the PDCCH for PDCCH indication information about a random access response (RAR) on the PDCCH using a random access RNTI (RA-RNTI). Refer to Figure 1 which shows a MAC protocol data unit (PDU) including a medium access control (MAC) RAR.

[0046] Upon detecting the PDCCH indication information about the RAR, the terminal device decodes the RAR at the time-frequency location indicated by the PDCCH indication information. If the RAR contains the random access preamble information transmitted by the terminal device, the terminal device then applies the information corresponding to the random access preamble in the RAR to transmit msg3. Refer to Figure 2 which shows a schematic diagram of a RAR. The RAR includes an uplink scheduling grant (UL Grant).

[0047] In msg3 containing a radio resource control (RRC) command such as RRCSetupRequest, the terminal device needs to carry its own UE ID. If there are many terminal devices performing random access, it is likely that other terminal devices will also transmit msg3 (carrying the UE ID of the terminal device) on the time-frequency location indicated by the UL Grant to attempt to access the network. In this case, random access collisions occur between the terminal devices, and the network device will only carry the ID of one of the terminal devices in msg4 to allow it to access the network.

[0048] Refer to Figure 3 . Terminal device 1 and terminal device 2 have random access collisions, terminal device 1 successfully performs random access, and terminal device 2 fails to perform random access.

[0049] Network slice:

[0050] A network slice is composed of a Radio Access Network (RAN) part and a Core Network (CN) part. The support of network slices by a communication network relies on carrying data communications belonging to different network slices by different protocol data unit sessions (PDU sessions). In implementation, a network carries the traffic of enhanced Mobile Broadband (eMBB) and Ultra-Reliable and Low Latency Communication (URLLC) on different PDU sessions. Different network slices have different Network Slice Selection Assistance Information (NSSAI) and different transmission performance requirements, such as reliability, transmission delay, transmission rate, etc. Each different PDU session can have multiple Quality of Service flows (QoS flows).

[0051] In combination with reference Figure 4 In a specific communication, in the downlink direction, first, a Service Data Flow (SDF) template of a NAS layer of a core network classifies different data packets from an application layer, maps the different data packets to different QoS flows in different PDU sessions, and causes the different data packets to be sent to a base station in the different PDU sessions. A network device maps the different QoS flows to different Data Radio Bearers (DRBs) according to ID information of the QoS flows, and sends the different QoS flows to a terminal device over an air interface. Similarly, for uplink data, similar operations are also implemented.

[0052] Synchronization Signal Block (SSB)-based random access resource division:

[0053] In 5G NR, because of the large-scale application of beamforming technology, a terminal device hopes to receive a msg2 / msg4 of a network reply on a specific beam when performing random access, so as to improve information receiving power.

[0054] In Rel-15 NR, the network device allocates different random access resources (such as random access time-frequency resources or random access preambles) for SSBs in different directions, so that the terminal device selects the corresponding random access resource of the SSB that matches its own expectations to perform random access. When the network device receives the msg1 of the terminal device, it determines the SSB that the terminal device expects to send downlink information according to the random access preamble and / or random access time-frequency resource used by the terminal device.

[0055] In combination with reference Figure 5 In (a) of FIG. 1, ssb-perRACH-OccasionAndCB-PreamblesPerSSB is set to 1:52, indicating that 1 SSB occupies 1 RO and 1 SSB corresponds to 52 collision-based preambles (CB-Preambles); msg1-FDM is set to 2, indicating that there are two ROs in different frequency domains at the same time; and the RO resources belonging to SSBs 0-3 are ROs 0-3, respectively.

[0056] In combination with reference Figure 5 In (b) of FIG. 1, ssb-perRACH-OccasionAndCB-PreamblesPerSSB is set to 4:13, indicating that 4 SSBs share 1 RO and 1 SSB corresponds to 13 collision-based random access preambles. It can be seen that SSBs 0-4 all share each RO, but apply different preamble sets.

[0057] Figure 6 A block diagram of a communication system is shown, which can include an access network 12 and a terminal device 14.

[0058] The access network 12 includes a plurality of network devices 120. The network device 120 can be a base station, which is a device deployed in an access network to provide wireless communication functions for terminals. The base station can include various forms of macro base stations, micro base stations, relay stations, access points, etc. In systems using different wireless access technologies, the names of devices with base station functions may vary, such as eNodeB or eNB in LTE systems, gNodeB or gNB in 5G NR-U systems. As communication technology evolves, the description of “base station” may change. For the convenience of the embodiments of the present application, the above-mentioned devices that provide wireless communication functions for terminal devices 14 are collectively referred to as network devices.

[0059] The terminal device 14 can include various handheld devices, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to a wireless modem with wireless communication functions, and various forms of user equipment, mobile stations (MS), terminal devices, and the like. For the convenience of description, the above-mentioned devices are collectively referred to as terminals. The network device 120 and the terminal device 14 communicate with each other through a certain air interface technology, such as a Uu interface.

[0060] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as a Global System for Mobile Communication (GSM) system, a Code Division Multiple Access (CDMA) system, a Wideband Code Division Multiple Access (WCDMA) system, a General Packet Radio Service (GPRS), a Long Term Evolution (LTE) system, an LTE Frequency Division Duplex (FDD) system, an LTE Time Division Duplex (TDD) system, an Advanced Long Term Evolution (LTE-A) system, a New Radio (NR) system, an evolved system of the NR system, an LTE-based access to Unlicensed spectrum (LTE-U) system, an NR-U system, a Universal Mobile Telecommunication System (UMTS), a Worldwide Interoperability for Microwave Access (WiMAX) communication system, a Wireless Local Area Networks (WLAN), a Wireless Fidelity (WiFi), a next-generation communication system, or other communication systems.

[0061] Generally, the conventional communication system supports a limited number of connections and is easy to implement. However, with the development of communication technology, the mobile communication system will not only support the conventional communication, but also support, for example, Device to Device (D2D) communication, Machine to Machine (M2M) communication, Machine Type Communication (MTC), Vehicle to Vehicle (V2V) communication, and Vehicle to Everything (V2X) system, etc. The embodiments of the present application can also be applied to these communication systems.

[0062] Figure 7 A flow chart of a method for determining random access resources provided by an example embodiment of the present application is shown. The method can be applied to a communication system as shown in Figure 6 In the terminal device and the network device shown, the method comprises:

[0063] In step 710, the network device sends random access configuration information to the terminal device, and the random access configuration information is used to indicate that the random access resources are allocated according to network slices or objects having a mapping relationship with the network slices.

[0064] The random access configuration information is information configured by the network device for random access, and the random access information includes an allocation result obtained by allocating the random access resources according to the network slices or the objects having a mapping relationship with the network slices.

[0065] The random access resources include, but are not limited to, at least one of random access time-frequency resources and random access preambles.

[0066] In one implementation mode, the random access configuration information can be used to indicate that the random access time-frequency resources are allocated according to the network slices or the objects having a mapping relationship with the network slices; in another implementation mode, the random access configuration information can be used to indicate that the random access preambles are allocated according to the network slices or the objects having a mapping relationship with the network slices.

[0067] The network slice (Network Slice) is a slice network based on a protocol data unit session (PDU session) and needs to be jointly processed by the RAN side and the CN side. Each network slice is logically isolated from the radio access network bearer network to the core network to meet the requirements of different types of application programs.

[0068] The network slice and the object having a mapping relationship with the network slice have a one-to-one relationship or a many-to-one relationship. That is, a plurality of network slices correspond to one object having a mapping relationship with the network slice, or one network slice corresponds to one object having a mapping relationship with the network slice. The object having a mapping relationship with the network slice supports querying one or more network slices corresponding to the object through the object.

[0069] Optionally, the identifier corresponding to the object having a mapping relationship with the network slice is data obtained by performing an operation on an identifier of the network slice, and embodiments of the present application do not limit the specific operation mode.

[0070] Optionally, the identifier of the network slice refers to single-network slice selection assistance information (S-NSSAI) corresponding to the network slice. Each network slice is identified by a unique S-NSSAI. The S-NSSAI is composed of a slice or service type (SST) and a slice differentiator (SD), the SST represents a service type, and the SD represents different terminal groups of services under the same service type.

[0071] That is, the identifier of the network slice or the identifier of the object having a mapping relationship with the network slice can identify the network slice. After the network device allocates the random access resource according to the network slice, the network device informs the terminal device of the binding relationship between the random access resource and the network slice through the random access configuration information. Optionally, when the network device allocates the random access resource, more random access resources are allocated to the network slice with more services or higher service performance requirements, and less random access resources are allocated to the network slice with less services or lower service performance requirements.

[0072] Optionally, in addition to indicating that the random access resource is allocated according to the network slice or the object having a mapping relationship with the network slice, the random access configuration information can also indicate that the random access resource is allocated according to a non-data transmission service.

[0073] The non-data transmission service is a service unrelated to data transmission, and the non-data transmission service includes but is not limited to tracking area update, uplink time advance acquisition, and ran notification area update.

[0074] In step 720, the terminal device receives the random access configuration information.

[0075] At step 730, the terminal device determines the random access resource according to the random access configuration information.

[0076] The random access resource matches the target network slice to be accessed by the terminal device.

[0077] Since the random access time-frequency resource is allocated according to the network slice or the object having a mapping relationship with the network slice in the random access configuration information, the terminal device can select the random access resource corresponding to the target network slice when accessing the target network slice according to the configuration of the network device.

[0078] Optionally, in the case where there are multiple random access resources corresponding to the target network slice, the terminal device randomly selects one of the random access resources, or selects one of the random access resources according to a certain rule.

[0079] In summary, the method provided in the embodiment, the network device indicates the binding relationship between the random access resource and the network slice by sending the random access configuration information to the terminal device. Since the network device can flexibly allocate the random access resource according to different network slices, such as increasing the size of the random access resource corresponding to the key network slice / popular slice service, or decreasing the size of the random access resource corresponding to the ordinary network slice / less popular slice service, when the terminal device determines the random access resource according to the random access configuration information, the terminal device can select the corresponding random access resource according to the target network slice to be accessed, thereby reducing the probability of collision.

[0080] Meanwhile, the method provided in the embodiment, since there is a binding relationship between the random access resource and the network slice, the network device can know the target network slice to be accessed by the terminal device through the random access resource in the random access process, so as to decide whether to reject the random access of the terminal device according to the current network load, thereby improving the efficiency of communication.

[0081] In the optional embodiment based on Figure 7 , the network device allocates the random access resource according to the network slice or the object having a mapping relationship with the network slice, which can include the following two implementation manners:

[0082] Implementation manner 1: The network device allocates the random access preamble according to the network slice or the object having a mapping relationship with the network slice.

[0083] That is, the network device performs slice division on the preamble domain, and there is a binding relationship between the random access preamble and the network slice.

[0084] Correspondingly, the random access configuration information sent by the network device at this time includes a first allocation result, and the first allocation result is an allocation result obtained by allocating random access preambles according to network slices or objects having a mapping relationship with the network slices.

[0085] Implementation 2: The network device allocates random access time-frequency resources according to network slices or objects having a mapping relationship with the network slices.

[0086] That is, the network device performs slice division on the random access time-frequency domain, and there is a binding relationship between the RO and the network slice.

[0087] Correspondingly, the random access configuration information sent by the network device at this time includes a second allocation result, and the second allocation result is an allocation result obtained by allocating random access time-frequency resources according to network slices or objects having a mapping relationship with the network slices.

[0088] Next, the above two implementation manners are exemplarily described.

[0089] Implementation 1:

[0090] The random access configuration information includes a first allocation result, and the first allocation result is an allocation result obtained by allocating random access preambles according to network slices or objects having a mapping relationship with the network slices.

[0091] In the embodiment of the application, one random access preamble can correspond to one network slice uniquely, or one random access preamble can correspond to two or more network slices.

[0092] When the network slice to which the terminal device needs to access is the network slice a according to the first allocation result, a target random access preamble can be selected from the random access preambles matched with the network slice a, and random access is performed.

[0093] Optionally, the first allocation result includes at least one of the following:

[0094] I. A ratio of the number of random access preambles allocated for at least one network slice or an object having a mapping relationship with the at least one network slice.

[0095] Exemplarily, there are a network slice a and a network slice b. The ratio of the number of random access preambles allocated for the network slice a and the network slice b is 3:2.

[0096] II. The number of random access preambles allocated for at least one network slice or an object having a mapping relationship with the at least one network slice.

[0097] For example, there are network slice a and network slice b. The number of random access preambles allocated for network slice a and network slice b is respectively: 12 and 40.

[0098] III. Whether to allocate random access preambles for at least one network slice or an object having a mapping relationship with at least one network slice.

[0099] For example, there are network slice a and network slice b. The bit map of random access preambles allocated for network slice a and network slice b is "11", that is, random access preambles are allocated for both network slice a and network slice b; the bit map of random access preambles allocated for network slice a and network slice b is "10", that is, random access preambles are allocated for network slice a, but not for network slice b; the bit map of random access preambles allocated for network slice a and network slice b is "00", that is, random access preambles are not allocated for both network slice a and network slice b.

[0100] In one implementation, the first allocation result includes the first item; in another implementation, the first allocation result includes the second item; in another implementation, the first allocation result includes the first item and the third item; in another implementation, the first allocation result includes the second item and the third item.

[0101] Optionally, the random access preambles are allocated in ascending order of the identity of the network slice or the identity of the object having a mapping relationship with the network slice; or, the random access preambles are allocated in descending order of the identity of the network slice or the identity of the object having a mapping relationship with the network slice.

[0102] That is, the network device can first allocate random access preambles to network slices with smaller identity values or objects having a mapping relationship with network slices with smaller identity values (i.e., ascending order allocation), or can first allocate random access preambles to network slices with larger identity values or objects having a mapping relationship with network slices with larger identity values (i.e., descending order allocation).

[0103] For example, in combination with reference to Figure 8 which shows a schematic diagram of slicing the preamble domain.

[0104] msg1-FDM is set to 2, which means that there are two ROs in different frequency domains at the same time; totalNumberOfRA-Preambles is 60, which means that the total number of preambles that can be used in the cell random access process is 60; ssb-perRACH-OccasionAndCB-PreamblesPerSSB is 2:25, which means that 2 SSBS share 1 RO, and 1 SSB corresponds to 25 collision-based random access preambles; numberOfRA-PreamblesGroupA is 10, which means that the number of random access preambles belonging to Group A is 10.

[0105] The network device slices the preamble domain, and the first allocation result can include: slice 0: slice 1 = 3:2; the first allocation result can also include: the number of random access preambles allocated to slice 0 is 36, and the number of random access preambles of slice 1 is 24; the first allocation result can also include: slice 0: slice 1 = 3:2, bitmap = '011' (slice 2 is set to 0); the first allocation result can also include: the number of random access preambles allocated to slice 0 is 36, and the number of random access preambles of slice 1 is 24, bitmap = '011'.

[0106] As shown in FIG. 1, RO 1 corresponds to SSB1 and SSB2, and the total number of random access preambles allocated to slice 0 is 36, and the total number of random access preambles allocated to slice 1 is 24. Figure 8

[0107] Referring to FIG. 1, if the terminal device wants to access the target network slice slice 0, the terminal device can select random access preamble 18 to try to access the network. If the terminal device wants to access the target network slice slice 1, the terminal device can select random access preamble 30 to try to access the network. Figure 9

[0108] Implementation 2:

[0109] The random access configuration information includes a second allocation result, and the second allocation result is an allocation result obtained by allocating random access time-frequency resources according to network slices or objects having a mapping relationship with the network slices.

[0110] In the embodiments of the present application, one random access time-frequency resource can correspond to one network slice uniquely, or one random access time-frequency resource can correspond to two or more network slices.

[0111] ​​The terminal device selects one random access time-frequency resource from the random access time-frequency resources matched with the network slice a and performs random access according to the second allocation result when the network slice the terminal device needs to access is the network slice a.

[0112] Optionally, the second allocation result includes at least one of the following:

[0113] I. A ratio of the number of random access time-frequency resources allocated for the at least one network slice or the object having a mapping relationship with the at least one network slice.

[0114] For example, there are the network slice a and the network slice b. The ratio of the number of random access time-frequency resources allocated for the network slice a and the network slice b is 3:1.

[0115] II. The number of random access time-frequency resources allocated for the at least one network slice or the object having a mapping relationship with the at least one network slice.

[0116] For example, there are the network slice a and the network slice b. The number of random access time-frequency resources allocated for the network slice a and the network slice b is 3 and 1 respectively.

[0117] III. A bitmap of whether random access time-frequency resources are allocated for the at least one network slice or the object having a mapping relationship with the at least one network slice.

[0118] For example, there are the network slice a, the network slice b and the network slice c. The bitmap of random access time-frequency resources allocated for the network slice a, the network slice b and the network slice c is “011”, that is, random access time-frequency resources are allocated for the network slice a and the network slice b, and no random access time-frequency resources are allocated for the network slice c.

[0119] In one implementation, the second allocation result includes the first item; in another implementation, the second allocation result includes the second item; in another implementation, the second allocation result includes the first item and the third item; in another implementation, the second allocation result includes the second item and the third item.

[0120] Optionally, the random access time-frequency resources are allocated in ascending order of the identifier of the network slice or the identifier of the object having a mapping relationship with the network slice; or, the random access time-frequency resources are allocated in descending order of the identifier of the network slice or the identifier of the object having a mapping relationship with the network slice.

[0121] That is, the network device can first allocate the random access time-frequency resource to the network slice with a smaller identification value or the object with a smaller identification value that has a mapping relationship with the network slice (i.e., ascending allocation), or can first allocate the random access time-frequency resource to the network slice with a larger identification value or the object with a larger identification value that has a mapping relationship with the network slice (i.e., descending allocation).

[0122] For example, referring to Figure 10 , a schematic diagram of slicing the random access time-frequency domain is shown.

[0123] msg1-FDM is set to 4, indicating that there are four ROs in different frequency domains at the same time; totalNumberOfRA-Preambles is 60, indicating that the total number of preambles that can be used in the cell random access process is 60; ssb-perRACH-OccasionAndCB-PreamblesPerSSB is 4:15, indicating that 4 SSBS share 1 RO, and 1 SSB corresponds to 15 collision-based random access preambles.

[0124] The network device slices the preamble domain, and the second allocation result can include: slice 0:slice 1=3:1; the second allocation result can also include: the number of ROs allocated to slice 0 is 3, and the number of ROs of slice 1 is 1; the second allocation result can also include: slice 0:slice 1=3:1, bitmap=‘011’ (slice 2 is set to 0); the second allocation result can also include: the number of ROs allocated to slice 0 is 3, and the number of ROs of slice 1 is 1, bitmap=‘011’.

[0125] As shown in Figure 10 , RO 0, RO 1, and RO 2 are allocated to slice 0, and RO 3 is allocated to slice 1.

[0126] For example, referring to Figure 11 , if the target network slice that the terminal device wants to access is slice 0, the terminal device can select RO 0 to try to access the network. If the target network slice that the terminal device wants to access is slice 1, the terminal device can select RO 3 to try to access the network.

[0127] In summary, the random access configuration information sent by the network device can include the first allocation result, i.e., the random access preambles are allocated according to the network slice or the object that has a mapping relationship with the network slice, or can include the second allocation result, i.e., the random access time-frequency resource is allocated according to the network slice or the object that has a mapping relationship with the network slice, thereby improving the flexibility of the random access resource determination method.

[0128] In an optional embodiment based on Figure 7 , the network device determines the random access configuration information according to at least one of network load condition, network capability and terminal historical access information. Figure 12 A flow chart of a method for determining random access resources provided by an example embodiment of the present application is shown. In this embodiment, steps 740 and 750 are also included:

[0129] In step 740, the network device determines the random access configuration information.

[0130] In this embodiment, the random access configuration information is determined by the network device according to at least one of network load condition, network capability and terminal historical access information.

[0131] In step 710, the network device sends the random access configuration information to the terminal device, and the random access configuration information is used to indicate that the random access resources are allocated according to network slices or objects having a mapping relationship with the network slices.

[0132] Optionally, the random access configuration information is carried in a system message, or the random access configuration information is carried in RRC signaling. The network device can also send the random access configuration information through other signaling, which is not limited in the embodiments of the present application.

[0133] Optionally, the random access resources can also be allocated according to non-data transmission services. The non-data transmission services include at least one of tracking area update, uplink time advance acquisition and radio access network notification area update.

[0134] In one implementation mode, the network slices include a default network slice, and the default network slice is used to carry services with basic transmission performance requirements and / or is associated with non-data transmission services. For example, the default network slice is only associated with non-data transmission services, or the default network slice is only used to carry eMBB services (i.e. services with basic transmission performance requirements), or the default network slice is used to carry eMBB services and is associated with non-data transmission services. That is, since the default network slice can carry non-data transmission services, the random access resources can be allocated according to non-data transmission services.

[0135] In another implementation mode, the random access configuration information is also used to indicate the correspondence between the random access resources and random access performed due to non-data transmission services. That is, the non-data transmission services are not carried by the network slices (such as the default network slice), and the random access configuration information additionally indicates the correspondence between the random access resources and random access performed due to non-data transmission services.

[0136] In step 720, the terminal device receives the random access configuration information.

[0137] At step 730, the terminal device determines the random access resource according to the random access configuration information.

[0138] At step 750, the terminal device performs random access using the random access resource.

[0139] Optionally, the random access resource includes at least one of a random access preamble and a random access time-frequency resource. The terminal device sends the random access preamble to the network device through the random access time-frequency resource.

[0140] To sum up, the method provided in this embodiment can indicate the random access resource corresponding to the non-data transmission service through the random access configuration information, so that the terminal device can also determine the corresponding random access resource when performing the non-data transmission service.

[0141] It should be noted that the above method embodiments can be implemented separately or in combination, and the present application does not limit this.

[0142] In the above various embodiments, the steps performed by the terminal device can be implemented separately as a processing method of handover failure on the terminal device side, and the steps performed by the network device can be implemented separately as a determination method of random access resource on the network device side.

[0143] Figure 13 A structure block diagram of a determination apparatus of random access resource provided by an example embodiment of the present application is shown, the apparatus can be implemented as a terminal device, or as a part of a terminal device, and the apparatus includes a receiving module 1301 and a determination module 1302.

[0144] The receiving module 1301 is configured to receive random access configuration information, and the random access configuration information is used to indicate that the random access resource is allocated according to a network slice or an object having a mapping relationship with the network slice.

[0145] The determination module 1302 is configured to determine the random access resource according to the random access configuration information, and the random access resource matches a target network slice to be accessed by the terminal device.

[0146] In an optional embodiment, the random access configuration information includes a first allocation result, and the first allocation result is an allocation result obtained by allocating the random access preamble according to the network slice or the object having the mapping relationship with the network slice.

[0147] In an optional embodiment, the first allocation result includes at least one of the following:

[0148] A ratio of the number of random access preambles allocated for the at least one network slice or the object having the mapping relationship with the at least one network slice;

[0149] a number of random access preambles allocated for the at least one network slice or the object having a mapping relationship with the at least one network slice;

[0150] a bitmap indicating whether random access preambles are allocated for the at least one network slice or the object having a mapping relationship with the at least one network slice.

[0151] In an optional embodiment, the random access preambles are allocated in ascending order of the identity of the network slice or the identity of the object having a mapping relationship with the network slice; or, the random access preambles are allocated in descending order of the identity of the network slice or the identity of the object having a mapping relationship with the network slice.

[0152] In an optional embodiment, the random access configuration information includes a second allocation result, the second allocation result being an allocation result of random access time-frequency resources allocated according to the network slice or the object having a mapping relationship with the network slice.

[0153] In an optional embodiment, the second allocation result includes at least one of the following:

[0154] a ratio of a number of random access time-frequency resources allocated for the at least one network slice or the object having a mapping relationship with the at least one network slice;

[0155] a number of random access time-frequency resources allocated for the at least one network slice or the object having a mapping relationship with the at least one network slice;

[0156] a bitmap indicating whether random access time-frequency resources are allocated for the at least one network slice or the object having a mapping relationship with the at least one network slice.

[0157] In an optional embodiment, the random access time-frequency resources are allocated in ascending order of the identity of the network slice or the identity of the object having a mapping relationship with the network slice;

[0158] or, the random access time-frequency resources are allocated in descending order of the identity of the network slice or the identity of the object having a mapping relationship with the network slice.

[0159] In an optional embodiment, the identity corresponding to the object having a mapping relationship with the network slice is data obtained by operating on the identity of the network slice.

[0160] In an optional embodiment, the network slice and the object having a mapping relationship with the network slice are in a many-to-one relationship, or the network slice and the object having a mapping relationship with the network slice are in a one-to-one relationship.

[0161] In an optional embodiment, the network slices include a default network slice; or, the random access configuration information is further used to indicate a correspondence between the random access resource and the random access performed due to non-data transmission service. In an optional embodiment, the non-data transmission service includes at least one of the following: tracking area update, uplink time advance acquisition, and radio access network notification area update.

[0162] In an optional embodiment, the random access configuration information is carried in a system message; or, the random access configuration information is carried in radio resource control (RRC) signaling.

[0163] In an optional embodiment, the apparatus further includes a random access module 1303; and the random access module 1303 is configured to perform random access using the target random access resource.

[0164] Figure 14 A structure block diagram of a random access resource determination apparatus provided by an example embodiment of the present application is shown, which can be implemented as a network device, or as a part of a network device, and the apparatus includes a sending module 1401.

[0165] The sending module 1401 is configured to send random access configuration information, and the random access configuration information is used to indicate that random access resources are allocated according to network slices or objects having a mapping relationship with the network slices.

[0166] The random access configuration information is used for a terminal device to determine random access resources, and the random access resources match a target network slice to be accessed by the terminal device.

[0167] In an optional embodiment, the random access configuration information includes a first allocation result, and the first allocation result is an allocation result obtained by allocating random access preambles according to network slices or objects having a mapping relationship with the network slices.

[0168] In an optional embodiment, the first allocation result includes at least one of the following:

[0169] A ratio of the number of random access preambles allocated for at least one network slice or an object having a mapping relationship with the at least one network slice;

[0170] The number of random access preambles allocated for at least one network slice or an object having a mapping relationship with the at least one network slice;

[0171] A bitmap indicating whether random access preambles are allocated for at least one network slice or an object having a mapping relationship with the at least one network slice.

[0172] In an optional embodiment, the random access preambles are allocated in ascending order of the identities of the network slices or the identities of the objects having the mapping relationship with the network slices; or, the random access preambles are allocated in descending order of the identities of the network slices or the identities of the objects having the mapping relationship with the network slices.

[0173] In an optional embodiment, the random access configuration information includes a second allocation result, the second allocation result being an allocation result obtained by allocating the random access time-frequency resources according to the network slices or the objects having the mapping relationship with the network slices.

[0174] In an optional embodiment, the second allocation result includes at least one of:

[0175] a ratio of the number of the random access time-frequency resources allocated for the at least one network slice or the objects having the mapping relationship with the at least one network slice;

[0176] the number of the random access time-frequency resources allocated for the at least one network slice or the objects having the mapping relationship with the at least one network slice;

[0177] a bitmap indicating whether the random access time-frequency resources are allocated for the at least one network slice or the objects having the mapping relationship with the at least one network slice.

[0178] In an optional embodiment, the random access time-frequency resources are allocated in ascending order of the identities of the network slices or the identities of the objects having the mapping relationship with the network slices; or, the random access time-frequency resources are allocated in descending order of the identities of the network slices or the identities of the objects having the mapping relationship with the network slices.

[0179] In an optional embodiment, the identity corresponding to the object having the mapping relationship with the network slice is data obtained by operating on the identity of the network slice.

[0180] In an optional embodiment, the network slice and the object having the mapping relationship with the network slice are in a many-to-one relationship, or the network slice and the object having the mapping relationship with the network slice are in a one-to-one relationship.

[0181] In an optional embodiment, the network slice includes a default network slice; or, the random access configuration information is further used to indicate a correspondence between the random access resources and random access performed due to non-data transmission service.

[0182] In an optional embodiment, the non-data transmission service includes at least one of tracking area update, uplink time advance acquisition, and radio access network notification area update. In an optional embodiment, the random access configuration information is carried in a system message; or, the random access configuration information is carried in radio resource control (RRC) signaling.

[0183] In an optional embodiment, the apparatus further includes a determining module 1402 configured to determine the random access configuration information, wherein the random access configuration information is determined according to at least one of network load condition, network capability, and terminal historical access information.

[0184] Figure 15 A structure diagram of a communication device (terminal device or network device) provided by an example embodiment of the present application is shown, which includes a processor 101, a receiver 102, a transmitter 103, a memory 104, and a bus 105.

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

[0186] The receiver 102 and the transmitter 103 can be implemented as a communication component, which can be a communication chip.

[0187] The memory 104 is connected to the processor 101 through the bus 105.

[0188] The memory 104 can be used to store at least one instruction, and the processor 101 is configured to execute the at least one instruction to implement various steps in the above method embodiments.

[0189] In addition, the memory 104 can be implemented by any type of volatile or non-volatile storage devices or a combination thereof, including but not limited to: a magnetic or optical disk, an Electrically-Erasable Programmable Read Only Memory (EEPROM), an Erasable Programmable Read Only Memory (EPROM), a Static Random Access Memory (SRAM), a Read-Only Memory (ROM), a magnetic storage, a flash memory, a Programmable Read-Only Memory (PROM).

[0190] In an example embodiment, a computer readable storage medium is also provided, and the computer readable storage medium stores at least one instruction, at least one program, a code set or an instruction set, which are loaded and executed by a processor to implement the method for determining random access resources performed by a communication device provided by each of the above-mentioned method embodiments.

[0191] In an example embodiment, a computer program product or computer program is also provided, and the computer program product or computer program includes computer instructions stored in a computer readable storage medium, and a processor of a computer device reads the computer instructions from the computer readable storage medium, and the processor executes the computer instructions to enable the computer device to perform the method for determining random access resources described in the above-mentioned aspects.

[0192] Those of ordinary skill in the art can understand that all or part of the steps of the above-mentioned embodiments can be completed by hardware, or by a program instructing relevant hardware, and the program can be stored in a computer readable storage medium, and the above-mentioned storage medium can be a read-only memory, a magnetic disk or an optical disk, etc.

[0193] The above-mentioned is only an optional embodiment of the present application, and is not used to limit the present application, and any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A method for determining random access resources, characterized in that, Applied to a terminal device, the method comprises: Receiving random access configuration information, the random access configuration information is used to indicate that random access resources are allocated according to network slices or objects having a mapping relationship with the network slices, wherein the random access resources include random access preambles and random access time-frequency resources, the random access configuration information includes a bitmap indicating whether random access preambles are allocated for at least one of the network slices or objects having a mapping relationship with at least one of the network slices, a bitmap indicating whether random access time-frequency resources are allocated for at least one of the network slices or objects having a mapping relationship with at least one of the network slices, and the number of random access time-frequency resources allocated for at least one of the network slices or objects having a mapping relationship with at least one of the network slices; the random access configuration information is also used to indicate that the random access resources are allocated according to non-data transmission services, and the non-data transmission services include tracking area update, uplink time advance acquisition and radio access network notification area update; According to the random access configuration information, determine the random access resources, the random access resources match the target network slice to be accessed by the terminal device.

2. The method of claim 1, wherein: The random access configuration information includes a first allocation result, and the first allocation result is an allocation result obtained by allocating random access preambles according to the network slices or objects having a mapping relationship with the network slices.

3. The method of claim 2, wherein, The first allocation result further includes at least one of: The ratio of the number of random access preambles allocated for at least one of the network slices or objects having a mapping relationship with at least one of the network slices; The number of random access preambles allocated for at least one of the network slices or objects having a mapping relationship with at least one of the network slices.

4. The method of claim 1, wherein: The random access configuration information includes a second allocation result, and the second allocation result is an allocation result obtained by allocating random access time-frequency resources according to the network slices or objects having a mapping relationship with the network slices.

5. The method of claim 4, wherein, The second allocation result further includes: The ratio of the number of random access time-frequency resources allocated for at least one of the network slices or objects having a mapping relationship with at least one of the network slices.

6. The method of any one of claims 1 to 5, wherein: The network slices and the objects having a mapping relationship with the network slices are in a many-to-one relationship, or the network slices and the objects having a mapping relationship with the network slices are in a one-to-one relationship.

7. The method of any one of claims 1 to 5, wherein: The random access configuration information is carried in a system message; Or, the random access configuration information is carried in radio resource control (RRC) signaling.

8. A method for determining random access resources, characterized by, Applied to a network device, the method comprises: transmit random access configuration information, the random access configuration information being used to indicate that random access resources are allocated according to network slices or objects having a mapping relationship with the network slices, wherein the random access resources include random access preambles and random access time-frequency resources, the random access configuration information includes a bitmap indicating whether random access preambles are allocated for at least one of the network slices or objects having a mapping relationship with the network slices, a bitmap indicating whether random access time-frequency resources are allocated for at least one of the network slices or objects having a mapping relationship with the network slices, and a quantity of random access time-frequency resources allocated for at least one of the network slices or objects having a mapping relationship with the network slices; the random access configuration information is also used to indicate that the random access resources are allocated according to non-data transmission services, the non-data transmission services including tracking area updates, uplink time advance acquisition, and radio access network notification area updates; The random access configuration information is used for a terminal device to determine random access resources, the random access resources matching a target network slice to be accessed by the terminal device.

9. The method of claim 8, wherein the random access configuration information includes a first allocation result of random access preambles allocated according to the network slices or objects having a mapping relationship with the network slices. The first allocation result further includes at least one of the following:

10. The method of claim 9, wherein, a ratio of a quantity of random access preambles allocated for at least one of the network slices or objects having a mapping relationship with the network slices; and a quantity of random access preambles allocated for at least one of the network slices or objects having a mapping relationship with the network slices.

11. The method of claim 8, wherein the random access configuration information includes a second allocation result of random access time-frequency resources allocated according to the network slices or objects having a mapping relationship with the network slices. The second allocation result further includes: a ratio of a quantity of random access time-frequency resources allocated for at least one of the network slices or objects having a mapping relationship with the network slices.

12. The method of claim 11, wherein, 13. The method of any one of claims 8 to 12, wherein the network slices and the objects having a mapping relationship with the network slices are in a many-to-one relationship, or the network slices and the objects having a mapping relationship with the network slices are in a one-to-one relationship.

14. The method of any one of claims 8 to 12, wherein the random access configuration information is carried in a system message. Or, the random access configuration information is carried in radio resource control (RRC) signaling. The apparatus is applied in a terminal device and includes a receiving module and a determining module. ​ ​ ​ 15. A device for determining random access resources, characterized in that, ​ The receiving module is configured to receive random access configuration information, where the random access configuration information is used to indicate that random access resources are allocated according to network slices or objects having a mapping relationship with the network slices, the random access resources include random access preambles and random access time-frequency resources, the random access configuration information includes a bitmap indicating whether random access preambles are allocated for at least one of the network slices or objects having a mapping relationship with the network slices, a bitmap indicating whether random access time-frequency resources are allocated for at least one of the network slices or objects having a mapping relationship with the network slices, and a quantity of random access time-frequency resources allocated for at least one of the network slices or objects having a mapping relationship with the network slices; and the random access configuration information is further used to indicate that the random access resources are allocated according to non-data transmission services, the non-data transmission services including tracking area updates, uplink time advance acquisition, and radio access network notification area updates. The determining module is configured to determine random access resources according to the random access configuration information, where the random access resources match a target network slice to be accessed by the terminal device.

16. A device for determining random access resources, characterized in that, The application is applied to a network device, and the apparatus includes a sending module. The sending module is configured to send random access configuration information, where the random access configuration information is used to indicate that random access resources are allocated according to network slices or objects having a mapping relationship with the network slices, the random access resources include random access preambles and random access time-frequency resources, the random access configuration information includes a bitmap indicating whether random access preambles are allocated for at least one of the network slices or objects having a mapping relationship with the network slices, a bitmap indicating whether random access time-frequency resources are allocated for at least one of the network slices or objects having a mapping relationship with the network slices, and a quantity of random access time-frequency resources allocated for at least one of the network slices or objects having a mapping relationship with the network slices; and the random access configuration information is further used to indicate that the random access resources are allocated according to non-data transmission services, the non-data transmission services including tracking area updates, uplink time advance acquisition, and radio access network notification area updates. The random access configuration information is used for a terminal device to determine random access resources, where the random access resources match a target network slice to be accessed by the terminal device.

17. A terminal device, comprising: The terminal device includes: a processor; a transceiver connected to the processor; a memory for storing executable instructions of the processor; the processor is configured to load and execute the executable instructions to implement the method for determining random access resources according to any one of claims 1 to 7.

18. A network device, comprising: The network device includes: a processor; a transceiver connected to the processor; a memory for storing executable instructions of the processor; The processor is configured to load and execute the executable instructions to implement the method for determining random access resources according to any one of claims 8 to 14.

19. A computer-readable storage medium, characterized in that, The readable storage medium stores executable instructions, and the processor loads and executes the executable instructions to implement the method for determining random access resources according to any one of claims 1 to 14.

Images