Information processing method and apparatus

Abstract

Disclosed in embodiments of the present disclosure are an information processing method and apparatus. According to the solution provided by the embodiments of the present disclosure, the method comprises: sending first information to a network device, the first information being used for indicating a transmission profile corresponding to each quality of service (QoS) flow among at least one QoS flow; receiving second information sent by the network device, the second information being used for indicating a mapping relationship between the at least one QoS flow and a sidelink (SL) radio bearer (RB), the second information being determined by the network device on the basis of the first information; and determining the mapping relationship between the at least one QoS flow and the SL RB on the basis of the second information, wherein the transmission profiles corresponding to one or more QoS flows mapped to the same SL RB are the same. Thus, the network can configure particular radio bearers on the basis of service attributes, so that the QoS flows comprised in the SL RB configuration acquired by the terminal are associated with the same transmission profile, thereby effectively ensuring the backward compatibility of service flows, improving the reliability of service transmission.

Description

Information processing method and device Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to an information processing method and device. Background Art

[0002] To support direct communication between terminals, sidelink (SL) communication was introduced. Carrier aggregation (CA) was introduced to meet the demand for increased system capacity. With the continuous development of technology, terminal and service versions are constantly iterating. To ensure service compatibility, the Tx profile was introduced to indicate the service version number.

[0003] Summary of the Invention

[0004] The embodiments of the present disclosure provide an information processing method and apparatus.

[0005] An embodiment of the first aspect of the present disclosure proposes an information processing method, which includes: sending first information to a network device, where the first information is used to indicate the sending attributes corresponding to each QoS flow in at least one quality of service QoS flow; receiving second information sent by the network device, where the second information is used to indicate the mapping relationship between at least one QoS flow and a side link SL radio bearer RB, and the second information is determined by the network device based on the first information; based on the second information, determining the mapping relationship between at least one QoS flow and the SL RB, wherein the sending attributes corresponding to the QoS flows mapped to the same SL RB are the same.

[0006] The second aspect embodiment of the present disclosure proposes an information processing method, which includes: receiving first information sent by a terminal, the first information is used to indicate the sending attributes corresponding to each QoS flow in at least one quality of service QoS flow; based on the first information, determining second information, the second information is used to indicate the mapping relationship between at least one QoS flow and a side link SL wireless bearer RB; sending second information to the terminal, the second information is used to determine the mapping relationship between at least one QoS flow and the SL RB, wherein the sending attributes corresponding to the QoS flows mapped to the same SL RB are the same.

[0007] An embodiment of the third aspect of the present disclosure proposes an information processing method, which includes: a terminal sends first information to a network device, where the first information is used to indicate the sending attributes corresponding to each QoS flow in at least one quality of service QoS flow; the network device determines second information based on the first information, where the second information is used to indicate the mapping relationship between at least one QoS flow and a side link SL wireless bearer RB; the network device sends second information to the terminal; the terminal determines the mapping relationship between at least one QoS flow and the SL RB based on the second information, wherein the sending attributes corresponding to the QoS flows mapped to the same SL RB are the same.

[0008] An embodiment of the fourth aspect of the present disclosure proposes a terminal, which includes: a transceiver module for sending first information to a network device, the first information being used to indicate the sending attributes corresponding to each QoS flow in at least one quality of service QoS flow; the transceiver module is also used to receive second information sent by the network device, the second information being used to indicate the mapping relationship between at least one QoS flow and a side link SL wireless bearer RB, and the second information is determined by the network device based on the first information; a processing module for determining the mapping relationship between at least one QoS flow and the SL RB based on the second information, wherein the sending attributes corresponding to the QoS flows mapped to the same SL RB are the same.

[0009] The fifth aspect embodiment of the present disclosure proposes a network device, wherein the network device comprises: a transceiver module for receiving first information sent by a terminal, the first information being used to indicate the sending attributes corresponding to each QoS flow in at least one quality of service QoS flow; a processing module for determining second information based on the first information, the second information being used to indicate the mapping relationship between at least one QoS flow and a side link SL wireless bearer RB; the transceiver module is further used to send second information to the terminal, the second information being used to determine the mapping relationship between at least one QoS flow and the SL RB, wherein the sending attributes corresponding to the QoS flows mapped to the same SL RB are the same.

[0010] The solution proposed in the embodiment of the present disclosure is to send first information to the network device, where the first information is used to indicate the sending attributes corresponding to each QoS flow in at least one quality of service QoS flow; receive second information sent by the network device, where the second information includes a mapping relationship between at least one QoS flow and a side link SL wireless bearer RB, and the second information is determined by the network device based on the first information; based on the second information, determine the mapping relationship between at least one QoS flow and the SL RB, wherein the sending attributes corresponding to one or more QoS flows mapped to the same SL RB are the same, so that the network can configure the corresponding wireless bearer based on the attributes of the service, so that the QoS flows contained in the configuration of the side link wireless bearer obtained by the terminal are associated with the same sending attributes, effectively ensuring the backward compatibility of the service flow and improving the reliability of service transmission. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure or the background technology, the drawings required for use in the embodiments of the present disclosure or the background technology will be described below.

[0012] FIG1A is a schematic diagram of the architecture of a communication system provided by an embodiment of the present disclosure;

[0013] FIG1B is a schematic diagram of a sidelink communication network state provided by an embodiment of the present disclosure;

[0014] FIG1C is a schematic diagram of a PDCP multiplexing mechanism provided by an embodiment of the present disclosure;

[0015] FIG2A is an interactive schematic diagram of an information processing method provided by an embodiment of the present disclosure;

[0016] 3A-3B are flowcharts of an information processing method provided by an embodiment of the present disclosure;

[0017] FIG4A is a flow chart of an information processing method provided by an embodiment of the present disclosure;

[0018] FIG5 is a flow chart of an information processing method provided by an embodiment of the present disclosure;

[0019] FIG6A is a schematic structural diagram of a terminal provided by an embodiment of the present disclosure;

[0020] FIG6B is a schematic structural diagram of a network device provided by an embodiment of the present disclosure;

[0021] FIG7A is a schematic structural diagram of a communication device provided by an embodiment of the present disclosure;

[0022] FIG7B is a schematic structural diagram of a chip provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0023] The embodiments of the present disclosure provide an information processing method and apparatus.

[0024] In a first aspect, an embodiment of the present disclosure provides an information processing method, the method comprising:

[0025] Sending first information to the network device, where the first information is used to indicate a sending attribute corresponding to each QoS flow in at least one quality of service QoS flow;

[0026] receiving second information sent by the network device, where the second information is used to indicate a mapping relationship between at least one QoS flow and a sidelink SL radio bearer RB, and the second information is determined by the network device based on the first information;

