[go: up one dir, main page]

WO2025091514A1 - Procédé et appareil de traitement d'informations - Google Patents

Procédé et appareil de traitement d'informations Download PDF

Info

Publication number
WO2025091514A1
WO2025091514A1 PCT/CN2023/129791 CN2023129791W WO2025091514A1 WO 2025091514 A1 WO2025091514 A1 WO 2025091514A1 CN 2023129791 W CN2023129791 W CN 2023129791W WO 2025091514 A1 WO2025091514 A1 WO 2025091514A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
qos flow
terminal
sending
network device
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2023/129791
Other languages
English (en)
Chinese (zh)
Inventor
赵力
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Xiaomi Mobile Software Co Ltd
Original Assignee
Beijing Xiaomi Mobile Software Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Xiaomi Mobile Software Co Ltd filed Critical Beijing Xiaomi Mobile Software Co Ltd
Priority to CN202380011815.7A priority Critical patent/CN117882402A/zh
Priority to PCT/CN2023/129791 priority patent/WO2025091514A1/fr
Publication of WO2025091514A1 publication Critical patent/WO2025091514A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/80—Responding to QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]

Definitions

  • the present disclosure relates to the field of communication technology, and in particular to an information processing method and device.
  • the sidelink (SL) communication method is introduced.
  • carrier aggregation (CA) is introduced.
  • Tx profile the transmission attribute (Tx profile) is introduced to indicate the version number of the service.
  • the embodiments of the present disclosure provide an information processing method and device.
  • the first aspect of the present disclosure proposes an information processing method, which includes: 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; receiving second information sent by the network device, the second information being used to indicate a mapping relationship between at least one QoS flow and a side link SL radio bearer RB, the second information being determined by the network device based on the first information; based on the second information, determining a 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.
  • 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 radio 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.
  • the third aspect embodiment of the present disclosure proposes an information processing method, which includes: a terminal sends first information to a network device, 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, the second information is used to indicate the mapping relationship between at least one QoS flow and a side link SL radio 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.
  • the fourth aspect embodiment of the present disclosure proposes a terminal, comprising: a transceiver module, used to send first information to a network device, 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, 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; a processing module, 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 the QoS flows mapped to the same SL RB are the same.
  • 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 also 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.
  • the solution proposed in the embodiment of the present disclosure is as follows: by sending first information to a network device, 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, the second information includes 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; based on the second information, determining a 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 radio bearer based on the attributes of the service, so that the QoS flows included in the configuration of the sidelink radio bearer obtained by the terminal are associated with the same sending attributes, thereby effectively ensuring backward compatibility of service flows and improving the reliability of service transmission.
  • FIG1A is a schematic diagram of the architecture of a communication system provided by an embodiment of the present disclosure.
  • FIG1B is a schematic diagram of a sidelink communication network state provided by an embodiment of the present disclosure.
  • FIG1C is a schematic diagram of a PDCP multiplexing mechanism provided by an embodiment of the present disclosure.
  • FIG2A is an interactive schematic diagram of an information processing method provided by an embodiment of the present disclosure.
  • 3A-3B are flowchart diagrams of an information processing method provided by an embodiment of the present disclosure.
  • FIG4A is a flow chart of an information processing method provided by an embodiment of the present disclosure.
  • FIG5 is a flow chart of an information processing method provided by an embodiment of the present disclosure.
  • FIG6A is a schematic diagram of the structure of a terminal provided by an embodiment of the present disclosure.
  • FIG6B is a schematic diagram of the structure of a network device provided by an embodiment of the present disclosure.
  • FIG7A is a schematic diagram of the structure of a communication device provided by an embodiment of the present disclosure.
  • FIG. 7B is a schematic diagram of the structure of a chip provided in an embodiment of the present disclosure.
  • the embodiments of the present disclosure provide an information processing method and device.
  • an embodiment of the present disclosure provides an information processing method, the method comprising:
  • 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;
  • a mapping relationship between 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.
  • the network is enabled to configure the corresponding wireless bearer based on the attributes of the service, so that the QoS flow included in the configuration of the sidelink wireless bearer obtained by the terminal is associated with the same sending attributes, effectively ensuring the backward compatibility of the service flow and improving the reliability of service transmission.
  • At least one QoS flow is associated with the same layer 2 identifier.
  • the QoS flows included in the configuration of the SL RB correspond to the same L2 ID, which improves the compatibility of the solution.
  • the terminal is in a radio resource control RRC connected state.
  • 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 included 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.
  • the first information is included in the sidelink terminal information SUI.
  • sending the information indicating the sending 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.
  • the sending attributes include backward compatibility and non-backward compatibility.
  • the network is enabled to determine whether each service is backward compatible, and configure the corresponding wireless bearer based on the attribute, so that the QoS flow included 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.
  • the method further includes:
  • the terminal can determine the sending attributes corresponding to each QoS flow based on the high-level configuration.
  • the sending attributes of the QoS flow can be flexibly determined, thereby effectively improving the compatibility of services and enhancing transmission efficiency.
  • the method further includes:
  • the QoS flow contained in the configuration of the sidelink wireless bearer obtained by the terminal is associated with the same sending attribute and the sending attribute is backward compatible, it can be determined to use a traditional carrier to send the wireless 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.
  • the method further includes:
  • the carrier used for transmission using the multiplexing mechanism includes a traditional carrier, thereby 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.
  • an embodiment of the present disclosure provides an information processing method, the method comprising:
  • Second information Based on the first information, determine second 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;
  • the network is enabled to configure the corresponding wireless bearer based on the attributes of the service, so that the QoS flow included in the configuration of the sidelink wireless bearer obtained by the terminal is associated with the same sending attributes, effectively ensuring the backward compatibility of the service flow and improving the reliability of service transmission.
  • At least one QoS flow is associated with the same layer 2 identifier.
  • the terminal is in a radio resource control RRC connected state.
  • the first information is included in the sidelink terminal information SUI.
  • the sending attributes include backward compatibility and non-backward compatibility.
  • an embodiment of the present disclosure provides an information processing method, the method comprising:
  • 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 at least one QoS flow and a sidelink SL radio bearer RB;
  • the network device sends second information to the terminal
  • the terminal determines a 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.
  • the network is enabled to configure the corresponding wireless bearer based on the attributes of the service, so that the QoS flow included in the configuration of the sidelink wireless bearer obtained by the terminal is associated with the same sending attributes, effectively ensuring the backward compatibility of the service flow and improving the reliability of service transmission.
  • At least one QoS flow is associated with the same layer 2 identifier.
  • the terminal is in a radio resource control RRC connected state.
  • the first information is included in the sidelink terminal information SUI.
  • the sending attributes include backward compatibility and non-backward compatibility.
  • the method further includes:
  • the terminal obtains, from a high layer, an association relationship between at least one QoS flow and a sending attribute;
  • 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.
  • the method further includes:
  • the terminal determines to use a single carrier to send 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.
  • the method further includes:
  • 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.
  • 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.
  • 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.
  • an embodiment of the present disclosure provides a terminal, the terminal comprising: one or more processors; wherein the terminal Used to execute the first aspect and the optional implementation manner of the first 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.
  • 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.
  • an embodiment of the present disclosure proposes a storage medium, which stores instructions.
  • the communication device executes the method described in the first aspect and the optional implementation method of the first aspect, the second aspect and the optional implementation method of the second aspect.
  • an embodiment of the present disclosure proposes a program product.
  • 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.
  • 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.
  • an embodiment of the present disclosure provides a chip or a chip system.
  • the chip or chip system includes a processing circuit configured to execute the method described in accordance with the first aspect and the optional implementation of the first aspect, the second aspect and the optional implementation of the second aspect.
  • the information processing method, information processing method, communication method, etc. can be replaced with each other, the information processing device, information processing device, communication device, etc., can be replaced with each other, and the information processing system, communication system, etc., can be replaced with each other.
  • each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined.
  • 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.
  • 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 of the steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.
  • elements expressed in the singular form such as “a”, “an”, “the”, “above”, “said”, “aforementioned”, “this”, etc., may mean “one and only one", or “one or more”, “at least one”, etc.
  • the noun after the article may be understood as a singular expression or a plural expression.
  • plurality refers to two or more.
  • the terms "at least one of”, “one or more”, “a plurality of”, “multiple”, etc. can be used interchangeably.
  • "at least one of A and B", “A and/or B", “A in one case, B in another case”, “in response to one case A, in response to another case B”, etc. may include the following technical solutions according to 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); in some embodiments, A and B (both A and B are executed). When there are more branches such as A, B, C, etc., the above is also similar.
  • the recording method of "A or B” may include the following technical solutions according to 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).
  • A A is executed independently of B
  • B B is executed independently of A
  • execution is selected from A and B (A and B are selectively executed).
  • 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 restrictions on the position, order, priority, quantity or content of the description objects.
  • the statement of the description object refers to the description in the context of the claims or embodiments, and should not constitute unnecessary restrictions due to the use of prefixes.
  • 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”
  • the "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”.
  • 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”.
  • the number of description objects is not limited by the ordinal number, and can be one or more. Taking the "first device” as an example, the number of "devices” can be one or more.
  • the objects modified by different prefixes may be the same or different. For example, if the description object is "device”, then the “first device” and the “second device” may be the same device or different devices, and their types may be the same or different. For another example, if the description object is "information”, then the "first information” and the “second information” may be the same information or different information, and their contents may be the same or different.
  • “including A”, “comprising A”, “used to indicate A”, and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.
  • 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 lower 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”, “no more than”, “lower than”, “lower than or equal to”, “not higher than”, and “below” can be replaced with each other.
  • devices and equipment may be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they may also be understood as “equipment”, “device”, “circuit”, “network element”, “node”, “function”, “unit”, “section”, “system”, “network”, “chip”, “chip system”, “entity”, “subject”, etc.
  • network can be interpreted as devices included in the network, such as access network equipment, core network equipment, etc.
  • access network 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 (node)", “access point”"transmission point (TP)””reception point (RP)”"transmission and/or reception point (TRP)""panel”"antennapanel””antennaarray”"cell”"macrocell”"smallcell”"femtocell”"picocell”"sector”""cellgroup”"servingcell”"carrier”"componentcarrier”"bandwidth part (BWP)” and the like.
  • RAN device radio access network device
  • BS base station
  • RRP radio reception point
  • TRP transmission and/or reception point
  • terminal or “terminal device” may be referred to as "user equipment (UE)", “user terminal (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.
  • UE user equipment
  • MS mobile station
  • MT mobile terminal
  • acquisition of data, information, etc. may comply with the laws and regulations of the country where the data is obtained.
  • data, information, etc. may be obtained with the user's consent.
  • each element, each row, or each column in the table of the embodiments of the present disclosure may be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns may also be implemented as an independent embodiment.
  • FIG1A is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.
  • a communication system 100 includes a terminal 101 and a network device 102 .
  • 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 (Pad), 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 (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 (smart grid), a wireless terminal device in transportation safety (transportation safety), a wireless terminal device in a smart city (smart city), a wireless terminal device in a smart home (smart home), and at least one of a reduced capability (RedCap) terminal, but is not limited to these.
  • a mobile phone a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented
  • 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 Node B (eNB) in a 5G communication system, a next generation evolved Node B (ng-eNB), a next generation Node B (gNB), a node B (NB), a home node B (HNB), a home evolved node B (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.
  • eNB evolved Node B
  • ng-eNB next generation evolved No
  • the network device may be composed of a centralized unit (central unit, CU) and a distributed unit (distributed unit, DU), wherein the CU may also be called a control unit (control unit).
  • the CU-DU structure may be used to split the protocol layer of the access network device, with some functions of the protocol layer being centrally controlled by the CU, and the remaining part or all of the functions of the protocol layer being distributed in the DU, and the DU being centrally controlled by the CU, but not limited to this.
  • 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.
  • a person of ordinary skill in the art 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.
  • the following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1 , or part of the subject, but are not limited thereto.
  • the subjects shown in FIG1 are examples, and the communication system may include all or part of the subjects in FIG1 , or may include other subjects other than FIG1 , and the number and form of the subjects are arbitrary, and the subjects may be physical or virtual, and the connection relationship between the subjects is an example, and the subjects may be connected or disconnected, and the connection may be in any manner, and may be a direct connection or an indirect connection, and may be a wired connection or a wireless connection.
  • the embodiments of the present disclosure may be applied to information processing systems, Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, fourth generation mobile communication systems (4G), fifth generation mobile communication systems (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 (FRA), new radio access technology (RAT), new radio (NR), new radio access (NX), future generation radio access (NX), new radio access technology (NXP), new radio access technology (NXP), new radio access technology (NXP-RAT), new radio (NR), new radio access (NXP-RAT), new radio access technology (NXP-RAT), new radio access technology (NXP-RAT), new radio (NR), new radio access (NXP-NXP), new radio access technology (NXP-NXP), new radio access technology (NXP-NXP), new radio
  • GSM Global System for Mobile communications
  • UMB Ultra Mobile Broadband
  • IEEE 802.11 Wi-Fi (registered trademark)
  • IEEE 802.16 WiMAX (registered trademark)
  • IEEE 802.20 Ultra-WideBand (UWB)
  • PLMN Public Land Mobile Network
  • D2D Device to Device
  • M2M Machine to Machine to Machine
  • IoT Internet of Things
  • V2X Vehicle-to-Everything
  • a number of systems may also be applied in combination (for example, combination of LTE or LTE-A with 5G, and the like).
  • a sidelink (SL) communication mode in order to support direct communication between terminals, a sidelink (SL) communication mode is introduced.
  • the interface between terminals is PC-5 (a bottom-level direct cellular communication protocol interface).
  • Terminal devices in network coverage (in coverage) and out of network coverage (out of coverage, OOC) can perform sidelink communication.
  • a first terminal in coverage can perform sidelink communication with a second terminal in coverage.
  • a first terminal in coverage can perform sidelink communication with a second terminal in OC.
  • a first terminal in coverage can perform sidelink communication with a second terminal in OC.
  • a first terminal in coverage can perform sidelink communication with a second terminal in OC.
  • a first terminal in coverage can perform sidelink communication with a second terminal in OC.
  • the terminal device in coverage can be in a radio resource control (Radio Resources Control, RRC) connected state (CONNECETED) or an RRC idle state (IDLE) or an RRC inactive state (INACTIVE).
  • RRC Radio Resources Control
  • IDLE an RRC idle state
  • IACTIVE an RRC inactive state
  • the sidelink communication performed by the terminal device includes three transmission modes, unicast, multicast and broadcast.
  • LTE V2X Transmission properties are defined to indicate the version number of the service.
  • R17 NR V2X introduces the discontinuous reception (DRX) feature.
  • TxProfile is defined for broadcast/multicast services according to the layer 2 (Layer 2, L2) identifier (ID) granularity. TxProfile is used to indicate whether the associated broadcast/multicast service supports DRX.
  • the transmitting terminal determines that there is a broadcast/multicast service that supports the DRX attribute, it can assume that the receiving terminal has enabled DRX and only sends 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 the DRX attribute, that is, it only wakes up during the "active" time to listen to the data of the broadcast/multicast service.
  • CA carrier aggregation
  • LTE V2X already supports sidelink carrier aggregation technology.
  • one of the goals of NR sidelink carrier aggregation is to ensure backward compatibility, that is, to ensure that old version terminals of R16/R17 can receive broadcast/multicast services sent by R18 terminals that support carrier aggregation.
  • a packet data convergence protocol (PDCP) duplication mechanism is introduced, also known as packet duplication, that is, a data packet is sent repeatedly.
  • the above mechanism is used for repeated transmission, which can improve the reliability of data packet transmission, reduce the delay of repeated transmission, and meet the requirements of ultra-reliable low-latency communications (URLLC).
  • URLLC ultra-reliable low-latency communications
  • a PDCP data packet will be transmitted to a radio link control layer (Radio Link Control, RLC) entity, and the RLC entity will send it to the media access control layer (Medium Access Control, MAC) layer after processing, and the MAC layer will complete the data scheduling.
  • RLC Radio Link Control
  • MAC Media Access Control
  • a PDCP packet will be transmitted to at least two RLC entities, for example, the primary RLC entity and the secondary RLC entity shown in Figure 1C.
  • the two RLC entities will process the packets independently and transmit the processed packets to the MAC layer. From the perspective of the MAC layer, these are two independent packets.
  • the MAC cannot identify whether this is a packet transmitted by PDCP duplication.
  • the MAC layer only needs to schedule according to the algorithm.
  • the protocol requires that the two packets of PDCP duplication be transmitted on different logical channels (Logical Channel, LCH) in different cells, for example, the primary LCH and secondary LCH shown in Figure 1C.
  • LCH Logical Channel
  • 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.
  • the network device can configure a SL radio bearer (RadioBearer, RB) for a UE in a radio resource control (Radio Resources Control, RRC) connected state through a sidelink radio bearer configuration SL-RadioBearerConfig, where 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.
  • SL-RadioBearerConfig configuration includes a service data adaptation protocol (Service Data Adaptation Protocol, SDAP) configuration
  • SDAP configuration includes a quality of service (Quality of Service, QoS) flow associated with this SL RB.
  • the network device may map backward-compatible QoS flows and non-backward-compatible QoS flows into one SL RB.
  • 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).
  • the existing carrier the existing carrier supported by R16/R17.
  • FIG2A is an interactive schematic 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, and the method includes:
  • Step S2101 Terminal 101 obtains a sending attribute associated with at least one QoS flow.
  • the transmit profile is configured at the granularity of the Quality of Service (QoS) flow.
  • terminal 101 obtains an association relationship between at least one QoS flow and a sending attribute from a higher layer of terminal 101 .
  • the access stratum (AS) of terminal 101 obtains the association relationship between at least one QoS flow and the sending attribute from the higher layer of terminal 101.
  • the above-mentioned sending attributes are backward compatible or non-backward compatible.
  • the QoS flow with a backward-compatible sending attribute refers to a QoS flow that can be received by an old version terminal of R16/R17.
  • Step S2102 Terminal 101 determines the sending attribute corresponding to each QoS flow.
  • the terminal 101 determines the sending attribute corresponding to each QoS flow based on the association relationship between at least one QoS flow and the sending attribute obtained from a higher layer of the terminal 101 .
  • the terminal 101 determines that the transmission attribute corresponding to the QoS flow without associated transmission attribute is backward compatible.
  • the terminal 101 determines that the transmission attribute corresponding to the QoS flow without associated transmission attribute is non-backward compatible.
  • Step S2103 Terminal 101 sends first information.
  • the network device 102 receives the first information.
  • the first information is used to indicate a sending attribute corresponding to each QoS flow in the at least one QoS flow.
  • 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.
  • 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” and the like.
  • the above-mentioned first information is included in the sidelink terminal information (Sidelink UE Information, SUI).
  • SUI Sidelink UE Information
  • the above-mentioned first information is included in terminal assistance information (UE Assistance Information, UAI).
  • UE Assistance Information UAI
  • the at least one QoS flow indicated by the first information is at least one QoS flow associated with the same layer 2 identifier.
  • the first information indicates a sending attribute of at least one QoS flow associated with the same layer 2 identifier.
  • the first information indicates the sending attributes of at least one QoS flow associated with each of the multiple target layer 2 addresses.
  • the terminal 101 has three target layer 2 addresses ABC, and the first information may include the sending attributes of at least one QoS flow associated with the target address A, the sending attributes of at least one QoS flow associated with the target address B, and the sending attributes of at least one QoS flow associated with the target address C.
  • the first information indicates the identifier of each QoS flow and the sending attributes of the QoS flow;
  • the first information indicates the identifier of each QoS flow and the sending attributes of the QoS flow;
  • the first information indicates the identifier of each QoS flow and the sending attributes of the QoS flow.
  • terminal 101 is in a radio resource control (RRC) connected state.
  • RRC radio resource control
  • Step S2104 the network device 102 determines the second information.
  • the network device 102 can determine the second information based on the first information.
  • the second information includes a mapping relationship between the at least one QoS flow and a sidelink (SL) radio bearer (RB).
  • SL sidelink
  • RB radio bearer
  • 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.
  • one or more QoS flows with a backward compatible transmission attribute are mapped to one or more SLRBs;
  • one or more QoS flows with a non-backward compatible transmission attribute are mapped to one or more SLRBs.
  • QoS flows with different transmission attributes are mapped to different SLRBs.
  • 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.
  • the second information includes one or more SLRB configurations.
  • QoS flows with different sending attributes cannot be mapped to the same SL RB.
  • Step S2105 the network device 102 sends the second information.
  • the network device 102 sends the second information to the terminal 101 via dedicated RRC signaling.
  • terminal 101 receives the second information mentioned above.
  • the second information is used by the terminal 101 to determine the mapping relationship between the above-mentioned at least one QoS flow and the SL RB.
  • Step S2106 the terminal 101 determines the mapping relationship between the above-mentioned at least one QoS flow and the SL RB.
  • 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 sending attributes corresponding to one or more QoS flows mapped to the same SL RB are the same.
  • the terminal 101 determines, based on the second information, one or more SL RBs whose sending attributes are backward compatible with at least one QoS flow mapping, and determines one or more SL RBs whose sending attributes are non-backward compatible with at least one QoS flow mapping.
  • QoS flows with different transmission attributes are mapped to different SLRBs.
  • one or more SL RBs mapped to at least one QoS flow with a backward-compatible attribute may be transmitted using a single carrier, where the single carrier is a legacy carrier, also referred to as a traditional carrier.
  • the legacy carrier refers to an SL carrier supported by an R16/R17 terminal.
  • one or more SL RBs mapped to at least one QoS flow with a sending attribute of backward compatibility 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.
  • carrier In some embodiments, the terms “carrier”, “band”, “frequency” and the like can be used interchangeably.
  • the names of information, etc. are not limited to the names described in the embodiments, and include “information”, “message”, “signal”, “signaling”, “report”, “configuration”, “indication”, “instruction”, “command”,
  • the terms “channel”, “parameter”, “domain”, “field”, “symbol”, “symbol”, “code element”, “codebook”, “codeword”, “codepoint”, “bit”, “data”, “program”, “chip” and the like are interchangeable.
  • the names of information, etc. are not limited to the names recorded in the embodiments, and terms such as “information”, “message”, “signal”, “signaling”, “report”, “configuration”, “indication”, “instruction”, “command”, “channel”, “parameter”, “domain”, “field”, “symbol”, “symbol”, “code element”, “codebook”, “codeword”, “codepoint”, “bit”, “data”, “program”, and “chip” can be used interchangeably.
  • the terms “physical downlink shared channel (PDSCH)”, “DL data” and the like can be interchangeable with each other, and the terms “physical uplink shared channel (PUSCH)”, “UL data” and the like can be interchangeable with each other.
  • radio wireless
  • RAN radio access network
  • AN access network
  • RAN-based and the like
  • RB resource block
  • PRB physical resource block
  • SCG resource element group
  • REG resource element group
  • PRB pair RB pair
  • RE resource element
  • obtain can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from high levels, obtaining by self-processing, autonomous implementation, etc.
  • terms such as “certain”, “preset”, “preset”, “set”, “indicated”, “some”, “any”, and “first” can be interchangeable, and "specific A”, “preset A”, “preset A”, “set A”, “indicated A”, “some A”, “any A”, and “first A” can be interpreted as A pre-defined in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., and can also be interpreted as specific A, some A, any A, or first A, etc., but is not limited to this.
  • the determination or judgment can be performed by a value represented by 1 bit (0 or 1), 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 to this.
  • the communication method involved in the embodiments of the present disclosure may include at least one of steps S2101 to S2106.
  • step 2101+2102 may be implemented as an independent embodiment
  • step 2103 may be implemented as an independent embodiment
  • step 2101+2102+2103 may be implemented as an independent embodiment
  • step 2103+2104 may be implemented as an independent embodiment
  • step 2103+2104+2105 may be implemented as an independent embodiment
  • step 2105+2106 may be implemented as an independent embodiment
  • step 2103+2104+2105+2106 may be implemented as an independent embodiment
  • step 2101+2102+2103+2104+2105+2106 may be implemented as an independent embodiment, and the like, but not limited thereto.
  • steps S2101-2102 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • 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 a terminal 101 and includes:
  • Step S3101 Obtain sending attributes associated with at least one QoS flow.
  • step S3101 can refer to the optional implementation of step S2101 in FIG. 2A and other related parts in the embodiment involved in FIG. 2A , which will not be described in detail here.
  • Step S3102 determine the sending attributes corresponding to each QoS flow.
  • step S3102 can refer to the optional implementation of step S2102 in FIG. 2A and other related parts in the embodiment involved in FIG. 2A , which will not be described in detail here.
  • step S3103 can refer to the optional implementation of step S2103 in FIG. 2A and other related parts in the embodiment involved in FIG. 2A , which will not be described in detail here.
  • Step S3104 receiving the second information.
  • step S3104 can refer to the optional implementation of step S2105 in FIG. 2A and other related parts in the embodiment involved in FIG. 2A , which will not be described in detail here.
  • Step S3105 determine the mapping relationship between the above at least one QoS flow and SL RB.
  • step S3105 can refer to the optional implementation of step S2106 in FIG. 2A and other related parts in the embodiment involved in FIG. 2A , which will not be described in detail here.
  • the communication method involved in the embodiments of the present disclosure may include at least one of steps S3101 to S3105.
  • step 3101+3102 may be implemented as an independent embodiment
  • step 3103 may be implemented as an independent embodiment
  • step 3101+3102+3103 may be implemented as an independent embodiment
  • step 3103+3104 may be implemented as an independent embodiment
  • step 3105 may be implemented as an independent embodiment
  • step 3103+3104+3105 may be implemented as an independent embodiment
  • step 3101+3102+3103+3104+3105 may be implemented as an independent embodiment, etc., but the present invention is not limited thereto.
  • FIG3B is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG3B , the present disclosure embodiment relates to an information processing method, which is executed by terminal 101 and includes:
  • Step S3201 sending the first information.
  • step S3201 can refer to step S2103 of FIG. 2A , the optional implementation 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.
  • the first information is determined based on the transmission attribute corresponding to the determined at least one QoS flow.
  • the optional implementation method thereof can refer to the optional implementation methods of 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 will not be repeated here.
  • the first information is used by the network device 102 to determine the second information based on the first information.
  • the network device 102 determines the second information based on the first information.
  • Step S3202 receiving second information.
  • 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.
  • Step S3203 determine the mapping relationship between the above at least one QoS flow and SL RB.
  • 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.
  • the communication method involved in the embodiments of the present disclosure may include at least one of steps S3201 to S3203.
  • step 3201 may be implemented as an independent embodiment
  • steps 3201+3202 may be implemented as an independent embodiment
  • step 3203 may be implemented as an independent embodiment
  • steps 3201+3202+3203 may be implemented as an independent embodiment, etc., but the present invention is not limited thereto.
  • 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 a network device 102 and includes:
  • Step S4101 receiving first information.
  • step S4101 can refer to the optional implementation of step S2103 in FIG. 2A and other related parts in the embodiment involved in FIG. 2A , which will not be described in detail here.
  • the first information is sent by the terminal 101 based on the determined transmission attribute corresponding to at least one QoS flow.
  • the optional implementation method thereof can refer to the optional implementation method of steps S2101-S2102 of FIG. 2A and other related parts of the embodiment involved in FIG. 2A, which will not be repeated here.
  • the second information is used by the terminal 101 to determine a mapping relationship between at least one QoS flow and an SL RB.
  • the optional implementation method thereof can refer to the optional implementation method of step S2106 of FIG. 2A and other related parts of the embodiment involved in FIG. 2A , which will not be described in detail here.
  • the communication method involved in the embodiments of the present disclosure may include at least one of steps S4101 to S4103.
  • step 4101 may be implemented as an independent embodiment
  • steps 4101+4102 may be implemented as an independent embodiment
  • step 4103 may be implemented as an independent embodiment
  • steps 4101+4102+4103 may be implemented as an independent embodiment, etc., but the present invention is not limited thereto.
  • FIG5 is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG5, the method involved in the embodiment of the present disclosure is used in a communication system 100, and the method includes:
  • 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.
  • 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.
  • Step S5103 the network device 102 sends the second information to the terminal 101.
  • step S5104 the terminal 101 determines the mapping relationship between the 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.
  • steps S5101-S5104 can refer to the steps in any embodiment or any multiple embodiments in the embodiments of Figures 2A, 3A-3B, and 4A above, and other related parts in the embodiments involved in Figures 2A, 3A-3B, and 4A.
  • 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.
  • 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 implementation modes or other examples.
  • tx profile is configured at the QoS flow granularity.
  • tx profile is configured according to QoS flow granularity, and the high-level layer indicates the mapping relationship between AS layer QoS flow and tx profile. If a QoS flow has no associated tx profile, the Qos flow is considered to be backward compatible; if a QoS flow has no associated tx profile, the Qos flow is considered to be non-backward compatible.
  • the UE reports the tx profile associated with the QoS flow to the network device.
  • the UE reports the tx profile associated with the QoS flow to the network device through the SUI.
  • the UE reports the tx profile corresponding to the QoS flow associated with the L2 ID to the network device. Specifically, for one L2 ID, the UE reports the tx profile corresponding to one or more QoS flows associated with the L2 ID to the network device.
  • the UE is in an RRC connected state.
  • the UE may operate in mode 1 or the UE operates in mode 2 and is in an RRC connected state.
  • 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 properties of at least one QoS flow and/or the identifier of at least one QoS flow, and the attributes of the IE may be optional.
  • IE information element
  • the network maps QoS flows with the same tx profile attributes to the same RB based on the SUI.
  • QoS flows with the same tx profile can be mapped to the same RB.
  • QoS flows with different tx profiles cannot be mapped to the same RB.
  • the embodiments of the present disclosure also propose a device for implementing any of the above methods, for example, a device is proposed, the above device includes a unit or module for implementing each step performed by the terminal in any of the above methods.
  • a device is also proposed, including a unit or module for implementing each step performed by a network device (such as an access network device, a core network function node, a core network device, etc.) in any of the above methods.
  • a network device such as an access network device, a core network function node, a core network device, etc.
  • the division of the units or modules in the above device is only a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated.
  • the units or modules in the device can be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions.
  • the processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the units or modules of the above device, where the processor is, for example, a general-purpose processor. For example, a central processing unit (CPU) or a microprocessor, and the memory is a memory in the device or a memory outside the device.
  • CPU central processing unit
  • microprocessor a microprocessor
  • the unit or module in the device can be implemented in the form of a hardware circuit, and the functions of some or all of the units or modules can be realized by designing the hardware circuit.
  • the above hardware circuit can be understood as one or more processors; for example, in one implementation, the above hardware circuit is an application-specific integrated circuit (ASIC), and the functions of some or all of the above units or modules are realized by designing the logical relationship of the components in the circuit; for example, in another implementation, the above hardware circuit can be realized by a programmable logic device (PLD), taking a field programmable gate array (FPGA) as an example, which can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by a configuration file, so as to realize the functions of some or all of the above units or modules. All units or modules of the above device can be realized in the form of a processor calling software, or in the form of a hardware circuit, or in part by a processor calling software, and the remaining part is realized in the form of a hardware circuit.
  • the processor is a circuit with signal processing capability.
  • the processor may be a circuit with instruction reading and running capability, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which may be understood as a microprocessor), or a digital signal processor (DSP); in another implementation, the processor may implement certain functions through the logical relationship of a hardware circuit, and the logical relationship of the above hardware circuit may be fixed or reconfigurable, such as a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA.
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • the process of the processor loading a configuration document to implement the hardware circuit configuration may be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules.
  • it can also be a hardware circuit designed for artificial intelligence, which can be understood as ASIC, such as Neural Network Processing Unit (NPU), Tensor Processing Unit (TPU), Deep Learning Processing Unit (DPU), etc.
  • ASIC Neural Network Processing Unit
  • NPU Neural Network Processing Unit
  • TPU Tensor Processing Unit
  • DPU Deep Learning Processing Unit
  • FIG6A is a schematic diagram of the structure of the terminal proposed in an embodiment of the present disclosure.
  • the terminal 6100 may include: at least one of a transceiver module 6101, a processing module 6102, etc.
  • the transceiver module is used to send first information to a network device, and the first information is used to indicate the transmission attribute 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 transmission attributes corresponding to one or more QoS flows mapped to the same SL RB are the same.
  • 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.
  • 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.
  • the 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.
  • FIG6B is a schematic diagram of the structure of a network device proposed in an embodiment of the present disclosure.
  • the network device 6200 may include: a transceiver module 6201.
  • the transceiver module is used to receive first information sent by a terminal, 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 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 a mapping relationship between at least one QoS flow and the SL RB, wherein the mapping
  • the sending attributes of one or more QoS flows directed to the same SL RB are the same.
  • 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.
  • 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.
  • the processing module is used to execute at least one of the other steps (such as step 2104, but not limited to this) performed by the network device 102 in any of the above methods, which will not be repeated here.
  • the transceiver module may include a sending module and/or a receiving module, and the sending module and the receiving module may be separate or integrated.
  • the transceiver module may be interchangeable with the transceiver.
  • the processing module can be a module or include multiple submodules.
  • the multiple submodules respectively execute all or part of the steps required to be executed by the processing module.
  • the processing module can be replaced with the processor.
  • FIG7A is a schematic diagram of the structure of a communication device 7100 proposed in an embodiment of the present disclosure.
  • the communication device 7100 may be a network device (e.g., an access network device, a core network device, etc.), or a terminal (e.g., a user device, etc.), or 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.
  • the communication device 7100 may be used to implement the method described in the above method embodiment, and the details may refer to the description in the above method embodiment.
  • 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 the communication protocol and the communication data
  • the central processing unit may be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute a program, and process the data of the program.
  • the communication device 7100 is used to execute any of the above methods.
  • the communication device 7100 further includes one or more memories 7102 for storing instructions.
  • the memory 7102 may also be outside the communication device 7100.
  • the communication device 7100 further 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, 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, step 2106, but not limited thereto).
  • the transceiver may include a receiver and/or a transmitter, and the receiver and the transmitter may be separate or integrated.
  • the terms such as transceiver, transceiver unit, transceiver, transceiver circuit, etc. may be replaced with each other, the terms such as transmitter, transmission unit, transmitter, transmission circuit, etc. may be replaced with each other, and the terms such as receiver, receiving unit, receiver, receiving circuit, etc. may be replaced with each other.
  • the communication device 7100 may include one or more interface circuits 7104.
  • the interface circuit 7104 is connected to the memory 7102, and the interface circuit 7104 may be used to receive signals from the memory 7102 or other devices, and may be used to send signals to the memory 7102 or other devices.
  • the interface circuit 7104 may read instructions stored in the memory 7102 and send the instructions to the processor 7101.
  • the communication device 7100 described in the above embodiments 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.
  • 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, and 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) an interface; Receivers, terminal devices, intelligent terminal devices, cellular phones, wireless devices, handheld devices, mobile units, vehicle-mounted devices, network devices, cloud devices, artificial intelligence devices, etc.; (6) Others, etc.
  • FIG. 7B is a schematic diagram of the structure of a chip 7200 provided in an embodiment of the present disclosure.
  • the communication device 7100 may be a chip or a chip system
  • the chip 7200 includes one or more processors 7201, and the chip 7200 is used to execute any of the above methods.
  • the chip 7200 further includes one or more interface circuits 7202.
  • 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 the interface circuit 7202 can be used to send signals to the memory 7203 or other devices.
  • the interface circuit 7202 can read instructions stored in the memory 7203 and send the instructions to the processor 7201.
  • 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 to these), and the processor 7201 executes at least one of the other steps.
  • interface circuit interface circuit
  • transceiver pin transceiver
  • the chip 7200 further includes one or more memories 7203 for storing instructions.
  • the memory 7203 may be outside the chip 7200.
  • the present disclosure also proposes a storage medium, on which instructions are stored, and when the instructions are executed on the communication device 7100, the communication device 7100 executes any of the above methods.
  • the storage medium is an electronic storage medium.
  • the storage medium is a computer-readable storage medium, but is not limited to this, and it can also be a storage medium readable by other devices.
  • the storage medium can be a non-transitory storage medium, but is not limited to this, and it can also be a temporary storage medium.
  • the present disclosure also proposes a program product, which, when executed by the communication device 7100, enables the communication device 7100 to execute any of the above methods.
  • the program product is a computer program product.
  • the present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to execute any one of the above methods.
  • the available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a high-density digital video disc (DVD)), or a semiconductor medium (e.g., a solid state disk (SSD)), etc.
  • a magnetic medium e.g., a floppy disk, a hard disk, a magnetic tape
  • an optical medium e.g., a high-density digital video disc (DVD)
  • DVD high-density digital video disc
  • SSD solid state disk

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Sont divulgués dans des modes de réalisation de la présente divulgation un procédé et un appareil de traitement d'informations. Selon la solution prévue par les modes de réalisation de la présente divulgation, le procédé consiste à : envoyer des premières informations à un dispositif de réseau, les premières informations étant utilisées pour indiquer un profil de transmission correspondant à chaque flux de qualité de service (QoS) parmi au moins un flux de QoS ; recevoir des secondes informations envoyées par le dispositif de réseau, les secondes informations étant utilisées pour indiquer une relation de mappage entre ledit au moins un flux QoS et un support radio (RB) de liaison latérale (SL), les secondes informations étant déterminées par le dispositif réseau sur la base des premières informations ; et déterminer la relation de mappage entre ledit au moins un flux de QoS et le RB SL sur la base des secondes informations, les profils de transmission correspondant à un ou plusieurs flux de QoS mappés sur le même RB SL étant identiques. Ainsi, le réseau peut configurer des supports radio particuliers sur la base d'attributs de service, de sorte que les flux de QoS compris dans la configuration RB SL acquise par le terminal sont associés au même profil de transmission, ce qui permet d'assurer efficacement la rétrocompatibilité des flux de service, améliorant la fiabilité de transmission de service.
PCT/CN2023/129791 2023-11-03 2023-11-03 Procédé et appareil de traitement d'informations Pending WO2025091514A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202380011815.7A CN117882402A (zh) 2023-11-03 2023-11-03 信息处理方法及装置
PCT/CN2023/129791 WO2025091514A1 (fr) 2023-11-03 2023-11-03 Procédé et appareil de traitement d'informations

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/129791 WO2025091514A1 (fr) 2023-11-03 2023-11-03 Procédé et appareil de traitement d'informations

