WO2022016376A1 - 随机接入信息的处理方法、终端和网络设备 - Google Patents

随机接入信息的处理方法、终端和网络设备 Download PDF

Info

Publication number
WO2022016376A1
WO2022016376A1 PCT/CN2020/103289 CN2020103289W WO2022016376A1 WO 2022016376 A1 WO2022016376 A1 WO 2022016376A1 CN 2020103289 W CN2020103289 W CN 2020103289W WO 2022016376 A1 WO2022016376 A1 WO 2022016376A1
Authority
WO
WIPO (PCT)
Prior art keywords
random access
slice
terminal
information
network
Prior art date
Application number
PCT/CN2020/103289
Other languages
English (en)
French (fr)
Inventor
石聪
Original Assignee
Oppo广东移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to PCT/CN2020/103289 priority Critical patent/WO2022016376A1/zh
Priority to CN202080101493.1A priority patent/CN115669151A/zh
Publication of WO2022016376A1 publication Critical patent/WO2022016376A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/10Scheduling measurement reports ; Arrangements for measurement reports
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/04Wireless resource allocation

Definitions

  • the present application relates to the field of communications, and more particularly, to a method, terminal and network device for processing random access information.
  • the terminal needs to perform random access in scenarios such as uplink data transmission, downlink data reception, and tracking area update.
  • the network allocates different random access resources for SSBs facing different directions. For example, a random access opportunity (Random access Ocassion, RO) or a random access preamble (random access preamble), so that the terminal selects the random access resource corresponding to the synchronization signal block (Synchronization Signal Block, SSB) that matches its own expectations. random access.
  • SSB Synchromsing Signal Block
  • the embodiments of the present application provide a method for processing random access information, a terminal, and a network device, which can optimize the allocation mode of random access resources.
  • An embodiment of the present application provides a method for processing random access information, including:
  • the terminal sends a random access report, where the random access report includes slice information of services related to the random access performed by the terminal.
  • 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.
  • the slice information includes an index value of a slice identifier in the slice identifier set supported by the cell accessed by the terminal.
  • the random access report further includes a preamble that has been tried in a random access process related to at least one synchronization signal block SSB or at least one channel state information reference signal CSI-RS. number of transmissions and/or preamble collision information.
  • the embodiment of the present application also provides a method for processing random access information, including:
  • the network device receives a random access report, where the random access report includes slice information of services related to the random access performed by the terminal;
  • the network device determines whether to adjust the random access resource corresponding to the slice information according to the random access report.
  • 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.
  • the slice information includes an index value of a slice identifier in the slice identifier set supported by the cell accessed by the terminal.
  • the random access report further includes a preamble that has been tried in a random access process related to at least one synchronization signal block SSB or at least one channel state information reference signal CSI-RS. number of transmissions and/or preamble collision information.
  • the network device determines whether to adjust the random access resource corresponding to the slice information according to the random access report, including: the network device sends the preamble according to the number of times and/or the preamble Collision information, to determine whether to adjust the number of preambles and/or the number of random access opportunities RO corresponding to the slice information.
  • An embodiment of the present application provides a terminal, including:
  • a sending unit configured to send a random access report, where the random access report includes slice information of a service for performing random access.
  • 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.
  • the slice information includes an index value of a slice identifier in the slice identifier set supported by the cell accessed by the terminal.
  • the random access report further includes a preamble that has been tried in a random access process related to at least one synchronization signal block SSB or at least one channel state information reference signal CSI-RS. number of transmissions and/or preamble collision information.
  • An embodiment of the present application provides a network device, including:
  • a receiving unit configured to receive a random access report, where the random access report includes slice information of services for performing random access
  • the processing unit is configured to determine, according to the random access report, whether to adjust the random access resource corresponding to the slice information.
  • 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.
  • the slice information includes an index value of a slice identifier in the slice identifier set supported by the cell accessed by the terminal.
  • the random access report further includes a preamble that has been tried in a random access process related to at least one synchronization signal block SSB or at least one channel state information reference signal CSI-RS. number of transmissions and/or preamble collision information.
  • the processing unit is specifically configured to determine whether to adjust the number of preambles and/or the random access opportunity corresponding to the slice information according to the number of times of sending the preamble and/or the preamble collision information. Number of ROs.
  • An embodiment of the present application provides a terminal, including a processor and a memory.
  • the memory is used for storing a computer program
  • the processor is used for calling and running the computer program stored in the memory, so that the terminal executes the method executed by the terminal in the above-mentioned method for processing random access information.
  • An embodiment of the present application provides a network device including a processor and a memory.
  • the memory is used for storing a computer program
  • the processor is used for calling and running the computer program stored in the memory, so that the network device executes the method executed by the network device in the above-mentioned method for processing random access information.
  • An embodiment of the present application provides a chip for implementing the above-mentioned method for processing random access information.
  • the chip includes: a processor for calling and running a computer program from the memory, so that the device installed with the chip executes the above-mentioned method for processing random access information.
  • Embodiments of the present application provide a computer-readable storage medium for storing a computer program, which, when the computer program is run by a device, causes the device to execute the above-mentioned method for processing random access information.
  • An embodiment of the present application provides a computer program product, including computer program instructions, and the computer program instructions cause a computer to execute the foregoing method for processing random access information.
  • An embodiment of the present application provides a computer program, which, when running on a computer, enables the computer to execute the above-mentioned method for processing random access information.
  • the random access report includes slice information of services related to the random access performed by the terminal, and random access resources can be allocated according to the slice information to optimize the allocation mode of random access resources.
  • FIG. 1 is a schematic diagram of an application scenario according to an embodiment of the present application.
  • FIG. 2 is a schematic flowchart of a method for processing random access information according to an embodiment of the present application.
  • FIG. 3 is an example diagram of a MAC-PDU containing a MAC-RAR.
  • FIG. 4 is an example diagram of specific content in the RAR.
  • FIG. 5 is a schematic diagram of a random access procedure.
  • FIG. 6 is a schematic diagram of a network slice.
  • FIG. 7 and FIG. 8 are schematic diagrams of the way of random access resource division based on SSB.
  • Figure 9 is a schematic diagram of random access optimization.
  • FIG. 10 is a schematic flowchart of a method for processing random access information according to another embodiment of the present application.
  • FIG. 11 is an example diagram of optimization of the number of random access resources.
  • FIG. 12 is an example diagram of a random access report.
  • FIG. 13 is a schematic block diagram of a terminal according to an embodiment of the present application.
  • FIG. 14 is a schematic block diagram of a network device according to an embodiment of the present application.
  • FIG. 15 is a schematic block diagram of a communication device according to an embodiment of the present application.
  • FIG. 16 is a schematic block diagram of a chip according to an embodiment of the present application.
  • FIG. 17 is a schematic block diagram of a communication system according to an embodiment of the present application.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • CDMA Wideband Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • LTE-A Advanced Long Term Evolution
  • NR New Radio
  • NTN Non-Terrestrial Networks
  • UMTS Universal Mobile Telecommunication System
  • WLAN Wireless Local Area Networks
  • Wireless Fidelity Wireless Fidelity
  • WiFi fifth-generation communication
  • D2D Device to Device
  • M2M Machine to Machine
  • MTC Machine Type Communication
  • V2V Vehicle to Vehicle
  • V2X Vehicle to everything
  • the communication system in this embodiment of the present application may be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, a dual connectivity (Dual Connectivity, DC) scenario, or a standalone (Standalone, SA) distribution. web scene.
  • Carrier Aggregation, CA Carrier Aggregation, CA
  • DC Dual Connectivity
  • SA standalone
  • the communication system in the embodiment of the present application may be applied to an unlicensed spectrum, where the unlicensed spectrum may also be considered as a shared spectrum; or, the communication system in the embodiment of the present application may also be applied to a licensed spectrum, where, Licensed spectrum can also be considered unshared spectrum.
  • the embodiments of the present application describe various embodiments in conjunction with network equipment and terminal equipment, where the terminal equipment may also be referred to as user equipment (User Equipment, UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
  • user equipment User Equipment, UE
  • access terminal subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
  • the terminal device can be a station (STAION, ST) in the WLAN, can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a personal digital processing (Personal Digital Assistant, PDA) devices, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, next-generation communication systems such as end devices in NR networks, or future Terminal equipment in the evolved public land mobile network (Public Land Mobile Network, PLMN) network, etc.
  • STAION, ST in the WLAN
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • the terminal device can be deployed on land, including indoor or outdoor, handheld, wearable, or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons, and satellites) superior).
  • the terminal device may be a mobile phone (Mobile Phone), a tablet computer (Pad), a computer with a wireless transceiver function, a virtual reality (Virtual Reality, VR) terminal device, and an augmented reality (Augmented Reality, AR) terminal Equipment, wireless terminal equipment in industrial control, wireless terminal equipment in self driving, wireless terminal equipment in remote medical, wireless terminal equipment in smart grid , wireless terminal equipment in transportation safety, wireless terminal equipment in smart city or wireless terminal equipment in smart home, etc.
  • a mobile phone Mobile Phone
  • a tablet computer Pad
  • a computer with a wireless transceiver function a virtual reality (Virtual Reality, VR) terminal device
  • augmented reality (Augmented Reality, AR) terminal Equipment wireless terminal equipment in industrial control, wireless terminal equipment in self driving, wireless terminal equipment in remote medical, wireless terminal equipment in smart grid , wireless terminal equipment in transportation safety, wireless terminal equipment in smart city or wireless terminal equipment in smart home, etc.
  • the terminal device may also be a wearable device.
  • Wearable devices can also be called wearable smart devices, which are the general term for the intelligent design of daily wear and the development of wearable devices using wearable technology, 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 clothing or accessories. Wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-scale, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, which needs to cooperate with other devices such as smart phones.
  • the network device may be a device for communicating with a mobile device, and the network device may be an access point (Access Point, AP) in WLAN, or a base station (Base Transceiver Station, BTS) in GSM or CDMA , it can also be a base station (NodeB, NB) in WCDMA, it can also be an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or access point, or in-vehicle equipment, wearable devices and NR networks
  • the network device may have a mobile feature, for example, the network device may be a mobile device.
  • the network device may be a satellite or a balloon station.
  • 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.
  • the network device may also be a base station set in a location such as land or water.
  • a network device may provide services for a cell, and a terminal device communicates with the network device through transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell, and the cell may be a network device (
  • the cell can belong to the macro base station, or it can belong to the base station corresponding to the small cell (Small cell).
  • Pico cell Femto cell (Femto cell), etc.
  • These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.
  • FIG. 1 exemplarily shows a communication system 100 .
  • the communication system includes one network device 110 and two terminal devices 120 .
  • the communication system 100 may include multiple network devices 110, and the coverage of each network device 110 may include other numbers of terminal devices 120, which are not limited in this embodiment of the present application.
  • the communication system 100 may further include a mobility management entity (Mobility Management Entity, MME), an access and mobility management function (Access and Mobility Management Function, AMF) and other network entities, to which the embodiments of the present application Not limited.
  • MME Mobility Management Entity
  • AMF Access and Mobility Management Function
  • the network equipment may further include access network equipment and core network equipment. That is, the wireless communication system further includes a plurality of core networks for communicating with the access network equipment.
  • the access network equipment may be a long-term evolution (long-term evolution, LTE) system, a next-generation (mobile communication system) (next radio, NR) system, or an authorized auxiliary access long-term evolution (authorized auxiliary access long-term evolution, LAA-
  • the evolved base station (evolutional node B, may be referred to as eNB or e-NodeB for short) in the LTE) system is a macro base station, a micro base station (also called a "small base station"), a pico base station, an access point (AP), Transmission site (transmission point, TP) or new generation base station (new generation Node B, gNodeB), etc.
  • a device having a communication function in the network/system may be referred to as a communication device.
  • the communication device may include a network device and a terminal device with a communication function, and the network device and the terminal device may be specific devices described in the embodiments of the present invention, which will not be repeated here;
  • the device may also include other devices in the communication system, for example, other network entities such as a network controller and a mobility management entity, which are not limited in this embodiment of the present application.
  • the "instruction" mentioned in the embodiments of the present application may be a direct instruction, an indirect instruction, or an associated relationship.
  • a indicates B it can indicate that A directly indicates B, for example, B can be obtained through A; it can also indicate that A indicates B indirectly, such as A indicates C, and B can be obtained through C; it can also indicate that there is an association between A and B relation.
  • corresponding may indicate that there is a direct or indirect corresponding relationship between the two, or may indicate that there is an associated relationship between the two, or indicate and be instructed, configure and be instructed configuration, etc.
  • FIG. 2 is a schematic flowchart of a method 200 for processing random access information according to an embodiment of the present application.
  • the method can optionally be applied to the system shown in Figure 1, but is not limited thereto.
  • the method includes at least some of the following.
  • the terminal sends a random access report, where the random access report includes slice information of services related to random access performed by the terminal.
  • the terminal needs to perform random access in scenarios such as uplink data transmission, downlink data reception, and tracking area update.
  • random access There are two types of random access: collision-based and collision-free.
  • the terminal uses a common random access preamble (RACH preamble) on a random access time-frequency resource (RACH occasion) to send message 1 (msg1) .
  • RACH preamble a random access time-frequency resource
  • RA Random Access, Random Access
  • RRNTI Radio Network Temporary Identifier, Network Temporary Identifier
  • PDCCH Physical Downlink Control Channel
  • RAR Random access response
  • subPDU in FIG. 3 represents a sub-PDU (Protocol Data Unit, protocol data unit), and Padding (opt) represents that padding is optional.
  • the terminal finds that the format of MAC subPDU3 includes a subheader that matches its own preamble ID, and can use the content in the relevant MAC RAR to send msg3 later.
  • the RAR may include Timing Advance Command (Timing Advance Command), UL Grant (Uplink Grant), Temporary (Temporary) C-RNTI, etc.
  • msg3 including RRC commands such as Radio Resource Control (Radio Resource Control, RRC) connection setup request (RRCSetupRequest)
  • RRC Radio Resource Control
  • RRCSetupRequest the terminal needs to carry its own UE ID (identification).
  • other terminals may also send msg3 (carrying the UE ID of the terminal) at the time-frequency position indicated by the uplink grant (UL grant) to try to access the network.
  • msg4 message 4 (msg4) to allow it to access the network.
  • Terminal 1 and Terminal 2 send a message 1 (msg1) to a network device such as a gNB, which may include a preamble.
  • the gNB returns 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 message 3 (msg3), such as an RRC connection setup request (RRCSetupRequest), to the network device, which may include terminal identifiers, such as UE ID#1 and UE ID#2.
  • the gNB returns the RRC connection establishment result, which may include the terminal identifier that successfully established the interception, such as UE ID#1.
  • the gNB may return a message that the RRC connection establishment is successful to the terminal 1, and return a message that the RRC connection establishment fails to the terminal 2.
  • a network slice may include a RAN (Radio Access Network, radio access network) part and a CN (Core Network, core network) part.
  • the support of network slices by a communication network relies on carrying data communications belonging to different slices in different PDU sessions. Different slices have different Network Slice Selection Assistance Information (NSSAI), and different transmission performance requirements such as reliability, transmission delay, transmission rate, etc.
  • NSSAI Network Slice Selection Assistance Information
  • the network can carry eMBB (enhanced Mobile Broadband, enhanced mobile broadband) and URLLC (Ultra-low latency communication, ultra-high reliability and ultra-low latency) services on different PDU sessions.
  • Each different PDU session may have multiple QoS (Quality of Service, quality of service) flows.
  • the NAS layer SDF (Service data flow) template of the core network classifies different data packets from the application layer and maps them to Different QoS flows (QoS flows) in different PDU sessions (sessions), and the QoS flows are sent to the base station in different PDU sessions.
  • the SDF template can be in UPF (User Plane Function, user plane function).
  • the base station maps the QoS flow to different DRBs (Data Radio Bearer, data radio bearer) according to the ID information of the QoS flow, and sends it to the terminal over the air interface.
  • DRBs Data Radio Bearer, data radio bearer
  • Similar operations are also implemented.
  • 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 marks. All packets in the same QoS flow are marked with the same QoS flow ID.
  • random access resources may be divided based on SSB.
  • the terminal hopes to receive the msg2/msg4 replied by the network on a specific beam when performing random access, so as to improve the information receiving power.
  • the network allocates different random access resources (such as RO or random access preamble) for SSBs facing different directions, so that the terminal can select the corresponding random access resource of the SSB that matches its own expectations to perform random access. enter. After the network receives the msg1 of the terminal, it determines the SSB that the terminal expects to send downlink information according to the random access preamble and/or the random access time-frequency resource (RACH ocassion) used by the terminal.
  • RACH ocassion random access time-frequency resource
  • the random access opportunity for SSB (for example, ssb-perRACH-OccasionAndCB-PreamblesPerSSB) is set to 1:52, and Msg1-FDM is set to 2, it belongs to SSB 0-SSB 3 RO resources are RO 0 to RO3, respectively.
  • the preamble sets applied by SSB 0 ⁇ SSB3 are the same, for example, preamble 0 ⁇ 51.
  • the SFN System Frame Number, system frame number
  • corresponding to SSB0 and SSB1 is 5
  • the subframe Subframe is 9
  • the SFN corresponding to SSB2 and SSB3 is 9, and the subframe Subframe is 9.
  • the random access opportunity for SSB (eg, ssb-perRACH-OccasionAndCB-PreamblesPerSSB) is set to 4:13, Msg1-FDM is set to 1, SSB0 ⁇ SSB4 share each RO , but applying a different set of preambles.
  • the preamble set of SSB0 is preamble 0 ⁇ 12; the preamble set of SSB1 is preamble 16 ⁇ 28; the preamble set of SSB2 is preamble 32 ⁇ 44; the preamble set of SSB3 is preamble 48 ⁇ 60.
  • the SFN corresponding to SSB0 to SSB3 is 5, and the subframe Subframe is 9.
  • random access resources can be divided according to different slices to realize random access optimization.
  • the network When the network configures random access resources and related parameters, it may be unreasonable, which affects the random access experience of the terminal.
  • the network requires terminal reporting to correct configuration errors.
  • the content to be reported by the terminal can be optimized.
  • the network device such as the gNB may send an information request (Information Request) to the terminal such as the UE, wherein the random access report request is set as true (ra-ReportReq is set as true).
  • the terminal may return an information response (Information Response) to the network device, which may include a random access report, such as ra-ReportList-r16.
  • the reported content may include the number of times of sending the random access preamble (NumberOfPreamblesSentOnSSB) attempted in random access to a certain SSB, and an indication of whether a collision is encountered during each corresponding attempt.
  • slice information of services related to random access performed by the terminal may be added to the random access report.
  • the network device can determine whether to adjust the random access resource corresponding to the slice information according to the number of times of sending the random access preamble, the indication of the collision, the slice information, and the like. For example, the number of random access opportunities and/or the number of random access preambles are adjusted.
  • 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.
  • the identifier used to identify a network slice may be S-NSSAI (Single Network Slice Selection Assistance Information, single network slice selection assistance information) that identifies a network slice.
  • S-NSSAI Single Network Slice Selection Assistance Information, single network slice selection assistance information
  • the terminal may not report the value of the network slice, but report the index of the ID. value.
  • the slice information includes an index value of a slice identifier in the slice identifier set supported by the cell accessed by the terminal.
  • the set of slice identifiers 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 an index value of a certain S-NSSAI in the NSSAI set.
  • the random access report is further included in at least one synchronization signal block (SSB) or at least one channel state information reference signal (Channel-state information Reference Signal, CSI-RS) related The number of attempted preamble transmissions and/or preamble collision information in the random access process.
  • SSB synchronization signal block
  • CSI-RS channel state information reference signal
  • the number of attempts to send the preamble in the random access process is too many, for example, exceeds a certain threshold, it can be determined that the random access resources allocated to the slice for the random access performed by the terminal are too few, and can be increased.
  • the random access resource corresponding to the slice is too few, and can be increased.
  • the random access report of the terminal includes slice information of services related to the random access performed by the terminal, which can assist the network to allocate random access resources according to the slice information, and optimize the allocation method of random access resources.
  • FIG. 10 is a schematic flowchart of a method 300 for processing random access information according to an embodiment of the present application.
  • the method can optionally be applied to the system shown in Figure 1, but is not limited thereto.
  • the method includes at least some of the following.
  • the network device receives a random access report, where the random access report includes slice information of services related to the random access performed by the terminal;
  • the network device determines, according to the random access report, whether to adjust the random access resource corresponding to the slice information.
  • the network device after receiving the random access report sent by one or more terminals, the network device can correspondingly adjust the allocation ratio of random access resources on different slices according to the content therein.
  • 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, the base station serving cell 1 can know that slice 1 The number of allocated random access resources is insufficient, and then the number of random access resources is optimized. 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 preamble sending is set to true.
  • the content of the random access report reported by multiple terminals includes: sending a preamble to SSB1 twice, the service slice ID is 2, and the collision value of the previous preamble sending is set to true.
  • the network device may increase the number of ROs or preambles for slice 1 and decrease the number of ROs or preambles for slice 2. For example, after optimization, the number of preambles of slice 1 under each SSB is 25, and the number of preambles of slice 2 under each SSB is 25.
  • 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.
  • the identifier for identifying a network slice may be an S-NSSAI identifying a network slice.
  • the slice information includes an index value of a slice identifier in the slice identifier set supported by the cell accessed by the terminal.
  • the set of slice identifiers 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 an index value of a certain S-NSSAI in the NSSAI set.
  • the random access report further includes the number of times and/or the preamble that has been tried in the random access process related to at least one SSB or at least one CSI-RS. Collision information.
  • the network device may determine that the random access resources allocated to the slice for the random access performed by the terminal are too few, The random access resource corresponding to the slice can be increased.
  • the network device determines, according to the random access report, whether to adjust the random access resource corresponding to the slice information, including:
  • the network device determines whether to adjust the number of preambles and/or the number of ROs corresponding to the slice information according to the number of times of sending the preamble and/or the preamble collision information.
  • the method for processing random access information is a method for optimizing random access based on terminal feedback, which can help the network to optimize the size of random access resources allocated to different slices, so as to improve the overall performance of terminals in different 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 retransmitted, and the longer the random access delay is.
  • FIG. 13 is a schematic block diagram of a terminal 400 according to an embodiment of the present application.
  • the terminal 400 may include:
  • the sending unit 410 is configured to send a random access report, where the random access report includes slice information of services related to the random access performed by the terminal.
  • 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.
  • the slice information includes an index value of a slice identifier in the slice identifier set supported by the cell accessed by the terminal.
  • the random access report further includes a preamble that has been tried in a random access process related to at least one synchronization signal block SSB or at least one channel state information reference signal CSI-RS. number of transmissions and/or preamble collision information.
  • the terminal 400 in this embodiment of the present application can implement the corresponding functions of the terminal in the foregoing method embodiments.
  • the terminal 400 in this embodiment of the present application can implement the corresponding functions of the terminal in the foregoing method embodiments.
  • the terminal 400 can implement the corresponding processes, functions, implementations, and beneficial effects of each module (sub-module, unit, or component, etc.) in the terminal 400, reference may be made to the corresponding descriptions in the foregoing method embodiments, which will not be repeated here.
  • each module (submodule, unit or component, etc.) in the terminal 400 of the application embodiment may be implemented by different modules (submodule, unit or component, etc.), or may be implemented by the same module (submodule, unit or component, etc.) implementation.
  • 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:
  • a receiving unit 510 configured to receive a random access report, where the random access report includes slice information of services related to the random access performed by the terminal;
  • the processing unit 520 is configured to determine, according to the random access report, whether to adjust the random access resource corresponding to the slice information.
  • 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.
  • the slice information includes an index value of a slice identifier in the slice identifier set supported by the cell accessed by the terminal.
  • the random access report further includes a preamble that has been tried in a random access process related to at least one synchronization signal block SSB or at least one channel state information reference signal CSI-RS. number of transmissions and/or preamble collision information.
  • the processing unit 520 is specifically configured to determine whether to adjust the number of preambles and/or random access corresponding to the slice information according to the number of times the preamble is sent and/or the preamble collision information. The number of opportunity ROs.
  • the network device 500 in this embodiment of the present application can implement the corresponding functions of the network device in the foregoing method embodiments.
  • the corresponding processes, functions, implementations, and beneficial effects of each module (submodule, unit, or component, etc.) in the network device 500 reference may be made to the corresponding descriptions in the foregoing method embodiments, which will not be repeated here.
  • each module (submodule, unit, or component, etc.) in the network device 500 of the application embodiment may be implemented by different modules (submodule, unit, or component, etc.), or may be implemented by the same module Module (submodule, unit or component, etc.) implementation.
  • FIG. 15 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, so that the communication device 600 implements the methods in the embodiments of the present application.
  • the communication device 600 may further include a memory 620 .
  • the processor 610 may call and run a computer program from the memory 620, so that the communication device 600 implements the methods in the embodiments of the present application.
  • the memory 620 may be a separate device independent of the processor 610 , or may be integrated in the processor 610 .
  • 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 other Information or data sent by a device.
  • the transceiver 630 may include a transmitter and a receiver.
  • the transceiver 630 may further include antennas, and the number of the antennas may be one or more.
  • the communication device 600 may be the network device of this 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 is not repeated here for brevity.
  • the communication device 600 may be a terminal of this embodiment of the present application, and the communication device 600 may implement corresponding processes implemented by the terminal in each method of this embodiment of the present application, which is not repeated here for brevity.
  • FIG. 16 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, so as to implement the method in the embodiments of the present application.
  • 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.
  • the memory 720 may be a separate device independent of the processor 710 , or may be integrated in the processor 710 .
  • 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 acquire information or data sent by other devices or chips.
  • the chip 700 may further include an output interface 740 .
  • the processor 710 can control the output interface 740 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.
  • the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiment of the present application, which is not repeated here for brevity.
  • the chip can be applied to the terminal in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the terminal in each method of the embodiment of the present application, which is not repeated here for brevity.
  • Chips applied to network equipment and terminals can be the same chip or different chips.
  • the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip, a system-on-chip, or a system-on-a-chip, or the like.
  • the above-mentioned processor may be a general-purpose processor, a digital signal processor (DSP), an off-the-shelf programmable gate array (field programmable gate array, FPGA), an application specific integrated circuit (ASIC) or Other programmable logic devices, transistor logic devices, discrete hardware components, etc.
  • DSP digital signal processor
  • FPGA field programmable gate array
  • ASIC application specific integrated circuit
  • the general-purpose processor mentioned above may be a microprocessor or any conventional processor or the like.
  • the memory mentioned above may be either volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically programmable Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • Volatile memory may be random access memory (RAM).
  • the memory in the embodiment of the present application may also be a static random access memory (static RAM, SRAM), a 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 connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is, 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.
  • FIG. 17 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 .
  • the terminal 810 sends a random access report, where the random access report includes slice information of services related to the random access performed by the terminal.
  • the network device 820 receives a random access report, where the random access report includes slice information of services related to the random access performed by the terminal; the network device determines, according to the random access report, whether to adjust the random access report corresponding to the slice information. into resources.
  • the terminal 810 may be used to implement the corresponding functions implemented by the terminal in the above method
  • the network device 820 may be used to implement the corresponding functions implemented by the network device in the above method. For brevity, details are not repeated here.
  • the above-mentioned embodiments it may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • 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 instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated.
  • the computer may be a general purpose computer, special purpose computer, computer network, or other programmable device.
  • the computer instructions may be stored on or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be transmitted over a wire from a website site, computer, server or data center (eg coaxial cable, optical fiber, Digital Subscriber Line (DSL)) or wireless (eg infrared, wireless, microwave, etc.) means to another website site, computer, server or data center.
  • the computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes an integration of one or more available media.
  • the available media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVD), or semiconductor media (eg, Solid State Disk (SSD)), and the like.
  • the size of the sequence numbers of the above-mentioned processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, and should not be dealt with in the embodiments of the present application. implementation constitutes any limitation.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请涉及一种随机接入信息的处理方法、终端和网络设备。该方法包括:终端发送随机接入报告,该随机接入报告中包括该终端与执行的随机接入相关的业务的切片信息。在本申请实施例中,在随机接入报告包括终端与执行的随机接入相关的业务的切片信息,可以按照切片信息分配随机接入资源,优化随机接入资源的分配方式。