[0027] Based on the second information, a mapping relationship between at least one QoS flow and the SL RB is determined, wherein the QoS flows mapped to the same SL RB have the same corresponding sending attributes.

[0028] In the above embodiment, the network is enabled to configure the corresponding wireless bearer based on the attributes of the service, so that the QoS flows contained in the configuration of the sidelink wireless bearer obtained by the terminal are associated with the same sending attributes, effectively ensuring the backward compatibility of the service flow and improving the reliability of service transmission.

[0029] In combination with some embodiments of the first aspect, in some embodiments, at least one QoS flow is associated with the same layer 2 identifier.

[0030] In the above embodiment, the QoS flows included in the configuration of the SL RB correspond to the same L2 ID, which improves the compatibility of the solution.

[0031] In combination with some embodiments of the first aspect, in some embodiments, the terminal is in a radio resource control RRC connected state.

[0032] In the above embodiment, the network is enabled to receive the attributes of each QoS flow sent by the terminal, and configure the corresponding wireless bearer based on the attributes, so that the QoS flows contained in the configuration of the sidelink wireless bearer obtained by the terminal are associated with the same sending attributes, effectively ensuring the backward compatibility of the service flow and improving the reliability of service transmission.

[0033] In combination with some embodiments of the first aspect, in some embodiments, the first information is included in the sidelink terminal information SUI.

[0034] In the above embodiment, sending the information indicating the transmission attributes of the QoS flow through the SUI can effectively save signaling overhead, improve the compatibility of the solution, and enhance the communication efficiency of the system.

[0035] In conjunction with some embodiments of the first aspect, in some embodiments, the sending attribute includes backward compatibility and non-backward compatibility.

[0036] In the above embodiment, the network is able to determine whether each service is backward compatible and configure the corresponding wireless bearer based on the attribute, so that the QoS flow contained in the configuration of the sidelink wireless bearer obtained by the terminal is associated with the same sending attribute, effectively ensuring the backward compatibility of the service flow and improving the compatibility of the solution.

[0037] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0038] Obtaining, from a higher layer, an association relationship between at least one QoS flow and a sending attribute;

[0039] It is determined that the sending attribute corresponding to the QoS flow without associated sending attribute is backward compatible, or it is determined that the sending attribute corresponding to the QoS flow without associated sending attribute is not backward compatible.

[0040] In the above embodiment, the terminal can determine the sending attributes corresponding to each QoS flow based on the high-level configuration. When the QoS flow has no associated sending attributes, the terminal can flexibly determine the sending attributes of the QoS flow, effectively improving the compatibility of the service and improving the transmission efficiency.

[0041] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0042] It is determined to use a single carrier to send the SL RB, wherein the sending attribute of at least one QoS flow mapped to the SL RB is backward compatible, and the single carrier is a traditional carrier.

[0043] In the above embodiment, when the QoS flows contained in the configuration of the sidelink radio bearer obtained by the terminal are associated with the same sending attributes and the sending attributes are backward compatible, it can be determined that the traditional carrier is used to send the radio bearer, thereby ensuring that the old version of the terminal can receive the service flow, effectively ensuring the backward compatibility of the service flow, and improving the reliability of service transmission.

[0044] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0045] It is determined to use a packet data convergence protocol (PDCP) multiplexing mechanism to send SL RBs, wherein a sending attribute of at least one QoS flow mapped to the SL RB is backward compatible, and at least one of the carriers used by the PDCP multiplexing mechanism is a traditional carrier.

[0046] In the above embodiment, the QoS flows contained in the configuration of the sidelink radio bearer obtained by the terminal are associated with the same transmission attributes, and when the transmission attributes are backward compatible, it can be determined that the carriers used for transmission using the multiplexing mechanism include traditional carriers, ensuring that terminals of old versions can receive the service flow, effectively ensuring the backward compatibility of the service flow, and at the same time using repeated transmission to improve the reliability of service transmission and reduce transmission delay.

[0047] In a second aspect, an embodiment of the present disclosure provides an information processing method, the method comprising:

[0048] receiving first information sent by a terminal, where the first information is used to indicate a sending attribute corresponding to each QoS flow in at least one quality of service QoS flow;

[0049] Determine second information based on the first information, where the second information is used to indicate a mapping relationship between at least one QoS flow and a sidelink SL radio bearer RB;

[0050] Second information is sent to the terminal, where the second information is used to determine a mapping relationship between at least one QoS flow and the SL RB, wherein the QoS flows mapped to the same SL RB have the same sending attributes.

[0051] In the above embodiment, the network is enabled to configure the corresponding wireless bearer based on the attributes of the service, so that the QoS flows contained in the configuration of the sidelink wireless bearer obtained by the terminal are associated with the same sending attributes, effectively ensuring the backward compatibility of the service flow and improving the reliability of service transmission.

[0052] In combination with some embodiments of the second aspect, in some embodiments, at least one QoS flow is associated with the same layer 2 identifier.

[0053] In combination with some embodiments of the second aspect, in some embodiments, the terminal is in a radio resource control RRC connected state.

[0054] In combination with some embodiments of the second aspect, in some embodiments, the first information is included in the sidelink terminal information SUI.

[0055] In conjunction with some embodiments of the second aspect, in some embodiments, the sending attribute includes backward compatibility and non-backward compatibility.

[0056] In a third aspect, an embodiment of the present disclosure provides an information processing method, which includes:

[0057] The terminal sends first information to the network device, where the first information is used to indicate a sending attribute corresponding to each QoS flow in at least one quality of service QoS flow;

[0058] The network device determines second information based on the first information, where the second information is used to indicate a mapping relationship between at least one QoS flow and a sidelink SL radio bearer RB;

[0059] The network device sends second information to the terminal;

[0060] Based on the second information, the terminal determines a mapping relationship between at least one QoS flow and the SL RB, wherein the QoS flows mapped to the same SL RB have the same sending attributes.

[0061] In the above embodiment, the network is enabled to configure the corresponding wireless bearer based on the attributes of the service, so that the QoS flows contained in the configuration of the sidelink wireless bearer obtained by the terminal are associated with the same sending attributes, effectively ensuring the backward compatibility of the service flow and improving the reliability of service transmission.

[0062] In combination with some embodiments of the third aspect, in some embodiments, at least one QoS flow is associated with the same layer 2 identifier.

[0063] In combination with some embodiments of the third aspect, in some embodiments, the terminal is in a radio resource control RRC connected state.

[0064] In combination with some embodiments of the third aspect, in some embodiments, the first information is included in the sidelink terminal information SUI.

[0065] In conjunction with some embodiments of the third aspect, in some embodiments, the sending attribute includes backward compatibility and non-backward compatibility.

