Devices and methods of communication
Patent Information
- Application Number
- PCT/CN2023/093617
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-11
- Publication Date
- 2024-11-14
Smart Images

Figure CN2023093617_14112024_PF_FP_ABST
Abstract
Description
DEVICES AND METHODS OF COMMUNICATIONTECHNICAL FIELD
[0001] Embodiments of the present disclosure generally relate to the field of telecommunication, and in particular, to methods, devices and computer storage media of communication for management of packets in quality of service (QoS) flows.BACKGROUND
[0002] Currently, protocol data unit (PDU) -set based QoS handling is being studied. In downlink (DL) , PDU set importance is provided by a core network (CN) to identify importance of a PDU set within a QoS flow. In uplink (UL) , PDU set importance may also be provided to an access stratum (AS) layer. It has been proposed that the PDU set importance may be defined within the scope of a QoS flow or cross different QoS flows. However, solutions related to PDU set importance across QoS flows are still unclear and need to be further developed.SUMMARY
[0003] In general, embodiments of the present disclosure provide methods, devices and computer storage media of communication for management of packets in QoS flows.
[0004] In a first aspect, there is provided a terminal device. The terminal device comprises a processor. The processor is configured to cause the terminal device to: receive, from an access network device, a configuration indicating information of a group comprising QoS flows or radio bearers (RBs) , importance or priorities of packets spanning across the QoS flows or RBs in the group; and manage the packets based on the information of the group.
[0005] In a second aspect, there is provided a terminal device. The terminal device comprises a processor. The processor is configured to cause the terminal device to: receive, from an access network device, a configuration indicating a mapping between a logical channel and at least one packet of a QoS flow; and perform, based on the mapping, a transmission or reception of the at least one packet.
[0006] In a third aspect, there is provided an access network device. The access network device comprises a processor. The processor is configured to cause the access network device to: transmit, to a terminal device, a configuration indicating information of a group comprising QoS flows or RBs, importance or priorities of packets spanning across the QoS flows or RBs in the group.
[0007] In a fourth aspect, there is provided an access network device. The access network device comprises a processor. The processor is configured to cause the access network device to: transmit, to a terminal device, a configuration indicating a mapping between a logical channel and at least one packet of a QoS flow.
[0008] In a fifth aspect, there is provided a method of communication. The method comprises: receiving, at a terminal device and from an access network device, a configuration indicating information of a group comprising QoS flows or RBs, importance or priorities of packets spanning across the QoS flows or RBs in the group; and manage the packets based on the information of the group.
[0009] In a sixth aspect, there is provided a method of communication. The method comprises: receiving, at a terminal device and from an access network device, a configuration indicating a mapping between a logical channel and at least one packet of a QoS flow; and performing, based on the mapping, a transmission or reception of the at least one packet.
[0010] In a seventh aspect, there is provided a method of communication. The method comprises: transmitting, at an access network device and to a terminal device, a configuration indicating information of a group comprising QoS flows or RBs, importance or priorities of packets spanning across the QoS flows or RBs in the group.
[0011] In an eighth aspect, there is provided a method of communication. The method comprises: transmitting, at an access network device and to a terminal device, a configuration indicating a mapping between a logical channel and at least one packet of a QoS flow.
[0012] In a ninth aspect, there is provided a computer readable medium having instructions stored thereon. The instructions, when executed on at least one processor, cause the at least one processor to perform the method according to any of the fifth to eighth aspects of the present disclosure.
[0013] Other features of the present disclosure will become easily comprehensible through the following description.BRIEF DESCRIPTION OF THE DRAWINGS
[0014] Through the more detailed description of some embodiments of the present disclosure in the accompanying drawings, the above and other objects, features and advantages of the present disclosure will become more apparent, wherein:
[0015] FIG. 1A illustrates an example communication network in which some embodiments of the present disclosure can be implemented;
[0016] FIG. 1B illustrates a schematic diagram of a QoS architecture in which some embodiments of the present disclosure can be implemented;
[0017] FIG. 2 illustrates a schematic diagram illustrating a process of communication according to embodiments of the present disclosure;
[0018] FIG. 3 illustrates a schematic diagram of an example grouping of QoS flows or RBs according to embodiments of the present disclosure;
[0019] FIG. 4 illustrates a schematic diagram illustrating another process of communication according to embodiments of the present disclosure;
[0020] FIG. 5A illustrates a schematic diagram illustrating an example mapping to a logical channel (LCH) according to embodiments of the present disclosure;
[0021] FIG. 5B illustrates a schematic diagram illustrating another example mapping to an LCH according to embodiments of the present disclosure;
[0022] FIG. 6 illustrates an example method of communication implemented at a terminal device in accordance with some embodiments of the present disclosure;
[0023] FIG. 7 illustrates another example method of communication implemented at a terminal device in accordance with some embodiments of the present disclosure;
[0024] FIG. 8 illustrates an example method of communication implemented at an access network device in accordance with some embodiments of the present disclosure;
[0025] FIG. 9 illustrates another example method of communication implemented at an access network device in accordance with some embodiments of the present disclosure; and
[0026] FIG. 10 illustrates a simplified block diagram of a device that is suitable for implementing embodiments of the present disclosure.
[0027] Throughout the drawings, the same or similar reference numerals represent the same or similar element.DETAILED DESCRIPTION
[0028] Principle of the present disclosure will now be described with reference to some embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitations as to the scope of the disclosure. The disclosure described herein can be implemented in various manners other than the ones described below.
[0029] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.
[0030] As used herein, the term ‘terminal device’ refers to any device having wireless or wired communication capabilities. Examples of the terminal device include, but not limited to, user equipment (UE) , personal computers, desktops, mobile phones, cellular phones, smart phones, personal digital assistants (PDAs) , portable computers, tablets, wearable devices, internet of things (IoT) devices, Ultra-reliable and Low Latency Communications (URLLC) devices, Internet of Everything (IoE) devices, machine type communication (MTC) devices, device on vehicle for V2X communication where X means pedestrian, vehicle, or infrastructure / network, devices for Integrated Access and Backhaul (IAB) , Space borne vehicles or Air borne vehicles in Non-terrestrial networks (NTN) including Satellites and High Altitude Platforms (HAPs) encompassing Unmanned Aircraft Systems (UAS) , eXtended Reality (XR) devices including different types of realities such as Augmented Reality (AR) , Mixed Reality (MR) and Virtual Reality (VR) , the unmanned aerial vehicle (UAV) commonly known as a drone which is an aircraft without any human pilot, devices on high speed train (HST) , or image capture devices such as digital cameras, sensors, gaming devices, music storage and playback appliances, or Internet appliances enabling wireless or wired Internet access and browsing and the like. The ‘terminal device’ can further has ‘multicast / broadcast’ feature, to support public safety and mission critical, V2X applications, transparent IPv4 / IPv6 multicast delivery, IPTV, smart TV, radio services, software delivery over wireless, group communications and IoT applications. It may also incorporated one or multiple Subscriber Identity Module (SIM) as known as Multi-SIM. The term “terminal device” can be used interchangeably with a UE, a mobile station, a subscriber station, a mobile terminal, a user terminal or a wireless device.
[0031] The term “network device” may refer to a core network device or an access network device. The term “core network device” refers to any device or entity that provides access and mobility management function (AMF) , network exposure function (NEF) , authentication server function (AUSF) , unified data management (UDM) , session management function (SMF) , user plane function (UPF) , a location management function (LMF) , etc. . In other embodiments, the core network device may be any other suitable device or entity providing any other suitable functionality.
[0032] As used herein, the term “access network device” refers to a device which is capable of providing or hosting a cell or coverage where terminal devices can communicate. Examples of an access network device include, but not limited to, a satellite, a unmanned aerial systems (UAS) platform, a Node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a next generation NodeB (gNB) , a transmission reception point (TRP) , a remote radio unit (RRU) , a radio head (RH) , a remote radio head (RRH) , an IAB node, a low power node such as a femto node, a pico node, a reconfigurable intelligent surface (RIS) , and the like.
[0033] The terminal device or the network device may have Artificial intelligence (AI) or Machine learning capability. It generally includes a model which has been trained from numerous collected data for a specific function, and can be used to predict some information.
[0034] The terminal or the network device may work on several frequency ranges, e.g. FR1 (410 MHz to 7125 MHz) , FR2 (24.25GHz to 71GHz) , frequency band larger than 100GHz as well as Tera Hertz (THz) . It can further work on licensed / unlicensed / shared spectrum. The terminal device may have more than one connections with the network devices under Multi-Radio Dual Connectivity (MR-DC) application scenario. The terminal device or the network device can work on full duplex, flexible duplex and cross division duplex modes.
[0035] The embodiments of the present disclosure may be performed in test equipment, e.g. signal generator, signal analyzer, spectrum analyzer, network analyzer, test terminal device, test network device, channel emulator.
[0036] In one embodiment, the terminal device may be connected with a first network device and a second network device. One of the first network device and the second network device may be a master node and the other one may be a secondary node. The first network device and the second network device may use different radio access technologies (RATs) . In one embodiment, the first network device may be a first RAT device and the second network device may be a second RAT device. In one embodiment, the first RAT device is eNB and the second RAT device is gNB. Information related with different RATs may be transmitted to the terminal device from at least one of the first network device or the second network device. In one embodiment, first information may be transmitted to the terminal device from the first network device and second information may be transmitted to the terminal device from the second network device directly or via the first network device. In one embodiment, information related with configuration for the terminal device configured by the second network device may be transmitted from the second network device via the first network device. Information related with reconfiguration for the terminal device configured by the second network device may be transmitted to the terminal device from the second network device directly or via the first network device.
[0037] As used herein, the singular forms ‘a’ , ‘an’ and ‘the’ are intended to include the plural forms as well, unless the context clearly indicates otherwise. The term ‘includes’ and its variants are to be read as open terms that mean ‘includes, but is not limited to. ’ The term ‘based on’ is to be read as ‘at least in part based on. ’ The term ‘one embodiment’ and ‘an embodiment’ are to be read as ‘at least one embodiment. ’ The term ‘another embodiment’ is to be read as ‘at least one other embodiment. ’ The terms ‘first, ’ ‘second, ’ and the like may refer to different or same objects. Other definitions, explicit and implicit, may be included below.
[0038] In some examples, values, procedures, or apparatus are referred to as ‘best, ’ ‘lowest, ’ ‘highest, ’ ‘minimum, ’ ‘maximum, ’ or the like. It will be appreciated that such descriptions are intended to indicate that a selection among many used functional alternatives can be made, and such selections need not be better, smaller, higher, or otherwise preferable to other selections.
[0039] As known, XR-awareness by UE and gNB may improve user experience, improve new radio (NR) system capacity in supporting XR services, and reduce UE power consumption. Due to Internet protocol (IP) segmentation or other reasons, a video frame in XR traffic may arrive at radio access network (RAN) as a set of PDUs (e.g., multiple packets) . For some services such as XR or media services, a group of packets may be used to carry payloads of a PDU set (e.g. a frame, video slice or tile) . Packets in such a PDU set may be decoded or handled as a whole. As mentioned above, PDU-set based QoS handling is being studied. It has been proposed that the PDU set importance may be defined within the scope of a QoS flow or cross different QoS flows. However, solutions related to PDU set importance across QoS flows are still unclear.
[0040] In consideration with PDU set importance across QoS flows, embodiments of the present disclosure provide solutions for managing packets in QoS flows. In one aspect, an access network device transmits, to a terminal device, a configuration indicating information of a group comprising QoS flows or RBs, wherein importance or priorities of packets span across the QoS flows or RBs in the group. The terminal device manages the packets based on the information of the group. In this way, relationships between importance across different QoS flows or RBs may be maintained and used for packet management.
[0041] In another aspect, an access network device transmits, to a terminal device, a configuration indicating a mapping between an LCH and at least one packet of a QoS flow. Based on the mapping, the terminal device performs a transmission or reception of the at least one packet. In this way, reliability of PDUs or PDU sets with higher importance may be improved and utilization of resources may be increased.
[0042] Principles and implementations of the present disclosure will be described in detail below with reference to the figures.
[0043] EXAMPLE OF COMMUNICATION NETWORK
[0044] FIG. 1A illustrates a schematic diagram of an example communication network 100A in which some embodiments of the present disclosure can be implemented. As shown in FIG. 1A, the communication network 100A may include a terminal device 110 and an access network device 120. In some embodiments, the access network device 120 may provide one or more serving cells (not shown) to serve the terminal device 110.
[0045] As shown in FIG. 1A, the communication network 100A may further include a core network device 130. In some embodiments, the access network device 120 and the core network device 130 may communicate with each other. The terminal device 110 may communicate with the core network device 130 via the access network device 120.
[0046] The terminal device 110 may communicate with the access network device 120 via a Uu interface. The access network device 120 may communicate with the core network device 130 via an Ng interface. The communications in the communication network 100A may conform to any suitable standards including, but not limited to, Global System for Mobile Communications (GSM) , Long Term Evolution (LTE) , LTE-Evolution, LTE-Advanced (LTE-A) , New Radio (NR) , Wideband Code Division Multiple Access (WCDMA) , Code Division Multiple Access (CDMA) , GSM EDGE Radio Access Network (GERAN) , Machine Type Communication (MTC) and the like. The embodiments of the present disclosure may be performed according to any generation communication protocols either currently known or to be developed in the future. Examples of the communication protocols include, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, 5.5G, 5G-Advanced networks, or the sixth generation (6G) networks.
[0047] It is to be understood that the number of devices in FIG. 1A is given for the purpose of illustration without suggesting any limitations to the present disclosure. The communication network 100A may include any suitable number of access network devices and / or terminal devices and / or core network devices adapted for implementing implementations of the present disclosure.
[0048] FIG. 1B illustrates a schematic diagram of a QoS architecture in which some embodiments of the present disclosure can be implemented. For convenience, FIG. 1B will be described in connection with the example of FIG. 1A. As shown in FIG. 1B, one or more PDU sessions (for convenience, only one PDU session is shown) may be established among the terminal device 110, the access network device 120 and the core network device 130. A PDU session may have a plurality of QoS flows. A QoS flow may be identified within a PDU session by a QoS flow identifier (QFI) carried in an encapsulation header over a NG-U tunnel. A PDU session may correspond to a plurality of RBs, and each RB may include one or more QoS flows.
[0049] Different QoS flows may have different QoS requirements. If PDU set importance span across QoS flows, an importance relationship between different QoS flows may need to be maintained to enable packet (e.g., PDU or PDU set) discard across QoS flows. Further, mapping from QoS flows to LCHs may need to be clarified.
[0050] Embodiments of the present disclosure provide solutions of communication for packet management so as to overcome the above and other potential issues. The detailed description will be made with reference to FIGs. 2 to 5 below.
[0051] EXAMPLE IMPLEMENTATION OF PACKET MANAGEMENT
[0052] FIG. 2 illustrates a schematic diagram illustrating a process 200 of communication according to embodiments of the present disclosure. For the purpose of discussion, the process 200 will be described with reference to FIG. 1A. The process 200 may involve the terminal device 110, the access network device 120 and the core network device 130 as illustrated in FIG. 1A.
[0053] As shown in FIG. 2, the network device 120 may determine 210 a configuration indicating information of a group comprising QoS flows or RBs. Importance or priorities of packets span across the QoS flows or RBs in the group. For convenience, such group may also be referred to as an importance group herein.
[0054] In some embodiments, a packet may be a service data unit (SDU) . In some embodiments, a packet may be a PDU. In some embodiments, a packet may be a PDU set. In some embodiments, an RB may be a data radio bearer (DRB) . In some embodiments, an RB may be a signaling radio bearer (SRB) .
[0055] In some embodiments, if importance of packets span across QoS flows or RBs, these QoS flows or RBs may belong to the same importance group. FIG. 3 illustrates a schematic diagram 300 of an example grouping of QoS flows or RBs according to embodiments of the present disclosure. It is assumed that importance with values 0, 1, 2, 3 spans across different QoS flows or RBs. As shown in FIG. 3, importance values 0 and 1 are associated with packets of a QoS flow or RB 311, and importance values 2 and 3 are associated with packets of a QoS flow or RB 312. In this case, the QoS flow or RB 311 and the QoS flow or RB 312 belong to a same importance group 310. It is to be understood that importance may be replaced by priority.
[0056] Continue to refer to FIG. 2, in some embodiments, the terminal device 110 may transmit 211, to the access network device 120, information of whether the terminal device 110 supports the importance or priorities of packets spanning across the QoS flows or RBs. In some embodiments, the terminal device 110 may transmit 211’ , to the core network device 130, the information of whether the terminal device 110 supports the importance or priorities of packets spanning across the QoS flows or RBs. In some embodiments, the terminal device 110 may report, to the access network device 120 or the core network device 130, capability of whether the terminal device 110 supports the importance or priorities of packets spanning across the QoS flows or RBs via an RRC signaling such as UE capability information.
[0057] In some embodiments for UL, the terminal device 110 may report 212 the information of the group to the access network device 120, e.g., via an RRC signaling such as UE assistance information. In some embodiments, the terminal device 110 may report 212’ the information of the group to the core network device 130, e.g., via an RRC signaling such as time sensitive communication (TSC) assistance information (TSCAI) or TSC assistance container (TSCAC) .
[0058] In some embodiments for DL, the core network device 130 may provide 213 the information of the group to the access network device 120. For example, the core network device 130 may provide the information of the group to the access network device 120 via an RRC signaling.
[0059] In some embodiments, the access network device 120 may determine the configuration indicating the information of the group based on any of the above information received from the core network device 130 and / or the terminal device 120.
[0060] In some embodiments, the information of the group may comprise an identity of the group to which the QoS flows or RBs belong. In some embodiments, the information of the group may comprise number of values of the importance or priorities for the group. In some embodiments, the information of the group may comprise a list of the QoS flows or RBs in the group, i.e., a list of QoS flows or RBs belong to the same importance group. In some embodiments, the information of the group may comprise a list of the values of the importance or priorities associated with the QoS flows or RBs. Each of the values is associated with a respective QoS flow or RB. It is to be understood that any combination of the above information may also be feasible.
[0061] For illustration, an example configuration may be configured as below.
[0062] In this example, importanceGroupId denotes an identity of the group, numberOfImportance denotes number of values of the importance or priorities for the group, and qfiList denotes a list of QoS flows or RBs.
[0063] For illustration, another example configuration may be configured as below.
[0064] In this example, importanceGroupId denotes an identity of the group, and qfi denotes an identity of a QoS flow which belongs to the group.
[0065] It is to be understood that the configuration may be configured in any other suitable forms, and the present disclosure does not limit this aspect.
[0066] With reference to FIG. 2, the access network device 120 may transmit 220 the configuration to the terminal device 110, e.g., via an RRC signaling.
[0067] As shown in FIG. 2, the terminal device 110 may manage 230 the packets in the QoS flows or RBs based on the information of the group. In some embodiments, the terminal device 110 may perform packet discard for the packets in the QoS flows or RBs based on the information of the group. For example, for different importance belonging to the same group, the terminal device 110 may preferentially discard a packet with a lower priority based on an importance value of the packet. By considering packet discard from a view of an importance group, a discarded packet ratio may be easily controlled and packet management may be optimized. It is to be understood that other details of packet discard may be carried out in any suitable ways existing or to be developed in future.
[0068] In some embodiments, the terminal device 110 may perform data scheduling based on the information of the group. For example, the terminal device 110 may perform the data scheduling for the group as a whole by considering different importance within the group. It is to be understood that any other suitable packet management behaviors may also be feasible.
[0069] With the process 200, relationships between importance across different QoS flows or RBs may be maintained and used for packet management.
[0070] EXAMPLE IMPLEMENTATION OF PACKET TRANSMISSION OR RECEPTION
[0071] FIG. 4 illustrates a schematic diagram illustrating another process 400 of communication according to embodiments of the present disclosure. For the purpose of discussion, the process 400 will be described with reference to FIG. 1A. The process 400 may involve the terminal device 110, the access network device 120 and the core network device 130 as illustrated in FIG. 1A.
[0072] As shown in FIG. 4, the network device 120 may transmit 410, to the terminal device 110, a configuration indicating a mapping between an LCH and at least one packet of a QoS flow. For example, the network device 120 may transmit the configuration indicating the mapping via an RRC signaling.
[0073] In some embodiments, QoS flows belonging to a group (i.e., importance group) may be mapped to respective (e.g., different) LCHs. Importance or priorities of packets span across the QoS flows in the group. In this way, reliability of PDUs or PDU sets with higher importance may be improved.
[0074] In some embodiments, the configuration may comprise a list of QoS flows associated with a radio link control (RLC) bearer configuration. The RLC bearer configuration is associated with the LCH.
[0075] For example, an example RLC bearer configuration may be configured as below.
[0076] In this example, information element (IE) servedQFI or servedQFIList may be configured per RLC bearer. If the IE servedQFI or servedQFIList is configured, the QoS flow identified by servedQFI or servedQFIList may be mapped to a LCH identified by IE logicalChannelIdentity.
[0077] In some embodiments, the configuration may comprise a list of QoS flows associated with a packet data convergence protocol (PDCP) configuration, and the PDCP configuration is associated with the LCH.
[0078] For example, an example PDCP configuration may be configured as below.
[0079] In this example, IE qfi or qfiList may be configured per PDCP configuration. The QoS flow identified by qfi or qfiList may be mapped to a LCH identified by IE logicalChannel.
[0080] In some embodiments, QoS flows in the same importance group may be mapped to the same RB (e.g., DRB) , and different QoS flows belonging to the same RB may be mapped to different LCHs. FIG. 5A illustrates a schematic diagram 500A illustrating an example mapping to an LCH according to embodiments of the present disclosure. As shown in FIG. 5A, importance with values 0, 1, 2, 3 spans across QoS flows 511 and 512. Importance values 0 and 1 are associated with packets of the QoS flow 511, and importance values 2 and 3 are associated with packets of the QoS flow 512. The QoS flow 511 and the QoS flow 512 belongs to a same importance group 510. The QoS flows 511 and 512 may be mapped to the same DRB, and then mapped to LCH 1 and LCH 2 respectively.
[0081] In some embodiments, QoS flows in the same importance group may be mapped to different RBs (e.g., DRBs) , and different QoS flows belonging to different RBs may be mapped to different LCHs. FIG. 5B illustrates a schematic diagram 500B illustrating another example mapping to an LCH according to embodiments of the present disclosure. As shown in FIG. 5B, importance with values 0, 1, 2, 3 spans across QoS flows 521 and 522. Importance values 0 and 1 are associated with packets of the QoS flow 521, and importance values 2 and 3 are associated with packets of the QoS flow 522. The QoS flow 521 and the QoS flow 522 belongs to a same importance group 520. The QoS flows 521 and 522 may be mapped to DRB 1 and DRB 2 respectively, and then mapped to LCH 1 and LCH 2 respectively.
[0082] In some embodiments, the configuration comprises, as a mapping restriction for the logical channel, a list of QoS flows allowed to be mapped to the LCH. In other words, by restricting a set of QoS flows that can be mapped to a LCH, differentiated processing of different QoS flows may be achieved. In this way, different QoS flows may be mapped to different LCHs which may be scheduled or handled differently.
[0083] For example, an example LCH configuration may be configured as below.
[0084] In this example, IE allowedQFI-List denotes the allowed QoS flow (s) mapped to this logical channel. If the IE is absent, there is no restriction for QoS flow for the mapping.
[0085] Correspondingly, an example logical channel priority (LCP) limitation may be described as below.
[0086] RRC controls the LCH mapping restrictions for each logical channel:
[0087] - allowedQFI-List which sets the allowed QoS flows for mapping to this logical channel.
[0088] In some embodiments, the configuration comprises, as a mapping restriction for the logical channel, a list of values of importance or priorities of packets allowed to be mapped to the logical channel. In other words, by restricting a set of importance or priorities that can be mapped to a LCH, differentiated processing of different importance or priorities may be achieved. In this way, different importance or priorities may be mapped to different LCHs which may be scheduled or handled differently.
[0089] For example, an example LCH configuration may be configured as below.
[0090] In this example, IE allowedImportance-List denotes the allowed importance mapped to this logical channel. If the IE is absent, there is no restriction for importance for the mapping.
[0091] Correspondingly, an example LCP limitation may be described as below.
[0092] RRC controls the LCH mapping restrictions for each logical channel:
[0093] - allowedImportance-List which sets the allowed importance (s) for mapping to this logical channel.
[0094] Continue to refer to FIG. 4, the terminal device 110 may perform 420, based on the mapping, a transmission or reception of the at least one packet. In some embodiments, the terminal device 110 may perform the transmission or reception of all the packets in a QoS flow based on the mapping. In some embodiments, the terminal device 110 may perform the transmission or reception of some of the packets in a QoS flow based on the mapping.
[0095] With the process 400, reliability of PDUs or PDU sets with higher importance may be improved and utilization of resources may be increased.
[0096] EXAMPLE IMPLEMENTATION OF METHODS
[0097] Accordingly, embodiments of the present disclosure provide methods of communication implemented at a terminal device and a network device. These methods will be described below with reference to FIGs. 6 to 9.
[0098] FIG. 6 illustrates an example method 600 of communication implemented at a terminal device in accordance with some embodiments of the present disclosure. For example, the method 600 may be performed at the terminal device 110 as shown in FIG. 1A. For the purpose of discussion, in the following, the method 600 will be described with reference to the terminal device 110 in FIG. 1A. It is to be understood that the method 600 may include additional blocks not shown and / or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard.
[0099] At block 610, the terminal device 110 receives, from an access network device, a configuration indicating information of a group comprising QoS flows or RBs, importance or priorities of packets spanning across the QoS flows or RBs in the group.
[0100] At block 620, the terminal device 110 manages the packets based on the information of the group.
[0101] In some embodiments, the information of the group may comprise at least one of the following: an identity of the group; number of values of the importance or priorities for the group; a list of the QoS flows or RBs in the group; or a list of the values of the importance or priorities associated with the QoS flows or RBs.
[0102] In some embodiments, the terminal device 110 may transmit, to the access network device 120 or the core network device 130, information of whether the terminal device supports the importance or priorities of packets spanning across the QoS flows or RBs.
[0103] In some embodiments, the terminal device 110 may transmit the information of the group to the access network device 120 or the core network device 130.
[0104] With the method 600, relationships between importance across different QoS flows or RBs may be maintained and used for packet management.
[0105] FIG. 7 illustrates another example method 700 of communication implemented at a terminal device in accordance with some embodiments of the present disclosure. For example, the method 700 may be performed at the terminal device 110 as shown in FIG. 1A. For the purpose of discussion, in the following, the method 700 will be described with reference to the terminal device 110 in FIG. 1A. It is to be understood that the method 700 may include additional blocks not shown and / or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard.
[0106] As shown in FIG. 7, at block 710, the terminal device 110 receives, from the access network device 120, a configuration indicating a mapping between a logical channel and at least one packet of a QoS flow.
[0107] In some embodiments, the configuration may comprise at least one of the following: a list of QoS flows associated with an RLC bearer configuration, the RLC bearer configuration being associated with the logical channel; or a list of QoS flows associated with a PDCP configuration, the PDCP configuration being associated with the logical channel.
[0108] In some embodiments, QoS flows belonging to a group may be mapped to different logical channels, importance or priorities of packets spanning across the QoS flows in the group.
[0109] In some embodiments, the configuration may comprise, as a mapping restriction for the logical channel, a list of QoS flows allowed to be mapped to the logical channel.
[0110] In some embodiments, the configuration may comprise, as a mapping restriction for the logical channel, a list of values of importance or priorities of packets allowed to be mapped to the logical channel.
[0111] At block 720, the terminal device 110 performs, based on the mapping, a transmission or reception of the at least one packet.
[0112] With the method 700, reliability of PDUs or PDU sets with higher importance may be improved and utilization of resources may be increased.
[0113] FIG. 8 illustrates an example method 800 of communication implemented at an access network device in accordance with some embodiments of the present disclosure. For example, the method 800 may be performed at the access network device 120 as shown in FIG. 1A. For the purpose of discussion, in the following, the method 800 will be described with reference to the access network device 120 in FIG. 1A. It is to be understood that the method 800 may include additional blocks not shown and / or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard.
[0114] As shown in FIG. 8, at block 810, the access network device 120 transmits, to the terminal device 110, a configuration indicating information of a group comprising QoS flows or RBs, importance or priorities of packets spanning across the QoS flows or RBs in the group.
[0115] In some embodiments, the information of the group may comprise at least one of the following: an identity of the group; number of values of the importance or priorities for the group; a list of the QoS flows or RBs in the group; or a list of the values of the importance or priorities associated with the QoS flows or RBs.
[0116] In some embodiments, the access network device 120 may receive, from the terminal device 110, information of whether the terminal device supports the importance or priorities of packets spanning across the QoS flows or RBs.
[0117] In some embodiments, the access network device 120 may receive the information of the group from the terminal device 110 or the core network device 130.
[0118] With the method 800, relationships between importance across different QoS flows or RBs may be maintained and used for packet management.
[0119] FIG. 9 illustrates another example method 900 of communication implemented at an access network device in accordance with some embodiments of the present disclosure. For example, the method 900 may be performed at the access network device 120 as shown in FIG. 1A. For the purpose of discussion, in the following, the method 900 will be described with reference to the access network device 120 in FIG. 1A. It is to be understood that the method 900 may include additional blocks not shown and / or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard.
[0120] As shown in FIG. 9, at block 910, the access network device 120 transmits, to the terminal device 110, a configuration indicating a mapping between a logical channel and at least one packet of a QoS flow.
[0121] In some embodiments, the configuration may comprises at least one of the following: a list of QoS flows associated with an RLC bearer configuration, the RLC bearer configuration being associated with the logical channel; or a list of QoS flows associated with a PDCP configuration, the PDCP configuration being associated with the logical channel.
[0122] In some embodiments, QoS flows belonging to a group may be mapped to different logical channels, importance or priorities of packets spanning across the QoS flows in the group.
[0123] In some embodiments, the configuration may comprise, as a mapping restriction for the logical channel, a list of QoS flows allowed to be mapped to the logical channel.
[0124] In some embodiments, the configuration may comprise, as a mapping restriction for the logical channel, a list of values of importance or priorities of packets allowed to be mapped to the logical channel.
[0125] With the method 900, reliability of PDUs or PDU sets with higher importance may be improved and utilization of resources may be increased.
[0126] EXAMPLE IMPLEMENTATION OF DEVICES
[0127] FIG. 10 is a simplified block diagram of a device 1000 that is suitable for implementing embodiments of the present disclosure. The device 1000 can be considered as a further example implementation of the terminal device 110 or the access network device 120 or the core network device 130 as shown in FIG. 1A. Accordingly, the device 1000 can be implemented at or as at least a part of the terminal device 110 or the access network device 120 or the core network device 130.
[0128] As shown, the device 1000 includes a processor 1010, a memory 1020 coupled to the processor 1010, a suitable transceiver 1040 coupled to the processor 1010, and a communication interface coupled to the transceiver 1040. The memory 1010 stores at least a part of a program 1030. The transceiver 1040 may be for bidirectional communications or a unidirectional communication based on requirements. The transceiver 1040 may include at least one of a transmitter 1042 or a receiver 1044. The transmitter 1042 and the receiver 1044 may be functional modules or physical entities. The transceiver 1040 has at least one antenna to facilitate communication, though in practice an Access Node mentioned in this application may have several ones. The communication interface may represent any interface that is necessary for communication with other network elements, such as X2 / Xn interface for bidirectional communications between eNBs / gNBs, S1 / NG interface for communication between a Mobility Management Entity (MME) / Access and Mobility Management Function (AMF) / SGW / UPF and the eNB / gNB, Un interface for communication between the eNB / gNB and a relay node (RN) , or Uu interface for communication between the eNB / gNB and a terminal device.
[0129] The program 1030 is assumed to include program instructions that, when executed by the associated processor 1010, enable the device 1000 to operate in accordance with the embodiments of the present disclosure, as discussed herein with reference to FIGs. 1A to 9. The embodiments herein may be implemented by computer software executable by the processor 1010 of the device 1000, or by hardware, or by a combination of software and hardware. The processor 1010 may be configured to implement various embodiments of the present disclosure. Furthermore, a combination of the processor 1010 and memory 1020 may form processing means 1050 adapted to implement various embodiments of the present disclosure.
[0130] The memory 1020 may be of any type suitable to the local technical network and may be implemented using any suitable data storage technology, such as a non-transitory computer readable storage medium, semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples. While only one memory 1020 is shown in the device 1000, there may be several physically distinct memory modules in the device 1000. The processor 1010 may be of any type suitable to the local technical network, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples. The device 1000 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
[0131] In some embodiments, a terminal device comprises a circuitry configured to: receive, from an access network device, a configuration indicating information of a group comprising QoS flows or RBs, importance or priorities of packets spanning across the QoS flows or RBs in the group; and manage the packets based on the information of the group.
[0132] In some embodiments, a terminal device comprises a circuitry configured to: receive, from an access network device, a configuration indicating a mapping between a logical channel and at least one packet of a QoS flow; and perform, based on the mapping, a transmission or reception of the at least one packet.
[0133] In some embodiments, an access network device comprises a circuitry configured to:transmit, to a terminal device, a configuration indicating information of a group comprising QoS flows or RBs, importance or priorities of packets spanning across the QoS flows or RBs in the group.
[0134] In some embodiments, an access network device comprises a circuitry configured to:transmit, to a terminal device, a configuration indicating a mapping between a logical channel and at least one packet of a QoS flow.
[0135] The term “circuitry” used herein may refer to hardware circuits and / or combinations of hardware circuits and software. For example, the circuitry may be a combination of analog and / or digital hardware circuits with software / firmware. As a further example, the circuitry may be any portions of hardware processors with software including digital signal processor (s) , software, and memory (ies) that work together to cause an apparatus, such as a terminal device or a network device, to perform various functions. In a still further example, the circuitry may be hardware circuits and or processors, such as a microprocessor or a portion of a microprocessor, that requires software / firmware for operation, but the software may not be present when it is not needed for operation. As used herein, the term circuitry also covers an implementation of merely a hardware circuit or processor (s) or a portion of a hardware circuit or processor (s) and its (or their) accompanying software and / or firmware.
[0136] Generally, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representation, it will be appreciated that the blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
[0137] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the process or method as described above with reference to FIGs. 1A to 9. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
[0138] Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
[0139] The above program code may be embodied on a machine readable medium, which may be any tangible medium that may contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine readable medium may be a machine readable signal medium or a machine readable storage medium. A machine readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the machine readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0140] Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are contained in the above discussions, these should not be construed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable sub-combination.
[0141] Although the present disclosure has been described in language specific to structural features and / or methodological acts, it is to be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
Claims
1.A terminal device, comprising:a processor configured to cause the terminal device to:receive, from an access network device, a configuration indicating information of a group comprising quality of service (QoS) flows or radio bearers (RBs) , importance or priorities of packets spanning across the QoS flows or RBs in the group; andmanage the packets based on the information of the group.2.The terminal device of claim 1, wherein the information of the group comprises at least one of the following:an identity of the group;number of values of the importance or priorities for the group;a list of the QoS flows or RBs in the group; ora list of the values of the importance or priorities associated with the QoS flows or RBs.3.The terminal device of claim 1, wherein the terminal device is further caused to:transmit, to the access network device or a core network device, information of whether the terminal device supports the importance or priorities of packets spanning across the QoS flows or RBs.4.The terminal device of claim 1, wherein the terminal device is further caused to:transmit the information of the group to the access network device or the core network device.5.A terminal device, comprising:a processor configured to cause the terminal device to:receive, from an access network device, a configuration indicating a mapping between a logical channel and at least one packet of a quality of service (QoS) flow; andperform, based on the mapping, a transmission or reception of the at least one packet.6.The terminal device of claim 5, wherein the configuration comprises at least one of the following:a list of QoS flows associated with a radio link control (RLC) bearer configuration, the RLC bearer configuration being associated with the logical channel; ora list of QoS flows associated with a packet data convergence protocol (PDCP) configuration, the PDCP configuration being associated with the logical channel.7.The terminal device of claim 5, wherein QoS flows belonging to a group are mapped to different logical channels, importance or priorities of packets spanning across the QoS flows in the group.8.The terminal device of claim 5, wherein the configuration comprises, as a mapping restriction for the logical channel, a list of QoS flows allowed to be mapped to the logical channel.9.The terminal device of claim 5, wherein the configuration comprises, as a mapping restriction for the logical channel, a list of values of importance or priorities of packets allowed to be mapped to the logical channel.10.An access network device, comprising:a processor configured to cause the access network device to:transmit, to a terminal device, a configuration indicating information of a group comprising quality of service (QoS) flows or radio bearers (RBs) , importance or priorities of packets spanning across the QoS flows or RBs in the group.11.The access network device of claim 10, wherein the information of the group comprises at least one of the following:an identity of the group;number of values of the importance or priorities for the group;a list of the QoS flows or RBs in the group; ora list of the values of the importance or priorities associated with the QoS flows or RBs.12.The access network device of claim 10, wherein the access network device is further caused to:receive, from the terminal device, information of whether the terminal device supports the importance or priorities of packets spanning across the QoS flows or RBs.13.The access network device of claim 10, wherein the access network device is further caused to:receive the information of the group from the terminal device or a core network device.14.An access network device, comprising:a processor configured to cause the access network device to:transmit, to a terminal device, a configuration indicating a mapping between a logical channel and at least one packet of a quality of service (QoS) flow.15.The access network device of claim 14, wherein the configuration comprises at least one of the following:a list of QoS flows associated with a radio link control (RLC) bearer configuration, the RLC bearer configuration being associated with the logical channel; ora list of QoS flows associated with a packet data convergence protocol (PDCP) configuration, the PDCP configuration being associated with the logical channel.16.The access network device of claim 14, wherein QoS flows belonging to a group are mapped to different logical channels, importance or priorities of packets spanning across the QoS flows in the group.17.The access network device of claim 14, wherein the configuration comprises, as a mapping restriction for the logical channel, a list of QoS flows allowed to be mapped to the logical channel.18.The access network device of claim 14, wherein the configuration comprises, as a mapping restriction for the logical channel, a list of values of importance or priorities of packets allowed to be mapped to the logical channel.
Citation Information
Patent Citations
Autonomous queue management method based on context awareness
CN101860475A
Managing bandwidth allocation among flows through assignment of drop priority
CN105164982A
Data transmission method and device
CN107306424A
Quality of service (QoS) control method and device
CN109548090A
Methods and systems for packet differentiation
US20150229970A1
