Access method, device and related equipment

Abstract

The embodiment of the invention provides an access method and device and related equipment. The method comprises the following steps: receiving a first message Msg1 of random access sent by a terminal; sending a random access response (RAR) message to the terminal; the MAC sub-header corresponding to the terminal in the RAR is provided with an indication field, and the indication field is related to an access scene of the terminal and an RRC response message used for terminal access. Through one-time exchange between the terminal and the network side equipment, the terminal can determine whether the RRC connection can be established with the network side equipment or not. Compared with a mode that the terminal firstly receives the random access response message and then obtains the transmission resource of the RRC establishment response message to receive the RRC message, the method and the device have the advantages that the number of times of signaling interaction between the terminal and the network side equipment can be reduced, and the time delay of terminal access is optimized.

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and in particular to an access method, device and related equipment. Background Art

[0002] In the current random access scheme, the random access response message and the RRC connection establishment response message are transmitted successively. The network indicates the resource configuration for transmitting the RRC message through the random access response message. The terminal needs to receive the random access response message first to obtain the transmission resources of the RRC establishment response message before receiving the RRC message. This will increase the number of signaling interactions between the terminal and the network, thereby increasing the access delay of the terminal. Summary of the invention

[0003] The purpose of the embodiments of the present invention is to provide an access method, apparatus and related equipment to reduce the number of signaling interactions between a terminal and a network device and optimize the access delay of the terminal. The specific technical solution is as follows:

[0004] In a first aspect of the present application, an access method is provided, which is applied to a network side device, and the method includes:

[0005] A first random access message Msg1 sent by a receiving terminal;

[0006] A random access response message RAR is sent to the terminal; an indication field is set in the MAC subheader corresponding to the terminal in the RAR, and the indication field is related to the access scenario of the terminal and the RRC response message used for the terminal access.

[0007] Optionally, the Msg1 carries the access reason of the terminal.

[0008] Optionally, before sending the RAR to the terminal, the method further includes:

[0009] Determine whether to allow the terminal to access based on the access reason of the terminal and / or the network side resource situation.

[0010] Optionally, if the access scenario of the terminal is access allowed, the RRC response message is an RRC connection establishment message or an RRC connection reconstruction message.

[0011] Optionally, the RRC connection establishment or the RRC connection reconstruction adopts a default configuration mode.

[0012] Optionally, if the access scenario of the terminal is that access is not allowed, the RRC response message is an RRC connection reject message or an RRC reconstruction reject message.

[0013] Optionally, if the access scenario of the terminal is resynchronization, the RAR does not carry the RRC response message.

[0014] Optionally, the indication field includes a first field, wherein the first field indicates different access scenarios of the terminal and indicates that the RRC response message is embedded in a RAR MAC SDU.

[0015] Optionally, the first field is a RAR MAC SDU length indication field; wherein the RAR MAC SDU length is related to the access scenario of the terminal.

[0016] Optionally, the RRC response message is embedded in the RAR MAC SDU by setting the RRC MAC SDU in the RAR MAC SDU.

[0017] Optionally, the indication field includes a second field and a third field;

[0018] The second field and the third field are used together to indicate that the RRC response message and the RAR message are multiplexed for transmission.

[0019] Optionally, the second field is a RAR MAC SDU length indication field; wherein the RAR MAC SDU length is related to the access scenario of the terminal; the third field is used to indicate whether an RRC MACSDU is transmitted after the RAR MAC SDU, and the RRC MAC SDU is the payload of the RRC response message.

[0020] Optionally, the third field specifically indicates whether the RAR MAC SDU is followed by an RRC MAC SDU.

[0021] A second aspect of the present application provides an access method, which is applied to a terminal, and the method includes:

[0022] Sending a first random access message Msg1 to the network side device;

[0023] An access response message RAR sent by the network side device is received, wherein the MAC subheader corresponding to the terminal in the RAR is set with an indication field, and the indication field is related to the access scenario of the terminal and the RRC response message used for the terminal access.

[0024] Optionally, the Msg1 carries the access reason of the terminal.

[0025] Optionally, if the access scenario of the terminal is access allowed, the RRC response message is an RRC connection establishment message or an RRC connection reconstruction message.

[0026] Optionally, the RRC connection establishment or the RRC connection reconstruction adopts a default configuration mode.

[0027] Optionally, if the access scenario of the terminal is that access is not allowed, the RRC response message is an RRC connection reject message or an RRC reconstruction reject message.

[0028] Optionally, if the access scenario of the terminal is resynchronization, the RAR does not carry the RRC response message.

[0029] Optionally, the indication field includes a first field, wherein the first field indicates different access scenarios of the terminal and indicates that the RRC response message is embedded in a RAR MAC SDU.

[0030] Optionally, the first field is a RAR MAC SDU length indication field; wherein the RAR MAC SDU length is related to the access scenario of the terminal.

[0031] Optionally, the RRC response message is embedded in the RAR MAC SDU by setting the RRC MAC SDU in the RAR MAC SDU.

[0032] Optionally, the indication field includes a second field and a third field;

[0033] The second field and the third field are used together to indicate that the RRC response message and the RAR message are multiplexed for transmission.

[0034] Optionally, the second field is a RAR MAC SDU length indication field; wherein the RAR MAC SDU length is related to the access scenario of the terminal; the third field is used to indicate whether an RRC MACSDU is transmitted after the RAR MAC SDU, and the RRC MAC SDU is the payload of the RRC response message.

[0035] Optionally, the third field specifically indicates whether the RAR MAC SDU is followed by an RRC MAC SDU.

[0036] In a third aspect of the present application, an access device applied to a network side device is provided, including:

[0037] A first receiving module, configured to receive a first random access message Msg1 sent by a terminal;

[0038] The first sending module is used to send a random access response message RAR to the terminal; the MAC subheader corresponding to the terminal in the RAR is set with an indication field, and the indication field is related to the access scenario of the terminal and the RRC response message used for the terminal access.

[0039] Optionally, the Msg1 carries the access reason of the terminal.

[0040] Optionally, the device further includes: a determination module, used to determine whether to allow the terminal to access according to the access reason of the terminal and / or network-side resource conditions before sending the RAR to the terminal.

[0041] Optionally, if the access scenario of the terminal is access allowed, the RRC response message is an RRC connection establishment message or an RRC connection reconstruction message.

[0042] Optionally, the RRC connection establishment or the RRC connection reconstruction adopts a default configuration mode.

[0043] Optionally, if the access scenario of the terminal is that access is not allowed, the RRC response message is an RRC connection reject message or an RRC reconstruction reject message.

[0044] Optionally, if the access scenario of the terminal is resynchronization, the RAR does not carry the RRC response message.

[0045] Optionally, the indication field includes a first field, wherein the first field indicates different access scenarios of the terminal and indicates that the RRC response message is embedded in a RAR MAC SDU.

[0046] Optionally, the first field is a RAR MAC SDU length indication field; wherein the RAR MAC SDU length is related to the access scenario of the terminal.

[0047] Optionally, the RRC response message is embedded in the RAR MAC SDU by setting the RRC MAC SDU in the RAR MAC SDU.

[0048] Optionally, the indication field includes a second field and a third field;

[0049] The second field and the third field are used together to indicate that the RRC response message and the RAR message are multiplexed for transmission.

[0050] Optionally, the second field is a RAR MAC SDU length indication field; wherein the RAR MAC SDU length is related to the access scenario of the terminal; the third field is used to indicate whether an RRC MACSDU is transmitted after the RAR MAC SDU, and the RRC MAC SDU is the payload of the RRC response message.

[0051] Optionally, the third field specifically indicates whether the RAR MAC SDU is followed by an RRC MAC SDU.

[0052] In a fourth aspect of the present application, an access device applied to a terminal is provided, including:

[0053] A second sending module, configured to send a first random access message Msg1 to a network side device;

[0054] The second receiving module is used to receive the access response message RAR sent by the network side device, and the MAC subheader corresponding to the terminal in the RAR is set with an indication field, and the indication field is related to the access scenario of the terminal and the RRC response message used for the terminal access.

[0055] Optionally, the Msg1 carries the access reason of the terminal.

[0056] Optionally, if the access scenario of the terminal is access allowed, the RRC response message is an RRC connection establishment message or an RRC connection reconstruction message.

[0057] Optionally, the RRC connection establishment or the RRC connection reconstruction adopts a default configuration mode.

[0058] Optionally, if the access scenario of the terminal is that access is not allowed, the RRC response message is an RRC connection reject message or an RRC reconstruction reject message.

[0059] Optionally, if the access scenario of the terminal is resynchronization, the RAR does not carry the RRC response message.

[0060] Optionally, the indication field includes a first field, wherein the first field indicates different access scenarios of the terminal and indicates that the RRC response message is embedded in a RAR MAC SDU.

[0061] Optionally, the first field is a RAR MAC SDU length indication field; wherein the RAR MAC SDU length is related to the access scenario of the terminal.

[0062] Optionally, the RRC response message is embedded in the RAR MAC SDU by setting the RRC MAC SDU in the RAR MAC SDU.

[0063] Optionally, the indication field includes a second field and a third field;

[0064] The second field and the third field are used together to indicate that the RRC response message and the RAR message are multiplexed for transmission.

[0065] Optionally, the second field is a RAR MAC SDU length indication field; wherein the RAR MAC SDU length is related to the access scenario of the terminal; the third field is used to indicate whether an RRC MACSDU is transmitted after the RAR MAC SDU, and the RRC MAC SDU is the payload of the RRC response message.

[0066] Optionally, the third field specifically indicates whether the RAR MAC SDU is followed by an RRC MAC SDU.

[0067] In a fifth aspect of the present application, a network side device is provided, including a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus;

[0068] Memory, used to store computer programs;

[0069] The processor is used to implement any one of the above-mentioned method steps applied to the network side when executing the program stored in the memory.

[0070] In a sixth aspect of the present application, a terminal is provided, comprising a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus;

[0071] Memory, used to store computer programs;

[0072] The processor is used to implement any one of the method steps applied to the terminal when executing the program stored in the memory.

[0073] In a seventh aspect of the present application, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, any of the above method steps is implemented.

[0074] Beneficial effects of the embodiments of the present application:

[0075] Using the access method, apparatus and related equipment provided in the embodiments of the present application, the network side device receives the first message Msg1 of random access sent by the terminal; sends a random access response message RAR to the terminal, and the MAC subheader corresponding to the terminal in the RAR is set with an indication field, and the indication field is related to the access scenario of the terminal and the RRC response message used for terminal access.

[0076] Therefore, through a single exchange between the terminal and the network side device, the terminal can determine whether it can establish an RRC connection with the network side device. Compared with the method in which the terminal first receives a random access response message and then obtains the transmission resources of the RRC establishment response message before receiving the RRC message, it can reduce the number of signaling interactions between the terminal and the network side device and optimize the access delay of the terminal.

[0077] Of course, it is not necessary to achieve all of the advantages described above at the same time to implement any product or method of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0078] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present invention. For ordinary technicians in this field, other embodiments can also be obtained based on these drawings.

[0079] Figure 1 A schematic diagram of a flow chart of an access method applied to a network side device provided in an embodiment of the present application;

