Access Control Method and User Equipment

Abstract

The present invention provides an access control method and a user equipment in the user equipment, which can efficiently and reliably establish a radio bearer for data transmission. The access control method includes: determining a layer 2 destination ID according to information obtained from an upper layer; and establishing a radio bearer RB associated with the determined layer 2 destination ID.

Description

Technical Field

[0001] The present invention relates to the field of wireless communication technologies, and more specifically, to a method for access control and corresponding base stations and user equipment. Background Art

[0002] Vehicle-to-Everything (V2X) wireless communication technology is a new generation of information and communication technology that connects vehicles to everything. Here, V represents vehicles, and X represents any object that interacts with vehicles. Currently, X mainly includes vehicles, people, roadside traffic infrastructure, and networks.

[0003] Currently, the V2X service types that UEs perform on the PC5 interface based on NR access technology can be unicast, groupcast, or broadcast. UEs performing V2X services can be divided into transmitter UEs and receiver UEs. A UE can be either a transmitter UE or a receiver UE. However, in a connection carrying a specific V2X, the transmitter UE and the receiver UE are different UEs.

[0004] To manage the QoS of V2X services, UEs can perform transmissions based on radio bearers (RBs). As a transmitter UE, when the upper layer of the UE (which can be understood as the non-access layer or the V2X application layer) instructs the lower layer (access layer) to first send a data packet carrying V2X service-related data, a radio bearer can be established for the transmission of this data. Establishing an RB includes establishing an SDAP entity, a PDCP entity, an RLC entity, and configuring relevant transmission parameters. When the RB is established, the data related to the specific V2X service can be sent through the RB.

[0005] For a receiver UE, correspondingly, such an RB also needs to be established to process the received data packets. However, for groupcast or broadcast services, when and how the receiver UE establishes such an RB, how to maintain such an RB, and finally when to release the RB are all issues that need to be solved. Summary of the Invention

[0006] The object of the present invention is to provide an access control method and a user equipment in a user equipment that can efficiently and reliably establish a radio bearer for data transmission. Moreover, the object of the present invention is also to provide an access control method and a user equipment in a user equipment that can well maintain the established radio bearer. Furthermore, the object of the present invention is also to provide an access control method and a user equipment in a user equipment that can release the established radio bearer at an appropriate time.

[0007] According to a first aspect of the present invention, there is provided an access control method in a user equipment, including: determining a layer 2 destination ID according to information obtained from an upper layer; and establishing a radio bearer RB associated with the determined layer 2 destination ID.

[0008] According to a second aspect of the present invention, there is provided an access control method in a user equipment, including: receiving a multimedia access control protocol data unit MAC PDU and determining a layer 2 destination ID included therein; and establishing an RB associated with the determined layer 2 destination ID when the determined layer 2 destination ID is the same as the layer 2 destination ID indicated by the upper layer and there is no logical channel identity LCID / radio bearer RB associated with the determined layer 2 destination ID.

[0009] In the above access control method, it may be that the process of establishing the RB includes at least one of the following operations: establishing a packet data convergence protocol PDCP entity; establishing a radio link control RLC entity; configuring the established PDCP entity and RLC entity by using predefined or preconfigured configuration information or configuration information broadcast in system information; associating the established RB with the determined layer 2 destination ID; notifying the established RB and its associated layer 2 destination ID to the upper layer; and associating the established RB with a service data adaptation protocol SDAP entity.

[0010] In the above access control method, it may be that it further includes: when the layer 2 destination ID included in the received multimedia access control protocol data unit MAC PDU is the same as the layer 2 destination ID associated with the RB, sending the multimedia access control service data unit MAC SDU corresponding to the MAC PDU to the radio link control RLC entity of the RB.

[0011] In the above access control method, it may be that when there is one MAC SDU, the MAC SDU is sent to the RLC entity of the RB; when there are multiple MAC SDUs and the logical channel identity identifiers (LCIDs) corresponding to these MAC SDUs are the same, these MAC SDUs are sent to the RLC entity of the RB; when there are multiple MAC SDUs and the LCIDs corresponding to these MAC SDUs are different, another RB associated with the determined layer 2 destination is established, and a part of these MAC SDUs is sent to the RB, and the remaining part is sent to the other RB.