[0066] In conjunction with some embodiments of the third aspect, in some embodiments, the method further includes:

[0067] The terminal obtains an association relationship between at least one QoS flow and a sending attribute from a higher layer;

[0068] The terminal determines that the transmission attribute corresponding to the QoS flow without associated transmission attribute is backward compatible, or determines that the transmission attribute corresponding to the QoS flow without associated transmission attribute is non-backward compatible.

[0069] In conjunction with some embodiments of the third aspect, in some embodiments, the method further includes:

[0070] The terminal determines to use a single carrier to send the SL RB, wherein the sending attribute of at least one QoS flow mapped to the SL RB is backward compatibility, and the single carrier is a traditional carrier.

[0071] In conjunction with some embodiments of the third aspect, in some embodiments, the method further includes:

[0072] The terminal determines to use the Packet Data Convergence Protocol PDCP multiplexing mechanism to send SL RB, wherein the sending attribute of at least one QoS flow mapped to the SL RB is backward compatible, and at least one of the carriers used by the PDCP multiplexing mechanism is a traditional carrier.

[0073] In a fourth aspect, an embodiment of the present disclosure proposes a terminal, which includes a transceiver module and a processing module; wherein the terminal is used to execute the first aspect and the optional implementation method of the first aspect.

[0074] In a fifth aspect, an embodiment of the present disclosure proposes a network device, which includes a transceiver module and a processing module; wherein the network device is used to execute the second aspect and the optional implementation method of the second aspect.

[0075] In a sixth aspect, an embodiment of the present disclosure proposes a terminal, comprising: one or more processors; wherein the terminal is used to execute the first aspect and the optional implementation method of the first aspect.

[0076] In a seventh aspect, an embodiment of the present disclosure proposes a network device, comprising: one or more processors; wherein the network device is used to execute the second aspect and the optional implementation method of the second aspect.

[0077] In the eighth aspect, an embodiment of the present disclosure proposes a communication system, which includes: a terminal and a network device; wherein the terminal is configured to execute the method described in the first aspect and the optional implementation of the first aspect, and the network device is configured to execute the method described in the second aspect and the optional implementation of the second aspect.

[0078] In the ninth aspect, an embodiment of the present disclosure proposes a storage medium, which stores instructions. When the instructions are executed on a communication device, the communication device executes the method described in the first aspect and the optional implementation of the first aspect, the second aspect and the optional implementation of the second aspect.

[0079] In a tenth aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the method described in the first aspect and the optional implementation of the first aspect, the second aspect and the optional implementation of the second aspect.

[0080] In an eleventh aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the method described in the first aspect and the optional implementation of the first aspect, the second aspect and the optional implementation of the second aspect.

[0081] In a twelfth aspect, an embodiment of the present disclosure provides a chip or a chip system, wherein the chip or chip system includes a processing circuit configured to execute the method described in accordance with the first aspect and its optional implementation, the second aspect and its optional implementation.

[0082] It is understandable that the above-mentioned terminals, network devices, communication systems, storage media, program products, computer programs, chips, or chip systems are all used to perform the methods proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

[0083] The present disclosure provides an information processing method and apparatus. In some embodiments, the terms "information processing method" and "communication method" are interchangeable; the terms "information processing apparatus" and "communication apparatus" are interchangeable; and the terms "information processing system" and "communication system" are interchangeable.

[0084] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0085] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0086] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0087] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0088] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0089] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0090] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0091] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0092] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0093] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0094] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0095] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

[0096] In some embodiments, devices and equipment can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they can also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject", etc.

[0097] In some embodiments, "network" can be interpreted as devices included in the network, such as access network equipment, core network equipment, etc.

[0098] In some embodiments, "access network device (AN device)" may also be referred to as "radio access network device (RAN device)", "base station (BS)", "radio base station", "fixed station", and in some embodiments may also be understood as "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission and / or reception point (TRP)" "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)", etc.

[0099] In some embodiments, "terminal" or "terminal device" may be referred to as "user equipment (UE)", "user terminal" "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc.

[0100] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0101] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0102] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0103] FIG1A is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.

[0104] As shown in FIG1A , a communication system 100 includes a terminal 101 and a network device 102 .

[0105] In some embodiments, the terminal 101 includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, a wireless terminal device in a smart home, and at least one of a reduced capability (RedCap) terminal, but is not limited thereto.

[0106] In some embodiments, the network device 102 is, for example, a node or device that accesses a terminal to a wireless network. The network device may include a node in an information processing network, an evolved NodeB (eNB) in a 5G communication system, a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved nodeB (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open base station (Open RAN), a cloud base station (Cloud RAN), a base station in other communication systems, and at least one of an access node in a Wi-Fi system, but is not limited thereto.

[0107] In some embodiments, the technical solution of the present disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within the access network devices involved in the embodiments of the present disclosure can be transformed into internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.

[0108] In some embodiments, the network device can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

[0109] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0110] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1 , or a portion thereof, but are not limited thereto. The entities shown in FIG1 are illustrative only. The communication system may include all or part of the entities shown in FIG1 , or may include other entities outside of FIG1 . The number and form of the entities are arbitrary, and the entities may be physical or virtual. The connection relationships between the entities are illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0111] The embodiments of the present disclosure can be applied to information processing systems, Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), future radio access (FRA), new radio access technology (RAT), new radio (NR), new radio access (NX), future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X), systems utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0112] In some embodiments, in order to support direct communication between terminals, a sidelink (SL) communication mode is introduced. The interface between terminals is PC-5 (a bottom-layer direct cellular communication protocol interface). Terminal devices in network coverage (in coverage) and out of network coverage (out of coverage, OOC) can both perform sidelink communication. For example, as shown in Figure 1B, the first terminal in coverage can perform sidelink communication with the second terminal in coverage. Alternatively, the first terminal in coverage can perform sidelink communication with the second terminal of OOC. Alternatively, the first terminal of OOC can perform sidelink communication with the second terminal of OOC. Among them, the terminal devices in coverage can be in a radio resource control (RRC) connected state (CONNECETED) or an RRC idle state (IDLE) or an RRC inactive state (INACTIVE). The sidelink communication performed by the terminal devices includes three transmission modes: unicast, multicast and broadcast.