[0080] Figure 2 A schematic diagram of a MAC subheader provided in an embodiment of the present application;

[0081] Figure 3 A schematic diagram of a RAR MAC SDU provided in an embodiment of the present application;

[0082] Figure 4 Another schematic diagram of a MAC subheader provided in an embodiment of the present application;

[0083] Figure 5 A schematic diagram of a MAC SDU provided in an embodiment of the present application;

[0084] Figure 6 A schematic diagram of a flow chart of an access method applied to a terminal provided in an embodiment of the present application;

[0085] Figure 7 A schematic diagram of a structure of an access device applied to a network side device provided in an embodiment of the present application;

[0086] Figure 8 A schematic diagram of a structure of an access device applied to a terminal provided in an embodiment of the present application;

[0087] Fig. 9 A schematic diagram of the structure of a network side device provided in an embodiment of the present application;

[0088] Fig.10 A schematic diagram of the structure of a terminal provided in an embodiment of the present application. DETAILED DESCRIPTION

[0089] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments in the present invention, all other embodiments obtained by ordinary technicians in this field based on this application belong to the scope of protection of the present invention.

[0090] The embodiments of the present application can be applied to various mobile communication systems, such as: New Radio (NR) system (also known as 5G system), Long Term Evolution (LTE) system, Advanced long term evolution (LTE-A) system, evolved Long Term Evolution (eLTE) system and other mobile communication systems.

[0091] Below, some terms used in this application are explained to facilitate understanding.

[0092] Terminal, also known as User Equipment (UE), is a device that provides voice and / or data connectivity to users, such as handheld devices with wireless connection functions, vehicle-mounted devices, etc. Common terminals include: mobile phones, tablet computers, laptops, PDAs, mobile internet devices (MID), wearable devices such as smart watches, smart bracelets, pedometers, etc.

[0093] The network side device, specifically the access network element, can be an ordinary base station (such as Node B or eNB), a new radio controller (New Radio controller, NR controller), a gNode B (gNB) in a 5G system, a centralized network element (Centralized Unit), a new wireless base station, a radio frequency remote module, a micro base station, a relay, a distributed network element (Distributed Unit), a transmission point (Transmission Reception Point, TRP) or a transmission point (Transmission Point, TP) or any other wireless access device; it can also be a non-ground network node device, such as a satellite, a drone, a spacecraft, etc., which is not limited in the embodiments of the present application.

[0094] The following is a brief introduction to the random access process specified in the current protocol.

[0095] At present, the general process of random access includes: the terminal sends a random access preamble code sequence (i.e., message 1, Msg1) on the PRACH (Physical Random Access Channel) resource; the terminal receives a random access response (Random Access Response, RAR) message (i.e., message 2, Msg2) on the PDCCH (Physical Downlink Control Channel) / PDSCH (Physical Downlink Shared Channel); the terminal sends message 3 (Msg3) on the PUSCH (Physical Uplink Shared Channel). Depending on different scenarios, Msg3 carries a variety of information. For example, when the terminal is in an idle state, Msg3 carries an RRC (Radio Resource Control) establishment request; the UE receives a contention resolution message (i.e., message 4, Msg4) on the PDSCH.

[0096] The specific process is as follows: before the random access process, the UE obtains the set of SSB (Synchronization Signal and PBCH block) indexes, PRACH time-frequency resources, PRACH Preamble format and PRACH Preamble sequence set parameters through the SIB (System Information Block) message. Then, the UE generates the PRACH Preamble sequence based on the information obtained, and sends the random access Preamble sequence on the selected PRACH time-frequency resources. The network side detects the Preamble sequence. If the Preamble sequence is detected, the corresponding random access response (RAR) information is fed back on the PDCCH / PDSCH. After sending the Preamble sequence, the terminal detects the RAR message fed back by the downlink PDCCH / PDSCH within the RAR time window. If the corresponding RAR message is detected, it means that the Preamble sequence sent by the terminal has been detected by the network side. The RAR message also includes the uplink timing advance adjustment amount of the terminal and the uplink scheduling permission for the transmission of message 3 of the scheduling terminal. Subsequently, the terminal obtains uplink synchronization according to the uplink timing advance adjustment amount, and sends message 3 (for example, RRC establishment request message) on PUSCH according to the uplink scheduling permission. After the base station receives and parses the UE identifier contained in message 3, it sends message 4 on PDSCH. The terminal receives and decodes the contention resolution message contained in message 4 on PDSCH, and the random access process is completed.

[0097] It can be seen that in the related technology, in the random access process, the random access response message and the RRC connection establishment response message are transmitted successively. The network side indicates the resource configuration for transmitting the RRC message through the random access response message. The terminal needs to first receive the random access response message and obtain the transmission resources of the RRC establishment response message before it can receive the RRC message. This results in a large number of signaling interactions between the terminal and the network side, which increases the access delay of the terminal.

[0098] For aerospace systems with low air interface rates, the information energy transmitted each time is limited. During the terminal access process, the random access response message and the RRC connection establishment message or RRC connection rejection message are transmitted successively, which increases the delay for the terminal to obtain information. In addition, the on-board processing complexity is high, which easily leads to a waste of resources.

[0099] In order to solve the above technical problems, the present application embodiment provides an access method, an apparatus and related equipment, see Figure 1 , Figure 1A schematic diagram of a flow chart of an access method applied to a network side device provided in an embodiment of the present application, the method may include the following steps:

[0100] S101: receiving a first random access message Msg1 sent by a terminal.

[0101] In the embodiment of the present application, before sending an access message, the terminal needs to complete downlink time synchronization and determine the PRACH time-frequency resources according to the received network-side broadcast message.

