CN116980973A - Method, base station, terminal, system and medium for maintaining data compression continuity - Google Patents
Method, base station, terminal, system and medium for maintaining data compression continuity Download PDFInfo
- Publication number
- CN116980973A CN116980973A CN202210435223.5A CN202210435223A CN116980973A CN 116980973 A CN116980973 A CN 116980973A CN 202210435223 A CN202210435223 A CN 202210435223A CN 116980973 A CN116980973 A CN 116980973A
- Authority
- CN
- China
- Prior art keywords
- base station
- bearer
- udc
- information
- data compression
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000013144 data compression Methods 0.000 title claims abstract description 216
- 238000000034 method Methods 0.000 title claims abstract description 138
- 238000007906 compression Methods 0.000 claims abstract description 39
- 230000006835 compression Effects 0.000 claims abstract description 39
- 238000011084 recovery Methods 0.000 claims abstract description 28
- 238000004891 communication Methods 0.000 claims abstract description 12
- 230000004048 modification Effects 0.000 claims description 120
- 238000012986 modification Methods 0.000 claims description 120
- 230000004044 response Effects 0.000 claims description 70
- 239000000725 suspension Substances 0.000 claims description 52
- 230000005540 biological transmission Effects 0.000 claims description 44
- 230000006837 decompression Effects 0.000 claims description 42
- 230000006870 function Effects 0.000 claims description 26
- 238000012546 transfer Methods 0.000 claims description 22
- XHSQDZXAVJRBMX-UHFFFAOYSA-N 2-(5,6-dichlorobenzimidazol-1-yl)-5-(hydroxymethyl)oxolane-3,4-diol Chemical compound OC1C(O)C(CO)OC1N1C2=CC(Cl)=C(Cl)C=C2N=C1 XHSQDZXAVJRBMX-UHFFFAOYSA-N 0.000 claims description 12
- 230000008569 process Effects 0.000 claims description 9
- 238000012790 confirmation Methods 0.000 claims description 6
- 238000000926 separation method Methods 0.000 claims description 5
- 230000001960 triggered effect Effects 0.000 claims description 5
- 238000004590 computer program Methods 0.000 claims description 3
- 230000005281 excited state Effects 0.000 claims description 3
- 238000013507 mapping Methods 0.000 claims description 3
- 238000012423 maintenance Methods 0.000 claims description 2
- 238000010586 diagram Methods 0.000 description 17
- 101001100327 Homo sapiens RNA-binding protein 45 Proteins 0.000 description 13
- 102100038823 RNA-binding protein 45 Human genes 0.000 description 13
- 101150090033 DRB2 gene Proteins 0.000 description 11
- 101100117568 Oryza sativa subsp. japonica DRB5 gene Proteins 0.000 description 11
- 230000011664 signaling Effects 0.000 description 7
- 239000013256 coordination polymer Substances 0.000 description 6
- 229920002477 rna polymer Polymers 0.000 description 6
- 101150034979 DRB3 gene Proteins 0.000 description 5
- 101100278514 Oryza sativa subsp. japonica DRB2 gene Proteins 0.000 description 5
- 230000006978 adaptation Effects 0.000 description 2
- 230000002776 aggregation Effects 0.000 description 2
- 238000004220 aggregation Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 239000013307 optical fiber Substances 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 102100022734 Acyl carrier protein, mitochondrial Human genes 0.000 description 1
- 101100087393 Caenorhabditis elegans ran-2 gene Proteins 0.000 description 1
- 101000678845 Homo sapiens Acyl carrier protein, mitochondrial Proteins 0.000 description 1
- 230000009471 action Effects 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 230000002708 enhancing effect Effects 0.000 description 1
- GVVPGTZRZFNKDS-JXMROGBWSA-N geranyl diphosphate Chemical compound CC(C)=CCC\C(C)=C\CO[P@](O)(=O)OP(O)(O)=O GVVPGTZRZFNKDS-JXMROGBWSA-N 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 230000003252 repetitive effect Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 230000011218 segmentation Effects 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
- 238000011144 upstream manufacturing Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/25—Maintenance of established connections
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/27—Transitions between radio resource control [RRC] states
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The disclosure provides a method, a base station, a terminal, a system and a medium for maintaining data compression continuity, and relates to the technical field of communication. The method comprises the following steps: the base station control plane entity indicates the base station user plane entity to configure or modify the carried UDC configuration information and informs the terminal of the UDC application area; when the terminal is configured to enter an RRC inactive state and maintain UDC continuity, reserving suspended UDC configuration information, carrying out uplink compression on small data packets sent in a UDC applicable area, and sending the compressed small data packets and RRC connection recovery request information to a base station of the terminal for requesting recovery; after receiving the request message for restoring the context of the base station requesting restoration and determining that the uplink data compression is applicable to the area, the base station control plane entity indicates the restoration mode of the uplink data compression of the base station user plane entity so as to decompress the small data packet based on the reserved UDC configuration information. The method and the device can maintain the continuity of uplink data compression when the terminal RRC inactive state transmits small data packets.
Description
Technical Field
The present disclosure relates to the field of communications technologies, and in particular, to a method, a base station, a terminal, a system, and a medium for maintaining data compression continuity.
Background
On one hand, more and more mobile terminal users become content producers, which aggravates the requirement for uplink resources; on the other hand, the increase of the downlink traffic also brings about a corresponding increase of the uplink traffic. There has been a relatively wide deployment of downlink carrier aggregation, and in correspondence with this, deployment of uplink carrier aggregation is limited by terminal power consumption and cost, and large-scale deployment is not realized, which aggravates asymmetry of uplink and downlink resources.
For the uplink and downlink proportion of a typical TDD network, when executing a service with a large uplink data volume, the uplink is easy to become a bottleneck of the network. For TDD networks, uplink enhancement is of more concern.
Meanwhile, uplink coverage limitation is also an important problem, and on one hand, as uplink service increases, uplink interference level is continuously deteriorated; on the other hand, the SIP signaling size in the voice service establishment phase may reach 2KB, which may cause RLC segmentation in an environment with poor channel conditions, and further cause an increase in voice service establishment delay, and even cause a voice service establishment failure.
To solve the above problems, a UDC (Uplink Data Compression ) scheme is proposed as an important uplink enhancement technology in 3GPP Rel-15 and standardization has been completed in 3 GPP. The UDC scheme of 3GPP is based on RFC1951 DEFLATE data compression algorithm. According to the conclusion of the 3gpp ran2#116bis conference at month 2022, the UDC scheme is supported in the 5G SA state, and each terminal supports only two bearers configured in UDC mode. As shown in fig. 1, the UDC header and the data portion are located after the SDAP header. The transmitting side PDCP entity supports a UDC compression function, which is located after numbering the data packets and before integrity protection or ciphering. The receiving side PDCP entity supports a UDC decompression function, which follows a reordering and repetition detection function. When the RRC layer instructs the PDCP entity to reestablish, the UE needs to reset the UDC compression buffer to a value of all 0 and pre-fill the configured dictionary into the compression buffer.
In the 5G network, the UE can reduce the power consumption of the terminal and the signaling interaction process between the terminal and the core network by entering an Inactive state (RRC Inactive state), thereby realizing the improvement of the access delay of the terminal. However, as shown in fig. 2, in the scheme before Rel-17, if there is a small packet to transmit, the terminal side still needs to complete the control plane establishment through the RRC recovery procedure, and then send and receive the packet. It is clear that this approach is not obvious for improving the access delay on the one hand, and on the other hand, it will cause the terminal to return to the Inactive state after completing one or more data packet transmissions, and for periodic small data packet transmissions it will still increase the excessive signaling interaction procedure between the terminal and the network. In view of the above problems, 3GPP has conducted research on small packet transmission (Small Data Transmission, SDT) in Rel-17, which aims to reduce the access delay of a terminal for transmitting small packets at the time of inactive, and it has been determined in the current standards that RACH-based packet transmission and configured grant-based packet transmission are supported.
In the Rel-16 standard, the transition procedure from the RRC inactive state to the connected state with respect to the terminal in a control plane and user plane separated architecture is perfected. Fig. 3 shows a signaling procedure for a terminal to change from a connected state to an RRC inactive state, and it can be seen from fig. 3 that during the triggered state, the PDCP related entity of the base station user plane entity CU-UP needs to perform a suspension operation, delete the related data buffer, and delete the F1-U related connection to the base station detach entity DU, and no data processing is performed for the user to receive or send to the DU, for which the related user context needs to be deleted. The current Rel-17 standard does not support the function of compressing uplink data packets in the process of transmitting small data packets.
It should be noted that the information disclosed in the above background section is only for enhancing understanding of the background of the present disclosure and thus may include information that does not constitute prior art known to those of ordinary skill in the art.
Disclosure of Invention
The present disclosure provides a method, a base station, a terminal, a system and a medium for maintaining data compression continuity, which at least overcome to some extent the technical problem that the uplink compression continuity is maintained when the terminal is not supported to transmit small data packets in an RRC inactive state in the related art.
According to one aspect of the present disclosure, there is provided a method of maintaining data compression continuity, the method comprising: the first base station control plane entity indicates the first base station user plane entity to configure or modify Uplink Data Compression (UDC) configuration information of the bearer through a bearer context establishment request or a bearer context modification request message, and indicates the first base station user plane entity to suspend the UDC bearer when the terminal enters an RRC inactive state, and informs one or more pre-configured UDC application areas of the bearer in the terminal through an air interface message; the method comprises the steps that a first base station control plane entity configures a terminal to enter an RRC inactive state, UDC continuity is kept when the terminal enters the RRC inactive state, so that when the terminal is in the RRC inactive state, the terminal reserves UDC configuration information of a suspended UDC bearer, and when a small data packet SDT (data packet) is born in a preconfigured UDC applicable area and needs to be sent, uplink compression operation is carried out on the small data packet to be sent by adopting the reserved UDC configuration information, and the compressed small data packet and an RRC connection recovery request message are sent to a second base station together, wherein the second base station is a base station of the terminal requesting RRC connection recovery; after receiving the context restoration request message of the second base station, the first base station control plane entity determines that the SDT is born in a preconfigured uplink data compression applicable area, and indicates a restoration mode of uplink data compression of the first base station user plane entity, so that the first base station user plane entity performs decompression operation on the small data packet sent by the terminal based on the reserved UDC configuration information.
In some embodiments, the method further comprises: the first base station control plane entity sends a first data bearer DRB list to the first base station user plane entity through a first bearer context establishment request message or a first bearer context modification request message so as to request establishment or modification of UDC configuration information contained in PDCP configuration; when the first base station is an LTE air interface, DRB To Setup List of an E-UTRAN mode is adopted by the first DRB establishment list; when the first base station is an NR air interface, the first DRB list is DRB To Setup List contained in PDU Session Resource To Setup Modification List in NR mode.
In some embodiments, the sum of the number of uplink data compression bearers to be configured and the number of currently activated uplink data compression bearers by the ue does not exceed a preset UDC bearer upper limit, and the number of currently activated uplink data compression bearers is the number of activated and unreleased uplink data compression bearers.
In some embodiments, the first bearer context establishment request message includes a first bearer list that requests establishment, and the first bearer list includes: one or more DRBs carry configuration information; the first bearer context modification request message includes a first bearer list requesting establishment and/or a second bearer list requesting modification, the first bearer list includes one or more DRB bearer configuration information, and the second bearer list includes: one or more DRBs carry configuration information, bearers of the UDC to be turned off, bearers of the UDC to be released.
In some embodiments, each DRB bearer configuration information includes at least the following information: 1) The DRB mark is a value of an integer type; 2) SDT bearing type indication information, enumeration type, and SDT bearing when the value is yes, supporting small data packet compression of the terminal in the RRC inactive state; 3) PDCP configuration information including at least the following information: the PDCP reestablishment indication information enumerates types, and indicates that the PDCP entity of the DRB needs to be reestablished when the value is yes, and the PDCP reestablishment information is carried only when the UDC configuration of the DRB needs to be deleted; 4) UDC configuration information, the UDC configuration information including at least the following information: (1) UDC decompresses the buffer size, enumerates the type, and takes the value including at least one of: 2048 bytes, 4096 bytes, and 8912 bytes; (2) dictionary information, enumeration type, and value including at least one of the following: a SIP-SID dictionary, a custom dictionary; (3) UDC continuity indication information: and (3) enumerating the types, wherein when the value is yes, the PDCP entity can continue or restart the uplink data compression function in the PDCP reestablishment process.
In some embodiments, the method further comprises: if the first base station user plane entity finds that the UDC configuration is contained in the PDCP configuration carried by the first bearer context modification request message after receiving the first bearer context establishment request message from the first base station control plane entity and the first base station user plane supports the UDC configuration, configuring an uplink data compression function of a corresponding DRB bearer by adopting related parameters, and returning a first bearer context establishment response message to the first base station control plane entity; if the first base station user plane entity finds that the UDC configuration is contained in the PDCP configuration carried by the first bearer context modification request message after receiving the first bearer context modification request message from the first base station control plane entity, and the first base station user plane supports the UDC configuration, configuring an uplink data compression function of a corresponding DRB bearer by adopting related parameters, and returning a first bearer context modification response message to the first base station control plane entity.
In some embodiments, the method further comprises: the first base station user plane entity performs bearer configuration by: checking whether the bearer configuration information of each DRB identifier carries UDC configuration information or not in a bearer list requested to be released, and if so, releasing the bearer corresponding to the DRB identifier; checking whether PDCP configuration information in the bearer configuration information of each bearer carries UDC configuration information or not in a bearer list requested to be modified, and if the first base station user plane entity supports the UDC capability, configuring an uplink data compression function for the bearer; if the number of configured uplink data compression bearers exceeds the preset UDC bearer upper limit value, determining that the bearer modification fails, and generating a failure cause value, wherein the failure cause value is used for indicating that the number of UDC bearers exceeds the preset UDC bearer upper limit value or that PDCP bearer configuration cannot be supported; if the configuration information of any one bearer with configured UDC function carries PDCP reestablishment instruction information, all data in the bearer, decompression caches and dictionary information are emptied, dictionary information and decompression caches are reconfigured according to the carried UDC configuration information, wherein if no dictionary is configured in the dictionary information, the size of the UDC decompression caches is set to 0; if the dictionary information is configured with a dictionary, configuring the UDC decompression buffer size according to the dictionary information; checking whether PDCP configuration information in the bearer configuration information of each bearer carries UDC configuration information or not in a bearer list established by the request, and if the first base station user plane entity supports the UDC capability, configuring an uplink data compression function for the bearer; if the number of configured uplink data compression bearers exceeds the preset UDC bearer upper limit value, determining that the bearer establishment fails, and generating a failure reason value, wherein the failure reason value is used for indicating that the number of UDC bearers exceeds the preset UDC bearer upper limit value or that PDCP bearer configuration cannot be supported.
In some embodiments, the first bearer context setup response message or the first bearer context modification response message includes: a bearer configuration success information list or a bearer configuration failure information list; the successful information list of bearer configuration is used for indicating one or more data bearers successfully configured in the bearer list requested to be established or modified; the bearer configuration failure information list is used to indicate one or more data bearers that cannot be configured in the bearer list that is requested to be established or modified.
In some embodiments, the bearer configuration success information list includes: an identification of one or more data bearers successfully configured; the bearer configuration failure information list includes: an identification of one or more data bearers that cannot be configured and a failure reason for each data bearer, the failure reason including: the number of UDC bearers exceeds a preset UDC bearer upper limit or PDCP bearer configuration cannot be supported.
In some embodiments, the method further comprises: after receiving a first bearer context establishment response message or a first bearer context modification response message from the first base station user plane entity, the first base station control plane entity determines a configuration result of the bearer which is requested to be established or modified in the first base station user plane entity; the first base station control plane entity generates a first RRC reconfiguration message sent to the terminal according to the configuration result, and sends the established or modified bearer configuration information to the terminal through the first RRC reconfiguration message, wherein the bearer configuration information carried in the first RRC reconfiguration message comprises: UDC configuration information, wherein the bearer in the configuration result and the bearer in the first RRC reconfiguration message have a mapping relation; for a bearer which needs to be added and configured as a UDC, placing a DRB identifier of the bearer in a DRB establishment list in an RRC message; for the bearer which needs to be modified into the existing bearer and is configured into the UDC, the bearer DRB identifier is placed in a DRB release list and a DRB establishment list in an RRC message, and the sum of the number of the bearer which is configured into the UDC by the terminal after RRC reconfiguration and the number of the uplink data compression bearers which are currently activated and not released is ensured to be not more than a preset UDC bearer upper limit value.
In some embodiments, the first RRC reconfiguration message includes at least the following information: 1) A DRB release list comprising: one or more DRB identifiers for deleting the UDC configuration information; 2) The DRB builds and modifies a list comprising: one or more DRB configuration information, each DRB configuration information comprising at least: (1) a DRB mark; (2) UDC decompresses the buffer size, enumerates the type, and takes the value including at least one of: 2048 bytes, 4096 bytes, and 8912 bytes; (3) dictionary information: the enumeration type, the value includes at least one of the following: SIP-SID dictionary, custom dictionary.
In some embodiments, after the first base station control plane entity sends the successfully established or modified bearer configuration information to the terminal through the first RRC reconfiguration message, the method further includes: the terminal performs configuration and reconfiguration of the UDC by: for each DRB identifier in the DRB release list, deleting all configuration information of the corresponding DRB, and recording the number of UDC bearers required to be released as T1; for each bearer needing to be configured in the UDC in the DRB establishment or modification list, configuring the size of a decompression cache and dictionary information of the UDC, setting all initial information in the cache to 0, and recording the number of the UDC bearers needing to be established as T2; recording that the number of the established UDC bearers is T0 before the terminal receives the first RRC reconfiguration message, and when the value of T0-T1+T2 does not exceed the preset UDC bearer upper limit value or one established DRB mark is not added or modified directly under the condition of not being released, determining that the UDC configuration of the bearers is successful, and generating a first RRC reconfiguration confirmation message; when the value of T0-T1+T2 exceeds the preset UDC bearing upper limit value or an established DRB mark is generated, the UDC configuration of the bearing is determined to fail, and a first RRC reconfiguration failure message is generated.
In some embodiments, the method further comprises: the first base station control plane entity determines that a small data packet transmission bearing which needs to be suspended when the terminal enters an inactive state, and indicates the first base station user plane entity to trigger a bearing suspension process through a second bearing context modification request message, wherein the second bearing context modification request message at least comprises the following information: bearing suspension indication information: the enumeration type at least comprises the following values: bearer suspension, bearer restoration, and small packet transmission restoration.
In some embodiments, the method further comprises: after receiving the second bearer context modification request message, the first base station user plane entity suspends all bearers according to the suspension indication carried in the bearer suspension indication message, and for the configured UDC bearers, continues to maintain the preconfigured decompression buffer and dictionary information during suspension, does not perform any operation of clearing or resetting to 0 for the UDC decompression buffer and dictionary, generates a second bearer context modification response message, and sends the second bearer context modification response message to the first base station control plane entity.
In some embodiments, the method further comprises: after receiving the second bearer context modification response message, the first base station control plane entity determines an uplink data compression application area of the terminal according to the preconfiguration information, and generates a second RRC reconfiguration message sent to the terminal, where the second RRC reconfiguration message is used for indicating that the terminal keeps the uplink compression capability of the small data packet transmission bearer when entering the RRC inactive state.
In some embodiments, the second RRC reconfiguration message includes: suspending configuration information; the suspension configuration information includes at least the following information: the SDT bearing list comprises one or more SDT bearing identifiers, and each SDT bearing identifier is a value of an integer type; the uplink data compression continuity indication information is of an enumeration type, and takes the value of a cell or a radio access network notification area RNA.
In some embodiments, the method further comprises: after receiving the second RRC reconfiguration message, the terminal configures related bearers according to the following procedures, and feeds back a second RRC reconfiguration confirmation message to the first base station: if the second RRC reconfiguration message contains the suspension configuration information, further judging whether the suspension configuration information contains the SDT bearer list or not; if the suspension configuration information contains the SDT bearer list, storing the corresponding DRB identification, and determining the bearer of the corresponding DRB identification as a support terminal to transmit small data packets in an RRC non-excited state; judging whether the suspension configuration information contains uplink data compression continuity indication information or not; if the suspension configuration information contains the uplink data compression continuity indication information, all bearers which are supported in an SDT state and configured with UDCs are configured, the uplink data compression configuration is kept when a small data packet is adopted for transmission, the configured decompression cache and dictionary information are kept continuously, and the configured uplink data compression applicable area is stored; if the suspension configuration information does not contain the uplink data compression continuity indication information, all bearers supporting the SDT state and configured with the UDC are not transmitted in an uplink data compression mode when the terminal is in an inactive state, and the configured decompression buffer memory and dictionary information are emptied.
In some embodiments, the method further comprises: if the suspension configuration information does not contain the SDT bearer list, determining that the bearer of the corresponding DRB identifier does not support the transmission of the small data packet when the terminal is in the RRC non-activated state.
In some embodiments, the method further comprises: when the SDT of the terminal bears an uplink data packet to be sent, caching the uplink data packet to be sent in an application layer, and indicating an access layer to check whether a cell currently resided in is in a preconfigured uplink data compression applicable area; if the access layer finds that the cell where the access layer resides is in a preconfigured uplink data compression applicable area, the access layer instructs the application layer to compress uplink data, the uplink data packet buffered by the application layer is sent to a PDCP layer of the terminal, the uplink data packet buffered by the application layer is sent to a compression buffer according to preconfigured dictionary information, after data compression is completed, the uplink data packet is sent to an MAC layer of the terminal, and when the data volume of the uplink data packet reaches a preset data volume threshold value, a subsequent sending operation is triggered; if the access layer finds that the cell where the cell resides is not in the preconfigured uplink data compression application area, the application layer informs the access layer of the uplink data packet to be sent, and the access layer does not perform uplink data compression operation when sending the uplink data packet.
In some embodiments, the second base station is different from the first base station, the method further comprising: after receiving the RRC connection restoration request message and the uplink data packet sent by the terminal, if no user context information of the terminal is found, the second base station caches the received uplink data packet in a MAC layer of the second base station, and sends a user context acquisition request message to a first base station control plane entity, where the user context acquisition request message includes a cell identifier where the terminal currently resides, a downlink channel address, and SDT indication information.
In some embodiments, the user context acquisition request message further includes: SDT side information, the SDT side information comprising: one or more transmissions.
In some embodiments, the method further comprises: the first base station control plane entity checks whether a cell where the terminal currently resides is in a preconfigured uplink data compression applicable area; if the first base station control plane entity finds that the cell where the terminal currently resides is located in a preconfigured uplink data compression applicable area, determining that the UDC transmission bearer is configured to continue to perform uplink data decompression operation by adopting the existing compression cache and dictionary information, and returning a part of user context transfer request message to the second base station; and if the first base station control plane entity finds that the cell where the terminal currently resides is not in the preconfigured uplink data compression applicable area, sending a user context acquisition response message to the second base station.
In some embodiments, the partial user context transfer request message includes: 1) A second base station allocates an identifier for the user on a base station interface; 2) The first base station locates the user allocated mark on the base station interface; 3) The SDT bearer setup list includes: one or more SDT bearer lists, each SDT bearer list comprising: (1) a DRB list; (2) uplink user plane address information on an interface between base stations; (3) RLC bearer configuration information of the DRB; (4) QOS information of the DRB; (5) RLC mode; (6) SN length of RLC; (7) slice configuration information.
In some embodiments, the user context acquisition response message includes: 1) A second base station allocates an identifier for the user on a base station interface; 2) The first base station locates the user allocated mark on the base station interface; 3) A DRB identification list comprising one or more DRB configuration information, each DRB configuration information comprising information such that: (1) the logic channel identification is a value of an integer type; (2) RLC layer configuration information; (3) MAC layer configuration information; (4) PDCP layer configuration information.
In some embodiments, the method further comprises: if the second base station receives the partial user context transfer request message, returning a partial user context transfer response message, wherein the partial user context transfer response message comprises an SDT data forwarding DRB identification list, and the SDT data forwarding DRB identification list comprises: one or more DRB configuration information, each DRB configuration information comprising information such as: (1) a DRB mark; (2) UDC indication information, enumeration type, when the value is yes, the DRB is configured for UDC; (3) a logic channel identifier, wherein the value is an integer type numerical value; (4) downlink user plane address information of interfaces between base stations.
In some embodiments, the method further comprises: after receiving the partial user context transfer request message, the first base station control plane entity sends a third bearer context modification request message to the first base station user plane entity, where the third bearer context modification request message is used to request to resume data reception, and the third bearer context modification request message includes the following information: 1) The carrying suspending indication information, the enumeration type and the value at least comprise: bearer suspension, bearer recovery and small data packet transmission recovery; 2) A downstream channel address comprising: IP address and port address; 3) UDC continuity indication information: and the Boolean type is used for indicating that all bearers configured as SDT bearers and UDC are configured to restore the uplink data compression continuity maintaining function when the value is yes.
In some embodiments, the method further comprises: after receiving the third bearer context modification request message, the first base station user plane entity restores the small data packet transmission bearer of the terminal according to the small data packet transmission restoration instruction information, and when the value of the UDC continuity instruction information is yes, determines whether the bearer restoration of the configured UDC adopts preconfigured cache information and dictionary information according to the second bearer configuration information; if not, the preconfigured cache information and dictionary information are cleared; the first base station user plane entity distributes the address information for receiving the uplink data for each bearing.
In some embodiments, the method further comprises: the first base station user plane entity sends a third bearer context modification response message to the first base station control plane entity to inform the first base station control plane entity that the bearer configuration has been completed.
In some embodiments, the third bearer context modification response message includes the following information: 1) The successfully configured bearer list comprises one or more identifiers of SDT bearers; 2) The uplink carried receiving address information comprises: IP address and port address.
In some embodiments, the method further comprises: after receiving the third bearer context modification response message, the first base station control plane entity sends the uplink bearer receiving address information to the second base station through the context acquisition response message, and when the first base station and the second base station are the same base station, the first base station control plane entity sends the uplink bearer receiving address information to the first base station separation entity.
In some embodiments, the method further comprises: and after receiving the third bearing context modification response message, the second base station sends the cached uplink data to the user plane entity of the first base station according to the received address information of the uplink bearing.
In some embodiments, the method further comprises: and the first base station user plane entity completes the decompression operation of the uplink data according to the preconfigured cache information and dictionary information and completes the updating operation of the cache information and the dictionary information.
According to another aspect of the present disclosure, there is also provided a base station including: a base station control plane entity and a base station user plane entity; the base station control plane entity is configured to instruct the first base station user plane entity to configure or modify uplink data compression UDC configuration information of the bearer through a bearer context establishment request or a bearer context modification request message, and instruct the first base station user plane entity to suspend the UDC bearer when the terminal enters an RRC inactive state, and notify one or more bearer preconfigured UDC applicable areas in the terminal through an air interface message; the base station user plane entity is used for configuring or modifying Uplink Data Compression (UDC) configuration information of a bearer, and acquiring the UDC bearer needing to be suspended when the terminal enters an RRC inactive state; when the terminal is in an RRC inactive state, the terminal reserves UDC configuration information of a suspended UDC bearer, and when the terminal has small data packets carried by a small data packet SDT in a preconfigured UDC applicable area and needs to be transmitted, the reserved UDC configuration information is adopted to carry out uplink compression operation on the small data packets to be transmitted, the compressed small data packets and an RRC connection recovery request message are transmitted to a second base station, and the second base station is a base station of the terminal requesting RRC connection recovery; the base station control plane entity is further configured to determine that the SDT is carried in a preconfigured uplink data compression applicable area after receiving the context restoration request message of the second base station, and instruct a restoration mode of uplink data compression of the user plane entity of the first base station; the first base station user plane entity is further configured to decompress a small data packet sent by the terminal based on the reserved UDC configuration information.
According to another aspect of the present disclosure, there is also provided a terminal including: an uplink data compression configuration information acquisition module and an uplink small data packet compression continuity maintenance module; the uplink data compression configuration information acquisition module is used for acquiring one or more bearing preconfigured UDC applicable areas notified by the first base station control plane entity through an air interface message; the first base station control plane entity indicates the first base station user plane entity to configure or modify the Uplink Data Compression (UDC) configuration information of the bearer through a bearer context establishment request or a bearer context modification request message; the uplink small data packet compression continuity maintaining module is used for reserving UDC configuration information of a suspended UDC bearer when the terminal is in an RRC inactive state, and performing uplink compression operation on the small data packet to be transmitted by adopting the reserved UDC configuration information when the small data packet SDT bearer of the terminal in a preconfigured UDC applicable area needs to be transmitted, and transmitting the compressed small data packet and an RRC connection restoration request message to a second base station, wherein the second base station is a base station of the terminal requesting RRC connection restoration; and after receiving the context restoration request message of the second base station, the first base station user plane entity determines that the SDT is born in a preconfigured uplink data compression applicable area, and indicates a restoration mode of uplink data compression of the first base station user plane entity, so that the first base station user plane entity decompresses the small data packet sent by the terminal based on the reserved UDC configuration information.
According to another aspect of the present disclosure, there is also provided a communication system including: the method comprises the steps that a first base station where a terminal is currently resident and a second base station where the terminal requests RRC connection recovery; the first base station includes: a first base station control plane entity and a first base station user plane entity; the terminal is used for acquiring one or more pre-configured UDC applicable areas which are informed by a first base station control surface entity through an air interface message, and carrying out uplink compression operation on a small data packet to be sent by adopting reserved UDC configuration information when the small data packet SDT is born by the terminal in the pre-configured UDC applicable areas and needs to be sent, and sending the compressed small data packet and an RRC connection restoration request message to a second base station, wherein the second base station is a base station of the terminal for requesting RRC connection restoration; the first base station user plane entity is used for configuring or modifying uplink data compression UDC configuration information of a bearer; the first base station control plane entity is configured to instruct the first base station user plane entity to configure or modify uplink data compression UDC configuration information of the bearer through a bearer context establishment request or a bearer context modification request message, and instruct the first base station user plane entity to suspend the UDC bearer when the terminal enters an RRC inactive state, and notify one or more of the pre-configured UDC applicable areas of the bearer through an air interface message; the first base station control plane entity is further configured to determine that the SDT is carried in a preconfigured uplink data compression applicable area after receiving the context restoration request message of the second base station, and instruct a restoration mode of uplink data compression of the first base station user plane entity; the first base station user plane entity is further configured to decompress a small data packet sent by the terminal based on the reserved UDC configuration information.
According to another aspect of the present disclosure, there is also provided a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the method of maintaining data compression continuity of any one of the above.
According to the method, the base station, the terminal, the system and the medium for maintaining data compression continuity, which are provided by the embodiment of the disclosure, small data packet transmission can maintain uplink data compression continuity when a scene supporting terminal of a base station control plane and user plane separation architecture is in an RRC inactive state, so that the delay of the small uplink control plane is ensured to realize rapid transmission of data packets, meanwhile, the control plane and the user plane are ensured to maintain understanding consistency for a user data transmission process after being separated, and the small data packet can still be adopted to promote coverage after the uplink data compression is supported when the RRC inactive state is adopted, thereby improving user experience.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure. It will be apparent to those of ordinary skill in the art that the drawings in the following description are merely examples of the disclosure and that other drawings may be derived from them without undue effort.
FIG. 1 is a diagram showing a UDC data format in the related art;
FIG. 2 is a diagram showing an RRC connection recovery process in Rel-16 according to the related art;
fig. 3 is a diagram illustrating a procedure from an RRC connected state to an RRC inactive state of a terminal in the related art;
FIG. 4 illustrates a schematic diagram of an application system in an embodiment of the present disclosure;
FIG. 5 illustrates a flow chart of a method of maintaining data compression continuity in an embodiment of the present disclosure;
FIG. 6 illustrates a UDC configuration and modification flow diagram in an embodiment of the present disclosure;
fig. 7 is a schematic diagram illustrating a procedure from an RRC connected state to an RRC inactive state in an embodiment of the present disclosure;
fig. 8 is a schematic diagram illustrating a procedure from an RRC inactive state to an RRC connected state in a terminal according to an embodiment of the present disclosure;
fig. 9 shows a schematic diagram of a base station in an embodiment of the disclosure;
FIG. 10 illustrates a schematic diagram of a terminal in an embodiment of the present disclosure;
FIG. 11 illustrates a schematic diagram of a communication system in an embodiment of the present disclosure;
fig. 12 shows a schematic diagram of a computer-readable storage medium in an embodiment of the disclosure.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. However, the exemplary embodiments may be embodied in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus a repetitive description thereof will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in software or in one or more hardware modules or integrated circuits or in different networks and/or processor devices and/or microcontroller devices.
For ease of understanding, before describing embodiments of the present disclosure, several terms referred to in the embodiments of the present disclosure are first explained as follows:
3GPP:3rd Generation Partnership Project, third generation partnership project;
NR: new Radio, new air interface;
gNB: the Next Generation NodeB, next generation base station;
RRC: radio Resource Control, radio resource control;
CP: control Plane;
UP: user Plane, user Plane;
CU: a Centralized Unit;
DU: distributed units, distributed units;
SDT: small Data Transmission, small data packet transmission;
UDC: uplink Data Compression, upstream data compression;
RACH: random Access Channel, random access channel;
DRB: data Radio Bearer, data resource bearer, abbreviated as data bearer;
SRB: signaling Radio Bearer signalling resource bearers, signalling bearers for short;
MAC: medium Access Control, medium access control;
RLC: radio Link Control, radio link control;
PDCP: packet Data Convergence Protocol, packet data convergence protocol.
The following detailed description of embodiments of the present disclosure refers to the accompanying drawings.
FIG. 4 illustrates an exemplary application system architecture diagram to which the method of maintaining data compression continuity in embodiments of the present disclosure may be applied. As shown in fig. 4, the system architecture includes a terminal 100, a network 200, and a network side device 300.
The medium used by the network 200 to provide a communication link between the terminal 100 and the network-side device 300 may be a wired network or a wireless network.
Alternatively, the wireless network or wired network described above uses standard communication techniques and/or protocols. The network is typically the Internet, but may be any network including, but not limited to, a local area network (Local Area Network, LAN), metropolitan area network (Metropolitan Area Network, MAN), wide area network (Wide Area Network, WAN), mobile, wired or wireless network, private network, or any combination of virtual private networks. In some embodiments, data exchanged over a network is represented using techniques and/or formats including HyperText Mark-up Language (HTML), extensible markup Language (Extensible MarkupLanguage, XML), and the like. All or some of the links may also be encrypted using conventional encryption techniques such as secure sockets layer (Secure Socket Layer, SSL), transport layer security (Transport Layer Security, TLS), virtual private network (Virtual Private Network, VPN), internet protocol security (Internet ProtocolSecurity, IPsec), etc. In other embodiments, custom and/or dedicated data communication techniques may also be used in place of or in addition to the data communication techniques described above.
Optionally, the terminal in the embodiments of the present disclosure may also be referred to as a UE (User Equipment), and in a specific implementation, the terminal may be a terminal-side Device such as a mobile phone, a tablet (Tablet Personal Computer), a Laptop (Laptop Computer), a personal digital assistant (Personal Digital Assistant, PDA), a mobile internet Device (Mobile Internet Device, MID), a Wearable Device (wireless Device), or a vehicle-mounted Device, which is not limited to a specific type of the terminal in the embodiments of the present disclosure.
The network side device 300 may be a base station, a relay, an access point, or the like. The base station may be a 5G or later version base station (e.g., 5G NR NB), or a base station in other communication systems (e.g., eNB base station), and it should be noted that the specific type of the network side device is not limited in the embodiments of the present disclosure.
Those skilled in the art will appreciate that the number of terminals, networks and network side devices in fig. 4 is merely illustrative and that any number of terminals, networks and network side devices may be provided as desired. The embodiments of the present disclosure are not limited in this regard.
Under the system architecture described above, embodiments of the present disclosure provide a method for maintaining data compression continuity, which may be performed by any electronic device having computing processing capabilities. In some embodiments, the method for maintaining data compression continuity provided in the embodiments of the present disclosure may be implemented by a terminal and a network side device in the system architecture in an interactive manner.
Fig. 5 shows a flowchart of a method for maintaining data compression continuity in an embodiment of the present disclosure, as shown in fig. 5, where the method for maintaining data compression continuity provided in an embodiment of the present disclosure includes the following steps:
s502, the first base station control plane entity indicates the first base station user plane entity to configure or modify the uplink data compression UDC configuration information of the bearer through a bearer context establishment request or a bearer context modification request message, and indicates the first base station user plane entity to suspend the UDC bearer when the terminal enters an RRC inactive state, and informs one or more bearer preconfigured UDC applicable areas in the terminal through an air interface message.
S504, the first base station control plane entity configures the terminal to enter an RRC inactive state and maintains UDC continuity when the terminal enters the RRC inactive state, so that when the terminal is in the RRC inactive state, the terminal reserves UDC configuration information of a suspended UDC bearer, and when a small data packet SDT (data packet) in a preconfigured UDC applicable area bears the small data packet to be transmitted, uplink compression operation is carried out on the small data packet to be transmitted by adopting the reserved UDC configuration information, the compressed small data packet and an RRC connection recovery request message are transmitted to a second base station, and the second base station requests the RRC connection recovery for the terminal.
S506, after receiving the context recovery request message of the second base station, the first base station control plane entity determines that the SDT is born in a preconfigured uplink data compression applicable area, and indicates a recovery mode of uplink data compression of the first base station user plane entity, so that the first base station user plane entity performs decompression operation on the small data packet sent by the terminal based on the reserved UDC configuration information.
Fig. 6 illustrates a UDC configuration and modification flow chart in an embodiment of the disclosure, where, as shown in fig. 6, a base station control plane entity may instruct a first base station user plane entity to configure or modify uplink data compressed UDC configuration information of a bearer through a bearer context establishment request or a bearer context modification request message.
In some embodiments, the method for maintaining data compression continuity provided in the embodiments of the present disclosure further comprises the steps of: the first base station control plane entity sends a first data bearer DRB list to the first base station user plane entity through a first bearer context establishment request message or a first bearer context modification request message so as to request establishment or modification of UDC configuration information contained in PDCP configuration; when the first base station is an LTE air interface, DRB To Setup List of an E-UTRAN mode is adopted by the first DRB establishment list; when the first base station is an NR air interface, the first DRB list is DRB To Setup List contained in PDU Session Resource To Setup Modification List in NR mode.
In some embodiments, the sum of the number of uplink data compression bearers to be configured by the ue and the number of currently active uplink data compression bearers does not exceed a preset UDC bearer upper limit, and the number of currently active uplink data compression bearers is the number of activated and unreleased uplink data compression bearers.
In some embodiments, the first bearer context establishment request message includes a first bearer list for requesting establishment, where the first bearer list includes: one or more DRBs carry configuration information; the first bearer context modification request message comprises a first bearer list which requests establishment and/or a second bearer list which requests modification, the first bearer list comprises one or more DRB bearer configuration information, and the second bearer list comprises: one or more DRBs carry configuration information, bearers of the UDC to be turned off, bearers of the UDC to be released.
In some embodiments, each DRB bearer configuration information includes at least the following information: 1) The DRB mark is a value of an integer type; 2) SDT bearing type indication information, enumeration type, and SDT bearing when the value is yes, supporting small data packet compression of the terminal in the RRC inactive state; 3) PDCP configuration information, which at least includes the following information: the PDCP reestablishment indication information enumerates types, and indicates that the PDCP entity of the DRB needs to be reestablished when the value is yes, and the PDCP reestablishment information is carried only when the UDC configuration of the DRB needs to be deleted; 4) UDC configuration information including at least the following information: (1) UDC decompresses the buffer size, enumerates the type, and takes the value including at least one of: 2048 bytes, 4096 bytes, and 8912 bytes; (2) dictionary information, enumeration type, and value including at least one of the following: a SIP-SID dictionary, a custom dictionary; (3) UDC continuity indication information: and (3) enumerating the types, wherein when the value is yes, the PDCP entity can continue or restart the uplink data compression function in the PDCP reestablishment process.
In some embodiments, the method for maintaining data compression continuity provided in the embodiments of the present disclosure further comprises the steps of: if the first base station user plane entity finds that the UDC configuration is contained in the PDCP configuration carried by the first bearer context modification request message after receiving the first bearer context establishment request message from the first base station control plane entity and the first base station user plane supports the UDC configuration, configuring an uplink data compression function of a corresponding DRB bearer by adopting related parameters, and returning a first bearer context establishment response message to the first base station control plane entity; if the first base station user plane entity finds that the UDC configuration is contained in the PDCP configuration carried by the first bearer context modification request message after receiving the first bearer context modification request message from the first base station control plane entity, and the first base station user plane supports the UDC configuration, configuring an uplink data compression function of a corresponding DRB bearer by adopting related parameters, and returning a first bearer context modification response message to the first base station control plane entity.
In some embodiments, the method for maintaining data compression continuity provided in the embodiments of the present disclosure further comprises the steps of: the first base station user plane entity performs bearer configuration by: checking whether the bearer configuration information of each DRB identifier carries UDC configuration information or not in a bearer list requested to be released, and if so, releasing the bearer corresponding to the DRB identifier; checking whether PDCP configuration information in the bearer configuration information of each bearer carries UDC configuration information or not in a bearer list requested to be modified, and if the first base station user plane entity supports the UDC capability, configuring an uplink data compression function for the bearer; if the number of configured uplink data compression bearers exceeds the preset UDC bearer upper limit value, determining that bearer modification fails, and generating a failure cause value, wherein the failure cause value is used for indicating that the number of UDC bearers exceeds the preset UDC bearer upper limit value or that PDCP bearer configuration cannot be supported; if the configuration information of any one bearer with configured UDC function carries PDCP reestablishment instruction information, all data in the bearer, decompression caches and dictionary information are emptied, dictionary information and decompression caches are reconfigured according to the carried UDC configuration information, wherein if no dictionary is configured in the dictionary information, the size of the UDC decompression caches is set to 0; if the dictionary information is configured with a dictionary, configuring the UDC decompression buffer size according to the dictionary information; checking whether PDCP configuration information in the bearer configuration information of each bearer carries UDC configuration information or not in a bearer list established by the request, and if the first base station user plane entity supports the UDC capability, configuring an uplink data compression function for the bearer; if the number of configured uplink data compression bearers exceeds the preset UDC bearer upper limit value, determining that the bearer establishment fails, and generating a failure cause value, wherein the failure cause value is used for indicating that the number of UDC bearers exceeds the preset UDC bearer upper limit value or that PDCP bearer configuration cannot be supported.
In some embodiments, the first bearer context setup response message or the first bearer context modification response message includes: a bearer configuration success information list or a bearer configuration failure information list; the bearer configuration success information list is used for indicating one or more data bearers successfully configured in the bearer list requested to be established or modified; the bearer configuration failure information list is used to indicate one or more data bearers that cannot be configured in the bearer list that is requested to be established or modified.
In some embodiments, the bearer configuration success information list includes: an identification of one or more data bearers successfully configured; the bearer configuration failure information list includes: the identity of the one or more data bearers that cannot be configured and the reason for failure of each data bearer, the reason for failure including: the number of UDC bearers exceeds a preset UDC bearer upper limit or PDCP bearer configuration cannot be supported.
In some embodiments, the method for maintaining data compression continuity provided in the embodiments of the present disclosure further comprises the steps of: after receiving a first bearer context establishment response message or a first bearer context modification response message from the first base station user plane entity, the first base station control plane entity determines a configuration result of the bearer which is requested to be established or modified in the first base station user plane entity; the first base station control plane entity generates a first RRC reconfiguration message sent to the terminal according to the configuration result, and sends the established or modified bearer configuration information to the terminal through the first RRC reconfiguration message, wherein the bearer configuration information carried in the first RRC reconfiguration message comprises: UDC configuration information, wherein the bearer in the configuration result and the bearer in the first RRC reconfiguration message have a mapping relation; for a bearer which needs to be added and configured as a UDC, placing a DRB identifier of the bearer in a DRB establishment list in an RRC message; for the bearer which needs to be modified into the existing bearer and is configured into the UDC, the bearer DRB identifier is placed in a DRB release list and a DRB establishment list in an RRC message, and the sum of the number of the bearer which is configured into the UDC by the terminal after RRC reconfiguration and the number of the uplink data compression bearers which are currently activated is the number of the uplink data compression bearers which are activated and not released is ensured not to exceed a preset UDC bearer upper limit value.
In some embodiments, the first RRC reconfiguration message includes at least the following information: 1) A DRB release list comprising: one or more DRB identifiers for deleting the UDC configuration information; 2) The DRB builds and modifies a list comprising: one or more DRB configuration information, each DRB configuration information comprising at least: (1) a DRB mark; (2) UDC decompresses the buffer size, enumerates the type, and takes the value including at least one of: 2048 bytes, 4096 bytes, and 8912 bytes; (3) dictionary information: the enumeration type, the value includes at least one of the following: SIP-SID dictionary, custom dictionary.
In some embodiments, after the first base station control plane entity sends the successfully established or modified bearer configuration information to the terminal through the first RRC reconfiguration message, the method for maintaining data compression continuity provided in the embodiments of the present disclosure further includes the following steps: the terminal performs configuration and reconfiguration of the UDC by: for each DRB identifier in the DRB release list, deleting all configuration information of the corresponding DRB, and recording the number of UDC bearers required to be released as T1; for each bearer needing to be configured in the UDC in the DRB establishment or modification list, configuring the size of a decompression cache and dictionary information of the UDC, setting all initial information in the cache to 0, and recording the number of the UDC bearers needing to be established as T2; recording that the number of the established UDC bearers is T0 before the terminal receives the first RRC reconfiguration message, and when the value of T0-T1+T2 does not exceed the preset UDC bearer upper limit value or one established DRB mark is not added or modified directly under the condition of not being released, determining that the UDC configuration of the bearers is successful, and generating a first RRC reconfiguration confirmation message; when the value of T0-T1+T2 exceeds the preset UDC bearing upper limit value or an established DRB mark is generated, the UDC configuration of the bearing is determined to fail, and a first RRC reconfiguration failure message is generated.
In some embodiments, the method for maintaining data compression continuity provided in the embodiments of the present disclosure further comprises the steps of: the first base station control plane entity determines that a small data packet transmission bearing which needs to be suspended when the terminal enters an inactive state, and indicates the first base station user plane entity to trigger a bearing suspension process through a second bearing context modification request message, wherein the second bearing context modification request message at least comprises the following information: bearing suspension indication information: the enumeration type at least comprises the following values: bearer suspension, bearer restoration, and small packet transmission restoration.
In some embodiments, the method for maintaining data compression continuity provided in the embodiments of the present disclosure further comprises the steps of: after receiving the second bearer context modification request message, the first base station user plane entity suspends all bearers according to the suspension indication carried in the bearer suspension indication message, and for the configured UDC bearers, continues to maintain the preconfigured decompression buffer and dictionary information during suspension, does not perform any operation of clearing or resetting to 0 for the UDC decompression buffer and dictionary, generates a second bearer context modification response message, and sends the second bearer context modification response message to the first base station control plane entity.
In some embodiments, the method for maintaining data compression continuity provided in the embodiments of the present disclosure further comprises the steps of: after receiving the second bearer context modification response message, the first base station control plane entity determines an uplink data compression application area of the terminal according to the preconfiguration information, and generates a second RRC reconfiguration message sent to the terminal, where the second RRC reconfiguration message is used for indicating that the terminal keeps the uplink compression capability of the small data packet transmission bearer when entering the RRC inactive state.
In some embodiments, the second RRC reconfiguration message includes: suspending configuration information; the suspension configuration information includes at least the following information: the SDT bearing list comprises one or more SDT bearing identifiers, and each SDT bearing identifier is a value of an integer type; the uplink data compression continuity indication information is of an enumeration type, and takes the value of a cell or a radio access network notification area RNA.
In some embodiments, the method for maintaining data compression continuity provided in the embodiments of the present disclosure further comprises the steps of: after receiving the second RRC reconfiguration message, the terminal configures related bearers according to the following procedures, and feeds back a second RRC reconfiguration confirmation message to the first base station: if the second RRC reconfiguration message contains the suspension configuration information, further judging whether the suspension configuration information contains the SDT bearer list or not; if the suspension configuration information contains the SDT bearer list, storing the corresponding DRB identification, and determining the bearer of the corresponding DRB identification as a support terminal to transmit small data packets in an RRC non-excited state; judging whether the suspension configuration information contains uplink data compression continuity indication information or not; if the suspension configuration information contains the uplink data compression continuity indication information, all bearers which are supported in an SDT state and configured with UDCs are configured, the uplink data compression configuration is kept when a small data packet is adopted for transmission, the configured decompression cache and dictionary information are kept continuously, and the configured uplink data compression applicable area is stored; if the suspension configuration information does not contain the uplink data compression continuity indication information, all bearers supporting the SDT state and configured with the UDC are not transmitted in an uplink data compression mode when the terminal is in an inactive state, and the configured decompression buffer memory and dictionary information are emptied.
In some embodiments, the method for maintaining data compression continuity provided in the embodiments of the present disclosure further comprises the steps of: if the suspension configuration information does not contain the SDT bearer list, determining that the bearer of the corresponding DRB identifier does not support the transmission of the small data packet when the terminal is in the RRC non-activated state.
In some embodiments, the method for maintaining data compression continuity provided in the embodiments of the present disclosure further comprises the steps of: when the SDT of the terminal bears an uplink data packet to be sent, caching the uplink data packet to be sent in an application layer, and indicating an access layer to check whether a cell currently resided in is in a preconfigured uplink data compression applicable area; if the access layer finds that the cell where the access layer resides is in a preconfigured uplink data compression applicable area, the access layer instructs the application layer to compress uplink data, the uplink data packet buffered by the application layer is sent to a PDCP layer of the terminal, the uplink data packet buffered by the application layer is sent to a compression buffer according to preconfigured dictionary information, after data compression is completed, the uplink data packet is sent to an MAC layer of the terminal, and when the data volume of the uplink data packet reaches a preset data volume threshold value, a subsequent sending operation is triggered; if the access layer finds that the cell where the cell resides is not in the preconfigured uplink data compression application area, the application layer informs the access layer of the uplink data packet to be sent, and the access layer does not perform uplink data compression operation when sending the uplink data packet.
In some embodiments, the second base station is different from the first base station, the method further comprising: after receiving the RRC connection restoration request message and the uplink data packet sent by the terminal, if no user context information of the terminal is found, the second base station caches the received uplink data packet in the MAC layer of the second base station, and sends a user context acquisition request message to the first base station control plane entity, where the user context acquisition request message includes a cell identifier where the terminal currently resides, a downlink channel address, and SDT indication information.
In some embodiments, the user context acquisition request message further includes: SDT side information, the SDT side information including: one or more transmissions.
In some embodiments, the method for maintaining data compression continuity provided in the embodiments of the present disclosure further comprises the steps of: the first base station control plane entity checks whether a cell where the terminal currently resides is in a preconfigured uplink data compression applicable area; if the first base station control plane entity finds that the cell where the terminal currently resides is located in a preconfigured uplink data compression applicable area, determining that the UDC transmission bearer is configured to continue to perform uplink data decompression operation by adopting the existing compression cache and dictionary information, and returning a part of user context transfer request message to the second base station; and if the first base station control plane entity finds that the cell where the terminal currently resides is not in the preconfigured uplink data compression applicable area, sending a user context acquisition response message to the second base station.
In some embodiments, the partial user context transfer request message includes: 1) A second base station allocates an identifier for the user on a base station interface; 2) The first base station locates the user allocated mark on the base station interface; 3) The SDT bearer setup list includes: one or more SDT bearer lists, each SDT bearer list comprising: (1) a DRB list; (2) uplink user plane address information on an interface between base stations; (3) RLC bearer configuration information of the DRB; (4) QOS information of the DRB; (5) RLC mode; (6) SN length of RLC; (7) slice configuration information.
In some embodiments, the user context acquisition response message includes: 1) A second base station allocates an identifier for the user on a base station interface; 2) The first base station locates the user allocated mark on the base station interface; 3) A DRB identification list comprising one or more DRB configuration information, each DRB configuration information comprising information such that: (1) the logic channel identification is a value of an integer type; (2) RLC layer configuration information; (3) MAC layer configuration information; (4) PDCP layer configuration information.
In some embodiments, the method for maintaining data compression continuity provided in the embodiments of the present disclosure further comprises the steps of: if the second base station receives the partial user context transfer request message, returning a partial user context transfer response message, wherein the partial user context transfer response message comprises an SDT data forwarding DRB identification list, and the SDT data forwarding DRB identification list comprises: one or more DRB configuration information, each DRB configuration information comprising information such as: (1) a DRB mark; (2) UDC indication information, enumeration type, when the value is yes, the DRB is configured for UDC; (3) a logic channel identifier, wherein the value is an integer type numerical value; (4) downlink user plane address information of interfaces between base stations.
In some embodiments, the method for maintaining data compression continuity provided in the embodiments of the present disclosure further comprises the steps of: after receiving the partial user context transfer request message, the first base station control plane entity sends a third bearer context modification request message to the first base station user plane entity, where the third bearer context modification request message is used to request to resume data reception, and the third bearer context modification request message includes the following information: 1) The carrying suspending indication information, the enumeration type and the value at least comprise: bearer suspension, bearer recovery and small data packet transmission recovery; 2) A downstream channel address comprising: IP address and port address; 3) UDC continuity indication information: and the Boolean type is used for indicating that all bearers configured as SDT bearers and UDC are configured to restore the uplink data compression continuity maintaining function when the value is yes.
In some embodiments, the method for maintaining data compression continuity provided in the embodiments of the present disclosure further comprises the steps of: after receiving the third bearer context modification request message, the first base station user plane entity restores the small data packet transmission bearer of the terminal according to the small data packet transmission restoration instruction information, and when the value of the UDC continuity instruction information is yes, determines whether the bearer restoration of the configured UDC adopts preconfigured cache information and dictionary information according to the second bearer configuration information; if not, the preconfigured cache information and dictionary information are cleared; the first base station user plane entity distributes the address information for receiving the uplink data for each bearing.
In some embodiments, the method for maintaining data compression continuity provided in the embodiments of the present disclosure further comprises the steps of: the first base station user plane entity sends a third bearer context modification response message to the first base station control plane entity to inform the first base station control plane entity that the bearer configuration has been completed.
In some embodiments, the third bearer context modification response message includes the following information: 1) The successfully configured bearer list comprises one or more identifiers of SDT bearers; 2) The uplink carried receiving address information comprises: IP address and port address.
In some embodiments, the method for maintaining data compression continuity provided in the embodiments of the present disclosure further comprises the steps of: after receiving the third bearer context modification response message, the first base station control plane entity sends the uplink bearer receiving address information to the second base station through the context acquisition response message, and when the first base station and the second base station are the same base station, the first base station control plane entity sends the uplink bearer receiving address information to the first base station separation entity.
In some embodiments, the method for maintaining data compression continuity provided in the embodiments of the present disclosure further comprises the steps of: and after receiving the third bearing context modification response message, the second base station sends the cached uplink data to the user plane entity of the first base station according to the received address information of the uplink bearing.
In some embodiments, the method for maintaining data compression continuity provided in the embodiments of the present disclosure further comprises the steps of: and the first base station user plane entity completes the decompression operation of the uplink data according to the preconfigured cache information and dictionary information and completes the updating operation of the cache information and the dictionary information.
The following describes two specific embodiments for explaining a user plane configuration method supporting a low latency service provided in the embodiments of the present disclosure:
example 1: in the control plane CP/user plane UP split base station scenario, the UDC configuration procedure of one bearer is modified by E1 interface message Bearer Context Modification procedure, where DRB1 has configured the UDC procedure, and the gNB-CU-CP deletes the UDC configuration for DRB1 and configures the UDC capabilities for the newly established bearers DRB2 and DRB 3. And then the gNB-CU-CP changes the UDC configuration information of the corresponding bearer for the UE through the RRC reconfiguration message.
The first base station control plane entity (gNB-CU-CP 1) sends a first bearer configuration information to the first base station user plane configuration entity by placing the first bearer configuration information in a first DRB establishment list through a first bearer establishment request or Bearer Context Modification Request, wherein the sum of the number of bearers of activated uplink data compression and the number of bearers of activated uplink data compression minus the number of bearers of released uplink data compression is configured through the first bearer establishment or modification request message does not exceed a first configuration number, and Bearer Context Modification Request comprises the following information:
●DRB to Setup List；
●DRB to Modify List；
The information content contained in DRB to Setup List for DRB2 and DRB3 is as follows:
for DRB2 are:
● DRB identification: 2;
● SDT bearer type indication: is;
● UDC configuration information, including the following:
■ Cache size: 2048 bytes;
■ Dictionary information: SIP-DIP;
for DRB3 are:
● DRB identification: 3, a step of;
● SDT bearer type indication: is;
● UDC configuration information, including the following:
■ Cache size: 2048 bytes;
■ Dictionary information: SIP-DIP;
the content for DRB1 in DRB to Modify List includes:
● DRB identification: 3, a step of;
● SDT bearer type indication: is;
● PDCP reestablishment information: is;
1) After the first base station user plane entity (gNB-CU-UP 1) receives Bearer Context Modification Request, the following steps are performed:
● Checking the released bearing list, and if the released bearing list is empty, not making the bearing list;
● And DRB to Modify List, if the DRB1 bearer is configured with the reestablishment instruction information and is configured with the UDC information before, all data in the bearer and the decompressed cache and dictionary information are emptied.
● Checking DRB to Setup List that PDCP configuration information in DRB1 and DRB2 information both carry UDC configuration, configuring uplink data compression for the bearer if the first base station user plane entity (gNB-CU-UP 1) supports UDC capability, configuring decompression buffer information according to dictionary information, and generating Bearer Context Modification Response response message.
2) The first base station user plane entity (gNB-CU-UP 1) generates Bearer Context Modification Response message according to the UDC configuration case, wherein Bearer Context Modification Response message comprises the following:
●DRB1；
●DRB2；
●DRB3；
3) After receiving the Bearer Context Modification Response message, the first base station control plane entity (gNB-CU-CP 1) determines a configuration result loaded in the first base station user plane entity (gNB-CU-UP 1), and sends the bearing configuration information to the terminal through an RRC reconfiguration message, wherein the RRC reconfiguration message comprises the following steps:
● First DRB release list: DRB1
● DRB1 configuration information:
■DRB1
● DRB2 configuration information:
■DRB2
■ Compressed cache size of UDC: 2048
■ Dictionary information: SIP-SDP dictionary
● DRB3 configuration information:
■DRB3
■ Compressed cache size of UDC: 2048
■ Dictionary information: SIP-SDP dictionary
Example 2: in the CP/UP separate base station scenario, the UE moves from the second base station (gNB 1) to the second base station (gNB 2) after entering the RRC inactive state, wherein the UDC available area configured on the network side is an RNA range, and wherein the second base station (gNB 2) belongs to the RNA range. Wherein both DRB1 and DRB2 are configured for UDC continuity.
1) The first base station control plane entity (gNB-CU-CP 1) triggers the SDT bearer to enter a suspended state and indicates to trigger the bearer suspension procedure via a Bearer Context Modification Request message, wherein Bearer Context Modification Request message includes, but is not limited to, the following:
● Bearing suspension indication information: suspension of
2) After receiving the Bearer Context Modification Request message, the first base station user plane entity (gNB-CU-UP 1) suspends all the bearers according to the suspending indication carried in the bearer suspending indication information, meanwhile, for the bearer configured with the UDC, the buffer memory and dictionary configuration information of the decompressor need to be kept continuously during suspending, no clearing or resetting to 0 is performed, and Bearer Context Modification Response message is generated and sent to the first base station control plane entity (gNB-CU-CP 1).
3) After receiving the Bearer Context Modification Response message, the first base station control plane entity (gNB-CU-CP 1) determines the UDC bearing application range of the terminal according to the first pre-configuration information, and generates a second RRC message sent to the terminal for indicating the terminal to enter an inactive state to keep the uplink compression capability of the SDT bearing. Wherein the second RRC message includes, but is not limited to, the following information:
● The suspension configuration information includes the following:
■ SDT bearer list: DRB1 and DRB2
■ Uplink data compression continuity indication information: RNA (ribonucleic acid)
4) After receiving the RRC reconfiguration message, the terminal configures related bearers according to the following process, and feeds back an RRC reconfiguration completion message of the bearers to the first base station:
If the suspension configuration information is contained, further judging whether the SDT bearer list is contained; if the SDT bearer list is included, corresponding DRB identifiers are saved, and the bearers are determined to support transmission of small data packets when the terminal is in an inactive state; further judging whether the uplink data compression continuity indicating information is contained; if the uplink data compression continuity indication information is included, all the bearers which are supported in the SDT state and are configured with the UDC are configured in an uplink compression mode when a small data packet is sent, and the dictionary and the compression cache are not deleted to be continuously maintained, and the application range of the UDC is saved; otherwise, these bearers do not support sending small packets in the idle state.
5) When the SDT of the terminal side bears data to be transmitted, the data is buffered in an application layer, and an access layer is instructed to check whether a cell where the access layer resides is in an area range configured by UDC, and as a second base station (gNB 2) is in the area range, the access layer instructs the application layer that the data can be compressed, an uplink data packet buffered in the application layer is transmitted to a PDCP layer of the terminal, and is transmitted to a MAC layer of the terminal after the data is transmitted to a compression buffer according to a dictionary, and a subsequent transmitting operation is triggered when the data quantity reaches a threshold.
6) After receiving the connection recovery request message and the uplink data packet sent by the terminal, the second base station (gNB 2) caches the received uplink data packet and indicates the context acquisition request message to the second base station (gNB 1) -CU-CP, wherein the context acquisition request message comprises the cell identifier and the downlink channel address where the terminal currently resides.
7) The first base station control plane entity (gNB-CU-CP 1) discovers that the cell where the terminal is currently resident is in the preconfigured range of the UDC continuity bearer, and when the cell is in the preconfigured range, the SDT bearer of the UDC can continue to perform uplink decompression operation by adopting the existing cache and dictionary, and the anchor point is still maintained in the first base station, and informs the second base station (gNB 2) through a partial user context transfer request (Partial UE Context Transfer) message. Wherein the connection response message includes the following:
● DRB identification list: DRB1 and DRB2, each DRB including the following information:
■ Logical channel identification: an integer value;
■ RLC layer configuration information;
■ MAC layer configuration information;
■ PDCP layer configuration information;
8) The first base station control plane entity (gNB-CU-CP 1) sends a bearer context modification request (Bearer Context Modification Request) message to resume data reception after the connection resume failure message, wherein the bearer context modification request (Bearer Context Modification Request) message includes, but is not limited to, the following information:
● Bearing suspension indication information: SDT recovery;
● Downstream channel address information: including the transmitted IP address and port address;
● UDC continuity indication: is;
9) And after receiving the UDC continuity indication message, the first base station user plane entity (gNB-CU-UP 1) restores all SDT bearers of the terminal according to the SDT restoration indication, and when the UDC continuity indication is yes, the bearer configured with the UDC is determined to restore to adopt the existing dictionary and cache information. And determining the received address information of the uplink bearer.
10 The first base station user plane entity (gNB-CU-UP 1) is informed about the completion of the bearer configuration by means of a bearer context modification request response (Bearer Context Modification Response) message. Wherein the bearer context modification request response (Bearer Context Modification Response) message includes, but is not limited to, the following:
● Successful bearer list configuration: DRB1 and DRB2;
● And receiving address information carried by the uplink.
11 After receiving the response (Bearer Context Modification Response) of the bearer context modification request, the first base station control plane entity (gNB-CU-CP 1) sends the uplink transmission address to the second base station (gNB 2) through the context acquisition response information, and if the first base station and the second base station (gNB 2) are the same base station, the first base station control plane entity (gNB-CU-CP 1) sends the uplink transmission address to the first base station separation entity.
12 After receiving the partial user context transfer response (Partial UE Context Transfer ACK) message, the second base station (gNB 2) sends the cached uplink data to the first base station user plane entity (gNB-CU-UP 1) according to the uplink bearing receiving address information.
13 The first base station user plane entity (gNB-CU-UP 1) completes the decompression operation of the uplink data according to the dictionary and the buffer information, and completes the updating operation of the dictionary and the buffer.
Fig. 7 shows a procedure in which a terminal is from an RRC connected state to an RRC inactive state; fig. 8 shows a procedure in which a terminal goes from an RRC inactive state to an RRC connected state.
Based on the same inventive concept, a base station is also provided in the embodiments of the present disclosure, as described in the following embodiments. Since the principle of the solution of the problem of the base station embodiment is similar to that of the method embodiment, the implementation of the base station embodiment can be referred to the implementation of the method embodiment, and the repetition is omitted.
Fig. 9 shows a schematic diagram of a base station in an embodiment of the disclosure, and as shown in fig. 9, the base station 300 includes: a base station control plane entity 3001 and a base station user plane entity 3002;
the base station control plane entity 3001 is configured to instruct the first base station user plane entity to configure or modify uplink data compression UDC configuration information of a bearer through a bearer context establishment request or a bearer context modification request message, instruct the first base station user plane entity 3002 that a suspended UDC bearer is required when the terminal enters an RRC inactive state, and notify one or more bearer preconfigured UDC applicable areas in the terminal through an air interface message;
The base station user plane entity 3002 is configured to configure or modify uplink data compression UDC configuration information of a bearer, and when the terminal enters an RRC inactive state, acquire a UDC bearer to be suspended; when the terminal is in an RRC inactive state, the terminal reserves UDC configuration information of a suspended UDC bearer, and when the terminal has small data packets carried by a small data packet SDT in a preconfigured UDC applicable area and needs to be transmitted, the reserved UDC configuration information is adopted to carry out uplink compression operation on the small data packets to be transmitted, the compressed small data packets and an RRC connection recovery request message are transmitted to a second base station, and the second base station is a base station of the terminal requesting RRC connection recovery; the base station control plane entity is further configured to determine that the SDT is carried in a preconfigured uplink data compression applicable area after receiving the context restoration request message of the second base station, and instruct a restoration mode of uplink data compression of the user plane entity of the first base station; the first base station user plane entity 3002 is further configured to perform a decompression operation on the small data packet sent by the terminal based on the reserved UDC configuration information.
Based on the same inventive concept, a base station is also provided in the embodiments of the present disclosure, as described in the following embodiments. Since the principle of the solution of the problem of the base station embodiment is similar to that of the method embodiment, the implementation of the base station embodiment can be referred to the implementation of the method embodiment, and the repetition is omitted.
Fig. 10 shows a schematic diagram of a terminal in an embodiment of the disclosure, as shown in fig. 10, the terminal 100 includes: an uplink data compression configuration information acquisition module 1001 and an uplink small data packet compression continuity holding module 1002.
The uplink data compression configuration information obtaining module 1001 is configured to obtain, through an air interface message, one or more UDC application areas configured in advance for carrying and notified by the first base station control plane entity; the first base station control plane entity indicates the first base station user plane entity to configure or modify the Uplink Data Compression (UDC) configuration information of the bearer through a bearer context establishment request or a bearer context modification request message; the uplink small data packet compression continuity maintaining module 1002 is configured to, when the terminal is in an RRC inactive state, reserve UDC configuration information of a suspended UDC bearer, and when the terminal needs to send a small data packet in a small data packet SDT bearer in a preconfigured UDC applicable area, perform uplink compression operation on the small data packet to be sent by using the reserved UDC configuration information, send the compressed small data packet together with an RRC connection restoration request message to a second base station, where the second base station is a base station that the terminal requests RRC connection restoration; the first base station user plane entity is further configured to determine that the SDT is carried in a preconfigured uplink data compression applicable area after receiving the context restoration request message of the second base station, and instruct the first base station user plane entity to restore the uplink data compression, so that the first base station user plane entity decompresses the small data packet sent by the terminal based on the reserved UDC configuration information.
Based on the same inventive concept, a communication system is also provided in the embodiments of the present disclosure, as described in the following embodiments. Since the principle of the solution of the problem of the base station embodiment is similar to that of the method embodiment, the implementation of the base station embodiment can be referred to the implementation of the method embodiment, and the repetition is omitted.
Fig. 11 shows a schematic diagram of a communication system in an embodiment of the disclosure, as shown in fig. 11, including: the terminal 100 and a first base station 300A where the terminal 100 currently resides and a second base station 300B where the terminal requests RRC connection restoration;
wherein the first base station 300A includes: a first base station control plane entity 3001A and a first base station user plane entity 3002A; the terminal is configured to obtain one or more pre-configured UDC application areas for carrying the notification of the first base station control plane entity 3002A through an air interface message, and when the small data packet SDT carried by the terminal in the pre-configured UDC application area needs to be sent, perform uplink compression operation on the small data packet to be sent by using the reserved UDC configuration information, and send the compressed small data packet and the RRC connection restoration request message to the second base station 300B, where the second base station 300B is a base station for the terminal to request RRC connection restoration; the first base station user plane entity 3002A is configured or adapted to modify uplink data compression UDC configuration information of a bearer; the first base station control plane entity 3001A is configured to instruct the first base station user plane entity 3002A to configure or modify uplink data compression UDC configuration information of a bearer through a bearer context establishment request or a bearer context modification request message, and instruct the first base station user plane entity 3002A to suspend a UDC bearer when the terminal enters an RRC inactive state, and notify one or more of the pre-configured UDC applicable areas of the bearer through an air interface message; the first base station control plane entity 3001A is further configured to determine that the SDT is carried in a preconfigured uplink data compression applicable area after receiving the context restoration request message of the second base station 300B, and instruct the restoration mode of uplink data compression of the first base station user plane entity 3002A; the first base station user plane entity 3002A is further configured to perform a decompression operation on the small data packet sent by the terminal based on the reserved UDC configuration information.
From the description of the embodiments above, those skilled in the art will readily appreciate that various aspects of the disclosure may be embodied in the following forms, namely: an entirely hardware embodiment, an entirely software embodiment (including firmware, micro-code, etc.) or an embodiment combining hardware and software aspects. Thus, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (may be a CD-ROM, a U-disk, a mobile hard disk, etc.) or on a network, including several instructions to cause a computing device (may be a personal computer, a server, a terminal device, or a network device, etc.) to perform the method according to the embodiments of the present disclosure.
In an exemplary embodiment of the present disclosure, a computer-readable storage medium, which may be a readable signal medium or a readable storage medium, is also provided. Fig. 12 illustrates a schematic diagram of a computer-readable storage medium in an embodiment of the present disclosure, where a program product capable of implementing the method of the present disclosure is stored on the computer-readable storage medium 1200 as illustrated in fig. 12. In some possible implementations, various aspects of the disclosure may also be implemented in the form of a program product comprising program code for causing a terminal to carry out the steps according to the various exemplary embodiments of the disclosure as described in the "exemplary methods" section of this specification, when the program product is run on the terminal.
More specific examples of the computer readable storage medium in the present disclosure may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
In this disclosure, a computer readable storage medium may include a data signal propagated in baseband or as part of a carrier wave, with readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Alternatively, the program code embodied on a computer readable storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
In particular implementations, the program code for carrying out operations of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., connected via the Internet using an Internet service provider).
It should be noted that although in the above detailed description several modules or units of a device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit in accordance with embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into a plurality of modules or units to be embodied.
Furthermore, although the steps of the methods in the present disclosure are depicted in a particular order in the drawings, this does not require or imply that the steps must be performed in that particular order or that all illustrated steps be performed in order to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step to perform, and/or one step decomposed into multiple steps to perform, etc.
From the description of the above embodiments, those skilled in the art will readily appreciate that the example embodiments described herein may be implemented in software, or may be implemented in software in combination with the necessary hardware. Thus, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (may be a CD-ROM, a U-disk, a mobile hard disk, etc.) or on a network, including several instructions to cause a computing device (may be a personal computer, a server, a mobile terminal, or a network device, etc.) to perform the method according to the embodiments of the present disclosure.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any adaptations, uses, or adaptations of the disclosure following the general principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
Claims (36)
1. A method of maintaining data compression continuity, comprising:
the first base station control plane entity indicates the first base station user plane entity to configure or modify Uplink Data Compression (UDC) configuration information of the bearer through a bearer context establishment request or a bearer context modification request message, and indicates the first base station user plane entity to suspend the UDC bearer when the terminal enters a Radio Resource Control (RRC) inactive state, and informs one or more bearer preconfigured UDC applicable areas in the terminal through an air interface message;
the method comprises the steps that a first base station control plane entity configures a terminal to enter an RRC inactive state, UDC continuity is kept when the terminal enters the RRC inactive state, so that when the terminal is in the RRC inactive state, the terminal reserves UDC configuration information of a suspended UDC bearer, and when a small data packet SDT (data packet) is born in a preconfigured UDC applicable area and needs to be sent, uplink compression operation is carried out on the small data packet to be sent by adopting the reserved UDC configuration information, and the compressed small data packet and an RRC connection recovery request message are sent to a second base station together, wherein the second base station is a base station of the terminal requesting RRC connection recovery;
after receiving the context restoration request message of the second base station, the first base station control plane entity determines that the SDT is born in a preconfigured uplink data compression applicable area, and indicates a restoration mode of uplink data compression of the first base station user plane entity, so that the first base station user plane entity performs decompression operation on the small data packet sent by the terminal based on the reserved UDC configuration information.
2. The method of maintaining data compression continuity as recited in claim 1, further comprising:
the first base station control plane entity sends a first data bearer DRB list to the first base station user plane entity through a first bearer context establishment request message or a first bearer context modification request message so as to request establishment or modification of UDC configuration information contained in PDCP configuration;
when the first base station is an LTE air interface, DRB To Setup List of an E-UTRAN mode is adopted by the first DRB establishment list; when the first base station is an NR air interface, the first DRB list is DRB To Setup List contained in PDU Session Resource To Setup Modification List in NR mode.
3. The method according to claim 2, wherein a sum of a number of uplink data compression bearers to be configured by the base station user plane entity and a number of currently activated uplink data compression bearers, which is a number of activated and unreleased uplink data compression bearers, does not exceed a preset UDC bearer upper limit value.
4. A method for maintaining continuity of data compression according to claim 3, wherein the first bearer context establishment request message includes a first bearer list for requesting establishment, and the first bearer list includes: one or more DRBs carry configuration information;
The first bearer context modification request message includes a first bearer list requesting establishment and/or a second bearer list requesting modification, the first bearer list includes one or more DRB bearer configuration information, and the second bearer list includes: one or more DRBs carry configuration information, bearers of the UDC to be turned off, bearers of the UDC to be released.
5. The method of maintaining data compression continuity according to claim 3, wherein each DRB bearer configuration information comprises at least the following information:
1) The DRB mark is a value of an integer type;
2) SDT bearing type indication information, enumeration type, and SDT bearing when the value is yes, supporting small data packet compression of the terminal in the RRC inactive state;
3) PDCP configuration information including at least the following information:
the PDCP reestablishment indication information enumerates types, and indicates that the PDCP entity of the DRB needs to be reestablished when the value is yes, and the PDCP reestablishment information is carried only when the UDC configuration of the DRB needs to be deleted;
4) UDC configuration information, the UDC configuration information including at least the following information:
(1) UDC decompresses the buffer size, enumerates the type, and takes the value including at least one of: 2048 bytes, 4096 bytes, and 8912 bytes;
(2) Dictionary information, enumeration type, and value including at least one of the following: a SIP-SID dictionary, a custom dictionary;
(3) UDC continuity indication information: and (3) enumerating the types, wherein when the value is yes, the PDCP entity can continue or restart the uplink data compression function in the PDCP reestablishment process.
6. The method of maintaining data compression continuity as recited in claim 5, further comprising:
if the first base station user plane entity finds that the UDC configuration is contained in the PDCP configuration carried by the first bearer context modification request message after receiving the first bearer context establishment request message from the first base station control plane entity and the first base station user plane supports the UDC configuration, configuring an uplink data compression function of a corresponding DRB bearer by adopting related parameters, and returning a first bearer context establishment response message to the first base station control plane entity;
if the first base station user plane entity finds that the UDC configuration is contained in the PDCP configuration carried by the first bearer context modification request message after receiving the first bearer context modification request message from the first base station control plane entity, and the first base station user plane supports the UDC configuration, configuring an uplink data compression function of a corresponding DRB bearer by adopting related parameters, and returning a first bearer context modification response message to the first base station control plane entity.
7. The method of maintaining data compression continuity as recited in claim 6, further comprising:
the first base station user plane entity performs bearer configuration by:
checking whether the bearer configuration information of each DRB identifier carries UDC configuration information or not in a bearer list requested to be released, and if so, releasing the bearer corresponding to the DRB identifier;
checking whether PDCP configuration information in the bearer configuration information of each bearer carries UDC configuration information or not in a bearer list requested to be modified, and if the first base station user plane entity supports the UDC capability, configuring an uplink data compression function for the bearer; if the number of configured uplink data compression bearers exceeds the preset UDC bearer upper limit value, determining that the bearer modification fails, and generating a failure cause value, wherein the failure cause value is used for indicating that the number of UDC bearers exceeds the preset UDC bearer upper limit value or that PDCP bearer configuration cannot be supported; if the configuration information of any one bearer with configured UDC function carries PDCP reestablishment instruction information, all data in the bearer, decompression caches and dictionary information are emptied, dictionary information and decompression caches are reconfigured according to the carried UDC configuration information, wherein if no dictionary is configured in the dictionary information, the size of the UDC decompression caches is set to 0; if the dictionary information is configured with a dictionary, configuring the UDC decompression buffer size according to the dictionary information;
Checking whether PDCP configuration information in the bearer configuration information of each bearer carries UDC configuration information or not in a bearer list established by the request, and if the first base station user plane entity supports the UDC capability, configuring an uplink data compression function for the bearer; if the number of configured uplink data compression bearers exceeds the preset UDC bearer upper limit value, determining that the bearer establishment fails, and generating a failure reason value, wherein the failure reason value is used for indicating that the number of UDC bearers exceeds the preset UDC bearer upper limit value or that PDCP bearer configuration cannot be supported.
8. The method for maintaining data compression continuity according to claim 7, wherein the first bearer context setup response message or the first bearer context modification response message includes: a bearer configuration success information list or a bearer configuration failure information list;
the successful information list of bearer configuration is used for indicating one or more data bearers successfully configured in the bearer list requested to be established or modified;
the bearer configuration failure information list is used to indicate one or more data bearers that cannot be configured in the bearer list that is requested to be established or modified.
9. The method for maintaining data compression continuity according to claim 8, wherein the bearer configuration success information list includes:
An identification of one or more data bearers successfully configured;
the bearer configuration failure information list includes: an identification of one or more data bearers that cannot be configured and a failure reason for each data bearer, the failure reason including: the number of UDC bearers exceeds a preset UDC bearer upper limit or PDCP bearer configuration cannot be supported.
10. The method of maintaining data compression continuity as recited in claim 7, further comprising:
after receiving a first bearer context establishment response message or a first bearer context modification response message from the first base station user plane entity, the first base station control plane entity determines a configuration result of the bearer which is requested to be established or modified in the first base station user plane entity;
the first base station control plane entity generates a first RRC reconfiguration message sent to the terminal according to the configuration result, and sends the established or modified bearer configuration information to the terminal through the first RRC reconfiguration message, wherein the bearer configuration information carried in the first RRC reconfiguration message comprises: UDC configuration information, wherein the bearer in the configuration result and the bearer in the first RRC reconfiguration message have a mapping relation;
for a bearer which needs to be added and configured as a UDC, placing a DRB identifier of the bearer in a DRB establishment list in an RRC message;
For the bearer which needs to be modified into the existing bearer and is configured into the UDC, the bearer DRB identifier is placed in a DRB release list and a DRB establishment list in an RRC message, and the sum of the number of the bearer which is configured into the UDC by the terminal after RRC reconfiguration and the number of the uplink data compression bearers which are currently activated and not released is ensured to be not more than a preset UDC bearer upper limit value.
11. The method for maintaining data compression continuity according to claim 10, wherein the first RRC reconfiguration message includes at least the following information:
1) A DRB release list comprising: one or more DRB identifiers for deleting the UDC configuration information;
2) The DRB builds and modifies a list comprising: one or more DRB configuration information, each DRB configuration information comprising at least:
(1) a DRB mark;
(2) UDC decompresses the buffer size, enumerates the type, and takes the value including at least one of: 2048 bytes, 4096 bytes, and 8912 bytes;
(3) dictionary information: the enumeration type, the value includes at least one of the following: SIP-SID dictionary, custom dictionary.
12. The method for maintaining data compression continuity according to claim 10, characterized in that after the first base station control plane entity sends the successfully established or modified bearer configuration information to the terminal through the first RRC reconfiguration message, the method further comprises:
The terminal performs configuration and reconfiguration of the UDC by:
for each DRB identifier in the DRB release list, deleting all configuration information of the corresponding DRB, and recording the number of UDC bearers required to be released as T1;
for each bearer needing to be configured in the UDC in the DRB establishment or modification list, configuring the size of a decompression cache and dictionary information of the UDC, setting all initial information in the cache to 0, and recording the number of the UDC bearers needing to be established as T2;
recording that the number of the established UDC bearers is T0 before the terminal receives the first RRC reconfiguration message, and when the value of T0-T1+T2 does not exceed the preset UDC bearer upper limit value or one established DRB mark is not added or modified directly under the condition of not being released, determining that the UDC configuration of the bearers is successful, and generating a first RRC reconfiguration confirmation message; when the value of T0-T1+T2 exceeds the preset UDC bearing upper limit value or an established DRB mark is generated, the UDC configuration of the bearing is determined to fail, and a first RRC reconfiguration failure message is generated.
13. The method of maintaining data compression continuity as recited in claim 1, further comprising:
The first base station control plane entity determines that a small data packet transmission bearing which needs to be suspended when the terminal enters an inactive state, and indicates the first base station user plane entity to trigger a bearing suspension process through a second bearing context modification request message, wherein the second bearing context modification request message at least comprises the following information:
bearing suspension indication information: the enumeration type at least comprises the following values: bearer suspension, bearer restoration, and small packet transmission restoration.
14. The method of maintaining data compression continuity as recited in claim 13, further comprising:
after receiving the second bearer context modification request message, the first base station user plane entity suspends all bearers according to the suspension indication carried in the bearer suspension indication message, and for the configured UDC bearers, continues to maintain the preconfigured decompression buffer and dictionary information during suspension, does not perform any operation of clearing or resetting to 0 for the UDC decompression buffer and dictionary, generates a second bearer context modification response message, and sends the second bearer context modification response message to the first base station control plane entity.
15. The method of maintaining data compression continuity as recited in claim 14, further comprising:
After receiving the second bearer context modification response message, the first base station control plane entity determines an uplink data compression application area of the terminal according to the preconfiguration information, and generates a second RRC reconfiguration message sent to the terminal, where the second RRC reconfiguration message is used for indicating that the terminal keeps the uplink compression capability of the small data packet transmission bearer when entering the RRC inactive state.
16. The method for maintaining data compression continuity according to claim 15, wherein the second RRC reconfiguration message includes: suspending configuration information;
the suspension configuration information includes at least the following information:
the SDT bearing list comprises one or more SDT bearing identifiers, and each SDT bearing identifier is a value of an integer type;
the uplink data compression continuity indication information is of an enumeration type, and takes the value of a cell or a radio access network notification area RNA.
17. The method of maintaining data compression continuity as recited in claim 15, further comprising:
after receiving the second RRC reconfiguration message, the terminal configures related bearers according to the following procedures, and feeds back a second RRC reconfiguration confirmation message to the first base station:
if the second RRC reconfiguration message contains the suspension configuration information, further judging whether the suspension configuration information contains the SDT bearer list or not;
If the suspension configuration information contains the SDT bearer list, storing the corresponding DRB identification, and determining the bearer of the corresponding DRB identification as a support terminal to transmit small data packets in an RRC non-excited state;
judging whether the suspension configuration information contains uplink data compression continuity indication information or not;
if the suspension configuration information contains the uplink data compression continuity indication information, all bearers which are supported in an SDT state and configured with UDCs are configured, the uplink data compression configuration is kept when a small data packet is adopted for transmission, the configured decompression cache and dictionary information are kept continuously, and the configured uplink data compression applicable area is stored;
if the suspension configuration information does not contain the uplink data compression continuity indication information, all bearers supporting the SDT state and configured with the UDC are not transmitted in an uplink data compression mode when the terminal is in an inactive state, and the configured decompression buffer memory and dictionary information are emptied.
18. The method of maintaining data compression continuity as recited in claim 17, further comprising:
if the suspension configuration information does not contain the SDT bearer list, determining that the bearer of the corresponding DRB identifier does not support the transmission of the small data packet when the terminal is in the RRC non-activated state.
19. The method of maintaining data compression continuity as recited in claim 1, further comprising:
when the SDT of the terminal bears an uplink data packet to be sent, caching the uplink data packet to be sent in an application layer, and indicating an access layer to check whether a cell currently resided in is in a preconfigured uplink data compression applicable area;
if the access layer finds that the cell where the access layer resides is in a preconfigured uplink data compression applicable area, the access layer instructs the application layer to compress uplink data, the uplink data packet buffered by the application layer is sent to a PDCP layer of the terminal, the uplink data packet buffered by the application layer is sent to a compression buffer according to preconfigured dictionary information, after data compression is completed, the uplink data packet is sent to an MAC layer of the terminal, and when the data volume of the uplink data packet reaches a preset data volume threshold value, a subsequent sending operation is triggered;
if the access layer finds that the cell where the cell resides is not in the preconfigured uplink data compression application area, the application layer informs the access layer of the uplink data packet to be sent, and the access layer does not perform uplink data compression operation when sending the uplink data packet.
20. The method of maintaining data compression continuity according to claim 1, wherein the second base station is different from the first base station, the method further comprising:
After receiving the RRC connection restoration request message and the uplink data packet sent by the terminal, if no user context information of the terminal is found, the second base station caches the received uplink data packet in a MAC layer of the second base station, and sends a user context acquisition request message to a first base station control plane entity, where the user context acquisition request message includes a cell identifier where the terminal currently resides, a downlink channel address, and SDT indication information.
21. The method for maintaining data compression continuity according to claim 20, wherein said user context acquisition request message further comprises: SDT side information, the SDT side information comprising: one or more transmissions.
22. The method of maintaining data compression continuity as recited in claim 20, further comprising:
the first base station control plane entity checks whether a cell where the terminal currently resides is in a preconfigured uplink data compression applicable area;
if the first base station control plane entity finds that the cell where the terminal currently resides is located in a preconfigured uplink data compression applicable area, determining that the UDC transmission bearer is configured to continue to perform uplink data decompression operation by adopting the existing compression cache and dictionary information, and returning a part of user context transfer request message to the second base station;
And if the first base station control plane entity finds that the cell where the terminal currently resides is not in the preconfigured uplink data compression applicable area, sending a user context acquisition response message to the second base station.
23. The method for maintaining data compression continuity according to claim 22, wherein said partial user context transfer request message comprises:
1) A second base station allocates an identifier for the user on a base station interface;
2) The first base station locates the user allocated mark on the base station interface;
3) The SDT bearer setup list includes: one or more SDT bearer lists, each SDT bearer list comprising:
(1) a DRB list;
(2) uplink user plane address information on an interface between base stations;
(3) RLC bearer configuration information of the DRB;
(4) QOS information of the DRB;
(5) RLC mode;
(6) SN length of RLC;
(7) slice configuration information.
24. The method for maintaining data compression continuity according to claim 22, wherein said user context acquisition response message comprises:
1) A second base station allocates an identifier for the user on a base station interface;
2) The first base station locates the user allocated mark on the base station interface;
3) A DRB identification list comprising one or more DRB configuration information, each DRB configuration information comprising information such that:
(1) The logic channel identification is a value of an integer type;
(2) RLC layer configuration information;
(3) MAC layer configuration information;
(4) PDCP layer configuration information.
25. The method of maintaining data compression continuity as recited in claim 22, further comprising:
if the second base station receives the partial user context transfer request message, returning a partial user context transfer response message, wherein the partial user context transfer response message comprises an SDT data forwarding DRB identification list, and the SDT data forwarding DRB identification list comprises: one or more DRB configuration information, each DRB configuration information comprising information such as:
(1) a DRB mark;
(2) UDC indication information, enumeration type, when the value is yes, the DRB is configured for UDC;
(3) a logic channel identifier, wherein the value is an integer type numerical value;
(4) downlink user plane address information of interfaces between base stations.
26. The method of maintaining data compression continuity as recited in claim 22, further comprising:
after receiving the partial user context transfer request message, the first base station control plane entity sends a third bearer context modification request message to the first base station user plane entity, where the third bearer context modification request message is used to request to resume data reception, and the third bearer context modification request message includes the following information:
1) The carrying suspending indication information, the enumeration type and the value at least comprise: bearer suspension, bearer recovery and small data packet transmission recovery;
2) A downstream channel address comprising: IP address and port address;
3) UDC continuity indication information: and the Boolean type is used for indicating that all bearers configured as SDT bearers and UDC are configured to restore the uplink data compression continuity maintaining function when the value is yes.
27. The method of maintaining data compression continuity as recited in claim 26, further comprising:
after receiving the third bearer context modification request message, the first base station user plane entity restores the small data packet transmission bearer of the terminal according to the small data packet transmission restoration instruction information, and when the value of the UDC continuity instruction information is yes, determines whether the bearer restoration of the configured UDC adopts preconfigured cache information and dictionary information according to the second bearer configuration information; if not, the preconfigured cache information and dictionary information are cleared;
the first base station user plane entity distributes the address information for receiving the uplink data for each bearing.
28. The method of maintaining data compression continuity as recited in claim 27, further comprising:
The first base station user plane entity sends a third bearer context modification response message to the first base station control plane entity to inform the first base station control plane entity that the bearer configuration has been completed.
29. The method for maintaining data compression continuity according to claim 28, wherein the third bearer context modification response message includes information as follows:
1) The successfully configured bearer list comprises one or more identifiers of SDT bearers;
2) The uplink carried receiving address information comprises: IP address and port address.
30. The method of maintaining data compression continuity as recited in claim 29, further comprising:
after receiving the third bearer context modification response message, the first base station control plane entity sends the uplink bearer receiving address information to the second base station through the context acquisition response message, and when the first base station and the second base station are the same base station, the first base station control plane entity sends the uplink bearer receiving address information to the first base station separation entity.
31. The method of maintaining data compression continuity as recited in claim 30, further comprising:
And after receiving the third bearing context modification response message, the second base station sends the cached uplink data to the user plane entity of the first base station according to the received address information of the uplink bearing.
32. The method of maintaining data compression continuity as recited in claim 31, further comprising:
and the first base station user plane entity completes the decompression operation of the uplink data according to the preconfigured cache information and dictionary information and completes the updating operation of the cache information and the dictionary information.
33. A base station, comprising: a base station control plane entity and a base station user plane entity;
the base station control plane entity is configured to instruct the first base station user plane entity to configure or modify uplink data compression UDC configuration information of the bearer through a bearer context establishment request or a bearer context modification request message, and instruct the first base station user plane entity to suspend the UDC bearer when the terminal enters an RRC inactive state, and notify one or more bearer preconfigured UDC applicable areas in the terminal through an air interface message;
the base station user plane entity is used for configuring or modifying Uplink Data Compression (UDC) configuration information of a bearer, and acquiring the UDC bearer needing to be suspended when the terminal enters an RRC inactive state; when the terminal is in an RRC inactive state, the terminal reserves UDC configuration information of a suspended UDC bearer, and when the terminal has small data packets carried by a small data packet SDT in a preconfigured UDC applicable area and needs to be transmitted, the reserved UDC configuration information is adopted to carry out uplink compression operation on the small data packets to be transmitted, the compressed small data packets and an RRC connection recovery request message are transmitted to a second base station, and the second base station is a base station of the terminal requesting RRC connection recovery;
The base station control plane entity is further configured to determine that the SDT is carried in a preconfigured uplink data compression applicable area after receiving the context restoration request message of the second base station, and instruct a restoration mode of uplink data compression of the user plane entity of the first base station; the first base station user plane entity is further configured to decompress a small data packet sent by the terminal based on the reserved UDC configuration information.
34. A terminal, comprising: an uplink data compression configuration information acquisition module and an uplink small data packet compression continuity maintenance module;
the uplink data compression configuration information acquisition module is used for acquiring one or more bearing preconfigured UDC applicable areas notified by the first base station control plane entity through an air interface message; the first base station control plane entity indicates the first base station user plane entity to configure or modify the Uplink Data Compression (UDC) configuration information of the bearer through a bearer context establishment request or a bearer context modification request message;
the uplink small data packet compression continuity maintaining module is used for reserving UDC configuration information of a suspended UDC bearer when the terminal is in an RRC inactive state, and performing uplink compression operation on the small data packet to be transmitted by adopting the reserved UDC configuration information when the small data packet SDT bearer of the terminal in a preconfigured UDC applicable area needs to be transmitted, and transmitting the compressed small data packet and an RRC connection restoration request message to a second base station, wherein the second base station is a base station of the terminal requesting RRC connection restoration;
And after receiving the context restoration request message of the second base station, the first base station user plane entity determines that the SDT is born in a preconfigured uplink data compression applicable area, and indicates a restoration mode of uplink data compression of the first base station user plane entity, so that the first base station user plane entity decompresses the small data packet sent by the terminal based on the reserved UDC configuration information.
35. A communication system, comprising: the method comprises the steps that a first base station where a terminal is currently resident and a second base station where the terminal requests RRC connection recovery; the first base station includes: a first base station control plane entity and a first base station user plane entity;
the terminal is used for acquiring one or more pre-configured UDC applicable areas which are informed by a first base station control surface entity through an air interface message, and carrying out uplink compression operation on a small data packet to be sent by adopting reserved UDC configuration information when the small data packet SDT is born by the terminal in the pre-configured UDC applicable areas and needs to be sent, and sending the compressed small data packet and an RRC connection restoration request message to a second base station, wherein the second base station is a base station of the terminal for requesting RRC connection restoration;
The first base station user plane entity is used for configuring or modifying uplink data compression UDC configuration information of a bearer;
the first base station control plane entity is configured to instruct the first base station user plane entity to configure or modify uplink data compression UDC configuration information of the bearer through a bearer context establishment request or a bearer context modification request message, and instruct the first base station user plane entity to suspend the UDC bearer when the terminal enters an RRC inactive state, and notify one or more of the pre-configured UDC applicable areas of the bearer through an air interface message;
the first base station control plane entity is further configured to determine that the SDT is carried in a preconfigured uplink data compression applicable area after receiving the context restoration request message of the second base station, and instruct a restoration mode of uplink data compression of the first base station user plane entity; the first base station user plane entity is further configured to decompress a small data packet sent by the terminal based on the reserved UDC configuration information.
36. A computer readable storage medium having stored thereon a computer program, wherein the computer program when executed by a processor implements the method of maintaining data compression continuity of any one of claims 1 to 32.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210435223.5A CN116980973A (en) | 2022-04-24 | 2022-04-24 | Method, base station, terminal, system and medium for maintaining data compression continuity |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210435223.5A CN116980973A (en) | 2022-04-24 | 2022-04-24 | Method, base station, terminal, system and medium for maintaining data compression continuity |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116980973A true CN116980973A (en) | 2023-10-31 |
Family
ID=88471883
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210435223.5A Pending CN116980973A (en) | 2022-04-24 | 2022-04-24 | Method, base station, terminal, system and medium for maintaining data compression continuity |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116980973A (en) |
-
2022
- 2022-04-24 CN CN202210435223.5A patent/CN116980973A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP6787459B2 (en) | Wireless terminal | |
| JP2021073823A (en) | Method and apparatus for reconfiguring bearer | |
| US20220225456A1 (en) | Radio access network node, radio terminal, and methods therefor | |
| JP7343652B2 (en) | Data processing methods, terminal devices, base stations, programs and communication systems | |
| JP2019534619A (en) | COMMUNICATION METHOD, DEVICE, AND SYSTEM | |
| WO2019153928A1 (en) | Rrc state transition method, terminal, cu, du, and computer-readable storage medium | |
| CN114208137B (en) | Compression and decompression method and device for Ethernet frame header | |
| KR20200004386A (en) | Communication method and device | |
| KR20200032177A (en) | Communication devices, infrastructure equipment, communication systems and methods | |
| EP4007342A1 (en) | Master node, secondary node, and method for same | |
| WO2020001256A1 (en) | Data transmission method and device | |
| EP3582576B1 (en) | Method and device for configuring gtp transmission channel and storage medium | |
| CN111757418B (en) | Data transmission method and device and wireless access network node | |
| CN112368976B (en) | Terminal and method for performing group communication | |
| CN116980973A (en) | Method, base station, terminal, system and medium for maintaining data compression continuity | |
| WO2010139215A1 (en) | Method, system and evolved node b for implementing service release | |
| CN112702765B (en) | Data transmission method, device, equipment and storage medium | |
| CN111132241B (en) | Communication method, mobility management entity, user equipment and serving gateway | |
| WO2016169188A1 (en) | Dedicated bearer modification method and system, gateway, terminal and storage medium | |
| CN111542094B (en) | RRC connection reestablishment method, RRC connection recovery method, computer-readable storage medium, and base station | |
| CN114071589B (en) | Link switching indication method, device, apparatus and storage medium | |
| CN114630355B (en) | Fault recovery method, device, equipment and storage medium based on core network | |
| CN117395674A (en) | Method and system for transmitting non-activated uplink small data, base station and terminal | |
| CN111278139A (en) | Method, device and storage medium for managing PDU session | |
| CN113141675A (en) | RRC connection reconfiguration method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |