Certains contenus de cette application ne sont pas disponibles pour le moment.
Si cette situation persiste, veuillez nous contacter àObservations et contact
1. (WO2018227861) PROCÉDÉ DE COMMUNICATION, APPAREIL DE COMMUNICATION ET DISPOSITIF COMPORTANT UNE MÉMOIRE POUR STOCKER DES PROGRAMMES
Document

Description

Title of Invention 0001   0002   0003   0004   0005   0006   0007   0008   0009   0010   0011   0012   0013   0014   0015   0016   0017   0018   0019   0020   0021   0022   0023   0024   0025   0026   0027   0028   0029   0030   0031   0032   0033   0034   0035   0036   0037   0038   0039   0040   0041   0042   0043   0044   0045   0046   0047   0048   0049   0050   0051   0052   0053   0054   0055   0056   0057   0058   0059   0060   0061   0062   0063   0064   0065   0066   0067   0068   0069   0070   0071   0072   0073   0074   0075   0076   0077   0078   0079   0080   0081   0082   0083   0084   0085   0086   0087   0088   0089   0090   0091   0092   0093   0094   0095   0096   0097   0098   0099   0100   0101   0102   0103   0104   0105   0106   0107   0108   0109   0110   0111   0112   0113   0114   0115   0116   0117   0118   0119   0120   0121   0122   0123   0124   0125   0126   0127   0128   0129   0130   0131   0132   0133   0134   0135   0136   0137   0138   0139   0140   0141   0142   0143   0144   0145   0146   0147   0148   0149   0150   0151   0152   0153   0154   0155   0156   0157   0158   0159   0160   0161   0162   0163   0164   0165   0166   0167   0168   0169   0170   0171   0172   0173   0174   0175   0176   0177   0178   0179   0180   0181   0182   0183   0184   0185   0186   0187   0188   0189   0190   0191   0192   0193   0194   0195   0196   0197   0198   0199   0200   0201   0202   0203   0204   0205   0206   0207   0208   0209   0210   0211   0212   0213   0214   0215   0216   0217   0218   0219   0220   0221   0222   0223   0224   0225   0226   0227   0228   0229   0230   0231   0232   0233   0234   0235   0236   0237   0238   0239   0240   0241   0242   0243   0244   0245   0246   0247   0248   0249   0250   0251   0252   0253   0254   0255   0256   0257   0258   0259   0260   0261   0262   0263   0264   0265   0266   0267   0268   0269   0270   0271   0272   0273   0274   0275   0276   0277   0278   0279   0280   0281  

Claims

1   2   3   4   5   6   7   8   9   10   11   12   13   14   15   16   17   18   19   20   21   22   23   24   25   26   27   28   29   30   31   32   33   34   35   36   37   38   39   40   41   42   43   44   45   46   47   48   49  

Drawings

0001   0002   0003   0004   0005   0006   0007   0008   0009   0010   0011   0012   0013   0014   0015   0016   0017   0018   0019   0020   0021   0022   0023   0024   0025   0026   0027   0028   0029   0030   0031   0032   0033   0034   0035   0036   0037   0038   0039   0040   0041  

Description

Title of Invention : COMMUNICATION METHOD, COMMUNICATION APPARATUS AND DEVICE WITH A MEMORY FOR STORING PROGRAMS

TECHNICAL FIELD

[0001]
The present disclosure generally relates to communication technologies, and in particular relates to a communication method, a communication apparatus and a memory for storing programs.

BACKGROUND

[0002]
QoS is Quality of Service. The final target for the network to provide services for users is to ensure QoS of users. The QoS architecture of the 5G New Radio (NR) system is shown as in Fig. 1, for each user equipment (UE) , the core network (CN) establishes one or more protocol data unit (PDU) sessions. For each UE, the RAN (Residential Access Network) establishes one or more Data Radio Bearers (DRBs) for per PDU Session. The RAN establishes at least one default DRB for each PDU Session established by the core network. The RAN maps packets belonging to different PDU sessions to different DRBs. NAS (Non-Access) level packet filters in the UE and in the core network associate uplink and downlink packets with service flows (QoS flows) . Access levels in the UE and RAN associate mappings of uplink and downlink QoS flows with Data Radio Bearers (DRB) . In the downlink, the RAN maps the QoS flows to the DRB according to a service flow identifier and associated QoS profiles. And in the uplink, the user equipment performs uplink division with the QoS flow identifier.
[0003]
In NR system, a new access sublevel, which is the Service Data Adaptation Protocol (SDAP) , is proposed to be used to provide QoS flow identifier in the uplink and downlink packets and achieve mapping of the uplink and downlink packets to the QoS flows, and mapping of the data radio bearer with the uplink and downlink service flows. Wherein, as for uplink, the new access sublevel adopts uplink reflective mapping, that is to say, as for each DRB, the UE monitors downlink QoS flow identifiers and uses the same mapping in the uplink. However, to achieve uplink reflective mapping function, for all downlink packets, a QoS flow identifier is needed to be marked over an air interface, which largely increases air interface burden.
[0004]
SUMMARY
[0005]
Embodiments of the present disclosure provide a communication method, a communication apparatus and a memory for storing programs, by which air interface burden can be saved.
[0006]
In accordance with a first aspect of the present application, a communication method is provided, and the method comprising: determining whether a QoS (Quality of Service) flow identifier is needed to be omitted in at least part of downlink messages sent to a user equipment; and omitting the QoS flow identifier in the at least part of downlink messages sent to the user equipment when the QoS flow identifier is needed to be omitted, otherwise carrying the QoS flow identifier in the at least part of downlink messages sent to the user equipment.
[0007]
In accordance with a second aspect of the present application, a communication method is provided, and the method comprising: determining whether a QoS flow identifier is needed to be omitted in at least part of uplink messages sent to a base station; and omitting the QoS flow identifier in the at least part of uplink messages sent to the base station when the QoS flow identifier is needed to be omitted, otherwise carrying the QoS flow identifier in the at least part of uplink messages sent to the base station. The service data adaptation protocol transparent mode is defined as the mode that no service data adaptation protocol (SDAP) header is used for its data/control PDU.
[0008]
In accordance with a third aspect of the present application, a communication apparatus is provided, and the apparatus comprising: a processor and a communication circuit connected to the processor, wherein the processor is configured for executing programs to perform the methods in the first aspect and second aspect.
[0009]
In accordance with a fourth aspect of the present application, a memory for storing programs, wherein the programs are executed to perform the methods in the first aspect and second aspect.
[0010]
According to the communication method and apparatus the subsequent advantages may be achieved: different from that in prior art, the base station determines whether it is needed to omit the QoS flow identifier in at least part of downlink messages sent to the UE, and omit the QoS flow identifier in at least part of downlink messages sent to the UE when it is needed. In this way, it is not needed for at least part of downlink messages to be marked with the QoS flow identifier over the air interface Uu, reducing the air interface Uu burden and increasing communication efficiency. Furthermore, the base station can control QoS mapping of the UE, increasing communication flexibility.

BRIEF DESCRIPTION OF THE DRAWINGS

[0011]
Fig. 1 is a schematic view illustrating a QoS architecture of the NR system in the prior art.
[0012]
Fig. 2 is a flowchart illustrating a first embodiment of a communication method according to the present disclosure.
[0013]
Fig. 3 is a flowchart illustrating a second embodiment of a communication method according to the present disclosure.
[0014]
Fig. 4 is a flowchart illustrating a third embodiment of a communication method according to the present disclosure.
[0015]
Fig. 5 is a flowchart illustrating a fourth embodiment of a communication method according to the present disclosure.
[0016]
Fig. 6 is a flowchart illustrating a fifth embodiment of a communication method according to the present disclosure.
[0017]
Fig. 7 is a diagram illustrating a communication process between a base station and a UE when the base station decides to adopt a SDAP transparent mode to send at least part of downlink messages to the UE as illustrated in Fig. 6.
[0018]
Fig. 8 is a flowchart illustrating a sixth embodiment of a communication method according to the present disclosure.
[0019]
Fig. 9 is a diagram illustrating a communication process between a base station and a UE when the UE decides to adopt a SDAP transparent mode.
[0020]
Fig. 10 is a flowchart illustrating a seventh embodiment of a communication method according to the present disclosure.
[0021]
Fig. 11 is a diagram illustrating a format of a packet data convergence protocol message sent to a UE as illustrated in Fig. 10.
[0022]
Fig. 12 is a flowchart illustrating an eighth embodiment of a communication method according to the present disclosure.
[0023]
Fig. 13 is a diagram illustrating a communication process between a base station and a UE when the base station decides to adopt a SDAP transparent mode to send at least part of downlink messages to the UE as illustrated in Fig. 12.
[0024]
Fig. 14 is a diagram illustrating a format of a SDAP control message sent to a UE as illustrated in Fig. 12.
[0025]
Fig. 15 is a flowchart illustrating a ninth embodiment of a communication method according to the present disclosure.
[0026]
Fig. 16 is a flowchart illustrating a tenth embodiment of a communication method according to the present disclosure.
[0027]
Fig. 17 is a flowchart illustrating an eleventh embodiment of a communication method according to the present disclosure.
[0028]
Fig. 18 is a flowchart illustrating a twelfth embodiment of a communication method according to the present disclosure.
[0029]
Fig. 19 is a flowchart illustrating a thirteenth embodiment of a communication method according to the present disclosure.
[0030]
Fig. 20 is a diagram illustrating a communication process between a base station and a UE when the base station initials /updates QoS flows and data radio bearer mapping as illustrated in Fig. 19.
[0031]
Fig. 21 is a flowchart illustrating a fourteenth embodiment of a communication method according to the present disclosure.
[0032]
Fig. 22 is a flowchart illustrating a fifteenth embodiment of a communication method according to the present disclosure.
[0033]
Fig. 23 is a flowchart illustrating a sixteenth embodiment of a communication method according to the present disclosure.
[0034]
Fig. 24 is a diagram illustrating a format of a SDAP control message received by a base station as illustrated in Fig. 23.
[0035]
Fig. 25 is a flowchart illustrating a seventeenth embodiment of a communication method according to the present disclosure.
[0036]
Fig. 26 is a flowchart illustrating an eighteenth embodiment of a communication method according to the present disclosure.
[0037]
Fig. 27 is a flowchart illustrating a nineteenth embodiment of a communication method according to the present disclosure.
[0038]
Fig. 28 is a flowchart illustrating a twentieth embodiment of a communication method according to the present disclosure.
[0039]
Fig. 29 is a flowchart illustrating a twenty-first embodiment of a communication method according to the present disclosure.
[0040]
Fig. 30 is a flowchart illustrating a twenty-second embodiment of a communication method according to the present disclosure.
[0041]
Fig. 31 is a flowchart illustrating a twenty-third embodiment of a communication method according to the present disclosure.
[0042]
Fig. 32 is a flowchart illustrating a twenty-fourth embodiment of a communication method according to the present disclosure.
[0043]
Fig. 33 is a flowchart illustrating a twenty-fifth embodiment of a communication method according to the present disclosure.
[0044]
Fig. 34 is a flowchart illustrating a twenty-sixth embodiment of a communication method according to the present disclosure.
[0045]
Fig. 35 is a flowchart illustrating a twenty-seventh embodiment of a communication method according to the present disclosure.
[0046]
Fig. 36 is a flowchart illustrating a twenty-eighth embodiment of a communication method according to the present disclosure.
[0047]
Fig. 37 is a flowchart illustrating a twenty-ninth embodiment of a communication method according to the present disclosure.
[0048]
Fig. 38 is a flowchart illustrating a thirtieth embodiment of a communication method according to the present disclosure.
[0049]
Fig. 39 is a flowchart illustrating a thirty-first embodiment of a communication method according to the present disclosure.
[0050]
Fig. 40 is a structural schematic view illustrating an embodiment of a communication apparatus according to the present disclosure.
[0051]
Fig. 41 is a structural schematic view illustrating an embodiment of a device with a memory according to the present disclosure.

DETAILED DESCRIPTION

[0052]
Fig. 2 is a flowchart illustrating a first embodiment of a communication method according to the present disclosure. The execution subject of the communication method in accordance with the first embodiment may be a base station (BS) . The base station may be connected to a core network and may have a wireless communication with a user equipment, providing communication coverage for a corresponding region thereof. The base station may be a macro base station, a micro base station, a pico base station or femtocell. In some embodiments, the base station may also be called as the wireless base station, access point, B node, long term B node (eNodeB, eNB) , gNB or other suitable terms. As is shown in Fig. 2, the communication method may include the following blocks.
[0053]
In block S11: the base station may determine whether a QoS flow identifier is needed to be omitted in at least part of downlink messages sent to a UE, and execute block S12 when it is needed, otherwise execute block S13.
[0054]
Some user equipments themselves don’t support uplink reflective mapping functions. That is to say, they don’t have the ability to perform uplink reflective mapping functions, or they have temporarily or permanent limitations such that they cannot perform uplink reflective mapping functions, or they cannot perform uplink reflective mapping functions over one or some QoS flow or one or some DRBs. At this time, the QoS flow identifier is needed to be omitted in the at least part of downlink messages sent to the UE. In some application scenarios, for example, an application scenario in which there is only one QoS flow in an uplink DRB for communication between the UE and the base station, or an application scenario in which the base station has informed the UE to initialize /update a mapping relationship between QoS flows and DRBs, or an application scenario in which the UE has finished initializing /updating a mapping between the QoS flows and DRBs, the base station may decide to omit the QoS flow identifier in the at least part of downlink messages sent to the UE. That is to say, to omit the QoS flow identifier in the downlink messages which are mapped to one QoS flow or some QoS flows. Or to omit the QoS flow identifier in the downlink messages of QoS flows which are mapped to one DRB or some DRBs. Thus burden of air interface can be reduced.
[0055]
In specific, in one application example, the user equipment may send an informing message to the base station in some cases in which for the user equipment there exists a QoS flow without using the uplink reflective QoS mapping function. Then the base station may decide to omit the QoS flow identifier in the at least part of downlink messages sent to the UE according to the informing message. Or the base station may decide to omit the QoS flow identifier in the at least part of downlink messages sent to the UE when detecting that for the user equipment there exists a QoS flow without using the uplink reflective QoS mapping function. The at least part of messages is transmitted via the QoS flow which doesn’t use the uplink reflective QoS mapping function. In some cases, the base station requires to omit the QoS flow identifier in the at least part of downlink messages sent to the UE. For example, in the case in which downlink messages are mapped to one QoS flow or DRB. Of course, the base station may also decide to omit the QoS flow identifier in all downlink messages.
[0056]
In the block S12: the base station may omit the QoS flow identifier in the at least part of downlink messages sent to the UE.
[0057]
In the block S13: the base station may carry the QoS flow identifier in the at least part of downlink messages sent to the UE.
[0058]
The QoS flow identifier may be configured to identify QoS flows to which the uplink /downlink message is mapped. The UE and base station may perform a mapping between the uplink and downlink messages and the QoS flows, and a mapping between the QoS flows and DRBs through the QoS flow identifier. In NR system, the DRB defines a packet treatment over the air interface Uu, which is uplink /downlink message treatment. The DRB serves packets with a same packet forwarding treatment. Separate DRBs may be established for QoS flows requiring different packet forwarding treatments.
[0059]
In specific, in one application example, the base station may send an informing message to the user equipment, so as to inform the UE that it omits the QoS flow identifier in the at least part of downlink messages subsequently sent to the UE, when the base station decides that it is needed to omit the QoS flow identifiers in the at least part of downlink messages. The informing message may be a radio resource control message, a PDCP (Packet Data Convergence Protocol) data message, a SDAP (Service Data Adaptation Protocol) control /data message or a combination thereof, which is not specifically limited herein.
[0060]
In another application example, the base station may omit the SDAP header carrying the QoS flow identifier, or keep the SDAP header without carrying the QoS flow identifier, when deciding that it is needed to omit the QoS flow identifier in the at least part of downlink messages sent to the UE. The at least part of downlink messages may be downlink messages which are mapped to one QoS flow or DRB.
[0061]
The service data adaptation protocol transparent mode is defined as the mode that no service data adaptation protocol (SDAP) header is used for its data/control PDU.
[0062]
Certainly, in other application examples, the base station may also send an informing message to the UE, such that the UE also omits the QoS flow identifier in uplink messages subsequently sent to the base station, which is not specifically limited herein.
[0063]
With the implementation of the above embodiment, the base station determines whether it is needed to omit the QoS flow identifier in at least part of downlink messages sent to the UE, and omit the QoS flow identifier in at least part of downlink messages sent to the UE when it is needed. In this way, it is not needed for at least part of downlink messages to be marked with the QoS flow identifier over the air interface Uu, reducing the air interface Uu burden and increasing communication efficiency. Furthermore, the base station can control QoS mapping of the UE, increasing communication flexibility.
[0064]
Fig. 3 is a flowchart illustrating a second embodiment of a communication method according to the present disclosure. The communication method in the second embodiment is based on that in the first embodiment. The same details as that in the first embodiment will not be described herein. As shown in Fig. 3, the communication method may further include the following blocks.
[0065]
In block S111: the base station may determine whether it is needed to adopt a SDAP transparent mode to send the at least part of downlink messages.
[0066]
In block S112: the base station may decide that it is needed to omit the QoS flow identifier in the at least part of downlink messages sent to the UE when the SDAP transparent mode is needed to be adopted, otherwise decide that it isn’t needed to omit the QoS flow identifier in the at least part of downlink messages.
[0067]
In NR system, data processed by the new AS sub-layer (i.e. SDAP layer) has two formats, one of which is data with a SDAP header carrying the QoS flow identifier, and the other of which is data without a SDAP header, namely the SDAP transparent mode is adopted.
[0068]
In specific, in one application example, the base station may decide that it is needed to adopt the SDAP transparent mode to transmit the at least part of downlink messages, when the base station detects that the UE doesn’t use uplink reflective QoS mapping functions over one QoS flow or DRB, or there is only one QoS flow in the DRBs established between the base station and the UE. Thus, the base station may decide that it is needed to omit the QoS flow identifier in the at least part of downlink messages sent to the UE.
[0069]
In another application example, the UE may send an informing message to the base station, and then the base station may decide that it is needed to adopt the SDAP transparent mode to transmit the at least part of downlink messages according to the informing message, when the UE doesn’t use uplink reflective QoS mapping functions over one QoS flow or DRB, or there is only one QoS flow in the DRBs established between the base station and the UE. Thus, the base station may decide that it is needed to omit the QoS flow identifier in the at least part of downlink messages sent to the UE.
[0070]
Of course, in other application examples, the base station may also decide that it is needed to adopt the SDAP transparent mode to transmit the at least part of downlink messages, when it has sent an informing message to the UE, which indicates initializing /updating the mapping between the QoS flow and DRB, or received an acknowledge message from the UE, which indicates the mapping between the QoS flow and DRB is completed to be initialized /updated. It will not specifically be limited herein.
[0071]
Further, as shown in Figs. 2 and 3 together, the block S12 may include the following blocks.
[0072]
In block S121: the base station may send a notification message in a predetermined form to the UE.
[0073]
The notification message in the predetermined form may be at least one of a radio resource control message, a PDCP message and a SDAP control /data message. The notification message may be configured to notify the UE that the base station will subsequently send at least part of downlink message to it in the SDAP transparent mode.
[0074]
In specific, in one example, the base station sends the notification message in the predetermined form to the UE. The notification message in the predetermined form may include a DRB identifier and a transparent mode identifier. The UE may know that the base station will subsequently send at least part of downlink message to it in the SDAP transparent mode when receiving the notification message in the predetermined form. The at least part of downlink messages are mapped to all QoS flows belonging to DRB with the DRB identifier to be transmitted.
[0075]
In other examples, for the notification message in the predetermined form, at least one transparent mode identifier bit may also be arranged in a packet header thereof. The base station may also send a plurality of notification message in the predetermined form. The UE may also send at least part of uplink messages to the base station in the SDAP transparent mode after receiving the notification message in the predetermined form. It is not limited herein.
[0076]
In block S122: the base station may omit the SDAP header in the at least part downlink messages sent to the UE, wherein the SDAP header may carry the QoS flow identifier.
[0077]
In specific, the base station sends an notification message in a predetermined form to the UE, and omits the SDAP header carrying the QoS flow identifier in at least part of downlink messages subsequently sent to the UE, after deciding that it is needed to adopt the transparent mode to send the at least part of downlink message to the UE. In this way, the base station can omit the SDAP header carrying the QoS flow identifier in a message which is mapped to one or some QoS flows or one or some DRBs, even in one PDCP packet, achieving a purpose of reducing the air interface burden.
[0078]
In other embodiments, the block S121 may also be left out, which is not limited herein.
[0079]
Fig. 4 is a flowchart illustrating a third embodiment of a communication method according to the present disclosure. The communication method in the third embodiment is based on that in the second embodiment to further extend the block S111. The same details as that in the second embodiment will not be described herein. As shown in Fig. 4, the block S111 may further include the following blocks.
[0080]
In block S 1111: the base station may determine whether an uplink reflective QoS mapping function is used by the UE which the downlink messages points to.
[0081]
For some UEs, they don’t support the uplink reflective QoS mapping function. Namely, they don’t have the capability of achieving the uplink reflective QoS mapping function, or they have temporary /permanent limitation such that they cannot realizing the uplink reflective QoS mapping function, or they don’t use the uplink reflective QoS mapping function over one or some QoS flows or one or some DRBs on purpose of saving resource. The base station determines whether the uplink reflective mapping function is used by the UE via performance detection of the UE or uplink messages from the UE.
[0082]
In block S1112: the base station may decide that it is needed to adopt the SDAP transparent mode when the uplink reflective QoS mapping function is not used.
[0083]
When the UE doesn’t use the uplink reflective QoS mapping function, or there exists a QoS flow which doesn’t use the uplink reflective QoS mapping function, the base station decides that it is needed to adopt the SDAP transparent mode to send at least part of downlink messages to the UE.
[0084]
For example, if there exists a QoS flow A which doesn’t use the uplink reflective QoS mapping function at the UE side, the base station decides that it is needed to adopt the SDAP transparent mode to send at least part of downlink messages to the UE. The at least part of downlink messages have a mapping relationship with the QoS flow A.
[0085]
In this embodiment, the base station determines whether the uplink reflective QoS mapping function is used by the UE and decides that it is needed to adopt the SDAP transparent mode to send at least part of downlink messages to the UE when the UE doesn’t use the uplink reflective QoS mapping function or there exists a QoS flow which doesn’t use the uplink reflective QoS mapping function. In this way, the QoS flow identifier isn’t needed to be arranged in the at least part of downlink messages via the air interface, reducing the burden of the air interface.
[0086]
In other embodiments, the base station may also determine whether the SADP transparent mode is adopted to send at least part of downlink messages to the UE in other ways, which is not limited herein.
[0087]
Fig. 5 is a flowchart illustrating a fourth embodiment of a communication method according to the present disclosure. The communication method in the fourth embodiment is based on that in the second embodiment to extend the block S111. The same details as that in the second embodiment will not be described herein. As shown in Fig. 5, the block S111 may further include the following blocks.
[0088]
In block S1113: the base station may determine whether there is only one QoS flow in an uplink DRB established with the UE.
[0089]
In block S1114: the base station may decide that it is needed to adopt the SDAP transparent mode when there is only one QoS flow in the uplink DRB.
[0090]
A plurality of QoS flows may be mapped to one same DRB when the UE establishes an uplink DRB with the base station. Therefore, it is needed to adopt the QoS flow identifier to distinguish different QoS flows. However, when there is only one QoS flow in the uplink DRB, the requirement to distinguish different QoS flows won’t exist. Thus, the QoS flow identifier can be left out in the messages in this case.
[0091]
The base station determines whether there is only one QoS flow in the uplink DRB established with the UE via detection or uplink message send by the UE. Thus, the base station decides that it is needed to adopt the SDAP transparent mode when there is only one QoS flow, and adopts the SDAP transparent mode to send at least part of downlink messages to the UE. In this way, the QoS flow identifier isn’t needed to be arranged in the at least part of downlink messages via the air interface, reducing the burden of the air interface.
[0092]
Fig. 6 is a flowchart illustrating a fifth embodiment of a communication method according to the present disclosure. The communication method in the fifth embodiment is based on that in the second embodiment to further extend the block S121. The same details as that in the second embodiment will not be described herein. As shown in Fig. 6, the block S121 may further include the following block.
[0093]
In block S1211: the base station may send a radio resource control message loaded with the notification message to the UE, such that the UE subsequently sends at least part of uplink messages to the base station in the SDAP transparent mode.
[0094]
The radio resource control message may at least include a transparent mode identifier. Or the radio resource control message may at least include a transparent mode and at least a DRB identifier.
[0095]
In specific, referring to Figs. 6-7 together, after deciding that it is needed to adopt the SDAP transparent mode to send the at least part of downlink messages to the UE, the base station sends a radio resource control message loaded with the notification message to the UE, such as a radio resource control message in which a transparent mode identifier bit and a DRB identifier are arranged, so as to notify the UE that it subsequently sends at least part of downlink messages to the UE in the SDAP transparent mode. At the meantime, the UE may send at least part of uplink messages to the base station in the SDAP transparent mode. The downlink and uplink messages are mapped to a QoS flow belonging to a DRB with the DRB identifier.
[0096]
Of course, in other embodiments, the radio resource control message may include a plurality of transparent mode identifier bits, and may also include a plurality of DRB identifiers, which are not limited herein.
[0097]
Alternatively, after the block S1211, the block S121 further includes the following blocks.
[0098]
In block S1212: the base station may determine whether a radio resource control response message sent by the UE is received.
[0099]
In block S1213: the base station may further execute the block S122 when the radio resource control response message is received.
[0100]
Further referring to Figs. 6-7 together, the base station sends the radio resource control message to the UE. The UE sends the radio resource control response message to the base station after receiving the radio resource control message. Then the base station omits the SDAP header in the at least part of downlink message sent to the UE.
[0101]
In other embodiments, as the radio resource control message is reliably transferred, the aforementioned blocks S1212 and S1213 may be left out, which is not limited herein.
[0102]
The present embodiment may be combined with any one of the above embodiments.
[0103]
Fig. 8 is a flowchart illustrating a sixth embodiment of a communication method according to the present disclosure. The communication method in the sixth embodiment is based on that in the second embodiment to further extend the block S111. The same details as that in the second embodiment will not be described herein. As shown in Fig. 8, the block S111 may further include the following blocks.
[0104]
In block S1115: the base station may receive a radio resource control message sent by the UE.
[0105]
The radio resource control message may at least include a transparent mode identifier. Or the radio resource control message may at least include a transparent mode and at least a DRB identifier.
[0106]
In specific, referring to Figs. 8-9 together, in some cases, for example, one case in which the UE decides not to adopt the uplink reflective QoS mapping function over one DRB, the UE sends the radio resource control message, in which a transparent mode identifier bit and a DRB identifier (i.e. DRB ID) are arranged, so as to notify the UE that the base station subsequently sends at least part of downlink messages to it in the SDAP transparent mode. At the meantime, the UE may also send at least part of uplink messages to the base station in the SDAP transparent mode. The downlink and uplink messages are mapped to a QoS flow belonging to a DRB with the DRB identifier.
[0107]
Of course, in other embodiments, the radio resource control message may include a plurality of transparent mode identifier bits, and may also include a plurality of DRB identifiers. The UE may also send the radio resource control message in a specific situation, which is not limited herein.
[0108]
In block S1116: the base station may determine whether the transparent mode identifier in the received radio resource control message is a predetermined value.
[0109]
In block S1117: the base station may decide it is needed to adopt the SDAP transparent mode when the transparent mode identifier is the predetermined value.
[0110]
In specific, in one example, the radio resource control message sent by the UE to the base station may include a transparent mode identifier bit. The base station determines whether the transparent mode identifier bit is a predetermined value such as 1, after receiving the radio resource control message. The base station decides it is needed to adopt the SDAP transparent mode when the transparent mode identifier bit is 1.
[0111]
In other examples, the transparent mode identifier may also include two bits or more bits, and even a string. The predetermined value may be provided according to specific requirements, such as 1111, which is not limited herein.
[0112]
Alternatively, before the block S122, the communication method may include the following block.
[0113]
In block S1220: the base station may send a radio resource control response message to the UE, thereby informing the UE that it subsequently send at least part of downlink messages to the UE in the SDAP transparent mode.
[0114]
Further referring to Figs. 8-9 together, in the aforementioned example, the base station sends the radio resource control response message to the UE after receiving the radio resource control message sent by the UE, so as to inform the UE that it subsequently send at least part of downlink messages to the UE in the SDAP transparent mode.
[0115]
In other examples, the UE may subsequently send at least part of uplink messages to the base station in the SDAP transparent mode, which is not limited herein. In this embodiment, the block S121 may be left out.
[0116]
In other embodiments, as the radio resource control message is reliably transferred, the aforementioned blocks S1212 and S1213 may be left out, which is not limited herein.
[0117]
Fig. 10 is a flowchart illustrating a seventh embodiment of a communication method according to the present disclosure. The communication method in the seventh embodiment is based on that in the second embodiment to further extend the block S121. The same details as that in the second embodiment will not be described herein. As shown in Fig. 10, the block S121 may further include the following block.
[0118]
In block S1214: the base station may send a PDCP message loaded with the notification message to the UE, such that the UE subsequently send at least part of uplink messages to the base station in the SDAP transparent mode.
[0119]
The PDCP message may include at least a transparent mode identifier bit.
[0120]
In specific, referring to Figs. 10-11 together, in one example, the format of the PDCP message is shown in Fig. 11. When the first bit D/C is 1, then it indicates that the current message is the PDCP data message, and when the first bit D/C is 0, then it indicates that the current message is the PDCP control message. The second bit Q is the transparent mode identifier bit. When the second bit Q is 1, then it indicates that the SDAP transparent mode is used, and when the second bit Q is 0, then it indicates that the SDAP transparent mode is not used. The third to sixth bits are reserve bits. PDCP SN indicates the serial number of the PDCP message. The transmission and reception entity of the PDCP message are used for realizing sequence transmitting and receiving of PCDP data units via the PDCP SN. The PDCP sub-layer respectively maintains a reordering window at the transmitting side and the receiving side, whose size is 50%of the SN range. The PDCP SN with 18 bites is adopted herein. Other data indicates the protocol data unit of the PDCP message.
[0121]
In the above example, the base station sends a PDCP data message to the UE and sets the transparent mode identifier bit as 1 in the PDCP data message when deciding to adopt the SDAP transparent mode to send at lease part of downlink messages to the UE, so as to notify the UE that it subsequently sends at least part of downlink messages to the UE in the SDAP transparent mode, and notify the UE to send at least part of uplink messages to it in the SDAP transparent mode meanwhile. The base station may omit the SDAP header in subsequently-sent downlink messages which are mapped to a QoS flow via a PDCP data message with the transparent mode identifier bit as 1. The PDCP data message is mapped to the QoS flow. The base station may also omit the SDAP header in subsequently-sent downlink messages which are mapped to a DRB via a PDCP data message with the transparent mode identifier bit as 1. The PDCP data message is mapped to different QoS flows of the DRB. Thus to omit the SDAP header in the downlink messages for QoS flows, DRBs or PDCP messages is realized, thereby reducing air interface overhead.
[0122]
In other examples, the format of the PDCP data message may be set depending on specific requirements, which is not limited herein.
[0123]
The communication method in this embodiment may be combined with any one of the aforementioned embodiments.
[0124]
Fig. 12 is a flowchart illustrating an eighth embodiment of a communication method according to the present disclosure. The communication method in the eighth embodiment is based on that in the second embodiment to further extend the block S121. The same details as that in the second embodiment will not be described herein. As shown in Fig. 12, the block S121 may further include the following block.
[0125]
In block S1215: the base station may send a SDAP control message loaded with the notification message to the UE, so as to notify the UE to subsequently send at least part of uplink messages to the base station in the SDAP transparent mode.
[0126]
The SDAP control message may at least include a transparent mode identifier bit. Or the SDAP control message may at least include a transparent mode identifier bit and the QoS flow identifier.
[0127]
In specific, in one example, referring to Figs. 12-13 together, the base station sends a SDAP control message to the UE and sets the transparent mode identifier bit as 1 in the SDAP control message when deciding to adopt the SDAP transparent mode to send at lease part of downlink messages to the UE, so as to notify the UE that it subsequently sends at least part of downlink messages to the UE in the SDAP transparent mode, and notify the UE to send at least part of uplink messages to it in the SDAP transparent mode meanwhile.
[0128]
The format of the SDAP control message may be referred to that in Fig. 14. As shown in Fig. 14 (a) , when the first bit D/C is 1, then it indicates that the current message is the SDAP control message, and when the first bit D/C is 0, then it indicates that the current message is a SDAP data message. The second bit Q is the transparent mode identifier bit. When the second bit Q is 1, then it indicates that the SDAP transparent mode is used, and when the second bit Q is 0, then it indicates that the SDAP transparent mode is not used. Data bits R are reserve bits. The data bit QFI is the QoS flow identifier. A data format shown in Fig. 14 (b) is similar to that in Fig. 14 (a) , which will not be described herein. The difference therebetween lies that the data bit QFI is not carried in the data format shown in Fig. 14 (b) .
[0129]
In the above example, when the base station sends the SDAP control message with the data format shown in Fig, 14 (a) to the UE, it subsequently sends at least part of downlink messages to the UE in the SDAP transparent mode, which are mapped to a QoS flow with the data bit QFI. When the base station sends the SDAP control message with the data format shown in Fig, 14 (b) to the UE, it subsequently sends at least part of downlink messages to the UE in the SDAP transparent mode, which are mapped to one DRB. The DRB identifier may be obtained from lower layer header, such PDCP header or MAC (Media Access Control) header. Therefore, the base station may achieve to omit the SDAP header in the downlink messages for QoS flows or DRBs, thereby reducing the air interface overhead.
[0130]
Of course, the SDAP control message may also be with other formats, and the UE may also send a SDAP reception acknowledge message to the base station, which are not limited herein.
[0131]
The communication method in this embodiment may be combined with any one of the aforementioned embodiments.
[0132]
Fig. 15 is a flowchart illustrating a ninth embodiment of a communication method according to the present disclosure. The communication method in the ninth embodiment is based on that in the first embodiment to further extend the block S11. The same details as that in the first embodiment will not be described herein. As shown in Fig. 15, the block S11 may further include the following blocks.
[0133]
In block S113: the base station may send downlink messages carrying a SDAP header with the QoS flow identifier, thereby informing the UE to map QoS flows with the QoS flow identifier to a corresponding DRB.
[0134]
The downlink messages carrying the SDAP header with the QoS flow identifier may include at least one of a SDAP control message and a SDAP data message. They may be configured to inform the UE to initialize or update the mapping between the QoS flows and DRB.
[0135]
In block S114: the base station may determine whether a quality of the sent downlink messages or duration during which the downlink messages are continuously sent meets a predetermined condition.
[0136]
In block S115: the base station may further decide that it is needed to omit the QoS flow identifier in at least part of downlink messages sent to the UE when the preset condition is met.
[0137]
The preset condition may be that the duration is greater than one threshold value. And it may also be that the quality is greater than one threshold value. The threshold value may be set with actual requirements, which is not limited herein.
[0138]
In specific, in one example, the base station continuously or discontinuously sends downlink messages carrying the SDAP header with the QoS flow identifier to the UE, such as the SDAP control messages, such that the UE maps the QoS flows with the QoS flow identifier to a corresponding DRB, for instance, mapping the QoS flow with the QoS flow identifier as x to the DRB whose identifier as y. In this way, the UE finishes initializing or updating the mapping relationship between the QoS flows and DRBs. The base station decides that the UE has completed initializing or updating the mapping relationship between the QoS flows and the DRBs, when the preset condition is met, and thus decides that it is needed to omit the QoS flow identifier in at least part of downlink messages send to the UE. The at least part of downlink messages may be all downlink messages which are mapped to the QoS flow with QoS flow identifier, or the DRB corresponding to QoS flow identifier. It is not limited herein.
[0139]
In this embodiment, the base station determines whether the quality of the sent downlink messages or the duration during which the downlink messages are continuously sent, which carries the SDAP header with the QoS flow identifier, meets a predetermined condition. And the base station further decides that it is needed to omit the QoS flow identifier in at least part of downlink messages sent to the UE when it meets the preset condition. In this way, the base station will send at least part of downlink message without the QoS flow identifier over the air interface, reducing air interface burden and increasing communication efficiency.
[0140]
In other embodiment, the base station may also un-omit the QoS flow identifier in a specific situation or further determine whether it is needed to omit the QoS flow identifier. It is not limited herein.
[0141]
Fig. 16 is a flowchart illustrating a tenth embodiment of a communication method according to the present disclosure. The communication method in the tenth embodiment is based on that in the ninth embodiment to further extend the block S114. The same details as that in the ninth embodiment will not be described herein. As shown in Fig. 16, the block S114 may further include the following blocks.
[0142]
In block S1141: the base station may determine that the quality of the sent downlink messages is greater than a first predetermined value;
[0143]
The first predetermined value may be a threshold set by the network in advance. A value thereof is set depending on the network and the UE, which is not specifically limited herein.
[0144]
In block S1142: the base station may decide that the predetermined condition is met when it is greater than the first predetermined value.
[0145]
In specific, in one example, the base station continuously or discontinuously sends downlink messages carrying the SDAP header with the QoS flow identifier, such as SDAP data messages, and meanwhile turns on a timer which may be configured to calculate the quality of the sent downlink messages. The base station determines whether the quality of the sent downlink messages is greater than the first predetermined value such as 10, decides that it meets when it is, and then the base station continues to execute subsequent blocks.
[0146]
In other example, the downlink messages may be messages in other types, such as PDCP messages, which is not limited herein.
[0147]
Fig. 17 is a flowchart illustrating an eleventh embodiment of a communication method according to the present disclosure. The communication method in the tenth embodiment is based on that in the tenth embodiment to further extend the block S1141. The same details as that in the ninth embodiment will not be described herein. As shown in Fig. 17, the block S1141 may further include the following block.
[0148]
In block S11411: the base station may determine whether a quality of the continuously-sent downlink messages is greater than the first predetermined value.
[0149]
In specific, in one example, the base station continuously sends downlink messages carrying the SDAP header with the QoS flow identifier such as SDAP data messages, and meanwhile turns on a timer which is configured to calculate the quality of the sent downlink messages. The base station determines whether the quality of the sent downlink messages is greater than the first predetermined value such as 10, decides that it meets when it is, and then the base station continues to execute subsequent blocks. Otherwise, the base station continuously sends downlink messages.
[0150]
In other example, the downlink messages may be messages in other types, such as PDCP messages, which is not limited herein.
[0151]
Fig. 18 is a flowchart illustrating a twelfth embodiment of a communication method according to the present disclosure. The communication method in the twelfth embodiment is based on that in the ninth embodiment to further extend the block S114. The same details as that in the ninth embodiment will not be described herein. As shown in Fig. 18, the block S114 may further include the following blocks.
[0152]
In block S1143: the base station may determine that a duration during which it continuously sends the downlink message to the UE is greater than a second predetermined value;
[0153]
The second predetermined value may be a threshold set by the network in advance. A value thereof is set depending on the network and the UE, which is not specifically limited herein.
[0154]
In block S1144: the base station may decide that the predetermined condition is met when it is greater than the second predetermined value.
[0155]
In specific, in one example, the base station continuously sends downlink messages carrying the SDAP header with the QoS flow identifier, such as SDAP data messages, and meanwhile turns on a timer which may be configured to calculate the duration during which the base station continuously sends the downlink messages. The base station determines whether the duration is greater than the second predetermined value such as 1 minute, decides that it meets the preset condition when it is, and then continues to execute subsequent blocks. Otherwise, the base station continuously sends downlink messages.
[0156]
In other example, the downlink messages may be messages in other types, such as PDCP messages, which is not limited herein.
[0157]
Fig. 19 is a flowchart illustrating a thirteenth embodiment of a communication method according to the present disclosure. The communication method in the thirteenth embodiment is based on that in the first embodiment to further extend the block S11. The same details as that in the first embodiment will not be described herein. As shown in Fig. 19, the block S11 may further include the following blocks.
[0158]
In block S116: the base station may determine whether it has sent a radio resource control message for updating the mapping relationship between QoS flows and DRBs to the UE.
[0159]
The radio resource control message may at least include the QoS flow identifier.
[0160]
In block S117: the base station may further decide that it is needed to omit the QoS flow identifier in at least part of downlink messages sent to the UE when it has.
[0161]
Referring to Figs. 19 and 20, in one example, the base station sends the radio resource control message for updating the mapping relationship between QoS flows and DRBs to the UE when it requires to notify the UE to initialize or update the mapping relationship between QoS flows and DRBs. The radio resource control message includes the QoS flow identifier QFI and the DRB identifier. The UE may map the QoS flow with the QoS flow identifier QFI to the DRB with the DRB identifier after receiving the radio resource control message. The base station may further decide that it is needed to omit the QoS flow identifier in at least part of downlink messages sent to the UE after deciding that it has sent the radio resource control message to the UE. Therefore, the at least part of downlink messages is being without the QoS flow identifier over the air interface, reducing air interface burden and increasing communication efficiency.
[0162]
In this embodiment, as the radio resource control message is reliably transferred, the base station may consider that the UE has received the radio resource control message without receiving a mapping acknowledge message sent by the UE.
[0163]
Of course, the UE may also send a mapping acknowledge to the base station in other example, which is not limited herein.
[0164]
Fig. 21 is a flowchart illustrating a fourteenth embodiment of a communication method according to the present disclosure. The communication method in the fourteenth embodiment is based on that in the first embodiment to further extend the block S11. The same details as that in the ninth embodiment will not be described herein. As shown in Fig. 21, the block S11 may further include the following blocks.
[0165]
In block S118: the base station may determine whether it receives a mapping acknowledge message sent by the UE.
[0166]
The mapping acknowledge message may include at least one of the following: a SDAP control message, a SDAP data message, a radio resource control message and a PDCP control message. The specific format of the mapping acknowledge message may be set depending on specific requirements, which is not limited herein.
[0167]
In block S119: the base station may decide that it is needed to omit the QoS flow identifier in at least part of downlink messages sent to the UE when receiving the mapping acknowledge message.
[0168]
Referring to Figs. 20 and 21, in one example, the base station sends the downlink message carrying the SDAP header with the QoS flow identifier QFI or the radio resource control message for updating the mapping relationship between QoS flows and DRBs to the UE when it requires to notify the UE to initialize or update the mapping relationship between QoS flows and DRBs. The UE may map the QoS flow with the QoS flow identifier QFI to the DRB with the DRB identifier after receiving the downlink message or radio resource control message, for example, mapping the QoS flow with QFI as x to the DRB with the DRB identifier as y, and then sends the mapping acknowledge message to the base station. The base station may decide that it is needed to omit the QoS flow identifier in at least part of downlink messages sent to the UE after receiving the mapping acknowledge message, and then sends at least part of downlink messages without the QoS flow identifier to the UE.
[0169]
In other examples, the UE may send a plurality of mapping acknowledge messages to the base station, which is not limited herein.
[0170]
The communication method in this embodiment may also be combined with any one in the ninth to thirteenth embodiment.
[0171]
Fig. 22 is a flowchart illustrating a fifteenth embodiment of a communication method according to the present disclosure. The communication method in the fifteenth embodiment is based on that in the first embodiment to further extend the block S12. The same details as that in the first embodiment will not be described herein. As shown in Fig. 22, the block S12 may further include the following blocks.
[0172]
In block S123: the base station may un-carry the QoS flow identifier in the SDAP header of the at least part of downlink messages, or un-carry the SDAP header in the at least part of downlink messages.
[0173]
In specific, the base station may un-carry the QoS flow identifier in the SDAP header of the at least part of downlink messages sent to the UE, after deciding that it is needed to omit the QoS flow identifier in the at least part of downlink messages sent to the UE. That is to say, the base station remains the SDAP header, but un-carries the QoS in the SDAP header. The base station may also un-carry the SDAP header in the at least part of downlink messages sent to the UE. For instance, the base station sends the at least part of downlink messages in the SDAP transparent mode.
[0174]
The communication method in this embodiment may also be combined with that in any one in the ninth to thirteenth embodiment.
[0175]
Fig. 23 is a flowchart illustrating a sixteenth embodiment of a communication method according to the present disclosure. The communication method in the sixteenth embodiment is based on that in the fourteenth embodiment to further extend the block S118. The same details as that in the fourteenth embodiment will not be described herein. As shown in Fig. 23, the block S118 may further include the following blocks.
[0176]
In block S1181: the base station may determine whether a value of an acknowledge bit in the SDAP control message is a third predetermined value.
[0177]
The SDAP control message may include the QoS flow identifier and an acknowledge bit. The third predetermined value may be set depending on specific requirements, which is not limited herein.
[0178]
In block S1182: the base station may decide that it has received the mapping acknowledge message sent by the UE when it is the third predetermined value.
[0179]
In one example, the format of the SDAP control message may be referred to that in Fig. 24. As shown in Fig. 24, when the first bit D/C is 1, then it indicates that the current message is the SDAP control message, and when the first bit D/C is 0, then it indicates that the current message is a SDAP data message. The second bit Q is the transparent mode identifier bit. When the second bit Q is 1, then it indicates that the SDAP transparent mode is used, and when the second bit Q is 0, then it indicates that the SDAP transparent mode is not used. The third bit A is the acknowledge bit. When the third bit A is 1, then it indicates that mapping has been completed, and when the third bit A is 0, then it indicates that mapping hasn’t been completed. The data bits R are reserve bits. Data bit QFI is the QoS flow identifier. The base station determines the third bit A in the SDAP control message is the third predetermined value which is 1, after receiving the SDAP control message sent by the UE. When the third bit A is 1, the base station decides that it has received the mapping acknowledge message sent by the UE, otherwise decides that it hasn’t received the mapping acknowledge message sent by the UE.
[0180]
In other examples, the SDAP control message may also be in other types, which is not limited herein.
[0181]
Fig. 25 is a flowchart illustrating a seventeenth embodiment of a communication method according to the present disclosure. The communication method in the seventeenth embodiment is based on that in the fourteenth embodiment to further extend the block S118. The same details as that in the fourteenth embodiment will not be described herein. As shown in Fig. 25, the block S118 may further include the following blocks.
[0182]
In block S1183: the base station may determine whether a payload size of a PDU of an uplink data message from the UE is zero bit.
[0183]
In block S1184: the base station may decide that it has received the mapping acknowledge message sent by the UE when it is.
[0184]
As the data length of the SDAP data message is zero bit, or data length of the payload of the PDCP message corresponding to the SDAP data message is zero bit, the base station determines whether the payload size of the PDU of the unlink data message is zero bit when receiving the uplink data message from the UE, and decides that it has received the mapping acknowledge message sent by the UE when it is zero bit, so as to continue to execute subsequent blocks.
[0185]
In other embodiments, the data length of the SDAP data message may also be set as a preset value, or a bit with a preset value may be set in the SDAP data message to as the mapping acknowledge message. It is not limited herein.
[0186]
Fig. 26 is a flowchart illustrating an eighteenth embodiment of a communication method according to the present disclosure. The communication method in the eighteenth embodiment is based on that in the fourteenth embodiment to further extend the block S118. The same details as that in the fourteenth embodiment will not be described herein. As shown in Fig. 26, the block S118 may further include the following blocks.
[0187]
In block S1185: the base station may determine whether a value of an acknowledge bit in the SDAP control message is a fourth predetermined value.
[0188]
The SDAP control message may include the QoS flow identifier and an acknowledge bit. The fourth predetermined value may be set depending on specific requirements, which is not limited herein.
[0189]
In block S1186: the base station may decide that it has received the mapping acknowledge message sent by the UE when it is.
[0190]
In one example, the format of the SDAP control message may be referred to that in Fig. 24, which will not be described herein. The base station determines the third bit A in the SDAP control message is the fourth predetermined value which is 1, after receiving the SDAP control message sent by the UE. When the third bit A is 1, the base station decides that it has received the mapping acknowledge message sent by the UE, and omits the QoS flow identifier in the at least part of downlink messages subsequently sent to the UE. The at least part of downlink messages are ones which are mapped to the QoS flow with the QoS flow identifier. Otherwise the base station decides that it hasn’t received the mapping acknowledge message sent by the UE.
[0191]
In other examples, the SDAP control message may also be in other types. For example, the SDAP data message includes an acknowledge bit A with one bit and the QoS flow identifier QFI with seven bits. It is not limited herein.
[0192]
Fig. 27 is a flowchart illustrating an eighteenth embodiment of a communication method according to the present disclosure. The communication method in the eighteenth embodiment is based on that in the fourteenth embodiment to further extend the block S118. The same details as that in the fourteenth embodiment will not be described herein. As shown in Fig. 27, the block S118 may further include the following blocks.
[0193]
In block S1187: the base station may determine whether the QoS flow identifier is included in a header of an uplink data message from the UE, and whether a DRB corresponding to the SDAP data message is a preset DRB.
[0194]
The header of the SDAP data message may at least include the QoS flow identifier. The preset DRB is the one with a preset DRB identifier, and corresponding to downlink messages transferred in the QoS flow with the QoS flow identifier.
[0195]
In other embodiments, the DRB identifier may also be set with actual requirements, which is not limited herein.
[0196]
In block S1188: the base station may decide that it has received the mapping acknowledge message sent by the UE when the QoS flow identifier is included and it is the preset DRB.
[0197]
In one example, the format of the SDAP control message may similarly be referred to that in Fig. 24, which will not be described herein. The SDAP data message is transferred to the base station via one DRB. The base station determines whether the header of the SDAP data message includes the QoS flow identifier and determines whether the DRB corresponding to the SDAP data message is the preset DRB, and decides that it has received the mapping acknowledge message and omits the QoS flow identifier in the at least part of downlink messages subsequently sent to the UE when it includes and it is. The at least part of downlink messages are ones which are mapped to the QoS flow with the QoS flow identifier. Otherwise the base station decides that it hasn’t received the mapping acknowledge message sent by the UE.
[0198]
In other examples, the SDAP control message may also be in other types. For example, the header only includes the QoS flow identifier, which is not limited herein.
[0199]
Fig. 28 is a flowchart illustrating a twentieth embodiment of a communication method according to the present disclosure. The execution subject of communication method in accordance with a twentieth embodiment may be a user equipment (UE) . The UE may be fixed and also mobile, such as cellular phones, personal digital assistants (PDA) , wireless modems, tablet PCs, laptops, cordless phones, etc. As shown in FIG. 28, the communication method may include the following blocks in this embodiment.
[0200]
In block S21: the UE may determine whether a QoS flow identifier is needed to be omitted in at least part of uplink messages sent to a base station, and execute block S22 when it is needed, otherwise execute block S23.
[0201]
Some user equipments themselves don’t support uplink reflective mapping functions, that is to say, they don’t have the ability to perform uplink reflective mapping functions, or they have temporarily or permanent limitations such that they cannot perform uplink reflective mapping functions, or they cannot perform uplink reflective mapping functions over one or some QoS flow or one or some DRBs. At this time, The QoS flow identifier is needed to be omitted in the at least part of downlink messages sent to the base station. In some application scenarios, for example, an application scenario in which there is only one QoS flow in an uplink DRB for communication between the UE and the base station, or an application scenario in which the base station has informed the UE to initialize /update a mapping relationship between QoS flows and DRBs, or an application scenario in which the UE has finished initializing /updating a mapping relationship between the QoS flows and DRBs, the UE may decide to omit the QoS flow identifier in the at least part of uplink messages sent to the base station. That is to say, to omit the QoS flow identifier in the uplink messages which are mapped to one QoS flow or some QoS flows. Or to omit the QoS flow identifier in the uplink messages of QoS flows which are mapped to one DRB or some DRBs. Thus burden of air interface can be reduced.
[0202]
In specific, in one application example, the user equipment may decide that it is needed to omit the QoS flow identifier in at least part of uplink messages in some cases in which for the user equipment there exists a QoS flow without using the uplink reflective QoS mapping function. The above-mentioned at least part of uplink messages are mapped to the QoS flow without using the uplink reflective QoS mapping function. Or The UE may decide to omit the QoS flow identifier in the at least part of uplink messages sent to the UE according to an informing message when receiving the informing message. In some cases, the UE requires to omit the QoS flow identifier in the at least part of uplink messages sent to the base station. For example, in the case in which uplink messages are mapped to one QoS flow or DRB. Of course, the UE may also decide to omit the QoS flow identifier in all uplink messages.
[0203]
In the block S12: the UE may omit the QoS flow identifier in the at least part of uplink messages sent to the base station.
[0204]
In the block S13: the UE may carry the QoS flow identifier in the at least part of uplink messages sent to the base station.
[0205]
The QoS flow identifier may be configured to identify QoS flows to which the uplink /downlink message is mapped. The UE and base station may perform a mapping between the uplink and downlink messages and the QoS flows, and a mapping between the QoS flows and DRBs through the QoS flow identifier. In NR system, the DRB defines a packet treatment over the air interface Uu, which is uplink /downlink message treatment. The DRB serves packets with a same packet forwarding treatment. Separate DRBs may be established for QoS flows requiring different packet forwarding treatments.
[0206]
In specific, in one application example, the base station may send an informing message to the user equipment, when the base station decides that it is needed to omit the QoS flow identifiers in the at least part of downlink messages. The UE may receive the informing message and then omit the QoS flow identifier in the at least part of uplink messages subsequently sent to the base station according the informing message. The informing message may be a radio resource control message, a PDCP data message, a SDAP control /data message or a combination thereof, which is not specifically limited herein.
[0207]
In another application example, the UE may omit the SDAP header carrying the QoS flow identifier, or keep the SDAP header without carrying the QoS flow identifier, when deciding that it is needed to omit the QoS flow identifier in the at least part of uplink messages sent to the base station. The at least part of uplink messages may be uplink messages which are mapped to one QoS flow or DRB.
[0208]
Certainly, in other application examples, the UE may also send an informing message to the base station, so as to inform the base station that the UE also omits the QoS flow identifier in uplink messages subsequently sent to the base station, which is not specifically limited herein.
[0209]
With the implementation of the above embodiment, the UE determines whether it is needed to omit the QoS flow identifier in at least part of uplink messags sent to the base station, and omit the QoS flow identifier in at least part of uplink messags sent to the base station when it is needed. In this way, it is not needed for at least part of uplink messages to be marked with the QoS flow identifier over the air interface Uu, reducing the air interface Uu burden and increasing communication efficiency. Furthermore, the base station may control QoS mapping of the UE, increasing communication flexibility.
[0210]
Fig. 29 is a flowchart illustrating a twenty-first embodiment of a communication method according to the present disclosure. The communication method in the twenty-first embodiment is based on that in the twentieth embodiment. The same details as that in the twentieth embodiment will not be described herein. As shown in Fig. 29, the communication method may further include the following blocks.
[0211]
In block S211: the UE may determine whether it is needed to adopt a SDAP transparent mode to send the at least part of uplink messages.
[0212]
In block S212: the UE may decide that it is needed to omit the QoS flow identifier in the at least part of uplink messages sent to the base station when the SDAP transparent mode is needed to be adopted, otherwise decide that it isn’t needed to omit the QoS flow identifier in the at least part of uplink messages.
[0213]
In NR system, data processed by the new AS sub-layer (i.e. SDAP layer) has two formats, one of which is data with a SDAP header carrying the QoS flow identifier, and the other of which is data without a SDAP header, namely the SDAP transparent mode is adopted.
[0214]
In specific, in one application example, the UE may decide that it is needed to adopt the SDAP transparent mode to transmit the at least part of uplink messages, when the UE doesn’t use uplink reflective QoS mapping functions over one QoS flow or DRB, or there is only one QoS flow in the DRBs established between the base station and the UE. Thus, the UE may decide that it is needed to omit the QoS flow identifier in the at least part of uplink messages sent to the base station.
[0215]
In another application example, the UE may also send an informing message to the base station, so as to inform the base station to subsequently adopt the SDAP transparent mode to transmit the at least part of uplink messages, which is not limited herein.
[0216]
Further, as shown in Figs. 2 and 3 together, the block S12 may include the following block.
[0217]
In block S221: the UE may omit the SDAP header in the at least part uplink messages sent to the base station, wherein the SDAP header may carry the QoS flow identifier.
[0218]
In specific, the UE omits the SDAP header carrying the QoS flow identifier in at least part of uplink messages subsequently sent to the base station, after deciding that it is needed to adopt the transparent mode to send the at least part of uplink message to the base station. In this way, the UE can omit the SDAP header carrying the QoS flow identifier in a message which is mapped to one or some QoS flows or one or some DRBs, even in one PDCP packet, achieving a purpose of reducing the air interface burden.
[0219]
Fig. 30 is a flowchart illustrating a twenty-second embodiment of a communication method according to the present disclosure. The communication method in the twenty-second embodiment is based on that in the twentieth embodiment to further extend the block S211. The same details as that in the twenty-first embodiment will not be described herein. As shown in Fig. 30, the block S211 may further include the following blocks.
[0220]
In block S 2111: the UE may determine whether it uses an uplink reflective QoS mapping function.
[0221]
In block S2112: the UE may decide that it is needed to adopt the SDAP transparent mode when the uplink reflective QoS mapping function is not used.
[0222]
When the UE doesn’t use the uplink reflective QoS mapping function, or there exists a QoS flow which doesn’t use the uplink reflective QoS mapping function, the UE decides that it is needed to adopt the SDAP transparent mode to send at least part of uplink messages to the UE. Therefore, the at least part of uplink messages don’t need to set the QoS flow identifier over the air interface, reducing the burden fo the air interface.
[0223]
For example, if there exists a QoS flow A which doesn’t use the uplink reflective QoS mapping function at the UE side, the UE decides that it is needed to adopt the SDAP transparent mode to send at least part of uplink messages to the UE. The at least part of uplink messages have a mapping relationship with the QoS flow A.
[0224]
In other embodiments, the UE may also determine whether the SADP transparent mode is adopted to send at least part of uplink messages to the base station in other ways, which is not limited herein.
[0225]
Fig. 31 is a flowchart illustrating a twenty-third embodiment of a communication method according to the present disclosure. The communication method in the twenty-third embodiment is based on that in the twenty-first embodiment to extend the block S211. The same details as that in the second embodiment will not be described herein. As shown in Fig. 31, the block S211 may further include the following blocks.
[0226]
In block S2113: the UE may determine whether there is only one QoS flow in an uplink DRB established with the base station.
[0227]
In block S2114: the UE may decide that it is needed to adopt the SDAP transparent mode when there is only one QoS flow in the uplink DRB.
[0228]
A plurality of QoS flows may be mapped to one same DRB when the UE establishes an uplink DRB with the base station. Therefore, it is needed to adopt the QoS flow identifier to distinguish different QoS flows. However, when there is only one QoS flow in the uplink DRB, the requirement to distinguish different QoS flows won’t exist. Thus, the QoS flow identifier can be left out in the messages in this case.
[0229]
The UE determines whether there is only one QoS flow in the uplink DRB established with the base station via detection. Thus, the UE decides that it is needed to adopt the SDAP transparent mode when there is only one QoS flow, and adopts the SDAP transparent mode to send at least part of uplink messages to the base station. In this way, the QoS flow identifier isn’t needed to be arranged in the at least part of uplink messages via the air interface, reducing the burden of the air interface.
[0230]
Fig. 32 is a flowchart illustrating a twenty-fourth embodiment of a communication method according to the present disclosure. The communication method in the twenty-fourth embodiment is based on that in the twenty-first embodiment to further extend the block S211. The same details as that in the twenty-first embodiment will not be described herein. As shown in Fig. 32, the block S211 may further include the following blocks.
[0231]
In block S2115: the UE may determine whether it receives a radio resource control message loaded with a notification message in a predetermined form from the base station.
[0232]
The radio resource control message may at least include a transparent mode identifier. Or the radio resource control message may at least include a transparent mode and at least a DRB identifier.
[0233]
In block S2116: the UE subsequently may decide that it is needed to send at least part of uplink messages to the base station in the SDAP transparent mode when it has received the radio resource control message.
[0234]
Alternatively, after the block S2116, the block S211 further includes the following block.
[0235]
In block S1212: the UE may send a radio resource control response message to the base station, such that the base station subsequently sends at least part of downlink messages to the UE in the SDAP transparent mode.
[0236]
In this embodiment, the specific communication process between the UE and base station may be referred to what described in the fifth embodiment, which will not be described herein. The method in this embodiment may also be combined with that in any one of the twenty-first to twenty-third embodiments.
[0237]
Fig. 33 is a flowchart illustrating a twenty-fifth embodiment of a communication method according to the present disclosure. The communication method in the twenty-fifth embodiment is based on that in the twenty-first embodiment to further extend the block S211. The same details as that in the twenty-first embodiment will not be described herein. As shown in Fig. 33, the block S111 may further include the following blocks.
[0238]
In block S2118: the UE may determine whether it has sent a radio resource control message loaded with a notification message in a predetermined form to the base station.
[0239]
The radio resource control message may at least include a transparent mode identifier. Or the radio resource control message may at least include a transparent mode and at least a DRB identifier.
[0240]
In block S2119: the UE may decide that it is needed to send at least part of uplink messages in the SDAP transparent mode when it has sent the radio resource control message to the base station.
[0241]
Alternatively, before deciding it is needed to adopt the SDAP transparent mode in the block S2119, the communication method may include the following blocks.
[0242]
In block S2120: the UE may determine whether it receives a radio resource control response message from the base station.
[0243]
In block S2121: the UE may further decide that it is needed to adopt the SDAP transparent mode to send at least part of uplink messages when it receives the radio resource control response message.
[0244]
In this embodiment, the specific communication process between the UE and base station may be referred to what described in the sixth embodiment, which will not be described herein.
[0245]
Fig. 34 is a flowchart illustrating a twenty-sixth embodiment of a communication method according to the present disclosure. The communication method in the twenty-sixth embodiment is based on that in the twenty-first embodiment to further extend the block S211. The same details as that in the twenty-first embodiment will not be described herein. As shown in Fig. 34, the block S211 may further include the following blocks.
[0246]
In block S2122: the UE may receive a PDCP message from the base station.
[0247]
The header of the PDCP message may include at least a transparent mode identifier bit.
[0248]
In block S2123: the UE may determine whether the transparent mode identifier bit is a preset value.
[0249]
In block S2124: the UE may decide that it is needed to adopt the SDAP transparent mode to send at least part of uplink messages when the transparent mode identifier bit is the preset value.
[0250]
In this embodiment, the specific communication process between the UE and base station and the format of the PDCP message may be referred to what described in the seventh embodiment, which will not be described herein. The method in this embodiment may also be combined with that in any one of the twenty-first to twenty-third embodiments.
[0251]
Fig. 35 is a flowchart illustrating a twenty-seventh embodiment of a communication method according to the present disclosure. The communication method in the twenty-seventh embodiment is based on that in the twenty-first embodiment to further extend the block S211. The same details as that in the twenty-first embodiment will not be described herein. As shown in Fig. 35, the block S211 may further include the following blocks.
[0252]
In block S1215: the UE may receive a SDAP control message from the base station.
[0253]
The SDAP control message may at least include a transparent mode identifier bit. Or the SDAP control message may at least include a transparent mode identifier bit and the QoS flow identifier.
[0254]
In block S2126: the UE may determine whether the transparent mode identifier bit is a preset value.
[0255]
In block S2124: the UE may decide that it is needed to adopt the SDAP transparent mode to send at least part of uplink messages when the transparent mode identifier bit is the preset value.
[0256]
In this embodiment, the specific communication process between the UE and base station and the format of the SDAP message may be referred to what described in the eighth embodiment, which will not be described herein. The method in this embodiment may also be combined with that in any one of the nineteenth to twenty-first embodiments.
[0257]
Fig. 36 is a flowchart illustrating a twenty-eighth embodiment of a communication method according to the present disclosure. The communication method in the twenty-eighth embodiment is based on that in the twentieth embodiment to further extend the block S21. The same details as that in the twentieth embodiment will not be described herein. As shown in Fig. 36, the block S21 may further include the following blocks.
[0258]
In block S213: the UE may determine whether it receives downlink messages carrying a SDAP header with the QoS flow identifier, thereby mapping QoS flows with the QoS flow identifier to a corresponding DRB.
[0259]
In block S214: the UE may decide that it is needed to omit the QoS flow identifier in at least part of uplink messages sent to the base station when receiving the downlink messages.
[0260]
In this embodiment, the specific communication process between the UE and base station may be referred to what described in the ninth embodiment, which will not be described herein.
[0261]
Fig. 37 is a flowchart illustrating a twenty-ninth embodiment of a communication method according to the present disclosure. The communication method in the twenty-ninth embodiment is based on that in the twentieth embodiment to further extend the block S21. The same details as that in the twentieth embodiment will not be described herein. As shown in Fig. 37, the block S21 may further include the following blocks.
[0262]
In block S215: the UE may determine whether it receives a radio resource control message for updating the mapping relationship between QoS flows and DRBs to the UE, thereby mapping QoS flows with the QoS flow identifier to a corresponding DRB.
[0263]
The radio resource control message may at least include the QoS flow identifier.
[0264]
In block S216: the base station may decide that it is needed to omit the QoS flow identifier in at least part of uplink messages sent to the base station when it receives the radio resource control message.
[0265]
In this embodiment, the specific communication process between the UE and base station may be referred to what described in the thirteenth embodiment, which will not be described herein.
[0266]
Fig. 38 is a flowchart illustrating a thirtieth embodiment of a communication method according to the present disclosure. The communication method in the thirtieth embodiment is based on that in the twenty-eighth or twenty-ninth embodiment to further extend the block S216. The same details as that in the twenty-eighth or twenty-ninth embodiment will not be described herein. As shown in Fig. 38, after the block S216, the communication method includes the following block.
[0267]
In block S217: the UE may send a mapping acknowledge message to the base station, such that the base station subsequently omit the QoS flow identifier in at least part of downlink message sent to the UE.
[0268]
The mapping acknowledge message may include at least one of the following: a SDAP control message, a SDAP data message, a radio resource control message and a PDCP control message. The specific format of the mapping acknowledge message may be set depending on specific requirements, which is not limited herein.
[0269]
In this embodiment, the specific communication process between the UE and base station and the format of the mapping acknowledge message may be referred to what described in the fourteenth, sixteenth to nineteenth embodiments, which will not be described herein. The method in this embodiment may also be combined with that in any one of the nineteenth to twenty-first embodiments.
[0270]
Fig. 39 is a flowchart illustrating a thirty-first embodiment of a communication method according to the present disclosure. The communication method in the thirty-first embodiment is based on that in the twentieth embodiment to further extend the block S22. The same details as that in the twentieth embodiment will not be described herein. As shown in Fig. 39, the block S22 may further include the following block.
[0271]
In block S223: the UE may un-carry the QoS flow identifier in the SDAP header of the at least part of uplink messages, or un-carry the SDAP header in the at least part of uplink messages.
[0272]
In specific, the UE may un-carry the QoS flow identifier in the SDAP header of the at least part of uplink messages sent to the base station, after deciding that it is needed to omit the QoS flow identifier in the at least part of uplink messages sent to the base station. That is to say, the UE remains the SDAP header, but un-carries the QoS in the SDAP header. The UE may also un-carry the SDAP header in the at least part of uplink messages sent to the base station. For instance, the UE sends the at least part of uplink messages in the SDAP transparent mode.
[0273]
The communication method in this embodiment may also be combined with that in the twenty-eighth or twenty-ninth embodiment.
[0274]
Fig. 40 is a structural schematic view illustrating an embodiment of a communication apparatus according to the present disclosure. As shown in Fig. 40, the communication apparatus 10 may include a processor 110 and a communication circuit 120. The processor 110 may be connected to the communication circuit 120.
[0275]
The communication circuit 120 may be configured for transmitting and receiving data, which is an interface for communication between the communication apparatus 10 and other communication devices.
[0276]
The processor 110 controls operations of the communication apparatus. The processor 110 may also be called as CPU (Central Processing Unit) . The processor 110 may be an integrated circuit chip with an ability to process signals. The processor 110 may also be a common processor, a Digital Signal Processor (DSP) , an Application Specific Integrated Circuits (ASIC) , a Field Programmable Gate Array (FPGA) or another programmable logical device, a discrete gate or transistor logic component, a discrete hardware component. The common processor may be a micro-processor, or also be any one of conventional processors, etc.
[0277]
In one embodiment, the processor 110 may be configured for performing programs to achieve any one of the communication methods in accordance with the first to nineteenth embodiment or a method provided with arbitrary and non-conflicting combination of the communication methods therein. And the communication apparatus 10 in the present embodiment may be a base station, and also be a separate component integrated in a base station, such as a base band board. In another embodiment, the processor 110 may also be configured for performing programs to achieve any one of the communication methods in accordance with the twentieth to thirty-first embodiment or a method provided with arbitrary and non-conflicting combination of the communication methods therein. And the communication apparatus 10 in the present embodiment may be a user equipment, and also be a separate component integrated in a user equipment, such as a base band chip.
[0278]
In other embodiments, the communication apparatus 10 may also include a memory (not shown in Fig. 40) and other components, which will not be restricted herein.
[0279]
Fig. 41 is a structural schematic view illustrating an embodiment of a device with a memory according to the present disclosure. As shown in Fig. 41, the device 50 is internally being stored with programs 501. The programs 501 may be performed to achieve any one of the communication methods in accordance with the first to nineteenth embodiment or a method provided with arbitrary and non-conflicting combination of the communication methods therein, or achieve any one of the communication methods in accordance with the twentieth to thirty-first embodiment or a method provided with arbitrary and non-conflicting combination of the communication methods therein.
[0280]
The device 50 may be a portable media such as a U disk or an optical disk, and may also be a base band board, a server or an independent component integrated in a base station, such as a base band chip.
[0281]
The above description depicts merely some exemplary embodiments of the disclosure, but does not mean to limit the scope of the disclosure. Any equivalent structure or flow transformations made to the disclosure, or any direct or indirect applications of the disclosure on other related fields, shall all be covered within the protection of the disclosure.