Publications (1)

Publication Number Publication Date
WO2025091514A1 true WO2025091514A1 (fr) 2025-05-08

Family

ID=90586953

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/129791 Pending WO2025091514A1 (fr) 2023-11-03 2023-11-03 Procédé et appareil de traitement d'informations

Country Status (2)

Country Link
CN (1) CN117882402A (fr)
WO (1) WO2025091514A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200163005A1 (en) * 2018-11-19 2020-05-21 Huawei Technologies Co., Ltd. System and method for supporting sidelink radio bearers
WO2022188692A1 (fr) * 2021-03-09 2022-09-15 华为技术有限公司 Procédé de détermination d'une configuration drx de liaison latérale et appareil de communication
US20220361036A1 (en) * 2019-10-29 2022-11-10 Lg Electronics Inc. Method and apparatus for signaling qos information in nr v2x
WO2023205950A1 (fr) * 2022-04-24 2023-11-02 Oppo广东移动通信有限公司 Procédé et appareil de gestion de porteuse, dispositif et support

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200163005A1 (en) * 2018-11-19 2020-05-21 Huawei Technologies Co., Ltd. System and method for supporting sidelink radio bearers
US20220361036A1 (en) * 2019-10-29 2022-11-10 Lg Electronics Inc. Method and apparatus for signaling qos information in nr v2x
WO2022188692A1 (fr) * 2021-03-09 2022-09-15 华为技术有限公司 Procédé de détermination d'une configuration drx de liaison latérale et appareil de communication
WO2023205950A1 (fr) * 2022-04-24 2023-11-02 Oppo广东移动通信有限公司 Procédé et appareil de gestion de porteuse, dispositif et support

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Discussion on Tx profile for broadcast and groupcast", 3GPP DRAFT; R2-2204863, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Online; 20220509 - 20220520, 25 April 2022 (2022-04-25), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052138490 *