[0102] As an example, the terminal randomly selects a time-frequency resource from the PRACH time-frequency resource candidate set notified by SIB1, and sends an access message based on the time-frequency resource.

[0103] Different from the related art, in the embodiment of the present application, the first random access message Msg1 sent by the terminal includes not only information for random access, but also information for RRC establishment request or RRC reconstruction request. That is, after determining the PRACH time-frequency resource, the terminal can send the first random access message based on the time-frequency resource, and the message includes information related to the random access request and information related to the RRC establishment request / RRC reconstruction request.

[0104] When different terminals send access requests, the time and frequency resources used may be different or the same.

[0105] S102: Send a random access response message RAR to the terminal, in which the MAC subheader corresponding to the terminal in the RAR is set with an indication field, where the indication field is related to the access scenario of the terminal and the RRC response message used for terminal access.

[0106] In the embodiment of the present application, the above RAR message corresponds to Msg2 fed back by the network side device to the terminal during the random access process, but is different from Msg2 in the related art. Specifically, in the embodiment of the present application, the random access response RAR sent by the terminal also includes an RRC response message for terminal access, that is, it carries information related to the RRC establishment response message or the RRC reconstruction response message.

[0107] Since the information carried by the RAR message has changed, it is necessary to further design the protocol format of the random access response RAR message in the related art, that is, to make changes based on the existing protocol format of the random access response message.

[0108] Specifically, random access response information for multiple terminals may be encapsulated in one random access response message, using a shared MAC header.

[0109] Taking a random access response message containing random access response information of N terminals as an example, the random access response message forms a transmission block at the MAC layer, namely, MAC PDU, which includes a MAC header and a MAC SDU, wherein the MAC header includes a MAC sub-header corresponding to each of the N terminals, and the MAC SDU includes a RAR MAC SDU corresponding to each MAC sub-header.

[0110] Among them, SDU (Service Data Unit) corresponds to the unprocessed data in a certain sublayer. That is, the data that has not been processed by the upper layer to this layer. PDU (Protocol Data Unit) corresponds to the data in a specific format processed by the sublayer. For a certain sublayer, it means that the SDU of this layer will be processed in a specific format and then passed to the next layer.

[0111] In one embodiment of the present application, an indication field is provided in the MAC subheader corresponding to each terminal, and the indication field is related to the access scenario of the terminal and the RRC response message used for terminal access.

[0112] Therefore, after receiving the RAR message, the terminal finds the MAC subheader corresponding to its own identifier and obtains the RRC response message corresponding to the terminal.

[0113] It can be seen that, by applying the access method provided in the embodiment of the present application, the network side device receives the first message Msg1 of random access sent by the terminal; and sends a random access response message RAR to the terminal, and the MAC subheader corresponding to the terminal in the RAR is set with an indication field, and the indication field is related to the access scenario of the terminal and the RRC response message used for terminal access.

[0114] Therefore, through a single exchange between the terminal and the network side device, the terminal can determine whether it can establish an RRC connection with the network side device. Compared with the method in which the terminal first receives a random access response message and then obtains the transmission resources of the RRC establishment response message before receiving the RRC message, it can reduce the number of signaling interactions between the terminal and the network side device and optimize the access delay of the terminal.

[0115] In one embodiment of the present application, the network side device can receive random access messages Msg1 sent by multiple terminals. For each random access message, the network side device can directly decide whether to allow the terminal to establish an RRC connection or reestablish an RRC connection based on the information related to the RRC establishment request or RRC reconstruction request contained in the random access message, as well as the current resource occupancy of the network side device.

[0116] In one embodiment of the present application, the information related to the RRC establishment request or the RRC re-establishment request may include identification information of the terminal, access reason of the terminal, and capability indication information of the terminal.

[0117] Among them, the identification information of the terminal can be ue-Identity (the unique ID of the terminal); the access reason of the terminal can be of various types. As an example, it includes: emergency (emergency call), highPriorityAccess (high priority access), mt-Access (mobile terminal access, such as response to paging), mo-Signalling (mobile originating signaling, such as attachment, location update, random access, etc.), mt-Data (mobile originating data). The terminal's capability indication information is UE Capability, which includes the terminal's performance parameters, supported functions, etc. For details, please refer to the relevant technology.

[0118] In one embodiment of the present application, the network side device determines whether to allow the terminal access according to the access reason of the terminal and / or the network side resource situation.

[0119] As an example, when the access reason of the terminal is a non-emergency type of access reason, and the network side resource occupancy rate is high, the terminal access can be denied. The above is only an example, and the specific judgment criteria can refer to the relevant technology, and the embodiments of the present application do not limit this.

[0120] In one embodiment of the present application, if the access scenario of the terminal is access allowed, the RRC response message carried in the RRC message sent by the network side device may be an RRC connection establishment message or an RRC connection reestablishment message. When the Msg1 sent by the terminal carries information related to the RRC establishment request, the RRC response message carried in the RRC message sent by the network side device is an RRC connection establishment message; when the Msg1 sent by the terminal carries information related to the RRC reestablishment request, the RRC response message carried in the RRC message sent by the network side device is an RRC connection reestablishment message.

[0121] Among them, the information fields included in the RRC connection establishment message or the RRC connection reconstruction message can be referred to in the relevant technology, and the embodiments of the present application are not limited to this.

[0122] In addition, when allowing the terminal to establish an RRC connection or RRC reestablishment, the network side device also needs to feedback information related to uplink synchronization to the terminal, which can be understood as the uplink timing advance adjustment amount of the terminal, which is calculated based on the random access related information in the access message sent by the terminal.