[0012] In the above access control method, it may be that it further includes: when the RB is not associated with a layer 2 source ID, associating the RB with the layer 2 source ID included in the received multimedia access control protocol data unit (MAC PDU).

[0013] In the above access control method, it may be that it further includes: when the LCIDs corresponding to the service data units (SDUs) included in the MAC PDU are different, at least indicating to the upper layer the number of RBs that need to be established.

[0014] In the above access control method, it may be that it further includes: when the configuration information of the RLC / PDCP entity is obtained from the system information broadcast in the cell, when it is detected that the corresponding configuration information has changed in the obtained system information, reconstructing the corresponding RLC / PDCP entity or reconstructing the corresponding RB.

[0015] In the above access control method, it may be that it further includes: when the upper layer updates the list of layer 2 destination IDs, when the user equipment determines that the determined layer 2 destination ID is no longer in the updated list, releasing the corresponding RB or RLC / PDCP entity; when the upper layer updates the mapping relationship between vehicle-to-everything (V2X) services and layer 2 destination IDs, when the user equipment determines that the determined layer 2 destination ID no longer exists or is valid, releasing the corresponding RB or RLC / PDCP entity and releasing the SDAP entity.

[0016] According to a fifth aspect of the present invention, there is provided a user equipment, including: a processor; and a memory storing instructions; wherein, the instructions execute the above access control method when run by the processor.

[0017] Advantages of the Invention

[0018] The access control method and user equipment in the user equipment according to the present invention can efficiently and reliably establish a radio bearer for data transmission, and moreover, can well maintain the established radio bearer. Furthermore, the established radio bearer can be released at an appropriate time. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Through the following detailed description in conjunction with the drawings, the above and other features of the present invention will become more obvious, where:

[0020] Figure 1 The flowchart of the access control method in the user equipment according to an embodiment of the present invention is shown;

[0021] Figure 2 The flowchart of another access control method in the user equipment according to an embodiment of the present invention is shown;

[0022] Figure 3 The block diagram of the user equipment according to an embodiment of the present invention is shown. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0023] The present invention will be described in detail below in conjunction with the drawings and specific embodiments. It should be noted that the present invention should not be limited to the specific embodiments described below. In addition, for the sake of simplicity, the detailed description of the known technologies not directly related to the present invention is omitted to prevent confusion in the understanding of the present invention.

[0024] Before the specific description, several terms mentioned in the present invention are described as follows. Unless otherwise specified, the terms involved in the present invention have the following meanings

[0025] UE User Equipment User equipment

[0026] NR New Radio New generation radio technology

[0027] Sidelink Sidelink

[0028] V2X Vechile to Everything Vehicle-to-everything communication

[0029] MAC Medium Access Control Multimedia access control

[0030] MAC CE MAC control element MAC control element

[0031] LCID Logical Channle Identity Logical channel identity identifier

[0032] RB radio bear Wireless bearer

[0033] RLC Radio Link Control Radio Link Control

[0034] PDCP Packet Data Convergence Protocol Packet Data Convergence Protocol

[0035] SDAP Service Data Adaptation Protocol Service Data Adaptation Protocol

[0036] PDU Protocol Data Unit Protocol Data Unit

[0037] SDU Service Data Unit Service Data Unit

[0038] PSID Provider Service Identifier Provider Service Identifier

[0039] ITS-AID Intelligent Transport Systems Application Identifier Intelligent Transport Systems Application Identifier

[0040] Layer 2 destination ID Layer 2 destination identity Layer 2 destination identity

[0041] Layer 2 source ID Layer 2 source identity Layer 2 source identity

[0042] To perform V2X services, the UE needs to know what kind of services it needs to perform. At the upper layer of the UE, such as the V2X application layer, these information can be provided to the UE. These information include:

[0043] - V2X service list

[0044] - The PSID or ITS-AID of the V2X application, and the geographical area location information applicable to this application

[0045] - The mapping between the service type and the V2X frequency, and the applicable geographical area information

[0046] For example, for a certain V2X service, its PSID or ITS-AID is X1, then the V2X frequency corresponding to X1 is F1, and the area information is D, which means that service X1 needs to be executed at frequency F1 in area D.

[0047] - Mapping information of layer 2 destination ID and V2X services in broadcast mode

[0048] For example, for a V2X service in broadcast mode, if its PSID or ITS-AID is X2, then the corresponding layer 2 destination ID is Y2.

