Wireless communication method, terminal device, and access network device

Abstract

Provided are a wireless communication method, a terminal device, and an access network device. The method comprises: a terminal device sends first capability information of the terminal device to an access network device by means of a first data radio bearer (DRB), the first DRB being established on the basis of mandatory capability information of the terminal device, or the first DRB being established on the basis of second capability information of the terminal device. In embodiments of the present application, the first DRB can be established on the basis of the mandatory capability information of the terminal device, or the first DRB can be established on the basis of the second capability information of the terminal device, so that the terminal device can subsequently transmit the capability information of the terminal device by means of the first DRB, thereby facilitating the transmission of the capability information of the terminal device by means of a user plane.

Description

Wireless communication methods, terminal equipment and access network equipment Technical Field

[0001] This application relates to the field of communication technology, and more specifically, to wireless communication methods, terminal devices, and access network devices. Background Technology

[0002] Currently, a scheme has been proposed to transmit terminal equipment capability information via the user plane to reduce the signaling radio bearer (SRB) overhead consumed in transmitting this information. However, the terminal equipment can only transmit capability information via the user plane after the data radio bearer (DRB) is established. In traditional air interface technologies, before the DRB is established, the terminal equipment needs to report its capability information (e.g., user equipment (UE) radio capabilities) so that the access network equipment can establish the DRB and allocate and schedule corresponding air interface resources based on this information. Therefore, the current scheme of transmitting terminal equipment capability information via the user plane cannot be implemented. Summary of the Invention

[0003] This application provides a wireless communication method, a terminal device, and an access network device. The various aspects covered by this application are described below.

[0004] In a first aspect, a wireless communication method is provided, comprising: a terminal device sending first capability information of the terminal device to an access network device via a first data radio bearer (DRB), wherein the first DRB is established based on mandatory capability information of the terminal device, or the first DRB is established based on second capability information of the terminal device.

[0005] In a second aspect, a wireless communication method is provided, comprising: an access network device receiving first capability information of a terminal device sent by a terminal device via a first DRB, wherein the first DRB is established based on mandatory capability information of the terminal device, or the first DRB is established based on second capability information of the terminal device.

[0006] Thirdly, a terminal device is provided, comprising: a transmitting unit, configured to transmit first capability information of the terminal device to an access network device via a first data radio bearer (DRB), wherein the first DRB is established based on mandatory capability information of the terminal device, or the first DRB is established based on second capability information of the terminal device.

[0007] Fourthly, an access network device is provided, comprising: a receiving unit, configured to receive first capability information of a terminal device sent by a terminal device via a first DRB, wherein the first DRB is established based on mandatory capability information of the terminal device, or the first DRB is established based on second capability information of the terminal device.

[0008] Fifthly, a terminal device is provided, including a processor, a memory, and a communication interface, wherein the memory is used to store one or more computer programs, and the processor is used to invoke the computer programs in the memory, causing the terminal device to perform some or all of the steps in the method of the first aspect.

[0009] In a sixth aspect, an access network device is provided, including a processor, a memory, and a transceiver, wherein the memory is used to store one or more computer programs, and the processor is used to invoke the computer programs in the memory to cause the access network device to perform some or all of the steps in the method of the second aspect.

[0010] Seventhly, embodiments of this application provide a communication system including the aforementioned terminal device and / or access network device. In another possible design, the system may further include other devices that interact with the terminal device or access network device as described in the embodiments of this application.

[0011] Eighthly, embodiments of this application provide a computer-readable storage medium storing a computer program that causes a communication device (e.g., a terminal device or an access network device) to perform some or all of the steps in the methods described above.

[0012] Ninthly, embodiments of this application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program operable to cause a communication device (e.g., a terminal device or an access network device) to perform some or all of the steps of the methods described in the foregoing aspects. In some implementations, the computer program product may be a software installation package.

[0013] In a tenth aspect, embodiments of this application provide a chip including a memory and a processor, the processor being able to call and run a computer program from the memory to implement some or all of the steps described in the methods of the foregoing aspects.

[0014] In this embodiment, a first DRB can be established based on the mandatory capability information of the terminal device or based on the second capability information of the terminal device, so that the terminal device can transmit the capability information of the terminal device through the first DRB, which helps to realize the transmission of the capability information of the terminal device through the user plane. Attached Figure Description

[0015] Figure 1 shows the wireless communication system 100 used in an embodiment of this application.

[0016] Figure 2 is a schematic diagram of the mapping relationship between the capabilities of terminal devices and the applications they support in 6G.

[0017] Figure 3 is a schematic flowchart of a method for reporting UE radio capability information applicable to an embodiment of this application.

[0018] Figure 4 is a schematic flowchart of a method for reporting UE radio capability information applicable to an embodiment of this application.

[0019] Figure 5 is a schematic flowchart of a wireless communication method according to an embodiment of this application.

[0020] Figure 6 is a schematic flowchart of a scheme for transmitting terminal device capability information in an embodiment of this application.

[0021] Figure 7 is a schematic flowchart of a scheme for transmitting terminal device capability information in another embodiment of this application.

[0022] Figure 8 is a schematic flowchart of a scheme for transmitting terminal device capability information in another embodiment of this application.

[0023] Figure 9 is a schematic diagram of the protocol stack applicable to the embodiments of this application.

[0024] Figure 10 is a schematic diagram of a protocol stack applicable to another embodiment of this application.

[0025] Figure 11 is a schematic diagram of a protocol stack applicable to another embodiment of this application.

[0026] Figure 12 is a schematic diagram of a protocol stack applicable to another embodiment of this application.

[0027] Figure 13 is a schematic diagram of a terminal device according to an embodiment of this application.

[0028] Figure 14 is a schematic diagram of an access network device according to an embodiment of this application.

[0029] Figure 15 is a schematic structural diagram of a communication device according to an embodiment of this application. Detailed Implementation

[0030] The technical solutions of this application will now be described with reference to the accompanying drawings. For ease of understanding, the following description will first introduce a schematic diagram of the communication system architecture of an embodiment of this application with reference to Figure 1. Figure 1 is a schematic diagram of a communication system architecture 100 applicable to an embodiment of this application. This network architecture may include terminal devices, access network (AN) nodes, and core network nodes.

[0031] It should be understood that the technical solutions of the embodiments of this application can be applied to various communication systems, such as: 5th generation (5G) systems or new radio (NR), long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, etc. The technical solutions provided in this application can also be applied to future communication systems, such as 6th generation mobile communication systems, satellite communication systems, and so on.

[0032] The terminal device in this application embodiment can also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal, remote station, remote terminal, mobile device, user terminal, terminal, wireless core network node, user agent, or user device. The terminal device in this application embodiment can be a device that provides voice and / or data connectivity to a user, and can be used to connect people, objects, and machines, such as a handheld device with wireless connectivity, vehicle-mounted device, etc. The terminal devices in the embodiments of this application can be mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, etc. Optionally, the terminal device can be used to act as a base station. For example, the terminal device can act as a dispatching entity, providing sidelink signals between terminal devices in vehicle-to-everything (V2X) or device-to-device (D2D) communications. For example, cellular phones and cars communicate with each other using sidelink signals. Cellular phones and smart home devices communicate without relaying communication signals through base stations.

[0033] Access network nodes can be access network devices. Access network devices are devices that terminals use to wirelessly access the network architecture. They are primarily responsible for air interface-side radio resource management, Quality of Service (QoS) management, data compression, and encryption. Access network devices can also be called radio access network (RAN) devices, such as base stations. A base station can broadly encompass, or be replaced by, various names including: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), master eNB (MeNB), secondary eNB (SeNB), multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, micro base station, relay node, donor node, or similar entities, or combinations thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. A base station can also be a mobile switching center, a device that performs base station functions in D2D, V2X, and machine-to-machine (M2M) communications, a network-side device in a 6G network, or a device that performs base station functions in future communication systems. A base station can support networks using the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the access network equipment.

[0034] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0035] In some deployments, the access network device in this application embodiment may refer to a CU or a DU, or the access network device may include both a CU and a DU. The gNB may also include an AAU.

[0036] Core network nodes can be categorized into several types, including User Plane Function (UPF) nodes, Access and Mobility Management Function (AMF) nodes, Session Management Function (SMF) nodes, Policy Control Function (PCF) nodes, Application Function (AF) nodes, Data Network (DN) nodes, Network Slice Selection Function (NSSF) nodes, Authentication Server Function (AUSF) nodes, Unified Data Management (UDM) nodes, Network Exposure Function (NEF) nodes, Network Repository Function (NRF) nodes, Network Slice-Specific Authentication and Authorization Function (NSSAAF) nodes, Edge Application Server Discovery Function (EASDF) nodes, and Network Slice Admission Control Function (NSACF) nodes. UPF nodes are primarily responsible for user data transmission. The other nodes, often referred to as Control Plane Function nodes, are mainly responsible for authentication, authorization, registration management, session management, mobility management, and policy control to ensure reliable and stable user data transmission.

[0037] UPF nodes can be used to forward and receive data from terminals. For example, a UPF node can receive service data from the data network and transmit it to the terminal through access network equipment; a UPF node can also receive user data from the terminal through access network equipment and forward it to the data network. The transmission resources allocated and scheduled by the UPF node for the terminal are managed and controlled by the SMF node. The bearer between the terminal and the UPF node can include: the user plane connection between the UPF node and the access network equipment, and the establishment of a channel between the access network equipment and the terminal. The user plane connection is a QoS flow that can be established between the UPF node and the access network equipment for transmitting data.

[0038] AMF nodes can be used to manage terminal access to the core network, such as terminal location updates, network registration, access control, terminal mobility management, and terminal attachment and detachment. While providing services for a terminal's session, the AMF node can also provide control plane storage resources for that session to store the session identifier and the SMF node identifier associated with the session identifier.

[0039] SMF nodes can be used to select user plane nodes for terminals, redirect user plane nodes for terminals, assign Internet Protocol (IP) addresses to terminals, establish bearers (also known as sessions) between terminals and UPF nodes, modify and release sessions, and perform QoS control.

[0040] PCF nodes are used to provide policies to AMF and SMF nodes, such as QoS policies and slice selection policies.

[0041] AF nodes are used to interact with 3GPP core network nodes to support the routing of application-impacted data, access network exposure functions, and interact with PCF nodes for policy control, etc.