Description

随机接入信息的处理方法、终端和网络设备 技术领域
本申请涉及通信领域,更具体地,涉及一种随机接入信息的处理方法、终端和网络设备。
背景技术
终端在有上行数据发送、接收下行数据和进行跟踪区域更新等情景下需要执行随机接入。在一些场景中,网络为面向不同方向的SSB分配不同的随机接入资源。例如,随机接入机会(Random access Ocassion,RO)或者随机接入前导码(random access preamble),以便终端选择与自己期望相符的同步信号块(Synchronization Signal Block,SSB)对应的随机接入资源执行随机接入。如何优化随机接入资源的分配方式是需要解决的问题。
发明内容
本申请实施例提供一种随机接入信息的处理方法、终端和网络设备,可以优化随机接入资源的分配方式。
本申请实施例提供一种随机接入信息的处理方法,包括:
终端发送随机接入报告,该随机接入报告中包括该终端与执行的随机接入相关的业务的切片信息。
可选地,在本申请实施例中,该切片信息包括用于标识一个网络切片的标识或者与网络切片有对应关系的对象的标识。
可选地,在本申请实施例中,该切片信息包括该终端所接入的小区支持的切片标识集合中一个切片标识的索引值。
可选地,在本申请实施例中,该随机接入报告中还包括在与至少一个同步信号块SSB或至少一个信道状态信息参考信号CSI-RS相关的随机接入过程中尝试过的前导码的发送次数和/或前导码碰撞信息。
本申请实施例还提供一种随机接入信息的处理方法,包括:
网络设备接收随机接入报告,该随机接入报告中包括终端与执行的随机接入相关的业务的切片信息;
该网络设备根据该随机接入报告,确定是否调整该切片信息对应的随机 接入资源。
可选地,在本申请实施例中,该切片信息包括用于标识一个网络切片的标识或者与网络切片有对应关系的对象的标识。
可选地,在本申请实施例中,该切片信息包括该终端所接入的小区支持的切片标识集合中一个切片标识的索引值。
可选地,在本申请实施例中,该随机接入报告中还包括在与至少一个同步信号块SSB或至少一个信道状态信息参考信号CSI-RS相关的随机接入过程中尝试过的前导码的发送次数和/或前导码碰撞信息。
可选地,在本申请实施例中,该网络设备根据该随机接入报告,确定是否调整该切片信息对应的随机接入资源,包括:该网络设备根据发送前导码的次数和/或前导码碰撞信息,确定是否调整该切片信息对应的前导码数目和/或随机接入时机RO数目。
本申请实施例提供一种终端,包括:
发送单元,用于发送随机接入报告,该随机接入报告中包括执行随机接入的业务的切片信息。
可选地,在本申请实施例中,该切片信息包括用于标识一个网络切片的标识或者与网络切片有对应关系的对象的标识。
可选地,在本申请实施例中,该切片信息包括该终端所接入的小区支持的切片标识集合中一个切片标识的索引值。
可选地,在本申请实施例中,该随机接入报告中还包括在与至少一个同步信号块SSB或至少一个信道状态信息参考信号CSI-RS相关的随机接入过程中尝试过的前导码的发送次数和/或前导码碰撞信息。
本申请实施例提供一种网络设备,包括:
接收单元,用于接收随机接入报告,该随机接入报告中包括执行随机接入的业务的切片信息;
处理单元,用于根据该随机接入报告,确定是否调整该切片信息对应的随机接入资源。
可选地,在本申请实施例中,该切片信息包括用于标识一个网络切片的标识或者与网络切片有对应关系的对象的标识。
可选地,在本申请实施例中,该切片信息包括该终端所接入的小区支持的切片标识集合中一个切片标识的索引值。
可选地,在本申请实施例中,该随机接入报告中还包括在与至少一个同步信号块SSB或至少一个信道状态信息参考信号CSI-RS相关的随机接入过程中尝试过的前导码的发送次数和/或前导码碰撞信息。
可选地,在本申请实施例中,该处理单元具体用于根据发送前导码的次数和/或该前导码碰撞信息,确定是否调整该切片信息对应的前导码数目和/或随机接入时机RO数目。
本申请实施例提供一种终端,包括处理器和存储器。该存储器用于存储计算机程序,该处理器用于调用并运行该存储器中存储的计算机程序,以使该终端执行上述的随机接入信息的处理方法中由终端执行的方法。
本申请实施例提供一种网络设备,包括处理器和存储器。该存储器用于存储计算机程序,该处理器用于调用并运行该存储器中存储的计算机程序,以使该网络设备执行上述的随机接入信息的处理方法中由网络设备执行的方法。
本申请实施例提供一种芯片,用于实现上述的随机接入信息的处理方法。
具体地,该芯片包括:处理器,用于从存储器中调用并运行计算机程序,使得安装有该芯片的设备执行上述的随机接入信息的处理方法。
本申请实施例提供一种计算机可读存储介质,用于存储计算机程序,当该计算机程序被设备运行时使得该设备执行上述的随机接入信息的处理方法。
本申请实施例提供一种计算机程序产品,包括计算机程序指令,该计算机程序指令使得计算机执行上述的随机接入信息的处理方法。
本申请实施例提供一种计算机程序,当其在计算机上运行时,使得计算机执行上述的随机接入信息的处理方法。
本申请实施例,在随机接入报告包括终端与执行的随机接入相关的业务的切片信息,可以按照切片信息分配随机接入资源,优化随机接入资源的分配方式。
附图说明
图1是根据本申请实施例的应用场景的示意图。
图2是根据本申请一实施例随机接入信息的处理方法的示意性流程图。
图3是包含MAC-RAR的MAC-PDU的示例图。
图4是RAR中的具体内容的示例图。
图5是一种随机接入过程的示意图。
图6是一种网络切片的示意图。
图7和图8是基于SSB的随机接入资源划分方式的示意图。
图9是随机接入优化的示意图。
图10是根据本申请另一实施例随机接入信息的处理方法的示意性流程图。
图11是随机接入资源数目优化的示例图。
图12是随机接入报告的示例图。
图13是根据本申请一实施例的终端的示意性框图。
图14是根据本申请一实施例的网络设备的示意性框图。
图15是根据本申请实施例的通信设备示意性框图。
图16是根据本申请实施例的芯片的示意性框图。
图17是根据本申请实施例的通信系统的示意性框图。
具体实施方式
下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信系统,例如:全球移动通讯(Global System of Mobile communication,GSM)系统、码分多址(Code Division Multiple Access,CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access,WCDMA)系统、通用分组无线业务(General Packet Radio Service,GPRS)、长期演进(Long Term Evolution,LTE)系统、先进的长期演进(Advanced long term evolution,LTE-A)系统、新无线(New Radio,NR)系统、NR系统的演进系统、非授权频谱上的LTE(LTE-based access to unlicensed spectrum,LTE-U)系统、非授权频谱上的NR(NR-based access to unlicensed spectrum,NR-U)系统、非地面通信网络(Non-Terrestrial Networks,NTN)系统、通用移动通信系统(Universal Mobile Telecommunication System,UMTS)、无线局域网(Wireless Local Area Networks,WLAN)、无线保真(Wireless Fidelity,WiFi)、第五代通信(5th-Generation,5G)系统或其他通信系统等。
通常来说,传统的通信系统支持的连接数有限,也易于实现,然而,随着通信技术的发展,移动通信系统将不仅支持传统的通信,还将支持例如,设备到设备(Device to Device,D2D)通信,机器到机器(Machine to Machine,M2M)通信,机器类型通信(Machine Type Communication,MTC),车辆间(Vehicle to Vehicle,V2V)通信,或车联网(Vehicle to everything,V2X)通信等,本申请实施例也可以应用于这些通信系统。
可选地,本申请实施例中的通信系统可以应用于载波聚合(Carrier Aggregation,CA)场景,也可以应用于双连接(Dual Connectivity,DC)场景,还可以应用于独立(Standalone,SA)布网场景。
可选地,本申请实施例中的通信系统可以应用于非授权频谱,其中,非授权频谱也可以认为是共享频谱;或者,本申请实施例中的通信系统也可以应用于授权频谱,其中,授权频谱也可以认为是非共享频谱。
本申请实施例结合网络设备和终端设备描述了各个实施例,其中,终端设备也可以称为用户设备(User Equipment,UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置等。
终端设备可以是WLAN中的站点(STAION,ST),可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol,SIP)电话、无线本地环路(Wireless Local Loop,WLL)站、个人数字处理(Personal Digital Assistant,PDA)设备、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、下一代通信系统例如NR网络中的终端设备,或者未来演进的公共陆地移动网络(Public Land Mobile Network,PLMN)网络中的终端设备等。
在本申请实施例中,终端设备可以部署在陆地上,包括室内或室外、手持、穿戴或车载;也可以部署在水面上(如轮船等);还可以部署在空中(例如飞机、气球和卫星上等)。
在本申请实施例中,终端设备可以是手机(Mobile Phone)、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(Virtual Reality,VR)终端设备、增强现实(Augmented Reality,AR)终端设备、工业控制(industrial control)中的无线终端设备、无人驾驶(self driving)中的无线终端设备、远程医疗(remote medical)中的无线终端设备、智能电网(smart grid)中的无线终端 设备、运输安全(transportation safety)中的无线终端设备、智慧城市(smart city)中的无线终端设备或智慧家庭(smart home)中的无线终端设备等。
作为示例而非限定,在本申请实施例中,该终端设备还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备,是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称,如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上,或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备,更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能,例如:智能手表或智能眼镜等,以及只专注于某一类应用功能,需要和其它设备如智能手机配合使用,如各类进行体征监测的智能手环、智能首饰等。
在本申请实施例中,网络设备可以是用于与移动设备通信的设备,网络设备可以是WLAN中的接入点(Access Point,AP),GSM或CDMA中的基站(Base Transceiver Station,BTS),也可以是WCDMA中的基站(NodeB,NB),还可以是LTE中的演进型基站(Evolutional Node B,eNB或eNodeB),或者中继站或接入点,或者车载设备、可穿戴设备以及NR网络中的网络设备(gNB)或者未来演进的PLMN网络中的网络设备或者NTN网络中的网络设备等。
作为示例而非限定,在本申请实施例中,网络设备可以具有移动特性,例如网络设备可以为移动的设备。可选地,网络设备可以为卫星、气球站。例如,卫星可以为低地球轨道(low earth orbit,LEO)卫星、中地球轨道(medium earth orbit,MEO)卫星、地球同步轨道(geostationary earth orbit,GEO)卫星、高椭圆轨道(High Elliptical Orbit,HEO)卫星等。可选地,网络设备还可以为设置在陆地、水域等位置的基站。
在本申请实施例中,网络设备可以为小区提供服务,终端设备通过该小区使用的传输资源(例如,频域资源,或者说,频谱资源)与网络设备进行通信,该小区可以是网络设备(例如基站)对应的小区,小区可以属于宏基站,也可以属于小小区(Small cell)对应的基站,这里的小小区可以包括:城市小区(Metro cell)、微小区(Micro cell)、微微小区(Pico cell)、毫微微小区(Femto cell)等,这些小小区具有覆盖范围小、发射功率低的特点,适用于提供高速率的数据传输服务。
图1示例性地示出了一种通信系统100。该通信系统包括一个网络设备110和两个终端设备120。可选地,该通信系统100可以包括多个网络设备110,并且每个网络设备110的覆盖范围内可以包括其它数量的终端设备120,本申请实施例对此不做限定。
可选地,该通信系统100还可以包括移动性管理实体(Mobility Management Entity,MME)、接入与移动性管理功能(Access and Mobility Management Function,AMF)等其他网络实体,本申请实施例对此不作限定。
其中,网络设备又可以包括接入网设备和核心网设备。即无线通信系统还包括用于与接入网设备进行通信的多个核心网。接入网设备可以是长期演进(long-term evolution,LTE)系统、下一代(移动通信系统)(next radio,NR)系统或者授权辅助接入长期演进(authorized auxiliary access long-term evolution,LAA-LTE)系统中的演进型基站(evolutional node B,简称可以为eNB或e-NodeB)宏基站、微基站(也称为“小基站”)、微微基站、接入站点(access point,AP)、传输站点(transmission point,TP)或新一代基站(new generation Node B,gNodeB)等。
应理解,本申请实施例中网络/系统中具有通信功能的设备可称为通信设备。以图1示出的通信系统为例,通信设备可包括具有通信功能的网络设备和终端设备,网络设备和终端设备可以为本发明实施例中所述的具体设备,此处不再赘述;通信设备还可包括通信系统中的其他设备,例如网络控制器、移动管理实体等其他网络实体,本申请实施例中对此不做限定。
应理解,本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”,仅仅是一种描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B这三种情况。另外,本文中字符“/”,一般表示前后关联对象是一种“或”的关系。
应理解,在本申请的实施例中提到的“指示”可以是直接指示,也可以是间接指示,还可以是表示具有关联关系。举例说明,A指示B,可以表示A直接指示B,例如B可以通过A获取;也可以表示A间接指示B,例如A指示C,B可以通过C获取;还可以表示A和B之间具有关联关系。
在本申请实施例的描述中,术语“对应”可表示两者之间具有直接对应或间接对应的关系,也可以表示两者之间具有关联关系,也可以是指示与被 指示、配置与被配置等关系。
为便于理解本申请实施例的技术方案,以下对本申请实施例的相关技术进行说明,以下相关技术作为可选方案与本申请实施例的技术方案可以进行任意结合,其均属于本申请实施例的保护范围。
图2是根据本申请一实施例随机接入信息的处理方法200的示意性流程图。该方法可选地可以应用于图1所示的系统,但并不仅限于此。该方法包括以下内容的至少部分内容。
S210、终端发送随机接入报告,该随机接入报告中包括该终端与执行的随机接入相关的业务的切片信息。
在一种示例中,终端在有上行数据发送、接收下行数据和进行跟踪区域更新等情景下需要进行随机接入。随机接入分为两种:基于碰撞的和免于碰撞的。
如图3所示,在基于碰撞的随机接入过程中,终端在一个随机接入时频资源上(RACH occasion)上使用一个公共的随机接入前导码(RACH preamble)发送消息1(msg1)。之后,终端用RA(Random Access,随机接入)-RNTI(Radio Network Temporary Identifier,网络临时标识符)在物理下行控制信道(Physical Downlink Control Channel,PDCCH)上监听网络关于随机接入响应(random access response,RAR)的PDCCH指示信息。当发现关于RAR的PDCCH指示信息后,终端会在PDCCH指示信息给出的时频位置上解码RAR。如果RAR中包括终端发送的随机接入前导码信息,终端继而会应用RAR中与该随机接入前导码对应的信息进而发送消息3(msg3)。例如,图3中的subPDU表示子PDU(Protocol Data Unit,协议数据单元),Padding(opt)表示填充是可选项。终端发现在MAC subPDU3这种格式中包括与自身preamble ID相符的一个子头,后续可以使用相关的MAC RAR中的内容发送msg3。
如图4所示,为RAR包括的具体内容的示例。RAR中可以包括Timing Advance Command(定时提前命令)、UL Grant(上行授权)、Temporary(临时)C-RNTI等。
在包含有无线资源控制(Radio Resource Control,RRC)连接建立请求(RRCSetupRequest)等RRC命令的msg3中,终端需要携带有自身UE ID(identification,标识)。在具有众多终端做随机接入的情况下,可能会有其他 终端在上行授权(uplink grant,UL grant)指示的时频位置上也发送msg3(携带该终端UE ID)尝试接入网络。该情况下,终端之间会发生随机接入碰撞,网络在消息4(msg4)中可以只会携带有其中一个UE的ID允许其接入网络。
如图5所示,为随机接入过程的一种示例:终端1和终端2向网络设备例如gNB发送消息1(msg1),其中可以包括前导码(preamble)。gNB向终端1和终端2返回消息2(msg2),其中包括随机接入响应RAR,RAR中包括上行授权(UL grant)。终端1和终端2向网络设备发送消息3(msg3),例如RRC连接建立请求(RRCSetupRequest),其中可以包括终端标识,例如UE ID#1和UE ID#2。gNB返回RRC连接建立结果,其中可以包括成功建立拦截的终端标识,例如UE ID#1。这时,gNB可以向终端1返回RRC连接建立成功的消息,向终端2返回RRC连接建立失败的消息。
网络切片可以包括RAN(Radio Access Network,无线接入网)部分和CN(Core Network,核心网)部分。通信网络对网络切片的支持依赖于将隶属于不同切片的的数据通信由不同的PDU会话(session)承载。不同的切片具有不同的网络切片选择协助信息(Network Slice Selection Assistance Information,NSSAI),以及不同的传输性能要求如可靠性、传输时延、传输速率等。在实际应用中,网络可以将eMBB(enhanced Mobile Broadband,增强移动宽带)和URLLC(Ultra-low latency communication,超高可靠性与超低时延)的业务在不同的PDU会话上进行承载。每个不同的PDU会话可以具有多个Qos(Quality of Service,服务质量)流(flow)。
例如,如图6所示,在具体通信中,在下行方向,核心网的NAS层SDF(业务数据流,Service data flow)模板(template)将来自应用层的不同的数据包进行分类,映射至不同PDU会话(session)中的不同QoS流(QoS flow),并且使QoS流在不同的PDU会话中发送给基站。其中,SDF模板可以在UPF(User Plane Function,用户面功能)中。基站根据QoS流的ID信息将QoS流映射至不同的DRB(Data Radio Bearer,数据无线承载)在空口上发送给终端。同理,对于上行数据,类似的操作也被实施。图6中的AN(Access Network,接入网)资源可以包括无线承载DRB。QoS规则(rules)可以包括:将应用层的数据包例如UL数据包根据QoS要求的不同要求,映射到不同的QoS流,并应用不同的QoS流标记。同一QoS流中的所有数据包标记相同的QoS流ID。
在一种示例中,可以基于SSB划分随机接入资源。在5G NR中,因为波束赋形技术的大规模应用,终端在执行随机接入时希望在特定的波束上接收网络回复的msg2/msg4,以提升信息接收功率。在Rel-15NR中,网络为面向不同方向的SSB分配不同的随机接入资源(如RO或者随机接入前导码),以便终端选择与自己期望相符的SSB的对应的随机接入资源执行随机接入。当网络接收到终端的msg1后,根据终端使用的随机接入前导码和/或随机接入时频资源(RACH ocassion)判断终端期望的发送下行信息的SSB。
参见图7,在一种示例中,如果面向SSB的随机接入机会(例如,ssb-perRACH-OccasionAndCB-PreamblesPerSSB)设为1:52,Msg1-FDM设为2,则属于SSB 0~SSB 3的RO资源分别为RO 0~RO3。其中,SSB 0~SSB3应用的前导码集合相同,例如preamble 0~51。此外,在本示例中,SSB0和SSB1对应的SFN(System Frame Number,系统帧号)为5,子帧Subframe为9;SSB2和SSB3对应的SFN为9,子帧Subframe为9。
参见图8,在一种示例中,如果面向SSB的随机接入机会(例如,ssb-perRACH-OccasionAndCB-PreamblesPerSSB)设为4:13,Msg1-FDM设为1,SSB0~SSB 4共享每一个RO,但应用不同的前导码集合。例如,SSB0的前导码集合为preamble 0~12;SSB1的前导码集合为preamble 16~28;SSB2的前导码集合为preamble 32~44;SSB3的前导码集合为preamble 48~60。此外,在本示例中,SSB0~SSB3对应的SFN为5,子帧Subframe为9。
为了在随机接入阶段使得面向不同切片业务发起随机接入的终端不互相发生随机接入冲突,可以按照不同切片划分随机接入资源,实现随机接入优化。
网络在配置随机接入资源和相关参数的时候可能存在不合理,影响终端随机接入体验的情况下。网络需要终端上报以修正配置错误。本实施例中,可以优化终端需要上报的内容。
如图9所示,为上报流程的示例。在随机接入过程之后,网络设备例如gNB可以向终端例如UE发送信息请求(Information Request),其中的随机接入报告请求设置为真(ra-ReportReq is set as true)。终端可以向网络设备返回信息响应(Information Response),其中可以包括随机接入报告,例如ra-ReportList-r16。
上报内容可以包括在面向某SSB做随机接入中尝试过的随机接入前导码 的发送次数(NumberOfPreamblesSentOnSSB)、相应的每次尝试过程中是否遇到碰撞的指示。在本申请实施例中,可以在随机接入报告中加入终端与执行的随机接入相关的业务的切片信息。这样,网络设备可以根据随机接入前导码的发送次数、碰撞的指示、切片信息等,确定是否调整该切片信息对应的随机接入资源。例如调整随机接入时机数目和/或随机接入前导码数目等。
可选地,在本申请实施例中,该切片信息包括用于标识一个网络切片的标识或者与网络切片有对应关系的对象的标识。
示例性地,用于标识一个网络切片的标识可以为标识一个网络切片的S-NSSAI(Single Network Slice Selection Assistance Information,单一网络切片选择协助信息)。
示例性地,如果小区为每个网络切片ID从小到大排序后赋予ID从1,2,3,4……的索引号,终端在上报时可以不上报网络切片的值,而上报ID的索引值。
可选地,在本申请实施例中,该切片信息包括该终端所接入的小区支持的切片标识集合中一个切片标识的索引值。
示例性地,终端所接入的小区支持的切片标识集合可以为NSSAI集合。切片标识集合中一个切片标识的索引值可以为NSSAI集合中某个S-NSSAI的索引值。
可选地,在本申请实施例中,该随机接入报告中还包括在与至少一个同步信号块(SSB)或至少一个信道状态信息参考信号(Channel-state information Reference Signal,CSI-RS)相关的随机接入过程中尝试过的前导码的发送次数和/或前导码碰撞信息。
示例性地,如果执行随机接入过程中尝试过的前导码的发送次数过多,例如超过某个阈值,可以判定为该终端执行随机接入的切片分配的随机接入资源过少,可以增加该切片对应的随机接入资源。
本申请实施例中,在终端的随机接入报告中包括终端与执行的随机接入相关的业务的切片信息,可以辅助网络按照切片信息分配随机接入资源,优化随机接入资源的分配方式。
图10是根据本申请一实施例随机接入信息的处理方法300的示意性流程图。该方法可选地可以应用于图1所示的系统,但并不仅限于此。该方法包括以下内容的至少部分内容。
S310、网络设备接收随机接入报告,该随机接入报告中包括终端与执行的随机接入相关的业务的切片信息;
S320、该网络设备根据该随机接入报告,确定是否调整该切片信息对应的随机接入资源。
在本实施例中,网络设备收到一个或多个终端发送的随机接入报告后,可以根据其中的内容相应的调整随机接入资源在不同切片上的分配比例。
例如,如图11和图12所示,切片1在每个SSB下的前导码数目为10,切片2在每个SSB下的前导码数目为40。如果有多个终端报告曾经在小区1上面向切片1执行随机接入,在尝试发送10+次随机接入前导码后才最终接入网络,那么提供小区1服务的基站可知晓为该切片1分配的随机接入资源数目不够用,继而对随机接入资源数目进行优化。例如,多个终端上报的随机接入报告内容包含:面向SSB1发送10次前导码、业务切片ID为1以及前9次前导码发送碰撞值设为真。并且,还有多个终端上报的随机接入报告内容包含:面向SSB1发送2次前导码、业务切片ID为2以及前1次前导码发送碰撞值设为真。网络设备可以增加切片1的RO数目或前导码数目,减少切片2的RO数目或前导码数目。例如,优化后切片1在每个SSB下的前导码数目为25,切片2在每个SSB下的前导码数目为25。
可选地,在本申请实施例中,该切片信息包括用于标识一个网络切片的标识或者与网络切片有对应关系的对象的标识。
示例性地,用于标识一个网络切片的标识可以为标识一个网络切片的S-NSSAI。
可选地,在本申请实施例中,该切片信息包括该终端所接入的小区支持的切片标识集合中一个切片标识的索引值。
示例性地,终端所接入的小区支持的切片标识集合可以为NSSAI集合。切片标识集合中一个切片标识的索引值可以为NSSAI集合中某个S-NSSAI的索引值。
可选地,在本申请实施例中,该随机接入报告中还包括在与至少一个SSB或至少一个CSI-RS相关的随机接入过程中尝试过的前导码的发送次数和/或前导码碰撞信息。
示例性地,如果执行随机接入过程中尝试过的前导码的发送次数过多,例如超过某个阈值,网络设备可以判定为该终端执行随机接入的切片分配的 随机接入资源过少,可以增加该切片对应的随机接入资源。
可选地,在本申请实施例中,该网络设备根据该随机接入报告,确定是否调整该切片信息对应的随机接入资源,包括:
该网络设备根据发送前导码的次数和/或前导码碰撞信息,确定是否调整该切片信息对应的前导码数目和/或RO数目。
本实施例的网络设备执行方法300的具体示例可以参见上述方法200的中关于网络设备例如基站的相关描述,为了简洁,在此不再赘述。
在本申请实施例中,随机接入信息的处理方法是一种基于终端反馈进行随机接入优化的方法,可以帮助网络优化为不同切片分配的随机接入资源大小,以提高不同切片终端的总体随机接入体验,以及目标为关键切片的终端的随机接入体验。随机接入体验的高低主要与接入碰撞概率低或者高有关。一般来说,碰撞的越多,需要重新发送前导码的次数也越多,随机接入的时延也越大。
图13是根据本申请一实施例的终端400的示意性框图。该终端400可以包括:
发送单元410,用于发送随机接入报告,该随机接入报告中包括终端与执行的随机接入相关的业务的切片信息。
可选地,在本申请实施例中,该切片信息包括用于标识一个网络切片的标识或者与网络切片有对应关系的对象的标识。
可选地,在本申请实施例中,该切片信息包括该终端所接入的小区支持的切片标识集合中一个切片标识的索引值。
可选地,在本申请实施例中,该随机接入报告中还包括在与至少一个同步信号块SSB或至少一个信道状态信息参考信号CSI-RS相关的随机接入过程中尝试过的前导码的发送次数和/或前导码碰撞信息。
本申请实施例的终端400能够实现前述的方法实施例中的终端的对应功能。该终端400中的各个模块(子模块、单元或组件等)对应的流程、功能、实现方式以及有益效果,可参见上述方法实施例中的对应描述,在此不再赘述。
需要说明,关于申请实施例的终端400中的各个模块(子模块、单元或组件等)所描述的功能,可以由不同的模块(子模块、单元或组件等)实现,也可以由同一个模块(子模块、单元或组件等)实现。
图14是根据本申请一实施例的网络设备500的示意性框图。该网络设备500可以包括:
接收单元510,用于接收随机接入报告,该随机接入报告中包括终端与执行的随机接入相关的业务的切片信息;
处理单元520,用于根据该随机接入报告,确定是否调整该切片信息对应的随机接入资源。
可选地,在本申请实施例中,该切片信息包括用于标识一个网络切片的标识或者与网络切片有对应关系的对象的标识。
可选地,在本申请实施例中,该切片信息包括该终端所接入的小区支持的切片标识集合中一个切片标识的索引值。
可选地,在本申请实施例中,该随机接入报告中还包括在与至少一个同步信号块SSB或至少一个信道状态信息参考信号CSI-RS相关的随机接入过程中尝试过的前导码的发送次数和/或前导码碰撞信息。
可选地,在本申请实施例中,该处理单元520具体用于根据发送前导码的次数和/或该前导码碰撞信息,确定是否调整该切片信息对应的前导码数目和/或随机接入时机RO数目。
本申请实施例的网络设备500能够实现前述的方法实施例中的网络设备的对应功能。该网络设备500中的各个模块(子模块、单元或组件等)对应的流程、功能、实现方式以及有益效果,可参见上述方法实施例中的对应描述,在此不再赘述。
需要说明,关于申请实施例的网络设备500中的各个模块(子模块、单元或组件等)所描述的功能,可以由不同的模块(子模块、单元或组件等)实现,也可以由同一个模块(子模块、单元或组件等)实现。
图15是根据本申请实施例的通信设备600示意性结构图。该通信设备600包括处理器610,处理器610可以从存储器中调用并运行计算机程序,以使通信设备600实现本申请实施例中的方法。
可选地,如图15所示,通信设备600还可以包括存储器620。其中,处理器610可以从存储器620中调用并运行计算机程序,以使通信设备600实现本申请实施例中的方法。
其中,存储器620可以是独立于处理器610的一个单独的器件,也可以集成在处理器610中。
可选地,如图15所示,通信设备600还可以包括收发器630,处理器610可以控制该收发器630与其他设备进行通信,具体地,可以向其他设备发送信息或数据,或接收其他设备发送的信息或数据。
其中,收发器630可以包括发射机和接收机。收发器630还可以进一步包括天线,天线的数量可以为一个或多个。
可选地,该通信设备600可为本申请实施例的网络设备,并且该通信设备600可以实现本申请实施例的各个方法中由网络设备实现的相应流程,为了简洁,在此不再赘述。
可选地,该通信设备600可为本申请实施例的终端,并且该通信设备600可以实现本申请实施例的各个方法中由终端实现的相应流程,为了简洁,在此不再赘述。
图16是根据本申请实施例的芯片700的示意性结构图。该芯片700包括处理器710,处理器710可以从存储器中调用并运行计算机程序,以实现本申请实施例中的方法。
可选地,如图16所示,芯片700还可以包括存储器720。其中,处理器710可以从存储器720中调用并运行计算机程序,以实现本申请实施例中由终端或者网络设备执行的方法。
其中,存储器720可以是独立于处理器710的一个单独的器件,也可以集成在处理器710中。
可选地,该芯片700还可以包括输入接口730。其中,处理器710可以控制该输入接口730与其他设备或芯片进行通信,具体地,可以获取其他设备或芯片发送的信息或数据。
可选地,该芯片700还可以包括输出接口740。其中,处理器710可以控制该输出接口740与其他设备或芯片进行通信,具体地,可以向其他设备或芯片输出信息或数据。
可选地,该芯片可应用于本申请实施例中的网络设备,并且该芯片可以实现本申请实施例的各个方法中由网络设备实现的相应流程,为了简洁,在此不再赘述。
可选地,该芯片可应用于本申请实施例中的终端,并且该芯片可以实现本申请实施例的各个方法中由终端实现的相应流程,为了简洁,在此不再赘述。
应用于网络设备和终端的芯片可以是相同的芯片或不同的芯片。
应理解,本申请实施例提到的芯片还可以称为系统级芯片,系统芯片,芯片系统或片上系统芯片等。
上述提及的处理器可以是通用处理器、数字信号处理器(digital signal processor,DSP)、现成可编程门阵列(field programmable gate array,FPGA)、专用集成电路(application specific integrated circuit,ASIC)或者其他可编程逻辑器件、晶体管逻辑器件、分立硬件组件等。其中,上述提到的通用处理器可以是微处理器或者也可以是任何常规的处理器等。
上述提及的存储器可以是易失性存储器或非易失性存储器,或可包括易失性和非易失性存储器两者。其中,非易失性存储器可以是只读存储器(read-only memory,ROM)、可编程只读存储器(programmable ROM,PROM)、可擦除可编程只读存储器(erasable PROM,EPROM)、电可擦除可编程只读存储器(electrically EPROM,EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory,RAM)。
应理解,上述存储器为示例性但不是限制性说明,例如,本申请实施例中的存储器还可以是静态随机存取存储器(static RAM,SRAM)、动态随机存取存储器(dynamic RAM,DRAM)、同步动态随机存取存储器(synchronous DRAM,SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM,DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM,ESDRAM)、同步连接动态随机存取存储器(synch link DRAM,SLDRAM)以及直接内存总线随机存取存储器(Direct Rambus RAM,DR RAM)等等。也就是说,本申请实施例中的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
图17是根据本申请实施例的通信系统800的示意性框图。该通信系统800包括终端810和网络设备820。
终端810发送随机接入报告,该随机接入报告中包括该终端与执行的随机接入相关的业务的切片信息。
网络设备820接收随机接入报告,该随机接入报告中包括终端与执行的随机接入相关的业务的切片信息;该网络设备根据该随机接入报告,确定是否调整该切片信息对应的随机接入资源。
其中,该终端810可以用于实现上述方法中由终端实现的相应的功能, 以及该网络设备820可以用于实现上述方法中由网络设备实现的相应的功能。为了简洁,在此不再赘述。
在上述实施例中,可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时,可以全部或部分地以计算机程序产品的形式实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行该计算机程序指令时,全部或部分地产生按照本申请实施例所述的流程或功能。该计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。该计算机指令可以存储在计算机可读存储介质中,或者从一个计算机可读存储介质向另一个计算机可读存储介质传输,例如,该计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(Digital Subscriber Line,DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。该计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。该可用介质可以是磁性介质,(例如,软盘、硬盘、磁带)、光介质(例如,DVD)、或者半导体介质(例如固态硬盘(Solid State Disk,SSD))等。
应理解,在本申请的各种实施例中,上述各过程的序号的大小并不意味着执行顺序的先后,各过程的执行顺序应以其功能和内在逻辑确定,而不应对本申请实施例的实施过程构成任何限定。
所属领域的技术人员可以清楚地了解到,为描述的方便和简洁,上述描述的系统、装置和单元的具体工作过程,可以参考前述方法实施例中的对应过程,在此不再赘述。
以上所述仅为本申请的具体实施方式,但本申请的保护范围并不局限于此,任何熟悉本技术领域的技术人员在本申请揭露的技术范围内,可轻易想到变化或替换,都应涵盖在本申请的保护范围之内。因此,本申请的保护范围应以该权利要求的保护范围为准。

Claims (28)

  1. 一种随机接入信息的处理方法,包括:
    终端发送随机接入报告,所述随机接入报告中包括所述终端与执行的随机接入相关的业务的切片信息。
  2. 根据权利要求1所述的方法,其中,所述切片信息包括用于标识一个网络切片的标识或者与网络切片有对应关系的对象的标识。
  3. 根据权利要求1所述的方法,其中,所述切片信息包括所述终端所接入的小区支持的切片标识集合中一个切片标识的索引值。
  4. 根据权利要求1至3中任一项所述的方法,其中,所述随机接入报告中还包括在与至少一个同步信号块SSB或一个信道状态信息参考信号CSI-RS相关的随机接入过程中尝试过的前导码的发送次数和/或前导码碰撞信息。
  5. 一种随机接入信息的处理方法,包括:
    网络设备接收随机接入报告,所述随机接入报告中包括终端与执行随机接入相关的业务的切片信息;
    所述网络设备根据所述随机接入报告,确定是否调整所述切片信息对应的随机接入资源。
  6. 根据权利要求5所述的方法,其中,所述切片信息包括用于标识一个网络切片的标识或者与网络切片有对应关系的对象的标识。
  7. 根据权利要求5所述的方法,其中,所述切片信息包括所述终端所接入的小区支持的切片标识集合中一个切片标识的索引值。
  8. 根据权利要求5至7中任一项所述的方法,其中,所述随机接入报告中还包括在与至少一个同步信号块SSB或至少一个信道状态信息参考信号CSI-RS相关的随机接入过程中尝试过的前导码的发送次数和/或前导码碰撞信息。
  9. 根据权利要求8所述的方法,其中,所述网络设备根据所述随机接入报告,确定是否调整所述切片信息对应的随机接入资源,包括:
    所述网络设备根据所述发送前导码的次数和/或所述前导码碰撞信息,确定是否调整所述切片信息对应的前导码数目和/或随机接入时机RO数目。
  10. 一种终端,包括:
    发送单元,用于发送随机接入报告,所述随机接入报告中包括所述终端与执行的随机接入相关的业务的切片信息。
  11. 根据权利要求10所述的终端,其中,所述切片信息包括用于标识一个网络切片的标识或者与网络切片有对应关系的对象的标识。
  12. 根据权利要求10所述的终端,其中,所述切片信息包括所述终端所接入的小区支持的切片标识集合中一个切片标识的索引值。
  13. 根据权利要求10至12中任一项所述的终端,其中,所述随机接入报告中还包括在与至少一个同步信号块SSB或至少一个信道状态信息参考信号CSI-RS相关的随机接入过程中尝试过的前导码的发送次数和/或前导码碰撞信息。
  14. 一种网络设备,包括:
    接收单元,用于接收随机接入报告,所述随机接入报告中包括终端与执行的随机接入相关的业务的切片信息;
    处理单元,用于根据所述随机接入报告,确定是否调整所述切片信息对应的随机接入资源。
  15. 根据权利要求14所述的网络设备,其中,所述切片信息包括用于标识一个网络切片的标识或者与网络切片有对应关系的对象的标识。
  16. 根据权利要求14所述的网络设备,其中,所述切片信息包括所述终端所接入的小区支持的切片标识集合中一个切片标识的索引值。
  17. 根据权利要求14至16中任一项所述的网络设备,其中,所述随机接入报告中还包括在与至少一个同步信号块SSB或至少一个信道状态信息参考信号CSI-RS相关的随机接入过程中尝试过的前导码的发送次数和/或前导码碰撞信息。
  18. 根据权利要求17所述的网络设备,其中,所述处理单元具体用于根据所述发送前导码的次数和/或所述前导码碰撞信息,确定是否调整所述切片信息对应的前导码数目和/或随机接入时机RO数目。
  19. 一种终端,包括:处理器和存储器,该存储器用于存储计算机程序,所述处理器用于调用并运行所述存储器中存储的计算机程序,以使所述终端执行如权利要求1至4中任一项所述的方法。
  20. 一种网络设备,包括:处理器和存储器,该存储器用于存储计算机程序,所述处理器用于调用并运行所述存储器中存储的计算机程序,以使所述 网络设备执行如权利要求5至9中任一项所述的方法。
  21. 一种芯片,包括:处理器,用于从存储器中调用并运行计算机程序,使得安装有所述芯片的设备执行如权利要求1至4中任一项所述的方法。
  22. 一种芯片,包括:处理器,用于从存储器中调用并运行计算机程序,使得安装有所述芯片的设备执行如权利要求5至9中任一项所述的方法。
  23. 一种计算机可读存储介质,用于存储计算机程序,当所述计算机程序被设备运行时使得所述设备执行如权利要求1至4中任一项所述的方法。
  24. 一种计算机可读存储介质,用于存储计算机程序,当所述计算机程序被设备运行时使得所述设备执行如权利要求5至9中任一项所述的方法。
  25. 一种计算机程序产品,包括计算机程序指令,该计算机程序指令使得计算机执行如权利要求1至4中任一项所述的方法。
  26. 一种计算机程序产品,包括计算机程序指令,该计算机程序指令使得计算机执行如权利要求5至9中任一项所述的方法。
  27. 一种计算机程序,所述计算机程序使得计算机执行如权利要求1至4中任一项所述的方法。
  28. 一种计算机程序,所述计算机程序使得计算机执行如权利要求5至9中任一项所述的方法。
PCT/CN2020/103289 2020-07-21 2020-07-21 随机接入信息的处理方法、终端和网络设备 WO2022016376A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2020/103289 WO2022016376A1 (zh) 2020-07-21 2020-07-21 随机接入信息的处理方法、终端和网络设备
CN202080101493.1A CN115669151A (zh) 2020-07-21 2020-07-21 随机接入信息的处理方法、终端和网络设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/103289 WO2022016376A1 (zh) 2020-07-21 2020-07-21 随机接入信息的处理方法、终端和网络设备

Publications (1)

Publication Number Publication Date
WO2022016376A1 true WO2022016376A1 (zh) 2022-01-27

Family

ID=79728401

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/103289 WO2022016376A1 (zh) 2020-07-21 2020-07-21 随机接入信息的处理方法、终端和网络设备

Country Status (2)

Country Link
CN (1) CN115669151A (zh)
WO (1) WO2022016376A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023227103A1 (zh) * 2022-05-27 2023-11-30 展讯通信(上海)有限公司 信息处理方法及相关装置
WO2024032506A1 (zh) * 2022-08-09 2024-02-15 华为技术有限公司 信息处理的方法和装置
WO2024060233A1 (zh) * 2022-09-23 2024-03-28 北京小米移动软件有限公司 信息上报方法和装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107295561A (zh) * 2016-04-01 2017-10-24 中兴通讯股份有限公司 资源的申请方法及装置
CN107872884A (zh) * 2016-09-26 2018-04-03 电信科学技术研究院 一种随机接入资源分配和随机接入方法、设备
US20190052334A1 (en) * 2017-08-10 2019-02-14 Hyoungsuk Jeon Beam Refinement During RACH

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107295561A (zh) * 2016-04-01 2017-10-24 中兴通讯股份有限公司 资源的申请方法及装置
CN107872884A (zh) * 2016-09-26 2018-04-03 电信科学技术研究院 一种随机接入资源分配和随机接入方法、设备
US20190052334A1 (en) * 2017-08-10 2019-02-14 Hyoungsuk Jeon Beam Refinement During RACH

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ZTE: "Consideration on RAN Side Network Slicing", 3GPP DRAFT; R3-160821 CONSIDERATION ON RAN SIDE NETWORK SLICING V5, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Bangalore, India; 20160411 - 20160415, 1 April 2016 (2016-04-01), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051082958 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023227103A1 (zh) * 2022-05-27 2023-11-30 展讯通信(上海)有限公司 信息处理方法及相关装置
WO2024032506A1 (zh) * 2022-08-09 2024-02-15 华为技术有限公司 信息处理的方法和装置
WO2024060233A1 (zh) * 2022-09-23 2024-03-28 北京小米移动软件有限公司 信息上报方法和装置

Also Published As

Publication number Publication date
CN115669151A (zh) 2023-01-31

Similar Documents

Publication Publication Date Title
WO2022016376A1 (zh) 随机接入信息的处理方法、终端和网络设备
WO2021168661A1 (zh) 信息传输方法、终端设备和网络设备
WO2022067519A1 (zh) 随机接入方法和终端设备
US20230107139A1 (en) Relay discovery method and terminal
WO2023108454A1 (zh) 上行同步中的定时提前量维持方法、终端设备和网络设备
WO2022067614A1 (zh) 无线通信方法、终端设备和网络设备
WO2022183406A1 (zh) 传输数据信道的方法、终端设备和网络设备
WO2022126667A1 (zh) 随机接入响应的处理方法、网络设备和终端设备
WO2022151085A1 (zh) 波束管理方法、终端设备和网络设备
EP4255090A1 (en) Data transmission method, terminal devices, and network device
WO2022099634A1 (zh) 无线通信方法、终端设备和网络设备
US11924741B2 (en) Auxiliary routing method, terminal device, and network device
WO2023102829A1 (zh) 无线通信的方法、终端设备和网络设备
WO2023077456A1 (zh) 随机接入的方法、终端设备和网络设备
WO2022193198A1 (zh) 侧行链路资源请求方法、终端设备和网络设备
WO2023130467A1 (zh) 无线通信的方法、终端设备和网络设备
WO2024040598A1 (zh) 无线通信的方法和终端设备
WO2024036538A1 (zh) 重复传输方法、终端设备和网络设备
WO2022021448A1 (zh) 检测控制信息的方法、传输控制信息的方法、终端设备和网络设备
WO2023133794A1 (zh) 数据传输方法、终端设备和网络设备
WO2022021032A1 (zh) 信息处理方法、终端设备和网络设备
WO2023133839A1 (zh) 通信方法和设备
WO2022266870A1 (zh) 侧行链路通信方法、终端设备、网络设备及通信系统
WO2022027697A1 (zh) 资源选择方法及装置
US20230254071A1 (en) Transmission method and terminal device

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20946187

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20946187

Country of ref document: EP

Kind code of ref document: A1