[0113] In some embodiments, as the versions of terminals and services continue to iterate, in order to ensure backward compatibility of the services, LTE V2X defines a transmission attribute (TxProfile) to indicate the version number of the service. For example, R17 NR V2X introduces the discontinuous reception (DRX) feature. In order to ensure backward compatibility, for example, to ensure that terminals of older versions can receive broadcast / multicast services of R17 terminals, and to ensure that R17 terminals can receive broadcast / multicast services of older versions of terminals, TxProfile is defined for broadcast / multicast services at the layer 2 (Layer 2, L2) identifier (ID) granularity. TxProfile is used to indicate whether the associated broadcast / multicast service supports DRX. If the transmitting terminal determines that a broadcast / multicast service supports the DRX attribute, it can assume that the receiving terminal has enabled DRX and only send data during the "active" time of the receiving terminal. The receiving terminal enables DRX only when it determines that all broadcast / multicast services of interest support DRX attributes, that is, it wakes up only during the "active" time to listen to the data of the broadcast / multicast services.

[0114] In some embodiments, in order to meet the demand for increased system capacity, carrier aggregation (CA) technology is introduced. CA technology can aggregate multiple carriers (Component Carrier, CC) together, effectively improving the uplink and downlink transmission rates. LTE V2X already supports sidelink carrier aggregation technology. Furthermore, one of the goals of NR sidelink carrier aggregation is to ensure backward compatibility, that is, to ensure that old version R16 / R17 terminals can receive broadcast / multicast services sent by R18 terminals that support carrier aggregation.

[0115] In some embodiments, to improve data packet reliability, a Packet Data Convergence Protocol (PDCP) duplication mechanism, also known as packet duplication, is introduced, which involves sending a single data packet repeatedly. Using this mechanism for repeated transmission can improve data packet transmission reliability, reduce the latency of repeated transmissions, and meet the requirements of Ultra-Reliable Low-Latency Communications (URLLC). If the PDCP duplication mechanism is not employed, a PDCP packet is transmitted to a Radio Link Control (RLC) entity. After processing, the RLC entity sends the packet to the Media Access Control (MAC) layer, which then schedules the data. If the PDCP duplication mechanism is employed, a PDCP packet is transmitted to at least two RLC entities, such as the primary and secondary RLC entities shown in FIG1C . Each RLC entity independently processes the packet and transmits the processed packet to the MAC layer. From the MAC layer's perspective, these are two independent packets. The MAC layer cannot identify whether this is a packet transmitted by PDCP duplication. The MAC layer only needs to schedule according to the algorithm. It should be noted that in the CA scenario, the protocol requires that the two packets of PDCP duplication be transmitted on different logical channels (LCH) in different cells, for example, the primary LCH and secondary LCH shown in Figure 1C. On the NR Uu interface, the LCH used for PDCP duplication is configured to the terminal by the network side through RB configuration. Network equipment can configure whether an RB enables PDCP duplication through SL RB configuration.

[0116] In some embodiments, the network device can configure a SL radio bearer (RadioBearer, RB) for a UE in a radio resource control (Radio Resources Control, RRC) connection state through a sidelink radio bearer configuration SL-RadioBearerConfig. The SL-RadioBearerConfig configuration includes a service data adaptation protocol (Service Data Adaptation Protocol, SDAP) configuration, and the SDAP configuration includes a quality of service (Quality of Service, QoS) flow associated with this SL RB.

[0117] In some embodiments, if the network device does not know the TxProfile associated with a QoS flow, it may map the backward-compatible QoS flow and the non-backward-compatible QoS flow into one SL RB. In this case, if the network configures the PDCP duplication of the SL RB to be disabled, the terminal is not required to use the legacy carrier, which can also be called the existing carrier (the existing carrier supported by R16 / R17). When the terminal does not use the legacy carrier, the backward-compatible QoS flow contained in this RB can only be transmitted through the new carrier, and the R16 / R17 terminal cannot receive this QoS flow.

[0118] The information processing method and device provided by the present disclosure are described in detail below with reference to the accompanying drawings.

[0119] FIG2A is an interactive diagram of an information processing method according to an embodiment of the present disclosure. As shown in FIG2A , the present disclosure embodiment relates to an information processing method, which includes:

[0120] Step S2101: Terminal 101 obtains a sending attribute associated with at least one QoS flow.

[0121] In some embodiments, the Tx Profile is configured at the granularity of a Quality of Service (QoS) flow.

[0122] In some embodiments, the terminal 101 obtains the association relationship between at least one QoS flow and the transmission attribute from a higher layer of the terminal 101 .

[0123] In some embodiments, the access stratum (AS) of the terminal 101 obtains the association relationship between at least one QoS flow and the sending attribute from the higher layer of the terminal 101 .

[0124] In some embodiments, the aforementioned sending attributes are backward compatible or non-backward compatible.

[0125] It is understandable that the QoS flow with the backward compatibility attribute refers to the QoS flow that can be received by the old version terminal of R16 / R17.

[0126] In step S2102, the terminal 101 determines the transmission attributes corresponding to each QoS flow.

[0127] In some embodiments, the terminal 101 determines the transmission attribute corresponding to each QoS flow based on an association relationship between at least one QoS flow and the transmission attribute obtained from a higher layer of the terminal 101 .

[0128] In some embodiments, the terminal 101 determines that the transmission attribute corresponding to the QoS flow without associated transmission attribute is backward compatible.

[0129] In some embodiments, the terminal 101 determines that the transmission attribute corresponding to the QoS flow without associated transmission attribute is non-backward compatible.

[0130] Step S2103: Terminal 101 sends first information.

[0131] In some embodiments, the network device 102 receives the first information.

[0132] In some embodiments, the first information is used to indicate a sending attribute corresponding to each QoS flow in the at least one QoS flow.

[0133] In some embodiments, the terminal 101 sends the sending attributes corresponding to each QoS flow determined above to the network device 102 through the above-mentioned first information.

[0134] In some embodiments, the name of the above-mentioned first information is not limited, and it can be, for example, "transmission attribute", "side link transmission attribute", "transmission attribute indication", etc.

[0135] In some embodiments, the first information is included in sidelink terminal information (Sidelink UE Information, SUI).

[0136] In some embodiments, the first information is included in UE Assistance Information (UAI).

[0137] In some embodiments, the at least one QoS flow indicated by the first information is at least one QoS flow associated with the same layer 2 identifier.

[0138] In some embodiments, the first information indicates a sending attribute of at least one QoS flow associated with the same layer 2 identifier.

[0139] In some embodiments, the first information indicates the transmission attributes of at least one QoS flow associated with each of the multiple target layer 2 addresses. Exemplarily, the terminal 101 has three target layer 2 addresses ABC, and the first information may include the transmission attributes of at least one QoS flow associated with target address A, the transmission attributes of at least one QoS flow associated with target address B, and the transmission attributes of at least one QoS flow associated with target address C. Exemplarily, for each QoS flow associated with target address A, the first information indicates the identifier of each QoS flow and the transmission attributes of the QoS flow; exemplary, for each QoS flow associated with target address B, the first information indicates the identifier of each QoS flow and the transmission attributes of the QoS flow; exemplary, for each QoS flow associated with target address C, the first information indicates the identifier of each QoS flow and the transmission attributes of the QoS flow.