[0049] - Mapping information of layer 2 destination ID and V2X services in multicast mode

[0050] For example, for a V2X service in multicast mode, if its PSID or ITS-AID is X3, then the corresponding layer 2 destination ID is Y3.

[0051] Mapping V2X services to specific layer 2 destination IDs is meaningful. The layer 2 destination ID can be used as an identifier for the UE to recognize a specific V2X service at the access stratum.

[0052] When the layer 2 destination ID carried in the data packet received by the UE is in the list of layer 2 destination IDs provided by the upper layer, it means that the data packet is the one the UE needs to receive; if the layer 2 destination ID carried in the data packet received by the UE does not belong to the layer 2 destination IDs provided by the upper layer, then the UE can discard the data packet.

[0053] In addition to the upper layer providing the layer 2 destination ID, the UE can also obtain the layer 2 destination ID through other means. For example, in a V2X service in multicast mode, the V2X application layer of the UE can provide information about the group identifier (groupidentifier), and then the UE converts this group ID into a layer 2 destination ID. Or based on the mapping relationship described above, map the PSID / ITS-AID of the service to the layer 2 destination ID.

[0054] It can be seen that the upper layer of the UE can directly or indirectly provide the layer 2 destination ID to the access stratum. This process can be called the process by which the UE determines the layer 2 destination ID. In this process, the layer 2 destination ID is passed to the access stratum of the receiving UE.

[0055] It should be noted that when a layer 2 destination ID is passed to the UE, the UE has a way to determine whether it belongs to the sending UE or the receiving UE. For example, along with the given layer 2 destination ID, there is other information indicating whether the UE needs to receive or send. There are two types of layer 2 destination ID lists obtained by the UE, one is the list of layer 2 destination IDs for sending, and the other is the list of layer 2 destination IDs for receiving. That is, the UE knows whether it belongs to the sending UE or the receiving UE in the ongoing V2X service.

[0056] The solutions discussed in this document are based on the UE identifying itself as a receiving UE.

[0057] In this document, related, corresponding, etc. can be used interchangeably.

[0058] In this document, the two terms "sidelink" and "V2X sidelink" can be used interchangeably.

[0059] Figure 1 The flowchart of the access control method in a user equipment according to an embodiment of the present invention is shown. As Figure 1 shown, the access control method includes step S110 and step S120.

[0060] In step S110, the UE determines the layer 2 destination ID according to the information obtained from the upper layer.

[0061] In step S120, the UE establishes an RB associated with the determined layer 2 destination ID.

[0062] According to the above access control method, when the UE determines the layer 2 destination ID, it establishes an RB associated with the determined layer 2 destination ID, thereby enabling the efficient and reliable establishment of a radio bearer for data transmission.

[0063] Figure 2 The flowchart of another access control method in a user equipment according to an embodiment of the present invention is shown. As Figure 2 shown, the access control method includes step S210 and step S220.

[0064] In step S210, the UE receives a MAC PDU and determines the layer 2 destination ID included therein.

[0065] In step S220, when the determined layer 2 destination ID is the same as the layer 2 destination ID indicated by the upper layer and there is no LCID / RB associated with the determined layer 2 destination ID, the UE establishes an RB associated with the determined layer 2 destination ID.

[0066] According to the above access control method, when the layer 2 destination ID included in the MAC PDU is the same as the layer 2 destination ID indicated by the upper layer and there is no LCID / RB associated with this layer 2 destination ID, the UE establishes an RB associated with this layer 2 destination ID, thereby enabling the efficient and reliable establishment of a radio bearer for data transmission.

[0067] Hereinafter, several embodiments of the present invention will be described in detail.

[0068] Embodiment 1

[0069] When the receiving UE determines a Layer 2 destination ID, a radio bearer is established, which is bound or associated with the determined Layer 2 destination ID.

[0070] The so-called binding or association means that when a MAC PDU is received and the Layer 2 destination ID carried in the MAC PDU is the Layer 2 destination ID determined by the UE, the MAC SDU corresponding to this MAC PDU will be sent to the RB bound to the Layer 2 destination ID for processing. Specifically, it can refer to sending it to the RLC entity, PDCP entity, and SDAP entity belonging to the RB for processing.

[0071] One implementation of the above solution can be