Also Published As

Publication number Publication date
CN117882402A (zh) 2024-04-12

Similar Documents

Publication Publication Date Title
CN117158100A (zh) 资源指示方法及装置、通信设备、通信系统、存储介质
CN117204099A (zh) 通信方法、终端、网络设备和存储介质
WO2025000303A1 (fr) Procédé d'indication d'informations, terminal, dispositif de réseau, système de communication et support de stockage
WO2025030558A1 (fr) Procédé d'accès aléatoire, terminal, dispositif réseau, dispositif de communication et support de stockage
WO2025000552A1 (fr) Procédé de traitement d'informations, et terminal et dispositif de réseau
WO2025000539A1 (fr) Procédé et appareil de communication de liaison montante, dispositif de communication, système de communication et support de stockage
WO2025091515A1 (fr) Procédé et appareil de communication en liaison latérale
WO2025010607A1 (fr) Procédé de traitement d'informations et appareil pour sa mise en oeuvre
WO2025000205A1 (fr) Procédé de mesure, dispositif et support de stockage
WO2025091514A1 (fr) Procédé et appareil de traitement d'informations
WO2025091406A1 (fr) Procédé de communication et appareil associé
WO2025030292A1 (fr) Procédés de communication de liaison latérale et appareils associés
WO2025043728A1 (fr) Procédé de communication, premier terminal, second terminal et système de communication
WO2025030432A1 (fr) Procédé de duplication de protocole de convergence de données par paquets (pdcp) de liaison latérale, et appareil associé
WO2025050408A1 (fr) Procédé et appareil de communication satellite, et dispositif de communication, système de communication et support de stockage
WO2025199894A1 (fr) Procédé de transmission de signal, dispositif de communication, système de communication et support de stockage
WO2025035230A1 (fr) Procédé et appareil de communication, dispositif de communication, système de communication et support de stockage
WO2025097452A1 (fr) Procédé de communication et appareil associé
WO2025025026A1 (fr) Procédé de traitement d'informations, dispositif de réseau, terminal, système de communication, et support de stockage
CN117796116A (zh) 上行通信方法、终端、网络设备、通信系统、存储介质
WO2025076660A1 (fr) Procédé et appareil de détermination, dispositif de communication, système de communication et support de stockage
WO2025065452A1 (fr) Procédés de traitement de communication, terminal et dispositifs de réseau d'accès
WO2024259708A1 (fr) Procédé et appareil de traitement, dispositif et système de communication et support de stockage
WO2025107208A1 (fr) Procédé et appareil de traitement d'informations, et support de stockage
WO2025208303A1 (fr) Procédé de commande de transmission, terminal, dispositif de réseau et support d'enregistrement

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23957370

Country of ref document: EP

Kind code of ref document: A1