[0042] A Data Network (DN) can provide data services to users for networks such as IP Multimedia Service (IMS) and the Internet. A DN can contain various application servers (AS) that provide different application services, such as carrier services, Internet access, or third-party services. The AS can implement the functions of an Application Server (AF).

[0043] NSSF is used for network slice selection and supports the following functions: selecting a set of network slice instance examples to serve the end device; determining allowed network slice selection assistance information (NSSAI), and, when necessary, determining the mapping to the subscribed single-network slice selection assistance information (S-NSSAI); determining the configured NSSAI, and, when necessary, determining the mapping to the subscribed S-NSSAI; determining the set of AMFs that may be used to query the end device, or determining a list of candidate AMFs based on the configuration.

[0044] AUSF is used to receive AMF requests for terminal authentication. It requests a key from UDM and then forwards the issued key to AMF for authentication processing.

[0045] UDM includes functions such as generating and storing user subscription information and managing authentication data, and supports interaction with external third-party servers.

[0046] NEF is used for capability exposure, meaning that based on NEF, network capabilities can be exported to external networks. Untrusted external applications can access core network data through NEF to ensure network security. NEF can provide functions such as QoS capability exposure for external applications, event subscription, and AF request distribution.

[0047] The NRF (Network Request Framework) is used for core network node registration, management, and status monitoring, thereby enabling automated management of core network nodes. When a core network node starts up, it must register with the NRF to provide services. Registration information may include, for example, the core network node's type, address, and service list.

[0048] EASDF is used to support edge computing. It is mainly responsible for dynamically resolving the domain name system (DNS) for multi-access edge computing (MEC) applications so that the session breakpoint of the user device can be connected to the application server closer to its physical location.

[0049] NSACF is the Network Slice Admission Control Function. Its main functions are to monitor and control the number of User Equipments (UEs) registered on each network slice, and to monitor and control the number of Protocol Data Unit (PDU) sessions established on each network slice. NSACF is also responsible for event-based network slice status notifications and reporting relevant information to user network functions (NFs).

[0050] In some communication systems (such as 5G systems), core network nodes can also be called network functions (NFs).

[0051] The nodes in Figure 1 can be network elements in hardware devices, software functions running on dedicated hardware, or virtualization functions implemented on a platform (e.g., a cloud platform). It should be noted that the network architecture shown in the above figures is merely an illustrative representation of the nodes included in the overall network architecture. In this application embodiment, the number of nodes included in the entire network architecture is not limited.

[0052] Those skilled in the art will understand that the network architecture shown in Figure 1 does not constitute a limitation on the network architecture. In specific implementations, the network architecture may include more or fewer nodes than shown, or combine certain nodes, etc. It should be understood that AN or RAN is represented in Figure 1 as (R)AN.

[0053] In some scenarios, network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenarios in which the network devices and terminal devices are located.

[0054] By way of example and not limitation, in the embodiments of this application, the network device may have mobility characteristics; for example, the network device may be a mobile device. In some embodiments of this application, the network device may be a satellite or a balloon station. For example, the satellite may be a low Earth orbit (LEO) satellite, a medium Earth orbit (MEO) satellite, a geostationary Earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. In some embodiments of this application, the network device may also be a base station located on land, water, or other similar locations.

[0055] In this embodiment, the network device can provide services to a cell. The terminal device communicates with the network device through the transmission resources (e.g., frequency domain resources, or spectrum resources) used by the cell. The cell can be the cell corresponding to the network device (e.g., a base station). The cell can belong to a macro base station or to a base station corresponding to a small cell. The small cell can include: metro cell, micro cell, pico cell, femto cell, etc. These small cells have the characteristics of small coverage area and low transmission power, and are suitable for providing high-speed data transmission services.

[0056] Terminal design based on big.LITTLE architecture

[0057] Currently, compared to traditional communication systems (e.g., 5G), future communication systems (e.g., 6G) place higher demands on key performance indicators such as peak data rate, latency, and reliability. These performance improvements mean increased peak power consumption for terminal devices. For example, to support higher peak data rates, terminal devices need to use more antennas to transmit over a larger bandwidth. Furthermore, to reduce latency, terminal devices need to support faster processing. Therefore, in a user-centric access network architecture, flexible cells composed of multiple TRPs can provide services to terminal devices. Besides considering energy-saving requirements from the network side, energy-saving design is also necessary on the terminal device side.

[0058] To maintain acceptable average power consumption for terminal devices, it's crucial to minimize power consumption during idle periods and periods of low traffic. To this end, a terminal design based on a small-core (LITTLE) architecture can be considered. In LITTLE mode, the terminal device can support fewer antennas, but the bandwidth is relatively smaller. In LITTLE mode, the terminal device can possess more powerful functions, such as supporting more antennas, greater bandwidth, and stronger processing capabilities. Thus, when the terminal device is idle or has low traffic demand, it can enter LITTLE mode. Conversely, the terminal device can switch to LITTLE mode on demand. For example, when the terminal device has high traffic demand, it can switch to LITTLE mode to meet the transmission requirements.

[0059] Furthermore, the big.LITTLE architecture allows for compatibility with different terminal types. For example, lightweight terminals may only support the little core mode. Conversely, standard and high-end terminal devices may support both little core and big core modes simultaneously.

[0060] To achieve the above design goals, the small core mode can support basic functions in the radio resource control (RRC) idle / RRC inactive states (such as paging reception, radio resource management (RRM) measurement, system message acquisition, initial cell access, etc.), and also support control plane functions in the RRC connected state and low-traffic data transmission. In other words, the small core mode supports the basic functions of low-capacity terminal devices and can operate independently. Conversely, the large core mode can support more efficient and faster data transmission; that is, the large core mode can implement more powerful functions to provide value-added services. For example, in the LP-WUS project being discussed in some protocols (3GPP R19NR), it is assumed that the terminal device implementation consists of two modules: a main radio (MR) and an ultra-low power receiver (LR). The main function of the LR is to listen at low power and receive LP-WUS signals from access network devices to wake up the MR to perform PDCCH listening. Regarding the terminal big.LITTLE design mentioned here, the small-core mode can be seen as a further enhancement of the LR function; that is, the small-core mode corresponds to the LR-based working mode, and the big-core mode corresponds to the MR-based working mode. Of course, the small-core mode can also be seen as part of the MR-based working mode. That is, the MR-based working mode can only include the big-core mode, or the MR-based working mode can include both big-core and small-core modes simultaneously.

[0061] Figure 2 illustrates the mapping relationship between the capabilities of terminal devices and the supported applications in 6G. Referring to Figure 2, for vertical industry applications (e.g., HRLLC) based on enhanced mobile broadband (eMBB) in 6G technology, the terminal device can support the 6G basic feature set corresponding to the basic service, as well as the relevant functions of low-end IoT devices, the 6G eMBB feature set, and the 6G vertical feature set (6G vertical feature set)1. For eMBB type services, the terminal device can support the 6G basic feature set corresponding to the basic service, as well as the relevant functions of low-end IoT devices, and the 6G eMBB feature set. For vertical industry applications based on the fundamental characteristics of 6G technology (e.g., sensing services), the terminal device can support the 6G basic feature set corresponding to the basic service, as well as the relevant functions of low-end IoT devices, and the 6G vertical industry application feature set 2. The 6G basic feature set corresponding to the basic service and the relevant functions of low-end IoT devices can be understood as the functions supported by the small-core mode mentioned above.

[0062] Based on the architecture shown in Figure 2, the 6G core network architecture has the following two characteristics: First, the 6G core network architecture can adapt to various RAN function combinations, from supporting minimal core systems (i.e., the small core operating mode introduced above) to supporting full-featured eMBB features. Second, it supports the functions required for new services (e.g., artificial intelligence (AI) & integrated sensing and communication (ISAC)), such as life cycle management (LCM).

[0063] In addition, for the architecture shown in Figure 2, the 6G radio access network supports the following two aspects: First, the support for basic general signals such as SSB, RACH, as well as low-end eMBB and low-end IoT is concentrated on the core bandwidth (BW), and the core BW supports independent operation; Second, additional air interface functions such as high-end eMBB feature sets and related vertical industry applications are added on demand, with minimal interdependence between them.

[0064] UE radio access capability reporting

[0065] In some implementations, UE capabilities (also known as terminal device capabilities) include UE access stratum capability (UE AS capability, also known as UE radio access capability) and UE non-access stratum capability (UE NAS capability). For UE non-access stratum capabilities, the terminal device can send NAS messages to the AMF, for example, by reporting UE non-access stratum capabilities when issuing an attach request to the core network.

[0066] Regarding UE access layer capabilities, when the network needs to obtain the radio access capabilities of a terminal device, it can trigger the connected UE to report its access layer capabilities through a UE Capability Enquiry. Typically, to ensure the security of UE access layer capability transmission, the network should only obtain UE access layer capability information when AS security is active. Referring to Figure 3, in step S310, the access network device can send a UE Capability Enquiry to the UE. In step S320, the UE can send UE Capability Information to the access network device, which can be carried in an RRC message.

[0067] In known communication systems (e.g., 5G NR), for accurate and efficient coordination and interoperability, access network devices need to obtain the radio capability information of the UE in order to make correct resource scheduling. For example, if the UE supports a certain feature and function, the access network device can configure it accordingly, while if the terminal device does not support a certain feature, the access network device cannot configure this function for it.

[0068] In some communication systems (e.g., 5G NR), UE capabilities rely on a hierarchical structure, where each capability parameter can be defined for each UE, each duplex mode, each frequency range, each band, and each band combination. That is, a UE can support different capabilities based on these parameters (see, for example, TS 38.306). For instance, Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP), and Radio Link Control (RLC) capability parameters can be defined for each UE, while other capability parameters, such as Media Access Control (MAC) and Physical (PHY) layer capabilities, may not always be defined based on the terminal device.

[0069] In some implementations, the UE's radio capability information includes information about the radio access technologies (RATs) supported by the UE (such as power level and frequency band). This can result in a very large amount of radio capability information. If the radio capability information is reported every time the UE transitions from CM-IDLE to CM-CONNECTED in the connection management (CM) state, the overhead of transmitting the radio capability information increases dramatically. Therefore, to reduce the overhead of transmitting radio capability information, the AMF stores the UE's radio capability information when the UE is in the CM-IDLE and RM-REGISTERED states. If this information is available, the AMF can send its latest UE radio capability information to the access network equipment in an N2 request message (i.e., an INITIAL CONTEXT SETUP REQUEST or a UE RADIO CAPABILITY CHECK REQUEST).

[0070] In some implementations, the AMF deletes the UE's radio capability information when the UE's registration management status changes to RM-DEREGISTERED. The AMF also deletes the UE's radio capability information when it receives a registration request with the registration type set to initial registration, or when it receives the first registration request with the registration type set to mobility registration update after the E-UTRA / EPC attach procedure.

[0071] In some implementations, the UE's radio capability information can be maintained in the core network, even during AMF reselection.

[0072] Because E-UTRA and NR add additional frequency bands and their combinations, they significantly increase the size of UE radio capabilities. Therefore, some communication protocols (such as 5G communication protocols) have proposed a method for efficiently transmitting UE radio capability information through the radio interface and other network interfaces: radio capability signaling optimization (RACS). In this scheme, a set of UE radio capabilities can be represented by assigning an identifier (e.g., UE radio capability ID). The UE radio capability ID can be assigned by the UE manufacturer or by the serving PLMN (Public Land Mobile Network). Manufacturer-assigned UE radio capability IDs can correspond to a set of pre-configured functions. For PLMN-assigned UE radio capability IDs, the assignment can be completed via NAS signaling. That is, within NG-RAN, from NG-RAN to E-UTRAN, from AMF to NG-RAN, and between RACS-supporting core network nodes, the UE radio capability ID is an alternative for transmitting UE radio capability information on the radio interface.

[0073] In existing technologies, the UE needs to report its radio capabilities to the access network equipment and the AMF (Access Module Manager). Furthermore, when the UE needs to update its radio capabilities, it must re-report to the access network equipment and AMF. And when the AMF cannot obtain the UE's radio capabilities from the RAN (Access Module), it also needs to trigger the UE to re-report its radio capabilities. Reporting UE radio capabilities consumes a significant amount of radio resources, and frequent UE radio capability update reports also increase the probability of congestion on the access network's SRB (Security Module Resource) resources. In addition, even when the UE is in a connected state, if it needs to update its radio capabilities, it must first enter an IDLE state and then perform periodic registration. Clearly, this disrupts service continuity. Moreover, with the advent of next-generation communication technologies and the use of new spectrum, the occupation of air interface signaling resources during UE radio capability reporting will be further exacerbated.

[0074] Even with RACS, the network side still needs to introduce new network element UE wireless capability management functions (UCMF) to allocate and manage UE wireless capability IDs. The UE, access network equipment, and core network equipment supporting RACS need to store the mapping relationship between UE wireless capability information and wireless capability IDs. Furthermore, access network equipment needs to simultaneously support different ID formats in 4G, 5G systems, and future communication systems, and be capable of transcoding between different ID formats. In addition, existing technologies simultaneously support wireless capability IDs allocated by the PLMN and those allocated by the UE manufacturer, further increasing the amount of data that the UE, access network equipment, and core network equipment supporting RACS need to store.

[0075] The mapping relationship between radio capability information and ID is not static, but dynamic. Different versions of ID have different mapping relationships. This means that all network entities that support RACS need a lot of signaling interaction to update the mapping relationship between UE radio capability information and radio capability ID.

[0076] When a UE needs to update its radio capability information but has not obtained the associated radio capability ID, it still needs to upload the entire radio capability information. It can be seen that even with RACS, air interface resource consumption cannot be completely avoided. Furthermore, the UE, access network equipment, AMF, and UCMF require additional signaling interactions to update and maintain the mapping relationship between radio capabilities and IDs, which also consumes more storage resources.

[0077] With the development of technology, in order to further reduce the SRB resources occupied by UE radio capability reporting, a NAS scheme for reporting UE radio capability information through the user plane is proposed. That is, after the UE's initial registration, the UE initiates a PDU session for UE radio capability reporting. The UE reports its radio capabilities through this PDU session and stores them in the core network element. Figure 4 illustrates an applicable method for reporting UE radio capability information according to an embodiment of this application. Assuming that when the UE performs initial access, its AS procedure is as shown in steps S410 to S460 of Figure 4.

[0078] In step S410, the UE sends an RRC setup request message to the access network device, which can be sent through SRB0.

[0079] In step S420, the access network device sends an RRC setup message to the UE, wherein the RRC setup message is used to establish SRB1.

[0080] In step S430, the UE sends an RRC setup complete message to the access network device via SRB1. This message contains the first NAS message (attach request / registration request) for the UE's initial access. From this step onwards, the UE begins NAS signaling interaction to complete the following steps: 1) UE ID acquisition, 2) authentication, and 3) NAS security establishment.

[0081] In step S440, the UE completes the initial AS security activation via SRB1.

[0082] In step S450, the UE reports its radio capabilities to the access network device via SRB1, as shown in Figure 3. Afterwards, the AMF can obtain and store the UE's radio capabilities from the access network device.

[0083] In step S460, the access network device sends an RRC reconfiguration message to the UE via SRB1 to establish SRB2 and DRB. The RRC reconfiguration message includes a NAS message: PDU session establishment accept.

[0084] As can be seen from the above introduction, in traditional air interface technologies, before the DRB is established, the terminal device needs to report its capability information (e.g., the UE radio capabilities mentioned earlier) so that the access network device can establish the DRB and allocate and schedule corresponding air interface resources based on the terminal device's capability information. However, as mentioned earlier, if it is desired to transmit the terminal device's capability information through the user plane, the terminal device can only transmit the capability information through the user plane data after the DRB is established. Therefore, the current solution of transmitting the terminal device's capability information through the user plane is not feasible.

[0085] To address the aforementioned problems, embodiments of this application provide a wireless communication method. In this method, a first DRB can be established based on the mandatory capability information of the terminal device, or based on the second capability information of the terminal device. This allows the terminal device to subsequently transmit its capability information through the first DRB, facilitating the transmission of terminal device capability information through the user plane. The wireless communication method of this application embodiment is described below with reference to FIG5. The method shown in FIG5 includes step S510.

[0086] In step S510, the terminal device sends its first capability information to the access network device through the first DRB.

[0087] In some implementations, the first capability information can indicate some or all of the UE's radio capabilities, as described above. Of course, the first capability information can also indicate the capabilities of new terminal devices introduced into the future communication system. In some scenarios, the capabilities of the terminal device and the capabilities of the UE can be used interchangeably; correspondingly, the capability information of the terminal device and the capability information of the UE can be used interchangeably.

[0088] In some implementations, the first DRB can also be called "DRBx", meaning that DRBx can be a DRB dedicated to transmitting first capability information. Of course, in the embodiments of this application, DRBx can also be used to transmit other information.

[0089] In some implementations, the first DRB is used to transmit first capability information through the user plane, or in other words, the first capability information can be transmitted to the first network element through the user plane.

[0090] In the embodiments of this application, the first network element is not limited. In some implementations, the first network element can be a network element in the core network, for example, the first network element can be an AMF or a UPF. Of course, the first network element can be any of the network elements described above. In other implementations, the first network element can also be a new network element introduced in the future communication system.

[0091] For example, if the first network element is a UPF, the terminal device will transmit the first capability information to the UPF through the access network device via the PDU session associated with the first DRB. Optionally, in addition to sending the first capability information, the terminal device may also send the identifier of the terminal device to which the first capability information belongs. The identifier of the terminal device may include, for example, a generic public subscription identifier (GPSI) and / or a subscription concealed identifier (SUCI).

[0092] For example, if the first network element is a DN, the terminal device transmits the first capability information to the UPF through the access network device via the PDU session associated with the first DRB. The UPF then transmits the first capability information to the DN via the N6 interface or a service interface. Optionally, in addition to sending the first capability information, the terminal device may also send the identifier of the terminal device to which the first capability information belongs. The identifier of the terminal device may include, for example, GPSI and / or SUCI.

[0093] As described above, the first DRB is established based on the mandatory capability information of the terminal device, or the first DRB is established based on the second capability information of the terminal device. Therefore, the following section will first introduce the above-mentioned scheme for establishing the first DRB in conjunction with Embodiment 1 and Embodiment 2.

[0094] Example 1: The first DRB is established based on the mandatory capability information of the terminal device.

[0095] In some implementations, the mandatory capability information of the terminal device is also called the mandatory capability information of the terminal device. It can be understood as the capability information that every terminal device supports, or in other words, the mandatory capability information of the terminal device is used to indicate the capabilities that every terminal device supports.

[0096] It should be understood that the mandatory capability information of a terminal device is capability information supported by every terminal device. Therefore, the terminal device does not need to report the mandatory capability information to the access network device, thereby reducing the overhead required for reporting the mandatory capability information. For example, the mandatory capability information of a terminal device can be predefined or preconfigured. Of course, in the embodiments of this application, the terminal device can report the mandatory capability information of the terminal device to the access network device.

[0097] In this embodiment of the application, the access network device can know the mandatory capability information of the terminal device in advance. Therefore, before the terminal device reports the first capability information, the access network device can establish a first DRB based on the mandatory capability information of the terminal device, which helps to realize the scheme of transmitting the first capability information in the user plane based on the first DRB.

[0098] In this application embodiment, the relationship between the aforementioned first capability information and mandatory capability information is not limited. In some implementations, the first capability information may not include the mandatory capability information of the terminal device to reduce the overhead of transmitting the first capability information. Of course, in this application embodiment, the first capability information may include the mandatory capability information of the terminal device, which helps to reduce the complexity of the access network device obtaining the mandatory capability information.

[0099] In this embodiment, the relationship between the aforementioned first capability information, mandatory capability information, and terminal device capability information (e.g., UE wireless capability information) is not limited. For example, the first capability information and the mandatory capability information may each include different capability information from the terminal device capability information. Alternatively, the first capability information and the mandatory capability information may constitute complete terminal device capability information. Yet another example is that the first capability information and the mandatory capability information may include partial information from the complete terminal device capability information.

[0100] Example 2: The first DRB is established based on the second capability information of the terminal device.

[0101] In some implementations, the second capability information includes capability information required for the establishment of the first DRB, or in other words, the second capability information indicates the terminal equipment capabilities required for the establishment of the first DRB. For example, the second capability information can be used to indicate the minimum set of capabilities required for the access network device to establish the first DRB, or in other words, the second capability information can be used to indicate the minimum set of capabilities required for the access network device to establish the first DRB and complete the corresponding resource allocation and scheduling, which helps to reduce the overhead of transmitting the second capability information.

[0102] In the embodiments of this application, the second capability information is not limited. In some implementations, the second capability information may be the small core capability information of the terminal device based on the big.LITTLE architecture (i.e., the capabilities supported by the terminal device in small core mode), and related descriptions can be found above.

[0103] In other implementations, it is assumed that the capability information includes capability information at the terminal device level (also known as "capability information per UE"), capability information at the duplex mode level (also known as "capability information per duplex mode"), capability information at the frequency range level (also known as "capability information per frequency range"), capability information at the bandwidth level (also known as "capability information per band"), and capability information at the band combination (bc) level (also known as "capability information per band combinations"). In this case, the second capability information may include one or more of the above-mentioned capability information. For example, the second capability information may only include capability information at the terminal device level, capability information at the duplex mode level, and capability information at the frequency range level (also known as "capability information at the bandwidth level per frequency range, but not capability information at the band combination level").

[0104] It should be noted that the aforementioned duplex modes may include, for example, frequency-division duplex (FDD) and / or time-division duplexing (TDD). The aforementioned frequency domain range may include, for example, FR1 and / or FR2. The aforementioned capability information at the granularity of frequency band combination can be understood as capability information for carrier aggregation (CA) and / or dual connectivity (DC).

[0105] In some other implementations, the second capability information may include only the capability information defined in the first version of 5G (e.g., Rel-15), and not the capability information defined in subsequent enhanced versions of 5G (e.g., Rel-16, Rel-17, Rel-18, etc.).

[0106] In some other implementations, the second capability information may only include the capability information defined in the first 6G version, and not the capability information defined in subsequent 6G enhanced versions.

[0107] In this embodiment, the relationship between the first capability information and the second capability information is not limited. In some implementations, the first capability information may not include the second capability information; that is, the capability indicated by the second capability information is any capability of the terminal device other than the capability indicated by the first capability information, in order to reduce the overhead of transmitting the first capability information. Of course, in this embodiment, the first capability information may include the second capability information. In this case, the access network device may directly send the first capability information and the second capability information to the first network element so that the first network element can obtain the first capability information and the second capability information.

[0108] In some implementations, if the first capability information does not include the second capability information, the access network device can send the second capability information to the first network element after the first DRB is established, so that the first network element can obtain both the first and second capability information. For example, the access network device can send the first capability information, the second capability information, and the identifier of the terminal device to the first network element.

[0109] In this embodiment, the communication method between the access network device and the first network element is not limited. For example, the access network device can send the aforementioned information to the first network element through a service-based interface (SBI) and a connection based on Hypertext Transfer Protocol (HTTP) or Quick UDP Internet Connections (QUIC). Alternatively, the access network device can send the aforementioned information to the first network element through a dedicated interface between the two.

[0110] It should be noted that if the first network element is not an AMF (Automatic Frame Controller), it can be understood that the first network element replaces the AMF in storing the terminal device's capability information (e.g., first capability information and / or second capability information). If the first network element is an AMF, it can be understood that the AMF still stores the terminal device's capability information (e.g., first capability information and / or second capability information).

[0111] In this embodiment, the relationship between the first capability information, the second capability information, and the terminal device capability information (e.g., UE wireless capabilities) is not limited. For example, the first capability information and the second capability information may each include different capability information from the terminal device capability information. Alternatively, the first capability information and the second capability information may constitute complete terminal device capability information. Yet another example is that the first capability information and the second capability information may include partial information from the complete terminal device capability information.

[0112] In some scenarios, the corresponding second capability information may differ for different terminal devices. Therefore, before establishing the first DRB, the terminal device can indicate the second capability information to the access network device. That is to say, the above method also includes: the terminal device sending the second capability information to the access network device.

[0113] In some implementations, the second capability information is transmitted via an SRB (e.g., SRB1). In this embodiment, the terminal device's capability information can be divided into first capability information and second capability information. In this case, the terminal device can send the second capability information to the access network device via an SRB, so that the access network device can establish a first DRB based on the second capability information, and then transmit the first capability information via the first DRB. Since the second capability information only contains a portion of the terminal device's capability information, compared to traditional solutions, transmitting the terminal device's capability information via an SRB helps avoid the problem of excessive signaling overhead caused by transmitting terminal device capability information via an SRB during initial access.

[0114] The mandatory capability information and the second capability information in the embodiments of this application have been introduced above with reference to Embodiments 1 and 2. The following describes the scheme for configuring the first DRB in the embodiments of this application. That is to say, the above method also includes: the access network device sending first configuration information to the terminal device, the first configuration information being used to configure the first DRB. The following describes the configuration method applicable to the embodiments of this application with reference to configuration method 1 and configuration method 2.

[0115] Configuration Method 1: The first configuration information is carried in an RRC Reconfiguration message. For example, the first configuration information is configured by adding or modifying the DRB's add or modify list "DRB-ToAddMod". This will be explained in conjunction with Figures 6 and 8 below.

[0116] In some implementations, the RRC reconfiguration message carries first indication information, which indicates acceptance of the PDU session associated with the first DRB. For example, the RRC reconfiguration message may carry a NAS message, which carries the first indication information, also known as a "PDU session establishment accept" message. Accordingly, if the terminal device receives the first indication information, it indicates that the PDU session associated with the first DRB has been successfully established.

[0117] In some implementations, the NAS message containing the PDU session establishment acceptance can include configurations related to QoS and the PDU session, and these configurations are associated with the first configuration information. For related information, please refer to the following text.

[0118] For example, the PDU session establishment accept message indicates acceptance of establishing an associated PDU session and further provides NAS layer parameters related to the PDU session, such as:

[0119] QoS rules, related uplink protocol descriptions, and related QoS parameters at the QoS flow level;

[0120] Session and service continuity mode (SCC) determines the continuity and recovery strategy of PDU sessions;

[0121] Single network slice selection assistance information (S-NSSAI) is used to identify network slices, allowing terminal devices or networks to select a suitable network slice to meet specific service requirements.

[0122] The data network name (DNN) is the name of the data network requested by the terminal device, used to identify the data service that the terminal device wants to access;

[0123] Allocated IPv4 address: This indicates the IPv4 address assigned to the terminal device for data transmission during a PDU session.

[0124] An interface identifier is used to distinguish different network interfaces, especially when multiple network interfaces or multiple PDU sessions are involved.

[0125] Session-Session Aggregate Maximum Bit Rate (AMBR) is used to define the aggregate maximum bit rate for uplink and downlink in a PDU session, ensuring that the data transmission rate of the session does not exceed this rate.

[0126] The selected PDU session type indicates the type of PDU session to be selected, which can be IPv4, IPv6, or IPv4v6. This determines the data transmission protocol of the PDU session.

[0127] In some implementations, the PDU session associated with the first DRB can be understood as a PDU session used to transmit first capability information.

[0128] In some implementations, the first configuration information is used to indicate one or more of the following: the identifier of the first DRB; the PDU session associated with the first DRB; the QoS flow associated with the first DRB; and the RLC bearer associated with the first DRB.

[0129] Taking the first configuration information used to indicate the identifier of the first DRB as an example, the identifier of the first DRB (also known as the DRB identifier (drb-Identity)) is used to represent the first DRB. In some implementations, the first DRB can be indicated by a fixed DRB identifier. For example, a certain DRB identifier can be specified in the protocol as belonging exclusively to the first DRB.

[0130] In this embodiment, the value of the DRB identifier is not limited. For example, the DRB identifier can be a reserved value in a known protocol. Or, for another example, the DRB identifier can be a newly introduced value in a future protocol.

[0131] Taking the first configuration information used to indicate the PDU session associated with the first DRB as an example, the first configuration information may carry the identifier of the PDU session (also known as the "PDU session ID"). In this embodiment, the PDU session transmitting the first capability information can be associated with the first DRB through the PDU session ID.

[0132] In some implementations, the information used to indicate the PDU session associated with the first DRB can be carried in the SDAP configuration (represented as sdap-Config) carried by the first configuration information.

[0133] Taking the first configuration information used to indicate the QoS flow associated with the first DRB as an example, the first configuration information may carry the identifier of the QoS flow (e.g., QFI). In the embodiments of this application, the QoS flow used to transmit the first capability information can be associated with the first DRB through the identifier of the QoS flow.

[0134] In some implementations, the information used to indicate the QoS flow associated with the first DRB can be adjusted by modifying the list of QoS flow maps to be added (mappedQoS-FlowsToAdd) to adjust the association between the QoS flow and the first DRB.

[0135] In this embodiment, the number of QoS flow identifiers carried in the first configuration information is not limited. For example, the first configuration information may carry one QFI to indicate a QoS flow used to transmit first capability information. Alternatively, the first configuration information may carry multiple QFIs to indicate multiple QoS flows used to transmit first capability information.

[0136] In some implementations, the information used to indicate the QoS flow associated with the first DRB can be carried in the SDAP configuration (referred to as sdap-Config) carried by the first configuration information.

[0137] Taking the first configuration information used to indicate the RLC bearer associated with the first DRB as an example, the first configuration information can carry the logical channel ID (LCID) of the RLC bearer. In some implementations, the RLC bearer can be indicated by a fixed LCID. For example, a specific LCID can be specified in the protocol to identify the RLC bearer associated with the first DRB.

[0138] In the embodiments of this application, the value of LCID is not limited. For example, LCID can be a reserved value in a known protocol. Or, for another example, LCID can be a newly introduced value in a future protocol.

[0139] In some implementation scenarios, the information used to indicate the RLC bearer associated with the first DRB can be carried in the RLC bearer configuration (RLC-BearerConfig) carried by the first configuration information.

[0140] In the embodiments of this application, the information indicated by the RLC bearer configuration is not limited. In some implementations, the RLC bearer configuration is also used to indicate one or more of the following: served radio bearer, RLC configuration (rlc-Config), and MAC-Logical Channel Configuration (mac-LogicalChannelConfig).

[0141] In some implementations, the serving radio bearer associates the RLC bearer with an SRB or DRB by indicating an SRB ID / DRB ID. For example, the serving radio bearer can associate the RLC bearer configuration information with a first DRB by indicating the DRB identifier of the first DRB.

[0142] In some implementations, the RLC configuration is used to indicate the RLC layer configuration information of the SRB / DRB, and to configure the relevant parameters for RLC-acknowledged mode (AM) and / or RLC-unacknowledged mode (UM). For the first DRB, the RLC configuration can be configured as RLC-AM and carry RLC-AM related parameters, such as the maximum retransmission threshold (denoted as maxRetxThreshold), polling bytes (denoted as pollByte), polling PDU (denoted as pollPDU), sequence number field length (denoted as sn-FieldLength), retransmission polling timer (denoted as t-PollRetransmit), reassembly timer (denoted as t-Reassembly), status report prohibition timer (denoted as t-StatusProhibit), etc.

[0143] In some implementations, MAC-logical channel configuration is used to configure the MAC layer logical channel (LCH), which mainly includes configuration parameters related to uplink logical channel priority, such as priority, priority bit rate (represented as prioritizedBitRate), token bucket period (represented as bucketSizeDuration), etc.

[0144] It should be noted that the embodiments of this application do not limit the information carried by the first configuration information. In addition to one or more types of information described above that can be indicated by the first configuration information, the first configuration information can also be used to indicate other information. In some implementations, the first configuration information can also carry PDCP configuration (represented as pdcp-config) to indicate the PDCP layer configuration information of the first DRB. For example, it may include a discard timer, a reordering timer, an uplink PDCP sequence number length (pdcp-SN-SizeUL), a downlink PDCP sequence number length (pdcp-SN-SizeDL), header compression, integrity protection, status report required, out-of-order delivery, ciphering disabled, etc.

[0145] Configuration method 2: The first configuration information is carried in the RRC setup message.

[0146] In some implementations, the RRC setup message carries SRB1 configuration information, which is used to establish SRB1. That is, when configuring SRB1 for the terminal device, the access network device also configures the first DRB for the terminal device. This will be explained below with reference to Figure 7.

[0147] In some implementations, the RRC setup message is transmitted via SRB0.

[0148] It should be noted that if the first configuration information is carried in the RRC establishment message, then when configuring the first DRB, the PDU session for the first DRB has not yet been established (i.e., there is no PDU session available for transmitting the first capability information), therefore the first DRB cannot be used yet. Based on this, the first configuration information in configuration method 2 may differ slightly from the first configuration information in configuration method 1.

[0149] In some implementations, the first configuration information is used to indicate one or more of the following: the identifier of the first DRB and / or the RLC bearer associated with the first DRB, as described above.

[0150] In other words, in some implementations, the first configuration information may not indicate the PDU session associated with the first DRB. Accordingly, the association between the first DRB and the PDU session is predefined, which can be understood, for example, as being predefined through a protocol. Of course, in the embodiments of this application, the PDU session associated with the first DRB can be indicated by the access network device after the PDU session is established.

[0151] It should be noted that, in the embodiments of this application, the indication of the PDU session associated with the first DRB by the access network device and the predefined method can be used alone or in combination. For example, the PDU session associated with the first DRB can be indicated by a predefined method. Subsequently, if the access network device re-indicates the PDU session associated with the first DRB, and the PDU session associated with the first DRB indicated by the access network device is different from the predefined PDU session associated with the first DRB, the terminal device can take the PDU session associated with the first DRB indicated by the access network device as the standard.

[0152] In some implementations, the first configuration information may not indicate the QoS flow associated with the first DRB. In this case, the association between the first DRB and the QoS flow (e.g., the QoS flow ID (QFI) corresponding to the PDU session) is predefined, where predefinition can be understood as being predefined by the protocol. Of course, in the embodiments of this application, the QoS flow associated with the first DRB can be indicated by the access network device after the PDU session is established.

[0153] It should be noted that, in the embodiments of this application, the indication of the QoS flow associated with the first DRB by the access network device and the predefined method can be used alone or in combination. For example, the QoS flow associated with the first DRB can be indicated by a predefined method. Subsequently, if the access network device re-indicates the QoS flow associated with the first DRB, and the QoS flow associated with the first DRB indicated by the access network device is different from the predefined QoS flow associated with the first DRB, the terminal device can take the QoS flow associated with the first DRB indicated by the access network device as the standard.

[0154] As mentioned above, in some scenarios, the QoS flow associated with the first DRB and / or the PDU session associated with the first DRB may be indicated by the access network device. That is, the above method further includes: the access network device sending a second configuration message to the terminal device, the second configuration message being used to configure the PDU session associated with the first DRB and / or the QoS flow associated with the first DRB.

[0155] In some implementations, the second configuration message is carried within an RRC reconfiguration message. In other implementations, the second configuration message may be located within the AS layer configuration information (e.g., SDAP configuration information) related to the PDU session carried in the RRC reconfiguration message.

[0156] In some implementations, the RRC reconfiguration message carries first indication information, which indicates acceptance of the PDU session associated with the first DRB. For example, the RRC reconfiguration message may carry a NAS message, which carries the first indication information, also known as a "PDU session establishment acceptance message". Accordingly, if the terminal device receives the first indication information, it indicates that the PDU session associated with the first DRB has been successfully established.

[0157] In some implementations, the PDU session associated with the first DRB can be understood as a PDU session used to transmit first capability information.

[0158] In some implementations, the above method further includes: in response to receiving the second configuration information, the terminal device determines that the first DRB is activated or in an available state.

[0159] In some scenarios, the first capability information is transmitted transparently to the first network element through the access network device. Therefore, the access network device may not be able to obtain the first capability information. Thus, the access network device can obtain the first capability information from the first network element. That is to say, the above method also includes: the first network element sending the first capability information to the access network device.

[0160] In some implementations, the access network device can directly obtain the first capability information from the first network element. For example, the first network element sends the first capability information and / or the identifier of the terminal device to the access network device through a direct connection interface. This direct connection interface may, for example, include an SBI interface. Accordingly, the first network element can communicate with the access network device through the SBI interface and via connections such as HTTP and QUIC. Of course, in the embodiments of this application, the direct connection interface may, for example, be a dedicated interface between the first network element and the access network device.

[0161] In other implementations, the access network device can obtain the first capability information from the first network element through the AMF. For example, the AMF can first obtain and store the first capability information from the first network element, and then the AMF can inform the access network device of the first capability information. It should be noted that if the first capability information of the terminal device is updated, the terminal device can instruct the AMF to obtain the updated capability information from the first network element. Alternatively, the AMF can subscribe to the terminal device's capability information from the first network element, so that if the terminal device's first capability information is updated, the first network element can proactively send the updated capability information to the AMF.

[0162] In other implementations, the access network device can obtain the first capability information from the first network element through the UPF. For example, after the first network element receives the first capability information, it can send the first capability information to the access network device through the UPF. The communication between the UPF and the access network device can be achieved through the N3 interface.

[0163] In some implementations, the above method further includes: the access network device sending a second RRC reconfiguration message to the terminal device, the second RRC reconfiguration message being used to configure SRB2 and / or other DRBs besides the first DRB.

[0164] In some implementations, SRB2 and / or other DRBs may be configured for the terminal device by the access network device based on the first capability information.

[0165] In some implementations, the second RRC reconfiguration message includes NAS signaling (such as PDU session establishment acceptance) for establishing PDU sessions for other DRBs.

[0166] In this embodiment of the application, after the terminal device establishes the first DRB and before other DRBs are established (e.g., before the terminal device receives the second RRC reconfiguration message), the terminal device may send first capability information to the access network device so that the access network device can establish other DRBs based on the first capability information.

[0167] In some implementations, if the access network device obtains the first capability information, it can reconfigure the first DRB based on that information. For example, the access network device can reconfigure header compression, PDCP duplication, and enable out-of-order delivery.

[0168] In this embodiment of the application, after the access network device obtains the first capability information, it can update the configuration of the first DRB according to the first capability information to configure some optional features that require the terminal device capability support, which is beneficial to improving the transmission efficiency of capability information.

[0169] In some implementations, the first DRB can be released if the terminal device has already sent the first capability information through the first DRB. For example, the release of the first DRB can be indicated by a second RRC reconfiguration message, wherein the second RRC reconfiguration message contains NAS signaling to indicate the release of the PDU session associated with the first DRB.

[0170] In this embodiment of the application, if the update cycle of the first capability information is relatively long, the first DRB can be released to improve resource utilization.

[0171] It should be noted that, in the embodiments of this application, the schemes of Embodiment 1 and Embodiment 2 can be used alone or in combination with the configuration process of the first DRB (including configuration method 1 and configuration method 2). For ease of understanding, the schemes for transmitting terminal device capability information in the embodiments of this application are described below with reference to Figures 6 to 8.

[0172] Figure 6 is a schematic flowchart of a scheme for transmitting terminal device capability information in an embodiment of this application. The scheme shown in Figure 6 is described using a combination of the mandatory capability information of the terminal device (i.e., the scheme described in Embodiment 1) and configuration method 1 as an example. Additionally, the first DRB is, for example, DRBx. The method shown in Figure 6 includes steps S610 to S670.

[0173] In step S610, the terminal device sends an RRC establishment request message to the access network device, wherein the RRC establishment request message can be sent through SRB0.

[0174] In step S620, the access network device sends an RRC establishment message to the terminal device, wherein the RRC establishment message is used to establish SRB1.

[0175] In step S630, the terminal device sends an RRC establishment completion message to the access network device via SRB1. This message contains the first NAS message (i.e., attach request / registration request) for the terminal device's initial access. From this step onwards, the terminal device begins NAS signaling interaction to complete the following steps: 1) obtaining the terminal device ID, 2) authentication, and 3) establishing NAS security.

[0176] In step S640, the terminal device completes the initial AS security activation via SRB1.

[0177] In step S650, the access network device sends an RRC reconfiguration message 1 to the terminal device. The RRC reconfiguration message 1 contains DRBx configuration information (as an example of the first configuration information) for DRBx establishment.

[0178] In some implementations, RRC reconfiguration message 1 carries a NAS message, which in turn carries a "PDU session establishment accept" message. Accordingly, if the terminal device receives the PDU session establishment accept message, it indicates that the PDU session associated with the first DRB has been successfully established.

[0179] In some implementations, the PDU session associated with the first DRB can be understood as a PDU session used to transmit first capability information.

[0180] In some implementations, the first configuration information is used to indicate one or more of the following: the identifier of the first DRB; the PDU session associated with the first DRB; the QoS flow associated with the first DRB; and the RLC bearer associated with the first DRB. See above for related information.

[0181] In some implementations, RRC reconfiguration message 1 includes a response message to the attach / register request, i.e., attach / register accepted.

[0182] In step S660, the terminal device sends first capability information to the first network element via the user through DRBx. Correspondingly, the access network device can obtain the first capability information from the first network element. The protocol stack used by the terminal device to send the first capability information to the first network element can be seen in Figures 9 to 12. Furthermore, the scheme for the access network device to obtain the first capability information from the first network element can be found above.

[0183] In step S670, the access network device sends an RRC reconfiguration message 2 to the terminal device via SRB1 to establish SRB2 and other DRBs besides DRBx. Reconfiguration message 2 can be used as an example of a second RRC reconfiguration message; see the above for a related description.

[0184] Figure 7 is a schematic flowchart of a scheme for transmitting terminal device capability information in another embodiment of this application. It is assumed that the scheme shown in Figure 7 combines the mandatory capability information of the terminal device (i.e., the scheme described in Embodiment 1) with configuration method 2 as an example. Furthermore, the first DRB is, for example, DRBx. The method shown in Figure 7 includes steps S710 to S770.

[0185] In step S710, the terminal device sends an RRC establishment request message to the access network device, wherein the RRC establishment request message can be sent through SRB0.

[0186] In step S720, the access network device sends an RRC establishment message to the terminal device. The RRC establishment message is used to establish SRB1, and the RRC establishment message carries DRBx configuration information (as an example of the first configuration information) for DRBx establishment.

[0187] In some implementations, the first configuration information is used to indicate the identifier of the first DRB and / or the RLC bearer associated with the first DRB. See above for further details.

[0188] It should be noted that a PDU session for transmitting the first capability information has not yet been established at this point, therefore DRBx cannot be used normally. Therefore, the first configuration information may not indicate the PDU session associated with the first DRB, nor the QoS flow associated with the first DRB.

[0189] Accordingly, the association between the first DRB and the PDU session is predefined, whereby predefinition can be understood, for example, as predefined through a protocol. Of course, in this embodiment, the PDU session associated with the first DRB can be indicated by the access network device after the PDU session is established (see step S750). Furthermore, the association between the first DRB and the QoS flow (e.g., the QFI corresponding to the PDU session) is predefined, whereby predefinition can be understood, for example, as predefined through a protocol. Of course, in this embodiment, the QoS flow associated with the first DRB can be indicated by the access network device after the PDU session is established (see step S750).

[0190] In step S730, the terminal device sends an RRC establishment completion message to the access network device via SRB1. This message contains the first NAS message (i.e., attach request / registration request) for the terminal device's initial access. From this step onwards, the terminal device begins NAS signaling interaction to complete the following steps: 1) obtaining the terminal device ID, 2) authentication, and 3) establishing NAS security.

[0191] In step S740, the terminal device completes the initial AS security activation via SRB1.

[0192] In step S750, the access network device sends an RRC reconfiguration message 1 to the terminal device. This RRC reconfiguration message 1 carries a NAS message, which in turn carries a "PDU session establishment accept" message. Accordingly, if the terminal device receives the PDU session establishment accept message, it indicates that the PDU session associated with the first DRB has been successfully established.

[0193] In some implementations, RRC reconfiguration message 1 is used to indicate the PDU session associated with the first DRB and the QoS flow associated with the first DRB. RRC reconfiguration message 1 serves as an example of second configuration information; further details can be found above.

[0194] In some implementations, if the terminal device receives RRC reconfiguration message 1, it can determine that the first DRB is activated or in an available state.

[0195] In step S760, the terminal device sends first capability information to the first network element via the user through DRBx. Correspondingly, the access network device can obtain the first capability information from the first network element. The protocol stack used by the terminal device to send the first capability information to the first network element can be seen in Figures 9 to 12. Furthermore, the scheme for the access network device to obtain the first capability information from the first network element can be found above.

[0196] In step S770, the access network device sends an RRC reconfiguration message 2 to the terminal device via SRB1 to establish SRB2 and other DRBs besides DRBx. Reconfiguration message 2 can be used as an example of a second RRC reconfiguration message; see the above for a related description.

[0197] Figure 8 is a schematic flowchart of a scheme for transmitting terminal device capability information in another embodiment of this application. It is assumed that the scheme shown in Figure 8 combines the second capability information of the terminal device (i.e., the scheme described in Embodiment 2) with configuration method 1 as an example. Furthermore, the first DRB is, for example, DRBx. The method shown in Figure 8 includes steps S810 to S880.

[0198] In step S810, the terminal device sends an RRC establishment request message to the access network device, wherein the RRC establishment request message can be sent through SRB0.

[0199] In step S820, the access network device sends an RRC establishment message to the terminal device, wherein the RRC establishment message is used to establish SRB1.

[0200] In step S830, the terminal device sends an RRC establishment completion message to the access network device via SRB1. This message contains the first NAS message (i.e., attach request / registration request) for the terminal device's initial access. From this step onwards, the terminal device begins NAS signaling interaction to complete the following steps: 1) obtaining the terminal device ID, 2) authentication, and 3) establishing NAS security.

[0201] In step S840, the terminal device completes the initial AS security activation via SRB1.

[0202] In step S850, the terminal device sends second capability information to the access network device through SRB1. The second capability information is used to establish DRBx. For a related introduction to the second capability information, please refer to the above text.

[0203] In some implementations, the access network device sends the second capability information to the AMF and / or the first network element. See the description of Embodiment 2 for further details.

[0204] In step S860, the access network device sends an RRC reconfiguration message 1 to the terminal device. The RRC reconfiguration message 1 contains DRBx configuration information (as an example of the first configuration information) for DRBx establishment.

[0205] In some implementations, RRC reconfiguration message 1 carries a NAS message, which in turn carries a "PDU session establishment accept" message. Accordingly, if the terminal device receives the PDU session establishment accept message, it indicates that the PDU session associated with the first DRB has been successfully established.

[0206] In some implementations, the PDU session associated with the first DRB can be understood as a PDU session used to transmit first capability information.

[0207] In some implementations, the first configuration information is used to indicate one or more of the following: the identifier of the first DRB; the PDU session associated with the first DRB; the QoS flow associated with the first DRB; and the RLC bearer associated with the first DRB. See above for related information.

[0208] In some implementations, RRC reconfiguration message 1 includes a response message to the attach / register request, i.e., attach / register accepted.

[0209] In step S870, the terminal device sends first capability information to the first network element via the user through DRBx. Correspondingly, the access network device can obtain the first capability information from the first network element. The protocol stack used by the terminal device to send the first capability information to the first network element can be seen in Figures 9 to 12. Furthermore, the scheme for the access network device to obtain the first capability information from the first network element can be found above.

[0210] In step S880, the access network device sends an RRC reconfiguration message 2 to the terminal device via SRB1 to establish SRB2 and other DRBs besides DRBx. Reconfiguration message 2 can be used as an example of a second RRC reconfiguration message; see the above for a related description.

[0211] The method flow of the embodiments of this application has been described above with reference to Figures 5 to 8. The protocol stack architecture applicable to the embodiments of this application is described below. As mentioned above, the terminal device can send first capability information to the first network element through the user based on the first DRB. The protocol stack applicable to the embodiments of this application is described below with reference to Figure 9. The protocol stacks of the terminal device, UPF, and the first network element, in descending order, include the End-to-End Protocol (E2E) layer, PDU layer, SDAP layer, PDCP layer, RLC layer, MAC layer, and PHY layer. Correspondingly, the protocol stack communicating with the UPF in the access network device, in descending order, includes the relay layer, the General Packet Radio Service Tunneling Protocol-User Plane (GTP / U) layer, the User Datagram Protocol (UDP) / Internet Protocol (IP) layer, the L2 layer, and the L1 layer. Furthermore, the protocol stack communicating with the terminal device in the access network device is deployed in the same way as the protocol stack in the terminal device.

[0212] It should be noted that the end-to-end protocol layer is a protocol layer introduced in this embodiment for communication between the terminal device and the first network element. This embodiment does not limit the name of this protocol layer. For example, it may be called the "first protocol layer," or it may be another similar protocol layer introduced in a future communication system.

[0213] Referring to Figure 9, a PDU layer can be configured in the terminal device, UPF, and the first network element to implement an end-to-end protocol (E2E protocol) between the terminal device and the first network element. In some implementations, this PDU layer can be based on IP protocol transmission (e.g., IPv4, IPv6, IPv4v6). In other implementations, this PDU layer can be transmitted via Ethernet. In still other implementations, this PDU layer can use unstructured PDU types for transmission. The following descriptions, in conjunction with Figures 10 to 12, will further illustrate this.

[0214] Referring to Figure 10, the PDU layer can be based on the IP protocol for transmission; therefore, the data packet includes an IP header. Correspondingly, the end-to-end protocol is similar to the APP layer protocol, and the terminal device can carry the first capability information through the payload of the end-to-end protocol layer. This end-to-end protocol can be carried by HTTP / 2 and TCP, or by HTTP / 3 and QUIC, or there may be a transport layer protocol similar to LCS-UPP between the end-to-end protocol layer and the IP layer.

[0215] As shown in Figure 11, the PDU layer can be based on the IP protocol for transmission; therefore, the data packet includes an IP header. Correspondingly, the end-to-end protocol is similar to NAS over IP, directly carried by the IP layer, and the terminal device can carry the initial capability information through the payload of the NAS layer.

[0216] Referring to Figure 12, the PDU layer can use unstructured PDU type (or non-IP protocol) transmission. In this case, the PDU layer data packets do not have actual headers, and the first capability information can be directly carried by SDAP via NAS and / or RRC. Specifically, the first capability information carried via RRC can be represented as msg{first capability information}. The first capability information carried via NAS can be represented as NAS msg{first capability information}. The first capability information carried via both NAS and RRC can be represented as RRC msg{NAS container[NAS msg(first capability information)]}.

[0217] The method embodiments of this application have been described in detail above with reference to Figures 1 to 12. The apparatus embodiments of this application will be described in detail below with reference to Figures 13 to 15. It should be understood that the descriptions of the method embodiments correspond to the descriptions of the apparatus embodiments; therefore, any parts not described in detail can be referred to the preceding method embodiments.

[0218] Figure 13 is a schematic diagram of a terminal device according to an embodiment of this application. The terminal device 1300 shown in Figure 13 includes: a transmitting unit 1310.

[0219] The transmitting unit 1310 is used to transmit the first capability information of the terminal device to the access network device through the first data radio bearer (DRB), wherein the first DRB is established based on the mandatory capability information of the terminal device, or the first DRB is established based on the second capability information of the terminal device.

[0220] In some implementations, the terminal device further includes: a first receiving unit, configured to receive first configuration information sent by the access network device, wherein the first configuration information is used to configure the first DRB.

[0221] In some implementations, the first configuration information is carried in a Radio Resource Control (RRC) reconfiguration message.

[0222] In some implementations, the RRC reconfiguration message carries first indication information, which is used to indicate acceptance of the Protocol Data Unit (PDU) session for establishing the first DRB association.

[0223] In some implementations, the first configuration information is used to indicate one or more of the following: the identifier of the first DRB; the PDU session associated with the first DRB; the Quality of Service (QoS) flow associated with the first DRB; and the Radio Link Layer Control (RLC) bearer associated with the first DRB.

[0224] In some implementations, the first configuration information is carried in an RRC establishment message, which carries signaling radio bearer SRB1 configuration information, and / or the RRC establishment message is transmitted through SRB0.

[0225] In some implementations, the association between the first DRB and the PDU session is predefined, and / or the association between the first DRB and the QoS flow is predefined.

[0226] In some implementations, the terminal device further includes: a second receiving unit, configured to receive a second configuration message sent by the access network device, the second configuration message being used to configure the PDU session associated with the first DRB and / or the QoS flow associated with the first DRB.

[0227] In some implementations, the second configuration message is carried as an RRC reconfiguration message.

[0228] In some implementations, the RRC reconfiguration message carries first indication information, which is used to indicate acceptance of the PDU session for establishing the first DRB association.

[0229] In some implementations, the terminal device further includes: a processing unit, configured to determine whether the first DRB is activated or in an available state in response to receiving the second configuration information.

[0230] In some implementations, the sending unit is further configured to send the second capability information to the access network device.

[0231] In some implementations, the second capability information is transmitted via SRB1.

[0232] In some implementations, the second capability information includes capability information required for the establishment of the first DRB.

[0233] In some implementations, the capability indicated by the second capability information is another capability of the terminal device besides the capability indicated by the first capability information; or the first capability information includes the second capability information.

[0234] In some implementations, the terminal device further includes: a third receiving unit, configured to receive a second RRC reconfiguration message sent by the access network device, the second RRC reconfiguration message being used to configure SRB2 and / or other DRBs besides the first DRB.

[0235] In some implementations, the first capability information is transmitted to the first network element via the user plane.

[0236] Figure 14 is a schematic diagram of an access network device according to an embodiment of this application. The access network device 1400 shown in Figure 14 includes: a receiving unit 1410.

[0237] The receiving unit 1410 is configured to receive first capability information of the terminal device sent by the terminal device through a first DRB, wherein the first DRB is established based on the mandatory capability information of the terminal device, or the first DRB is established based on the second capability information of the terminal device.

[0238] In some implementations, the access network device further includes: a first sending unit, configured to send first configuration information to the terminal device, wherein the first configuration information is used to configure the first DRB.

[0239] In some implementations, the first configuration information is carried in an RRC reconfiguration message.

[0240] In some implementations, the RRC reconfiguration message carries first indication information, which is used to indicate acceptance of the PDU session for establishing the first DRB association.

[0241] In some implementations, the first configuration information is used to indicate one or more of the following: the identifier of the first DRB; the PDU session associated with the first DRB; the QoS flow associated with the first DRB; and the RLC bearer associated with the first DRB.

[0242] In some implementations, the first configuration information is carried in an RRC establishment message, which carries SRB1 configuration information, and / or the RRC establishment message is transmitted through SRB0.

[0243] In some implementations, the association between the first DRB and the PDU session is predefined, and / or the association between the first DRB and the QoS flow is predefined.

[0244] In some implementations, the access network device further includes: a second sending unit, configured to send a second configuration message to the terminal device, the second configuration message being used to configure the PDU session associated with the first DRB and / or the QoS flow associated with the first DRB.

[0245] In some implementations, the second configuration message is carried as an RRC reconfiguration message.

[0246] In some implementations, the RRC reconfiguration message carries first indication information, which is used to indicate acceptance of the PDU session for establishing the first DRB association.

[0247] In some implementations, the receiving unit is further configured to receive the second capability information sent by the terminal device.

[0248] In some implementations, the second capability information is transmitted via SRB1.

[0249] In some implementations, the second capability information includes capability information required for the establishment of the first DRB.

[0250] In some implementations, the capability indicated by the second capability information is another capability of the terminal device besides the capability indicated by the first capability information; or the first capability information includes the second capability information.

[0251] In some implementations, the access network device further includes: a third sending unit, configured to send a second RRC reconfiguration message to the terminal device, the second RRC reconfiguration message being used to configure SRB2 and / or other DRBs besides the first DRB.

[0252] In some implementations, the first capability information is transmitted to the first network element via the user plane.

[0253] In some implementations, the receiving unit is further configured to receive the first capability information sent by the first network element.

[0254] In some implementations, the first network element is a network element in the core network.

[0255] In an optional embodiment, the transmitting unit 1310 may be a transceiver 1530. The terminal device 1300 may also include a processor 1510 and a memory 1520, as shown in FIG15.

[0256] In an optional embodiment, the transmitting unit 1410 may be a transceiver 1530. The access network device 1400 may also include a processor 1510 and a memory 1520, as shown in FIG15.

[0257] Figure 15 is a schematic structural diagram of a communication device according to an embodiment of this application. The dashed lines in Figure 15 indicate that the unit or module is optional. This device 1500 can be used to implement the methods described in the above method embodiments. Device 1500 can be a chip, a terminal device, or a network device.

[0258] Apparatus 1500 may include one or more processors 1510. The processor 1510 may support apparatus 1500 in implementing the methods described in the preceding method embodiments. The processor 1510 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be other 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 devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0259] The apparatus 1500 may further include one or more memories 1520. The memories 1520 store a program that can be executed by the processor 1510, causing the processor 1510 to perform the methods described in the preceding method embodiments. The memories 1520 may be independent of the processor 1510 or integrated into the processor 1510.

[0260] The device 1500 may also include a transceiver 1530. The processor 1510 can communicate with other devices or chips via the transceiver 1530. For example, the processor 1510 can send and receive data with other devices or chips via the transceiver 1530.

[0261] This application also provides a computer-readable storage medium for storing a program. This computer-readable storage medium can be applied to a terminal or network device provided in this application, and the program causes a computer to execute the methods performed by the terminal or network device in various embodiments of this application.

[0262] This application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to a terminal or network device provided in this application embodiment, and the program causes a computer to execute the methods performed by the terminal or network device in various embodiments of this application.

[0263] This application also provides a computer program. This computer program can be applied to the terminal or network device provided in this application, and the computer program causes the computer to execute the methods performed by the terminal or network device in various embodiments of this application.

[0264] It should be understood that the terms "system" and "network" in this application can be used interchangeably. Furthermore, the terminology used in this application is only for explaining specific embodiments of the application and is not intended to limit the application. The terms "first," "second," "third," and "fourth," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. In addition, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion.

[0265] In the embodiments of this application, the term "instruction" can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.

[0266] In the embodiments of this application, "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.

[0267] In the embodiments of this application, the term "correspondence" can indicate a direct or indirect correspondence between two things, or an association between two things, or a relationship such as instruction and being instructed, configuration and being configured.

[0268] In this application embodiment, "predefined" or "preconfigured" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices). This application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.

[0269] In this application embodiment, the "protocol" may refer to a standard protocol in the field of communication, such as the LTE protocol, the NR protocol, and related protocols applied to future communication systems. This application does not limit this.

[0270] In the embodiments of this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0271] In the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0272] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0273] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0274] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0275] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can read or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs, DVDs) or semiconductor media (e.g., solid-state disks, SSDs), etc.

[0276] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for wireless communication, characterized in that, include: The terminal device sends its first capability information to the access network device through a first data radio bearer (DRB). The first DRB is established based on the terminal device's mandatory capability information, or the first DRB is established based on the terminal device's second capability information.

2. The method as described in claim 1, characterized in that, The method further includes: The terminal device receives first configuration information sent by the access network device, the first configuration information being used to configure the first DRB.

3. The method as described in claim 2, characterized in that, The first configuration information is carried in the Radio Resource Control (RRC) reconfiguration message.

4. The method as described in claim 3, characterized in that, The RRC reconfiguration message carries first indication information, which is used to indicate acceptance of the Protocol Data Unit (PDU) session for establishing the first DRB association.

5. The method according to any one of claims 2-4, characterized in that, The first configuration information is used to indicate one or more of the following: The identifier of the first DRB; The PDU session associated with the first DRB; The QoS flow associated with the first DRB; The first DRB is associated with the Radio Link Layer Control (RLC) bearer.

6. The method as described in claim 2, characterized in that, The first configuration information is carried in an RRC establishment message, which is used to carry signaling radio bearer SRB1 configuration information, and / or The RRC establishment message is transmitted via SRB0.

7. The method as described in claim 6, characterized in that, The association between the first DRB and PDU session is predefined, and / or The association between the first DRB and the QoS flow is predefined.

8. The method as described in claim 6, characterized in that, The method further includes: The terminal device receives a second configuration message sent by the access network device. The second configuration message is used to configure the PDU session associated with the first DRB and / or the QoS flow associated with the first DRB.

9. The method as described in claim 8, characterized in that, The second configuration message is carried within the RRC reconfiguration message.

10. The method as described in claim 9, characterized in that, The RRC reconfiguration message carries first indication information, which is used to indicate acceptance of the PDU session for establishing the first DRB association.

11. The method according to any one of claims 8-10, characterized in that, The method further includes: In response to receiving the second configuration information, the terminal device determines that the first DRB is activated or in an available state.

12. The method according to any one of claims 1-10, characterized in that, The method further includes: The terminal device sends the second capability information to the access network device.

13. The method as described in claim 12, characterized in that, The second capability information is transmitted via SRB1.

14. The method according to any one of claims 1-13, characterized in that, The second capability information includes the capability information required for the establishment of the first DRB.

