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

Abstract

The invention discloses an information transmission method and device, a terminal, equipment and a core network function, and belongs to the technical field of communication, and the information transmission method comprises the steps that the terminal obtains first configuration, the first configuration is used for configuring a special bearer for information transmission, and the special bearer is independent of an SRB and a DRB; and the terminal transmits information through the dedicated bearer.

Description

Technical Field

[0001] This application belongs to the field of communication technologies, and particularly relates to an information transmission method, apparatus, terminal, device, and core network function. Background Art

[0002] In some related technologies, a terminal can only perform transmission using a Signaling Radio Bearer (SRB) or a Data Radio Bearer (DRB), resulting in relatively poor transmission performance of the terminal. Summary of the Invention

[0003] Embodiments of this application provide an information transmission method, apparatus, terminal, device, and core network function, which can solve the problem of relatively poor transmission performance of a terminal.

[0004] In a first aspect, an information transmission method is provided, including:

[0005] A terminal obtains a first configuration for configuring a dedicated bearer for information transmission, where the dedicated bearer is independent of the SRB and the DRB;

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

[0007] In a second aspect, an information transmission method is provided, including:

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

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

[0010] In a third aspect, an information transmission method is provided, including:

[0011] A core network function sends a trigger message for triggering information transmission to a radio access network device;

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

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

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

[0015] The terminal reports capability information about dedicated bearers;

[0016] Among them, the dedicated bearer is a dedicated bearer for information transmission, and the dedicated bearer is independent of the SRB and DRB.

[0017] In a fifth aspect, a method for receiving capability information is provided, including:

[0018] The radio access network device receives the capability information about the dedicated bearer of the terminal reported by the terminal;

[0019] Among them, the dedicated bearer is a dedicated bearer for information transmission, and the dedicated bearer is independent of the SRB and DRB.

[0020] In a sixth aspect, an information transmission device is provided, including:

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

[0022] A transmission module, configured to transmit information through the dedicated bearer.

[0023] In a seventh aspect, an information transmission device is provided, including:

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

[0025] A first receiving module, configured to receive information transmitted by the terminal through the dedicated bearer.

[0026] In an eighth aspect, an information transmission device is provided, including:

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

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

[0029] Among them, 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.

[0030] In a ninth aspect, a capability information reporting device is provided, including:

[0031] A reporting module, configured to report the capability information about the dedicated bearer;

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

[0033] In a tenth aspect, a capability information receiving device is provided, including:

[0034] A receiving module, configured to receive the capability information about the dedicated bearer of the terminal reported by the terminal;

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

[0036] In an eleventh aspect, a terminal is provided. The terminal includes a processor and a memory. The memory stores a program or instruction that can run on the processor. When the program or instruction is executed by the processor, the steps of the information transmission method on the terminal side provided in the embodiments 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 embodiments of the present application are implemented.

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

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

[0039] In a thirteenth aspect, a radio access network device is provided. The radio access network device includes a processor and a memory. The memory stores a program or instruction that can run on the processor. When the program or instruction is executed by the processor, the steps of the information transmission method on the radio access network device side provided in the embodiments 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 embodiments of the present application are implemented.

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

[0041] In a fourteenth aspect, a radio access network device is provided, including a processor and a communication interface. The communication interface is configured to receive the capability information of the terminal reported by the terminal regarding dedicated bearers. The dedicated bearer is a dedicated bearer for information transmission and is independent of the SRB and DRB.

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

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

[0044] In a seventeenth aspect, a readable storage medium is provided. Programs or instructions are stored on the readable storage medium. When the programs or instructions are executed by a processor, the steps of the information transmission method on the terminal side provided in the embodiments of the present application are implemented, or the steps of the information transmission method on the radio access network device side provided in the embodiments of the present application are implemented, or the steps of the information transmission method on the core network function side provided in the embodiments of the present application are implemented, or the steps of the capability information reporting method provided in the embodiments of the present application are implemented, or the steps of the capability information receiving method provided in the embodiments of the present application are implemented.

[0045] In an eighteenth aspect, a wireless communication system is provided, including a terminal, a radio 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 embodiments of the present application. The radio access network device can be used to execute the steps of the information transmission method on the radio access network device side provided in the embodiments of the present application. 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 embodiments of the present application.

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

[0047] In a twentieth aspect, a chip is provided. The chip includes a processor and a communication interface, and the communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the information transmission method on the terminal side provided in the embodiments of the present application, or to implement the information transmission method on the radio access network device side provided in the embodiments of the present application, or to implement the information transmission method on the core network function side provided in the embodiments of the present application, or to implement the capability information reporting method on the core network function side provided in the embodiments of the present application, or to implement the capability information receiving method provided in the embodiments of the present application.

[0048] In a twenty-first aspect, a computer program / program product is provided. The computer program / program product 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 provided in the embodiments 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 radio access network device side provided in the embodiments 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 provided in the embodiments 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 embodiments 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 embodiments of the present application.

[0049] In the embodiments of the present application, the terminal obtains a first configuration, where the first configuration is used to configure a dedicated bearer for information transmission, and the dedicated bearer is independent of the SRB and the DRB; the terminal transmits information through the dedicated bearer. In this way, it can be realized that the terminal can transmit information through a dedicated bearer other than the SRB and the DRB, thereby improving the transmission performance of the terminal. Description of the Drawings

[0050] Figure 1 is a block diagram of a wireless communication system to which the embodiments of the present application can be applied;

[0051] Figure 2 is a flowchart of an information transmission method provided in the embodiments of the present application;

[0052] Figure 3 is a flowchart of a method for reporting capability information provided by an embodiment of the present application;

[0053] Figure 4 is a flowchart of another information transmission method provided by an embodiment of the present application;

[0054] Figure 5 is a flowchart of a method for receiving capability information provided by an embodiment of the present application;

[0055] Figure 6 is a flowchart of another information transmission method provided by an embodiment of the present application;

[0056] Figures 7 to 9 is a schematic diagram of a protocol layer architecture provided by an embodiment of the present application;

[0057] Figure 10 is a structural diagram of an information transmission device provided by an embodiment of the present application;

[0058] Figure 11 is a structural diagram of a capability information reporting device provided by an embodiment of the present application;

[0059] Figure 12 is a structural diagram of another information transmission device provided by an embodiment of the present application;

[0060] Figure 13 is a structural diagram of a capability information receiving device provided by an embodiment of the present application;

[0061] Figure 14 is a structural diagram of another information transmission device provided by an embodiment of the present application;

[0062] Figure 15 is a structural diagram of a communication device provided by an embodiment of the present application;

[0063] Figure 16 is a structural diagram of a device provided by an embodiment of the present application;

[0064] Figure 17 is a structural diagram of a radio access network device provided by an embodiment of the present application;

[0065] Figure 18 is a structural diagram of another network-side device provided by an embodiment of the present application. Detailed implementation manners

[0066] The technical solutions in the embodiments of the present application will be clearly described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are some, but not all, of the embodiments of the present application. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in the present application belong to the scope of protection of the present application.

[0067] The terms "first", "second", etc. in the present application are used to distinguish similar objects, rather than to describe a specific order or sequence. It should be understood that such terms can be interchanged under appropriate circumstances 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 multiple. In addition, "or" in the present application means at least one of the connected objects. For example, "A or B" covers three scenarios, namely, Scenario 1: including A and not including B; Scenario 2: including B and not including A; Scenario 3: including both A and B. The character " / " generally indicates an "or" relationship between the associated objects before and after.

[0068] The term "indication" in the present application can be either a direct indication (or an explicit indication) or an indirect indication (or an implicit indication). Among them, a direct indication can be understood as that the sender clearly informs the recipient of specific information, operations to be performed, or request results, etc. in the sent indication; an indirect indication can be understood as that the recipient determines the corresponding information according to the indication sent by the sender, or makes a judgment and determines the operations to be performed or request results, etc. according to the judgment result.

[0069] It should be noted that the technology described in the embodiments of this application is not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, and 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 this application are often used interchangeably, and the described technology can be used not only in the systems and radio technologies mentioned above, but also in other systems and radio technologies. The following description describes the New Radio (NR) system for example purposes, and uses the NR term in most of the following descriptions, but these technologies can also be applied to systems other than the NR system, such as the 6th Generation (6G) communication system. th Generation, 6G) communication system.

[0070] Figure 1The block diagram of a wireless communication system to which the embodiments of the present application can be applied is shown. The wireless communication system includes a terminal 11 and a network-side device 12. Among them, the terminal 11 can be a mobile phone, a tablet personal computer, a 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, a flight vehicle, a vehicle user equipment (VUE), a shipborne device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication functions, such as refrigerators, TVs, washing machines, or furniture, etc.), a game console, a personal computer (PC), a teller machine, or a self-service machine, etc., terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart earphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart ankle chains, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle user equipment can also be referred to as a vehicle terminal, a vehicle controller, a vehicle module, a vehicle component, a vehicle chip, or a vehicle unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiments of the present application.

[0071] The network-side device 12 may include an access network device or a core network device. Among them, 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, etc. Among them, the base station may 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, transmission reception point (TRP), or some other suitable term in the art. As long as the same technical effect is achieved, the base station is not limited to a specific technical term. It should be noted that in the embodiments of the present application, only the base station in the NR system is taken as an example for introduction, and the specific type of the base station is not limited.

[0072] The core network device can also be referred to as a core network function, a core network node, or a core network function, etc. It can 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 (BSF), Application Function (AF), etc. It should be noted that in the embodiments of this application, only the core network device in the NR system is taken as an example for introduction, and the specific type of the core network device is not limited.

[0073] Next, with reference to the accompanying drawings, a method, apparatus, terminal, device, and core network function for information transmission provided by the embodiments of this application will be described in detail through some embodiments and their application scenarios.

[0074] Please refer to Figure 2 , Figure 2 which is a flowchart of a method for information transmission provided by the embodiments of this application. As Figure 2 shown, it includes the following steps:

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

[0076] Among them, obtaining the above first configuration may be that the terminal receives the first configuration sent by the network-side device, or the terminal generates the above first configuration, or the terminal receives the first configuration sent by other terminals.

[0077] 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:

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

[0079] Among them, the above AI data may include an AI model, AI model parameters, AI model training data, etc.

[0080] In some embodiments, the above information may be information that the network-side device needs to collect. For example, the network-side collects at least one of the following through configuring the dedicated bearer:

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

[0082] In the embodiments of the present application, for the information collection scenario, the above dedicated bearer may be referred to as a Collection Radio Bearer (CRB). In the embodiments of the present application, the name of the dedicated bearer is not limited.

[0083] It should be noted that in the embodiments of the present application, it is not limited that the above information is information that the network-side device needs to collect. For example, it may 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 cases, and this is not limited.

[0084] In the embodiments of the present application, the above information may also be data information.

[0085] The dedicated bearer for the above information transmission can be understood as that the above dedicated bearer is a bearer dedicated to transmitting the above information.

[0086] The above dedicated bearer being independent of the SRB and DRB can be understood as that the above dedicated bearer is neither an SRB nor a DRB, and is a newly defined bearer in the embodiments of the present application.

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

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

[0089] In the embodiments of the present application, it can be realized that the terminal can transmit information through a dedicated bearer other than the SRB and DRB, thereby improving the transmission performance of the terminal.

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

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

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

[0093] Among them, the dedicated bearer for information interaction between the terminal and the radio access network device can be understood as that the terminal transmits information to the radio access network through the dedicated bearer. For example, the two ends of the end-to-end entity of the dedicated bearer are located in 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 OAM, or is triggered by the CN node, the radio access network device establishes a dedicated bearer, which is used to transmit the configuration and reporting data related to data collection between the radio access network device and the terminal. The two ends of the end-to-end entity of the bearer are located in the radio access network device and the terminal respectively. The transmission between the radio access network device and other nodes is carried out through a dedicated data pipeline, which is the pipeline between nodes.

[0094] The dedicated bearer for information interaction between the terminal and the core network function can be understood as that the terminal transmits information to the core network function through the 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 the core network node to transmit terminal information transparent to the radio access network device, the radio access network device establishes a dedicated bearer, which is used to transmit the configuration and reporting data related to data collection for the core network function between the radio access network device and the terminal. The two ends of the end-to-end entity of the bearer can be located in the core network function and the terminal respectively; the transmission between the radio access network device and other nodes is carried out through a dedicated data pipeline established for each terminal.

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

[0096] In some implementation manners, the information interaction between the terminal and the radio access network function and the information interaction between the terminal and the core network function can be transmitted using the same dedicated bearer or different dedicated bearers, and are distinguished by the bearer identifier or the packet format.

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

[0098] 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 handover process, and the mapping relationship of the dedicated bearer.

[0099] Among them, the identifier of the above dedicated bearer is used to indicate the above dedicated bearer, such as indicating the terminal to create or use the above dedicated bearer through this identifier.

[0100] The attribute information of the above dedicated bearer is used to represent at least one belonging of the above dedicated bearer.

[0101] In some embodiments, the attribute information of the above dedicated bearer includes at least one of the following:

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

[0103] At least one protocol layer corresponding to the above dedicated bearer may be at least one protocol layer included in the protocol stack corresponding to the dedicated bearer.

[0104] The attribute information of the above protocol layer may include the configuration 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, etc. Each protocol layer can be flexibly configured through the above attribute information.

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

[0106] The transmission mode of the dedicated bearer, the maximum data length of the dedicated bearer, the reordering information of the dedicated bearer, the delivery mode 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.

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

[0108] The above RLC transmission mode may include Transparent Mode (TM), Acknowledged Mode (AM), or Unacknowledged Mode (UM).

[0109] Through the above RLC transmission mode or DAPS transmission mode, the above dedicated bearer can support more flexible transmission.

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

[0111] The reordering information of the above dedicated bearer can be reordering timing (T-reordering) information, or other reordering information, which is not limited thereto, so that the reordering of the dedicated bearer can be flexibly configured to support more flexible transmission.

[0112] The delivery mode of the above dedicated bearer can be in-sequence delivery to support more flexible transmission.

[0113] The logical channel identifier, logical channel priority, or guaranteed bit rate of the above dedicated bearer can flexibly configure the logical channel identifier, logical channel priority, or guaranteed bit rate of the dedicated bearer to support more flexible transmission.

[0114] The bearer type of the above dedicated bearer may include: 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 or Dual Connectivity (DC) duplication transmission to support more flexible transmission.

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

[0116] The security attribute information of the above dedicated bearer can indicate whether to enable the integrity protection function or whether to enable encryption and decryption, etc., to support more flexible transmission.

[0117] The segmentation attribute information of the above dedicated bearer can be additional segmentation information of the dedicated bearer, such as Sequence Number (SN) length, maximum number of segments, segmentation indication field length, tail segment mark, etc., so as to support more flexible segmented transmission.

[0118] The attribute information of the above dedicated bearer may further include bearer format information, such as the maximum packet size, the size of the Length Indicator field, the size of the Segment offset field, etc.

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

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

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

[0122] Among them, the mapping relationship between the above dedicated bearer and the protocol entity may include at least one of the following:

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

[0124] The mapping relationship between the dedicated bearer and the Service Data Adaptation Protocol for Core Network (DSAP-CN) entity.

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

[0126] The mapping relationship between the dedicated bearer and at least one type of data in the DSAP-Uu entity;

[0127] The mapping relationship between the dedicated bearer and at least one type of data in the DSAP-CN entity.

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

[0129] Through the mapping relationship of the above dedicated bearer, the data transmitted by the dedicated bearer can be flexibly configured to further improve the transmission flexibility of the dedicated bearer.

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

[0131] The routing information of the dedicated bearer; or

[0132] Packet format information, which is used to determine the routing information of the data packet of the dedicated bearer.

[0133] The routing information of the above dedicated bearer can represent the destination route of the information. For example, it enables the information (such as data collection content) to terminate at the radio access network device or at the protocol layer of the core network. For the information of dedicated bearer 1, its routing attribute is to the DSAP-Uu of the gNB, and for the data of dedicated bearer 2, its routing attribute is to the DSAP-CN of the core network. The routing information of the above dedicated bearer can also be a bearer identifier, and the routing of the dedicated bearer to different nodes is indicated through the bearer identifier.

[0134] It can be understood that the above packet format information for determining the routing information of the packets of the dedicated bearer means that the above packet format information represents the routing information corresponding to different packet formats, so that the specific information carried by the packet can indicate the routing information of the packets of the dedicated bearer, that is, the routing information is carried with the packet. For example, in a certain field in the Packetheader, 0 represents the DSAP-Uu of the radio access network, and 1 represents the DSAP-CN of the core network.

[0135] Through the above routing information or packet format information of the dedicated bearer, the routing of the above dedicated bearer can be flexibly configured to improve the flexibility of data transmission.

[0136] The processing information of the above dedicated bearer during the handover process can indicate the processing method of the above dedicated bearer during the cell handover process, such as whether service continuity is required during handover, whether the cache is cleared, whether the transmission status variable is reset, etc. Through the processing information of the dedicated bearer during the handover process, flexible transmission of information through the above dedicated bearer during the handover process can be supported.

[0137] It should be noted that in some embodiments, some of the identification of the above 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 handover process, and the mapping relationship of the dedicated bearer can also be protocol agreements to save the overhead of the first configuration.

[0138] As an alternative embodiment, the first configuration is carried in a configuration message, where:

[0139] The first configuration is carried through a first information field in the configuration message, and the first information field is an information field dedicated to the configuration of the dedicated bearer; or,

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

[0141] Among them, the above configuration message may be a Radio Resource Control (RRC) configuration or reconfiguration message.

[0142] The information field dedicated to the dedicated bearer configuration can be understood as that the above information field is only used to configure the above dedicated bearer, which is different from the information fields of SRB and DRB. For example: in the configuration message, SRB and DRB each already have their own fields for addition, modification, and release (such as srb-ToAddModList, srb3-ToRelease, drb-ToAddModList, drb-ToReleaseList), and there is an independent information field in the above configuration message. In this way, the above dedicated bearer configuration is made more flexible through the independent information field.

[0143] The above second information field, which is the configuration information field for multiple bearers, can be that the second information field is used for the configuration of the above dedicated bearer and also for the configuration of at least one of SRB or DRB. For example: the above second information field is to add some additional configuration fields for the above dedicated bearer in the bearer configuration field of the above configuration message defined in the protocol, and merge the configuration of the dedicated bearer into the configuration of one of the bearer types to reduce the complexity of the configuration message.

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

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

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

[0147] The dedicated bearer can coexist with SRB;

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

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

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

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

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

[0153] The dedicated bearer supports cell handover.

[0154] The co - existence of the above - mentioned dedicated bearer with SRB and DRB can be understood as that the terminal can simultaneously transmit these three bearers.

[0155] The parallel transmission of the above - mentioned dedicated bearer with SRB and DRB can be understood as that the terminal can perform the parallel transmission of these three bearers.

[0156] The co - existence of the above - mentioned dedicated bearer with SRB can be understood as that the terminal can simultaneously transmit these two bearers.

[0157] The parallel transmission of the above - mentioned dedicated bearer with SRB can be understood as that the terminal can perform the parallel transmission of these two bearers.

[0158] The above - mentioned target conditions can be conditions agreed upon by the protocol or configured by the network side, such as establishing the above - mentioned dedicated bearer after successful establishment of the RRC connection, activation of Uu - interface security, or obtaining the terminal - related capabilities.

[0159] The arrangement of the identifier of the above - mentioned dedicated bearer together with the identifier of SRB or DRB means that the above - mentioned dedicated bearer shares the ID space with SRB or DRB. For example, if the DRB ID space is extended to a maximum of 64, then the DRB can share these 64 ID spaces with the dedicated bearer. The separate arrangement of the identifier of the above - mentioned dedicated bearer means that the above - mentioned dedicated bearer has a separate ID space, such as stipulating an ID space of 1 - 32 specifically for the dedicated bearer, etc. In this way, the flexible configuration of the identifier of the dedicated bearer can be realized to improve the flexibility of the dedicated bearer.

[0160] The configurable attribute of the above - mentioned dedicated bearer means that the attribute of the dedicated bearer can be configured dynamically or flexibly. Specifically, the attribute of the above - mentioned dedicated bearer is dynamically or flexibly configured by the above - mentioned first configuration or other configuration information to support more flexible transmission.

[0161] In some embodiments, the attribute of the above - mentioned dedicated bearer includes at least one of the following:

[0162] The transmission configuration of the dedicated bearer, the security attribute of the dedicated bearer, the segmentation attribute of the dedicated bearer.

[0163] Among them, for the above - mentioned transmission configuration, security attribute, and segmentation attribute, refer to the attribute information of the dedicated bearer configured by the above - mentioned first configuration, which will not be elaborated here.

[0164] In this embodiment, the configurable attribute of the above - mentioned dedicated bearer can be realized to support more flexible transmission.

[0165] The above dedicated bearer corresponding to at least one QoS means that the above dedicated bearer can transmit data streams with one or more QoS attributes. For example, for 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, different data stream attributes can be explicitly carried through an additional layer to distinguish them.

[0166] The above dedicated bearer supporting cell handover can be configured flexibly in the process of cell handover, such as clearing the cache and resetting the transmission variables of the above dedicated bearer, or retaining the cache and resetting the transmission variables, or retaining the cache and transmission variables.

[0167] Since the above dedicated bearer has the above at least one characteristic, when the terminal transmits information through this dedicated bearer, it has higher flexibility and can also meet transmission requirements such as continuity requirements and transmission efficiency.

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

[0169] DSAP-CN entity;

[0170] DSAP-Uu entity.

[0171] Among them, the above DSAP-Uu entity is used to transmit information between the terminal and the radio access network device, and the above DSAP-CN entity is used to transmit information between the terminal and the core network function.

[0172] Through the above DSAP-CN entity or DSAP-Uu entity, flexible information transfer between the terminal and the network side can be achieved.

[0173] As an alternative implementation, the method further includes:

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

[0175] The above reconfiguration can be to reconfigure the dedicated bearer in the cell handover scenario, or the serving cell has not changed, and the network side device reconfigures the dedicated bearer for the terminal due to demand changes or its own algorithm requirements, etc.

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

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

[0178] In the case where there is no explicit reset or no explicit reconstruction indication for the configuration of the second configuration change, the state variables of the corresponding Packet Data Convergence Protocol (PDCP) entity and Radio Link Control (RLC) entity of the dedicated bearer are maintained; or,

[0179] In the 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,

[0180] In the case where the configuration of the second configuration change carries an explicit reset or reconstruction indication, the terminal reconstructs or resets at least one of the PDCP entity and the RLC entity corresponding to the dedicated bearer.

[0181] The above Layer 2 includes protocol layers other than the PHY layer in the L1 protocol stack, such as the MAC layer, RLC layer, PDCP layer, and SDAP layer.

[0182] The above non - impact on Layer 2 means that when changing the configuration of the dedicated bearer, it does not affect Layer 2. For example, when processing the PDCP layer or RLC layer, the PDCP layer and RLC layer can perform no operation.

[0183] The above maintenance of the state variables of the PDCP entity and the RLC entity means that for the second configuration, the PDCP entity and the RLC entity can perform no operation, so the state variables are maintained, thereby achieving continuous transmission to improve transmission performance.

[0184] The above reconstruction or reset 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.

[0185] In some embodiments, for the PDCP entity, in the case where the configuration of the second configuration change carries an explicit reset or reconstruction indication or affects Layer 2, reconstruction can be performed, and the RLC transmission mode is distinguished. The AM state variable is maintained, the UM state variable is reset, and the Service Data Unit (SDU) in the cache can continue to be retained, so as to continuously receive and send according to the new security key after re - configuration, ensuring service continuity to a certain extent.

[0186] In one embodiment, it is as follows:

[0187] The serving cell of the terminal does not change. Due to changes in requirements or its own algorithm needs, etc., the base station reconfigures the dedicated bearer of the UE to change some configurations. When the changed configuration does not affect Layer 2, such as the processing of PDCP or RLC, PDCP and RLC can do nothing, and the state variables are maintained. The data of the terminal's dedicated bearer continues to be received and sent continuously, and the service continuity is not affected at all. When the configuration change affects the Layer 2 data processing, such as when the security key needs to be updated, it may be necessary to reconstruct or reset the PDCP entity or the RLC entity. At this time, for the RLC layer, since the data it caches that has not been sent or not successfully sent is all with the old security key and cannot continue, the RLC layer generally resets the transmission variable and clears the cache. For the PDCP layer, reconstruction can be performed at this time, and the RLC transmission mode is distinguished. The AM state variable is maintained, the UM state variable is reset, and the SDUs in the cache can continue to be retained to facilitate continuous reception and transmission according to the new security key after reconfiguration, ensuring service continuity to a certain extent.

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

[0189] Reset the RLC entity corresponding to the dedicated bearer of the terminal;

[0190] The handover process of the PDCP entity corresponding to the dedicated bearer of the terminal, and the handover process includes at least one of the following:

[0191] Clear the cache and reset the transmission variable;

[0192] Retain the cache and reset the transmission variable;

[0193] Retain the cache and the transmission variable.

[0194] By resetting the RLC entity corresponding to the dedicated bearer of the terminal, it is possible to establish 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 handover.

[0195] The above handover process of the PDCP entity can retain or clear the cache, retain or reset the transmission variable, so as to achieve continuous data transmission during cell handover and improve the transmission performance.

[0196] In some embodiments, it is also possible to configure whether to delete the data of the dedicated bearer. 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.

[0197] An embodiment is as follows:

[0198] For a handover scenario, generally, the target cell gives a new configuration to the dedicated bearer and sends it to the terminal in the handover command for the terminal to use after accessing the target cell. For the dedicated bearer, the target cell can configure RLC reset, PDCP re - establishment, and optionally, can configure whether to delete the data of the dedicated bearer. RLC reset is because generally, the RLC state is not transferred between the source cell and the target cell, and a new RLC entity is established for the dedicated bearer on the target side. For PDCP re - establishment, for the PDCP entity of UM, the state variable is cleared, and for the PDCP entity of AM, the state variable is maintained. The purpose of this is to better ensure the service continuity in the AM mode. For the option of deleting the dedicated bearer data, it 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, and if it is still valid, it can be retained. The most typical data that needs to be retained is the data sent to the core network node, which will not be affected by the change of the home base station in terms of its validity.

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

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

[0201] The above - mentioned capability information of the dedicated bearer can be whether the terminal supports the above - mentioned dedicated bearer, or the specific capabilities of supporting the above - mentioned dedicated bearer.

[0202] In some implementation manners, the capability information includes at least one of the following:

[0203] Whether the terminal supports the dedicated bearer;

[0204] At least one capability of the dedicated bearer supported by the terminal;

[0205] Whether the terminal supports information collection;

[0206] At least one function of information collection supported by the terminal;

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

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

[0209] The above - mentioned at least one capability of the supported dedicated bearer means that the above - mentioned dedicated bearer has multiple capabilities, and the specific capabilities supported by the terminal are indicated through the above - mentioned capability information, such as the ability to support the interaction between the terminal and the radio access network device, the interaction between the terminal and the core network function, or the ability to transmit multiple QoS data streams, etc.

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

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

[0212] The capability range of the above at least one protocol layer means that the capability ranges of different protocol layers are different. For example, it supports at least one of the capabilities such as the PDCP layer providing header compression and decompression, security operations, split bearer routing and duplication, and supports at least one of the three modes of TM, UM, and AM provided by the RLC layer, etc.

[0213] Through the above capability information, the network side can know the corresponding capabilities of the terminal, so as to configure a dedicated bearer that matches the capabilities of the terminal, making the transmission of the dedicated bearer more reliable.

[0214] In the embodiment of the present application, the terminal obtains a first configuration, and the first configuration is used to configure a dedicated bearer for information transmission, and the dedicated bearer is independent of the SRB and DRB; the terminal transmits information through the dedicated bearer. In this way, the terminal can transmit information through a dedicated bearer other than the SRB and DRB, thereby improving the transmission performance of the terminal.

[0215] In the embodiment of the present application, the terminal is configured with a dedicated bearer for transmitting signaling, data, model information, etc. related to data collection, and uses the bearer identifier or packet format to solve the routing problem of reaching different nodes, and performs different handover processes according to the bearer characteristics to meet the continuity requirements and transmission efficiency.

[0216] Please refer to Figure 3 , Figure 3 which is a flowchart of a method for reporting capability information provided by the embodiment of the present application. As Figure 3 shown, it includes the following steps:

[0217] Step 301, the terminal reports capability information about the dedicated bearer;

[0218] Among them, the dedicated bearer is a dedicated bearer for information transmission, and the dedicated bearer is independent of the SRB and DRB.

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

[0220] Whether the terminal supports the dedicated bearer;

[0221] At least one capability of the dedicated bearer supported by the terminal;

[0222] Whether the terminal supports information collection;

[0223] At least one function of information collection supported by the terminal;

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

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

[0226] In this embodiment, since the terminal reports the capability information about the dedicated bearer, when the terminal supports the above dedicated bearer, the terminal can perform information transmission through the dedicated bearer, thereby improving the flexibility of data transmission processing.

[0227] It should be noted that this embodiment is used as the implementation manner of the terminal capability reporting corresponding to the embodiment shown in Figure 2 For the relevant description of the specific implementation manner, reference can be made to the relevant description of the embodiment shown in Figure 2 To avoid repeated description, this embodiment will not be elaborated herein.

[0228] Please refer to Figure 4 , Figure 4 is the flowchart of another information transmission method provided by the embodiment of the present application. As shown in Figure 4 , it includes the following steps:

[0229] Step 401: 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, and the dedicated bearer is independent of the signaling radio bearer SRB and the data radio bearer DRB;

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

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

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

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

[0234] Among them, the first radio access network device and the second radio access network device may be the same or different.

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

[0236] 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 handover process, and the mapping relationship of the dedicated bearer.

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

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

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

[0240] 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 mode of the dedicated bearer, the logical channel identifier of the dedicated bearer, the logical channel priority of the dedicated bearer, the guaranteed bit rate of the dedicated bearer.

[0241] Optionally, the bearer type of the dedicated bearer includes: a split bearer; or,

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

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

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

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

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

[0247] The routing information of the dedicated bearer; or

[0248] Packet format information, which is used to determine the routing information of the packets of the dedicated bearer.

[0249] Optionally, the first configuration is carried in a configuration message, where:

[0250] The first configuration is carried by a first information field in the configuration message, and the first information field is an information field dedicated to the configuration of the dedicated bearer; or,

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

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

[0253] The dedicated bearer can coexist with the signaling radio bearer (SRB) and the data radio bearer (DRB) simultaneously;

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

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

[0256] 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 separately;

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

[0258] The dedicated bearer corresponds to at least one quality of service (QoS);

[0259] The dedicated bearer supports cell handover.

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

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

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

[0263] The service data adaptation protocol (DSAP)-Uu entity;

[0264] The service data adaptation protocol for the Ng interface (DSAP-Ng) entity, which is used for the interaction between the first radio access network device and the core network function;

[0265] The service data adaptation protocol for the Xn interface (DSAP-Xn) entity, which is used for the interaction between the first radio access network device and other radio access network devices.

[0266] Optionally, the method further includes:

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

[0268] 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 Link Control (RLC) entity corresponding to the dedicated bearer are maintained; or,

[0269] When the configuration of the second configuration change has no explicit reset or no explicit reconstruction indication, the state variables of the PDCP entity and the RLC entity corresponding to the dedicated bearer are maintained; or,

[0270] When the configuration of the second configuration change affects Layer 2, the first radio access network device reconstructs or resets at least one of the PDCP entity and the RLC entity corresponding to the dedicated bearer; or,

[0271] When the configuration of the second configuration change carries an explicit reset or reconstruction indication, the first radio access network device reconstructs or resets at least one of the PDCP entity and the RLC entity corresponding to the dedicated bearer.

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

[0273] Reset the RLC entity corresponding to the dedicated bearer of the terminal;

[0274] The handover process of the PDCP entity corresponding to the dedicated bearer of the terminal, and the handover process includes at least one of the following:

[0275] Clear the cache and reset the transmission variable;

[0276] Retain the cache and reset the transmission variable;

[0277] Retain the cache and the transmission variable.

[0278] Optionally, the method further includes:

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

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

[0281] Whether the terminal supports the dedicated bearer;

[0282] At least one capability of the dedicated bearer supported by the terminal;

[0283] Whether the terminal supports information collection;

[0284] At least one function of the information collection supported by the terminal;

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

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

[0287] Optionally, the first radio access network device sends the first configuration to the terminal, including at least one of the following:

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

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

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

[0291] Among them, the above trigger can be triggered based on the requirements of the radio access network device, the core network or other radio access network devices.

[0292] In this embodiment, it is possible to support multiple ways to trigger the establishment of the above dedicated bearer to meet more transmission requirements.

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

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

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

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

[0297] It should be noted that this embodiment is used as an implementation manner of the network-side device corresponding to the embodiment shown in Figure 2 For the specific implementation manner, reference can be made to the relevant description of the embodiment shown in Figure 2 To avoid repeated description, this embodiment will not be elaborated here.

[0298] Please refer to Figure 5 , Figure 5It is a flowchart of a method for receiving capability information provided by an embodiment of the present application. As Figure 5 shown, it includes the following steps:

[0299] Step 501, the radio access network device receives the capability information of the terminal reported by the terminal regarding the dedicated bearer;

[0300] Among them, the dedicated bearer is a dedicated bearer for information transmission, and the dedicated bearer is independent of the SRB and DRB.

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

[0302] Whether the terminal supports the dedicated bearer;

[0303] At least one capability of the dedicated bearer supported by the terminal;

[0304] Whether the terminal supports information collection;

[0305] At least one function of the information collection supported by the terminal;

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

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

[0308] It should be noted that, as an implementation manner of the radio access network device corresponding to the embodiments shown in Figure 2 and Figure 3 , the specific implementation manner can refer to the relevant descriptions of the embodiments shown in Figure 2 and Figure 3 . To avoid repeated description, this embodiment will not be elaborated here.

[0309] Please refer to Figure 6 , Figure 6 It is a flowchart of another information transmission method provided by an embodiment of the present application. As Figure 6 shown, it includes the following steps:

[0310] Step 601, the core network function sends a trigger message for triggering information transmission to the radio access network device;

[0311] Step 602, the core network function receives the information sent by the radio access network device or the control node;

[0312] Among them, the information is the information transmitted by the terminal through the dedicated bearer; or, the information is the information generated based on the information transmitted by the terminal through the 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.

[0313] Among them, the above wireless access network device may be the first wireless access network device or the second wireless access network device in the above embodiments.

[0314] Optionally, the control node includes:

[0315] A control plane control node, or a user plane control node.

[0316] Among them, the information received by the core network function from the control node may be that the wireless access network device makes the information transmitted by the terminal through the above dedicated bearer transparent, such as in a per UE (per User Equipment) control plane (Control Plane, CP) manner or a per UE user plane (User Plane, UP) manner. In the former case, it is transmitted through a per UE signaling pipeline from the wireless access network device to the core network control network element, and in the latter case, it is transmitted through a per UE data pipeline from the wireless access network device to the core network user plane network element, and then transmitted to the corresponding server.

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

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

[0319] It should be noted that, as an implementation manner corresponding to the core network function in the embodiments shown in Figure 2 and Figure 4 The specific implementation manner can refer to the relevant descriptions of the embodiments shown in Figure 2 and Figure 4 To avoid repeated description, this embodiment will not be elaborated here.

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

[0321] Embodiment 1:

[0322] This embodiment mainly describes the overall architecture of data collection. In this embodiment, basic architectures and solution descriptions are given for various possible scenarios of data collection to fully prove the feasibility of this case. It may include the following three situations:

[0323] Scenario (1): The simplest type of data collection is triggered by the base station itself. For example, when the base station needs to obtain some link quality, transmission effects, or even the effects of algorithm control, transmit AI models / parameters, and sense data of the Uu interface, it is necessary to configure data collection and report the results with the UE. This process is directly completed between the base station and the UE, and the protocol layer for processing these data collection configurations and results can be exemplified by a new layer, DSAP-Uu.

[0324] As Figure 7 shown in the figure, (a) is an architectural diagram of DSAP-Uu in the air interface with the possible 6G air interface protocol stack as an example, and (b) is a transmission architectural diagram of DSAP-Uu in the air interface with the 5G air interface protocol stack as an example. Of course, the 6G protocol stack is only for illustrative purposes because 6G may re-design / merge / split the protocol stack, and it is not excluded that 6G continues to use the L2 protocol composed of three sub-layers, PDCP, RLC, and MAC, similar to 5G.

[0325] Figure 7 The shown architectural example can well configure data collection and report the results between the gNB and the UE, and end-to-end at the base station. The base station is responsible for the data collection process. Of course, the base station can trigger the data collection and configuration process based on its own needs. More commonly, the OAM triggers the base station to perform relevant data collection. For example, the OAM gives the data collection requirements to the base station. The base station selects appropriate UEs according to the algorithm and configures data collection for each selected UE, and receives the reports of the data collection results from each selected UE. Both the configuration and reporting processes are carried out using the above one-to-one dedicated bearer protocol stack. Of course, after the base station collects the results of all UEs, it can also summarize or even statistically operate on the UE results and finally return the statistical results to the OAM.

[0326] Scenario (2): Another type of data collection is directly triggered by a dedicated node in the core network. For example, when the data collection center in the core network needs to obtain some UE data, it can directly configure data collection with the UE and receive the results. This process is directly end-to-end between the UE and the data collection center in the core network. The base station participates in the transmission but only acts as a transparent transmission and cannot parse or modify the data. And the protocol layer for processing these data collection configurations and results can be exemplified by a new layer, DSAP-CN.

[0327] As Figure 8 shown in the figure, both examples show the protocol stack with the L2 defined by the protocol including three sub-layers, PDCP / RLC / MAC, for the convenience of explanation. When 6G develops a new L2 protocol stack name and division, it can directly replace Figure 8The sublayers therein do not affect the transmission and implementation effects. The subsequent protocol stack examples are also illustrated with existing sublayers as examples and can be replaced by the new 6G protocol stack by the same token. (c) is an architecture diagram in which the core network protocol stack is directly carried and transmitted through the air interface, while (d) is an architecture diagram in which the core network protocol stack is transmitted after being encapsulated by the corresponding protocol stack of the air interface. The advantage of (c) is simplicity and directness. The core network data collection requirements have their own dedicated pipelines for carrying, which facilitates the configuration and control of transmission parameters. Although (d) adds a layer of encapsulation mechanism and increases the processing steps of core network data collection to a certain extent, its advantage is that it can multiplex and transmit the data collection data packets for other purposes, which is convenient for centralized management and control, saves the overhead of the air interface bearer, and improves efficiency.

[0328] Figure 8 The architecture example shown can well perform the configuration and result reporting of data collection between the core network data collection node and the UE, and end-to-end at the core network data collection node. The base station assists in its transmission but is transparent throughout the process, better protecting data and user privacy. Among them, the transmission between the gNB and the core network data collection node can have different methods. For example, the gNB first reaches the core network control node (such as the AMF node similar to the 5G system) through the CP method, and then the control node transfers it to the corresponding data collection center. Or the gNB first reaches the core network user plane control node (such as the UPF node similar to the 5G system) through the UP method, and then the user plane control node transfers it to the corresponding data collection center. Or it is addressed to the corresponding data collection center in the core network in a bus manner.

[0329] Case (3), Another type of data collection is triggered by a dedicated node in the core network, other nodes in the RAN, or even non-3GPP. For example, if the core network data collection center needs to obtain some data, it can request data from the base station. The base station selects a suitable UE according to the algorithm and performs data collection configuration and result reception through the Uu interface process. After that, the base station processes the UE data results to form the processed data collection results and reports them to the core network data collection center. This process is carried out hop by hop by the core network data collection center, the base station, and the UE. The base station participates in it, not just transparent transmission, but also parses and modifies the requirements and results. The protocol layer for processing these data collection configurations and results between the core network data collection center and the base station can be exemplified by a new layer DSAP-NG. Similarly, there can also be a protocol layer dedicated to processing data collection configurations and results between base stations, such as DSAP-Xn. If it is other third-party or non-3GPP nodes, the protocol layer is based on the implementation.

[0330] Such as Figure 9As shown, the protocol stack example is also illustrated with existing sub-layers and can be replaced by the new 6G protocol stack by the same token. (e) is a case where the core network node interacts with the base station for data collection, and then the base station configures and reports the Uu interface data collection, while (f) is a case where other RAN nodes interact with the base station for data collection, and then the base station configures and reports the Uu interface data collection. Generally speaking, the core network data collection node or other RAN nodes can first put forward the requirement for receipt collection to the base station. The base station node converts the requirement into a separate data collection configuration for each selected UE and receives its report. After summarizing and processing the reported data of the UE, the base station node feeds back to the original requirement node.

[0331] Figure 9 The architecture example shown can well perform the configuration of data collection and result reporting, and each level participates in processing and analyzing the requirements and data. For example, the requirement node can request sensing data from a certain base station without specifying any UE. After receiving the requirement, the base station selects appropriate UEs according to the need, sends a sensing data collection request to them, collects the UE data, and processes the data of all UEs, such as hiding the identity and privacy information of the UEs, and reports the statistically processed result to the requirement node. Among them, the transmission between the gNB and the core network data collection node can have different methods. For example, the gNB first reaches the core network control node (such as the AMF node similar to the 5G system) through a CP-like method, and then the control node transfers it to the corresponding data collection center. Or the gNB first reaches the core network user plane control node (such as the UPF node similar to the 5G system) through a UP-like method, and then the user plane control node transfers it to the corresponding data collection center. Or in the core network, it is addressed to the corresponding data collection center in a bus manner. If it is within the RAN node, it is generally transmitted through the node interface.

[0332] Embodiment 2:

[0333] In this embodiment, the bearer management process related to data collection is mainly described.

[0334] Since there are only two types of bearers, SRB and DRB, in the existing Uu interface, SRB has default special attributes, such as the highest priority, infinite guaranteed bit rate, default encryption and integrity protection functions enabled, clearing the corresponding cache and transmission variables during handover, etc. This is not conducive to large-scale data collection and processing, with low efficiency and the disruption of the transmission of other normal data. For DRB, since it requires a complete core network control node, such as the interaction of data flow attributes between AMF and gNB before establishment, and the DRB data flow requires a corresponding channel between gNB and the core network user plane entity such as UPF, as well as a standardized data path conversion process during handover, DRB is only suitable for data collection processes similar to UP transmission by the core network node through UPF, and its adaptability is severely limited.

[0335] Therefore, it is necessary to design a new type of bearer (i.e., dedicated bearer). On the one hand, it overcomes the above disadvantages. On the other hand, it is compatible with more future scenarios of data collection as much as possible to achieve a unified solution. The new type of bearer needs a name different from SRB and DRB, such as CRB, etc. In short, a special name is needed for distinction. In the embodiments of this application, there is no limitation. For the convenience of description, CRB is taken as an example for illustration.

[0336] The new type of bearer (such as CRB) is dedicated to data collection-related control and information transmission, and its features include at least one of the following:

[0337] The new type of bearer and the traditional SRB and DRB can coexist and be transmitted in parallel. In the bearers of a UE, SRB and CRB can coexist / transmit together, or SRB, DRB, and CRB can coexist / transmit together;

[0338] The establishment of CRB can be based on certain conditions, such as successful establishment of RRC connection, activation of Uu interface security, or acquisition of UE-related capabilities, etc.;

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

[0340] All CRB-related transmission attributes can be configured. For example, the SN length in L2, the length of the Length Indicator (LI) field, the length of the Segment Offset (SO) field, whether to deliver in order, the length of the T-Reordering timer, RLC AM / UM operations, logical channel priority, guaranteed bit rate, etc.;

[0341] CRB-related security attributes can also be configured. For example, whether to perform radio interface encryption, whether to perform radio interface integrity protection, etc.;

[0342] The CRB segmentation attributes, namely parameters. For example, currently, whether it is an SRB or a DRB, the maximum packet size is 9000 bytes. However, for data collection or model transmission, it is very likely to exceed this upper limit. Therefore, special segmentation operations need to be considered;

[0343] For different QoS attributes of CRB, on the same CRB, it is possible to multiplex multiple data collection data streams. If each stream has different QoS attributes, then additional layers may be required to explicitly carry and distinguish different data stream attributes;

[0344] The different treatments of CRB during handover generally fall into three types. The first is to clear the cache and reset the transmission variables, which provides no guarantee of service continuity, and the data collection process is restarted in the target cell. The second is to retain the unsent or unacknowledged cache and reset the transmission variables, which to a certain extent allows the unfinished data collection process to continue in the target cell. The third is to retain the cache and the transmission variables, which well realizes service continuity, without wasting resources repeatedly in the target cell and enabling continuous sequencing.

[0345] For the new bearer type (such as CRB), it can be a mandatory supported feature and capability of 6G UE. On the other hand, since CRB is not a necessary requirement for UE communication like traditional SRB and DRB, the data collection function can be an additional or auxiliary function of the UE. Therefore, the new bearer type CRB can also be an optional capability. Thus, 6G UE can report capabilities for CRB, including at least one of the following:

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

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

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

[0349] For the CRBs supported by the UE, the optional capability range of each layer configuration;

[0350] If the new bearer type CRB is an optional 6G UE capability, after the UE reports the relevant capabilities, the network side can configure an appropriate CRB for the UE according to the capabilities and requirements, so as to bear different data collection requirements. The network side configures the CRB for the UE, which mainly includes at least one of the following:

[0351] Use an independent domain to perform CRB addition, modification, and release. Since the SRB and DRB already have their own domains for addition, modification, and release (such as srb-ToAddModList, srb3-ToRelease, drb-ToAddModList, drb-ToReleaseList), as a bearer type different from the SRB and DRB, the CRB needs to be independently controlled and operated with a separate domain such as crb-ToAddModList, crb-ToReleaseList; or, it is not excluded that some additional configuration domains for the CRB are added to the existing bearer configuration domain, and the configuration of the CRB is merged into the configuration of one of the bearer types;

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

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

[0354] The CRB can also be configured for DAPS mode transmission and configured most flexibly;

[0355] In particular, the mapping relationship can also be configured, that is, for each CRB, configure which data collection content is mapped to the CRB for transmission. For the CRB, since the data flow of the CRB is different from that of the SRB and DRB, the traditional protocol regulations or the method of configuring QoS flows cannot be directly applied, so new mapping rules are defined, such as a CRB corresponding to a DSAP-Uu or DSAP-CN entity, or a CRB corresponding to a certain application or a certain type of data in a DSAP-Uu / DSAP-CN;

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

[0357] For another example, a CRB bearer can correspond to a DSAP-Uu entity 3, which is used for the control and / or collection of sensed data, while another CRB bearer can correspond to another DSAP-Uu entity 4, which is used for the control and / or transfer of an AI model;

[0358] For another example, a CRB bearer can correspond to a DSAP-Uu entity 5, which is used for the control and / or collection of sensed data between the UE and the base station, while another CRB bearer can correspond to another DSAP-CN entity 1, which is used for the control and / or collection of sensed data between the UE and the core network node;

[0359] For another example, a DSAP-Uu entity 6 can correspond to three CRB bearers at the same time. Among them, the control and / or collection of sensed 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 sensed data between the UE of the DSAP-CN entity 2 embedded in the DSAP-Uu entity 6 and the core network function corresponds to CRB3;

[0360] When the CRB and the DSAP-Uu or DSAP-CN entity are in a one-to-one correspondence, the mapping relationship only needs to associate the two;

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

[0362] After the base station completes the CRB bearer configuration for the UE, the UE and the network can use the CRB to transmit data collection-related control and information. If the mapping relationship has been configured between one or more CRB bearers and a DSAP-Uu / DSAP-CN entity, the data carried by the CRB bearers within this scope can be naturally transferred to the corresponding DSAP-Uu entity for processing, or transmitted through the pipeline between the gNB and the core network node to the corresponding DSAP-CN entity. However, if the data in a CRB bearer can have multiple different routes, it is also necessary to carry the necessary differentiation 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:

[0363] When the data packets of DSAP-Uu and DSAP-CN are multiplexed in a CRB bearer, data encapsulation can be used for differentiation. For example, the data packet of DSAP-CN is carried in a DSAP-Uu data packet in the form of a container. Then, the data packet received from this CRB will first be sent to the DSAP-Uu entity for processing. According to the parsing method of the DSAP-Uu data packet, if it is found to be a packet of this layer, it will be processed by itself. If it is found to be a DSAP-CN container data packet, it will be taken out and delivered to the corresponding DSAP-CN entity through the pipeline between the corresponding gNB and the core network function;

[0364] When multiple DSAP-CN data packets are multiplexed in a CRB bearer, it is necessary to differentiate each DSAP-CN data packet. For example, an explicit identifier is carried in the data packet to be able to distinguish different DSAP-CN entities. Additionally, further, this differentiation process 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.;

[0365] When the data packet of DSAP-Uu and multiple DSAP-CN data packets are multiplexed in a CRB bearer, in addition to the need to encapsulate the DSAP-CN data packets, additional destination entity differentiation or data stream differentiation is also required, and explicit markers can be carried;

[0366] After completing all configuration methods, the UE and the network can make good use of the CRB bearer for data collection-related transmission and routing, providing flexible configuration and management according to different data requirements, ensuring both the transmission experience and improving system efficiency.

[0367] The method provided by the embodiments of this application enables the base station to process bearer establishment and handover on demand, ensuring the transmission efficiency of UE data collection, reducing the complexity of the UE and improving the system efficiency on the basis of ensuring the data collection effect.

[0368] It should be noted that the embodiments of this application can be applied to 5G or 6G, etc., and are not limited to Uu. It can be extended to other different versions, and specific limitations are not made.

[0369] For the information transmission method provided by the embodiments of this application, the execution subject can be an information transmission device. In the embodiments of this application, taking the information transmission device executing the information transmission method as an example, the information transmission device provided by the embodiments of this application is described.

[0370] For the capability information reporting method provided by the embodiments of this application, the execution subject can be a capability information reporting device. In the embodiments of this application, taking the capability information reporting device executing the capability information reporting method as an example, the capability information reporting device provided by the embodiments of this application is described.

[0371] For the capability information receiving method provided by the embodiments of this application, the execution subject can be a capability information receiving device. In the embodiments of this application, taking the capability information receiving device executing the capability information receiving method as an example, the capability information receiving device provided by the embodiments of this application is described.

[0372] Please refer to Figure 10 , Figure 10 which is a structural diagram of an information transmission device provided by the embodiments of this application. As Figure 10 shown, the information transmission device 1000 includes:

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

[0374] A transmission module 1002, configured to transmit information through the dedicated bearer.

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

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

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

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

[0379] 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 handover process, and the mapping relationship of the dedicated bearer.

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

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

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

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

[0384] Optionally, the bearer type of the dedicated bearer includes: a split bearer; or,

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

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

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

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

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

[0390] The routing information of the dedicated bearer; or

[0391] Packet format information, which is used to determine the routing information of the packets of the dedicated bearer.

[0392] Optionally, the first configuration is carried in a configuration message, where:

[0393] The first configuration is carried by a first information field in the configuration message, and the first information field is an information field dedicated to the configuration of the dedicated bearer; or,

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

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

[0396] The dedicated bearer can coexist with SRBs and DRBs;

[0397] The dedicated bearer can be transmitted in parallel with SRBs and DRBs;

[0398] The dedicated bearer can coexist with SRBs;

[0399] The dedicated bearer can be transmitted in parallel with SRBs;

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

[0401] 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 separately;

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

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

[0404] The dedicated bearer supports cell handover.

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

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

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

[0408] Service Data Adaptation Protocol (DSAP) - Core Network (CN) entity;

[0409] DSAP - Uu entity.

[0410] Optionally, the device further includes:

[0411] A receiving module, configured to receive a second configuration sent by a network - side device, where the second configuration is used to re - configure the dedicated bearer.

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

[0413] When the configuration change of the second configuration has no explicit reset or no explicit reconstruction indication, the state variables of the Packet Data Convergence Protocol (PDCP) entity and the Radio Link Control (RLC) entity corresponding to the dedicated bearer are maintained; or,

[0414] In the case where the configuration change of the second configuration 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,

[0415] In the case where the configuration of the second configuration change carries an explicit reset or reconstruction indication, the terminal reconstructs or resets at least one of the PDCP entity and the RLC entity corresponding to the dedicated bearer.

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

[0417] Reset the RLC entity corresponding to the dedicated bearer of the terminal;

[0418] The handover process of the PDCP entity corresponding to the dedicated bearer of the terminal, and the handover process includes at least one of the following:

[0419] Clear the cache and reset the transmission variable;

[0420] Retain the cache and reset the transmission variable;

[0421] Retain the cache and the transmission variable.

[0422] Optionally, the device further includes:

[0423] A reporting module, configured to report capability information about the dedicated bearer.

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

[0425] Whether the terminal supports the dedicated bearer;

[0426] At least one capability of the dedicated bearer supported by the terminal;

[0427] Whether the terminal supports information collection;

[0428] At least one function of the information collection supported by the terminal;

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

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

[0431] The above information transmission device can improve the transmission performance of the terminal.

[0432] 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 a chip. For example, the electronic device may be a terminal or other devices other than the terminal. Exemplarily, 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 a server, a Network Attached Storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0433] The information transmission device provided by the embodiments of the present application can implement Figure 2 each process implemented by the method embodiments shown and achieve the same technical effects. To avoid repetition, details are not described herein again.

[0434] Please refer to Figure 11 , Figure 11 which is a structural diagram of a capability information reporting device provided by the embodiments of the present application. As Figure 11 shown, the capability information reporting device 1100 includes:

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

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

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

[0438] Whether the terminal supports the dedicated bearer;

[0439] At least one capability of the dedicated bearer supported by the terminal;

[0440] Whether the terminal supports information collection;

[0441] At least one function of the information collection supported by the terminal;

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

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

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

[0445] 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 a chip. For example, the electronic device may be a terminal or other devices other than terminals. Exemplarily, 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.

[0446] The capability information reporting device provided in the embodiments of the present application can implement Figure 8 each process implemented by the method embodiments shown, and achieve the same technical effects. To avoid repetition, details are not described herein again.

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

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

[0449] A first receiving module 1202, configured to receive information transmitted by the terminal through the dedicated bearer.

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

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

[0452] Information interaction between the terminal and core network functions.

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

[0454] An identifier of the dedicated bearer, attribute information of the dedicated bearer, routing-related information of the dedicated bearer, processing information of the dedicated bearer during a handover process, and a mapping relationship of the dedicated bearer.

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

[0456] 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 a bearer type of the dedicated bearer.

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

[0458] 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 mode 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.

[0459] Optionally, the bearer type of the dedicated bearer includes: a split bearer; or,

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

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

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

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

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

[0465] The routing information of the dedicated bearer; or

[0466] Packet format information, which is used to determine the routing information of the packets of the dedicated bearer.

[0467] Optionally, the first configuration is carried in a configuration message, where:

[0468] The first configuration is carried through a first information field in the configuration message, and the first information field is an information field dedicated to the configuration of the dedicated bearer; or,

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

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

[0471] The dedicated bearer can coexist with a signaling radio bearer (SRB) and a data radio bearer (DRB);

[0472] The dedicated bearer can transmit in parallel with the SRB and the DRB;

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

[0474] 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;

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

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

[0477] The dedicated bearer supports cell handover.

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

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

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

[0481] Service Data Adaptation Protocol (DSAP)-Uu entity;

[0482] DSAP-Ng entity, which is used for the interaction between the first radio access network device and the core network function;

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

[0484] Optionally, the device further includes:

[0485] A second sending module, configured to send a second configuration to the terminal, where the second configuration is used to reconfigure the dedicated bearer.

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

[0487] When the configuration change of the second configuration has no explicit reset or no explicit reconstruction indication, the state variables of the PDCP entity and the RLC entity corresponding to the dedicated bearer are maintained; or,

[0488] When the configuration change of the second configuration affects layer 2, the radio access network device reconstructs or resets at least one of the PDCP entity and the RLC entity corresponding to the dedicated bearer; or,

[0489] In the case that the configuration of the second configuration change carries an explicit reset or reconstruction indication, the radio access network device reconstructs or resets at least one of the PDCP entity and the RLC entity corresponding to the dedicated bearer.

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

[0491] Reset the RLC entity corresponding to the dedicated bearer of the terminal;

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

[0493] Clear the cache and reset the transmission variable;

[0494] Retain the cache and reset the transmission variable;

[0495] Retain the cache and the transmission variable.

[0496] Optionally, the device further includes:

[0497] A second receiving module, configured to receive the capability information of the terminal regarding the dedicated bearer reported by the terminal.

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

[0499] Whether the terminal supports the dedicated bearer;

[0500] At least one capability of the dedicated bearer supported by the terminal;

[0501] Whether the terminal supports information collection;

[0502] At least one function of the information collection supported by the terminal;

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

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

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

[0506] In the case that the radio access network device triggers information transmission, send the first configuration to the terminal;

[0507] In the case that the radio access network device receives a first trigger message sent by the core network for triggering information transmission, send the first configuration to the terminal;

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

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

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

[0511] A fourth sending module, configured to process the information for the core network and send the processed information to the core network.

[0512] The above information transmission device can improve the transmission performance of the terminal.

[0513] The information transmission device in the embodiments of the present application 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 a chip. The electronic device may be a terminal or a network-side device.

[0514] The information transmission device provided in the embodiments of the present application can implement Figure 4 each process implemented by the method embodiments shown, and achieve the same technical effects. To avoid repetition, details are not described here again.

[0515] Please refer to Figure 13 , Figure 13 which is a structural diagram of a capability information receiving device provided in the embodiments of the present application. As Figure 13 shown, the capability information receiving device 1300 includes:

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

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

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

[0519] whether the terminal supports the dedicated bearer;

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

[0521] whether the terminal supports information collection;

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

[0523] the maximum number of the dedicated bearers supported by the terminal.

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

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

[0526] The capability information receiving device in the embodiments of the present application 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 a chip. The electronic device may be a terminal or a network-side device.

[0527] The capability information receiving device provided by the embodiments of the present application can achieve Figure 5 Each process implemented by the method embodiments shown, and achieve the same technical effects. To avoid repetition, it will not be elaborated here.

[0528] Please refer to Figure 14 , Figure 14 It is a structural diagram of another information transmission device provided by the embodiments of the present application. As Figure 14 shown, the information transmission device 1400 includes:

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

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

[0531] 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 a signaling radio bearer SRB and a data radio bearer DRB.

[0532] Optionally, the control node includes:

[0533] A control plane control node, or a user plane control node.

[0534] 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,

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

[0536] The above information transmission device can improve the transmission performance of the terminal.

[0537] The information transmission device in the embodiments of the present application 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 a chip. The electronic device may be a terminal or a network-side device.

[0538] The information transmission device provided in the embodiments of the present application can implement Figure 9 each process implemented by the method embodiments shown and achieve the same technical effects. To avoid repetition, details are not described herein again.

[0539] Optionally, as Figure 15 shown, the embodiments of the present application further provide a communication device 1500, including a processor 1501 and a memory 1502. A program or instruction that can run on the processor 1501 is stored on the memory 1502. For example, when the communication device 1500 is a terminal, when the program or instruction is executed by the processor 1501, each step of the information transmission method embodiment on the terminal side is implemented and the same technical effects can be achieved. When the communication device 1500 is a radio access network device, when the program or instruction is executed by the processor 1501, each step of the information transmission method embodiment on the radio access network device side is implemented and the same technical effects can be achieved. When the communication device 1500 is a core network function, when the program or instruction is executed by the processor 1501, each step of the information transmission method embodiment on the core network function side is implemented and the same technical effects can be achieved. To avoid repetition, details are not described herein again.

[0540] The embodiments of the present application further provide a communication device, including a processor and a communication interface. The communication interface is used to obtain a first configuration, and the first configuration is used to configure a dedicated bearer for information transmission, and the dedicated bearer is independent of the SRB and the DRB; a transmission module is used to transmit information through the dedicated bearer. This communication device embodiment corresponds to the above-mentioned perception measurement result processing method embodiment. Each implementation process and implementation manner of the above method embodiment can be applied to this communication device embodiment, and the same technical effects can be achieved.

[0541] The embodiments of the present application further provide a communication device, including a processor and a communication interface. The communication interface is used to report capability information about a dedicated bearer; the dedicated bearer is a dedicated bearer for information transmission, and the dedicated bearer is independent of the SRB and the DRB. This communication device embodiment corresponds to the above-mentioned capability information reporting method embodiment. Each implementation process and implementation manner of the above method embodiment can be applied to this communication device embodiment, and the same technical effects can be achieved.

[0542] Specifically, Figure 16 is a schematic diagram of the hardware structure of a terminal for implementing the embodiments of the present application.

[0543] The terminal 1600 includes, but is not limited to, at least some components such as 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 a processor 1610.

[0544] Those skilled in the art can understand that the terminal 1600 may further include a power supply (such as a battery) for supplying power to each component. The power supply can be logically connected to the processor 1610 through a power management system, so as to implement functions such as management of charging, discharging, and power consumption management through the power management system. Figure 16 The terminal structure shown does not limit the terminal. The terminal may include more or fewer components than shown in the figure, or combine some components, or have different component arrangements, which will not be elaborated here.

[0545] It should be understood that in the embodiments of the present application, the input unit 1604 may include a graphics processing unit (GPU) 16041 and a microphone 16042. 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 at least one of a touch panel 16071 and 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. The 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 a joystick, which will not be elaborated here.

[0546] In the embodiments of the present application, after receiving downlink data from a network-side terminal, the radio frequency unit 1601 can transmit it to the processor 1610 for processing; in addition, the radio frequency unit 1601 can send uplink data to the network-side terminal. Generally, the radio frequency unit 1601 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

[0547] 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. Among them, the first storage area may store an operating system, application programs 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 a volatile and a 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. The volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (Synchronous DRAM, SDRAM), a double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDR SDRAM), an enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), a synchronous link dynamic random access memory (Synch link DRAM, SLDRAM), and a direct rambus random access memory (Direct Rambus RAM, DRRAM). The memory 1609 in the embodiments of the present application includes but is not limited to these and any other suitable types of memories.

[0548] The processor 1610 may include one or more processing units; optionally, the processor 1610 integrates an application processor and a modem processor. Among them, the application processor mainly processes operations related to the operating system, user interface, and application programs, etc., and the modem processor mainly processes wireless communication signals, such as a baseband processor. It can be understood that the above modem processor may not be integrated into the processor 1610 either.

[0549] In one embodiment:

[0550] 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, and the dedicated bearer is independent of the signaling radio bearer SRB and the data radio bearer DRB; information is transmitted through the dedicated bearer.

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

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

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

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

[0555] 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 handover, the mapping relationship of the dedicated bearer.

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

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

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

[0559] 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, the guaranteed bit rate of the dedicated bearer.

[0560] Optionally, the bearer type of the dedicated bearer includes: a split bearer; or,

[0561] The transmission mode of the dedicated bearer includes at least one of the following: radio link control (RLC) transmission mode, dual active protocol stack (DAPS) transmission mode.

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

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

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

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

[0566] The routing information of the dedicated bearer; or

[0567] Packet format information, which is used to determine the routing information of the packets of the dedicated bearer.

[0568] Optionally, the first configuration is carried in a configuration message, where:

[0569] the first configuration is carried by a first information field in the configuration message, and the first information field is an information field dedicated to the dedicated bearer configuration; or,

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

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

[0572] the dedicated bearer can coexist with the SRB and the DRB;

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

[0574] the dedicated bearer can coexist with the SRB;

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

[0576] the dedicated bearer is established under target conditions;

[0577] 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 separately;

[0578] the attributes of the dedicated bearer are configurable;

[0579] the dedicated bearer corresponds to at least one quality of service QoS;

[0580] the dedicated bearer supports cell handover.

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

[0582] the transmission configuration of the dedicated bearer, the security attributes of the dedicated bearer, the segmentation attributes of the dedicated bearer.

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

[0584] service data adaptation protocol DSAP - core network CN entity;

[0585] DSAP - Uu entity.

[0586] Optionally, the radio frequency unit 1601 is further configured to receive a second configuration sent by a network - side device, and the second configuration is used to re - configure the dedicated bearer.

[0587] 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 Link Control (RLC) entity corresponding to the dedicated bearer are maintained; or,

[0588] When the configuration of the second configuration change has no explicit reset or no explicit re-establishment indication, the state variables of the PDCP entity and the RLC entity corresponding to the dedicated bearer are maintained; or,

[0589] When 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,

[0590] When 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.

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

[0592] Reset the RLC entity corresponding to the dedicated bearer of the terminal;

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

[0594] Clear the cache and reset the transmission variable;

[0595] Retain the cache and reset the transmission variable;

[0596] Retain the cache and the transmission variable.

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

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

[0599] Whether the terminal supports the dedicated bearer;

[0600] At least one capability of the dedicated bearer supported by the terminal;

[0601] Whether the terminal supports information collection;

[0602] At least one function of the information collection supported by the terminal;

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

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

[0605] In another embodiment:

[0606] A radio frequency unit 1601, configured 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 the SRB and the DRB.

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

[0608] Whether the terminal supports the dedicated bearer;

[0609] At least one capability of the dedicated bearer supported by the terminal;

[0610] Whether the terminal supports information collection;

[0611] At least one function of the information collection supported by the terminal;

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

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

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

[0615] It can be understood that the implementation processes of the implementation manners mentioned in this embodiment can refer to the relevant descriptions of the above method for sending perception measurement results, and achieve the same or corresponding technical effects. To avoid repetition, they will not be elaborated here.

[0616] This application embodiment also provides a device, including a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction to implement as Figure 4 or Figure 5 shown in the steps of the method embodiment. This device embodiment corresponds to the above method embodiment for sending perception measurement results. Each implementation process and implementation manner of the above method embodiment can be applied to this device embodiment, and the same technical effects can be achieved.

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

[0618] An embodiment of the present application further provides a device, including a processor and a communication interface. The communication interface is configured to receive the capability information of the terminal reported by the terminal regarding a dedicated bearer. The dedicated bearer is a dedicated bearer for information transmission and is independent of the Signaling Radio Bearer (SRB) and the Data Radio Bearer (DRB).

[0619] Specifically, an embodiment of the present application further provides a radio access network device. As Figure 17 shown, the radio access network device 1700 includes: an antenna 1701, a radio frequency device 1702, a baseband device 1703, a processor 1704, and a memory 1705. The antenna 1701 is connected to the radio frequency device 1702. In the uplink direction, the radio frequency device 1702 receives information through the antenna 1701 and sends the received information to the baseband device 1703 for processing. In the downlink direction, the baseband device 1703 processes the information to be sent and sends it to the radio frequency device 1702. The radio frequency device 1702 processes the received information and then sends it out through the antenna 1701.

[0620] In the above embodiments, the sensing measurement method can be implemented in the baseband device 1703, and the baseband device 1703 includes a baseband processor.

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

[0622] The device may further include a network interface 1706, and the interface is, for example, a Common Public Radio Interface (CPRI).

[0623] Specifically, the device 1700 in an embodiment of the present application further includes: instructions or programs stored on the memory 1705 and executable on the processor 1704. The processor 1704 calls the instructions or programs in the memory 1705 to execute Figure 12 the methods executed by the modules shown in or 13 and achieves the same technical effects. To avoid repetition, it will not be elaborated here.

[0624] In one embodiment:

[0625] The radio frequency device 1702 is configured to send a first configuration to the terminal. 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); receive the information transmitted by the terminal through the dedicated bearer.

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

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

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

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

[0630] 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 handover, the mapping relationship of the dedicated bearer.

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

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

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

[0634] 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 mode of the dedicated bearer, the logical channel identifier of the dedicated bearer, the logical channel priority of the dedicated bearer, the guaranteed bit rate of the dedicated bearer.

[0635] Optionally, the bearer type of the dedicated bearer includes: a split bearer; or,

[0636] The transmission mode of the dedicated bearer includes at least one of the following: radio link control (RLC) transmission mode, dual active protocol stack (DAPS) transmission mode.

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

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

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

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

[0641] The routing information of the dedicated bearer; or

[0642] Packet format information, which is used to determine the routing information of the packets of the dedicated bearer.

[0643] Optionally, the first configuration is carried in a configuration message, where:

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

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

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

[0647] The dedicated bearer can coexist with the signaling radio bearer SRB and the data radio bearer DRB;

[0648] The dedicated bearer can transmit in parallel with the SRB and the DRB;

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

[0650] 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 separately;

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

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

[0653] The dedicated bearer supports cell handover.

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

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

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

[0657] Service data adaptation protocol DSAP-Uu entity;

[0658] DSAP-Ng entity, which is used for the interaction between the first radio access network device and the core network function;

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

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

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

[0662] when the configuration change of the second configuration has no explicit reset or no explicit reconstruction indication, the state variables of the PDCP entity and the RLC entity corresponding to the dedicated bearer are maintained; or,

[0663] when the configuration change of the second configuration affects Layer 2, the radio access network device reconstructs or resets at least one of the PDCP entity and the RLC entity corresponding to the dedicated bearer; or,

[0664] when the configuration change of the second configuration carries an explicit reset or reconstruction indication, the radio access network device reconstructs or resets at least one of the PDCP entity and the RLC entity corresponding to the dedicated bearer.

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

[0666] reset the RLC entity corresponding to the dedicated bearer of the terminal;

[0667] handover processing of the PDCP entity corresponding to the dedicated bearer of the terminal, where the handover processing includes at least one of the following:

[0668] clear the cache and reset the transmission variable;

[0669] retain the cache and reset the transmission variable;

[0670] retain the cache and the transmission variable.

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

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

[0673] whether the terminal supports the dedicated bearer;

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

[0675] whether the terminal supports information collection;

[0676] At least one function of information collection supported by the terminal;

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

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

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

[0680] When the radio access network device triggers information transmission, send the first configuration to the terminal;

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

[0682] When the radio access network device receives a second trigger message sent by another radio access network device for triggering information transmission, send the first configuration to the terminal.

[0683] 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:

[0684] Transparently transmit the information to the core network; or

[0685] Process the information for the core network and send the processed information to the core network.

[0686] In another embodiment:

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

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

[0689] Whether the terminal supports the dedicated bearer;

[0690] At least one capability of the dedicated bearer supported by the terminal;

[0691] Whether the terminal supports information collection;

[0692] At least one function of information collection supported by the terminal;

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

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

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

[0696] It can be understood that the implementation processes of the implementation manners mentioned in this embodiment can refer to the relevant descriptions of the above method embodiments, and achieve the same or corresponding technical effects. To avoid repetition, they will not be elaborated here.

[0697] The embodiment of the present application further provides a device, including a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction to implement as Figure 6 shown in the steps of the method embodiment. This device embodiment corresponds to the above signal measurement method embodiment. The implementation processes and implementation manners of the above method embodiment can all be applied to this device embodiment, and the same technical effects can be achieved.

[0698] The embodiment of the present application further provides a device, including a processor and a communication interface. Wherein, the communication interface is configured 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 a control node; where 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 the dedicated bearer; the dedicated bearer is a dedicated bearer for information transmission, and the dedicated bearer is independent of a signaling radio bearer (SRB) and a data radio bearer (DRB).

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

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

[0701] The network interface 1802 is configured 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 a control node;

[0702] Wherein, the information is the information transmitted by the terminal through a dedicated bearer; or, the information is the 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).

[0703] Optionally, the control node includes:

[0704] A control plane control node, or a user plane control node.

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

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

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

[0708] It can be understood that the implementation processes of the implementation manners mentioned in this embodiment can refer to the relevant descriptions of the method embodiments above, and achieve the same or corresponding technical effects. To avoid repetition, they will not be elaborated here.

[0709] This application embodiment also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, it implements each process of the above information transmission method, capability information reporting method, or capability information receiving method embodiment, and can achieve the same technical effects. To avoid repetition, they will not be elaborated here.

[0710] Wherein, the processor is the processor in the terminal in the above embodiment. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disc, etc. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0711] This application embodiment further provides a chip, 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 each process of the above information transmission method, capability information reporting method, or capability information receiving method embodiment, and can achieve the same technical effects. To avoid repetition, they will not be elaborated here.

[0712] It should be understood that the chip mentioned in this application embodiment may also be referred to as a system-on-chip, system chip, chip system, or system-on-chip, etc.

[0713] Another embodiment of the present application further provides a computer program / program product. The computer program / program product is stored in a storage medium and is executed by at least one processor to implement the various processes of the above information transmission method, capability information reporting method or capability information receiving method embodiments, and can achieve the same technical effects. To avoid repetition, it will not be elaborated here.

[0714] Another embodiment of the present application further provides a wireless communication system, including: a terminal, a radio 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 by the embodiments of the present application. The radio access network device can be used to execute the steps of the information transmission method on the radio access network device side provided by the embodiments of the present application. The core network function can be used to execute the steps of the information transmission method on the core network function side provided by the embodiments of the present application.

[0715] Another embodiment of the present application further provides a wireless communication system, including: a terminal and a radio access network device. The terminal can be used to execute the steps of the information transmission method on the terminal side provided by the embodiments of the present application, or the terminal can be used to execute the steps of the capability information reporting method provided by the embodiments of the present application. The radio access network device can be used to execute the steps of the information transmission method on the radio access network device side provided by the embodiments of the present application, or the radio access network device can be used to execute the steps of the capability information receiving method provided by the embodiments of the present application.

[0716] It should be noted that in this article, the terms "include", "comprise" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements but also includes other elements not explicitly listed, or further includes elements inherent to such process, method, article or device. Without more limitations, an element defined by the statement "including one..." does not exclude the existence of another identical element in the process, method, article or device including that 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 a reverse order according to the functions involved. For example, the described methods can be performed in an order different from that described, and various steps can be added, omitted or combined. In addition, the features described with reference to certain examples can be combined in other examples.

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

[0718] The embodiments of the present application have been described above in conjunction with the accompanying drawings. However, the present application is not limited to the above specific embodiments. The above specific embodiments are merely illustrative and not restrictive. Under the inspiration of the present application, those of ordinary skill in the art can also make many forms of embodiments without departing from the purpose of the present application and the scope protected by the claims. These embodiments are all within the protection scope of the present application.

Claims

1. An information transmission method, characterized in that, it includes: The terminal obtains a first configuration, 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); The terminal transmits information through the dedicated bearer.

2. The method according to claim 1, characterized in that, the dedicated bearer is used for at least one of the following: Information interaction between the terminal and the radio access network device; Information interaction between the terminal and the core network function.

3. The method according to claim 1 or 2, characterized in that, 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 handover, the mapping relationship of the dedicated bearer.

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

5. The method according to claim 4, characterized in that, 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, the guaranteed bit rate of the dedicated bearer.

6. The method according to claim 4 or 5, characterized in that, the bearer type of the dedicated bearer includes: a split bearer; or, the transmission mode of the dedicated bearer includes at least one of the following: the radio link control (RLC) transmission mode, the dual active protocol stack (DAPS) transmission mode.

7. The method according to any one of claims 4 to 6, characterized in that, 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, characterized in that, the routing-related information of the dedicated bearer includes: The routing information of the dedicated bearer; or Packet format information, where the packet format information is used to determine the routing information of the packets of the dedicated bearer.

9. The method according to any one of claims 1 to 8, characterized in that, the first configuration is carried in a configuration message, where: The first configuration is carried through a first information field in the configuration message, and the first information field is an information field dedicated to the configuration of the dedicated bearer; 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 for multiple bearers.

10. The method according to any one of claims 1 to 9, characterized in that, the dedicated bearer has at least one of the following characteristics: The dedicated bearer can coexist with the SRB and the DRB; The dedicated bearer can be transmitted in parallel with the SRB and the DRB; The dedicated bearer and the SRB can exist simultaneously; 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 handover.

11. The method according to claim 10, characterized in that 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, the segmentation attributes of the dedicated bearer.

12. The method according to any one of claims 1 to 11, characterized in that the dedicated bearer is used to transfer 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, characterized in that the method further includes: the terminal receives a second configuration sent by the network-side device, and the second configuration is used to reconfigure the dedicated bearer.

14. The method according to claim 13, characterized in that when the configuration changed by the second configuration does not affect layer 2, the state variables of the packet data convergence protocol (PDCP) entity and the radio link control (RLC) entity corresponding to the dedicated bearer are maintained; or, when the configuration changed by the second configuration has no explicit reset or no explicit reconstruction indication, the state variables of the PDCP entity and the RLC entity corresponding to the dedicated bearer are maintained; or, when the configuration changed by the second configuration 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, when the configuration changed by the second configuration carries an explicit reset or reconstruction indication, the terminal reconstructs or resets at least one of the PDCP entity and the RLC entity corresponding to the dedicated bearer.

15. The method according to claim 13, characterized in that in the case of cell handover, the second configuration is used to configure at least one of the following: reset the RLC entity corresponding to the dedicated bearer of the terminal; handover processing of the PDCP entity corresponding to the dedicated bearer of the terminal, and the handover processing includes at least one of the following: clear the cache and reset the transmission variable; retain the cache and reset the transmission variable; retain the cache and the transmission variable.

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

17. The method according to claim 16, characterized in that 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, characterized in that, it includes: 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, and 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 according to claim 18, characterized in that, the dedicated bearer is used for at least one of the following: Information interaction between the terminal and a second radio access network device; Information interaction between the terminal and core network functions.

20. The method according to claim 18 or 19, characterized in that, 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 a handover process, the mapping relationship of the dedicated bearer.

21. The method according to any one of claims 18 to 20, characterized in that, the first configuration is carried in a configuration message, where: the first configuration is carried through a first information field in the configuration message, and the first information field is an information field dedicated to the configuration of the dedicated bearer; 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 for multiple bearers.

22. The method according to any one of claims 18 to 21, characterized in that, the dedicated bearer has at least one of the following characteristics: The dedicated bearer can coexist with the signaling radio bearer (SRB) and the data radio bearer (DRB); The dedicated bearer can transmit 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 attribute of the dedicated bearer is configurable; The dedicated bearer corresponds to at least one quality of service (QoS); The dedicated bearer supports cell handover.

23. The method according to any one of claims 18 to 22, characterized in that, the dedicated bearer is used to transmit information of at least one of the following protocol entities: A service data adaptation protocol (DSAP)-Uu entity; A DSAP-Ng entity, where the DSAP-Ng entity is used for interaction between the first radio access network device and core network functions; A DSAP-Xn entity, where the DSAP-Xn entity is used for interaction between the first radio access network device and other radio access network devices.

24. The method according to any one of claims 18 to 23, characterized in that, the method further includes: 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 according to any one of claims 18 to 24, wherein, the method further comprises: the first radio access network device receives the capability information of the terminal reported by the terminal regarding the dedicated bearer.

26. The method according to any one of claims 18 to 25, wherein, the first radio access network device sends a first configuration to the terminal, including at least one of the following: when 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 sent by the core network for triggering information transmission, the first radio access network device sends a first configuration to the terminal; when the first radio access network device receives a second trigger message sent by another radio access network device for triggering information transmission, the radio access network device sends a first configuration to the terminal.

27. An information transmission method, wherein, it comprises: the core network function sends a trigger message for triggering information transmission to the radio access network device; the core network function receives information sent by the radio 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 the 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 according to claim 27, wherein, the control node includes: a control plane control node, or, a user plane control node.

29. The method according to 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 the information sent by the radio access network device and processed by the radio access network device through the DSAP - Ng entity.

30. An information transmission device, wherein, it comprises: an acquisition module, configured to acquire a first configuration for configuring a dedicated bearer for information transmission, the dedicated bearer being independent of the signaling radio bearer SRB and the data radio bearer DRB; a transmission module, configured to transmit information through the dedicated bearer.

31. The device according to claim 30, wherein, the device further comprises: a reception module, configured to receive a second configuration sent by the network side for reconfiguring the dedicated bearer.

32. The device according to claim 30 or 31, wherein, the device further comprises: a reporting module, configured to report the capability information regarding the dedicated bearer.

33. An information transmission device, wherein, it comprises: a first sending module, configured to send a first configuration to the terminal for configuring a dedicated bearer for information transmission, the dedicated bearer being independent of the signaling radio bearer SRB and the data radio bearer DRB; A first receiving module, configured to receive information transmitted by the terminal through the dedicated bearer.

34. The apparatus according to claim 33, wherein, the apparatus further comprises: A second sending module, configured to send a second configuration to the terminal, where the second configuration is used to reconfigure the dedicated bearer.

35. The apparatus according to claim 33 or 34, wherein, the apparatus further comprises: A second receiving module, configured to receive the capability information of the terminal reported by the terminal regarding the dedicated bearer.

36. An information transmission apparatus, wherein, comprises: A sending module, configured to send a trigger message for triggering information transmission to a radio access network device; A receiving module, configured to receive information sent by the radio access network device or a control node; wherein, 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 the dedicated bearer; the dedicated bearer is a dedicated bearer for information transmission, and the dedicated bearer is independent of a signaling radio bearer SRB and a data radio bearer DRB.

37. A terminal, wherein, comprises a processor and a memory, the memory stores a program or instruction that can 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 1 to 17 are implemented.

38. A radio access network device, wherein, comprises a processor and a memory, the memory stores a program or instruction that can 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, wherein, comprises a processor and a memory, the memory stores a program or instruction that can 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 27 to 29 are implemented.

40. A readable storage medium, wherein, the readable storage medium stores a program or instruction, and when the program or instruction is executed by a processor, the steps of the information transmission method according to any one of claims 1 to 17 are implemented, or the steps of the information transmission method according to any one of claims 18 to 26 are implemented, or the steps of the information transmission method according to any one of claims 27 to 29 are implemented.

Images