Random access method, terminal, network side device and readable storage medium
By adopting a registration service in the 6G network and using QoS-guaranteed links for information transmission, the problem of rapid terminal access is solved, RRC signaling overhead is reduced, and service-oriented terminal access is realized.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- CHINA MOBILE COMM LTD RES INST
- Filing Date
- 2022-04-29
- Publication Date
- 2026-05-29
Smart Images
Figure CN117015060B_ABST
Abstract
Description
Technical Field
[0001] This application belongs to the field of communication technology, specifically relating to a random access method, a terminal, a network-side device, and a readable storage medium. Background Technology
[0002] In 6th generation mobile networks (6G), besides transmitting service data and Radio Resource Control (RRC) signaling, a significant amount of information needs to be exchanged between the terminal and network-side peer access layers, as well as within the access layers themselves. This includes configuration or update interaction information for Artificial Intelligence (AI) models, measurement-based protocol sublayer state interaction information, and selection of appropriate protocol sublayer functions based on service characteristics. All of this requires the 6G network protocol stack to possess capabilities such as on-demand function selection, unified Protocol Data Unit (PDU) format, low redundancy overhead, and flexible capabilities with no or light connections between protocol layers. In this context, how to achieve rapid service-oriented terminal access is a pressing issue that needs to be addressed. Summary of the Invention
[0003] The purpose of this application is to provide a random access method, terminal, network-side device, and readable storage medium to enable service-oriented terminal fast access.
[0004] To solve the above-mentioned technical problems, this application is implemented as follows:
[0005] Firstly, a random access method is provided, including:
[0006] The first RRC layer entity of the terminal sends a registration request to the first MAC layer entity of the terminal through the first link, wherein the first link is a QoS-guaranteed link between the first RRC layer entity and the first MAC layer entity.
[0007] Based on the registration request, the first MAC layer entity sends a random access request to the second MAC layer entity of the network-side device;
[0008] The first MAC layer entity receives a random access response from the second MAC layer entity;
[0009] Based on the random access response, after completing the establishment or registration of the terminal context, the first MAC layer entity sends a registration response to the first RRC layer entity through a second link. The second link is a QoS-guaranteed link between the first MAC layer entity and the first RRC layer entity.
[0010] Secondly, a random access method is provided, including:
[0011] The second MAC layer entity of the network-side device receives a random access request from the first MAC layer entity of the terminal.
[0012] Based on the random access request, the second MAC layer entity sends a random access response to the first MAC layer entity after completing the establishment or registration of the terminal context;
[0013] The second MAC layer entity sends a terminal registration request to the second RRC layer entity of the network-side device through a third link, wherein the third link is a QoS-guaranteed link between the second MAC layer entity and the second RRC layer entity.
[0014] The second RRC layer entity sends the terminal's registration response to the second MAC layer entity through the fourth link, which is a QoS-guaranteed link between the second RRC layer entity and the second MAC layer entity.
[0015] Thirdly, a terminal is provided, including a first RRC layer entity and a first MAC layer entity;
[0016] The first RRC layer entity is used to: send a registration request to the first MAC layer entity through a first link, wherein the first link is a QoS-guaranteed link between the first RRC layer entity and the first MAC layer entity.
[0017] The first MAC layer entity is configured to: send a random access request to the second MAC layer entity of the network-side device based on the registration request, receive a random access response from the second MAC layer entity, and, based on the random access response, after completing the establishment or registration of the terminal context, send a registration response to the first RRC layer entity through a second link, wherein the second link is a QoS-guaranteed link between the first MAC layer entity and the first RRC layer entity.
[0018] Fourthly, a network-side device is provided, including a second RRC layer entity and a second MAC layer entity;
[0019] The second MAC layer entity is used to: receive a random access request from the first MAC layer entity of the terminal; based on the random access request, after completing the establishment or registration of the terminal context, send a random access response to the first MAC layer entity; and send a terminal registration request to the second RRC layer entity through a third link, wherein the third link is a link with QoS guarantee capability between the second MAC layer entity and the second RRC layer entity.
[0020] The second RRC layer entity is used to: send a terminal registration response to the second MAC layer entity via a fourth link, wherein the fourth link is a QoS-guaranteed link between the second RRC layer entity and the second MAC layer entity.
[0021] Fifthly, a communication device is provided, including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method described in the first aspect, or the steps of the method described in the second aspect.
[0022] In a sixth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or the steps of the method described in the second aspect.
[0023] In this embodiment, the terminal's first RRC layer entity sends a registration request to the terminal's first MAC layer entity via a first link. Based on the registration request, the first MAC layer entity sends a random access request to the network-side device's second MAC layer entity, receives a random access response from the second MAC layer entity, and, based on the random access response, after completing the establishment or registration of the terminal context, sends a registration response to the first RRC layer entity via a second link. This first or second link is a link with QoS guarantee capabilities. Therefore, when the terminal accesses the RAN, no bearer is established at the RRC layer; instead, network-side authentication is achieved through a registration service, thus enabling fast service-oriented terminal access. Attached Figure Description
[0024] Figure 1 This is a flowchart of a random access method provided in an embodiment of this application;
[0025] Figure 2 This is a schematic diagram showing the connection between the RRC layer entity and the MAC layer entity via QoL in an embodiment of this application;
[0026] Figure 3 This is a schematic diagram of the random access response in an embodiment of this application;
[0027] Figure 4 This is a flowchart of another random access method provided in the embodiments of this application;
[0028] Figure 5 This is a flowchart of a random access procedure provided in an embodiment of this application;
[0029] Figure 6 This is a schematic diagram of the structure of a terminal provided in an embodiment of this application;
[0030] Figure 7 This is a schematic diagram of the structure of a network-side device provided in an embodiment of this application;
[0031] Figure 8 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Detailed Implementation
[0032] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0033] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.
[0034] To facilitate understanding of the embodiments of this application, the following issues will be explained first.
[0035] The scenarios applicable to the embodiments of this application include, but are not limited to, 6G communication systems and other communication systems.
[0036] In the 6G protocol stack, an AI Plane and a Data Plane can be introduced. These two planes are integrated into the Control Plane and User Plane of the protocol stack to implement the protocol stack functions and services required by the terminal, such as User Equipment (UE) and the terminal's service transmission, thereby realizing a flexible wireless network.
[0037] Flexibility can be understood as configuring different protocol stack functions according to user needs (such as service QoS requirements, service type requirements, slice type, etc.). For example, protocol functions can be designed in the form of Service Oriented Function (SOF) and provided to users in the form of "services". The internal functions of the "service" itself can be defined by the receiving end and the sending end according to their own implementation, such as artificial intelligence (AI) related models or algorithms, data plane related processing, etc.
[0038] To break through the rigid inter-layer logic constraints while adhering to the principle of equality between the receiver and transmitter in the protocol stack, and to realize the flexible capabilities of the 6G protocol stack, such as on-demand function selection, unified PDU format, low redundancy overhead, and flexible capabilities with no or light connections between protocol layers, it is necessary to break through the 5G protocol stack solution and realize SOF-based protocol functions.
[0039] To enable rapid service-oriented terminal access, this application proposes that when a terminal accesses the Radio Access Network (RAN), no bearer, such as a Signaling Radio Bearer (SRB) (e.g., SRB1 / 2 / 3), is established at the Radio Resource Control (RRC) layer. Instead, network-side authentication is achieved through service registration. This method allows for seamless handover within the RAN when the terminal moves.
[0040] In this embodiment, the RRC layer and the RRC layer entity have the same meaning and can be interchanged. The MAC layer and the MAC layer entity have the same meaning and can be interchanged.
[0041] The random access method, terminal, network-side device, and readable storage medium provided in this application will be described in detail below with reference to the accompanying drawings and through specific embodiments and application scenarios.
[0042] Please see Figure 1 , Figure 1 This is a flowchart of a random access method provided in an embodiment of this application. The method is applied to a terminal, such as... Figure 1 As shown, the method includes the following steps:
[0043] Step 11: The first RRC layer entity of the terminal sends a registration request to the first MAC layer entity of the terminal through the first link.
[0044] Step 12: Based on the registration request, the first MAC layer entity sends a random access request to the second MAC layer entity of the network-side device. This can be either contention-based or non-contention-based access; there is no limitation on this.
[0045] Step 13: The first MAC layer entity receives the random access response from the second MAC layer entity.
[0046] Step 14: Based on the random access response, after completing the establishment or registration of the terminal context, the first MAC layer entity sends a registration response to the first RRC layer entity through the second link.
[0047] In this embodiment, the first link is a link with Quality of Service (QoS) guarantee capability between the first RRC layer entity and the first Media Access Control (MAC layer) entity. This first link, i.e., a link with QoS guarantee capability, can be called a QoS Oriented Link (QoL). The second link is a link with QoS guarantee capability between the first MAC layer entity and the first RRC layer entity. This second link, i.e., a link with QoS guarantee capability, can be called a QoL. A QoL is not a bearer established between the MAC layer and the RRC layer, such as SRB1 / 2 / 3, but rather a data stream formed by data packets with the same QoS level. Different QoLs identify different QoS guarantee requirements.
[0048] It should be noted that the first link and the second link can be the same or different. That is, the RRC layer entity and MAC layer entity on the terminal side can define different QoS levels according to their respective information transmission capabilities. When sending or receiving information, the RRC layer entity and MAC layer entity on the terminal side can select different QoS levels for data transmission based on their respective understandings.
[0049] In some embodiments, the above registration request is an RRC registration request, such as Request of RRC Registration, and correspondingly, the above registration response is an RRC registration response, such as Response for RRC Registration.
[0050] In some embodiments, after the establishment or registration of the terminal context is completed, the terminal context can be further updated on both the terminal side and the network side during basic data transmission.
[0051] In the random access method of this application embodiment, the first RRC layer entity of the terminal can send a registration request to the first MAC layer entity of the terminal through a first link. Based on the registration request, the first MAC layer entity can send a random access request to the second MAC layer entity of the network-side device, receive a random access response from the second MAC layer entity, and, based on the random access response, after completing the establishment or registration of the terminal context, send a registration response to the first RRC layer entity through a second link. This first or second link is a link with QoS guarantee capabilities. Therefore, when the terminal accesses the RAN, no bearer needs to be established at the RRC layer; network-side authentication is achieved through service registration, thereby enabling fast service-oriented terminal access. Furthermore, it reduces RRC signaling overhead, eliminating the need to establish bearers such as SRBs; only simple activation information is required, laying the foundation for the SOF definition of Service Oriented RAN (SO-RAN).
[0052] In this embodiment, the service-oriented terminal access process is the first step for the terminal to request services from the network-side device. Through the access process, the terminal can obtain basic network service functions, such as SOF, from the network-side device. The access process allows for the separate establishment of contexts at the MAC and RRC layers on both the peer-to-peer terminal and network sides. No bearer (e.g., SRB1 / 2 / 3) needs to be established between the MAC and RRC layers; only the terminal's context registration process is required. The MAC layers on both the terminal and network sides interact with their respective RRC layers to complete terminal registration.
[0053] For example, see Figure 2 As shown, on the terminal side and the network side, the MAC layer and the RRC layer can be connected via a link with QoS guarantee capabilities, such as... Figure 2 The QoL (Quality of Service) values 0 through n are used for information transmission. The QoL between the MAC and RRC layers indicates the QoS requirements that need to be guaranteed during information transmission between them. Different QoL values have different QoS guarantee requirements.
[0054] After the MAC and RRC layers are activated, a Quality of Service (QoL) is established between them. The QoL on the terminal side and the network side can be the same or different. If the QoL between the MAC and RRC layers on the terminal and network sides is the same, it can be configured through RRC signaling or explicitly defined through a protocol. If the QoL between the MAC and RRC layers on the terminal and network sides is different, the MAC and RRC layers can define different QoLs according to their respective information transmission capabilities. When sending or receiving information, the MAC and RRC layers can select different QoLs for data transmission based on their respective understandings.
[0055] In some embodiments, when the MAC layer sends data to the RRC layer, the MAC layer can select an appropriate QoS level (QoL) according to the QoS requirements of the data to be sent. The data sent by the MAC layer can be encapsulated into a MAC SDU, including but not limited to request messages, control information, measurement information, etc.
[0056] In other embodiments, when the RRC layer sends data to the MAC layer, the RRC layer can select an appropriate QoS level according to the QoS requirements of the data to be sent. The data sent by the RRC layer can be encapsulated into an RRC PDU, including but not limited to control or configuration information, indication information, etc.
[0057] Optionally, when a terminal accesses the network, it initiates a registration request to the network side. The MAC layer and RRC layer transmit information through QoL, and only the terminal context registration needs to be performed at the RRC layer. When the terminal accesses the network via Msg1 (carrying the Preamble code), the terminal's identifier (such as MAC UE ID) is established at the MAC layer on the network side.
[0058] In optional embodiments of this application, different links with QoS guarantee capabilities, such as different QoLs, between the first MAC layer entity and the first RRC layer entity identify different QoS guarantee capabilities, thereby selecting the appropriate QoL to transmit data according to the QoS requirements of the data to be sent.
[0059] In optional embodiments of this application, the QoS-guaranteed link, such as QoL, between the first MAC layer entity and the first RRC layer entity is configured via RRC signaling and / or established via protocol definition.
[0060] In optional embodiments of this application, the aforementioned random access request includes a preamble, which is used to characterize the terminal's features and / or identity information for indication to the network side. That is, by defining physical layer information such as a preamble, more terminal features and / or identity information can be indicated to the network side. For example, preambles can be categorized based on terminal features; for instance, a preamble of a certain type or feature can identify a terminal for URLLC services.
[0061] In optional embodiments of this application, the random access response can be reconstructed to indicate that the MAC layer on the network side has completed the establishment or registration of the terminal context. The random access response may include at least one of the following: Hybrid Automatic Repeat reQuest (HARQ) configuration information and a first identifier. The HARQ configuration information can be used for data reselection to achieve highly feasible data transmission. The first identifier identifies the terminal's identity at the MAC layer, uniquely identifying the terminal at the MAC layer. Based on this identifier, it can be indicated that the MAC layer on the network side has completed the establishment or registration of the terminal context. The first identifier may be, for example, the MAC UE ID. Since the MAC layer can schedule multiple cells or a single cell, the MAC UE ID is not a cell-level parameter; it remains unchanged as long as the terminal does not perform a MAC layer handover.
[0062] For example, see Figure 3 As shown, in a specific embodiment of this application, the random access response may include not only existing information such as ULGrant and Timing Advance Command, but also MAC UE ID and HARQ configuration information. The MAC UE ID is used to identify the terminal's identity at the MAC layer. The HARQ configuration information may include DL-Mod, DL-PNI (Process Number Indicator), DL-Cat, DL-OffsetIndicator, UL-Mod, UL-PNI, UL-Cat, and UL-OffsetIndicator. DL-Mod and UL-Mod indicate the HARQ mode, for example, each 2 bits, indicating four modes: synchronous HARQ+(retransmission) adaptive mode, synchronous HARQ+(retransmission) non-adaptive mode, asynchronous HARQ+(retransmission) adaptive mode, and asynchronous HARQ+(retransmission) non-adaptive mode. DL-PNI and UL-PNI indicate the number of HARQ processes, for example, each 2 bits, indicating that four process numbers are available. DL-Cat and UL-Cat indicate terminal capabilities, for example, each using 4 bits to indicate 16 terminal capabilities. DL-OffsetIndicator and UL-OffsetIndicator indicate time offsets, for example, each using 4 bits to indicate 16 time offsets, with units including symbols, slots, and subframes.
[0063] In optional embodiments of this application, when the random access response includes HARQ configuration information, the random access response can be acknowledged / negatively acknowledged (ACK / NACK) via the HARQ process. After receiving the random access response, the terminal's first MAC layer entity can send ACK / NACK feedback to the network-side device's second MAC layer entity via the HARQ process, so that the network-side device can confirm whether the terminal has completed the establishment or registration of the terminal context. For example, if ACK information is received, it can be confirmed that the terminal has completed the establishment or registration of the terminal context; while if NACK information is received, it can be confirmed that the terminal has not completed the establishment or registration of the terminal context.
[0064] In an optional embodiment of this application, the registration request includes: a capability identifier for the terminal at the RRC layer. This capability identifier can be obtained by uniformly identifying the terminal according to different data processing capabilities, and can indicate at least, but is not limited to, the following: AI capabilities supported by the terminal, service type capabilities, and the terminal's own capability characteristics. The service type capabilities include, but are not limited to, Ultra-Reliable Low Latency Communication (URLLC) services, Massive Machine Type Communication (mMTC) services, Enhanced Mobile Broadband (eMBB) services, and newly added high-reliability, low-latency, high-speed services. The terminal's own capability characteristics include, but are not limited to, IoT terminals, body area network terminals, vehicle-to-everything (V2X) terminals, and ordinary terminals.
[0065] In optional embodiments of this application, the registration response includes at least one of the following: HARQ configuration information and a first identifier; the first identifier is used to identify the identity of the terminal at the MAC layer.
[0066] Please see Figure 4 , Figure 4 This is a flowchart of a random access method provided in an embodiment of this application. The method is applied to a network-side device, such as a base station or a RAN network element. Figure 4 As shown, the method includes the following steps:
[0067] Step 41: The second MAC layer entity of the network-side device receives a random access request from the first MAC layer entity of the terminal. This can be either contention-based or non-contention-based access; there is no limitation on this.
[0068] Step 42: Based on the random access request, the second MAC layer entity sends a random access response to the first MAC layer entity after completing the establishment or registration of the terminal context.
[0069] Step 43: The second MAC layer entity sends the terminal's registration request to the second RRC layer entity of the network-side device through the third link.
[0070] Step 44: The second RRC layer entity sends the terminal's registration response to the second MAC layer entity through the fourth link.
[0071] In this embodiment, the third link is a QoS-guaranteed link between the second MAC layer entity and the second RRC layer entity. This third link, also known as the QoS-guaranteed link, can be referred to as QoL. The fourth link is also a QoS-guaranteed link between the second RRC layer entity and the second MAC layer entity. This fourth link, also known as the QoS-guaranteed link, can be referred to as QoL. QoL is not a bearer established between the MAC layer and the RRC layer, such as SRB1 / 2 / 3, but rather a data stream formed by data packets with the same QoS level. Different QoLs identify different QoS guarantee requirements.
[0072] It should be noted that the third and fourth links can be the same or different. That is, the RRC and MAC layer entities on the network side can define different QoS levels according to their respective information transmission capabilities. When sending or receiving information, the RRC and MAC layer entities on the network side can choose different QoS levels for data transmission based on their respective understandings.
[0073] In some embodiments, the registration request of the terminal is an RRC registration request such as a UE RRCRegistration Request, and correspondingly, the registration response of the terminal is an RRC registration response such as a UE RRCRegistration Response.
[0074] In some embodiments, after the establishment or registration of the terminal context is completed, the terminal context can be further updated on both the terminal side and the network side during basic data transmission.
[0075] In the random access method of this application embodiment, after receiving a random access request from the first MAC layer entity of the terminal, the second MAC layer entity of the network-side device can, based on the random access request and after completing the establishment or registration of the terminal context, send a random access response to the first MAC layer entity. Then, through a third link, it sends a terminal registration request to the second RRC layer entity of the network-side device. The second RRC layer entity then sends a terminal registration response to the second MAC layer entity through a fourth link. Therefore, when a terminal accesses the RAN, no bearer needs to be established at the RRC layer; instead, network-side authentication is achieved through service registration, thus enabling fast service-oriented terminal access. Furthermore, it reduces RRC signaling overhead, eliminating the need to establish bearers such as SRBs, requiring only simple activation information, thus laying the foundation for the SOF definition of Service Oriented RAN (SO-RAN).
[0076] In optional embodiments of this application, different links with QoS guarantee capabilities, such as different QoLs, between the second MAC layer entity and the second RRC layer entity identify different QoS guarantee capabilities, thereby selecting the appropriate QoL to transmit data according to the QoS requirements of the data to be sent.
[0077] In optional embodiments of this application, the QoS-guaranteed link, such as QoL, between the second MAC layer entity and the second RRC layer entity is configured via RRC signaling and / or established via protocol definition.
[0078] In optional embodiments of this application, the aforementioned random access request includes a preamble, which is used to characterize the terminal's features and / or identity information for indication to the network side. That is, by defining physical layer information such as a preamble, more terminal features and / or identity information can be indicated to the network side. For example, preambles can be categorized based on terminal features; for instance, a preamble of a certain type or feature can identify a terminal for URLLC services.
[0079] In optional embodiments of this application, the random access response can be reconstructed to indicate that the MAC layer on the network side has completed the establishment or registration of the terminal context. The random access response may include at least one of the following: HARQ configuration information and a first identifier. The first identifier is used to identify the terminal's identity at the MAC layer, and is a unique identifier for a terminal at the MAC layer. Based on this identifier, it can be indicated that the MAC layer on the network side has completed the establishment or registration of the terminal context. The first identifier may be, for example, a MAC UE ID.
[0080] In an optional embodiment of this application, after sending a random access response to the first MAC layer entity and before sending a terminal registration request to the second RRC layer entity, the second MAC layer entity receives ACK information fed back by the first MAC layer entity through the HARQ process. That is, after recognizing that the terminal has completed the establishment or registration of its terminal context, the second MAC layer entity initiates a terminal registration request to the second RRC layer entity to complete the establishment or registration of the terminal context at the network-side RRC layer.
[0081] In optional embodiments of this application, the registration request of the terminal may include, but is not limited to, at least one of the following: HARQ configuration information, a first identifier, physical layer power for receiving the preamble, preamble format, and preamble indication information; the first identifier is used to identify the terminal's identity at the MAC layer.
[0082] The following is combined with Figure 5 The random access process in the embodiments of this application will be described.
[0083] like Figure 5 As shown, the terminal and network communicate via the Uu port. The process of the terminal initiating a registration request service to the network includes the following steps:
[0084] S51: The RRC layer entity on the terminal side sends a registration request message, such as Requestof RRC Registration, to the MAC layer entity on the terminal side. This message carries the terminal's capability identifier at the RRC layer.
[0085] S52: After receiving the registration request from the RRC layer entity on the terminal side, the MAC layer entity on the terminal side initiates a Random Access Request (RA Request) to the MAC layer entity on the network side, such as Msg1. Msg1 carries the terminal's access preamble, which represents the terminal's characteristics and / or identity information. This may be contention-based access or non-contention-based access.
[0086] S53: After receiving Msg1, the MAC layer on the network side constructs a random access response, such as Msg2, and sends Msg2 to the MAC layer entity on the terminal side. Msg2 carries HARQ configuration information, MAC UE ID, etc. Through Msg2, the MAC layers on the terminal side and the network side can complete the terminal context establishment.
[0087] S54: After receiving Msg2, the MAC layer entity on the terminal side completes the HARQ process and sends an ACK / NACK response to Msg2 through the HARQ process. This means that a HARQ process is introduced into Msg2. The HARQ process used by Msg2 can be the default value ProcessID == 0, or any other value. The terminal only needs to provide feedback.
[0088] S55: Performed separately on the terminal side and the network side:
[0089] S55-A: After the MAC layer entity on the terminal side confirms that Msg2 has been received correctly and completes the establishment or registration of the terminal context at the MAC layer, it sends a registration response message, such as Response for RRCRegistration, to the RRC layer entity on the terminal side. This message carries at least one of the following: MAC UE ID, HARQ configuration information, etc.
[0090] S55-B: After the MAC layer entity on the network side receives the feedback ACK information, it confirms that the terminal has completed registration and sends an RRC registration request message, such as a UE RRC Registration Request, to the RRC layer entity on the network side. This message carries at least one of the following: MAC UE ID, HARQ configuration information, physical layer power of the receiving terminal's preamble, preamble format, and preamble code indication information.
[0091] S56: The RRC layer entity on the network side sends a registration success response to the MAC layer entity on the network side.
[0092] Through the above S55-S56, a basic context for the RRC-MAC terminal is established on both the terminal and network sides. The terminal obtains basic network services from the network side, such as interactive context updates and data transmission with non-customized QoS requirements.
[0093] S57: When it is necessary to update the terminal context of the RRC layer, the RRC layer entity on the terminal side sends a terminal context update request message, such as UE RRC Context Update, to the RRC layer on the network side to perform related control procedures such as MAC layer configuration.
[0094] S58: The RRC layer on the network side sends a context update complete message, such as UERRC Context Update Complete, to the RRC layer on the terminal side.
[0095] Please see Figure 6 , Figure 6This is a schematic diagram of the structure of a terminal provided in an embodiment of this application, such as... Figure 6 As shown, terminal 60 includes: a first RRC layer entity 61 and a first MAC layer entity 62.
[0096] The first RRC layer entity 61 is used to: send a registration request to the first MAC layer entity 62 through a first link, wherein the first link is a QoS-guaranteed link between the first RRC layer entity 61 and the first MAC layer entity 62.
[0097] The first MAC layer entity 62 is configured to: send a random access request to the second MAC layer entity of the network-side device based on the registration request, receive a random access response from the second MAC layer entity, and, based on the random access response, after completing the establishment or registration of the terminal context, send a registration response to the first RRC layer entity 61 through a second link, wherein the second link is a QoS-guaranteed link between the first MAC layer entity 62 and the first RRC layer entity 61.
[0098] Optionally, the different QoS-guaranteed links between the first MAC layer entity 62 and the first RRC layer entity 61 identify different QoS-guaranteed capabilities.
[0099] Optionally, the QoS-guaranteed link between the first MAC layer entity 62 and the first RRC layer entity 61 is configured via RRC signaling and / or established via protocol definition.
[0100] Optionally, the random access request includes a preamble, which is used to characterize the features and / or identity information of the terminal.
[0101] Optionally, the random access response includes at least one of the following: HARQ configuration information and a first identifier; wherein the first identifier is used to identify the identity of the terminal at the MAC layer.
[0102] Optionally, when the random access response includes HARQ configuration information, after receiving the random access response, the first MAC layer entity 62 sends an ACK / NACK response to the second MAC layer entity through the HARQ process.
[0103] Optionally, the registration request includes: the terminal's capability identifier at the RRC layer;
[0104] And / or, the registration response includes at least one of the following: HARQ configuration information, a first identifier; wherein the first identifier is used to identify the identity of the terminal at the MAC layer.
[0105] The terminal 60 in this embodiment can implement the above. Figure 1 The various processes of the method embodiments shown can achieve the same technical effect, and will not be described again here to avoid repetition.
[0106] Please see Figure 7 , Figure 7 This is a schematic diagram of the structure of a network-side device provided in an embodiment of this application. This network-side device may be, for example, a base station or a RAN network element. Figure 7 As shown, the network-side device 70 includes: a second RRC layer entity 71 and a second MAC layer entity 72.
[0107] The second MAC layer entity 72 is configured to: receive a random access request from the first MAC layer entity of the terminal; based on the random access request, after completing the establishment or registration of the terminal context, send a random access response to the first MAC layer entity; and send a terminal registration request to the second RRC layer entity 71 through a third link, wherein the third link is a QoS-guaranteed link between the second MAC layer entity 72 and the second RRC layer entity 71.
[0108] The second RRC layer entity 71 is used to send a terminal registration response to the second MAC layer entity 72 via a fourth link, wherein the fourth link is a QoS-guaranteed link between the second RRC layer entity 71 and the second MAC layer entity 72.
[0109] Optionally, the different QoS-guaranteed links between the second MAC layer entity 72 and the second RRC layer entity 71 identify different QoS-guaranteed capabilities.
[0110] Optionally, the QoS-guaranteed link between the second MAC layer entity 72 and the second RRC layer entity 71 is configured via RRC signaling and / or established via protocol definition.
[0111] Optionally, the random access request includes a preamble, which is used to indicate the characteristics and / or identity information of the terminal.
[0112] Optionally, the random access response includes at least one of the following: HARQ configuration information and a first identifier; wherein the first identifier is used to identify the identity of the terminal at the MAC layer.
[0113] Optionally, after sending a random access response to the first MAC layer entity and before sending the terminal registration request to the second RRC layer entity 71 of the network-side device, the second MAC layer entity 72 is further configured to: receive ACK information fed back by the first MAC layer entity through the HARQ process.
[0114] Optionally, the registration request of the terminal includes at least one of the following: HARQ configuration information, a first identifier, physical layer power for receiving the preamble, preamble format, and preamble indication information; wherein, the first identifier is used to identify the identity of the terminal at the MAC layer.
[0115] The terminal 70 in this embodiment can implement the above. Figure 4 The various processes of the method embodiments shown can achieve the same technical effect, and will not be described again here to avoid repetition.
[0116] Optional, such as Figure 8 As shown, this application embodiment also provides a communication device 80, including a processor 81, a memory 82, and a program or instructions stored in the memory 82 and executable on the processor 81. For example, when the communication device 80 is a terminal, the program or instructions executed by the processor 81 can achieve the above-mentioned functions. Figure 1 The various processes of the illustrated method embodiments can achieve the same technical effect. When the communication device 80 is a network-side device, the program or instructions executed by the processor 81 can implement the above-described... Figure 4 The various processes of the method embodiments shown can achieve the same technical effect, and will not be described again here to avoid repetition.
[0117] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they can implement the various processes of the above-described random access method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.
[0118] Computer-readable media include both permanent and non-permanent, removable and non-removable media, which can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.
[0119] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.
[0120] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.
[0121] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a service classification device (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.
[0122] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.
Claims
1. A random access method, characterized in that, include: The terminal’s first Radio Resource Control (RRC) layer entity sends a registration request to the terminal’s first Media Access Control (MAC) layer entity through a first link. The first link is a link with Quality of Service (QoS) guarantee capability between the first RRC layer entity and the first MAC layer entity. Based on the registration request, the first MAC layer entity sends a random access request to the second MAC layer entity of the network-side device; The first MAC layer entity receives a random access response from the second MAC layer entity; Based on the random access response, after completing the establishment or registration of the terminal context, the first MAC layer entity sends a registration response to the first RRC layer entity through a second link. The second link is a QoS-guaranteed link between the first MAC layer entity and the first RRC layer entity.
2. The method according to claim 1, characterized in that, The different QoS-guaranteed links between the first MAC layer entity and the first RRC layer entity identify different QoS-guaranteed capabilities.
3. The method according to claim 1 or 2, characterized in that, The QoS-guaranteed link between the first MAC layer entity and the first RRC layer entity is configured via RRC signaling and / or established via protocol definition.
4. The method according to claim 1, characterized in that, The random access request includes a preamble, which is used to characterize the features and / or identity information of the terminal.
5. The method according to claim 1, characterized in that, The random access response includes at least one of the following: Hybrid Automatic Repeat Request (HARQ) configuration information and a first identifier; wherein the first identifier is used to identify the identity of the terminal at the MAC layer.
6. The method according to claim 5, characterized in that, When the random access response includes HARQ configuration information, after receiving the random access response, the method further includes: The first MAC layer entity sends ACK / NACK feedback to the second MAC layer entity through the HARQ process.
7. The method according to claim 1, characterized in that, The registration request includes: the terminal's capability identifier at the RRC layer; And / or, The registration response includes at least one of the following: HARQ configuration information and a first identifier; wherein the first identifier is used to identify the identity of the terminal at the MAC layer.
8. A random access method, characterized in that, include: The second MAC layer entity of the network-side device receives a random access request from the first MAC layer entity of the terminal. Based on the random access request, the second MAC layer entity sends a random access response to the first MAC layer entity after completing the establishment or registration of the terminal context; The second MAC layer entity sends a terminal registration request to the second RRC layer entity of the network-side device through a third link, wherein the third link is a QoS-guaranteed link between the second MAC layer entity and the second RRC layer entity. The second RRC layer entity sends the terminal's registration response to the second MAC layer entity through the fourth link, which is a QoS-guaranteed link between the second RRC layer entity and the second MAC layer entity.
9. The method according to claim 8, characterized in that, The different QoS-guaranteed links between the second MAC layer entity and the second RRC layer entity identify different QoS-guaranteed capabilities.
10. The method according to claim 8 or 9, characterized in that, The QoS-guaranteed link between the second MAC layer entity and the second RRC layer entity is configured via RRC signaling and / or established via protocol definition.
11. The method according to claim 8, characterized in that, The random access request includes a preamble, which is used to indicate the characteristics and / or identity information of the terminal.
12. The method according to claim 8, characterized in that, The random access response includes at least one of the following: HARQ configuration information and a first identifier; wherein the first identifier is used to identify the identity of the terminal at the MAC layer.
13. The method according to claim 8, characterized in that, After sending a random access response to the first MAC layer entity and before sending a terminal registration request to the second RRC layer entity of the network-side device, the method further includes: The second MAC layer entity receives the ACK information fed back by the first MAC layer entity through the HARQ process.
14. The method according to claim 8, characterized in that, The registration request of the terminal includes at least one of the following: HARQ configuration information, a first identifier, physical layer power for receiving the preamble, preamble format, and preamble indication information; wherein, the first identifier is used to identify the identity of the terminal at the MAC layer.
15. A terminal, characterized in that, Includes the first RRC layer entity and the first MAC layer entity; The first RRC layer entity is used to: send a registration request to the first MAC layer entity through a first link, wherein the first link is a QoS-guaranteed link between the first RRC layer entity and the first MAC layer entity. The first MAC layer entity is configured to: send a random access request to the second MAC layer entity of the network-side device based on the registration request, receive a random access response from the second MAC layer entity, and, based on the random access response, after completing the establishment or registration of the terminal context, send a registration response to the first RRC layer entity through a second link, wherein the second link is a QoS-guaranteed link between the first MAC layer entity and the first RRC layer entity.
16. A network-side device, characterized in that, Includes second RRC layer entities and second MAC layer entities; The second MAC layer entity is used to: receive a random access request from the first MAC layer entity of the terminal; based on the random access request, after completing the establishment or registration of the terminal context, send a random access response to the first MAC layer entity; and send a terminal registration request to the second RRC layer entity through a third link, wherein the third link is a link with QoS guarantee capability between the second MAC layer entity and the second RRC layer entity. The second RRC layer entity is used to: send a terminal registration response to the second MAC layer entity via a fourth link, wherein the fourth link is a QoS-guaranteed link between the second RRC layer entity and the second MAC layer entity.
17. A communication device, characterized in that, It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the random access method as described in any one of claims 1 to 7, or the steps of the random access method as described in any one of claims 8 to 14.
18. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the random access method as described in any one of claims 1 to 7, or the steps of the random access method as described in any one of claims 8 to 14.