Claims

[Claim 1]
A communication method, comprising: determining whether a QoS (Quality of Service) flow identifier is needed to be omitted in at least part of downlink messages sent to a user equipment; and omitting the QoS flow identifier in the at least part of downlink messages sent to the user equipment when the QoS flow identifier is needed to be omitted, otherwise carrying the QoS flow identifier in the at least part of downlink messages sent to the user equipment.
[Claim 2]
The method according to claim 1, wherein the determining whether the QoS flow identifier is needed to be omitted in the at least part of downlink messages sent to the user equipment comprises: determining whether a service data adaptation protocol transparent mode is needed to be adopted to send the at least part of downlink messages; and deciding that the QoS flow identifier is needed to be omitted in the at least part of downlink messages sent to the user equipment when the service data adaptation protocol transparent mode is needed, otherwise the QoS flow identifier is not needed to be omitted in the at least part of downlink messages sent to the user equipment; and the omitting the QoS flow identifier in the at least part of downlink messages sent to the user equipment comprises: sending a notification message in a predetermined form to the user equipment; and omitting a service data adaptation protocol header in the at least part of downlink messages sent to the user equipment, wherein the QoS flow identifier is carried in the service data adaptation protocol header.
[Claim 3]
The method according to claim 2, wherein the determining whether the service data adaptation protocol transparent mode is needed to be used to send the at least part of downlink messages comprises: determining whether an uplink reflective QoS mapping function is used by the user equipment to which is pointed by the downlink messages; and deciding that the service data adaptation protocol transparent mode is needed to be adopted when the uplink reflective QoS mapping function is not used.
[Claim 4]
The method according to claim 2, wherein the determining whether the service data adaptation protocol transparent mode is needed to be adopted to send the at least part of downlink messages comprises: determining whether there is only one QoS flow in an uplink data radio bearer established with the user equipment; and deciding that the service data adaptation protocol transparent mode is needed to be adopted when there is only the one QoS flow.
[Claim 5]
The method according to any one of claims 2-4, wherein the sending the notification message in the predetermined form to the user equipment comprises: sending a radio resource control message loaded with the notification message to the user equipment, such that the user equipment subsequently sends at least part of uplink messages in the service data adaptation protocol transparent mode.
[Claim 6]
The method according to claim 5, wherein the radio resource control message at least comprises a transparent mode identifier, or the radio resource control message at least comprises a transparent mode identifier and at least one data radio bearer identifier.
[Claim 7]
The method according to claim 5, after the sending the radio resource control message loaded with the notification message to the user equipment, further comprising: determining whether a radio resource control response message sent by the user equipment is received; and further omitting the service data adaptation protocol header in the at least part of downlink messages sent to the user equipment when the radio resource control response message is received.
[Claim 8]
The method according to claim 2, wherein the determining whether the service data adaptation protocol transparent mode is needed to be adopted to send the at least part of downlink messages comprises: receiving a radio resource control message sent by the user equipment, wherein the radio resource control message at least comprises a transparent mode identifier, or the radio resource control message at least comprises a transparent mode identifier and at least one data radio bearer identifier; determining whether the transparent mode identifier in the received radio resource control message is a preset value; and deciding that the service data adaptation protocol transparent mode is needed to be adopted when the transparent mode identifier is the preset value.
[Claim 9]
The method according to claim 8, before the omitting the service data adaptation protocol header in the at least part of downlink messages sent to the user equipment, comprising: sending a radio resource control response message to the user equipment, thereby informing the user equipment that the service data adaptation protocol transparent mode is subsequently adopted to send the at least part of downlink messages to the user equipment.
[Claim 10]
The method according to any one of claims 2-4, wherein the sending the notification message in the predetermined form to the user equipment comprises: sending a packet data convergence protocol message loaded with the notification message, thereby informing the user equipment to subsequently send at least part uplink messages in the service data adaptation protocol transparent mode, wherein the packet data convergence protocol message comprises at least one transparent mode identifier.
[Claim 11]
The method according to any one of claims 2-4, wherein the sending the notification message in the predetermined form to the user equipment comprises: sending a service data adaptation protocol control message loaded with the notification message, thereby informing the user equipment to subsequently send at least part uplink messages in the service data adaptation protocol transparent mode, wherein the service data adaptation protocol control message comprises at least one transparent mode identifier.
[Claim 12]
The method according to claim 11, wherein the service data adaptation protocol control message further comprises the QoS flow identifier.
[Claim 13]
The method according to claim 1, wherein the determining whether the QoS flow identifier is needed to be omitted in the at least part of downlink messages sent to the user equipment comprises: sending downlink messages carrying a service data adaptation protocol header with the QoS flow identifier to the user equipment, thereby informing the user equipment to map a QoS flow with the QoS flow identifier to a corresponding data radio bearer; determining whether a quality of the sent downlink messages or duration during which the downlink messages are continuously sent meets a preset condition; and deciding that the QoS flow identifier is needed to be omitted in the at least part of downlink messages sent to the user equipment when the preset condition is met.
[Claim 14]
The method according to claim 13, wherein determining whether the quality of the sent downlink messages or duration during which the downlink messages are continuously sent meets the preset condition comprises: determining whether the quantity of the sent downlink messages is greater than a first predetermined value; and deciding that the preset condition is met when the quantity of the sent downlink messages is greater than the first predetermined value.
[Claim 15]
The method according to claim 14, wherein the determining whether the quantity of the sent downlink messages is greater than the first predetermined value comprises: determining whether a quantity of the continuously-sent downlink messages is greater than the first preset value.
[Claim 16]
The method according to claim 13, wherein determining whether the quality of the sent downlink messages or duration during which the downlink messages are continuously sent meets the preset condition comprises: determining a duration during which the downlink messages are continuously sent to the user equipment is greater than a second predetermined value; and deciding that the preset condition is met when the duration is greater than the second predetermined value.
[Claim 17]
The method according to claim 1, wherein the determining whether the QoS flow identifier is needed to be omitted in the at least part of downlink messages sent to the user equipment comprises: determining whether a radio resource control message for updating a mapping between QoS flows and data radio bearers has been sent to the user equipment, wherein the radio resource control message at least comprises the QoS flow identifier; and further deciding that the QoS flow identifier is needed to be omitted in the at least part of downlink messages sent to the user equipment when the radio resource control message has been sent.
[Claim 18]
The method according to any one of claims 13-17, wherein the determining whether the QoS flow identifier is needed to be omitted in the at least part of downlink messages sent to the user equipment comprises: determining whether a mapping acknowledge message sent by the user equipment is received; deciding that the QoS flow identifier is needed to be omitted in the at least part of downlink messages sent to the user equipment when the mapping acknowledge message is received.
[Claim 19]
The method according to any one of claims 13-17, wherein the omitting the QoS flow identifier in the at least part of downlink messages sent to the user equipment comprises: un-carrying the QoS flow identifier in the service data adaptation protocol header of the at least part of downlink messages; or un-carrying the service data adaptation protocol header in the at least part of downlink messages.
[Claim 20]
The method according to claim 18, wherein the mapping acknowledge message comprises at least one of the following: a service data adaptation protocol control message, a service data adaptation protocol data message, a radio resource control message and a packet data convergence protocol control message.
[Claim 21]
The method according to claim 20, wherein the service data adaptation protocol control message comprises the QoS flow identifier and an acknowledge bit; and the determining whether the mapping acknowledge message sent by the user equipment is received comprises: determining whether a value of the acknowledge bit is a third predetermined value; and deciding that the mapping acknowledge message is received when the value of the acknowledge bit is the third predetermined value.
[Claim 22]
The method according to claim 20, wherein the service data adaptation protocol data message has a data length which is zero bit; and the determining whether the mapping acknowledge message sent by the user equipment is received comprises: determining whether a payload size of a protocol data unit of a uplink data message received from the user equipment is zero bit; and deciding that the mapping acknowledge message is received when the payload size of the protocol data unit is zero bit.
[Claim 23]
The method according to claim 20, wherein the service data adaptation protocol control message at least comprises the QoS flow identifier and an acknowledge bit; and the determining whether the mapping acknowledge message sent by the user equipment is received comprises: determining whether a value of the acknowledge bit is a fourth predetermined value; and deciding that the mapping acknowledge message is received when the value of the acknowledge bit is the fourth predetermined value.
[Claim 24]
The method according to claim 20, wherein a header of the service data adaptation protocol control message at least comprises the QoS flow identifier; and the determining whether the mapping acknowledge message sent by the user equipment is received comprises: determining whether the header of the service data adaptation protocol data message from the user equipment comprises the QoS flow identifier and whether a data radio bearer corresponding to the service data adaptation protocol data message is a preset data radio bearer; and deciding that the mapping acknowledge message is received when the header comprises the QoS flow identifier and the data radio bearer is the preset data radio bearer.
[Claim 25]
The method according to claim 24, wherein the preset data radio bearer is corresponding to a downlink message which is transferred via a QoS flow with the QoS flow identifier.
[Claim 26]
A communication method, comprising: determining whether a QoS flow identifier is needed to be omitted in at least part of uplink messages sent to a base station; and omitting the QoS flow identifier in the at least part of uplink messages sent to the base station when the QoS flow identifier is needed to be omitted, otherwise carrying the QoS flow identifier in the at least part of uplink messages sent to the base station.
[Claim 27]
The method according to claim 26, wherein the determining whether the QoS flow identifier is needed to be omitted in the at least part of uplink messages sent to the base station comprises: determining whether a service data adaptation protocol transparent mode is needed to be adopted to send the at least part of uplink messages; and deciding that the QoS flow identifier is needed to be omitted in the at least part of uplink messages sent to the base station when the service data adaptation protocol transparent mode is needed, otherwise the QoS flow identifier is not needed to be omitted in the at least part of uplink messages sent to the base station; and the omitting the QoS flow identifier in the at least part of uplink messages sent to the base station comprises: omitting a service data adaptation protocol header in the at least part of uplink messages sent to the base station, wherein the QoS flow identifier is carried in the service data adaptation protocol header.
[Claim 28]
The method according to claim 27, wherein the determining whether the service data adaptation protocol transparent mode is needed to be used to send the at least part of uplink messages comprises: determining whether an uplink reflective QoS mapping function is used; and deciding that the service data adaptation protocol transparent mode is needed to be adopted when the uplink reflective QoS mapping function is not used.
[Claim 29]
The method according to claim 27, wherein the determining whether the service data adaptation protocol transparent mode is needed to be used to send the at least part of uplink messages comprises: determining whether there is only one QoS flow in an uplink data radio bearer established with the base station; and deciding that that the service data adaptation protocol transparent mode is needed to be used when there is only the one QoS flow.
[Claim 30]
The method according to any one of claims 27-29, wherein the determining whether the service data adaptation protocol transparent mode is needed to be adopted to send the at least part of uplink messages further comprises: determining whether a radio resource control message loaded with a notification message in a predetermined form is received from the base station; and deciding that the service data adaptation protocol transparent mode is needed to be adopted when the radio resource control message is received.
[Claim 31]
The method according to claim 30, wherein the radio resource control message at least comprises a transparent mode identifier, or the radio resource control message at least comprises a transparent mode identifier and at least one data radio bearer identifier.
[Claim 32]
The method according to claim 30, after receiving the radio resource control message loaded with the notification message in the predetermined form, further comprising: sending a radio resource control response message to the base station, such that the base station sends at least part of downlink messages in the service data adaptation protocol transparent mode.
[Claim 33]
The method according to claim 27, wherein the determining whether the service data adaptation protocol transparent mode is needed to be adopted to send the at least part of uplink messages comprises: determining whether a radio resource control message loaded with a notification message in a predetermined form has been sent to the base station, wherein the radio resource control message at least comprises a transparent mode identifier and at least one data radio bearer identifier; and deciding that the service data adaptation protocol transparent mode is needed to be adopted to send the at least part of uplink messages when the radio resource control message has been sent.
[Claim 34]
The method according to claim 33, before the deciding that the service data adaptation protocol transparent mode is needed to be adopted to send the at least part of uplink messages, comprising: determining whether a radio resource control response message is received from the base station; and further deciding that the service data adaptation protocol transparent mode is needed to be adopted to send the at least part of uplink messages when the radio resource control response message is received.
[Claim 35]
The method according to any one of claims 27-29, wherein the determining whether the service data adaptation protocol transparent mode is needed to be adopted to send the at least part of uplink messages further comprises: receiving a packet data convergence protocol message from the base station, wherein the packet data convergence protocol message comprises at least one transparent mode identifier bit; determining whether the one transparent mode identifier bit is a preset value; and deciding that the service data adaptation protocol transparent mode is needed to be adopted to send the at least part of uplink messages when the transparent mode identifier bit is the preset value.
[Claim 36]
The method according to any one of claims 27-29, wherein the determining whether the service data adaptation protocol transparent mode is needed to be adopted to send the at least part of uplink messages further comprises: receiving a service data adaptation protocol control message from the base staion, wherein the service data adaptation protocol control message comprises at least one transparent mode identifier bit; determining whether the transparent mode identifier bit is a preset value; and deciding that the service data adaptation protocol transparent mode is needed to be adopted to send the at least part of uplink messages when the transparent mode identifier is the preset value.
[Claim 37]
The method according to claim 36, wherein the service data adaptation protocol control message further comprises the QoS flow identifier.
[Claim 38]
The method according to claim 26, wherein the determining whether the QoS flow identifier is needed to be omitted in the at least part of uplink messages sent to the base station comprises: determining whether downlink messages carrying a service data adaptation protocol header with the QoS flow identifier from the base station are received, such that a QoS flow with the QoS flow identifier is mapped to a corresponding data radio bearer; and deciding that the QoS flow identifier is needed to be omitted in the at least part of uplink messages sent to the base station when the downlink messages are received.
[Claim 39]
The method according to claim 26, wherein the determining whether the QoS flow identifier is needed to be omitted in the at least part of uplink messages sent to the base station comprises: determining whether a radio resource control message for updating a mapping between QoS flows and data radio bearers from the base station is received, wherein the radio resource control message at least comprises the QoS flow identifier; and deciding that the QoS flow identifier is needed to be omitted in the at least part of uplink messages sent to the base station when the radio resource control message is received.
[Claim 40]
The method according to claims 38 or 39, after the downlink messages carrying a service data adaptation protocol header with the QoS flow identifier from the base station are received or the radio resource control message for updating a mapping between QoS flows and data radio bearers from the base station is received, comprising: sending a mapping acknowledge message to the base station, such that the base station omits the QoS flow identifier in the subsequently-sent at least part of downlink messages.
[Claim 41]
The method according to claims 38 or 39, wherein the omitting the QoS flow identifier in the at least part of uplink messages sent to the base station comprises: un-carrying the QoS flow identifier in the service data adaptation protocol header of the at least part of uplink messages sent to the base station; or un-carrying the service data adaptation protocol header in the at least part of uplink messages sent to the base station.
[Claim 42]
The method according to claim 40, wherein the mapping acknowledge message sent to the base station comprises at least one of the following: a service data adaptation protocol control message, a service data adaptation protocol data message, a radio resource control message and a packet data convergence protocol control message.
[Claim 43]
The method according to claim 42, wherein the service data adaptation protocol control message comprises the QoS flow identifier and an acknowledge bit.
[Claim 44]
The method according to claim 42, wherein the service data adaptation protocol data message has a data length which is zero bit.
[Claim 45]
The method according to claim 42, wherein the service data adaptation protocol control message at least comprises the QoS flow identifier and an acknowledge bit.
[Claim 46]
The method according to claim 42, wherein a header of the service data adaptation protocol control message at least comprises the QoS flow identifier, and the service data adaptation protocol control message is transferred in a preset data radio bearer.
[Claim 47]
The method according to claim 46, wherein the preset data radio bearer is corresponding to a downlink message which is transferred via a QoS flow with the QoS flow identifier.
[Claim 48]
An communication apparatus, comprising a processor and a communication circuit connected to the processor, wherein the processor is configured for executing programs to perform the method in any one of claims 1-25 and 26-47.
[Claim 49]
A memory for storing programs, wherein the programs are executed to perform the method in any one of claims 1-25 and 26-47.

Drawings

[ Fig. 0001]  
[ Fig. 0002]  
[ Fig. 0003]  
[ Fig. 0004]  
[ Fig. 0005]  
[ Fig. 0006]  
[ Fig. 0007]  
[ Fig. 0008]  
[ Fig. 0009]  
[ Fig. 0010]  
[ Fig. 0011]  
[ Fig. 0012]  
[ Fig. 0013]  
[ Fig. 0014]  
[ Fig. 0015]  
[ Fig. 0016]  
[ Fig. 0017]  
[ Fig. 0018]  
[ Fig. 0019]  
[ Fig. 0020]  
[ Fig. 0021]  
[ Fig. 0022]  
[ Fig. 0023]  
[ Fig. 0024]  
[ Fig. 0025]  
[ Fig. 0026]  
[ Fig. 0027]  
[ Fig. 0028]  
[ Fig. 0029]  
[ Fig. 0030]  
[ Fig. 0031]  
[ Fig. 0032]  
[ Fig. 0033]  
[ Fig. 0034]  
[ Fig. 0035]  
[ Fig. 0036]  
[ Fig. 0037]  
[ Fig. 0038]  
[ Fig. 0039]  
[ Fig. 0040]  
[ Fig. 0041]