[0140] In some embodiments, terminal 101 is in a Radio Resources Control (RRC) connected state.

[0141] In some embodiments, terminal 101 may operate in resource allocation mode 1 (mode 1) or in resource allocation mode 2 (mode 2). Mode 1 refers to a resource allocation mode in which the network dynamically schedules the resource allocation, i.e., the network dynamically allocates sidelink transmission resources to the terminal based on the terminal's buffered data report; mode 2 refers to a resource allocation mode in which the terminal autonomously selects from a network-broadcasted resource pool, i.e., the terminal randomly selects sidelink transmission resources from a network-configured or pre-configured resource pool.

[0142] In step S2104 , the network device 102 determines the second information.

[0143] In some embodiments, the network device 102 can determine the second information based on the first information.

[0144] In some embodiments, the second information includes a mapping relationship between the at least one QoS flow and a sidelink (SL) radio bearer (RB).

[0145] In some embodiments, the mapping relationship between the at least one QoS flow and the SL RB is that the transmission attributes corresponding to one or more QoS flows mapped to the same SL RB are the same. Exemplarily, one or more QoS flows with a transmission attribute of backward compatibility are mapped to one or more SLRBs; and exemplary, one or more QoS flows with a transmission attribute of non-backward compatibility are mapped to one or more SLRBs.

[0146] In some embodiments, QoS flows with different transmission attributes are mapped to different SLRBs.

[0147] In some embodiments, the name of the above-mentioned second information is not limited, and it can be, for example, "sidelink radio bearer configuration", "service data adaptation protocol configuration", "sidelink configuration", "radio bearer configuration", etc.

[0148] In some embodiments, the second information includes one or more SLRB configurations.

[0149] In some embodiments, QoS flows with different transmission attributes cannot be mapped to the same SL RB.

[0150] Step S2105: The network device 102 sends the second information.

[0151] In some embodiments, the network device 102 sends the second information to the terminal 101 via dedicated RRC signaling.

[0152] In some embodiments, terminal 101 receives the second information.

[0153] In some embodiments, the second information is used by the terminal 101 to determine a mapping relationship between the at least one QoS flow and the SL RB.

[0154] Step S2106: Terminal 101 determines a mapping relationship between the at least one QoS flow and the SL RB.

[0155] In some embodiments, the terminal 101 determines a mapping relationship between the at least one QoS flow and the SL RB based on the second information, wherein the transmission attributes corresponding to one or more QoS flows mapped to the same SL RB are the same.

[0156] In some embodiments, the terminal 101 determines, based on the second information, one or more SL RBs for at least one QoS flow mapping whose sending attribute is backward compatible, and determines one or more SL RBs for at least one QoS flow mapping whose sending attribute is non-backward compatible.

[0157] In some embodiments, QoS flows with different transmission attributes are mapped to different SLRBs.

[0158] In some embodiments, one or more SL RBs mapped to at least one QoS flow with a backward-compatible transmission attribute may be transmitted using a single carrier, where the single carrier is a legacy carrier, also referred to as a traditional carrier. Specifically, the legacy carrier refers to an SL carrier supported by R16 / R17 terminals.

[0159] In some embodiments, one or more SL RBs mapped to at least one QoS flow with a backward-compatible transmission attribute may be transmitted using a PDCP multiplexing mechanism, wherein at least one of the carriers used by the PDCP multiplexing mechanism is a legacy carrier.

[0160] In some embodiments, terms such as "carrier", "band", and "frequency" can be used interchangeably.

[0161] In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codeword", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0162] In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codeword", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0163] In some embodiments, terms such as "physical downlink shared channel (PDSCH)" and "DL data" can be used interchangeably, and terms such as "physical uplink shared channel (PUSCH)" and "UL data" can be used interchangeably.

[0164] In some embodiments, the terms "radio", "wireless", "radio access network (RAN)", "access network (AN)", "RAN-based" and the like may be used interchangeably.

[0165] In some embodiments, terms such as "resource block (RB)", "physical resource block (PRB)", "sub-carrier group (SCG)", "resource element group (REG)", "PRB pair", "RB pair", "resource element (RE)", and "sub-carrier" can be used interchangeably.

[0166] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

[0167] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0168] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "a certain", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, a certain A, any A, or first A, etc., but not limited to this.

[0169] In some embodiments, the determination or judgment can be performed by a value represented by 1 bit (0 or 1), or by a true or false value (Boolean value) represented by true or false, or by comparison of numerical values ​​(for example, comparison with a predetermined value), but is not limited thereto.

[0170] The communication method involved in the embodiments of the present disclosure may include at least one of steps S2101 to S2106. For example, steps 2101 and 2102 may be implemented as independent embodiments, step 2103 may be implemented as an independent embodiment, steps 2101, 2102, and 2103 may be implemented as independent embodiments, steps 2103, 2104, and 2105 may be implemented as independent embodiments, steps 2105 and 2106 may be implemented as independent embodiments, steps 2103, 2104, 2105, and 2106 may be implemented as independent embodiments, and steps 2101, 2102, 2103, 2104, 2105, and 2106 may be implemented as independent embodiments, etc., but the present invention is not limited thereto.

[0171] In some embodiments, steps S2101-2102 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0172] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 2A .

[0173] FIG3A is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG3A , the present disclosure embodiment relates to an information processing method, which is executed by terminal 101 and includes:

[0174] Step S3101: Obtain sending attributes associated with at least one QoS flow.

[0175] The optional implementation of step S3101 can refer to the optional implementation of step S2101 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0176] Step S3102: Determine the sending attributes corresponding to each QoS flow.

[0177] The optional implementation of step S3102 can refer to the optional implementation of step S2102 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0178] Step S3103, sending the first information.

[0179] The optional implementation of step S3103 can refer to the optional implementation of step S2103 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0180] Optionally, the first information is used by the network device 102 to determine the second information based on the first information. Optional implementations thereof can be found in the optional implementations of step S2104 in FIG2A and other related parts of the embodiment involved in FIG2A , which will not be described in detail here.

[0181] Step S3104, receiving the second information.

[0182] The optional implementation of step S3104 can refer to the optional implementation of step S2105 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0183] Step S3105: Determine the mapping relationship between the at least one QoS flow and the SL RB.