[0123] In one embodiment of the present application, the above-mentioned information related to random access may be a random access preamble, i.e., a PRACH Preamble, which is usually a Zadf-Chu sequence and can be used as an uplink synchronization sequence of a PRACH channel. That is, the network side device calculates information related to uplink synchronization of the terminal according to the above-mentioned information related to random access, and carries the information in a random access response message.

[0124] In addition, when allowing the terminal to establish an RRC connection or RRC reestablishment, the network side device also needs to allocate uplink time and frequency resources to the terminal and carry this information in the RAR message.

[0125] In one embodiment of the present application, the RRC connection establishment or RRC connection reconstruction adopts a default configuration mode. Specifically, since in the embodiment of the present application, the RRC connection establishment message or the RRC connection reconstruction message is carried in the RAR message and sent, it is not convenient to set more configuration information related to the RRC response in the RAR message. For the RRC connection establishment or RRC connection reconstruction, the default configuration mode is adopted. That is, the terminal configures the physical layer according to the default parameters. In this way, the air interface transmission overhead can be reduced.

[0126] In one embodiment of the present application, if the access scenario of the terminal is that access is not allowed, the RRC response message is an RRC connection rejection message or an RRC reconstruction rejection message. Specifically, when the terminal is not allowed to access, when the Msg1 sent by the terminal carries information related to the RRC establishment request, the RRC response message carried in the RRC message sent by the network side device is an RRC connection rejection message; when the Msg1 sent by the terminal carries information related to the RRC reconstruction request, the RRC response message carried in the RRC message sent by the network side device is an RRC reconstruction rejection message.

[0127] Among them, the information fields included in the RRC connection rejection message or the RRC reconstruction rejection message can be referred to in the relevant technology, and the embodiments of the present application are not limited to this.

[0128] In addition, when the terminal is rejected from establishing an RRC connection, since the terminal cannot establish an RRC connection with the network side device, there is no need to complete uplink synchronization or allocate uplink time and frequency resources to the terminal. That is, in this case, the RAR message sent by the network side device does not have to include information related to uplink synchronization and allocation information of uplink time and frequency resources.

[0129] When allowing the terminal to establish an RRC connection or refusing the terminal to establish an RRC connection, the RAR message sent by the network side device needs to include the identification information of the terminal, so that the terminal can identify the message sent to itself.

[0130] In one embodiment of the present application, if the access scenario of the terminal is resynchronization, the RAR message does not carry an RRC response message. Specifically, if the Msg1 sent by the terminal carries only information related to resynchronization and does not carry information related to the RRC establishment request, then the network side device can determine that the terminal expects to perform uplink synchronization, and the network side device calculates based on the information related to uplink synchronization and feeds back information related to uplink synchronization to the terminal, such as the uplink timing advance adjustment amount of the terminal. In this case, the RAR message does not need to carry an RRC response message.

[0131] In one embodiment of the present application, the indication field includes a first field, the first field indicates different access scenarios of the terminal, and indicates that the RRC response message is embedded in the RAR MAC SDU.

[0132] Specifically, a first field may be set in the MAC subheader corresponding to the terminal in the RAR message, and the first field may indicate different access scenarios of the terminal and indicate that the RRC response message is embedded in the RAR MAC SDU.

[0133] That is to say, there is a correspondence between the value of the first field and the scenario. When the terminal recognizes the first field, it can identify the access scenario. When the terminal recognizes the first field, it can know that the RAR message is different from the RAR message in the related technology, that is, the RAR message also carries an RRC response message, and the effective load of the RRC response message is embedded in the RAR MACSDU.

[0134] In one embodiment of the present application, the first field is a RAR MAC SDU length indication field, wherein the RAR MAC SDU length is related to the access scenario of the terminal.

[0135] Specifically, the first field is the RAR MAC SDU length indication field, which is used to indicate the length of the RAR MAC SDU and pre-sets the relationship between the length of the RAR MAC SDU and the access scenario of the terminal, so that the terminal can identify the value of the first field and determine the access scenario.

[0136] In one embodiment of the present application, the embedding method of the RRC response message into the RAR SDU is: setting the RRC MAC SDU in the RAR MAC SDU.

[0137] For details, see Figure 2 , Figure 2 A schematic diagram of a MAC subheader provided in an embodiment of the present application includes: Figure 2The fields shown in the figure, where the E field belongs to the extended field, and is used to indicate whether there are other fields in the MAC header; for example, if E is set to "1", it means that there is at least one (E / T / RAPID) field following. The T field belongs to the type field, and is used to indicate that the MAC subheader contains a random access ID, or a BACK OFF indication. If T is set to "0", it means that the subheader contains a BI value. If it is set to "1", it means that the random access preamble ID field appears in this subheader; R is a reserved bit.

[0138] The ROID is calculated based on the time-frequency domain resources used by the terminal to send the access message.

[0139] L is the RAR MAC SDU length indication field, which can indicate the length of the RAR MAC SDU corresponding to the MAC subheader, and the value of this field can indicate the access scenario of the terminal, and indicate that the RRC response message is set in the RAR MACSDU.

[0140] See also Figure 3 , Figure 3 A schematic diagram of a RAR MAC SDU provided in an embodiment of the present application includes UE CRID (contention resolution identifier), T / F Adjust, Channel Config1, Channel Config2 and RRC RES, wherein RRC RES is a field representing RRC establishment response information in an RRC response message. Wherein, oct represents the byte number.

[0141] After receiving the RAR message, the terminal can identify the RAR MAC SDU sent to itself according to the UE ID, and then parse the RRC RES therefrom, which is equivalent to obtaining the RRC response message.

