Random access information processing method, terminal and network device
By sending random access reports by the terminal, network equipment adjusts slice resources, solving the problem of unreasonable allocation of random access resources in the communication system, and optimizing the random access experience and resource utilization of the terminal.
Patent Information
- Application Number
- CN202080101493.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-07-21
- Publication Date
- 2024-12-10
- Estimated Expiration
- 2040-07-21
AI Technical Summary
The existing communication system has unreasonable configuration in the allocation of random access resources, which has affected the terminal's random access experience, especially when the synchronization signal blocks facing different directions allocate random access resources, which is prone to collisions and insufficient resources. .
Send a random access report through the terminal, including service slice information related to random access. The network device adjusts the random access resources corresponding to the slice based on the number of preamble sent and collision information, optimizes the number of preambles and the random access timing to reduce the number of preambles to the number of random access points to reduce the number of preambles and the time to Collision probability and improve resource utilization.
The allocation method of random access resources is optimized, the random access delay and collision rate of terminals is reduced, the random access experience of different slice terminals is improved, and the random access performance of key slices is ensured.
Smart Images

Figure CN115669151B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of communications, and more specifically, to a method, terminal and network device for processing random access information. Background Art
[0002] The terminal needs to perform random access in scenarios such as sending uplink data, receiving downlink data, and updating the tracking area. In some scenarios, the network allocates different random access resources for synchronization signal blocks (SSB) facing different directions. For example, random access opportunities (RO) or random access preambles (random access preambles), so that the terminal can select the random access resources corresponding to the synchronization signal block (SSB) that meets its expectations to perform random access. How to optimize the allocation method of random access resources is a problem that needs to be solved. Summary of the invention
[0003] The embodiments of the present application provide a method, a terminal and a network device for processing random access information, which can optimize the allocation method of random access resources.
[0004] The embodiment of the present application provides a method for processing random access information, including:
[0005] The terminal sends a random access report, which includes slice information of the service related to the random access performed by the terminal.
[0006] In one embodiment, in an embodiment of the present application, the slice information includes an identifier for identifying a network slice or an identifier of an object that has a corresponding relationship with the network slice.
[0007] In one implementation, in an embodiment of the present application, the slice information includes an index value of a slice identifier in a set of slice identifiers supported by a cell to which the terminal accesses.
[0008] In one embodiment, in an embodiment of the present application, the random access report also includes the number of preamble code transmissions attempted and / or preamble code collision information during a random access process associated with at least one synchronization signal block SSB or at least one channel state information reference signal CSI-RS.
[0009] The embodiment of the present application also provides a method for processing random access information, including:
[0010] The network device receives a random access report, where the random access report includes slice information of a service related to the random access performed by the terminal;
[0011] The network device determines whether to adjust the random access resources corresponding to the slice information based on the random access report.
[0012] In one embodiment, in an embodiment of the present application, the slice information includes an identifier for identifying a network slice or an identifier of an object that has a corresponding relationship with the network slice.
[0013] In one implementation, in an embodiment of the present application, the slice information includes an index value of a slice identifier in a set of slice identifiers supported by a cell to which the terminal accesses.
[0014] In one embodiment, in an embodiment of the present application, the random access report also includes the number of preamble code transmissions attempted and / or preamble code collision information during a random access process associated with at least one synchronization signal block SSB or at least one channel state information reference signal CSI-RS.
[0015] In one implementation, in an embodiment of the present application, the network device determines whether to adjust the random access resources corresponding to the slice information based on the random access report, including: the network device determines whether to adjust the number of preamble codes and / or the number of random access opportunities RO corresponding to the slice information based on the number of preamble code transmissions and / or preamble code collision information.
[0016] An embodiment of the present application provides a terminal, including:
[0017] A sending unit is used to send a random access report, where the random access report includes slice information of the service performing random access.
[0018] In one embodiment, in an embodiment of the present application, the slice information includes an identifier for identifying a network slice or an identifier of an object that has a corresponding relationship with the network slice.
[0019] In one implementation, in an embodiment of the present application, the slice information includes an index value of a slice identifier in a set of slice identifiers supported by a cell to which the terminal accesses.
[0020] In one embodiment, in an embodiment of the present application, the random access report also includes the number of preamble code transmissions attempted and / or preamble code collision information during a random access process associated with at least one synchronization signal block SSB or at least one channel state information reference signal CSI-RS.
[0021] The present application provides a network device, including:
[0022] A receiving unit, configured to receive a random access report, where the random access report includes slice information of a service performing random access;
[0023] A processing unit is used to determine whether to adjust the random access resources corresponding to the slice information based on the random access report.
[0024] In one embodiment, in an embodiment of the present application, the slice information includes an identifier for identifying a network slice or an identifier of an object that has a corresponding relationship with the network slice.
[0025] In one implementation, in an embodiment of the present application, the slice information includes an index value of a slice identifier in a set of slice identifiers supported by a cell to which the terminal accesses.
[0026] In one embodiment, in an embodiment of the present application, the random access report also includes the number of preamble code transmissions attempted and / or preamble code collision information during a random access process associated with at least one synchronization signal block SSB or at least one channel state information reference signal CSI-RS.
[0027] In one implementation, in an embodiment of the present application, the processing unit is specifically used to determine whether to adjust the number of preamble codes and / or the number of random access opportunities RO corresponding to the slice information based on the number of times the preamble code is sent and / or the preamble code collision information.
[0028] The embodiment of the present application provides a terminal, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the terminal executes the method executed by the terminal in the above-mentioned random access information processing method.
[0029] The embodiment of the present application provides a network device, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the network device executes the method executed by the network device in the above-mentioned random access information processing method.
[0030] An embodiment of the present application provides a chip for implementing the above-mentioned random access information processing method.
[0031] Specifically, the chip includes: a processor, which is used to call and run a computer program from a memory, so that a device equipped with the chip executes the above-mentioned random access information processing method.
[0032] An embodiment of the present application provides a computer-readable storage medium for storing a computer program. When the computer program is executed by a device, the device executes the above-mentioned method for processing random access information.
[0033] An embodiment of the present application provides a computer program product, including computer program instructions, which enable a computer to execute the above-mentioned random access information processing method.
[0034] An embodiment of the present application provides a computer program, which, when executed on a computer, enables the computer to execute the above-mentioned method for processing random access information.
[0035] In an embodiment of the present application, the random access report includes slice information of the terminal and the service related to the random access performed, and random access resources can be allocated according to the slice information to optimize the allocation method of random access resources. BRIEF DESCRIPTION OF THE DRAWINGS
[0036] Figure 1 It is a schematic diagram of an application scenario according to an embodiment of the present application.
[0037] Figure 2 It is a schematic flowchart of a method for processing random access information according to an embodiment of the present application.
[0038] Figure 3 This is an example diagram of MAC (Medium Access Control)-PDU (Protocol Data Unit) including MAC (Medium Access Control)-RAR (Random Access Response).
[0039] Figure 4 This is an example of the specific content in RAR.
[0040] Figure 5 It is a schematic diagram of a random access process.
[0041] Figure 6 This is a schematic diagram of network slicing.
[0042] Figure 7 and Figure 8 This is a schematic diagram of the random access resource allocation method based on SSB.
[0043] Fig. 9 It is a schematic diagram of random access optimization.
[0044] Fig.10 It is a schematic flowchart of a method for processing random access information according to another embodiment of the present application.
[0045] Fig.11 This is an example diagram of optimizing the number of random access resources.
[0046] Fig.12is an example diagram of a random access report.
[0047] Fig.13 It is a schematic block diagram of a terminal according to an embodiment of the present application.
[0048] Fig.14 is a schematic block diagram of a network device according to an embodiment of the present application.
[0049] Fig.15 It is a schematic block diagram of a communication device according to an embodiment of the present application.
[0050] Fig.16 is a schematic block diagram of a chip according to an embodiment of the present application.
[0051] Fig.17 It is a schematic block diagram of a communication system according to an embodiment of the present application. DETAILED DESCRIPTION
[0052] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.
[0053] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (Wireless Fidelity) system. Fidelity, WiFi), fifth-generation communication (5th-Generation, 5G) system or other communication systems, etc.
[0054] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device to device (Device to Device, D2D) communication, machine to machine (Machine to Machine, M2M) communication, machine type communication (Machine Type Communication, MTC), vehicle to vehicle (V2V) communication, or vehicle to everything (V2X) communication, etc. The embodiments of the present application can also be applied to these communication systems.
[0055] In one implementation, the communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, or a standalone (SA) networking scenario.
[0056] In one embodiment, the communication system in the embodiment of the present application can be applied to an unlicensed spectrum, wherein the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, wherein the authorized spectrum can also be considered as an unshared spectrum.
[0057] The embodiments of the present application describe various embodiments in conjunction with network devices and terminal devices, wherein the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
[0058] The terminal device can be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a next-generation communication system such as an NR network, or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.
[0059] In the embodiments of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (for example, on airplanes, balloons and satellites, etc.).
[0060] In the embodiment of the present application, the terminal device can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self driving, a wireless terminal device in remote medical, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.
[0061] As an example but not limitation, in the embodiments of the present application, the terminal device may also be a wearable device. Wearable devices may also be referred to as wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also powerful functions achieved through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include full-featured, large-sized, and fully or partially independent of smartphones, such as smart watches or smart glasses, as well as devices that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various types of smart bracelets and smart jewelry for vital sign monitoring.
[0062] In an embodiment of the present application, the network device may be a device for communicating with a mobile device. The network device may be an access point (AP) in WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (EvolutionalNode B, eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and a network device (gNB) in an NR network, or a network device in a future evolved PLMN network, or a network device in an NTN network, etc.
[0063] As an example and not limitation, in an embodiment of the present application, the network device may have a mobile characteristic, for example, the network device may be a mobile device. In one embodiment, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. In one embodiment, the network device may also be a base station set up in a location such as land or water.
[0064] In an embodiment of the present application, the network device can provide services for a cell, and the terminal device communicates with the network device through the transmission resources used by the cell (for example, frequency domain resources, or spectrum resources). The cell can be a cell corresponding to the network device (for example, a base station), and the cell can belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.
[0065] Figure 1 A communication system 100 is exemplarily shown. The communication system includes a network device 110 and two terminal devices 120. In one embodiment, the communication system 100 may include multiple network devices 110, and each network device 110 may include other number of terminal devices 120 within its coverage area, which is not limited in the present embodiment.
[0066] In one implementation, the communication system 100 may also include other network entities such as a mobility management entity (MME), an access and mobility management function (AMF), etc., which is not limited in the embodiments of the present application.
[0067] Among them, the network equipment may include access network equipment and core network equipment. That is, the wireless communication system also includes multiple core networks for communicating with the access network equipment. The access network equipment may be an evolutionary base station (evolutional node B, referred to as eNB or e-NodeB) macro base station, micro base station (also called "small base station"), micro-micro base station, access point (AP), transmission point (TP) or new generation base station (new generation Node B, gNodeB) in a long-term evolution (LTE) system, a next-generation (mobile communication system) (next radio, NR) system or an authorized auxiliary access long-term evolution (LAA-LTE) system.
[0068] 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 shown as an example, the communication equipment may include network equipment and terminal equipment with communication functions. The network equipment and terminal equipment may be specific equipment described in the embodiments of the present invention, which will not be repeated here; the communication equipment may also include other equipment in the communication system, such as network controllers, mobile management entities and other network entities, which are not limited to the embodiments of the present application.
[0069] It should be understood that the terms "system" and "network" are often used interchangeably in this article. The term "and / or" in this article is only a description of the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.
[0070] It should be understood that the "indication" mentioned in the embodiments of the present application can be a direct indication, an indirect indication, or an indication of an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association relationship between A and B.
[0071] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between two items, or an association relationship between the two items, or a relationship between indication and being indicated, configuration and being configured, and the like.
[0072] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following related technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all belong to the protection scope of the embodiments of the present application.
[0073] Figure 2 FIG. 2 is a schematic flow chart of a method 200 for processing random access information according to an embodiment of the present application. The method can be applied to Figure 1 The system shown in the figure is not limited thereto. The method includes at least part of the following contents.
[0074] S210. The terminal sends a random access report, which includes slice information of the service related to the random access performed by the terminal.
[0075] In one example, the terminal needs to perform random access in scenarios such as sending uplink data, receiving downlink data, and updating tracking areas. There are two types of random access: collision-based and collision-free.
[0076] like Figure 3 As shown, in the collision-based random access process, the terminal uses a common random access preamble (RACH preamble) on a random access time-frequency resource (random access channel opportunity, RACH occasion) to send message 1 (msg1). Afterwards, the terminal uses RA (Random Access)-RNTI (Radio Network Temporary Identifier) to monitor the network's PDCCH indication information about the random access response (RAR) on the physical downlink control channel (Physical Downlink Control Channel, PDCCH). When the PDCCH indication information about the RAR is found, the terminal will decode the RAR at the time-frequency position given by the PDCCH indication information. If the RAR includes the random access preamble information sent by the terminal, the terminal will then apply the information in the RAR corresponding to the random access preamble to send message 3 (msg3). For example, Figure 3 The subPDU in the subPDU indicates a subPDU (Protocol Data Unit), and Padding (opt) indicates that padding is optional. The terminal finds that the MACsubPDU3 format includes a subheader that matches its own preamble ID, and can subsequently use the content in the related MAC RAR to send msg3.
[0077] like Figure 4The figure shows an example of the specific contents included in the RAR. The RAR may include a timing advance command (TimingAdvance Command), an uplink grant (UL Grant), a temporary (Temporary) C-RNTI (Cell Radio Network Temporary Identifier, cell radio network temporary identifier), etc.
[0078] In msg3, which contains RRC commands such as Radio Resource Control (RRC) connection establishment request (RRCSetupRequest), the terminal needs to carry its own UE ID (identification). In the case of many terminals performing random access, other terminals may also send msg3 (carrying the terminal UE ID) at the time-frequency position indicated by the uplink grant (UL grant) to try to access the network. In this case, random access collisions will occur between terminals, and the network may only carry the ID of one of the UEs in message 4 (msg4) to allow it to access the network.
[0079] like Figure 5 As shown, it is an example of a random access process: Terminal 1 and Terminal 2 send message 1 (msg1) to a network device such as a gNB, which may include a preamble. The gNB returns a message 2 (msg2) to Terminal 1 and Terminal 2, which includes a random access response RAR, and the RAR includes an uplink grant (UL grant). Terminal 1 and Terminal 2 send a message 3 (msg3) to the network device, such as an RRC connection establishment request (RRCSetupRequest), which may include a terminal identifier, such as UEID#1 and UE ID#2. The gNB returns an RRC connection establishment result, which may include a terminal identifier of a successfully established connection, such as UE ID#1. At this time, the gNB may return a message of successful RRC connection establishment to Terminal 1, and a message of failed RRC connection establishment to Terminal 2.
[0080] Network slices can include a RAN (Radio Access Network) part and a CN (CoreNetwork) part. The communication network's support for network slicing depends on carrying data communications belonging to different slices by different PDU sessions. Different slices have different Network Slice Selection Assistance Information (NSSAI), as well as different transmission performance requirements such as reliability, transmission latency, transmission rate, etc. In actual applications, the network can carry eMBB (enhanced Mobile Broadband) and URLLC (Ultra-low latency communication) services on different PDU sessions. Each different PDU session can have multiple QoS (Quality of Service) flows.
[0081] For example, Figure 6 As shown, in specific communications, in the downlink direction, the NAS layer SDF (Service data flow) template of the core network classifies different data packets from the application layer, maps them to different QoS flows in different PDU sessions, and sends the QoS flows to the base station in different PDU sessions. Among them, the SDF template can be in the UPF (User Plane Function). The base station maps the QoS flow to different DRBs (Data Radio Bearers) on the air interface according to the ID information of the QoS flow and sends them to the terminal. Similarly, similar operations are also implemented for uplink data. Figure 6 The AN (Access Network) resources in the access network may include a radio bearer DRB. The QoS rules may include: mapping application layer data packets, such as UL data packets, to different QoS flows according to different QoS requirements, and applying different QoS flow markings. All data packets in the same QoS flow are marked with the same QoS flow ID.
[0082] In one example, random access resources can be divided based on SSB. In 5G NR, due to the large-scale application of beamforming technology, the terminal hopes to receive msg2 / msg4 replied by the network on a specific beam when performing random access to improve the information receiving power. In Rel-15 NR, the network allocates different random access resources (such as RO or random access preamble) to SSBs facing different directions, so that the terminal selects the random access resources corresponding to the SSB that meets its expectations to perform random access. When the network receives the msg1 from the terminal, it determines the SSB that the terminal expects to send downlink information based on the random access preamble and / or random access time-frequency resources (RACH ocassion) used by the terminal.
[0083] See also Figure 7 In one example, if the random access opportunity for SSB (e.g., ssb-perRACH-OccasionAndCB-PreamblesPerSSB) is set to 1:52 and Msg1-FDM is set to 2, the RO resources belonging to SSB 0 to SSB 3 are RO 0 to RO3, respectively. The preamble set applied to SSB 0 to SSB 3 is the same, for example, preamble 0 to 51. In addition, in this example, the SFN (System Frame Number) corresponding to SSB0 and SSB1 is 5, and the subframe is 9; the SFN corresponding to SSB2 and SSB3 is 9, and the subframe is 9.
[0084] See also Figure 8 In one example, if the random access opportunity for SSB (e.g., ssb-perRACH-OccasionAndCB-PreamblesPerSSB) is set to 4:13, Msg1-FDM is set to 1, SSB0 to SSB 4 share each RO, but apply different preamble sets. For example, the preamble set of SSB0 is preamble 0 to 12; the preamble set of SSB1 is preamble 16 to 28; the preamble set of SSB2 is preamble 32 to 44; and the preamble set of SSB3 is preamble 48 to 60. In addition, in this example, the SFN corresponding to SSB0 to SSB3 is 5 and the subframe is 9.
[0085] In order to prevent random access conflicts between terminals initiating random access for different slice services during the random access phase, random access resources can be divided according to different slices to achieve random access optimization.
[0086] The network may be unreasonable when configuring random access resources and related parameters, which may affect the random access experience of the terminal. The network requires the terminal to report to correct the configuration error. In this embodiment, the content that the terminal needs to report can be optimized.
[0087] like Fig. 9 As shown, it is an example of the reporting process. After the random access process, the network device, such as the gNB, may send an information request (Information Request) to the terminal, such as the UE, in which the random access report request is set to true (ra-ReportReq is set as true). The terminal may return an information response (InformationResponse) to the network device, which may include a random access report, such as ra-ReportList-r16.
[0088] The reported content may include the number of random access preambles sent in the random access attempt to a certain SSB (NumberOfPreamblesSentOnSSB), and an indication of whether a collision was encountered during each attempt. In an embodiment of the present application, slice information of the terminal and the service related to the random access performed may be added to the random access report. In this way, the network device can determine whether to adjust the random access resources corresponding to the slice information based on the number of random access preambles sent, the indication of the collision, the slice information, etc. For example, adjust the number of random access opportunities and / or the number of random access preambles, etc.
[0089] In one embodiment, in an embodiment of the present application, the slice information includes an identifier for identifying a network slice or an identifier of an object that has a corresponding relationship with the network slice.
[0090] Exemplarily, the identifier used to identify a network slice may be S-NSSAI (Single Network Slice Selection Assistance Information) that identifies a network slice.
[0091] For example, if the cell sorts each network slice ID from small to large and assigns index numbers ID1, 2, 3, 4..., the terminal may not report the value of the network slice when reporting, but report the index value of the ID.
[0092] In one implementation, in an embodiment of the present application, the slice information includes an index value of a slice identifier in a set of slice identifiers supported by a cell to which the terminal accesses.
[0093] Exemplarily, the slice identifier set supported by the cell accessed by the terminal may be an NSSAI set. The index value of a slice identifier in the slice identifier set may be the index value of a certain S-NSSAI in the NSSAI set.
[0094] In one embodiment, in an embodiment of the present application, the random access report also includes the number of preamble code transmissions attempted and / or preamble code collision information during a random access process associated with at least one synchronization signal block (SSB) or at least one channel state information reference signal (Channel-state informationReference Signal, CSI-RS).
[0095] Exemplarily, if the number of times the preamble code is attempted to be sent during the random access process is too many, for example, exceeding a certain threshold, it can be determined that the random access resources allocated to the slice for the terminal to perform random access are too few, and the random access resources corresponding to the slice can be increased.
[0096] In an embodiment of the present application, the random access report of the terminal includes slice information of the terminal and the service related to the random access performed, which can assist the network in allocating random access resources according to the slice information and optimize the allocation method of random access resources.
[0097] Fig.10 FIG. 3 is a schematic flow chart of a method 300 for processing random access information according to an embodiment of the present application. The method can be applied to Figure 1 The system shown in the figure is not limited thereto. The method includes at least part of the following contents.
[0098] S310. The network device receives a random access report, where the random access report includes slice information of a service related to the random access performed by the terminal;
[0099] S320. The network device determines whether to adjust the random access resources corresponding to the slice information based on the random access report.
[0100] In this embodiment, after the network device receives the random access report sent by one or more terminals, it can adjust the allocation ratio of the random access resources on different slices accordingly according to the content thereof.
[0101] For example, Fig.11 and Fig.12As shown, the number of preambles for slice 1 under each SSB is 10, and the number of preambles for slice 2 under each SSB is 40. If multiple terminals report that they have performed random access to slice 1 on cell 1, and finally access the network after trying to send 10+ random access preambles, then the base station providing service for cell 1 can know that the number of random access resources allocated to slice 1 is insufficient, and then optimize the number of random access resources. For example, the content of the random access report reported by multiple terminals includes: sending 10 preambles to SSB1, the service slice ID is 1, and the collision value of the first 9 preambles is set to true. In addition, the content of the random access report reported by multiple terminals includes: sending 2 preambles to SSB1, the service slice ID is 2, and the collision value of the first 1 preamble is set to true. The network device can increase the number of ROs or preambles of slice 1, and reduce the number of ROs or preambles of slice 2. For example, after optimization, the number of preambles for slice 1 under each SSB is 25, and the number of preambles for slice 2 under each SSB is 25.
[0102] In one embodiment, in an embodiment of the present application, the slice information includes an identifier for identifying a network slice or an identifier of an object that has a corresponding relationship with the network slice.
[0103] Exemplarily, the identifier used to identify a network slice may be an S-NSSAI that identifies a network slice.
[0104] In one implementation, in an embodiment of the present application, the slice information includes an index value of a slice identifier in a set of slice identifiers supported by a cell to which the terminal accesses.
[0105] Exemplarily, the slice identifier set supported by the cell accessed by the terminal may be an NSSAI set. The index value of a slice identifier in the slice identifier set may be the index value of a certain S-NSSAI in the NSSAI set.
[0106] In one implementation, in an embodiment of the present application, the random access report also includes the number of preamble code transmissions attempted in a random access process associated with at least one SSB or at least one CSI-RS and / or preamble code collision information.
[0107] Exemplarily, if the number of times the preamble code is attempted to be sent during the random access process is too many, for example, exceeding a certain threshold, the network device can determine that the random access resources allocated to the slice for the terminal to perform random access are too few, and can increase the random access resources corresponding to the slice.
[0108] In one implementation, in the embodiment of the present application, the network device determines, according to the random access report, whether to adjust the random access resource corresponding to the slice information, including:
[0109] The network device determines whether to adjust the number of preamble codes and / or the number of ROs corresponding to the slice information based on the number of times the preamble code is sent and / or the preamble code collision information.
[0110] For a specific example of the network device executing the method 300 of this embodiment, reference may be made to the related description of the network device such as a base station in the above method 200, which will not be described again for the sake of brevity.
[0111] In an embodiment of the present application, the method for processing random access information is a method for optimizing random access based on terminal feedback, which can optimize the network so that the sizes of random access resources allocated to different slices are different, so as to improve the overall random access experience of terminals in different slices, and the random access experience of terminals targeting key slices. The level of random access experience is mainly related to the low or high probability of access collision. Generally speaking, the more collisions there are, the more times the preamble needs to be resent, and the greater the delay of random access.
[0112] Fig.13 4 is a schematic block diagram of a terminal 400 according to an embodiment of the present application. The terminal 400 may include:
[0113] The sending unit 410 is used to send a random access report, which includes slice information of the terminal and the service related to the random access performed.
[0114] In one embodiment, in an embodiment of the present application, the slice information includes an identifier for identifying a network slice or an identifier of an object that has a corresponding relationship with the network slice.
[0115] In one implementation, in an embodiment of the present application, the slice information includes an index value of a slice identifier in a set of slice identifiers supported by a cell to which the terminal accesses.
[0116] In one embodiment, in an embodiment of the present application, the random access report also includes the number of preamble code transmissions attempted and / or preamble code collision information during a random access process associated with at least one synchronization signal block SSB or at least one channel state information reference signal CSI-RS.
[0117] The terminal 400 of the embodiment of the present application can implement the corresponding functions of the terminal in the aforementioned method embodiment. The corresponding processes, functions, implementation methods and beneficial effects of each module (submodule, unit or component, etc.) in the terminal 400 can be found in the corresponding description in the aforementioned method embodiment, which will not be repeated here.
[0118] It should be noted that the functions described by each module (sub-module, unit or component, etc.) in the terminal 400 of the embodiment of the present application can be implemented by different modules (sub-modules, units or components, etc.) or by the same module (sub-module, unit or component, etc.).
[0119] Fig.14 is a schematic block diagram of a network device 500 according to an embodiment of the present application. The network device 500 may include:
[0120] A receiving unit 510 is configured to receive a random access report, where the random access report includes slice information of a service related to a random access performed by the terminal;
[0121] The processing unit 520 is used to determine whether to adjust the random access resources corresponding to the slice information according to the random access report.
[0122] In one embodiment, in an embodiment of the present application, the slice information includes an identifier for identifying a network slice or an identifier of an object that has a corresponding relationship with the network slice.
[0123] In one implementation, in an embodiment of the present application, the slice information includes an index value of a slice identifier in a set of slice identifiers supported by a cell to which the terminal accesses.
[0124] In one embodiment, in an embodiment of the present application, the random access report also includes the number of preamble code transmissions attempted and / or preamble code collision information during a random access process associated with at least one synchronization signal block SSB or at least one channel state information reference signal CSI-RS.
[0125] In one implementation, in an embodiment of the present application, the processing unit 520 is specifically used to determine whether to adjust the number of preamble codes and / or the number of random access opportunities RO corresponding to the slice information based on the number of times the preamble code is sent and / or the preamble code collision information.
[0126] The network device 500 of the embodiment of the present application can implement the corresponding functions of the network device in the aforementioned method embodiment. The corresponding processes, functions, implementation methods and beneficial effects of each module (submodule, unit or component, etc.) in the network device 500 can be found in the corresponding description in the aforementioned method embodiment, which will not be repeated here.
[0127] It should be noted that the functions described in the various modules (sub-modules, units or components, etc.) in the network device 500 of the embodiment of the application can be implemented by different modules (sub-modules, units or components, etc.) or by the same module (sub-module, unit or component, etc.).
[0128] Fig.156 is a schematic structural diagram of a communication device 600 according to an embodiment of the present application. The communication device 600 includes a processor 610, and the processor 610 can call and run a computer program from a memory to enable the communication device 600 to implement the method in the embodiment of the present application.
[0129] In one embodiment, Fig.15 As shown, the communication device 600 may further include a memory 620. The processor 610 may call and run a computer program from the memory 620 to enable the communication device 600 to implement the method in the embodiment of the present application.
[0130] The memory 620 may be a separate device independent of the processor 610 , or may be integrated into the processor 610 .
[0131] In one embodiment, Fig.15 As shown, the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices.
[0132] The transceiver 630 may include a transmitter and a receiver. The transceiver 630 may further include an antenna, and the number of the antennas may be one or more.
[0133] In one implementation, the communication device 600 may be a network device of an embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the network device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.
[0134] In one implementation, the communication device 600 may be a terminal of an embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the terminal in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.
[0135] Fig.16 7 is a schematic structural diagram of a chip 700 according to an embodiment of the present application. The chip 700 includes a processor 710, and the processor 710 can call and run a computer program from a memory to implement the method in the embodiment of the present application.
[0136] In one embodiment, Fig.16 As shown, the chip 700 may further include a memory 720. The processor 710 may call and run a computer program from the memory 720 to implement the method executed by the terminal or the network device in the embodiment of the present application.
[0137] The memory 720 may be a separate device independent of the processor 710 , or may be integrated into the processor 710 .
[0138] In one implementation, the chip 700 may further include an input interface 730. The processor 710 may control the input interface 730 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.
[0139] In one implementation, the chip 700 may further include an output interface 740. The processor 710 may control the output interface 740 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.
[0140] In one implementation, the chip can be applied to the network device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.
[0141] In one implementation, the chip can be applied to the terminal in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the terminal in each method of the embodiments of the present application, which will not be described in detail here for the sake of brevity.
[0142] The chips used in the network device and the terminal may be the same chip or different chips.
[0143] 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.
[0144] The processor mentioned above may be a general-purpose processor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC) or other programmable logic devices, transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processor mentioned above may be a microprocessor or any conventional processor, etc.
[0145] The memory mentioned above may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable ROM (PROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM) or a flash memory. The volatile memory may be a random access memory (RAM).
[0146] 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.
[0147] Fig.17 8 is a schematic block diagram of a communication system 800 according to an embodiment of the present application. The communication system 800 includes a terminal 810 and a network device 820.
[0148] Terminal 810 sends a random access report, which includes slice information of the service related to the random access performed by the terminal.
[0149] The network device 820 receives a random access report, which includes slice information of a service related to a random access performed by the terminal; the network device determines whether to adjust the random access resources corresponding to the slice information based on the random access report.
[0150] The terminal 810 can be used to implement the corresponding functions implemented by the terminal in the above method, and the network device 820 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, they will not be described in detail here.
[0151] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instruction is loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network or other programmable devices. The computer instruction can be stored in a computer-readable storage medium, or transmitted from a computer-readable storage medium to another computer-readable storage medium, for example, the computer instruction can be transmitted from a website site, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server, a data center, etc. that contains one or more available media integrations. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).
[0152] It should be understood that in the various 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.
[0153] 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.
[0154] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present 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 method for processing random access information, comprising: The terminal sends a random access report, where the random access report includes slice information of a service related to the random access performed by the terminal; The random access report also includes the number of preamble code transmissions attempted and / or preamble code collision information during a random access process associated with at least one synchronization signal block SSB or a channel state information reference signal CSI-RS.
2. The method according to claim 1, wherein: The slice information includes an identifier for identifying a network slice or an identifier of an object corresponding to the network slice.
3. The method according to claim 1, wherein: The slice information includes the index value of a slice identifier in a set of slice identifiers supported by the cell to which the terminal accesses.
4. A method for processing random access information, comprising: The network device receives a random access report, where the random access report includes slice information of a service related to random access performed by the terminal; The network device determines, according to the random access report, whether to adjust the random access resources corresponding to the slice information; The random access report also includes the number of preamble transmissions attempted during a random access process associated with at least one synchronization signal block SSB or at least one channel state information reference signal CSI-RS and / or preamble collision information; Among them, the network device determines whether to adjust the random access resources corresponding to the slice information according to the random access report, including: the network device determines whether to adjust the number of preamble codes and / or the number of random access opportunities RO corresponding to the slice information according to the number of times the preamble code is sent and / or the preamble code collision information.
5. The method according to claim 4, wherein: The slice information includes an identifier for identifying a network slice or an identifier of an object corresponding to the network slice.
6. The method according to claim 4, wherein: The slice information includes the index value of a slice identifier in a set of slice identifiers supported by the cell to which the terminal accesses.
7. A terminal, comprising: A sending unit, configured to send a random access report, wherein the random access report includes slice information of a service related to the random access performed by the terminal; The random access report also includes the number of preamble code transmissions attempted and / or preamble code collision information during a random access process associated with at least one synchronization signal block SSB or at least one channel state information reference signal CSI-RS.
8. The terminal according to claim 7, wherein: The slice information includes an identifier for identifying a network slice or an identifier of an object corresponding to the network slice.
9. The terminal according to claim 7, wherein: The slice information includes the index value of a slice identifier in a set of slice identifiers supported by the cell to which the terminal accesses.
10. A network device comprising: A receiving unit, configured to receive a random access report, wherein the random access report includes slice information of a service related to a random access performed by the terminal; A processing unit, configured to determine whether to adjust the random access resource corresponding to the slice information according to the random access report; The random access report also includes the number of preamble transmissions attempted during a random access process associated with at least one synchronization signal block SSB or at least one channel state information reference signal CSI-RS and / or preamble collision information; The processing unit is specifically used to determine whether to adjust the number of preamble codes and / or the number of random access opportunities RO corresponding to the slice information according to the number of times the preamble code is sent and / or the preamble code collision information.
11. The network device according to claim 10, wherein: The slice information includes an identifier for identifying a network slice or an identifier of an object corresponding to the network slice.
12. The network device according to claim 10, wherein: The slice information includes the index value of a slice identifier in a set of slice identifiers supported by the cell to which the terminal accesses.
13. A terminal, comprising: A processor and a memory, the memory being used to store a computer program, and the processor being used to call and run the computer program stored in the memory, so that the terminal executes the method according to any one of claims 1 to 3.
14. A network device 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 so that the network device executes the method according to any one of claims 4 to 6.
15. A chip, comprising: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 3.
16. A chip, comprising: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 4 to 6.
17. A computer-readable storage medium, used for storing a computer program, which, when executed by a device, causes the device to perform the method according to any one of claims 1 to 6.
18. A computer program product comprising computer program instructions, the computer program instructions causing a computer to execute the method according to any one of claims 1 to 6.
Citation Information
Patent Citations
Random access resource allocation and random access method and device
CN107872884A
Access Procedures In Wireless Communications
US20200229241A1
Random access information based on network slices
WO2023129515A1