15. The method according to any one of claims 1-14, characterized in that, The capability indicated by the second capability information is any capability of the terminal device other than the capability indicated by the first capability information; or The first capability information includes the second capability information.

16. The method according to any one of claims 1-15, characterized in that, The method further includes: The terminal device receives a second RRC reconfiguration message sent by the access network device. The second RRC reconfiguration message is used to configure SRB2 and / or other DRBs besides the first DRB.

17. The method according to any one of claims 1-16, characterized in that, The first capability information is transmitted to the first network element via the user plane.

18. A method for wireless communication, characterized in that, include: The access network device receives first capability information of the terminal device sent by the terminal device through a first DRB, wherein the first DRB is established based on the mandatory capability information of the terminal device, or the first DRB is established based on the second capability information of the terminal device.

19. The method as described in claim 18, characterized in that, The method further includes: The access network device sends first configuration information to the terminal device, the first configuration information being used to configure the first DRB.

20. The method as described in claim 19, characterized in that, The first configuration information is carried in an RRC reconfiguration message.

21. The method as described in claim 20, characterized in that, The RRC reconfiguration message carries first indication information, which is used to indicate acceptance of the PDU session for establishing the first DRB association.

22. The method according to any one of claims 19-21, characterized in that, The first configuration information is used to indicate one or more of the following: The identifier of the first DRB; The PDU session associated with the first DRB; The QoS flow associated with the first DRB; The RLC bearer associated with the first DRB.

23. The method as described in claim 19, characterized in that, The first configuration information is carried in an RRC establishment message, which is used to carry SRB1 configuration information, and / or The RRC establishment message is transmitted via SRB0.

24. The method as described in claim 23, characterized in that, The association between the first DRB and PDU session is predefined, and / or The association between the first DRB and the QoS flow is predefined.

25. The method as described in claim 23, characterized in that, The method further includes: The access network device sends a second configuration message to the terminal device. The second configuration message is used to configure the PDU session associated with the first DRB and / or the QoS flow associated with the first DRB.

26. The method as described in claim 25, characterized in that, The second configuration message is carried within the RRC reconfiguration message.

27. The method as described in claim 26, characterized in that, The RRC reconfiguration message carries first indication information, which is used to indicate acceptance of the PDU session for establishing the first DRB association.

28. The method according to any one of claims 18-27, characterized in that, The method further includes: The access network device receives the second capability information sent by the terminal device.

29. The method as described in claim 28, characterized in that, The second capability information is transmitted via SRB1.

30. The method according to any one of claims 18-29, characterized in that, The second capability information includes the capability information required for the establishment of the first DRB.

31. The method according to any one of claims 18-30, characterized in that, The capability indicated by the second capability information is any capability of the terminal device other than the capability indicated by the first capability information; or The first capability information includes the second capability information.

32. The method according to any one of claims 18-31, characterized in that, The method further includes: The access network device sends a second RRC reconfiguration message to the terminal device. The second RRC reconfiguration message is used to configure SRB2 and / or other DRBs besides the first DRB.

33. The method according to any one of claims 18-32, characterized in that, The first capability information is transmitted to the first network element via the user plane.

34. The method as described in claim 33, characterized in that, The method further includes: The access network device receives the first capability information sent by the first network element.

35. The method as described in claim 33 or 34, characterized in that, The first network element is a network element in the core network.

36. A terminal device, characterized in that, include: The transmitting unit is configured to transmit first capability information of the terminal device to the access network device via a first data radio bearer (DRB), wherein the first DRB is established based on the mandatory capability information of the terminal device, or the first DRB is established based on the second capability information of the terminal device.

37. The terminal device as described in claim 36, characterized in that, The terminal device also includes: The first receiving unit is configured to receive first configuration information sent by the access network device, wherein the first configuration information is used to configure the first DRB.

38. The terminal device as described in claim 37, characterized in that, The first configuration information is carried in the Radio Resource Control (RRC) reconfiguration message.

39. The terminal device as described in claim 38, characterized in that, The RRC reconfiguration message carries first indication information, which is used to indicate acceptance of the Protocol Data Unit (PDU) session for establishing the first DRB association.

40. The terminal device as described in any one of claims 37-39, characterized in that, The first configuration information is used to indicate one or more of the following: The identifier of the first DRB; The PDU session associated with the first DRB; The QoS flow associated with the first DRB; The first DRB is associated with the Radio Link Layer Control (RLC) bearer.

41. The terminal device as described in claim 37, characterized in that, The first configuration information is carried in an RRC establishment message, which is used to carry signaling radio bearer SRB1 configuration information, and / or The RRC establishment message is transmitted via SRB0.

42. The terminal device as described in claim 41, characterized in that, The association between the first DRB and PDU session is predefined, and / or The association between the first DRB and the QoS flow is predefined.

43. The terminal device as described in claim 41, characterized in that, The terminal device also includes: The second receiving unit is configured to receive a second configuration message sent by the access network device. The second configuration message is used to configure the PDU session associated with the first DRB and / or the QoS flow associated with the first DRB.

44. The terminal device as described in claim 43, characterized in that, The second configuration message is carried within the RRC reconfiguration message.

45. The terminal device as described in claim 44, characterized in that, The RRC reconfiguration message carries first indication information, which is used to indicate acceptance of the PDU session for establishing the first DRB association.

46. ​​The terminal device as described in any one of claims 43-45, characterized in that, The terminal device also includes: In response to receiving the second configuration information, the processing unit is configured to determine whether the first DRB is activated or in an available state.

47. The terminal device as described in any one of claims 36-45, characterized in that, The sending unit is further configured to send the second capability information to the access network device.

48. The terminal device as described in claim 47, characterized in that, The second capability information is transmitted via SRB1.

49. The terminal device as described in any one of claims 36-48, characterized in that, The second capability information includes the capability information required for the establishment of the first DRB.

50. The terminal device as described in any one of claims 36-49, characterized in that, The capability indicated by the second capability information is any capability of the terminal device other than the capability indicated by the first capability information; or The first capability information includes the second capability information.

51. The terminal device as described in any one of claims 36-50, characterized in that, The terminal device also includes: The third receiving unit is configured to receive a second RRC reconfiguration message sent by the access network device. The second RRC reconfiguration message is used to configure SRB2 and / or other DRBs besides the first DRB.

52. The terminal device as described in any one of claims 36-51, characterized in that, The first capability information is transmitted to the first network element via the user plane.

53. An access network device, characterized in that, include: The receiving unit is configured to receive first capability information of the terminal device sent by the terminal device through a first DRB, wherein the first DRB is established based on the mandatory capability information of the terminal device, or the first DRB is established based on the second capability information of the terminal device.

54. The access network device as described in claim 53, characterized in that, The access network equipment also includes: The first sending unit is configured to send first configuration information to the terminal device, wherein the first configuration information is used to configure the first DRB.

55. The access network device as described in claim 54, characterized in that, The first configuration information is carried in an RRC reconfiguration message.

56. The access network device as described in claim 55, characterized in that, The RRC reconfiguration message carries first indication information, which is used to indicate acceptance of the PDU session for establishing the first DRB association.

57. The access network device as described in any one of claims 54-56, characterized in that, The first configuration information is used to indicate one or more of the following: The identifier of the first DRB; The PDU session associated with the first DRB; The QoS flow associated with the first DRB; The RLC bearer associated with the first DRB.

58. The access network device as described in claim 54, characterized in that, The first configuration information is carried in an RRC establishment message, which is used to carry SRB1 configuration information, and / or The RRC establishment message is transmitted via SRB0.

59. The access network device as described in claim 58, characterized in that, The association between the first DRB and PDU session is predefined, and / or The association between the first DRB and the QoS flow is predefined.

60. The access network device as described in claim 58, characterized in that, The access network equipment also includes: The second sending unit is used to send a second configuration message to the terminal device. The second configuration message is used to configure the PDU session associated with the first DRB and / or the QoS flow associated with the first DRB.

61. The access network device as described in claim 60, characterized in that, The second configuration message is carried within the RRC reconfiguration message.

62. The access network device as described in claim 61, characterized in that, The RRC reconfiguration message carries first indication information, which is used to indicate acceptance of the PDU session for establishing the first DRB association.

63. The access network device as described in any one of claims 53-62, characterized in that, The receiving unit is further configured to receive the second capability information sent by the terminal device.

64. The access network device as described in claim 63, characterized in that, The second capability information is transmitted via SRB1.

65. The access network device as described in any one of claims 53-64, characterized in that, The second capability information includes the capability information required for the establishment of the first DRB.

66. The access network device as described in any one of claims 53-65, characterized in that, The capability indicated by the second capability information is any capability of the terminal device other than the capability indicated by the first capability information; or The first capability information includes the second capability information.

67. The access network device as described in any one of claims 53-66, characterized in that, The access network equipment also includes: The third sending unit is used to send a second RRC reconfiguration message to the terminal device. The second RRC reconfiguration message is used to configure SRB2 and / or other DRBs besides the first DRB.

68. The access network device as described in any one of claims 53-67, characterized in that, The first capability information is transmitted to the first network element via the user plane.

69. The access network device as described in claim 68, characterized in that, The receiving unit is also used to receive the first capability information sent by the first network element.

70. The access network device as described in claim 68 or 69, characterized in that, The first network element is a network element in the core network.

71. A terminal device, characterized in that, The device includes a transceiver, a memory, and a processor. The memory stores a program, and the processor invokes the program in the memory and controls the transceiver to receive or send signals so that the terminal device performs the method as described in any one of claims 1-17.

72. A network device, characterized in that, The device includes a transceiver, a memory, and a processor. The memory stores a program, and the processor invokes the program in the memory and controls the transceiver to receive or transmit signals so that the network device performs the method as described in any one of claims 18-35.

73. An apparatus, characterized in that, Includes a processor for calling a program from memory to cause the device to perform the method as described in any one of claims 1-35.

74. A chip, characterized in that, Includes a processor for calling a program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 1-35.

75. A computer-readable storage medium, characterized in that, It contains a program that causes a computer to perform the method as described in any one of claims 1-35.

76. A computer program product, characterized in that, Includes a program that causes a computer to perform the method as described in any one of claims 1-35.

77. A computer program, characterized in that, The computer program causes the computer to perform the method as described in any one of claims 1-35.

Images