[0142] It can be seen that in one embodiment of the present application, information related to the RRC establishment response can be embedded in the MAC layer payload of the RAR message for transmission, and indicated by the first field in the MAC subheader, which can support the network side device to transmit random access response information and RRC establishment response information for multiple terminals at one time.

[0143] By identifying the first field, the terminal can determine the access scenario and learn that the RAR message carries an RRC response message. Then, the terminal simultaneously obtains the random access response information and the RRC establishment response information according to the indication information in the MAC subheader, thereby reducing the number of interactions between the terminal and the network side device, and reducing the delay in terminal access or terminal receiving response messages.

[0144] In one embodiment of the present application, the indication field includes a second field and a third field; the second field and the third field are used together to indicate that the RRC response message and the RAR message are multiplexed for transmission.

[0145] In this embodiment, the RAR message and the RRC response message are multiplexed for transmission, that is, the time-frequency domain resources of a transmission block are multiplexed. The difference from the previous embodiment is that the RAR message and the RRC response message correspond to their own MAC SDUs and are not merged into one MAC SDU.

[0146] Specifically, in order to indicate the multiplexed transmission, the second field and the third field are set in the MAC subheader. The terminal identifies the second field and the third field, and can know that the RRC response message and the RAR message are multiplexed for transmission.

[0147] In one embodiment of the present application, the second field is a RAR MAC SDU length indication field; wherein the RAR MACSDU length is related to the access scenario of the terminal; the third field is used to indicate whether an RRC MACSDU is transmitted after the RAR MAC SDU, and the RRC MAC SDU is the payload of the RRC response message.

[0148] Specifically, the second field is used to indicate the length of the RAR MAC SDU, and the relationship between the length of the RAR MAC SDU and the access scenario of the terminal is pre-set, so that the terminal can identify the value of the second field and determine the access scenario.

[0149] The third field is used to indicate whether RRC MAC SDU is transmitted after RAR MAC SDU, and RRC MAC SDU is the payload of the RRC response message.

[0150] In one embodiment of the present application, the third field specifically indicates whether the RAR MAC SDU is followed by the RRC MACSDU. Figure 4 , Figure 4 Another schematic diagram of the MAC subheader provided in the embodiment of the present application shows that an F field is added, which is the third field and is used to indicate whether the RAR MAC SDU is followed by the RRC MAC SDU. The information of the remaining fields remains unchanged, as can be seen above.

[0151] Accordingly, see Figure 5 , Figure 5 A schematic diagram of the MAC SDU corresponding to the MAC subheader provided in an embodiment of the present application. It can be seen that the MAC SDU includes a RAR MAC SDU and an adjacent RRC MAC SDU, wherein the RRC MAC SDU includes information related to the RRC establishment response.

[0152] It can be seen that in one embodiment of the present application, the RAR MAC SDU and the RRC MAC SDU can be multiplexed for transmission, and the time-frequency domain resources of the same transmission block can be multiplexed. At the same time, the MAC subheader indicates whether there is an RRCMAC SDU immediately after the RAR MAC SDU, thereby supporting the terminal to simultaneously obtain random access response information and RRC establishment response information according to the MAC subheader indication, reducing the number of interactions between the terminal and the network side device, and reducing the delay in the terminal accessing or the terminal receiving the response message.

[0153] In one embodiment of the present application, the network side device is a non-ground network node device that carries the access network.

[0154] That is, the access method provided by the present application can be applied to aerospace systems, and non-ground network node devices can carry the entire access network or a part of the access network. For aerospace systems, the amount of information transmitted each time is limited, and the distance between the satellite and the ground is far, and the delay is high. If the terminal receives the random access response message and the RRC establishment response message successively, it is more detrimental to the access delay of the terminal, and the on-board processing complexity is high.

[0155] For aerospace systems, applying the access method provided in the embodiments of the present application can reduce the number of signaling interactions between the satellite and the ground, significantly reduce the latency of the terminal accessing the onboard access network, reduce the complexity of onboard processing, and reduce the waste of onboard time and frequency resources.

[0156] The present application also provides an access method for a terminal, see Figure 6 , Figure 6 A schematic diagram of a flow chart of an access method applied to a terminal provided in an embodiment of the present application, the method comprising the following steps:

[0157] S601: Sending a first random access message Msg1 to a network side device;

[0158] S602: receiving an access response message RAR sent by a network side device, wherein the MAC subheader corresponding to the terminal in the RAR is provided with an indication field, and the indication field is related to an access scenario of the terminal and an RRC response message used for terminal access.

[0159] Therefore, through a single exchange between the terminal and the network side device, the terminal can determine whether it can establish an RRC connection with the network side device. Compared with the method in which the terminal first receives a random access response message and then obtains the transmission resources of the RRC establishment response message before receiving the RRC message, it can reduce the number of signaling interactions between the terminal and the network side device and optimize the access delay of the terminal.

[0160] In one embodiment of the present application, the Msg1 carries the access reason of the terminal.

[0161] In one embodiment of the present application, if the access scenario of the terminal is access allowed, the RRC response message is an RRC connection establishment message or an RRC connection reestablishment message.

[0162] In one embodiment of the present application, the RRC connection establishment or the RRC connection reconstruction adopts a default configuration method.

[0163] In one embodiment of the present application, if the access scenario of the terminal is that access is not allowed, the RRC response message is an RRC connection reject message or an RRC reestablishment reject message.

[0164] In one embodiment of the present application, if the access scenario of the terminal is resynchronization, the RAR does not carry the RRC response message.

[0165] In one embodiment of the present application, the indication field includes a first field, the first field indicates different access scenarios of the terminal and indicates that the RRC response message is embedded in the RAR MAC SDU.