[0072] When the upper layer of the UE determines a Layer 2 destination ID, it indicates the Layer 2 destination ID to the lower layer. Preferably, it is the RRC layer. Based on this indication, the RRC layer triggers the RB establishment process, and the purpose of this process is to establish an associated RB for the Layer 2 destination ID. Specifically, it can include one or more of the following operations:

[0073] 1) Establish a PDCP entity. By default, only one PDCP entity can be established;

[0074] 2) Establish an RLC entity. By default, only one RLC entity can be established;

[0075] 3) Configure the established PDCP entity and RLC entity using pre-defined or pre-configured configuration information or configuration information broadcast in the system information.

[0076] For example, the pre-configured information for the PDCP entity can include

[0077] - Setting the duration of the reordering timer t-Reordering,

[0078] - Setting the duration of the discard timer discardTimer,

[0079] - Setting the length of the PDCP SN (Sequence Number) pdcp-SN-Size.

[0080] For example, the above parameters can be set as shown in the following table, indicating that the length of the PDCP SN is set to 16 bits, and the durations of the reordering timer t-Reordering and the discard timer discardTimer are undefined, indicating that they can be defined by the receiving UE itself.

[0081] Name Value PDCP configuration pdcp-SN-Size 16 t-Reordering Undefined discardTimer Undefined

[0082] The configuration information for the RLC entity may at least include:

[0083] - Configuration of the transmission mode of the RLC entity

[0084] - Configuration of the SN length of the RLC

[0085] - Logical channel ID

[0086] For example, the above parameters can be set as shown in the following table. The value of RLC configuration is UM, indicating that the mode of the configured RLC entity is Unacknowledged Mode (UM); the value of the sequence number (SN) length of the RLC is 6 bits; the logical channel ID is Undefined, indicating that it is defined by the UE itself. It should be noted that although the LCID can be customized by the UE, once the RB is established, its corresponding LCID is also determined and associated with the RB. Since this RB is associated with a certain layer 2 destination ID, it can also be understood that this LCID is also associated with this layer 2 destination ID, or it can be understood that an RB can be determined by its associated layer 2 destination ID and LCID.

[0087] Name Value RLC configuration UM SN-field-Size 6 logicalChannelIdentity Undefined

[0088] Further optionally, if the configuration information of RLC / PDCP for broadcast services is different from the configuration information of RLC / PDCP for multicast services, that is, the UE includes the configuration information of RLC / PDCP for broadcast services and the configuration information of RLC / PDCP for multicast services in the received system message, then the UE configures using the corresponding configuration information according to whether the service corresponding to the layer 2 destination ID it determines is of the broadcast type or the multicast type.

[0089] Further, it can also be that the predefined configuration information of RLC / PDCP is different from the configuration information of RLC / PDCP included in the system information received by the cell where the UE is located. Then the UE can always use the configuration information of RLC / PDCP included in the system information to configure the above RLC entity / PDCP entity.

[0090] 4) Associate the established RB with the determined layer 2 destination ID.

[0091] 5) Optionally, the established RB and its associated layer 2 destination ID can be notified to the upper layer.

[0092] 6) And optionally, associate the established RB with the SDAP entity. For the established RB, if there already exists an SDAP entity associated with the layer 2 destination ID associated with this RB, then simply associate the established RB with the SDAP entity;

[0093] If there does not yet exist an SDAP entity associated with the layer 2 destination ID corresponding to this RB, then an SDAP entity needs to be established.

[0094] The configuration information of the SDAP entity can also be broadcast by system information or predefined.

[0095] Embodiment 2

[0096] Based on Embodiment 1, after an RB associated with a certain layer 2 destination ID is established, when the UE receives a MAC PDU, and the layer 2 destination ID carried in this MAC PDU is the same as the layer 2 destination ID associated with this RB, then the MAC SDU corresponding to this MAC PDU is sent to the RLC entity of this RB. Here, the MAC SDU corresponding to the MAC PDU refers to one or more MAC SDUs contained in the MAC PDU obtained after the MAC PDU passes through a disassembly and demultiplexing entity.

[0097] If it contains only one MAC SDU, then this MAC SDU can be sent to the RLC entity of this RB.

[0098] If it contains multiple MAC SDUs and the LCIDs corresponding to these MAC SDUs are the same, then these MAC SDUs can be sent to the RLC entity of this RB.

[0099] If it contains multiple MAC SDUs and the LCIDs corresponding to these SDUs are different, then the UE indicates this information to the upper layer. Based on this information or this indication, the RRC triggers the establishment of an RB, and the specific establishment process is the same as that in Embodiment 1. Then the UE can choose to send one of the SDUs to the RLC entity of the previously established RB, and then send the other SDUs to the RLC entity of the newly established RB.

[0100] For example, the UE establishes an association between RB0 and a layer 2 destination ID. When the UE receives a MAC PDU containing the layer 2 destination ID, and there are two MAC SDUs in this MAC PDU, the LCID corresponding to SDU-1 is 3, and the LCID corresponding to SDU-2 is 5. Then the MAC can send an indication to the RRC to trigger the establishment of a new RB also associated with this layer 2 destination ID, which is called RB1 here. Then SDU-1 is sent to the RLC entity of RB0, and SDU-2 is sent to the RLC entity of RB1 for processing.

[0101] Embodiment 3

[0102] In addition to carrying the layer 2 destination ID, the MAC PDU also carries the layer 2 source ID. Based on Embodiment 1 or 2, if this already established RB has not been associated with any layer 2 source ID, then when receiving this MAC PDU, the UE can associate this RB with this layer 2 source ID.

[0103] Specifically, the MAC layer can indicate both the layer 2 source ID and the layer 2 destination ID to the RRC layer, and the RRC layer associates the corresponding RB with the layer 2 source ID; if this RB has already been associated with a certain layer 2 source ID, and this layer 2 source ID is different from the layer 2 source ID carried in this MAC PDU, then the MAC layer notifies the RRC layer of this information, and the RRC layer triggers the establishment of a new RB. The specific establishment process is the same as that in Embodiment 1, except that the established RB is not only associated with the layer 2 destination ID carried in this MAC PDU, but also associated with the layer 2 source ID carried in this MAC PDU, and the newly established RB is associated with the SDAP entity associated with the previously established RB.

[0104] It is mentioned in Embodiment 1 that the established RB can be determined by its associated layer 2 destination ID and LCID. Based on this embodiment, it can be further understood that the established RB can be determined by its associated layer 2 destination ID, layer 2 source ID, and LCID.

[0105] Therefore, for a MAC PDU, which carries the layer 2 destination ID and the layer 2 source ID, and the LCID is carried in the MAC sub-header corresponding to a certain MAC SDU included in the MAC PDU, these three parameters can uniquely determine which RB the received MAC SDU can be received and processed by.

[0106] Embodiment 4

[0107] The difference between Embodiment 4 and Embodiment 1 is the moment of triggering the establishment of the RB.

[0108] In Embodiment 1, when the UE determines the Layer 2 destination ID, it triggers the establishment of a relevant RB. In this embodiment, when the UE receives a MAC PDU carrying the same Layer 2 destination ID as the Layer 2 destination ID indicated by the upper layer, and when the UE determines that there is no LCID / RB associated with this Layer 2 destination ID, the MAC can indicate this information to the RRC layer; the RRC layer triggers the establishment of a relevant RB based on this information or this indication.

[0109] The specific establishment process can be the same as the establishment process in Embodiment 1. Optionally, in addition to being associated with the Layer 2 destination ID carried in the MAC PDU, the established RB can also be associated with the Layer 2 source ID carried in the MAC PDU. Optionally, the UE can configure the LCID of the established RB to have the same value as the LCID carried in the subheader corresponding to the MAC SDU included in the MAC PDU, so that the established RB is associated with a set of Layer 2 destination ID, Layer 2 source ID, and LCID.

[0110] Once the RB is established, in the subsequent data reception process:

[0111] When the UE receives a MAC PDU carrying the same Layer 2 destination ID as the Layer 2 destination ID indicated by the upper layer, and there is a corresponding LCID / RB associated with this Layer 2 destination ID, then the MAC SDU corresponding to the MAC PDU is sent to the RLC entity of the corresponding RB for processing. After the MAC SDU is sent to the RLC layer, it can be called an RLC PDU.

[0112] One specific implementation method can be:

[0113] When the UE receives a MAC PDU, the UE first determines whether the carried Layer 2 destination ID is the same as the Layer 2 destination ID indicated by the upper layer:

[0114] If they are not the same, the MAC PDU is discarded; if they are the same, it is further determined whether there is a corresponding LCID / RB associated with this Layer 2 destination ID.

[0115] If there is no corresponding LCID / RB associated with this Layer 2 destination ID, then the UE can indicate to the upper layer. Based on this indication, the upper layer can trigger the establishment of an RB associated with this Layer 2 destination ID. The specific establishment process can refer to the RB establishment process in Embodiment 1;

[0116] If there is a corresponding radio bearer (RB) associated with this layer 2 destination ID, the data carried by the MAC PDU can be sent to this RB or the RLC entity of the RB for processing. Optionally, if there is a corresponding RB associated with this layer 2 destination ID, it can further be determined which RB among one or more RBs associated with this layer 2 destination ID has a layer 2 source ID associated with it that is the same as the layer 2 source ID carried in this MAC PDU, or it can be determined whether there is an RB that is associated with both the layer 2 source ID and the layer 2 destination ID carried in this MAC PDU:

[0117] If there is no such RB, the UE can indicate to the upper layer. Based on this indication, the upper layer can trigger the establishment of an RB that is associated with both this layer 2 destination ID and this layer 2 source ID. The specific establishment process can refer to Embodiment 3;

[0118] If there is such an RB (one or more), it can be considered that there is an RB that is associated with both the layer 2 source ID and the layer 2 destination ID carried in this MAC PDU. Then, the data carried by the MAC PDU can be sent to this RB or the RLC entity of the RB for processing. Optionally, if there is such an RB, the UE can further determine whether there is an RB among these RBs whose LCID is the same as the LCID corresponding to a certain MAC SDU contained in the MAC PDU. This LCID corresponding to the MAC SDU can be in the subheader corresponding to this MAC SDU contained in the MAC PDU.

[0119] For an existing RB that is associated with both the layer 2 source ID and the layer 2 destination ID in the MAC PDU, its LCID has been determined. Then

[0120] If among these RBs, there is such an RB, that is, the LCID of this RB is the same as the LCID corresponding to the MAC SDU contained in the MAC PDU, then this MAC SDU can be sent to this RB or the RLC entity of the RB for processing;

[0121] If there is no such RB, that is, although these RBs are simultaneously associated with the layer 2 source ID and the layer 2 destination ID carried in this MAC PDU, but the LCIDs configured for these RBs are not the same as the LCID corresponding to the MAC SDU contained in the MAC PDU, then the UE can indicate to the upper layer. Based on this indication, the upper layer can trigger the establishment of an RB. The established RB is associated with this layer 2 destination ID, and is also associated with this layer 2 source ID, and the LCID configured for this RB has the same value as the LCID corresponding to this MAC SDU. The specific establishment process can refer to Embodiment 3. This RB or the RLC entity of the RB is subsequently used to process the corresponding MAC SDU.

[0122] A specific implementation method 2 can be:

[0123] When the UE receives a MAC PDU, the UE first determines whether the carried layer 2 destination ID is the same as the layer 2 destination ID indicated by the upper layer:

[0124] If they are not the same, then discard this MAC PDU; if they are the same, then further determine whether there is a corresponding LCID / RB associated with the layer 2 destination ID and the layer 2 source ID contained in this MAC PDU.

[0125] If there is no corresponding LCID / RB associated with the layer 2 destination ID and the layer 2 source ID contained in this MAC PDU, then the UE can indicate to the upper layer. Based on this indication, the upper layer can trigger the establishment of an RB associated with this layer 2 destination ID. The specific establishment process can refer to Embodiment 3;

[0126] If there is such an RB (one or more), then the operations after "there is an RB that is simultaneously associated with the layer 2 source ID and the layer 2 destination ID carried in this MAC PDU" in the above-mentioned Implementation Method 1 can be performed.

[0127] Embodiment 5

[0128] Based on Embodiment 4, if the LCIDs corresponding to the SDUs contained in this MAC PDU are different, then the MAC also needs to indicate to the upper layer the number of RBs that need to be established, and the optional values of the LCIDs corresponding to each RB. Here, the UE can set the LCIDs corresponding to the RLCs of these established RBs to be the same as the LCIDs corresponding to the SDUs contained in the MAC PDU.