[0184] The optional implementation of step S3105 can refer to the optional implementation of step S2106 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0185] The communication method involved in the embodiments of the present disclosure may include at least one of steps S3101 to S3105. For example, steps 3101 and 3102 may be implemented as independent embodiments, step 3103 may be implemented as an independent embodiment, steps 3101, 3102, and 3103 may be implemented as independent embodiments, steps 3103 and 3104 may be implemented as independent embodiments, step 3105 may be implemented as an independent embodiment, steps 3103, 3104, and 3105 may be implemented as independent embodiments, steps 3101, 3102, 3103, 3104, and 3105 may be implemented as independent embodiments, and the like, but the present invention is not limited thereto.

[0186] FIG3B is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG3B , the embodiment of the present disclosure relates to an information processing method, which is executed by terminal 101 and includes:

[0187] Step S3201, sending the first information.

[0188] Optional implementations of step S3201 can be found in step S2103 of FIG. 2A , optional implementations of step S3103 of FIG. 3A , and other related parts in the embodiments involved in FIG. 2A and FIG. 3A , which will not be described in detail here.

[0189] Optionally, the first information is determined based on the transmission attributes corresponding to the at least one determined QoS flow. For optional implementations, see steps S2101-S2102 of FIG. 2A , steps S3101-S3102 of FIG. 3A , and other related parts of the embodiments involved in FIG. 2A and FIG. 3A , which are not described in detail here.

[0190] Optionally, the first information is used by the network device 102 to determine the second information based on the first information. Optional implementations thereof can be found in the optional implementations of step S2104 in FIG2A and other related parts of the embodiment involved in FIG2A , which will not be described in detail here.

[0191] Step S3202, receiving the second information.

[0192] The optional implementation of step S3202 can refer to the optional implementation of step S2105 in Figure 2A, step S3104 in Figure 3A, and other related parts in the embodiments involved in Figures 2A and 3A, which will not be repeated here.

[0193] Step S3203: Determine a mapping relationship between the at least one QoS flow and the SL RB.

[0194] The optional implementation of step S3203 can refer to the optional implementation of step S2106 in Figure 2A, step S3105 in Figure 3A, and other related parts in the embodiments involved in Figures 2A and 3A, which will not be repeated here.

[0195] The communication method according to the embodiments of the present disclosure may include at least one of steps S3201 to S3203. For example, step 3201 may be implemented as an independent embodiment, steps 3201+3202 may be implemented as independent embodiments, step 3203 may be implemented as an independent embodiment, steps 3201+3202+3203 may be implemented as independent embodiments, etc., but the present invention is not limited thereto.

[0196] FIG4A is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG4A , the present disclosure embodiment relates to an information processing method, which is executed by the network device 102 and includes:

[0197] Step S4101, receiving first information.

[0198] The optional implementation of step S4101 can refer to the optional implementation of step S2103 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0199] Optionally, the first information is sent by the terminal 101 based on the transmission attributes corresponding to the at least one QoS flow determined. Optional implementations thereof can be found in the optional implementations of steps S2101-S2102 of FIG. 2A and other related parts of the embodiment involved in FIG. 2A , which will not be described in detail here.

[0200] Step S4102, determine the second information.

[0201] The optional implementation of step S4102 can refer to the optional implementation of step S2104 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0202] Step S4103: Send the second information.

[0203] The optional implementation of step S4103 can refer to the optional implementation of step S2105 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0204] Optionally, the second information is used by the terminal 101 to determine the mapping relationship between at least one QoS flow and the SL RB. For its optional implementation, please refer to the optional implementation of step S2106 in Figure 2A and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.

[0205] The communication method involved in the embodiments of the present disclosure may include at least one of steps S4101 to S4103. For example, step 4101 may be implemented as an independent embodiment, steps 4101+4102 may be implemented as independent embodiments, step 4103 may be implemented as an independent embodiment, steps 4101+4102+4103 may be implemented as independent embodiments, etc., but the present invention is not limited thereto.

[0206] FIG5 is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG5 , the method according to the embodiment of the present disclosure is used in a communication system 100, and the method includes:

[0207] In step S5101, the terminal 101 sends first information to the network device 102, where the first information is used to indicate a sending attribute corresponding to each QoS flow in at least one QoS flow.

[0208] In step S5102, the network device 102 determines second information based on the first information, where the second information includes a mapping relationship between the at least one QoS flow and the SL RB.

[0209] Step S5103 , the network device 102 sends the second information to the terminal 101 .

[0210] In step S5104, the terminal 101 determines a mapping relationship between the at least one QoS flow and the SL RB based on the second information, wherein the transmission attributes corresponding to the one or more QoS flows mapped to the same SL RB are the same.

[0211] The optional implementation methods of steps S5101-S5104 can refer to the steps in any embodiment or any multiple embodiments in the above-mentioned Figures 2A, 3A-3B, and 4A, and other related parts of the embodiments involved in Figures 2A, 3A-3B, and 4A.

[0212] In some embodiments, the above method may include the method described in the above embodiments of the communication system side, terminal side, network device side, etc., which will not be repeated here.

[0213] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0214] The following is an exemplary introduction to the methods described in the above embodiments.

[0215] In some embodiments, tx profiles are configured at the QoS flow granularity.

[0216] As an example, tx profiles are configured at the QoS flow granularity, and higher layers indicate the mapping relationship between AS layer QoS flows and tx profiles. If a QoS flow has no associated tx profile, the QoS flow is considered backward compatible; if a QoS flow has no associated tx profile, the QoS flow is considered non-backward compatible.

[0217] In some embodiments, the UE reports the tx profile associated with the QoS flow to the network device.

[0218] As an example, the UE reports the tx profile associated with the QoS flow to the network device through the SUI.

[0219] As an example, the UE reports the tx profile corresponding to the QoS flow associated with the L2 ID to the network device. Specifically, for an L2 ID, the UE reports the tx profile corresponding to one or more QoS flows associated with the L2 ID to the network device.

[0220] As an example, the UE is in an RRC connected state. The UE may operate in mode 1 or the UE may operate in mode 2 and be in an RRC connected state.

[0221] As an example, the specific ASN.1 changes may be, for example: adding an information element (IE) sl-TxPorfile-v18xy in the sidelink transmission resource request SL-TxResourceReq-v1700, which is used to indicate the transmission attributes of at least one QoS flow and / or the identifier of at least one QoS flow. The attributes of the IE may be optional.

[0222] In some embodiments, the network maps QoS flows with the same tx profile attributes to the same RB based on the SUI.

[0223] As an example, based on the SUI, the network device can map QoS flows with the same tx profile to the same RB, but cannot map QoS flows with different tx profiles to the same RB.

[0224] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a network device (e.g., an access network device, a core network function node, a core network device, etc.) in any of the above methods.

[0225] It should be understood that the division of the various units or modules in the above apparatus is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a single physical entity, or they may be physically separated. Furthermore, the units or modules in the apparatus may be implemented in the form of a processor invoking software: for example, the apparatus includes a processor connected to a memory storing instructions, and the processor invokes the instructions stored in the memory to implement any of the above methods or the functions of the various units or modules of the apparatus. The processor may be, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory may be internal to the apparatus or external to the apparatus. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0226] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0227] Figure 6A is a structural diagram of a terminal proposed in an embodiment of the present disclosure. As shown in Figure 6A, the terminal 6100 may include: at least one of a transceiver module 6101, a processing module 6102, etc. In some embodiments, the transceiver module is used to send first information to a network device, and the first information is used to indicate the sending attributes corresponding to each QoS flow in at least one quality of service QoS flow; the transceiver module is also used to receive second information sent by the network device, and the second information includes a mapping relationship between at least one QoS flow and a side link SL radio bearer RB, and the second information is determined by the network device based on the first information; the processing module is used to determine the mapping relationship between at least one QoS flow and the SL RB based on the second information, wherein the sending attributes corresponding to one or more QoS flows mapped to the same SL RB are the same.

[0228] Optionally, the above-mentioned transceiver module is used to execute at least one of the communication steps such as sending and / or receiving (for example, step 2103, step 2105, but not limited to this) performed by the terminal 101 in any of the above methods, which will not be repeated here.

[0229] Optionally, the above-mentioned processing module is used to execute at least one of the other steps (such as step 2101, step 2102, step 2106, but not limited thereto) performed by the terminal 101 in any of the above methods, which will not be repeated here.

[0230] Figure 6B is a structural diagram of a network device proposed in an embodiment of the present disclosure. As shown in Figure 6B, the network device 6200 may include: a transceiver module 6201. In some embodiments, the transceiver module is used to receive first information sent by a terminal, and the first information is used to indicate the transmission attributes corresponding to each QoS flow in at least one quality of service QoS flow; the processing module is used to determine second information based on the first information, and the second information includes a mapping relationship between at least one QoS flow and a side link SL radio bearer RB; the transceiver module is also used to send second information to the terminal, and the second information is used to determine the mapping relationship between at least one QoS flow and the SL RB, wherein the transmission attributes corresponding to one or more QoS flows mapped to the same SL RB are the same.

[0231] Optionally, the above-mentioned transceiver module is used to execute at least one of the communication steps such as sending and / or receiving (for example, step 2103, step 2105, but not limited to this) performed by the network device 102 in any of the above methods, which will not be repeated here.

[0232] Optionally, the processing module is used to execute at least one of the other steps (such as step 2104, but not limited thereto) performed by the network device 102 in any of the above methods, which will not be repeated here.

[0233] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, and the transmitting module and the receiving module may be separate or integrated. Optionally, the transceiver module may be interchangeable with the transceiver.

[0234] In some embodiments, the processing module can be a single module or can include multiple submodules. Optionally, the multiple submodules respectively execute all or part of the steps required to be executed by the processing module. Optionally, the processing module can be interchangeable with the processor.

[0235] Figure 7A is a schematic diagram of the structure of a communication device 7100 proposed in an embodiment of the present disclosure. Communication device 7100 can be a network device (e.g., an access network device, a core network device, etc.), a terminal (e.g., a user equipment, etc.), a chip, a chip system, or a processor that supports a network device to implement any of the above methods, or a chip, a chip system, or a processor that supports a terminal to implement any of the above methods. Communication device 7100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0236] As shown in FIG7A , the communication device 7100 includes one or more processors 7101. The processor 7101 may be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control a communication device (e.g., a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. The communication device 7100 is used to perform any of the above methods.

[0237] In some embodiments, the communication device 7100 further includes one or more memories 7102 for storing instructions. Optionally, all or part of the memories 7102 may be located outside the communication device 7100.

[0238] In some embodiments, the communication device 7100 further includes one or more transceivers 7103. When the communication device 7100 includes one or more transceivers 7103, the transceiver 7103 performs at least one of the communication steps such as sending and / or receiving in the above method (for example, step 2103 and step 2105, but not limited thereto), and the processor 7101 performs at least one of the other steps (for example, step 2101, step 2102, step 2104, and step 2106, but not limited thereto).

[0239] In some embodiments, a transceiver may include a receiver and / or a transmitter. The receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0240] In some embodiments, the communication device 7100 may include one or more interface circuits 7104. Optionally, the interface circuit 7104 is connected to the memory 7102. The interface circuit 7104 may be configured to receive signals from the memory 7102 or other devices, and may be configured to send signals to the memory 7102 or other devices. For example, the interface circuit 7104 may read instructions stored in the memory 7102 and send the instructions to the processor 7101.

[0241] The communication device 7100 described in the above embodiment may be a network device or a terminal, but the scope of the communication device 7100 described in the present disclosure is not limited thereto, and the structure of the communication device 7100 may not be limited by FIG. 7A. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: (1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data or programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0242] 7B is a schematic diagram of the structure of a chip 7200 proposed in an embodiment of the present disclosure. If the communication device 7100 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 7200 shown in FIG7B , but the present disclosure is not limited thereto.

[0243] The chip 7200 includes one or more processors 7201 , and the chip 7200 is configured to execute any of the above methods.

[0244] In some embodiments, the chip 7200 further includes one or more interface circuits 7202. Optionally, the interface circuit 7202 is connected to the memory 7203. The interface circuit 7202 can be used to receive signals from the memory 7203 or other devices, and can be used to send signals to the memory 7203 or other devices. For example, the interface circuit 7202 can read instructions stored in the memory 7203 and send the instructions to the processor 7201.

[0245] In some embodiments, the interface circuit 7202 executes at least one of the communication steps such as sending and / or receiving in the above method (for example, step S2101, step S2102, step S2103, but not limited thereto), and the processor 7201 executes at least one of the other steps.

[0246] In some embodiments, terms such as interface circuit, interface, transceiver pin, and transceiver may be used interchangeably.

[0247] In some embodiments, the chip 7200 further includes one or more memories 7203 for storing instructions. Alternatively, all or part of the memories 7203 may be located outside the chip 7200.

[0248] The present disclosure also proposes a storage medium having instructions stored thereon. When the instructions are executed on the communication device 7100, the communication device 7100 executes any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a temporary storage medium.

[0249] The present disclosure also provides a program product, which, when executed by the communication device 7100, enables the communication device 7100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0250] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

[0251] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented using software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present disclosure are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer program can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a high-density digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0252] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0253] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0254] The above description is merely a specific embodiment of the present disclosure, but the scope of protection of the present disclosure is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this disclosure should be included in the scope of protection of the present disclosure. Therefore, the scope of protection of the present disclosure should be based on the scope of protection of the claims.

Claims

