Information transmission method and apparatus, terminal, device, and core network function

Abstract

The present application relates to the technical field of communications, and discloses an information transmission method and apparatus, a terminal, a device, and a core network function. The information transmission method in embodiments of the present application comprises: a terminal acquires a first configuration, wherein the first configuration is used for configuring a dedicated bearer for information transmission, and the dedicated bearer is independent of an SRB and a DRB; and the terminal transmits information by means of the dedicated bearer.

Description

Information transmission method, device, terminal, equipment and core network function

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Chinese Patent Application No. 202311637697.9 filed in China on December 1, 2023, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present application belongs to the field of communication technology, and specifically relates to an information transmission method, apparatus, terminal, equipment and core network function. Background Art

[0004] In some related technologies, a terminal can only transmit data using a signaling radio bearer (SRB) or a data radio bearer (DRB), which results in poor transmission performance of the terminal. Summary of the Invention

[0005] The embodiments of the present application provide an information transmission method, apparatus, terminal, device, and core network function, which can solve the problem of poor transmission performance of the terminal.

[0006] In a first aspect, a method for transmitting information is provided, comprising:

[0007] The terminal obtains a first configuration, where the first configuration is used for a dedicated bearer for configuration information transmission, where the dedicated bearer is independent of the SRB and the DRB;

[0008] The terminal transmits information through the dedicated bearer.

[0009] In a second aspect, an information transmission method is provided, comprising:

[0010] The first radio access network device sends a first configuration to the terminal, where the first configuration is used for a dedicated bearer for configuration information transmission, where the dedicated bearer is independent of the SRB and the DRB;

[0011] The first radio access network device receives the information transmitted by the terminal through the dedicated bearer.

[0012] In a third aspect, an information transmission method is provided, comprising:

[0013] The core network function sends a trigger message for triggering information transmission to the wireless access network device;

[0014] The core network function receives information sent by the radio access network device or the control node;

[0015] The information is information transmitted by the terminal through a dedicated bearer; or, the information is information generated based on information transmitted by the terminal through a dedicated bearer; the dedicated bearer is a dedicated bearer for information transmission, and the dedicated bearer is independent of SRB and DRB.

[0016] In a fourth aspect, a capability information reporting method is provided, including:

[0017] The terminal reports capability information about the dedicated bearer;

[0018] The dedicated bearer is a dedicated bearer for information transmission, and the dedicated bearer is independent of SRB and DRB.

[0019] In a fifth aspect, a method for receiving capability information is provided, comprising:

[0020] The wireless access network device receives the dedicated bearer capability information of the terminal reported by the terminal;

[0021] The dedicated bearer is a dedicated bearer for information transmission, and the dedicated bearer is independent of SRB and DRB.

[0022] In a sixth aspect, an information transmission device is provided, comprising:

[0023] An acquisition module, configured to acquire a first configuration, where the first configuration is used to configure a dedicated bearer for information transmission, where the dedicated bearer is independent of a signaling radio bearer (SRB) and a data radio bearer (DRB);

[0024] The transmission module is configured to transmit information via the dedicated bearer.

[0025] In a seventh aspect, an information transmission device is provided, comprising:

[0026] A first sending module is configured to send a first configuration to a terminal, where the first configuration is used to configure a dedicated bearer for information transmission, where the dedicated bearer is independent of a signaling radio bearer (SRB) and a data radio bearer (DRB);

[0027] The first receiving module is configured to receive information transmitted by the terminal through the dedicated bearer.

[0028] In an eighth aspect, an information transmission device is provided, comprising:

[0029] A sending module, configured to send a trigger message for triggering information transmission to a wireless access network device;

[0030] A receiving module, configured to receive information sent by the wireless access network device or the control node;

[0031] The information is information transmitted by the terminal through a dedicated bearer; or, the information is information generated based on information transmitted by the terminal through a dedicated bearer; the dedicated bearer is a dedicated bearer for information transmission, and the dedicated bearer is independent of the signaling radio bearer SRB and the data radio bearer DRB.

[0032] In a ninth aspect, a capability information reporting device is provided, comprising:

[0033] A reporting module, configured to report capability information about dedicated bearers;

[0034] The dedicated bearer is a dedicated bearer for information transmission, and the dedicated bearer is independent of SRB and DRB.

[0035] In a tenth aspect, a capability information receiving device is provided, comprising:

[0036] a receiving module, configured to receive capability information of the terminal regarding a dedicated bearer reported by the terminal;

[0037] The dedicated bearer is a dedicated bearer for information transmission, and the dedicated bearer is independent of SRB and DRB.

[0038] In the eleventh aspect, a terminal is provided, which includes a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the terminal-side information transmission method provided in the embodiment of the present application are implemented, or when the program or instruction is executed by the processor, the steps of the capability information reporting method provided in the embodiment of the present application are implemented.

[0039] In the twelfth aspect, a terminal is provided, including a processor and a communication interface, wherein the communication interface is used to obtain a first configuration, the first configuration is used to configure a dedicated bearer for information transmission, and the dedicated bearer is independent of SRB and DRB; a transmission module is used to transmit information through the dedicated bearer.

[0040] In the twelfth aspect, a terminal is provided, including a processor and a communication interface, wherein the communication interface is used to report capability information about a dedicated bearer; wherein the dedicated bearer is a dedicated bearer for information transmission, and the dedicated bearer is independent of SRB and DRB.

[0041] In the thirteenth aspect, a wireless access network device is provided, which includes a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the information transmission method on the wireless access network device side provided in the embodiment of the present application are implemented, or when the program or instruction is executed by the processor, the steps of the capability information receiving method provided in the embodiment of the present application are implemented.

[0042] In the fourteenth aspect, a wireless access network device is provided, including a processor and a communication interface, wherein the communication interface is used to send a first configuration to a terminal, the first configuration is used to configure a dedicated bearer for information transmission, and the dedicated bearer is independent of SRB and DRB; a receiving module is used to receive information transmitted by the terminal through the dedicated bearer.

[0043] In the fourteenth aspect, a wireless access network device is provided, including a processor and a communication interface, wherein the communication interface is used to receive capability information of the terminal about a dedicated bearer reported by the terminal; wherein the dedicated bearer is a dedicated bearer for information transmission, and the dedicated bearer is independent of SRB and DRB.

[0044] In the fifteenth aspect, a core network function is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the information transmission method on the core network function side provided in the embodiment of the present application are implemented.

[0045] In the sixteenth aspect, a core network function is provided, including a processor and a communication interface, wherein the communication interface is used to send a trigger message for triggering information transmission to a wireless access network device; receive information sent by the wireless access network device or the control node; wherein the information is information transmitted by the terminal through a dedicated bearer; or, the information is information generated based on the information transmitted by the terminal through a dedicated bearer; the dedicated bearer is a dedicated bearer for information transmission, and the dedicated bearer is independent of the signaling radio bearer SRB and the data radio bearer DRB.

[0046] In the seventeenth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the information transmission method on the terminal side as provided in the embodiment of the present application are implemented, or the steps of the information transmission method on the wireless access network device side as provided in the embodiment of the present application are implemented, or the steps of the information transmission method on the core network function side as provided in the embodiment of the present application are implemented, or the steps of the capability information reporting method as provided in the embodiment of the present application are implemented, or the steps of the capability information receiving method as provided in the embodiment of the present application are implemented.

[0047] In the eighteenth aspect, a wireless communication system is provided, including: a terminal, a wireless access network device and a core network function, the terminal can be used to execute the steps of the information transmission method on the terminal side provided in the embodiment of the present application, the wireless access network device can be used to execute the steps of the information transmission method on the wireless access network device side provided in the embodiment of the present application, and the core network function can be used to execute the steps of the information transmission method on the core network function side provided in the embodiment of the present application.

[0048] In the nineteenth aspect, a wireless communication system is provided, including: a terminal and a wireless access network device, wherein the terminal can be used to execute the steps of the information transmission method on the terminal side provided in the embodiment of the present application, or the terminal can be used to execute the steps of the capability information reporting method provided in the embodiment of the present application, and the wireless access network device can be used to execute the steps of the information transmission method on the wireless access network device side provided in the embodiment of the present application, or the wireless access network device can be used to execute the steps of the capability information receiving method provided in the embodiment of the present application.

[0049] In the twentieth aspect, a chip is provided, which includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the information transmission method on the terminal side as provided in the embodiment of the present application, or to implement the information transmission method on the wireless access network device side as provided in the embodiment of the present application, or to implement the information transmission method on the core network function side as provided in the embodiment of the present application, or to implement the capability information reporting method on the core network function side as provided in the embodiment of the present application, or to implement the capability information receiving method as provided in the embodiment of the present application.

[0050] In aspect 21, a computer program / program product is provided, which is stored in a storage medium, and the program / program product is executed by at least one processor to implement the steps of the information transmission method on the terminal side as provided in the embodiment of the present application, or the program / program product is executed by at least one processor to implement the steps of the information transmission method on the wireless access network device side as provided in the embodiment of the present application, or the program / program product is executed by at least one processor to implement the steps of the information transmission method on the core network function side as provided in the embodiment of the present application, or the program / program product is executed by at least one processor to implement the steps of the capability information reporting method provided in the embodiment of the present application, or the program / program product is executed by at least one processor to implement the steps of the capability information receiving method provided in the embodiment of the present application.

[0051] In an embodiment of the present application, a terminal obtains a first configuration, which is used to configure a dedicated bearer for information transmission. The dedicated bearer is independent of SRBs and DRBs. The terminal transmits information via the dedicated bearer. This allows the terminal to transmit information via a dedicated bearer other than SRBs and DRBs, thereby improving the terminal's transmission performance. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] FIG1 is a block diagram of a wireless communication system to which embodiments of the present application may be applied;

[0053] FIG2 is a flow chart of an information transmission method provided in an embodiment of the present application;

[0054] FIG3 is a flow chart of a capability information reporting method provided in an embodiment of the present application;

[0055] FIG4 is a flowchart of another information transmission method provided in an embodiment of the present application;

[0056] FIG5 is a flowchart of a method for receiving capability information provided in an embodiment of the present application;

[0057] FIG6 is a flowchart of another information transmission method provided in an embodiment of the present application;

[0058] 7 to 9 are schematic diagrams of the protocol layer architecture provided in embodiments of the present application;

[0059] FIG10 is a structural diagram of an information transmission device provided in an embodiment of the present application;

[0060] 11 is a structural diagram of a capability information reporting device provided in an embodiment of the present application;

[0061] FIG12 is a structural diagram of another information transmission device provided in an embodiment of the present application;

[0062] FIG13 is a structural diagram of a capability information receiving device provided in an embodiment of the present application;

[0063] FIG14 is a structural diagram of another information transmission device provided in an embodiment of the present application;

[0064] FIG15 is a structural diagram of a communication device provided in an embodiment of the present application;

[0065] FIG16 is a structural diagram of a device provided in an embodiment of the present application;

[0066] FIG17 is a structural diagram of a wireless access network device provided in an embodiment of the present application;

[0067] Figure 18 is a structural diagram of another network-side device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0068] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0069] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0070] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.

[0071] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the technology described can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) systems. thGeneration, 6G) communication system.

[0072] FIG1 is a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device (Wearable Device), an aircraft (Flight Vehicle), a vehicle-mounted device (VUE), a ship-mounted device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), a game console, a personal computer (PC), an ATM, or a self-service machine, or other terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, vehicle-mounted controller, vehicle-mounted module, vehicle-mounted component, vehicle-mounted chip or vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application.

[0073] The network-side device 12 may include an access network device or a core network device, wherein the access network device may also be referred to as a radio access network (RAN) device, a radio access network function, or a radio access network unit. The access network device may include a base station, a wireless local area network (WLAN) access point (AP), or a wireless fidelity (WiFi) node. Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home evolved Node B (home evolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the relevant field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0074] The core network device may also be referred to as a core network function, a core network node or a core network function, etc., which may include but is not limited to at least one of the following: Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized Network Configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (L-NEF), Binding Support Function (Binding Support Function) Function, BSF), application function (Application Function, AF), etc. It should be noted that in the embodiment of the present application, only the core network device in the NR system is introduced as an example, and the specific type of the core network device is not limited.

[0075] Below, in combination with the accompanying drawings, an information transmission method, apparatus, terminal, device and core network function provided by the embodiments of the present application are described in detail through some embodiments and their application scenarios.

[0076] Please refer to FIG2 , which is a flowchart of an information transmission method provided in an embodiment of the present application. As shown in FIG2 , the method includes the following steps:

[0077] Step 201: The terminal obtains a first configuration, where the first configuration is used for a dedicated bearer for configuration information transmission, and the dedicated bearer is independent of SRB and DRB.

[0078] The acquiring of the first configuration may be that the terminal receives the first configuration sent by the network side device, or the terminal generates the first configuration, or the terminal receives the first configuration sent by other terminals.

[0079] The above information may be information to be sent by the terminal, for example, including but not limited to at least one of the following:

[0080] Perception data, artificial intelligence (AI) data, measurement results, configuration, link quality, transmission performance, algorithm control effects, control information, etc.

[0081] Among them, the above-mentioned AI data may include AI models, AI model parameters or AI model training data, etc.

[0082] In some implementations, the above information may be information that needs to be collected by the network-side device. For example, the network-side device may collect at least one of the following by configuring the above dedicated bearer:

[0083] Perception data, AI data, measurement results, configuration, link quality, transmission effect, algorithm control effect, etc.

[0084] In the embodiment of the present application, for the information collection scenario, the above-mentioned dedicated bearer can be called a collection radio bearer (CRB). The embodiment of the present application does not limit the name of the dedicated bearer.

[0085] It should be noted that the embodiments of the present application do not limit the above information to information that needs to be collected by the network side. For example, it can also be information actively sent by the terminal, or information sent by the network side to the terminal, or information to be sent in other situations. There is no limitation on this.

[0086] In the embodiment of the present application, the above information may also be data information.

[0087] The dedicated bearer for the above-mentioned information transmission can be understood as the dedicated bearer being a bearer dedicated to transmitting the above-mentioned information.

[0088] The above-mentioned dedicated bearer is independent of SRB and DRB, which can be understood as, the above-mentioned dedicated bearer is neither SRB nor DRB, and is a newly defined bearer in the embodiment of the present application.

[0089] Step 202: The terminal transmits information through the dedicated bearer.

[0090] The terminal transmitting the information through the dedicated bearer may be that the terminal sends the information to the network side through the dedicated bearer.

[0091] In an embodiment of the present application, it is possible to enable the terminal to transmit information through a dedicated bearer other than SRB and DRB, thereby improving the transmission performance of the terminal.

[0092] As an optional implementation manner, the dedicated bearer is used for at least one of the following:

[0093] Information interaction between the terminal and the wireless access network device;

[0094] Information interaction between the terminal and the core network function.

[0095] The above-mentioned dedicated bearer is used for information exchange between the terminal and the radio access network device, which can be understood as the terminal transmitting information to the radio access network through the above-mentioned dedicated bearer. For example, the end-to-end entity of the dedicated bearer is located at the radio access network and the terminal respectively. For example: in the data collection scenario, if the radio access network device triggers the data collection function by itself, or is triggered by other radio access network nodes, or is triggered by operations, administration, and maintenance (OAM), or is triggered by a core network (CN) node, the radio access network device establishes a dedicated bearer, which is used to transmit configuration and reporting data related to data collection between the radio access network device and the terminal. The end-to-end entity of the bearer is located at the radio access network device and the terminal respectively. The transmission between the radio access network device and other nodes is carried out using a dedicated data pipeline, which is a pipeline between nodes.

[0096] The aforementioned dedicated bearer is used for information exchange between the terminal and the core network function, which can be understood as the terminal transmitting information to the core network function via the aforementioned dedicated bearer, and the transmission of this information is transparent to the radio access network device. For example: if the radio access network device is triggered by a core network node to transmit terminal information transparently to the radio access network device, the radio access network device will establish a dedicated bearer. This bearer is used to transmit data collection-related configuration and reporting data for the core network function between the radio access network device and the terminal. The end-to-end entities of this bearer can be located at the core network function and the terminal respectively. Transmission between the radio access network device and other nodes is carried out using a dedicated data pipeline established for each terminal.

[0097] In the above implementation manner, the dedicated bearer can be used to enable information transmission between the terminal and the radio access network device or the core network function, so as to further improve the transmission performance of the terminal.

[0098] In some implementations, information interaction between the terminal and the radio access network function and information interaction between the terminal and the core network function may be transmitted using the same dedicated bearer or different dedicated bearers, and may be distinguished by a bearer identifier or data packet format.

[0099] As an optional implementation manner, the first configuration includes at least one of the following:

[0100] The identifier of the dedicated bearer, the attribute information of the dedicated bearer, the routing related information of the dedicated bearer, the processing information of the dedicated bearer during the switching process, and the mapping relationship of the dedicated bearer.

[0101] The identifier of the dedicated bearer is used to indicate the dedicated bearer, for example, the identifier is used to instruct the terminal to create or use the dedicated bearer.

[0102] The attribute information of the dedicated bearer is used to indicate at least one attribute of the dedicated bearer.

[0103] In some implementations, the attribute information of the dedicated bearer includes at least one of the following:

[0104] Attribute information of at least one protocol layer corresponding to the dedicated bearer, transmission configuration information of the dedicated bearer, security attribute information of the dedicated bearer, segmentation attribute information of the dedicated bearer, and bearer type of the dedicated bearer.

[0105] The at least one protocol layer corresponding to the dedicated bearer may be at least one protocol layer included in a protocol stack corresponding to the dedicated bearer.

[0106] The attribute information of the protocol layer may include configurations of the protocol layer, such as the Packet Data Convergence Protocol (PDCP) layer configuration, the Radio Link Control (RLC) layer configuration corresponding to the CRB, or the Medium Access Control (MAC) layer configuration. Each protocol layer can be flexibly configured using the attribute information.

[0107] The transmission configuration information of the dedicated bearer may include at least one of the following:

[0108] The transmission mode of the dedicated bearer, the maximum data length of the dedicated bearer, the reordering information of the dedicated bearer, the delivery method of the dedicated bearer, the logical channel identifier of the dedicated bearer, the logical channel priority of the dedicated bearer, and the guaranteed bit rate of the dedicated bearer.

[0109] The transmission mode of the dedicated bearer may include at least one of the following: RLC transmission mode and Dual Active Protocol Stack (DAPS) transmission mode.

[0110] The RLC transmission mode may include a transparent mode (TM), an acknowledged mode (AM) or an unacknowledged mode (UM).

[0111] The above-mentioned RLC transmission mode or DAPS transmission mode can enable the above-mentioned dedicated bearer to support more flexible transmission.

[0112] The maximum data length of the above dedicated bearer can be flexibly configured to support more flexible transmission.

[0113] The above-mentioned dedicated bearer reordering information may be reordering timing (T-reordering) information, or other reordering information, which is not limited to this. In this way, the dedicated bearer reordering can be flexibly configured to support more flexible transmission.

[0114] The delivery mode of the above-mentioned dedicated bearer can be delivered in sequence or not, so as to support more flexible transmission.

[0115] The above-mentioned logical channel identifier of the dedicated bearer, the logical channel priority of the dedicated bearer or the guaranteed bit rate of the dedicated bearer can realize flexible configuration of the logical channel identifier of the dedicated bearer, the logical channel priority of the dedicated bearer or the guaranteed bit rate of the dedicated bearer to support more flexible transmission.

[0116] The bearer type of the above-mentioned dedicated bearer may include: a split bearer. This bearer can perform optional path transmission between the Master Cell Group (MCG) and the Secondary Cell Group (SCG), or perform carrier aggregation (CA) duplication transmission (duplication) or dual connectivity (DC) duplication transmission to support more flexible transmission.

[0117] In some embodiments, the bearer type of the dedicated bearer may include a non-split bearer.

[0118] The security attribute information of the above-mentioned dedicated bearer can indicate whether the integrity protection function is enabled or whether encryption and decryption are enabled, so as to support more flexible transmission.

[0119] The segmentation attribute information of the dedicated bearer may be additional segmentation information of the dedicated bearer, such as sequence number (SN) length, maximum number of segments, segment indication field length, tail segment flag, etc., so as to support more flexible segment transmission.

[0120] The attribute information of the dedicated bearer may further include bearer format information, such as maximum packet size, length indicator field (Length Indicator) size, segment offset field (Segment Offset) size, etc.

[0121] The mapping relationship of the above dedicated bearer includes at least one of the following:

[0122] The mapping relationship between the dedicated bearer and the protocol entity;

[0123] The mapping relationship between the dedicated bearer and the data of the protocol entity.

[0124] The mapping relationship between the dedicated bearer and the protocol entity may include at least one of the following:

[0125] The mapping relationship between the dedicated bearer and the Service Data Adaptation Protocol for Uu interface (DSAP-Uu) entity;

[0126] The mapping relationship between dedicated bearers and Service Data Adaptation Protocol for Core Network (DSAP-CN) entities.

[0127] The mapping relationship between the dedicated bearer and the protocol entity data may include at least one of the following:

[0128] A mapping relationship between a dedicated bearer and at least one type of data in a DSAP-Uu entity;

[0129] A mapping relationship between a dedicated bearer and at least one type of data in a DSAP-CN entity.

[0130] In addition, the above data may be application data, and therefore, the mapping relationship between the above dedicated bearer and protocol entity data may include a mapping relationship between the dedicated bearer and application data of the protocol entity.

[0131] The data transmitted by the dedicated bearer can be flexibly configured through the above mapping relationship of the dedicated bearer, so as to further improve the transmission flexibility of the dedicated bearer.

[0132] The routing related information of the dedicated bearer may explicitly or implicitly indicate the routing of the dedicated bearer. For example, the routing related information of the dedicated bearer may include:

[0133] Routing information of the dedicated bearer; or

[0134] Data packet format information, where the data packet format information is used to determine routing information of the data packet of the dedicated bearer.

[0135] The routing information for the dedicated bearer can indicate the destination route of the information. For example, the information (e.g., data collection content) can be terminated at a radio access network device or at the core network protocol layer. For example, the routing attribute for dedicated bearer 1 is DSAP-Uu to the gNB, while the routing attribute for dedicated bearer 2 is DSAP-CN to the core network. The routing information for the dedicated bearer can also be a bearer identifier, which indicates the route of the dedicated bearer to different nodes.

[0136] The above-mentioned data packet format information is used to determine the routing information of the data packet of the dedicated bearer, which can be understood as follows: the above-mentioned data packet format information represents the routing information corresponding to different data packet formats, so that the specific information carried by the data packet can indicate the routing information of the data packet of the dedicated bearer, that is, the routing information is carried with the packet, such as a field in the data packet header (Packet header), 0 represents DSAP-Uu of the wireless access network, and 1 represents DSAP-CN of the core network.

[0137] The routing information or data packet format information of the dedicated bearer can be used to flexibly configure the routing of the dedicated bearer, thereby improving the flexibility of data transmission.

[0138] The processing information of the above-mentioned dedicated bearer during the switching process can indicate the processing method of the above-mentioned dedicated bearer during the cell switching process, such as whether service continuity is required during switching, whether the cache is cleared, whether the transmission state variable is reset, etc. The processing information of the dedicated bearer during the switching process can support flexible transmission of information through the above-mentioned dedicated bearer during the switching process.

[0139] It should be noted that, in some implementations, part of the above-mentioned dedicated bearer identifier, attribute information of the dedicated bearer, routing-related information of the dedicated bearer, processing information of the dedicated bearer during the switching process, and the mapping relationship of the dedicated bearer may also be protocol agreements to save the overhead of the first configuration.

[0140] As an optional implementation manner, the first configuration is carried in a configuration message, wherein:

[0141] The first configuration is carried in a first information field in the configuration message, where the first information field is an information field dedicated to the dedicated bearer configuration; or

[0142] The first configuration is carried in a second information field in the configuration message, and the second information field is a configuration information field for multiple bearers.

[0143] The configuration message may be a Radio Resource Control (RRC) configuration or reconfiguration message.

[0144] The information field dedicated to the dedicated bearer configuration can be understood as being used only for configuring the dedicated bearer and differs from the information fields for SRBs and DRBs. For example, in configuration messages, SRBs and DRBs each have their own fields for adding, modifying, and releasing (e.g., srb-ToAddModList, srb3-ToRelease, drb-ToAddModList, drb-ToReleaseList). These independent information fields are present in the configuration message. This independent information field makes dedicated bearer configuration more flexible.

[0145] The second information field, which is a configuration information field for multiple bearers, may be used for configuring the dedicated bearer and also for configuring at least one of an SRB or a DRB. For example, the second information field may be added to the bearer configuration field of the configuration message defined in the protocol, with some additional configuration fields for the dedicated bearer being added to the configuration of one of the bearer types, thereby reducing the complexity of the configuration message.

[0146] As an optional implementation manner, the dedicated bearer has at least one of the following characteristics:

[0147] The dedicated bearer can coexist with SRB and DRB;

[0148] The dedicated bearer can be transmitted in parallel with the SRB and DRB;

[0149] The dedicated bearer and SRB can exist at the same time;

[0150] The dedicated bearer and the SRB can be transmitted in parallel;

[0151] The dedicated bearer is established under target conditions;

[0152] The identifier of the dedicated bearer is arranged together with the identifier of the SRB, or the identifier of the dedicated bearer is arranged together with the identifier of the DRB, or the identifier of the dedicated bearer is arranged alone;

[0153] The attributes of the dedicated bearer are configurable;

[0154] The dedicated bearer corresponds to at least one Quality of Service (QoS);

[0155] The dedicated bearer supports cell switching.

[0156] The fact that the dedicated bearer, SRB, and DRB can coexist can be understood as the terminal being able to transmit these three bearers at the same time.

[0157] The fact that the dedicated bearer, SRB, and DRB can be transmitted in parallel can be understood as the terminal being able to perform parallel transmission of these three bearers.

[0158] The fact that the dedicated bearer and SRB can coexist can be understood as the terminal being able to transmit the two bearers at the same time.

[0159] The fact that the dedicated bearer and the SRB can be transmitted in parallel can be understood as the terminal being able to perform parallel transmission of these two bearers.

[0160] The above target conditions may be conditions agreed upon in the protocol or configured on the network side, such as establishing the above dedicated bearer after successful RRC connection establishment, secure activation of the Uu port, or obtaining terminal-related capabilities.

[0161] Arranging the identifier of the above-mentioned dedicated bearer together with the identifier of the SRB or DRB means that the above-mentioned dedicated bearer shares the identifier (ID) space with the SRB or DRB. For example, if the DRB ID space is extended to a maximum of 64, the DRB can share these 64 ID spaces with the dedicated bearer. Arranging the identifier of the above-mentioned dedicated bearer separately means that there is a separate ID space for the above-mentioned dedicated bearer, such as specifying an ID space of 1-32 specifically for the dedicated bearer. In this way, flexible configuration of the identifier of the dedicated bearer can be achieved to improve the flexibility of the dedicated bearer.

[0162] The configurable attributes of the dedicated bearer refer to that the attributes of the dedicated bearer can be dynamically or flexibly configured. Specifically, the attributes of the dedicated bearer are dynamically or flexibly configured by the first configuration or other configuration information to support more flexible transmission.

[0163] In some implementations, the attributes of the dedicated bearer include at least one of the following:

[0164] The transmission configuration of the dedicated bearer, the security attributes of the dedicated bearer, and the segmentation attributes of the dedicated bearer.

[0165] Among them, the above-mentioned transmission configuration, security attributes and segmentation attributes refer to the attribute information of the dedicated bearer configured through the above-mentioned first configuration, and are not described here in detail.

[0166] In this implementation, the attributes of the dedicated bearer can be made configurable to support more flexible transmission.

[0167] The above-mentioned dedicated bearer corresponds to at least one QoS, which means that the above-mentioned dedicated bearer can transmit data streams with one or more QoS attributes. For example, different QoS attributes of the dedicated bearer. On the same dedicated bearer, it is possible to multiplex multiple data collection data streams. If each stream has different QoS attributes, an additional layer can be used to explicitly carry and distinguish different data stream attributes.

[0168] The dedicated bearer supports cell switching, which may be configured flexibly such as clearing the cache and resetting the transmission variables, or retaining the cache and resetting the transmission variables, or retaining the cache and the transmission variables during the cell switching process.

[0169] Since the dedicated bearer has at least one of the above characteristics, the terminal has higher flexibility when transmitting information through the dedicated bearer, and can also meet transmission requirements such as continuity and transmission efficiency.

[0170] As an optional implementation manner, the dedicated bearer is used to transmit information of at least one of the following protocol entities:

[0171] DSAP-CN entity;

[0172] DSAP-Uu entity.

[0173] The DSAP-Uu entity is used to transmit information between the terminal and the wireless access network device, and the DSAP-CN entity is used to transmit information between the terminal and the core network function.

[0174] Through the above-mentioned DSAP-CN entity or DSAP-Uu entity, the terminal and the network side can flexibly transmit information.

[0175] As an optional implementation, the method further includes:

[0176] The terminal receives a second configuration sent by a network-side device, where the second configuration is used to reconfigure the dedicated bearer.

[0177] The above reconfiguration can be reconfiguring the above dedicated bearer in a cell switching scenario, or the serving cell may not be changed, and the network side equipment reconfigures the dedicated bearer for the terminal due to changes in demand or its own algorithm requirements.

[0178] In this implementation, since the second configuration is used to reconfigure the dedicated bearer, the dedicated bearer can meet more transmission requirements.

[0179] Optionally, when the configuration of the second configuration change does not affect layer 2, the state variables of the PDCP entity and the RLC entity corresponding to the dedicated bearer are maintained; or,

[0180] In the case where the configuration of the second configuration change has no explicit reset or no explicit re-establishment indication, the state variables of the Packet Data Convergence Protocol (PDCP) entity and the Radio Resource Control (RLC) entity corresponding to the dedicated bearer are maintained; or,

[0181] In a case where the configuration of the second configuration change affects Layer 2, the terminal re-establishes or resets at least one of the PDCP entity and the RLC entity corresponding to the dedicated bearer; or,

[0182] In a case where the configuration of the second configuration change carries an explicit reset or re-establishment indication, the terminal re-establishes or resets at least one of the PDCP entity and the RLC entity corresponding to the dedicated bearer.

[0183] The above-mentioned layer 2 includes protocol layers other than the PHY layer which is an L1 protocol stack, such as the MAC layer, the RLC layer, the PDCP layer, and the SDAP layer.

[0184] The above-mentioned not affecting layer 2 may mean that when the configuration of the above-mentioned dedicated bearer is changed, layer 2 is not affected. For example, when the PDCP layer or the RLC layer is processed, the PDCP layer and the RLC layer may not perform any operation.

[0185] Maintaining the state variables of the PDCP entity and the RLC entity means that no operation may be performed on the second configuration PDCP entity and the RLC entity, and the state variables are maintained, thereby achieving continuous transmission to improve transmission performance.

[0186] The above-mentioned reestablishment or resetting of at least one of the PDCP entity and the RLC entity can achieve more flexible processing of the PDCP entity and the RLC entity.

[0187] In some embodiments, for the PDCP entity, when the configuration of the second configuration change carries an explicit reset or re-establishment indication or affects Layer 2, re-establishment can be performed, and the RLC transmission mode can be distinguished, the AM state variables are maintained, the UM state variables are reset, and the service data unit (SDU) in the cache can continue to be retained so that it can be continuously received and sent according to the new security key after re-configuration, thereby ensuring business continuity to a certain extent.

[0188] In one embodiment,

[0189] While the terminal's serving cell remains unchanged, the base station reconfigures the dedicated bearer for the user equipment (UE) to modify certain configurations due to changes in demand or its own algorithm. If the configuration change does not affect Layer 2 processing, such as PDCP or RLC processing, the PDCP and RLC entities can remain silent, maintaining state variables. Data on the terminal's dedicated bearer continues to be received and transmitted, ensuring service continuity. However, if the configuration change impacts Layer 2 data processing, such as requiring a security key update, the PDCP or RLC entity may need to be reestablished or reset. In this case, the RLC layer, which caches unsent or unsuccessfully transmitted data, all contains old security keys and cannot be processed. Therefore, the RLC layer typically resets transmission variables and clears the cache. However, the PDCP layer can reestablish the data, distinguishing between different RLC transmission modes: AM state variables are maintained, while UM state variables are reset. The SDUs in the cache can be retained, allowing for continuous reception and transmission based on the new security keys after the reconfiguration, ensuring service continuity to a certain extent.

[0190] Optionally, in the case of cell handover, the second configuration is used to configure at least one of the following:

[0191] Resetting the RLC entity corresponding to the dedicated bearer of the terminal;

[0192] Handover processing of the PDCP entity corresponding to the dedicated bearer of the terminal, the handover processing including at least one of the following:

[0193] Clear the cache and reset the transfer variables;

[0194] Keep the cache and reset the transfer variables;

[0195] Preserve cache and transfer variables.

[0196] Resetting the RLC entity corresponding to the dedicated bearer of the terminal can achieve establishment of a new RLC entity for the dedicated bearer on the target side without transferring the RLC state between the source cell and the target cell to support cell switching.

[0197] The handover process of the PDCP entity can retain or clear the cache, and retain or reset the transmission variables, so as to achieve continuous data transmission during the cell handover process, thereby improving transmission performance.

[0198] In some implementations, it is also possible to configure whether the dedicated bearer data is deleted. If it is valid in the target cell, it is not deleted. If it is invalid in the target cell, it is deleted to further improve the transmission performance of the dedicated bearer.

[0199] In one embodiment,

[0200] For handover scenarios, the target cell generally gives a new configuration to the dedicated bearer, and the source cell sends it to the terminal in the handover command for the terminal to use after accessing the target cell. The target cell can configure RLC reset and PDCP reconstruction for the dedicated bearer, and optionally configure whether the dedicated bearer data is deleted. RLC reset is because the RLC status is generally not transmitted between the source cell and the target cell, and a new RLC entity is established on the target side for the dedicated bearer. For PDCP reconstruction, the state variables of the PDCP entity of UM are cleared, and the state variables of the PDCP entity of AM are maintained. The purpose of this is to better ensure business continuity in AM mode. The deletion option for dedicated bearer data is mainly to distinguish the validity of the data. For example, if the dedicated bearer data of the source cell is no longer valid in the target cell, it can be deleted. If it continues to be valid, it can be retained. The most typical data that needs to be retained is the data sent to the core network node, and its validity will not be affected by changes in the affiliated base station.

[0201] As an optional implementation, the method further includes:

[0202] The terminal reports capability information about the dedicated bearer.

[0203] The capability information of the dedicated bearer may be whether the terminal supports the dedicated bearer, or the specific capability of supporting the dedicated bearer.

[0204] In some embodiments, the capability information includes at least one of the following:

[0205] whether the terminal supports the dedicated bearer;

[0206] at least one capability of the dedicated bearer supported by the terminal;

[0207] whether the terminal supports information collection;

[0208] at least one function of information collection supported by the terminal;

[0209] the maximum number of the dedicated bearers supported by the terminal;

[0210] The capability range of at least one protocol layer corresponding to the dedicated bearer supported by the terminal.

[0211] At least one capability of the dedicated bearer supported above means that the dedicated bearer has multiple capabilities, and the specific capabilities supported by the terminal are indicated through the above capability information, such as supporting the interaction between the terminal and the wireless access network equipment, the interaction between the terminal and the core network function, or the ability to transmit multiple QoS data streams.

[0212] The above-mentioned information collection refers to whether the terminal supports information collection when the above-mentioned dedicated bearer is used for information collection, that is, transmits relevant information to the network side.

[0213] The at least one function of the information collection supported above may refer to the terminal supporting reporting of specific information in the information collection. For example, if the information collection involves multiple types of information, the terminal supports at least one of the multiple types of information.

[0214] The capability scope of the above-mentioned at least one protocol layer refers to the different capability scopes of different protocol layers, such as supporting the PDCP layer to provide at least one capability of header compression and decompression, security operation, separate bearer routing and replication, etc., supporting the RLC layer to provide at least one mode of the three modes of TM, UM, and AM, etc.

[0215] The capability information enables the network side to learn the corresponding capabilities of the terminal and configure a dedicated bearer that matches the terminal's capabilities, making the transmission of the dedicated bearer more reliable.

[0216] In an embodiment of the present application, a terminal obtains a first configuration, which is used to configure a dedicated bearer for information transmission. The dedicated bearer is independent of SRBs and DRBs. The terminal transmits information via the dedicated bearer. This allows the terminal to transmit information via a dedicated bearer other than SRBs and DRBs, thereby improving the terminal's transmission performance.

[0217] In the embodiment of the present application, a dedicated bearer is configured for the terminal to transmit signaling, data, and model information related to data collection, etc., and a bearer identifier or packet format is used to solve the routing problem to reach different nodes, and different switching processing is performed according to the bearer characteristics to meet continuity requirements and transmission efficiency.

[0218] Please refer to FIG3 , which is a flowchart of a capability information reporting method provided in an embodiment of the present application. As shown in FIG3 , the method includes the following steps:

[0219] Step 301: The terminal reports capability information about the dedicated bearer;

[0220] The dedicated bearer is a dedicated bearer for information transmission, and the dedicated bearer is independent of SRB and DRB.

[0221] Optionally, the capability information includes at least one of the following:

[0222] whether the terminal supports the dedicated bearer;

[0223] at least one capability of the dedicated bearer supported by the terminal;

[0224] whether the terminal supports information collection;

[0225] at least one function of information collection supported by the terminal;

[0226] the maximum number of the dedicated bearers supported by the terminal;

[0227] The capability range of at least one protocol layer corresponding to the dedicated bearer supported by the terminal.

[0228] In this embodiment, since the terminal reports the capability information about the dedicated bearer, it can be achieved that when the terminal supports the dedicated bearer, the terminal can transmit information through the dedicated bearer, thereby improving the flexibility of data transmission processing.

[0229] It should be noted that this embodiment is an implementation method of terminal capability reporting corresponding to the embodiment shown in Figure 2. Its specific implementation method can refer to the relevant description of the embodiment shown in Figure 2. In order to avoid repeated description, this embodiment will not be repeated.

[0230] Please refer to FIG4 , which is a flowchart of another information transmission method provided in an embodiment of the present application. As shown in FIG4 , the method includes the following steps:

[0231] Step 401: A first radio access network device sends a first configuration to a terminal, where the first configuration is used to configure a dedicated bearer for information transmission, where the dedicated bearer is independent of a signaling radio bearer (SRB) and a data radio bearer (DRB).

[0232] Step 402: The first radio access network device receives information transmitted by the terminal through the dedicated bearer.

[0233] Optionally, the dedicated bearer is used for at least one of the following:

[0234] Information interaction between the terminal and the second radio access network device;

[0235] Information interaction between the terminal and the core network function.

[0236] The first radio access network device and the second radio access network device may be the same or different.

[0237] Optionally, the first configuration includes at least one of the following:

[0238] The identifier of the dedicated bearer, the attribute information of the dedicated bearer, the routing related information of the dedicated bearer, the processing information of the dedicated bearer during the switching process, and the mapping relationship of the dedicated bearer.

[0239] Optionally, the attribute information of the dedicated bearer includes at least one of the following:

[0240] Attribute information of at least one protocol layer corresponding to the dedicated bearer, transmission configuration information of the dedicated bearer, security attribute information of the dedicated bearer, segmentation attribute information of the dedicated bearer, and bearer type of the dedicated bearer.

[0241] Optionally, the transmission configuration information of the dedicated bearer includes at least one of the following:

[0242] The transmission mode of the dedicated bearer, the maximum data length of the dedicated bearer, the reordering timing information of the dedicated bearer, the delivery method of the dedicated bearer, the logical channel identifier of the dedicated bearer, the logical channel priority of the dedicated bearer, and the guaranteed bit rate of the dedicated bearer.

[0243] Optionally, the bearer type of the dedicated bearer includes: a separate bearer; or

[0244] The transmission mode of the dedicated bearer includes at least one of the following: a radio link control RLC transmission mode and a dual active protocol stack DAPS transmission mode.

[0245] Optionally, the mapping relationship of the dedicated bearer includes at least one of the following:

[0246] The mapping relationship between the dedicated bearer and the protocol entity;

[0247] The mapping relationship between the dedicated bearer and the data of the protocol entity.

[0248] Optionally, the routing related information of the dedicated bearer includes:

[0249] Routing information of the dedicated bearer; or

[0250] Data packet format information, where the data packet format information is used to determine routing information of the data packet of the dedicated bearer.

[0251] Optionally, the first configuration is carried in a configuration message, wherein:

[0252] The first configuration is carried in a first information field in the configuration message, where the first information field is an information field dedicated to the dedicated bearer configuration; or

[0253] The first configuration is carried in a second information field in the configuration message, and the second information field is a configuration information field for multiple bearers.

[0254] Optionally, the dedicated bearer has at least one of the following characteristics:

[0255] The dedicated bearer can exist simultaneously with the signaling radio bearer SRB and the data radio bearer DRB;

[0256] The dedicated bearer can be transmitted in parallel with the SRB and DRB;

[0257] The dedicated bearer is established under target conditions;

[0258] The identifier of the dedicated bearer is arranged together with the identifier of the SRB, or the identifier of the dedicated bearer is arranged together with the identifier of the DRB, or the identifier of the dedicated bearer is arranged alone;

[0259] The attributes of the dedicated bearer are configurable;

[0260] The dedicated bearer corresponds to at least one quality of service QoS;

[0261] The dedicated bearer supports cell switching.

[0262] Optionally, the attributes of the dedicated bearer include at least one of the following:

[0263] The transmission configuration of the dedicated bearer, the security attributes of the dedicated bearer, and the segmentation attributes of the dedicated bearer.

[0264] Optionally, the dedicated bearer is used to transmit information of at least one of the following protocol entities:

[0265] Service Data Adaptation Protocol DSAP-Uu entity;

[0266] a Service Data Adaptation Protocol for Ng interface (DSAP-Ng) entity, the DSAP-Ng entity being used for interaction between the first radio access network device and a core network function;

[0267] A Service Data Adaptation Protocol for Xn interface (DSAP-Xn) entity is used for interaction between the first radio access network device and other radio access network devices.

[0268] Optionally, the method further includes:

[0269] The first radio access network device sends a second configuration to the terminal, where the second configuration is used to reconfigure the dedicated bearer.

[0270] Optionally, when the configuration of the second configuration change does not affect layer 2, the state variables of the Packet Data Convergence Protocol PDCP entity and the Radio Resource Control RLC entity corresponding to the dedicated bearer are maintained; or,

[0271] In the case where the configuration of the second configuration change has no explicit reset or no explicit re-establishment indication, the state variables of the Packet Data Convergence Protocol (PDCP) entity and the Radio Resource Control (RLC) entity corresponding to the dedicated bearer are maintained; or,

[0272] In a case where the configuration of the second configuration change affects layer 2, the first radio access network device reestablishes or resets at least one of the PDCP entity and the RLC entity corresponding to the dedicated bearer; or

[0273] In a case where the configuration of the second configuration change carries an explicit reset or re-establishment indication, the first radio access network device re-establishes or resets at least one of the PDCP entity and the RLC entity corresponding to the dedicated bearer.

[0274] Optionally, in the case of cell handover, the second configuration is used to configure at least one of the following:

[0275] Resetting the RLC entity corresponding to the dedicated bearer of the terminal;

[0276] Handover processing of the PDCP entity corresponding to the dedicated bearer of the terminal, the handover processing including at least one of the following:

[0277] Clear the cache and reset the transfer variables;

[0278] Keep the cache and reset the transfer variables;

[0279] Preserve cache and transfer variables.

[0280] Optionally, the method further includes:

[0281] The first radio access network device receives capability information of the terminal regarding the dedicated bearer reported by the terminal.

[0282] Optionally, the capability information includes at least one of the following:

[0283] whether the terminal supports the dedicated bearer;

[0284] at least one capability of the dedicated bearer supported by the terminal;

[0285] whether the terminal supports information collection;

[0286] at least one function of information collection supported by the terminal;

[0287] the maximum number of the dedicated bearers supported by the terminal;

[0288] The capability range of at least one protocol layer corresponding to the dedicated bearer supported by the terminal.

[0289] Optionally, the first radio access network device sending the first configuration to the terminal includes at least one of the following:

[0290] When the first radio access network device triggers information transmission, the first radio access network device sends a first configuration to the terminal;

[0291] When the first radio access network device receives a first trigger message for triggering information transmission sent by the core network, the radio access network device sends a first configuration to the terminal;

[0292] In a case where the first radio access network device receives a second trigger message for triggering information transmission sent by other radio access network devices, the first radio access network device sends a first configuration to the terminal.

[0293] The above triggering may be based on the needs of a radio access network device, a core network or other radio access network devices.

[0294] In this implementation, it is possible to support multiple ways of triggering the establishment of the above-mentioned dedicated bearer to meet more transmission requirements.

[0295] Optionally, when the radio access network device receives a first trigger message sent by a core network for triggering information transmission, the method further includes:

[0296] The first radio access network device transparently transmits the information to the core network; or,

[0297] The first radio access network device processes the information to the core network and sends the processed information to the core network.

[0298] The above processing can be to analyze, modify or integrate the information sent by the terminal to report to the core network information that is easier for the core network to identify and process, so as to improve the information transmission effect.

[0299] It should be noted that this embodiment is an implementation of the network side device corresponding to the embodiment shown in Figure 2. Its specific implementation can refer to the relevant description of the embodiment shown in Figure 2. In order to avoid repeated description, this embodiment will not be repeated.

[0300] Please refer to FIG5 , which is a flowchart of a method for receiving capability information provided in an embodiment of the present application. As shown in FIG5 , the method includes the following steps:

[0301] Step 501: A wireless access network device receives dedicated bearer capability information of a terminal reported by the terminal.

[0302] The dedicated bearer is a dedicated bearer for information transmission, and the dedicated bearer is independent of SRB and DRB.

[0303] Optionally, the capability information includes at least one of the following:

[0304] whether the terminal supports the dedicated bearer;

[0305] at least one capability of the dedicated bearer supported by the terminal;

[0306] whether the terminal supports information collection;

[0307] at least one function of information collection supported by the terminal;

[0308] the maximum number of the dedicated bearers supported by the terminal;

[0309] The capability range of at least one protocol layer corresponding to the dedicated bearer supported by the terminal.

[0310] It should be noted that this embodiment is an implementation of the wireless access network device corresponding to the embodiments shown in Figures 2 and 3. Its specific implementation can refer to the relevant descriptions of the embodiments shown in Figures 2 and 3. In order to avoid repeated descriptions, this embodiment will not be repeated.

[0311] Please refer to FIG6 , which is a flowchart of another information transmission method provided in an embodiment of the present application. As shown in FIG6 , the method includes the following steps:

[0312] Step 601: The core network function sends a trigger message for triggering information transmission to the wireless access network device.

[0313] Step 602: The core network function receives information sent by the radio access network device or control node;

[0314] The information is information transmitted by the terminal through a dedicated bearer; or, the information is information generated based on information transmitted by the terminal through a dedicated bearer; the dedicated bearer is a dedicated bearer for information transmission, and the dedicated bearer is independent of the signaling radio bearer SRB and the data radio bearer DRB.

[0315] The wireless access network device may be the first wireless access network device or the second wireless access network device in the above embodiment.

[0316] Optionally, the control node includes:

[0317] Control plane control node, or user plane control node.

[0318] Among them, the information sent by the core network function receiving control node may be transparent to the wireless access network device of the terminal through the above-mentioned dedicated bearer transmission information, such as the control plane (Control Plane, CP) method or the user plane (User Plane, UP) method per UE equivalent to the terminal as the granularity (per UE). The former is transmitted by the wireless access network device to the per UE signaling pipe of the core network control network element, and the latter is transmitted by the wireless access network device to the per UE data pipe of the core network user plane network element, and then transmitted to the corresponding server.

[0319] Optionally, the core network function receives the information sent by the control node through a Service Data Adaptation Protocol DSAP-Core Network CN entity; or,

[0320] The core network function receives information sent by the wireless access network device through the DSAP-Ng entity and processed by the wireless access network device.

[0321] It should be noted that this embodiment is an implementation method of the core network function corresponding to the embodiments shown in Figures 2 and 4. Its specific implementation method can refer to the relevant descriptions of the embodiments shown in Figures 2 and 4. In order to avoid repetition, this embodiment will not be repeated.

[0322] The following uses a data collection scenario and a dedicated bearer as a CRB to illustrate the method provided in the embodiment of the present application through multiple embodiments:

[0323] Example 1:

[0324] This example mainly describes the overall architecture of data collection. In this example, the basic architecture and solution descriptions for various possible scenarios of data collection are given to fully demonstrate the feasibility of this case. The following three scenarios can be included:

[0325] Case (1): The simplest data collection is triggered by the base station itself. For example, the base station needs to know the link quality of the Uu interface, transmission effect, or even the effect of algorithm control, transmission AI model / parameters, perception data, etc., and needs to configure data collection and report the results with the UE. This process is completed directly between the base station and the UE, and the protocol layer that handles these data collection configurations and results can be exemplified by a new layer DSAP-Uu.

[0326] As shown in Figure 7, (a) shows the DSAP-Uu air interface architecture using a possible 6G air interface protocol stack as an example, while (b) shows the DSAP-Uu air interface transmission architecture using a 5G air interface protocol stack as an example. The 6G protocol stack is merely an example, as 6G may involve protocol stack redesign, merging, or splitting. Of course, it is not ruled out that 6G will continue to use the L2 protocol consisting of the PDCP, RLC, and MAC sublayers similar to 5G.

[0327] The example architecture shown in Figure 7 effectively configures and reports data collection results between the gNB and UEs, terminating end-to-end at the base station, which is responsible for the data collection process. The base station can, of course, trigger data collection and configuration based on its own needs. More commonly, OAM triggers the base station to perform data collection. For example, OAM provides data collection requirements to the base station, which then selects appropriate UEs based on an algorithm, configures data collection for each selected UE, and receives reports of data collection results from each selected UE. Both configuration and reporting processes utilize the aforementioned one-to-one dedicated bearer protocol stack. After collecting data from all UEs, the base station can also summarize or even perform statistical analysis on the UE results, ultimately returning the statistical results to OAM.

[0328] Case (2): Another type of data collection is triggered directly by a dedicated node in the core network. For example, if the core network's data collection center needs to obtain some UE data, it can directly configure data collection with the UE and receive the results. This process is a direct end-to-end operation between the UE and the core network's data collection center. The base station participates in the transmission, but only transparently and cannot parse or modify the data. The protocol layer that handles these data collection configurations and results can be exemplified by a new layer, DSAP-CN.

[0329] As shown in Figure 8, both examples illustrate the protocol stack using the protocol-defined L2 layer, which includes the three sublayers PDCP / RLC / MAC, for ease of explanation. When 6G develops new L2 protocol stack names and divisions, the sublayers in Figure 8 can be directly replaced without affecting transmission or implementation. Subsequent protocol stack examples also use existing sublayers, which can be replaced by the new 6G protocol stack. (c) illustrates an architecture where the core network protocol stack is directly transmitted over the air interface, while (d) illustrates an architecture where the core network protocol stack is encapsulated by the corresponding air interface protocol stack before transmission. The advantage of (c) is its simplicity and directness. Core network data collection requirements have their own dedicated pipeline, facilitating the configuration and control of transmission parameters. While (d) adds an encapsulation mechanism, which increases the number of processing steps for core network data collection, its advantage is that it can be multiplexed with data collection packets for other purposes, facilitating centralized management and control, saving air interface overhead, and improving efficiency.

[0330] The example architecture shown in Figure 8 effectively configures data collection and reporting between the core network data collection node and the UE. The end-to-end data collection process terminates at the core network data collection node, with base stations assisting in transmission while ensuring full transparency, thereby better protecting data and user privacy. Transmission between the gNB and the core network data collection node can take various forms. For example, the gNB can first transmit data to the core network control node (e.g., the AMF node in a 5G system) via the CP, which then forwards the data to the corresponding data collection center. Alternatively, the gNB can first transmit data to the core network user plane control node (e.g., the UPF node in a 5G system) via the UP, which then forwards the data to the corresponding data collection center. Alternatively, data can be addressed to the corresponding data collection center via a bus within the core network.

[0331] Case (3): Another type of data collection is triggered by a dedicated core network node, other RAN nodes, or even non-3GPP nodes. For example, if the core network's data collection center needs to obtain certain data, it can request it from the base station. The base station selects an appropriate UE based on an algorithm and configures data collection and receives the results via the Uu interface. The base station then processes the UE's data results, generating processed data collection results and reporting them to the core network data collection center. This process is carried out hop by hop, from the core network data collection center, base station, and UE. The base station participates in this process, not just transparently transmitting data, but also parsing and modifying the requirements and results. The protocol layer between the core network data collection center and the base station that handles these data collection configurations and results can be exemplified by a new layer, DSAP-NG. Similarly, a dedicated protocol layer, such as DSAP-Xn, can also exist between base stations to handle data collection configurations and results. If the node is a third party or even one outside of 3GPP, the protocol layer is implementation-dependent.

[0332] As shown in Figure 9, the protocol stack example also uses the existing sublayer as an example. The same principle applies to the new 6G protocol stack. (e) involves data collection and interaction between a core network node and a base station, which then performs Uu interface data collection, configuration, and reporting. (f) involves data collection and interaction between other RAN nodes and a base station, which then performs Uu interface data collection, configuration, and reporting. Generally speaking, a core network data collection node or other RAN node can first submit a data collection request to the base station. The base station node converts the request into a separate data collection configuration for each selected UE and receives its report. The base station node then aggregates and processes the UE's reported data and feeds it back to the original requesting node.

[0333] The architecture example shown in Figure 9 effectively configures data collection and reports results. Each layer participates in processing and parsing requests and data. For example, a requesting node can request sensing data from a base station without specifying any specific UE. Upon receiving the request, the base station selects an appropriate UE, sends a sensing data collection request, collects UE data, and processes the data from all UEs, for example, masking UE identities and privacy information. The processed results are then reported to the requesting node. Transmission between the gNB and the core network data collection node can take various forms. For example, the gNB can first transmit data to a core network control node (e.g., an AMF node in a 5G system) via a CP-like mechanism, which then forwards the data to the corresponding data collection center. Alternatively, the gNB can first transmit data to a core network user plane control node (e.g., a UPF node in a 5G system), which then forwards the data to the corresponding data collection center. Alternatively, data can be addressed to the corresponding data collection center via a bus within the core network. Within RAN nodes, transmission is typically performed via an inter-node interface.

[0334] Example 2:

[0335] In this embodiment, the bearer management process related to data collection is described in detail.

[0336] Since the existing Uu interface only has two types of bearers, SRB and DRB, SRB has default special properties, such as the highest priority, guaranteed infinite bit rate, default encryption and integrity protection functions, and clearing of corresponding caches and transmission variables during switching. This makes it not conducive to large-scale data collection and processing, inefficient, and will disrupt the transmission of other normal data. DRB requires a complete core network control node, such as the exchange of data flow attributes between the AMF and the gNB, before it can be established. The DRB data flow requires a corresponding channel between the gNB and the core network user plane entity, such as the UPF, as well as a standardized data path conversion process during switching. Therefore, DRB is only suitable for the data collection process similar to UP transmission performed by the core network node through the UPF, and its adaptability is severely limited.

[0337] Therefore, it is necessary to design a new bearer type (i.e., dedicated bearer) to overcome the above shortcomings on the one hand, and on the other hand to be compatible with more future scenarios of data collection as much as possible to achieve a unified solution. The new bearer type needs to be named differently from SRB and DRB, such as CRB, etc. In short, a special name is required to distinguish them. This is not limited in the embodiments of the present application. For the convenience of description, CRB is used as an example for illustration.

[0338] New bearer types (e.g., CRBs) are used specifically for data collection-related control and information transmission. Their characteristics include at least one of the following:

[0339] The new bearer type can coexist and transmit in parallel with the traditional SRB and DRB. In a UE bearer, SRB and CRB can coexist / transmit, or SRB, DRB and CRB can coexist / transmit.

[0340] The establishment of CRB can be based on certain conditions, such as successful RRC connection establishment, Uu port security activation, or acquisition of UE related capabilities;

[0341] The bearer identifier of the CRB can be arranged together with the DRB / SRB, or arranged separately in a dedicated space. For example, the SRB ID = 0, 1, 2, 3, 4 in the protocol is arranged independently of the DRB. The RB ID of the DRB is 1-32. In the 6G era, for example, if the DRB ID space is expanded to a maximum of 64, the DRB can share the 64 ID space with the CRB, or a dedicated ID space of 1-32 can be specified for the CRB.

[0342] All CRB-related transmission attributes can be configured, such as the L2 SN length, Length Indicator (LI) length, Segment Offset (SO) length, in-sequence delivery, T-Reordering timer length, RLC AM / UM operation, logical channel priority, guaranteed bit rate, etc.

[0343] CRB-related security attributes can also be configured, such as whether to perform air interface encryption and air interface integrity protection.

[0344] CRB segmentation attributes, i.e., parameters, are currently limited to 9000 bytes for both SRB and DRB. However, data collection or model transmission may exceed this limit, so special segmentation operations need to be considered.

[0345] Different QoS attributes of CRBs. On the same CRB, it is possible to multiplex multiple data collection data flows. If each flow has different QoS attributes, an additional layer may be required to explicitly carry the attributes of different data flows.

[0346] The different processing of CRB during switching can be generally divided into three types. The first one clears the cache and resets the transmission variables, which does not guarantee any business continuity and re-performs the data collection process in the target cell. The second one retains the unsent or unconfirmed cache and resets the transmission variables. To a certain extent, the unfinished data collection process can be continued in the target cell. The third one retains the cache and the transmission variables, which realizes business continuity very well. There is no need to waste resources repeatedly in the target cell and continuous sorting is possible.

[0347] New bearer types (e.g., CRB) can be used as mandatory support features and capabilities for 6G UEs. However, unlike traditional SRBs and DRBs, CRBs are not mandatory requirements for UE communications. Data collection functions can be used as additional or auxiliary functions of UEs. Therefore, new bearer types such as CRBs can also be used as optional capabilities. Therefore, 6G UEs can report capabilities for CRBs, including at least one of the following:

[0348] Whether the UE supports the new bearer type CRB function, or which CRB capabilities it supports;

[0349] Whether the UE supports the corresponding data collection function, or which data collection functions it supports;

[0350] The maximum number of CRBs supported by the UE;

[0351] The CRBs supported by the UE and the range of optional capabilities configured at each layer;

[0352] If the new bearer type CRB is an optional 6G UE capability, the UE needs to report the relevant capabilities before the network can configure the appropriate CRB for the UE based on the capabilities and requirements to carry different data collection requirements. The network side configures the CRB for the UE, mainly including at least one of the following:

[0353] Use independent fields to add, modify, and release CRBs. Since SRBs and DRBs each have their own fields for adding, modifying, and releasing CRBs (e.g., srb-ToAddModList, srb3-ToRelease, drb-ToAddModList, drb-ToReleaseList), CRBs, as a bearer type distinct from SRBs and DRBs, require independent control operations using separate fields, such as crb-ToAddModList and crb-ToReleaseList. Alternatively, it is not excluded that additional configuration fields for CRBs be added to the existing bearer configuration fields, and the CRB configuration be merged into the configuration of one of the bearer types.

[0354] Configure the RB ID and corresponding layer attributes for the CRB, such as PDCP configuration, RLC layer configuration corresponding to the CRB, MAC layer configuration, etc. In addition to drawing on existing parameters, the configuration parameters also need to consider the characteristics of the CRB itself (such as the characteristics listed above), such as transport format, security option configuration, priority, guaranteed bit rate, etc.

[0355] CRB can be configured as a split bearer, with optional path transmission in MCG and SCG, or CA duplication and / or DC duplication transmission;

[0356] CRB can also be configured for DAPS transmission, providing the most flexible configuration;

[0357] In particular, you can also configure mapping relationships, that is, for each CRB, configure which data collection content is mapped to the CRB for transmission. For CRBs, since the data flow of CRBs is different from that of SRBs and DRBs, the traditional protocol provisions or the way of configuring QoS flows cannot be directly applied. Therefore, new mapping rules are defined. For example, one CRB corresponds to one DSAP-Uu or DSAP-CN entity, or one CRB corresponds to a certain application or type of data in a DSAP-Uu / DSAP-CN:

[0358] For example, a CRB bearer may correspond to a DSAP-Uu entity 1, which is used to transmit configuration or control information related to data collection. Therefore, the CRB may be configured in RLC AM mode because the control information requires high reliability. Another CRB bearer may correspond to another DSAP-Uu entity 2, which is used to transmit a large amount of data content related to data collection. Due to different data reliability requirements, different RLC transmission modes may be configured.

[0359] For another example, one CRB bearer may correspond to one DSAP-Uu entity 3, which is used for controlling and / or collecting sensing data, while another CRB bearer may correspond to another DSAP-Uu entity 4, which is used for controlling and / or delivering an AI model.

[0360] For another example, one CRB bearer may correspond to one DSAP-Uu entity 5, which is used for controlling and / or collecting sensing data between the UE and the base station, while another CRB bearer may correspond to another DSAP-CN entity 1, which is used for controlling and / or collecting sensing data between the UE and the core network node;

[0361] For another example, a DSAP-Uu entity 6 can correspond to three CRB bearers at the same time, wherein the control and / or collection of perception data between the UE and the base station in the DSAP-Uu entity 6 corresponds to CRB1, the control and / or collection of positioning data between the UE and the base station in the DSAP-Uu entity 6 corresponds to CRB2, and the control and / or collection of perception data between the UE and the core network function of the DSAP-CN entity 2 embedded in the DSAP-Uu entity 6 corresponds to CRB3;

[0362] When the CRB and DSAP-Uu or DSAP-CN entities are one-to-one, the mapping relationship only needs to associate the two;

[0363] When a CRB corresponds to one of the data types in a DSAP-Uu / DSAP-CN, the mapping relationship can configure the association between the CRB and a specific data type (e.g., control information / data, perception / positioning / AI, CN / base station, etc.), or the association between the CRB and a specific data attribute (e.g., attribute 1, attribute 2, attribute 3, etc.);

[0364] After the base station completes the CRB bearer configuration for the UE, the UE and the network can use CRB to transmit data collection related control and information. If a mapping relationship has been configured between one or more CRB bearers and a DSAP-Uu / DSAP-CN entity, the data carried by the CRB within this range can be naturally passed to the corresponding DSAP-Uu entity for processing, or transmitted to the corresponding DSAP-CN entity via the pipeline between the gNB and the core network node. However, if the data in a CRB bearer can have multiple different routes, it is also necessary to carry necessary distinguishing information or routing information in the data packet so that the corresponding data packet can find the correct processing entity, including at least one of the following:

[0365] When DSAP-Uu and DSAP-CN packets are multiplexed in a CRB bearer, they can be distinguished by data encapsulation. For example, DSAP-CN packets are carried in a DSAP-Uu packet as a container. Then, packets received from the CRB are first sent to the DSAP-Uu entity for processing. Based on the DSAP-Uu packet parsing method, if it is found to be a packet of the current layer, it will process it itself. If it is found to be a DSAP-CN container packet, it will be extracted and delivered to the corresponding DSAP-CN entity through the pipeline between the corresponding gNB and the core network function.

[0366] When multiple DSAP-CN data packets are multiplexed in one CRB bearer, it is necessary to distinguish the data packets of each DSAP-CN, for example, by carrying an explicit identifier in the data packet to distinguish the corresponding different DSAP-CN entities. Furthermore, this distinction processing can not only distinguish different DSAP-CN entities, but also further distinguish data types, etc. For example, for the same core network positioning service entity, its data can also be marked as data streams 1-3, respectively for positioning control information, positioning reporting information, positioning assistance information, etc.;

[0367] When DSAP-Uu packets and multiple DSAP-CN packets are multiplexed in a CRB bearer, in addition to encapsulating the DSAP-CN packets, additional destination entity distinction or data flow distinction is required, both of which can carry explicit tags;

[0368] After completing various configuration methods, the UE and the network can make good use of CRB bearers for data collection-related transmission and good routing, providing them with flexible configuration and management according to different data requirements, which not only ensures the transmission experience but also improves system efficiency.

[0369] The method provided in the embodiment of the present application enables the base station to perform bearer establishment and switching processing on demand, ensuring the transmission efficiency of UE data collection, thereby reducing the complexity of the UE and improving system efficiency while ensuring the data collection effect.

[0370] It should be noted that the embodiments of the present application can be applied to 5G or 6G, etc., and are not limited to Uu. They can be extended to other different versions without specific limitation.

[0371] The information transmission method provided in the embodiment of the present application can be executed by an information transmission device. In the embodiment of the present application, the information transmission device provided in the embodiment of the present application is described by taking the information transmission method executed by the information transmission device as an example.

[0372] The capability information reporting method provided in the embodiment of the present application can be performed by a capability information reporting device. In the embodiment of the present application, the capability information reporting device performing the capability information reporting method is taken as an example to illustrate the capability information reporting device provided in the embodiment of the present application.

[0373] The capability information receiving method provided in the embodiment of the present application can be executed by a capability information receiving device. In the embodiment of the present application, the capability information receiving device performing the capability information receiving method is taken as an example to illustrate the capability information receiving device provided in the embodiment of the present application.

[0374] Please refer to FIG. 10 , which is a structural diagram of an information transmission device provided in an embodiment of the present application. As shown in FIG. 10 , the information transmission device 1000 includes:

[0375] An acquisition module 1001 is configured to acquire a first configuration, where the first configuration is used to configure a dedicated bearer for information transmission, where the dedicated bearer is independent of a signaling radio bearer (SRB) and a data radio bearer (DRB);

[0376] The transmission module 1002 is configured to transmit information via the dedicated bearer.

[0377] Optionally, the dedicated bearer is used for at least one of the following:

[0378] Information interaction between the terminal and the wireless access network device;

[0379] Information interaction between the terminal and the core network function.

[0380] Optionally, the first configuration includes at least one of the following:

[0381] The identifier of the dedicated bearer, the attribute information of the dedicated bearer, the routing related information of the dedicated bearer, the processing information of the dedicated bearer during the switching process, and the mapping relationship of the dedicated bearer.

[0382] Optionally, the attribute information of the dedicated bearer includes at least one of the following:

[0383] Attribute information of at least one protocol layer corresponding to the dedicated bearer, transmission configuration information of the dedicated bearer, security attribute information of the dedicated bearer, segmentation attribute information of the dedicated bearer, and bearer type of the dedicated bearer.

[0384] Optionally, the transmission configuration information of the dedicated bearer includes at least one of the following:

[0385] The transmission mode of the dedicated bearer, the maximum data length of the dedicated bearer, the reordering information of the dedicated bearer, the delivery method of the dedicated bearer, the logical channel identifier of the dedicated bearer, the logical channel priority of the dedicated bearer, and the guaranteed bit rate of the dedicated bearer.

[0386] Optionally, the bearer type of the dedicated bearer includes: a separate bearer; or

[0387] The transmission mode of the dedicated bearer includes at least one of the following: a radio link control RLC transmission mode and a dual active protocol stack DAPS transmission mode.

[0388] Optionally, the mapping relationship of the dedicated bearer includes at least one of the following:

[0389] The mapping relationship between the dedicated bearer and the protocol entity;

[0390] The mapping relationship between the dedicated bearer and the data of the protocol entity.

[0391] Optionally, the routing related information of the dedicated bearer includes:

[0392] Routing information of the dedicated bearer; or

[0393] Data packet format information, where the data packet format information is used to determine routing information of the data packet of the dedicated bearer.

[0394] Optionally, the first configuration is carried in a configuration message, wherein:

[0395] The first configuration is carried in a first information field in the configuration message, where the first information field is an information field dedicated to the dedicated bearer configuration; or

[0396] The first configuration is carried in a second information field in the configuration message, and the second information field is a configuration information field for multiple bearers.

[0397] Optionally, the dedicated bearer has at least one of the following characteristics:

[0398] The dedicated bearer can coexist with SRB and DRB;

[0399] The dedicated bearer can be transmitted in parallel with the SRB and DRB;

[0400] The dedicated bearer and SRB can exist at the same time;

[0401] The dedicated bearer and the SRB can be transmitted in parallel;

[0402] The dedicated bearer is established under target conditions;

[0403] The identifier of the dedicated bearer is arranged together with the identifier of the SRB, or the identifier of the dedicated bearer is arranged together with the identifier of the DRB, or the identifier of the dedicated bearer is arranged alone;

[0404] The attributes of the dedicated bearer are configurable;

[0405] The dedicated bearer corresponds to at least one quality of service QoS;

[0406] The dedicated bearer supports cell switching.

[0407] Optionally, the attributes of the dedicated bearer include at least one of the following:

[0408] The transmission configuration of the dedicated bearer, the security attributes of the dedicated bearer, and the segmentation attributes of the dedicated bearer.

[0409] Optionally, the dedicated bearer is used to transmit information of at least one of the following protocol entities:

[0410] Service Data Adaptation Protocol DSAP-Core Network CN entity;

[0411] DSAP-Uu entity.

[0412] Optionally, the device further comprises:

[0413] The receiving module is used to receive a second configuration sent by a network side device, where the second configuration is used to reconfigure the dedicated bearer.

[0414] Optionally, when the configuration of the second configuration change does not affect layer 2, the state variables of the Packet Data Convergence Protocol PDCP entity and the Radio Resource Control RLC entity corresponding to the dedicated bearer are maintained; or,

[0415] In the case where the configuration of the second configuration change has no explicit reset or no explicit re-establishment indication, the state variables of the Packet Data Convergence Protocol (PDCP) entity and the Radio Resource Control (RLC) entity corresponding to the dedicated bearer are maintained; or,

[0416] In a case where the configuration of the second configuration change affects Layer 2, the terminal re-establishes or resets at least one of the PDCP entity and the RLC entity corresponding to the dedicated bearer; or,

[0417] In a case where the configuration of the second configuration change carries an explicit reset or re-establishment indication, the terminal re-establishes or resets at least one of the PDCP entity and the RLC entity corresponding to the dedicated bearer.

[0418] Optionally, in the case of cell handover, the second configuration is used to configure at least one of the following:

[0419] Resetting the RLC entity corresponding to the dedicated bearer of the terminal;

[0420] Handover processing of the PDCP entity corresponding to the dedicated bearer of the terminal, the handover processing including at least one of the following:

[0421] Clear the cache and reset the transfer variables;

[0422] Keep the cache and reset the transfer variables;

[0423] Preserve cache and transfer variables.

[0424] Optionally, the device further comprises:

[0425] The reporting module is used to report capability information about the dedicated bearer.

[0426] Optionally, the capability information includes at least one of the following:

[0427] whether the terminal supports the dedicated bearer;

[0428] at least one capability of the dedicated bearer supported by the terminal;

[0429] whether the terminal supports information collection;

[0430] at least one function of information collection supported by the terminal;

[0431] the maximum number of the dedicated bearers supported by the terminal;

[0432] The capability range of at least one protocol layer corresponding to the dedicated bearer supported by the terminal.

[0433] The above-mentioned information transmission device can improve the transmission performance of the terminal.

[0434] In the embodiments of the present application, the information transmission device may be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or chip. For example, the electronic device may be a terminal, or may be a device other than a terminal. For example, the terminal may include but is not limited to the types of terminals listed in the embodiments of the present application, and the other devices may be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0435] The information transmission device provided in the embodiment of the present application can implement each process implemented by the method embodiment shown in Figure 2 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0436] Please refer to FIG11 , which is a structural diagram of a capability information reporting device provided in an embodiment of the present application. As shown in FIG11 , the capability information reporting device 1100 includes:

[0437] A reporting module 1101 is configured to report capability information about a dedicated bearer;

[0438] The dedicated bearer is a dedicated bearer for information transmission, and the dedicated bearer is independent of SRB and DRB.

[0439] Optionally, the capability information includes at least one of the following:

[0440] whether the terminal supports the dedicated bearer;

[0441] at least one capability of the dedicated bearer supported by the terminal;

[0442] whether the terminal supports information collection;

[0443] at least one function of information collection supported by the terminal;

[0444] the maximum number of the dedicated bearers supported by the terminal;

[0445] The capability range of at least one protocol layer corresponding to the dedicated bearer supported by the terminal.

[0446] The above-mentioned capability information reporting device can improve the transmission performance of the terminal.

[0447] In the embodiments of the present application, the capability information reporting device may be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or chip. For example, the electronic device may be a terminal, or may be a device other than a terminal. For example, the terminal may include but is not limited to the types of terminals listed in the embodiments of the present application, and other devices may be servers, NAS, etc., which are not specifically limited in the embodiments of the present application.

[0448] The capability information reporting device provided in the embodiment of the present application can implement the various processes implemented by the method embodiment shown in Figure 8 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0449] Please refer to FIG. 12 , which is a structural diagram of another information transmission device provided in an embodiment of the present application. As shown in FIG. 12 , the information transmission device 1200 includes:

[0450] A first sending module 1201 is configured to send a first configuration to a terminal, where the first configuration is used to configure a dedicated bearer for information transmission, where the dedicated bearer is independent of a signaling radio bearer (SRB) and a data radio bearer (DRB);

[0451] The first receiving module 1202 is configured to receive information transmitted by the terminal through the dedicated bearer.

[0452] Optionally, the dedicated bearer is used for at least one of the following:

[0453] Information interaction between the terminal and the second radio access network device;

[0454] Information interaction between the terminal and the core network function.

[0455] Optionally, the first configuration includes at least one of the following:

[0456] The identifier of the dedicated bearer, the attribute information of the dedicated bearer, the routing related information of the dedicated bearer, the processing information of the dedicated bearer during the switching process, and the mapping relationship of the dedicated bearer.

[0457] Optionally, the attribute information of the dedicated bearer includes at least one of the following:

[0458] Attribute information of at least one protocol layer corresponding to the dedicated bearer, transmission configuration information of the dedicated bearer, security attribute information of the dedicated bearer, segmentation attribute information of the dedicated bearer, and bearer type of the dedicated bearer.

[0459] Optionally, the transmission configuration information of the dedicated bearer includes at least one of the following:

[0460] The transmission mode of the dedicated bearer, the maximum data length of the dedicated bearer, the reordering timing information of the dedicated bearer, the delivery method of the dedicated bearer, the logical channel identifier of the dedicated bearer, the logical channel priority of the dedicated bearer, and the guaranteed bit rate of the dedicated bearer.

[0461] Optionally, the bearer type of the dedicated bearer includes: a separate bearer; or

[0462] The transmission mode of the dedicated bearer includes at least one of the following: a radio link control RLC transmission mode and a dual active protocol stack DAPS transmission mode.

[0463] Optionally, the mapping relationship of the dedicated bearer includes at least one of the following:

[0464] The mapping relationship between the dedicated bearer and the protocol entity;

[0465] The mapping relationship between the dedicated bearer and the data of the protocol entity.

[0466] Optionally, the routing related information of the dedicated bearer includes:

[0467] Routing information of the dedicated bearer; or

[0468] Data packet format information, where the data packet format information is used to determine routing information of the data packet of the dedicated bearer.

[0469] Optionally, the first configuration is carried in a configuration message, wherein:

[0470] The first configuration is carried in a first information field in the configuration message, where the first information field is an information field dedicated to the dedicated bearer configuration; or

[0471] The first configuration is carried in a second information field in the configuration message, and the second information field is a configuration information field for multiple bearers.

[0472] Optionally, the dedicated bearer has at least one of the following characteristics:

[0473] The dedicated bearer can exist simultaneously with the signaling radio bearer SRB and the data radio bearer DRB;

[0474] The dedicated bearer can be transmitted in parallel with the SRB and DRB;

[0475] The dedicated bearer is established under target conditions;

[0476] The identifier of the dedicated bearer is arranged together with the identifier of the SRB, or the identifier of the dedicated bearer is arranged together with the identifier of the DRB, or the identifier of the dedicated bearer is arranged alone;

[0477] The attributes of the dedicated bearer are configurable;

[0478] The dedicated bearer corresponds to at least one quality of service QoS;

[0479] The dedicated bearer supports cell switching.

[0480] Optionally, the attributes of the dedicated bearer include at least one of the following:

[0481] The transmission configuration of the dedicated bearer, the security attributes of the dedicated bearer, and the segmentation attributes of the dedicated bearer.

[0482] Optionally, the dedicated bearer is used to transmit information of at least one of the following protocol entities:

[0483] Service Data Adaptation Protocol DSAP-Uu entity;

[0484] A DSAP-Ng entity, wherein the DSAP-Ng entity is used for interaction between the first radio access network device and a core network function;

[0485] DSAP-Xn entity, the DSAP-Xn entity is used for interaction between the first wireless access network device and other wireless access network devices.

[0486] Optionally, the device further comprises:

[0487] The second sending module is used to send a second configuration to the terminal, where the second configuration is used to reconfigure the dedicated bearer.

[0488] Optionally, when the configuration of the second configuration change does not affect layer 2, the state variables of the Packet Data Convergence Protocol PDCP entity and the Radio Resource Control RLC entity corresponding to the dedicated bearer are maintained; or,

[0489] In the case where the configuration of the second configuration change has no explicit reset or no explicit re-establishment indication, the state variables of the Packet Data Convergence Protocol (PDCP) entity and the Radio Resource Control (RLC) entity corresponding to the dedicated bearer are maintained; or,

[0490] In a case where the configuration of the second configuration change affects Layer 2, the radio access network device reestablishes or resets at least one of the PDCP entity and the RLC entity corresponding to the dedicated bearer; or

[0491] In a case where the configuration of the second configuration change carries an explicit reset or re-establishment indication, the radio access network device re-establishes or resets at least one of the PDCP entity and the RLC entity corresponding to the dedicated bearer.

[0492] Optionally, in the case of cell handover, the second configuration is used to configure at least one of the following:

[0493] Resetting the RLC entity corresponding to the dedicated bearer of the terminal;

[0494] Handover processing of the PDCP entity corresponding to the dedicated bearer of the terminal, the handover processing including at least one of the following:

[0495] Clear the cache and reset the transfer variables;

[0496] Keep the cache and reset the transfer variables;

[0497] Preserve cache and transfer variables.

[0498] Optionally, the device further comprises:

[0499] The second receiving module is configured to receive capability information of the terminal regarding the dedicated bearer reported by the terminal.

[0500] Optionally, the capability information includes at least one of the following:

[0501] whether the terminal supports the dedicated bearer;

[0502] at least one capability of the dedicated bearer supported by the terminal;

[0503] whether the terminal supports information collection;

[0504] at least one function of information collection supported by the terminal;

[0505] the maximum number of the dedicated bearers supported by the terminal;

[0506] The capability range of at least one protocol layer corresponding to the dedicated bearer supported by the terminal.

[0507] Optionally, the sending the first configuration to the terminal includes at least one of the following:

[0508] When the wireless access network device triggers information transmission, sending a first configuration to the terminal;

[0509] When the radio access network device receives a first trigger message sent by the core network for triggering information transmission, sending a first configuration to the terminal;

[0510] When the radio access network device receives a second trigger message for triggering information transmission sent by other radio access network devices, the radio access network device sends a first configuration to the terminal.

[0511] Optionally, when the radio access network device receives a first trigger message sent by a core network for triggering information transmission, the apparatus further includes:

[0512] A third sending module is configured to transparently transmit the information to the core network; or

[0513] The fourth sending module is used to process the information to the core network and send the processed information to the core network.

[0514] The above-mentioned information transmission device can improve the transmission performance of the terminal.

[0515] The information transmission device in the embodiment of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal or a network-side device.

[0516] The information transmission device provided in the embodiment of the present application can implement each process implemented by the method embodiment shown in Figure 4 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0517] Please refer to FIG. 13 , which is a structural diagram of a capability information receiving apparatus provided in an embodiment of the present application. As shown in FIG. 13 , the capability information receiving apparatus 1300 includes:

[0518] The receiving module 1301 is configured to receive capability information of the terminal regarding a dedicated bearer reported by the terminal;

[0519] The dedicated bearer is a dedicated bearer for information transmission, and the dedicated bearer is independent of SRB and DRB.

[0520] Optionally, the capability information includes at least one of the following:

[0521] whether the terminal supports the dedicated bearer;

[0522] at least one capability of the dedicated bearer supported by the terminal;

[0523] whether the terminal supports information collection;

[0524] at least one function of information collection supported by the terminal;

[0525] the maximum number of the dedicated bearers supported by the terminal;

[0526] The capability range of at least one protocol layer corresponding to the dedicated bearer supported by the terminal.

[0527] The capability information receiving device can improve the transmission performance of the terminal.

[0528] The capability information receiving device in the embodiment of the present application may be an electronic device, such as an electronic device with an operating system, or a component in the electronic device, such as an integrated circuit or a chip. The electronic device may be a terminal or a network-side device.

[0529] The embodiment of the present application provides a capability information receiving device that can implement the various processes implemented by the method embodiment shown in Figure 5 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0530] Please refer to FIG. 14 , which is a structural diagram of another information transmission device provided in an embodiment of the present application. As shown in FIG. 14 , the information transmission device 1400 includes:

[0531] The sending module 1401 is configured to send a trigger message for triggering information transmission to a wireless access network device;

[0532] A receiving module 1402 is configured to receive information sent by the radio access network device or the control node;

[0533] The information is information transmitted by the terminal through a dedicated bearer; or, the information is information generated based on information transmitted by the terminal through a dedicated bearer; the dedicated bearer is a dedicated bearer for information transmission, and the dedicated bearer is independent of the signaling radio bearer SRB and the data radio bearer DRB.

[0534] Optionally, the control node includes:

[0535] Control plane control node, or user plane control node.

[0536] Optionally, the receiving module 1402 receives the information sent by the control node through a service data adaptation protocol DSAP-core network CN entity; or,

[0537] The receiving module 1402 receives information sent by the wireless access network device and processed by the wireless access network device through the DSAP-Ng entity.

[0538] The above-mentioned information transmission device can improve the transmission performance of the terminal.

[0539] The information transmission device in the embodiment of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal or a network-side device.

[0540] The information transmission device provided in the embodiment of the present application can implement the various processes implemented by the method embodiment shown in Figure 9 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0541] Optionally, as shown in Figure 15, an embodiment of the present application further provides a communication device 1500, including a processor 1501 and a memory 1502, wherein the memory 1502 stores a program or instruction that can be run on the processor 1501. For example, when the communication device 1500 is a terminal, the program or instruction, when executed by the processor 1501, implements the various steps of the embodiment of the information transmission method on the terminal side, and can achieve the same technical effect. When the communication device 1500 is a wireless access network device, the program or instruction, when executed by the processor 1501, implements the various steps of the embodiment of the information transmission method on the wireless access network device side, and can achieve the same technical effect. When the communication device 1500 is a core network function, the program or instruction, when executed by the processor 1501, implements the various steps of the embodiment of the information transmission method on the core network function side, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0542] An embodiment of the present application also provides a communications device, including a processor and a communications interface, wherein the communications interface is configured to obtain a first configuration, the first configuration being configured to configure a dedicated bearer for information transmission, the dedicated bearer being independent of an SRB and a DRB; and a transmission module configured to transmit information via the dedicated bearer. This communications device embodiment corresponds to the aforementioned perception measurement result processing method embodiment, and each implementation process and implementation method of the aforementioned method embodiment are applicable to this communications device embodiment and can achieve the same technical effects.

[0543] An embodiment of the present application further provides a communications device, including a processor and a communications interface, wherein the communications interface is configured to report capability information about a dedicated bearer; wherein the dedicated bearer is a dedicated bearer for information transmission and is independent of SRBs and DRBs. This communications device embodiment corresponds to the aforementioned capability information reporting method embodiment, and each implementation process and implementation method of the aforementioned method embodiment are applicable to this communications device embodiment and can achieve the same technical effects.

[0544] Specifically, FIG16 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.

[0545] The terminal 1600 includes but is not limited to: a radio frequency unit 1601, a network module 1602, an audio output unit 1603, an input unit 1604, a sensor 1605, a display unit 1606, a user input unit 1607, an interface unit 1608, a memory 1609 and at least some of the components of the processor 1610.

[0546] Those skilled in the art will appreciate that the terminal 1600 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to the processor 1610 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The terminal structure shown in FIG16 does not limit the terminal. The terminal may include more or fewer components than shown, or combine certain components, or arrange the components differently, which will not be described in detail here.

[0547] It should be understood that in an embodiment of the present application, the input unit 1604 may include a graphics processing unit (GPU) 16041 and a microphone 16042, and the graphics processing unit 16041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 1606 may include a display panel 16061, and the display panel 16061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 1607 includes a touch panel 16071 and at least one of the other input terminals 16072. The touch panel 16071 is also called a touch screen. The touch panel 16071 may include two parts: a touch detection device and a touch controller. Other input terminals 16072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and an operating stick, which will not be repeated here.

[0548] In the embodiment of the present application, after receiving downlink data from a network-side terminal, the RF unit 1601 may transmit the data to the processor 1610 for processing. Furthermore, the RF unit 1601 may send uplink data to the network-side terminal. Typically, the RF unit 1601 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.

[0549] The memory 1609 can be used to store software programs or instructions and various data. The memory 1609 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 1609 may include a volatile memory or a non-volatile memory, or the memory 1609 may include both volatile and non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DRRAM). The memory 1609 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0550] Processor 1610 may include one or more processing units. Optionally, processor 1610 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 1610.

[0551] In one embodiment:

[0552] The radio frequency unit 1601 is used to obtain a first configuration, where the first configuration is used to configure a dedicated bearer for information transmission, where the dedicated bearer is independent of the signaling radio bearer SRB and the data radio bearer DRB; and information is transmitted through the dedicated bearer.

[0553] Optionally, the dedicated bearer is used for at least one of the following:

[0554] Information interaction between the terminal and the wireless access network device;

[0555] Information interaction between the terminal and the core network function.

[0556] Optionally, the first configuration includes at least one of the following:

[0557] The identifier of the dedicated bearer, the attribute information of the dedicated bearer, the routing related information of the dedicated bearer, the processing information of the dedicated bearer during the switching process, and the mapping relationship of the dedicated bearer.

[0558] Optionally, the attribute information of the dedicated bearer includes at least one of the following:

[0559] Attribute information of at least one protocol layer corresponding to the dedicated bearer, transmission configuration information of the dedicated bearer, security attribute information of the dedicated bearer, segmentation attribute information of the dedicated bearer, and bearer type of the dedicated bearer.

[0560] Optionally, the transmission configuration information of the dedicated bearer includes at least one of the following:

[0561] The transmission mode of the dedicated bearer, the maximum data length of the dedicated bearer, the reordering information of the dedicated bearer, the delivery method of the dedicated bearer, the logical channel identifier of the dedicated bearer, the logical channel priority of the dedicated bearer, and the guaranteed bit rate of the dedicated bearer.

[0562] Optionally, the bearer type of the dedicated bearer includes: a separate bearer; or

[0563] The transmission mode of the dedicated bearer includes at least one of the following: a radio link control RLC transmission mode and a dual active protocol stack DAPS transmission mode.

[0564] Optionally, the mapping relationship of the dedicated bearer includes at least one of the following:

[0565] The mapping relationship between the dedicated bearer and the protocol entity;

[0566] The mapping relationship between the dedicated bearer and the data of the protocol entity.

[0567] Optionally, the routing related information of the dedicated bearer includes:

[0568] Routing information of the dedicated bearer; or

[0569] Data packet format information, where the data packet format information is used to determine routing information of the data packet of the dedicated bearer.

[0570] Optionally, the first configuration is carried in a configuration message, wherein:

[0571] The first configuration is carried in a first information field in the configuration message, where the first information field is an information field dedicated to the dedicated bearer configuration; or

[0572] The first configuration is carried in a second information field in the configuration message, and the second information field is a configuration information field for multiple bearers.

[0573] Optionally, the dedicated bearer has at least one of the following characteristics:

[0574] The dedicated bearer can coexist with SRB and DRB;

[0575] The dedicated bearer can be transmitted in parallel with the SRB and DRB;

[0576] The dedicated bearer and SRB can exist at the same time;

[0577] The dedicated bearer and the SRB can be transmitted in parallel;

[0578] The dedicated bearer is established under target conditions;

[0579] The identifier of the dedicated bearer is arranged together with the identifier of the SRB, or the identifier of the dedicated bearer is arranged together with the identifier of the DRB, or the identifier of the dedicated bearer is arranged alone;

[0580] The attributes of the dedicated bearer are configurable;

[0581] The dedicated bearer corresponds to at least one quality of service QoS;

[0582] The dedicated bearer supports cell switching.

[0583] Optionally, the attributes of the dedicated bearer include at least one of the following:

[0584] The transmission configuration of the dedicated bearer, the security attributes of the dedicated bearer, and the segmentation attributes of the dedicated bearer.

[0585] Optionally, the dedicated bearer is used to transmit information of at least one of the following protocol entities:

[0586] Service Data Adaptation Protocol DSAP-Core Network CN entity;

[0587] DSAP-Uu entity.

[0588] Optionally, the radio frequency unit 1601 is further used to receive a second configuration sent by a network side device, where the second configuration is used to reconfigure the dedicated bearer.

[0589] Optionally, when the configuration of the second configuration change does not affect layer 2, the state variables of the Packet Data Convergence Protocol PDCP entity and the Radio Resource Control RLC entity corresponding to the dedicated bearer are maintained; or,

[0590] In the case where the configuration of the second configuration change has no explicit reset or no explicit re-establishment indication, the state variables of the Packet Data Convergence Protocol (PDCP) entity and the Radio Resource Control (RLC) entity corresponding to the dedicated bearer are maintained; or,

[0591] In a case where the configuration of the second configuration change affects Layer 2, the terminal re-establishes or resets at least one of the PDCP entity and the RLC entity corresponding to the dedicated bearer; or,

[0592] In a case where the configuration of the second configuration change carries an explicit reset or re-establishment indication, the terminal re-establishes or resets at least one of the PDCP entity and the RLC entity corresponding to the dedicated bearer.

[0593] Optionally, in the case of cell handover, the second configuration is used to configure at least one of the following:

[0594] Resetting the RLC entity corresponding to the dedicated bearer of the terminal;

[0595] Handover processing of the PDCP entity corresponding to the dedicated bearer of the terminal, the handover processing including at least one of the following:

[0596] Clear the cache and reset the transfer variables;

[0597] Keep the cache and reset the transfer variables;

[0598] Preserve cache and transfer variables.

[0599] Optionally, the radio frequency unit 1601 is further configured to report capability information about the dedicated bearer.

[0600] Optionally, the capability information includes at least one of the following:

[0601] whether the terminal supports the dedicated bearer;

[0602] at least one capability of the dedicated bearer supported by the terminal;

[0603] whether the terminal supports information collection;

[0604] at least one function of information collection supported by the terminal;

[0605] the maximum number of the dedicated bearers supported by the terminal;

[0606] The capability range of at least one protocol layer corresponding to the dedicated bearer supported by the terminal.

[0607] In another embodiment:

[0608] The radio frequency unit 1601 is used to report capability information about a dedicated bearer; wherein the dedicated bearer is a dedicated bearer for information transmission, and the dedicated bearer is independent of SRB and DRB.

[0609] Optionally, the capability information includes at least one of the following:

[0610] whether the terminal supports the dedicated bearer;

[0611] at least one capability of the dedicated bearer supported by the terminal;

[0612] whether the terminal supports information collection;

[0613] at least one function of information collection supported by the terminal;

[0614] the maximum number of the dedicated bearers supported by the terminal;

[0615] The capability range of at least one protocol layer corresponding to the dedicated bearer supported by the terminal.

[0616] The above terminal can improve the transmission performance of the terminal.

[0617] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the above-mentioned perception measurement result sending method and achieve the same or corresponding technical effects. To avoid repetition, it will not be repeated here.

[0618] An embodiment of the present application further provides a device including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the method embodiment shown in Figure 4 or Figure 5. This device embodiment corresponds to the above-mentioned method for sending perception measurement results, and each implementation process and implementation method of the above-mentioned method embodiment are applicable to this device embodiment and can achieve the same technical effect.

[0619] An embodiment of the present application also provides a device, including a processor and a communication interface, wherein the communication interface is used to send a first configuration to a terminal, the first configuration is used to configure a dedicated bearer for information transmission, and the dedicated bearer is independent of SRB and DRB; a receiving module is used to receive information transmitted by the terminal through the dedicated bearer.

[0620] An embodiment of the present application also provides a device, including a processor and a communication interface, wherein the communication interface is used to receive capability information of the terminal about a dedicated bearer reported by the terminal; wherein the dedicated bearer is a dedicated bearer for information transmission, and the dedicated bearer is independent of SRB and DRB.

[0621] Specifically, embodiments of the present application also provide a wireless access network device. As shown in Figure 17, wireless access network device 1700 includes an antenna 1701, a radio frequency device 1702, a baseband device 1703, a processor 1704, and a memory 1705. Antenna 1701 is connected to radio frequency device 1702. In the uplink direction, radio frequency device 1702 receives information via antenna 1701 and sends the received information to baseband device 1703 for processing. In the downlink direction, baseband device 1703 processes the information to be transmitted and sends it to radio frequency device 1702. Radio frequency device 1702 processes the received information and then sends it through antenna 1701.

[0622] The perception measurement method in the above embodiment may be implemented in the baseband device 1703 , which includes a baseband processor.

[0623] The baseband device 1703 may include, for example, at least one baseband board, on which multiple chips are arranged, as shown in Figure 17, one of which is, for example, a baseband processor, which is connected to the memory 1705 through a bus interface to call the program in the memory 1705 and execute the device operations shown in the above method embodiment.

[0624] The device may further include a network interface 1706 , such as a Common Public Radio Interface (CPRI).

[0625] Specifically, the device 1700 of the embodiment of the present application also includes: instructions or programs stored in the memory 1705 and executable on the processor 1704. The processor 1704 calls the instructions or programs in the memory 1705 to execute the methods executed by the modules shown in FIG12 or 13 and achieve the same technical effect. To avoid repetition, they will not be elaborated here.

[0626] In one embodiment:

[0627] Among them, the radio frequency device 1702 is used to send a first configuration to the terminal, where the first configuration is used to configure a dedicated bearer for information transmission, and the dedicated bearer is independent of the signaling radio bearer SRB and the data radio bearer DRB; and receive the information transmitted by the terminal through the dedicated bearer.

[0628] Optionally, the dedicated bearer is used for at least one of the following:

[0629] Information interaction between the terminal and the second radio access network device;

[0630] Information interaction between the terminal and the core network function.

[0631] Optionally, the first configuration includes at least one of the following:

[0632] The identifier of the dedicated bearer, the attribute information of the dedicated bearer, the routing related information of the dedicated bearer, the processing information of the dedicated bearer during the switching process, and the mapping relationship of the dedicated bearer.

[0633] Optionally, the attribute information of the dedicated bearer includes at least one of the following:

[0634] Attribute information of at least one protocol layer corresponding to the dedicated bearer, transmission configuration information of the dedicated bearer, security attribute information of the dedicated bearer, segmentation attribute information of the dedicated bearer, and bearer type of the dedicated bearer.

[0635] Optionally, the transmission configuration information of the dedicated bearer includes at least one of the following:

[0636] The transmission mode of the dedicated bearer, the maximum data length of the dedicated bearer, the reordering timing information of the dedicated bearer, the delivery method of the dedicated bearer, the logical channel identifier of the dedicated bearer, the logical channel priority of the dedicated bearer, and the guaranteed bit rate of the dedicated bearer.

[0637] Optionally, the bearer type of the dedicated bearer includes: a separate bearer; or

[0638] The transmission mode of the dedicated bearer includes at least one of the following: a radio link control RLC transmission mode and a dual active protocol stack DAPS transmission mode.

[0639] Optionally, the mapping relationship of the dedicated bearer includes at least one of the following:

[0640] The mapping relationship between the dedicated bearer and the protocol entity;

[0641] The mapping relationship between the dedicated bearer and the data of the protocol entity.

[0642] Optionally, the routing related information of the dedicated bearer includes:

[0643] Routing information of the dedicated bearer; or

[0644] Data packet format information, where the data packet format information is used to determine routing information of the data packet of the dedicated bearer.

[0645] Optionally, the first configuration is carried in a configuration message, wherein:

[0646] The first configuration is carried in a first information field in the configuration message, where the first information field is an information field dedicated to the dedicated bearer configuration; or

[0647] The first configuration is carried in a second information field in the configuration message, and the second information field is a configuration information field for multiple bearers.

[0648] Optionally, the dedicated bearer has at least one of the following characteristics:

[0649] The dedicated bearer can exist simultaneously with the signaling radio bearer SRB and the data radio bearer DRB;

[0650] The dedicated bearer can be transmitted in parallel with the SRB and DRB;

[0651] The dedicated bearer is established under target conditions;

[0652] The identifier of the dedicated bearer is arranged together with the identifier of the SRB, or the identifier of the dedicated bearer is arranged together with the identifier of the DRB, or the identifier of the dedicated bearer is arranged alone;

[0653] The attributes of the dedicated bearer are configurable;

[0654] The dedicated bearer corresponds to at least one quality of service QoS;

[0655] The dedicated bearer supports cell switching.

[0656] Optionally, the attributes of the dedicated bearer include at least one of the following:

[0657] The transmission configuration of the dedicated bearer, the security attributes of the dedicated bearer, and the segmentation attributes of the dedicated bearer.

[0658] Optionally, the dedicated bearer is used to transmit information of at least one of the following protocol entities:

[0659] Service Data Adaptation Protocol DSAP-Uu entity;

[0660] A DSAP-Ng entity, wherein the DSAP-Ng entity is used for interaction between the first radio access network device and a core network function;

[0661] DSAP-Xn entity, the DSAP-Xn entity is used for interaction between the first wireless access network device and other wireless access network devices.

[0662] Optionally, the radio frequency device 1702 is further used to send a second configuration to the terminal, where the second configuration is used to reconfigure the dedicated bearer.

[0663] Optionally, when the configuration of the second configuration change does not affect layer 2, the state variables of the Packet Data Convergence Protocol PDCP entity and the Radio Resource Control RLC entity corresponding to the dedicated bearer are maintained; or,

[0664] In the case where the configuration of the second configuration change has no explicit reset or no explicit re-establishment indication, the state variables of the Packet Data Convergence Protocol (PDCP) entity and the Radio Resource Control (RLC) entity corresponding to the dedicated bearer are maintained; or,

[0665] In a case where the configuration of the second configuration change affects Layer 2, the radio access network device reestablishes or resets at least one of the PDCP entity and the RLC entity corresponding to the dedicated bearer; or

[0666] In a case where the configuration of the second configuration change carries an explicit reset or re-establishment indication, the radio access network device re-establishes or resets at least one of the PDCP entity and the RLC entity corresponding to the dedicated bearer.

[0667] Optionally, in the case of cell handover, the second configuration is used to configure at least one of the following:

[0668] Resetting the RLC entity corresponding to the dedicated bearer of the terminal;

[0669] Handover processing of the PDCP entity corresponding to the dedicated bearer of the terminal, the handover processing including at least one of the following:

[0670] Clear the cache and reset the transfer variables;

[0671] Keep the cache and reset the transfer variables;

[0672] Preserve cache and transfer variables.

[0673] Optionally, the radio frequency device 1702 is further configured to receive capability information of the terminal regarding the dedicated bearer reported by the terminal.

[0674] Optionally, the capability information includes at least one of the following:

[0675] whether the terminal supports the dedicated bearer;

[0676] at least one capability of the dedicated bearer supported by the terminal;

[0677] whether the terminal supports information collection;

[0678] at least one function of information collection supported by the terminal;

[0679] the maximum number of the dedicated bearers supported by the terminal;

[0680] The capability range of at least one protocol layer corresponding to the dedicated bearer supported by the terminal.

[0681] Optionally, the sending the first configuration to the terminal includes at least one of the following:

[0682] When the wireless access network device triggers information transmission, sending a first configuration to the terminal;

[0683] When the radio access network device receives a first trigger message sent by the core network for triggering information transmission, sending a first configuration to the terminal;

[0684] When the radio access network device receives a second trigger message for triggering information transmission sent by other radio access network devices, the radio access network device sends a first configuration to the terminal.

[0685] Optionally, when the radio access network device receives a first trigger message sent by the core network for triggering information transmission, the radio frequency device 1702 is further configured to:

[0686] Transmit the information to the core network; or

[0687] The information is processed to the core network, and the processed information is sent to the core network.

[0688] In another embodiment:

[0689] The radio frequency device 1702 is used to receive capability information about a dedicated bearer of the terminal reported by the terminal; wherein the dedicated bearer is a dedicated bearer for information transmission, and the dedicated bearer is independent of SRB and DRB.

[0690] Optionally, the capability information includes at least one of the following:

[0691] whether the terminal supports the dedicated bearer;

[0692] at least one capability of the dedicated bearer supported by the terminal;

[0693] whether the terminal supports information collection;

[0694] at least one function of information collection supported by the terminal;

[0695] the maximum number of the dedicated bearers supported by the terminal;

[0696] The capability range of at least one protocol layer corresponding to the dedicated bearer supported by the terminal.

[0697] The above-mentioned device can improve the transmission performance of the terminal.

[0698] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the above-mentioned method embodiment and achieve the same or corresponding technical effects. To avoid repetition, it will not be repeated here.

[0699] The present application also provides an embodiment of a device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the method embodiment shown in FIG6 . This device embodiment corresponds to the aforementioned signal measurement method embodiment, and each implementation process and implementation method of the aforementioned method embodiment are applicable to this device embodiment and can achieve the same technical effects.

[0700] An embodiment of the present application also provides a device, including a processor and a communication interface, wherein the communication interface is used to send a trigger message for triggering information transmission to a wireless access network device; receive information sent by the wireless access network device or the control node; wherein the information is information transmitted by the terminal through a dedicated bearer; or, the information is information generated based on the information transmitted by the terminal through a dedicated bearer; the dedicated bearer is a dedicated bearer for information transmission, and the dedicated bearer is independent of the signaling radio bearer SRB and the data radio bearer DRB.

[0701] Specifically, the embodiment of the present application further provides a network-side device. As shown in FIG18 , the network-side device 1800 includes a processor 1801, a network interface 1802, and a memory 1803. The network interface 1802 is, for example, a common public radio interface (CPRI).

[0702] Specifically, the network side device 1800 of the embodiment of the present application also includes: instructions or programs stored in the memory 1803 and executable on the processor 1801. The processor 1801 calls the instructions or programs in the memory 1803 to execute the methods executed by the modules shown in FIG12 and achieve the same technical effect. To avoid repetition, it will not be elaborated here.

[0703] Network interface 1802, used to send a trigger message for triggering information transmission to a radio access network device; receive information sent by the radio access network device or the control node;

[0704] The information is information transmitted by the terminal through a dedicated bearer; or, the information is information generated based on information transmitted by the terminal through a dedicated bearer; the dedicated bearer is a dedicated bearer for information transmission, and the dedicated bearer is independent of the signaling radio bearer SRB and the data radio bearer DRB.

[0705] Optionally, the control node includes:

[0706] Control plane control node, or user plane control node.

[0707] Optionally, the network interface 1802 receives the information sent by the control node through a service data adaptation protocol DSAP-core network CN entity; or,

[0708] The network interface 1802 receives information sent by the wireless access network device through the DSAP-Ng entity and processed by the wireless access network device.

[0709] The above-mentioned device can improve the transmission performance of the terminal.

[0710] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the above-mentioned method embodiment and achieve the same or corresponding technical effects. To avoid repetition, it will not be repeated here.

[0711] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, each process of the above-mentioned information transmission method, capability information reporting method or capability information receiving method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0712] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as ROM, RAM, a magnetic disk, or an optical disk. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0713] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned information transmission method, capability information reporting method or capability information receiving method embodiments, and can achieve the same technical effect. To avoid repetition, they will not be repeated here.

[0714] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0715] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the above-mentioned information transmission method, capability information reporting method or capability information receiving method embodiments, and can achieve the same technical effects. To avoid repetition, they are not repeated here.

[0716] An embodiment of the present application further provides a wireless communication system, including: a terminal, a wireless access network device, and a core network function, wherein the terminal can be used to execute the steps of the information transmission method on the terminal side provided in the embodiment of the present application, the wireless access network device can be used to execute the steps of the information transmission method on the wireless access network device side provided in the embodiment of the present application, and the core network function can be used to execute the steps of the information transmission method on the core network function side provided in the embodiment of the present application.

[0717] An embodiment of the present application further provides a wireless communication system, including: a terminal and a wireless access network device, wherein the terminal can be used to execute the steps of the information transmission method on the terminal side provided in the embodiment of the present application, or the terminal can be used to execute the steps of the capability information reporting method provided in the embodiment of the present application, and the wireless access network device can be used to execute the steps of the information transmission method on the wireless access network device side provided in the embodiment of the present application, or the wireless access network device can be used to execute the steps of the capability information receiving method provided in the embodiment of the present application.

[0718] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0719] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general-purpose hardware platform, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for enabling a terminal or network-side device to execute the methods described in each embodiment of the present application.

[0720] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. An information transmission method, comprising: The terminal obtains a first configuration, where the first configuration is used to configure a dedicated bearer for information transmission, where the dedicated bearer is independent of a signaling radio bearer SRB and a data radio bearer DRB; The terminal transmits information through the dedicated bearer.

2. The method of claim 1, wherein: The dedicated bearer is used for at least one of the following: Information interaction between the terminal and the wireless access network device; Information interaction between the terminal and the core network function.

3. The method according to claim 1 or 2, wherein: The first configuration includes at least one of the following: The identifier of the dedicated bearer, the attribute information of the dedicated bearer, the routing related information of the dedicated bearer, the processing information of the dedicated bearer during the switching process, and the mapping relationship of the dedicated bearer.

4. The method of claim 3, wherein: The attribute information of the dedicated bearer includes at least one of the following: Attribute information of at least one protocol layer corresponding to the dedicated bearer, transmission configuration information of the dedicated bearer, security attribute information of the dedicated bearer, segmentation attribute information of the dedicated bearer, and bearer type of the dedicated bearer.

5. The method of claim 4, wherein: The transmission configuration information of the dedicated bearer includes at least one of the following: The transmission mode of the dedicated bearer, the maximum data length of the dedicated bearer, the reordering information of the dedicated bearer, the delivery method of the dedicated bearer, the logical channel identifier of the dedicated bearer, the logical channel priority of the dedicated bearer, and the guaranteed bit rate of the dedicated bearer.

6. The method according to claim 4 or 5, wherein: The bearer type of the dedicated bearer includes: a separate bearer; or, The transmission mode of the dedicated bearer includes at least one of the following: a radio link control RLC transmission mode and a dual activation protocol stack DAPS transmission mode.

7. The method according to any one of claims 4 to 6, wherein: The mapping relationship of the dedicated bearer includes at least one of the following: The mapping relationship between the dedicated bearer and the protocol entity; The mapping relationship between the dedicated bearer and the data of the protocol entity.

8. The method according to any one of claims 4 to 7, wherein: The routing related information of the dedicated bearer includes: routing information of the dedicated bearer; or Data packet format information, where the data packet format information is used to determine routing information of the data packet of the dedicated bearer.

9. The method according to any one of claims 1 to 8, wherein: The first configuration is carried in a configuration message, wherein: The first configuration is carried by a first information field in the configuration message, where the first information field is an information field dedicated to the dedicated bearer configuration; or, The first configuration is carried through a second information field in the configuration message, and the second information field is a configuration information field of multiple bearers.

10. The method according to any one of claims 1 to 9, wherein: The dedicated bearer has at least one of the following characteristics: The dedicated bearer can exist simultaneously with the SRB and the DRB; The dedicated bearer can be transmitted in parallel with the SRB and the DRB; The dedicated bearer and SRB can exist at the same time; The dedicated bearer and the SRB can be transmitted in parallel; The dedicated bearer is established under target conditions; The identifier of the dedicated bearer is arranged together with the identifier of the SRB, or the identifier of the dedicated bearer is arranged together with the identifier of the DRB, or the identifier of the dedicated bearer is arranged alone; The attributes of the dedicated bearer are configurable; The dedicated bearer corresponds to at least one quality of service QoS; The dedicated bearer supports cell switching.

11. The method of claim 10, wherein: The attributes of the dedicated bearer include at least one of the following: The transmission configuration of the dedicated bearer, the security attributes of the dedicated bearer, and the segmentation attributes of the dedicated bearer.

12. The method according to any one of claims 1 to 11, wherein: The dedicated bearer is used to transmit information of at least one of the following protocol entities: Service Data Adaptation Protocol DSAP-Core Network CN entity; DSAP-Uu entity.

13. The method according to any one of claims 1 to 12, further comprising: The terminal receives a second configuration sent by a network side device, where the second configuration is used to reconfigure the dedicated bearer.

14. The method of claim 13, wherein: In the case where the configuration of the second configuration change does not affect layer 2, the state variables of the packet data convergence protocol PDCP entity and the radio resource control RLC entity corresponding to the dedicated bearer are maintained; or, In the case where the configuration of the second configuration change has no explicit reset or no explicit re-establishment indication, the state variables of the Packet Data Convergence Protocol PDCP entity and the Radio Resource Control RLC entity corresponding to the dedicated bearer are maintained; or, In a case where the configuration of the second configuration change affects layer 2, the terminal reconstructs or resets at least one of the PDCP entity and the RLC entity corresponding to the dedicated bearer; or, In a case where the configuration of the second configuration change carries an explicit reset or re-establishment indication, the terminal re-establishes or resets at least one of the PDCP entity and the RLC entity corresponding to the dedicated bearer.

15. The method of claim 13, wherein: In the case of cell handover, the second configuration is used to configure at least one of the following: Resetting the RLC entity corresponding to the dedicated bearer of the terminal; A switching process of the PDCP entity corresponding to the dedicated bearer of the terminal, wherein the switching process includes at least one of the following: Clear the cache and reset the transfer variables; Keep the cache and reset the transfer variables; Preserve cache and transfer variables.

16. The method according to any one of claims 1 to 15, further comprising: The terminal reports capability information about the dedicated bearer.

17. The method of claim 16, wherein: The capability information includes at least one of the following: whether the terminal supports the dedicated bearer; at least one capability of the dedicated bearer supported by the terminal; whether the terminal supports information collection; at least one function of information collection supported by the terminal; The maximum number of the dedicated bearers supported by the terminal; The capability range of at least one protocol layer corresponding to the dedicated bearer supported by the terminal.

18. An information transmission method, comprising: The first radio access network device sends a first configuration to the terminal, where the first configuration is used to configure a dedicated bearer for information transmission, where the dedicated bearer is independent of a signaling radio bearer SRB and a data radio bearer DRB; The first radio access network device receives information transmitted by the terminal through the dedicated bearer.

19. The method of claim 18, wherein: The dedicated bearer is used for at least one of the following: Information interaction between the terminal and the second radio access network device; Information interaction between the terminal and the core network function.

20. The method of claim 18 or 19, wherein: The first configuration includes at least one of the following: The identifier of the dedicated bearer, the attribute information of the dedicated bearer, the routing related information of the dedicated bearer, the processing information of the dedicated bearer during the switching process, and the mapping relationship of the dedicated bearer.

21. The method according to any one of claims 18 to 20, wherein: The first configuration is carried in a configuration message, wherein: The first configuration is carried by a first information field in the configuration message, where the first information field is an information field dedicated to the dedicated bearer configuration; or, The first configuration is carried through a second information field in the configuration message, and the second information field is a configuration information field of multiple bearers.

22. The method of any one of claims 18 to 21, wherein: The dedicated bearer has at least one of the following characteristics: The dedicated bearer can exist simultaneously with the signaling radio bearer SRB and the data radio bearer DRB; The dedicated bearer can be transmitted in parallel with the SRB and the DRB; The dedicated bearer is established under target conditions; The identifier of the dedicated bearer is arranged together with the identifier of the SRB, or the identifier of the dedicated bearer is arranged together with the identifier of the DRB, or the identifier of the dedicated bearer is arranged alone; The attributes of the dedicated bearer are configurable; The dedicated bearer corresponds to at least one quality of service QoS; The dedicated bearer supports cell switching.

23. The method of any one of claims 18 to 22, wherein: The dedicated bearer is used to transmit information of at least one of the following protocol entities: Service Data Adaptation Protocol DSAP-Uu entity; A DSAP-Ng entity, wherein the DSAP-Ng entity is used for interaction between the first radio access network device and a core network function; DSAP-Xn entity, the DSAP-Xn entity is used for interaction between the first wireless access network device and other wireless access network devices.

24. The method of any one of claims 18 to 23, further comprising: The first radio access network device sends a second configuration to the terminal, where the second configuration is used to reconfigure the dedicated bearer.

25. The method of any one of claims 18 to 24, further comprising: The first radio access network device receives capability information of the terminal about the dedicated bearer reported by the terminal.

26. The method of any one of claims 18 to 25, wherein: The first radio access network device sending the first configuration to the terminal includes at least one of the following: In a case where the first radio access network device triggers information transmission, the first radio access network device sends a first configuration to the terminal; When the first radio access network device receives a first trigger message for triggering information transmission sent by the core network, the first radio access network device sends a first configuration to the terminal; In a case where the first radio access network device receives a second trigger message for triggering information transmission sent by other radio access network devices, the radio access network device sends a first configuration to the terminal.

27. An information transmission method, comprising: The core network function sends a trigger message for triggering information transmission to the wireless access network device; The core network function receives information sent by the wireless access network device or the control node; The information is information transmitted by the terminal through a dedicated bearer; or, the information is information generated based on information transmitted by the terminal through a dedicated bearer; the dedicated bearer is a dedicated bearer for information transmission, and the dedicated bearer is independent of the signaling radio bearer SRB and the data radio bearer DRB.

28. The method of claim 27, wherein: The control node comprises: Control plane control node, or user plane control node.

29. The method of claim 27 or 28, wherein: The core network function receives the information sent by the control node through the service data adaptation protocol DSAP-core network CN entity; or, The core network function receives information sent by the wireless access network device through the DSAP-Ng entity and processed by the wireless access network device.

30. An information transmission device, comprising: An acquisition module, configured to acquire a first configuration, where the first configuration is used to configure a dedicated bearer for information transmission, where the dedicated bearer is independent of a signaling radio bearer SRB and a data radio bearer DRB; A transmission module is used to transmit information through the dedicated bearer.

31. The apparatus of claim 30, further comprising: The receiving module is used to receive a second configuration sent by the network side, where the second configuration is used to reconfigure the dedicated bearer.

32. The apparatus of claim 30 or 31, further comprising: The reporting module is used to report capability information about the dedicated bearer.

33. An information transmission device, comprising: A first sending module, configured to send a first configuration to a terminal, where the first configuration is used to configure a dedicated bearer for information transmission, where the dedicated bearer is independent of a signaling radio bearer SRB and a data radio bearer DRB; The first receiving module is used to receive information transmitted by the terminal through the dedicated bearer.

34. The apparatus of claim 33, further comprising: The second sending module is used to send a second configuration to the terminal, where the second configuration is used to reconfigure the dedicated bearer.

35. The apparatus of claim 33 or 34, further comprising: The second receiving module is used to receive capability information of the terminal about the dedicated bearer reported by the terminal.

36. An information transmission device, comprising: A sending module, used to send a trigger message for triggering information transmission to a wireless access network device; A receiving module, used to receive information sent by the wireless access network device or the control node; The information is information transmitted by the terminal through a dedicated bearer; or, the information is information generated based on information transmitted by the terminal through a dedicated bearer; the dedicated bearer is a dedicated bearer for information transmission, and the dedicated bearer is independent of the signaling radio bearer SRB and the data radio bearer DRB.

37. A terminal comprising a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the programs or instructions are executed by the processor, the steps of the information transmission method according to any one of claims 1 to 17 are implemented.

38. A wireless access network device, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the information transmission method according to any one of claims 18 to 26 are implemented.

39. A core network function, comprising a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the programs or instructions are executed by the processor, the steps of the information transmission method as described in any one of claims 27 to 29 are implemented.

40. A readable storage medium storing a program or instruction, wherein the program or instruction, when executed by a processor, implements the steps of the information transmission method as described in any one of claims 1 to 17, or implements the steps of the information transmission method as described in any one of claims 18 to 26, or implements the steps of the information transmission method as described in any one of claims 27 to 29.

Images