[0129] For example, SDU-1 and SDU-2 are included in the MAC PDU, and their corresponding LCIDs are LCID-1 and LCID-2 respectively. Then, based on the indication from the underlying layer (MAC layer), RRC establishes two RBs, called RB0 and RB1. The LCID value of the RLC entity of RB0 can be set to the value of LCID-1, and the LCID value of the RLC entity of RB1 can be set to the value of LCID-2. Therefore, SDU-1 can be processed by the RLC entity of RB0, and SDU-2 can be processed by the RLC entity of RB1.

[0130] Subsequently, if the UE receives a MAC PDU containing the layer 2 destination ID, for the SDU with the corresponding LCID of LCID-1 included therein, it is sent to RB0 for processing, and for the SDU with the corresponding LCID of LCID-2 included therein, it is sent to RBl for processing.

[0131] Embodiment 6

[0132] Based on Embodiment 1 or 4, if the configuration information of the RLC / PDCP entity is obtained by the UE from the system information broadcast in the cell, then when the UE moves from one cell to another cell and the UE detects that the corresponding configuration information has changed in the obtained system information, the UE needs to re-establish the corresponding RLC / PDCP entity or re-establish the corresponding RB.

[0133] The re-establishment includes:

[0134] 1) Re-establishing the RLC entity may include discarding all RLC SDUs or RLC PDUs, and / or stopping and resetting all timers, and / or resetting variables to their initial values, etc.

[0135] 2) Re-establishing the PDCP entity may include stopping and resetting the t-Reordering timer, and / or sending all PDCP SDUs to the upper layer in ascending order, and / or resetting variables to their initial values, etc.

[0136] Embodiment 7

[0137] Based on Embodiment 1 or 4, when the upper layer updates the list of layer 2 destination IDs, when the access stratum of the UE, preferably when the RRC layer determines that the previously determined layer 2 destination ID is no longer in the updated list, the release process of the corresponding RB or RLC / PDCP entity is triggered.

[0138] It can also be that when the upper layer updates the mapping relationship between V2X services and layer 2 destination IDs, when the access stratum of the UE determines that the previously determined layer 2 destination ID no longer exists or is valid, the release process of the corresponding RB or RLC / PDCP entity is triggered, as well as the release of the SDAP entity.

[0139] This release process may include one or more of the following operations:

[0140] 1) Releasing the RLC entity, which may include discarding all RLC SDUs or RLC PDUs

[0141] 2) Releasing the PDCP entity, which may include sending all PDCP SDUs to the upper layer in ascending order.

[0142] 3) Releasing the SDAP entity.

[0143] Embodiment 8

[0144] On the basis of establishing an RB (for example, establishing an RB according to the method of Embodiment 1 or 4), the UE may configure a timer for each established RB. This timer may be configured at the RLC layer. When this RB or the RLC entity of this RB is established, the timer is started. When the RLC entity of a certain RB receives data sent from the lower layer, such as a MAC SDU, then the timer is restarted. When the timer runs out, the RLC indicates to the upper layer, for example, to the RRC layer; based on this indication, the upper layer of the UE may trigger the release process of the corresponding RB or RLC / PDCP entity, and the release of the SDAP entity. The specific release process may refer to Embodiment 7. In addition, when the reconstruction situation mentioned in Embodiment 6 occurs, the timer may also be restarted.

[0145] This timer may also be configured at the MAC layer. The MAC layer sets a timer for each logical channel. When data is sent to a certain logical channel, its corresponding timer is restarted. When the timer runs out, the MAC indicates to the upper layer, for example, to the RRC layer; based on this indication, the upper layer of the UE may trigger the release process of the corresponding RB or RLC / PDCP entity, and the release of the SDAP entity. The specific release process may refer to Embodiment 7. Here, the "corresponding RB" refers to the RB to which this logical channel belongs, or the RB with this logical channel number.

[0146] Embodiment 9

[0147] On the basis of establishing the RB (for example, establishing the RB according to the method of Embodiment 1 or 4), the UE can also configure a timer for each group of Layer 2 source IDs and Layer 2 destination IDs. The difference from Embodiment 8 is that multiple RBs can be associated with a group of Layer 2 source IDs and Layer 2 destination IDs. As long as there is data received being processed in these multiple RBs, the timer can be restarted. When the timer runs out, the release process of the corresponding RB or RLC / PDCP entity can be triggered, as well as the release of the SDAP entity. The specific release process can refer to Embodiment 7. In addition, when the reconstruction situation mentioned in Embodiment 6 occurs, the timer can also be restarted.