[0166] In one embodiment of the present application, the first field is a RAR MAC SDU length indication field; wherein the RAR MAC SDU length is related to the access scenario of the terminal.

[0167] In one embodiment of the present application, the embedding method of the RRC response message into the RAR MAC SDU is: setting the RRC MAC SDU in the RAR MAC SDU.

[0168] In one embodiment of the present application, the indication field includes a second field and a third field;

[0169] The second field and the third field are used together to indicate that the RRC response message and the RAR message are multiplexed for transmission.

[0170] In one embodiment of the present application, the second field is a RAR MAC SDU length indication field; wherein the RARMAC SDU length is related to the access scenario of the terminal; the third field is used to indicate whether an RRC MAC SDU is transmitted after the RAR MAC SDU, and the RRC MAC SDU is the payload of the RRC response message.

[0171] In one embodiment of the present application, the third field specifically indicates whether the RAR MAC SDU is followed by the RRC MAC SDU.

[0172] The present application also provides an access device for network side equipment. Figure 7 , Figure 7 A schematic diagram of a structure of an access device applied to a network side device provided in an embodiment of the present application includes the following modules:

[0173] The first receiving module 701 is configured to receive a first random access message Msg1 sent by a terminal;

[0174] The first sending module 702 is used to send a random access response message RAR to the terminal; the MAC subheader corresponding to the terminal in the RAR is set with an indication field, and the indication field is related to the access scenario of the terminal and the RRC response message used for the terminal access.

[0175] Thus, through a single exchange between the terminal and the network side device, the terminal can determine whether it can establish an RRC connection with the network side device. When the RRC connection with the network side device is allowed to be established, the uplink synchronization information and uplink time-frequency resource allocation information can be obtained at one time. It can be seen that compared with the method in which the terminal first receives the random access response message and then obtains the transmission resources of the RRC establishment response message before receiving the RRC message, the number of signaling interactions between the terminal and the network side device can be reduced, and the access delay of the terminal can be optimized.

[0176] The present application also provides an access device for a terminal, see Figure 8 , Figure 8 A schematic diagram of a structure of an access device applied to a terminal provided in an embodiment of the present application includes the following modules:

[0177] The second sending module 801 is used to send a first random access message Msg1 to the network side device;

[0178] The second receiving module 802 is used to receive the access response message RAR sent by the network side device, and the MAC subheader corresponding to the terminal in the RAR is set with an indication field, and the indication field is related to the access scenario of the terminal and the RRC response message used for the terminal access.

[0179] Thus, through a single exchange between the terminal and the network side device, the terminal can determine whether it can establish an RRC connection with the network side device. When the RRC connection with the network side device is allowed to be established, the uplink synchronization information and uplink time-frequency resource allocation information can be obtained at one time. It can be seen that compared with the method in which the terminal first receives the random access response message and then obtains the transmission resources of the RRC establishment response message before receiving the RRC message, the number of signaling interactions between the terminal and the network side device can be reduced, and the access delay of the terminal can be optimized.

[0180] The embodiment of the present application also provides a network side device, which may be an electronic device, such as Fig. 9 As shown, it includes a processor 901, a communication interface 902, a memory 903 and a communication bus 904, wherein the processor 901, the communication interface 902, and the memory 903 communicate with each other through the communication bus 904.

[0181] Memory 903, used for storing computer programs;

[0182] The processor 901 is used to execute the program stored in the memory 903 to implement the following steps:

[0183] A first random access message Msg1 sent by a receiving terminal;

[0184] A random access response message RAR is sent to the terminal; an indication field is set in the MAC subheader corresponding to the terminal in the RAR, and the indication field is related to the access scenario of the terminal and the RRC response message used for the terminal access.

[0185] The embodiment of the present application also provides a terminal, which may be an electronic device, such as Fig.10 As shown, it includes a processor 1001, a communication interface 1002, a memory 1003 and a communication bus 1004, wherein the processor 1001, the communication interface 1002, and the memory 1003 communicate with each other through the communication bus 1004.

[0186] Memory 1003, used for storing computer programs;

[0187] The processor 1001 is used to execute the program stored in the memory 1003, and implements the following steps:

[0188] Sending a first random access message Msg1 to the network side device;

[0189] An access response message RAR sent by the network side device is received, wherein the MAC subheader corresponding to the terminal in the RAR is set with an indication field, and the indication field is related to the access scenario of the terminal and the RRC response message used for the terminal access.

[0190] The communication bus mentioned in the above electronic device can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The communication bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus.

[0191] The communication interface is used for communication between the above electronic device and other devices.

[0192] The memory may include a random access memory (RAM) or a non-volatile memory (NVM), such as at least one disk memory. Optionally, the memory may also be at least one storage device located away from the aforementioned processor.

[0193] The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

[0194] In another embodiment of the present invention, a computer-readable storage medium is provided, in which a computer program is stored. When the computer program is executed by a processor, the steps of any of the above access methods are implemented.

[0195] In another embodiment of the present invention, a computer program product including instructions is provided, which, when executed on a computer, enables the computer to execute any accessing step in the above embodiments.

[0196] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented by 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, the process or function described in the embodiment of the present invention 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 device. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, computer, server or data center to another website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state hard disk Solid State Disk (SSD)), etc.

[0197] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0198] Each embodiment in this specification is described in a related manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the access device, network side equipment, and computer storage medium embodiments, since they are basically similar to the access method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the access method embodiment.

[0199] The above description is only a preferred embodiment of the present invention and is not intended to limit the protection scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention are included in the protection scope of the present invention.

Claims