1. An information processing method, characterized in that: The method is executed by a terminal, and includes: Sending first information to a network device, where the first information is used to indicate a sending attribute corresponding to each QoS flow in at least one quality of service QoS flow; receiving second information sent by the network device, where the second information is used to indicate a mapping relationship between the at least one QoS flow and a sidelink SL radio bearer RB, and the second information is determined by the network device based on the first information; Based on the second information, a mapping relationship between the at least one QoS flow and the SL RB is determined, wherein the sending attributes corresponding to the QoS flows mapped to the same SL RB are the same.

2. The method according to claim 1, characterized in that The at least one QoS flow is associated with the same layer 2 identifier.

3. The method according to claim 1 or 2, characterized in that: The terminal is in a radio resource control RRC connected state.

4. The method according to any one of claims 1 to 3, characterized in that: The first information is included in the sidelink terminal information SUI.

5. The method according to any one of claims 1 to 4, characterized in that: The transmission attributes include backward compatibility and non-backward compatibility.

6. The method according to claim 5, characterized in that The method further comprises: An association relationship between the at least one QoS flow and the sending attribute is obtained from a high layer.

7. The method according to claim 6, characterized in that The method further comprises: It is determined that the sending attribute corresponding to the QoS flow without associated sending attribute is backward compatible, or it is determined that the sending attribute corresponding to the QoS flow without associated sending attribute is not backward compatible.

8. The method according to any one of claims 1 to 7, characterized in that: The method further comprises: It is determined to use a single carrier to send the SL RB, wherein a sending attribute of at least one QoS flow mapped to the SL RB is backward compatible, and the single carrier is a traditional carrier.

9. The method according to any one of claims 1 to 7, characterized in that: The method further comprises: Determine to use a packet data convergence protocol PDCP multiplexing mechanism to send the SL RB, wherein a sending attribute of at least one QoS flow mapped to the SL RB is backward compatible, and at least one of the carriers used by the PDCP multiplexing mechanism is a traditional carrier.

10. An information processing method, characterized in that: The method is performed by a network device, and the method includes: receiving first information sent by a terminal, where the first information is used to indicate a sending attribute corresponding to each QoS flow in at least one quality of service QoS flow; Based on the first information, determine second information, where the second information is used to indicate a mapping relationship between the at least one QoS flow and a sidelink SL radio bearer RB; The second information is sent to the terminal, where the second information is used to determine a mapping relationship between the at least one QoS flow and the SL RB, wherein the sending attributes corresponding to the QoS flows mapped to the same SL RB are the same.

11. The method according to claim 10, characterized in that The at least one QoS flow is associated with the same layer 2 identifier.

12. The method according to claim 10 or 11, characterized in that: The terminal is in a radio resource control RRC connected state.

13. The method according to any one of claims 10 to 12, characterized in that: The first information is included in the sidelink terminal information SUI.

14. The method according to any one of claims 10 to 13, characterized in that: The transmission attributes include backward compatibility and non-backward compatibility.

15. An information processing method, characterized in that: The method comprises: The terminal sends first information to the network device, where the first information is used to indicate a sending attribute corresponding to each QoS flow in at least one quality of service QoS flow; The network device determines second information based on the first information, where the second information is used to indicate a mapping relationship between the at least one QoS flow and a sidelink SL radio bearer RB; The network device sends the second information to the terminal; The terminal determines a mapping relationship between the at least one QoS flow and the SL RB based on the second information, wherein the QoS flows mapped to the same SL RB have the same sending attributes.

16. The method according to claim 15, characterized in that The at least one QoS flow is associated with the same layer 2 identifier.

17. The method according to claim 15 or 16, characterized in that The terminal is in a radio resource control RRC connected state.

18. The method according to any one of claims 15 to 17, characterized in that: The first information is included in the sidelink terminal information SUI.

19. The method according to any one of claims 15 to 18, characterized in that: The transmission attributes include backward compatibility and non-backward compatibility.

20. The method according to claim 19, characterized in that The method further comprises: The terminal obtains the association relationship between the at least one QoS flow and the sending attribute from a high layer.

21. The method according to claim 20, characterized in that The method further comprises: The terminal determines that the transmission attribute corresponding to the QoS flow without associated transmission attribute is backward compatible, or determines that the transmission attribute corresponding to the QoS flow without associated transmission attribute is not backward compatible.

22. The method according to any one of claims 15 to 21, characterized in that: The method further comprises: The terminal determines to use a single carrier to send the SL RB, wherein a sending attribute of at least one QoS flow mapped to the SL RB is backward compatible, and the single carrier is a traditional carrier.

23. The method according to any one of claims 15 to 21, characterized in that: The method further comprises: The terminal determines to use a packet data convergence protocol PDCP multiplexing mechanism to send the SL RB, wherein a sending attribute of at least one QoS flow mapped to the SL RB is backward compatible, and at least one of the carriers used by the PDCP multiplexing mechanism is a traditional carrier.

24. A terminal, characterized in that: The terminal comprises: A transceiver module, configured to send first information to a network device, wherein the first information is used to indicate a sending attribute corresponding to each QoS flow in at least one quality of service QoS flow; The transceiver module is further used to receive second information sent by the network device, where the second information is used to indicate a mapping relationship between the at least one QoS flow and the sidelink SL radio bearer RB, and the second information is determined by the network device based on the first information; A processing module is used to determine a mapping relationship between the at least one QoS flow and the SL RB based on the second information, wherein the sending attributes corresponding to the QoS flows mapped to the same SL RB are the same.

25. A network device, characterized in that: The network equipment includes: A transceiver module, configured to receive first information sent by a terminal, wherein the first information is used to indicate a sending attribute corresponding to each QoS flow in at least one quality of service QoS flow; A processing module, configured to determine second information based on the first information, wherein the second information includes a mapping relationship between the at least one QoS flow and a sidelink SL radio bearer RB; The transceiver module is also used to send the second information to the terminal, and the second information is used to determine the mapping relationship between the at least one QoS flow and the SL RB, wherein the sending attributes corresponding to one or more QoS flows mapped to the same SL RB are the same.

26. A terminal, characterized in that: The terminal comprises: one or more processors; The terminal is used to execute the information processing method according to any one of claims 1 to 9.

27. A network device, characterized in that: The network equipment includes: one or more processors; Wherein, the network device is used to execute the information processing method described in any one of claims 10-14.

28. A communication system, characterized in that: It comprises a terminal and a network device, wherein the terminal is configured to implement the positioning measurement method according to any one of claims 1 to 9, and the network device is configured to implement the information processing method according to any one of claims 10 to 14.

29. A storage medium storing instructions, characterized in that: When the instruction is executed on a communication device, the communication device is caused to execute the information processing method according to any one of claims 1 to 9 or 10 to 14.

Images