[0148] Such a timer can be configured in the SDAP layer, and one such timer is configured for each SDAP entity. When the SDAP entity is established, the timer is started; when the SDAP entity processes the data provided by the lower layer, the timer can be restarted. When the timer runs out, the SDAP can indicate to the upper layer to trigger the release process of the corresponding RB or RLC / PDCP entity, as well as the release of the SDAP entity. Here, the "corresponding RB" refers to all RBs associated with this group of Layer 2 source IDs and Layer 2 destination IDs.

[0149] Figure 3 The block diagram of the user equipment UE30 according to an embodiment of the present invention is shown. As Figure 3 shown, the UE30 includes a processor 310 and a memory 320. The processor 310 can include, for example, a microprocessor, a microcontroller, an embedded processor, etc. The memory 320 can include, for example, a volatile memory (such as a random access memory RAM), a hard disk drive (HDD), a non-volatile memory (such as a flash memory), or other memories, etc. Program instructions are stored on the memory 320. When the instructions are run by the processor 310, the above access control method in the user equipment described in detail in the present invention can be executed.

[0150] The program running on the device according to the present invention can be a program that enables a computer to implement the functions of the embodiments of the present invention by controlling a central processing unit (CPU). The program or the information processed by the program can be temporarily stored in a volatile memory (such as a random access memory RAM), a hard disk drive (HDD), a non-volatile memory (such as a flash memory), or other memory systems.

[0151] Programs for implementing the functions of the embodiments of the present invention can be recorded on a computer-readable recording medium. The corresponding functions can be implemented by causing a computer system to read the programs recorded on the recording medium and execute these programs. The so-called "computer system" here can be a computer system embedded in the device, and can include an operating system or hardware (such as peripheral devices). The "computer-readable recording medium" can be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a recording medium for short-time dynamic storage of programs, or any other recording medium readable by a computer.

[0152] The various features or functional modules of the devices used in the above embodiments can be implemented or executed by circuits (for example, single-chip or multi-chip integrated circuits). Circuits designed to execute the functions described in this specification can include general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination of the above devices. The general-purpose processor can be a microprocessor, or any existing processor, controller, microcontroller, or state machine. The above circuits can be digital circuits or analog circuits. In the case where new integrated circuit technologies that replace existing integrated circuits emerge due to the progress of semiconductor technology, one or more embodiments of the present invention can also be implemented using these new integrated circuit technologies.

[0153] In addition, the present invention is not limited to the above embodiments. Although various examples of the embodiments have been described, the present invention is not limited thereto. Fixed or non-mobile electronic devices installed indoors or outdoors can be used as terminal devices or communication devices, such as AV devices, kitchen devices, cleaning devices, air conditioners, office equipment, vending machines, and other household appliances, etc.

[0154] As described above, the embodiments of the present invention have been described in detail with reference to the accompanying drawings. However, the specific structure is not limited to the above embodiments, and the present invention also includes any design changes that do not deviate from the gist of the present invention. In addition, various changes can be made to the present invention within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. Furthermore, components having the same effect described in the above embodiments can be mutually replaced.

Claims

1. An access control method performed by a user equipment, the method comprising: When the upper layer indicates a specific destination for data transmission to the lower layer, establishing a Packet Data Convergence Protocol (PDCP) entity and a Radio Link Control (RLC) entity of a radio bearer for the data transmission, wherein the lower layer is the Radio Resource Control (RRC) layer, and the PDCP entity and the RLC entity are configured according to a predefined configuration, wherein the predefined configuration includes: PDCP sequence number length; RLC sequence number length; and logical channel number.

2. A user equipment, comprising: a processor; and a memory storing instructions; wherein the processor runs the instructions to: When the upper layer indicates a specific destination for data transmission to the lower layer, establish a Packet Data Convergence Protocol (PDCP) entity and a Radio Link Control (RLC) entity of a radio bearer for the data transmission, wherein the lower layer is the Radio Resource Control (RRC) layer, and the PDCP entity and the RLC entity are configured according to a predefined configuration, wherein the predefined configuration includes: PDCP sequence number length; RLC sequence number length; and logical channel number.

Images