1. An access method, It is characterized in that Applied to a network side device, the method includes: A first random access message Msg1 sent by a receiving terminal; A random access response message RAR is sent to the terminal; an indication field is set in the MAC subheader corresponding to the terminal in the RAR, and the indication field is related to the access scenario of the terminal and the RRC response message used for the terminal access.

2. The method according to claim 1, It is characterized in that The Msg1 carries the access reason of the terminal.

3. The method according to claim 2, It is characterized in that Before sending the RAR to the terminal, the method further includes: Determine whether to allow the terminal to access based on the access reason of the terminal and / or the network side resource situation.

4. The method according to claim 3, It is characterized in that If the access scenario of the terminal is access allowed, the RRC response message is an RRC connection establishment message or an RRC connection reestablishment message.

5. The method according to claim 4, It is characterized in that The RRC connection establishment or the RRC connection reestablishment adopts a default configuration mode.

6. The method according to claim 3, It is characterized in that If the access scenario of the terminal is that access is not allowed, the RRC response message is an RRC connection reject message or an RRC reestablishment reject message.

7. The method according to claim 3, It is characterized in that If the access scenario of the terminal is resynchronization, the RAR does not carry the RRC response message.

8. The method according to claim 1, It is characterized in that The indication field includes a first field, the first field indicates different access scenarios of the terminal and indicates that the RRC response message is embedded in the RAR MAC SDU.

9. The method according to claim 8, It is characterized in that The first field is a RAR MAC SDU length indication field; wherein the RAR MAC SDU length is related to the access scenario of the terminal.

10. The method according to claim 9, It is characterized in that The embedding method of the RRC response message into the RAR MAC SDU is: setting the RRC MAC SDU in the RAR MAC SDU.

11. The method according to claim 1, It is characterized in that The indication field includes a second field and a third field; The second field and the third field are used together to indicate that the RRC response message and the RAR message are multiplexed for transmission.

12. The method according to claim 11, It is characterized in that The second field is a RAR MAC SDU length indication field, wherein the RAR MAC SDU length is related to the access scenario of the terminal; the third field is used to indicate whether an RRC MAC SDU is transmitted after the RARMAC SDU, and the RRC MAC SDU is the payload of the RRC response message.

13. The method according to claim 12, characterized in that in, The third field specifically indicates whether the RAR MAC SDU is followed by the RRC MAC SDU.

14. An access method, It is characterized in that Applied to a terminal, the method comprises: Sending a first random access message Msg1 to the network side device; An access response message RAR sent by the network side device is received, wherein the MAC subheader corresponding to the terminal in the RAR is set with an indication field, and the indication field is related to the access scenario of the terminal and the RRC response message used for the terminal access.

15. The method according to claim 14, It is characterized in that The Msg1 carries the access reason of the terminal.

16. The method according to claim 14, It is characterized in that If the access scenario of the terminal is access allowed, the RRC response message is an RRC connection establishment message or an RRC connection reestablishment message.

17. The method according to claim 16, It is characterized in that The RRC connection establishment or the RRC connection reestablishment adopts a default configuration mode.

18. The method according to claim 14, It is characterized in that If the access scenario of the terminal is that access is not allowed, the RRC response message is an RRC connection reject message or an RRC reestablishment reject message.

19. The method according to claim 14, It is characterized in that If the access scenario of the terminal is resynchronization, the RAR does not carry the RRC response message.

20. The method according to claim 14, It is characterized in that The indication field includes a first field, the first field indicates different access scenarios of the terminal and indicates that the RRC response message is embedded in the RAR MAC SDU.

21. The method according to claim 20, It is characterized in that The first field is a RAR MAC SDU length indication field; wherein the RAR MAC SDU length is related to the access scenario of the terminal.

22. The method according to claim 21, It is characterized in that The embedding method of the RRC response message into the RAR MAC SDU is: setting the RRC MAC SDU in the RAR MAC SDU.

23. The method according to claim 14, It is characterized in that The indication field includes a second field and a third field; The second field and the third field are used together to indicate that the RRC response message and the RAR message are multiplexed for transmission.

24. The method according to claim 23, It is characterized in that The second field is a RAR MAC SDU length indication field, wherein the RAR MAC SDU length is related to the access scenario of the terminal; the third field is used to indicate whether an RRC MAC SDU is transmitted after the RARMAC SDU, and the RRC MAC SDU is the payload of the RRC response message.

25. The method according to claim 24, characterized in that in, The third field specifically indicates whether the RAR MAC SDU is followed by the RRC MAC SDU.

26. An access device, It is characterized in that Applied to a network side device, the device comprises: A first receiving module, configured to receive a first random access message Msg1 sent by a terminal; The first sending module is used to send a random access response message RAR to the terminal; the MAC subheader corresponding to the terminal in the RAR is set with an indication field, and the indication field is related to the access scenario of the terminal and the RRC response message used for the terminal access.

27. An access device, It is characterized in that Applied to a terminal, the device comprises: A second sending module, configured to send a first random access message Msg1 to a network side device; The second receiving module is used to receive the access response message RAR sent by the network side device, and the MAC subheader corresponding to the terminal in the RAR is set with an indication field, and the indication field is related to the access scenario of the terminal and the RRC response message used for the terminal access.

28. A network side device, It is characterized in that It includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus; Memory, used to store computer programs; A processor, for implementing the method steps described in any one of claims 1-13 when executing a program stored in a memory.

29. A terminal, It is characterized in that It includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus; Memory, used to store computer programs; A processor, for implementing the method steps described in any one of claims 14-25 when executing a program stored in a memory.

30. A computer readable storage medium, It is characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method steps described in any one of claims 1-13 or 14-25 are implemented.

Images