CN112469052A - Slice information reporting method and device - Google Patents
Slice information reporting method and device Download PDFInfo
- Publication number
- CN112469052A CN112469052A CN201910866188.0A CN201910866188A CN112469052A CN 112469052 A CN112469052 A CN 112469052A CN 201910866188 A CN201910866188 A CN 201910866188A CN 112469052 A CN112469052 A CN 112469052A
- Authority
- CN
- China
- Prior art keywords
- slice
- terminal
- reporting
- nas
- information
- 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.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/02—Arrangements for optimising operational condition
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0055—Transmission or use of information for re-establishing the radio link
- H04W36/0079—Transmission or use of information for re-establishing the radio link in case of hand-off failure or rejection
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The invention provides a slice information reporting method and device, and belongs to the technical field of wireless communication. The slice information reporting method is applied to a terminal and comprises the following steps: and if the slice is unavailable, the radio resource control RRC layer of the terminal sends a reason value of the unavailable slice to the non-access stratum NAS. Through the technical scheme of the invention, the user can know the reason why the slice is unavailable, and further can take corresponding measures to improve the channel quality.
Description
Technical Field
The present invention relates to the field of wireless communication technologies, and in particular, to a method and an apparatus for reporting slice information.
Background
In the related art handover process, a source base station sends a handover preparation message to a target base station, and the target base station performs admission control and replies a handover command. If the target base station does not support the slice in operation in the switching process, the slice is directly rejected, so that service interruption is caused, and the service experience of a user is influenced.
At this time, although the Radio Resource Control (RRC) layer may know that the Data Resource Bearer (DRB) is released due to handover, the terminal may only sense that the currently running slice is degraded or released, and the terminal does not know what is degraded or released, which may seriously affect the user experience.
Disclosure of Invention
The technical problem to be solved by the present invention is to provide a method and an apparatus for reporting slice information, which enable a user to know the reason why a slice is unavailable, and further to take corresponding measures to improve channel quality.
To solve the above technical problem, embodiments of the present invention provide the following technical solutions:
the embodiment of the invention provides a slice information reporting method, which is applied to a terminal and comprises the following steps:
and if the slice is unavailable, the radio resource control RRC layer of the terminal sends a reason value of the unavailable slice to the non-access stratum NAS.
Optionally, the slice unavailable comprises at least one of:
the current running slice of the terminal is released;
the QoS of the slice currently operated by the terminal is returned;
the slice currently running by the terminal is rolled back to the default slice.
Optionally, the value of the reason for the slice being unavailable comprises at least one of: a cause value of slice rollback, a cause value of slice release, and a cause value of slice failure.
Optionally, the cause value comprises at least one of:
poor channel quality; the base station does not support; slice congestion.
Optionally, the method specifically includes at least one of:
if the situation that the QoS of the slice is reduced or the bearing is released due to the fact that multiple RLC layer retransmissions and/or MAC layer HARQ retransmissions occur is detected, the RRC layer of the terminal sends a slice rollback reason value to the NAS to be the channel quality difference;
if an RRC reconfiguration message carrying a signaling for releasing the bearer of the network side equipment is received, the RRC layer of the terminal sends a reason value for the slice rollback to the NAS, wherein the reason value is not supported by the base station;
and if the slice congestion information of the network side equipment is received, the RRC layer of the terminal sends the slice back-off reason value to the NAS to be the slice congestion.
Optionally, the method further comprises:
and if receiving the slice congestion relieving information of the network side equipment, the RRC layer of the terminal sends a slice available indication to the NAS, wherein the slice available indication carries a slice identifier.
Optionally, the method further comprises:
notifying an end user of the cause value.
The embodiment of the present invention further provides a device for reporting slice information, which is applied to a terminal, and includes:
and the sending module is positioned in a Radio Resource Control (RRC) layer of the terminal and used for sending the reason value that the slice is unavailable to a non-access stratum (NAS) if the slice is unavailable.
Optionally, the slice unavailable comprises at least one of:
the current running slice of the terminal is released;
the QoS of the slice currently operated by the terminal is returned;
the slice currently running by the terminal is rolled back to the default slice.
Optionally, the value of the reason for the slice being unavailable comprises at least one of: a cause value of slice rollback, a cause value of slice release, and a cause value of slice failure.
Optionally, the cause value comprises at least one of:
poor channel quality; the base station does not support; slice congestion.
Optionally, the sending module is specifically configured to execute at least one of the following:
if the fact that the QoS of the slice is reduced or the bearing is released due to the fact that multiple RLC layer retransmissions and/or MAC layer HARQ retransmissions occur is detected, the reason value for sending the slice rollback to the NAS is the poor channel quality;
if an RRC reconfiguration message carrying a signaling for releasing the bearer of the network side equipment is received, sending a reason value of the slice rollback to the NAS, wherein the reason value is not supported by the base station;
and if the slice congestion information of the network side equipment is received, sending a slice rollback reason value to the NAS to be the slice congestion.
Optionally, the sending module is further configured to send a slice availability indication to the NAS if slice congestion mitigation information of the network side device is received, where the slice availability indication carries a slice identifier.
Optionally, the sending module is further configured to notify the end user of the cause value.
An embodiment of the present invention further provides a device for reporting slice information, including: the slice information reporting method comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the computer program realizes the steps of the slice information reporting method when being executed by the processor.
An embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the steps in the slice information reporting method described above are implemented.
The embodiment of the invention has the following beneficial effects:
in the above scheme, when the network degrades or releases the slice of the terminal for some reasons, the RRC layer of the terminal may know the reason why the slice is unavailable, but the NAS cannot know the reason why the slice is unavailable, and the unavailable slice with unknown reason will affect the user experience.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments of the present invention will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without inventive labor.
Fig. 1 is a schematic flow chart of a slice information reporting method according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of a device for reporting slice information according to an embodiment of the present invention.
Detailed Description
In order to make the technical problems, technical solutions and advantages to be solved by the embodiments of the present invention clearer, the following detailed description will be given with reference to the accompanying drawings and specific embodiments.
Exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention can be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.
The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus. In the description and in the claims "and/or" means at least one of the connected objects.
The techniques described herein are not limited to Long Term Evolution (LTE)/LTE Evolution (LTE-Advanced) systems, and may also be used for various wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" are often used interchangeably. CDMA systems may implement Radio technologies such as CDMA2000, Universal Terrestrial Radio Access (UTRA), and so on. UTRA includes Wideband CDMA (Wideband Code Division Multiple Access, WCDMA) and other CDMA variants. TDMA systems may implement radio technologies such as Global System for Mobile communications (GSM). The OFDMA system may implement radio technologies such as Ultra Mobile Broadband (UMB), evolved-UTRA (E-UTRA), IEEE 802.11(Wi-Fi), IEEE 802.16(WiMAX), IEEE 802.20, Flash-OFDM, etc. UTRA and E-UTRA are parts of the Universal Mobile Telecommunications System (UMTS). LTE and higher LTE (e.g., LTE-A) are new UMTS releases that use E-UTRA. UTRA, E-UTRA, UMTS, LTE-A, and GSM are described in documents from an organization named "third Generation Partnership Project" (3 GPP). CDMA2000 and UMB are described in documents from an organization named "third generation partnership project 2" (3GPP 2). The techniques described herein may be used for both the above-mentioned systems and radio technologies, as well as for other systems and radio technologies. However, the following description describes the NR system for purposes of example, and NR terminology is used in much of the description below, although the techniques may also be applied to applications other than NR system applications.
The following description provides examples and does not limit the scope, applicability, or configuration set forth in the claims. Changes may be made in the function and arrangement of elements discussed without departing from the spirit and scope of the disclosure. Various examples may omit, substitute, or add various procedures or components as appropriate. For example, the described methods may be performed in an order different than described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.
In the related art handover process, a source base station sends a handover preparation message to a target base station, and the target base station performs admission control and replies a handover command. If the target base station does not support the slice in operation in the switching process, the slice is directly rejected, so that service interruption is caused, and the service experience of a user is influenced.
At this time, although the Radio Resource Control (RRC) layer may know that the Data Resource Bearer (DRB) is released due to handover, the terminal may only sense that the currently running slice is degraded or released, and the terminal does not know what is degraded or released, which may seriously affect the user experience.
In order to solve the above problem, embodiments of the present invention provide a method and an apparatus for reporting slice information, which enable a user to know the reason why a slice is unavailable, and further to take corresponding measures to improve channel quality.
An embodiment of the present invention provides a method for reporting slice information, which is applied to a terminal, and as shown in fig. 1, the method includes:
step 101: and if the slice is unavailable, the radio resource control RRC layer of the terminal sends a reason value of the unavailable slice to the non-access stratum NAS.
In this embodiment, when a network degrades or releases a slice of a terminal for some reasons, an RRC layer of the terminal may know the reason why the slice is unavailable, but an NAS cannot know the reason why the slice is unavailable, and the unavailable slice with an unknown reason will affect user experience.
When the terminal operates slice 1 in the connected state, slice 1 currently operating may be released, or the quality of service (QoS) of slice 1 may be rolled back, or slice 1 may be rolled back to a default slice, due to poor current channel quality, or the target base station does not support the slice. I.e. the slice is not available comprising at least one of:
the current running slice of the terminal is released;
the QoS of the slice currently operated by the terminal is returned;
the slice currently running by the terminal is rolled back to the default slice.
The slice fallback means that the original QoS of a slice cannot be continuously satisfied, and has the same or similar meaning as the slice downgrading, and the slice release means that the Data Radio Bearer (DRB) of the slice cannot be continuously provided with a service for the slice and is released.
When this occurs, the RRC layer of the terminal (UE) notifies the NAS of a cause value of slice release or backoff. I.e. the reason value that the slice is not available comprises at least one of: a cause value of slice rollback, a cause value of slice release, and a cause value of slice failure.
Optionally, the cause value comprises at least one of:
poor channel quality; the base station does not support; slice congestion.
Optionally, the method specifically includes at least one of:
if the situation that the QoS of the slice is reduced or the bearing is released due to the fact that multiple RLC layer retransmissions and/or MAC layer HARQ retransmissions occur is detected, the RRC layer of the terminal sends a slice rollback reason value to the NAS to be the channel quality difference;
if an RRC reconfiguration message carrying a signaling for releasing the bearer of the network side equipment is received, the RRC layer of the terminal sends a reason value for the slice rollback to the NAS, wherein the reason value is not supported by the base station;
and if the slice congestion information of the network side equipment is received, the RRC layer of the terminal sends the slice back-off reason value to the NAS to be the slice congestion.
The reason value is used for informing the NAS layer of the reason for the slice fallback or the slice release or the bearer release, and the NAS layer may inform the user of the information so that the user may select a corresponding operation, for example, the user moves into a cell coverage area to improve channel quality, or the user moves from a cell that does not support the slice to a cell that supports the slice, or the user manually selects a Network or a Public Land Mobile Network (PLMN).
In the cause value, 'poor channel quality' refers to that the downlink or uplink channel of the serving cell is poor, which causes multiple retransmissions of uplink or downlink data through a radio link control sublayer (RLC) or a media access control sublayer (MAC), or decoding failure, which causes phenomena such as increased time delay, increased error rate, and decreased QoS. Therefore, when the terminal detects that multiple RLC layer retransmissions and/or MAC layer Hybrid Automatic Repeat reQuest (HARQ) retransmissions occur, which results in QoS degradation or bearer release of the slice (the QoS includes at least one of error rate, delay, and rate), the RRC layer of the terminal reports the cause value of the slice backoff to the NAS layer as 'poor channel quality'.
In the cause value, 'base station does not support' means that the target cell does not support the slice in the handover process, and at this time, the terminal receives an RRC reconfiguration message sent to the terminal by the network side and includes a signaling for releasing the bearer. After receiving the information, the terminal may know that the bearer corresponding to the slice is released because the base station does not support the slice.
In the cause value, 'congestion' refers to that the network is congested, so that the QoS of the slice currently operated by the terminal is backed off. The network side may send congestion information to the terminal, where the congestion information is used to inform the terminal to release bearers due to network congestion or reduce QoS, and the congestion information may be simple indication information or backoff configuration, for example, to instruct the terminal to backoff for 30 seconds and then initiate the slice service. After the terminal receives the congestion information, the RRC of the terminal reports the reason value of the slice degradation to an upper layer (NAS) to be congestion. Because the QoS descending terminal can not be intuitively felt, the network side can reduce the scheduling of the terminal due to congestion, thereby causing the QoS to descend)
In addition, the base station may also send other cause values to the terminal, and the RRC of the terminal sends the cause values or equivalent information to the NAS, so that the user or system layer perceives the reason that the slice is unavailable.
Optionally, the method further comprises:
and if receiving the slice congestion relieving information of the network side equipment, the RRC layer of the terminal sends a slice available indication to the NAS, wherein the slice available indication carries a slice identifier. For example, when congestion of a Slice is relieved, the RRC layer notifies the NAS, and the Slice congestion relief or the current Slice service operates normally and carries Single Network Slice Selection Assistance Information (S-NSSAI) of the Slice.
Optionally, the method further comprises: notifying an end user of the cause value. Such as informing the end user of the cause value by voice prompt, or informing the end user of the cause value through the screen of the terminal, etc. The end user may also be informed to take corresponding measures to improve the channel quality, such as informing the end user to move to improve the channel quality or informing the end user to return to the slice coverage area.
An embodiment of the present invention further provides a device for reporting slice information, which is applied to a terminal, and as shown in fig. 2, the device includes:
a sending module 21, located in the radio resource control RRC layer of the terminal, configured to send a value of a cause of slice unavailability to a non-access stratum NAS if the slice unavailability occurs.
In this embodiment, when a network degrades or releases a slice of a terminal for some reasons, an RRC layer of the terminal may know the reason why the slice is unavailable, but an NAS cannot know the reason why the slice is unavailable, and the unavailable slice with an unknown reason will affect user experience.
Optionally, the slice unavailable comprises at least one of:
the current running slice of the terminal is released;
the QoS of the slice currently operated by the terminal is returned;
the slice currently running by the terminal is rolled back to the default slice.
Optionally, the value of the reason for the slice being unavailable comprises at least one of: a cause value of slice rollback, a cause value of slice release, and a cause value of slice failure.
Optionally, the cause value comprises at least one of:
poor channel quality; the base station does not support; slice congestion.
Optionally, the sending module 21 is specifically configured to execute at least one of the following:
if the fact that the QoS of the slice is reduced or the bearing is released due to the fact that multiple RLC layer retransmissions and/or MAC layer HARQ retransmissions occur is detected, the reason value for sending the slice rollback to the NAS is the poor channel quality;
if an RRC reconfiguration message carrying a signaling for releasing the bearer of the network side equipment is received, sending a reason value of the slice rollback to the NAS, wherein the reason value is not supported by the base station;
and if the slice congestion information of the network side equipment is received, sending a slice rollback reason value to the NAS to be the slice congestion.
Optionally, the sending module 21 is further configured to send a slice availability indication to the NAS if slice congestion mitigation information of the network side device is received, where the slice availability indication carries a slice identifier.
Optionally, the sending module 21 is further configured to notify the end user of the reason value. Such as informing the end user of the cause value by voice prompt, or informing the end user of the cause value through the screen of the terminal, etc. The end user may also be informed to take corresponding measures to improve the channel quality, such as informing the end user to move to improve the channel quality or informing the end user to return to the slice coverage area.
The slice information reporting apparatus of this embodiment can implement all the steps in the slice information reporting method in the above embodiments, and is not described herein again.
An embodiment of the present invention further provides a device for reporting slice information, including: the slice information reporting method comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the computer program realizes the steps of the slice information reporting method when being executed by the processor.
An embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the steps in the slice information reporting method described above are implemented.
It is to be understood that the embodiments described herein may be implemented in hardware, software, firmware, middleware, microcode, or any combination thereof. For a hardware implementation, the Processing units may be implemented within one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), general purpose processors, controllers, micro-controllers, microprocessors, other electronic units configured to perform the functions described herein, or a combination thereof.
For a software implementation, the techniques described herein may be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. The software codes may be stored in a memory and executed by a processor. The memory may be implemented within the processor or external to the processor.
The embodiments in the present specification are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, apparatus, or computer program product. Accordingly, embodiments of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
Embodiments of the present invention are described with reference to flowchart illustrations and/or block diagrams of methods, user terminal devices (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing user terminal device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing user terminal device, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing user terminal to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing user terminal device to cause a series of operational steps to be performed on the computer or other programmable user terminal device to produce a computer implemented process such that the instructions which execute on the computer or other programmable user terminal device provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While preferred embodiments of the present invention have been described, additional variations and modifications of these embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the embodiments of the invention.
It is further noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or user terminal that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or user terminal. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or user terminal device that comprises the element.
While the preferred embodiments of the present invention have been described, it will be understood by those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the invention as defined in the following claims.
Claims (10)
1. A slice information reporting method is applied to a terminal and comprises the following steps:
and if the slice is unavailable, the radio resource control RRC layer of the terminal sends a reason value of the unavailable slice to the non-access stratum NAS.
2. The method for reporting slice information according to claim 1, wherein the slice unavailability includes at least one of:
the current running slice of the terminal is released;
the QoS of the slice currently operated by the terminal is returned;
the slice currently running by the terminal is rolled back to the default slice.
3. The method for reporting slice information as claimed in claim 2, wherein the value of the reason for the slice unavailability comprises at least one of: a cause value of slice rollback, a cause value of slice release, and a cause value of slice failure.
4. The method for reporting slice information of claim 3, wherein the cause value comprises at least one of the following:
poor channel quality; the base station does not support; slice congestion.
5. The method for reporting slice information according to claim 4, wherein the method specifically includes at least one of:
if the situation that the QoS of the slice is reduced or the bearing is released due to the fact that multiple RLC layer retransmissions and/or MAC layer HARQ retransmissions occur is detected, the RRC layer of the terminal sends a slice rollback reason value to the NAS to be the channel quality difference;
if an RRC reconfiguration message carrying a signaling for releasing the bearer of the network side equipment is received, the RRC layer of the terminal sends a reason value for the slice rollback to the NAS, wherein the reason value is not supported by the base station;
and if the slice congestion information of the network side equipment is received, the RRC layer of the terminal sends the slice back-off reason value to the NAS to be the slice congestion.
6. The method for reporting slice information according to any one of claims 1 to 5, wherein the method further comprises:
and if receiving the slice congestion relieving information of the network side equipment, the RRC layer of the terminal sends a slice available indication to the NAS, wherein the slice available indication carries a slice identifier.
7. The method for reporting slice information according to any one of claims 1 to 5, wherein the method further comprises:
notifying an end user of the cause value.
8. The utility model provides a section information reporting device which characterized in that, is applied to the terminal, includes:
and the sending module is positioned in a Radio Resource Control (RRC) layer of the terminal and used for sending the reason value that the slice is unavailable to a non-access stratum (NAS) if the slice is unavailable.
9. A slice information reporting device is characterized by comprising: memory, processor and computer program stored on the memory and executable on the processor, the computer program, when executed by the processor, implementing the steps in the slice information reporting method according to any one of claims 1 to 7.
10. A computer-readable storage medium, having a computer program stored thereon, wherein the computer program, when being executed by a processor, implements the steps of the slice information reporting method according to any one of claims 1 to 7.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910866188.0A CN112469052B (en) | 2019-09-09 | 2019-09-09 | Slice information reporting method and device |
| PCT/CN2020/113966 WO2021047498A1 (en) | 2019-09-09 | 2020-09-08 | Slice information reporting method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910866188.0A CN112469052B (en) | 2019-09-09 | 2019-09-09 | Slice information reporting method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112469052A true CN112469052A (en) | 2021-03-09 |
| CN112469052B CN112469052B (en) | 2023-03-31 |
Family
ID=74807592
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910866188.0A Active CN112469052B (en) | 2019-09-09 | 2019-09-09 | Slice information reporting method and device |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN112469052B (en) |
| WO (1) | WO2021047498A1 (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2022206887A1 (en) * | 2021-03-31 | 2022-10-06 | 中国移动通信有限公司研究院 | Transmission method and apparatus, and device and readable storage medium |
| WO2023077464A1 (en) * | 2021-11-05 | 2023-05-11 | 北京小米移动软件有限公司 | Method and apparatus for a plurality of network slice admission control functions (nsacfs) to report slice state information |
| WO2023123355A1 (en) * | 2021-12-31 | 2023-07-06 | Oppo广东移动通信有限公司 | Information reporting method and apparatus, and device, storage medium and program product |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102469548A (en) * | 2010-11-05 | 2012-05-23 | 中兴通讯股份有限公司 | Access handling method, device and system |
| CN107071799A (en) * | 2017-02-16 | 2017-08-18 | 北京小米移动软件有限公司 | Network section collocation method and device, wireless access network RAN node and terminal |
| CN108293222A (en) * | 2015-11-30 | 2018-07-17 | 华为技术有限公司 | A kind of notification method and user equipment of system message |
| US20180288654A1 (en) * | 2017-03-29 | 2018-10-04 | Mei-Ju Shih | Wireless communication method and system for network slicing |
| US20180352491A1 (en) * | 2017-06-02 | 2018-12-06 | Fg Innovation Ip Company Limited | Methods, devices, and systems for service-driven mobility management |
| CN109195187A (en) * | 2018-08-03 | 2019-01-11 | 西安电子科技大学 | Handover network dicing method based on network slice server log file |
| CN109391648A (en) * | 2017-08-04 | 2019-02-26 | 华为技术有限公司 | It is a kind of to apply correlating method, device and the communication system being sliced with network |
| CN109819488A (en) * | 2017-11-20 | 2019-05-28 | 华为技术有限公司 | A kind of conversation switching method, equipment and system |
| US20190222367A1 (en) * | 2018-01-17 | 2019-07-18 | FG Innovation Company Limited | Cell (re)selection and uplink component carrier selection |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109474967B (en) * | 2017-01-25 | 2019-11-19 | 华为技术有限公司 | Communication means and communication device |
| US10820185B2 (en) * | 2017-05-08 | 2020-10-27 | Qualcomm Incorporated | Mobility between areas with heterogeneous network slices |
-
2019
- 2019-09-09 CN CN201910866188.0A patent/CN112469052B/en active Active
-
2020
- 2020-09-08 WO PCT/CN2020/113966 patent/WO2021047498A1/en active Application Filing
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102469548A (en) * | 2010-11-05 | 2012-05-23 | 中兴通讯股份有限公司 | Access handling method, device and system |
| CN108293222A (en) * | 2015-11-30 | 2018-07-17 | 华为技术有限公司 | A kind of notification method and user equipment of system message |
| CN107071799A (en) * | 2017-02-16 | 2017-08-18 | 北京小米移动软件有限公司 | Network section collocation method and device, wireless access network RAN node and terminal |
| US20180288654A1 (en) * | 2017-03-29 | 2018-10-04 | Mei-Ju Shih | Wireless communication method and system for network slicing |
| US20180352491A1 (en) * | 2017-06-02 | 2018-12-06 | Fg Innovation Ip Company Limited | Methods, devices, and systems for service-driven mobility management |
| CN109391648A (en) * | 2017-08-04 | 2019-02-26 | 华为技术有限公司 | It is a kind of to apply correlating method, device and the communication system being sliced with network |
| CN109819488A (en) * | 2017-11-20 | 2019-05-28 | 华为技术有限公司 | A kind of conversation switching method, equipment and system |
| US20190222367A1 (en) * | 2018-01-17 | 2019-07-18 | FG Innovation Company Limited | Cell (re)selection and uplink component carrier selection |
| CN109195187A (en) * | 2018-08-03 | 2019-01-11 | 西安电子科技大学 | Handover network dicing method based on network slice server log file |
Non-Patent Citations (3)
| Title |
|---|
| ""R2-1700594_NW slicing"", 《3GPP TSG_RAN\WG2_RL2》 * |
| CATT: "R3-182906 "TP for 38.423 on slice related cause value"", 《3GPP TSG_RAN\WG3_IU》 * |
| QUALCOMM INCORPORATED: "S2-174442 "TS 23.501 - Proposal for co-existence of network slices stemming from offline discussion."", 《3GPP TSG_SA\WG2_ARCH》 * |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2022206887A1 (en) * | 2021-03-31 | 2022-10-06 | 中国移动通信有限公司研究院 | Transmission method and apparatus, and device and readable storage medium |
| WO2023077464A1 (en) * | 2021-11-05 | 2023-05-11 | 北京小米移动软件有限公司 | Method and apparatus for a plurality of network slice admission control functions (nsacfs) to report slice state information |
| WO2023123355A1 (en) * | 2021-12-31 | 2023-07-06 | Oppo广东移动通信有限公司 | Information reporting method and apparatus, and device, storage medium and program product |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2021047498A1 (en) | 2021-03-18 |
| CN112469052B (en) | 2023-03-31 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107535012B (en) | Relay selection or reselection method, device and system | |
| KR102205265B1 (en) | Method and system for improving circuit switched fall back(csfb) performance | |
| CN112469052B (en) | Slice information reporting method and device | |
| US20150131619A1 (en) | Differentiated VoLTE Based on Dual Radio and DRVCC | |
| US9516694B2 (en) | Method and apparatus for inter radio access technology (IRAT) cell reselection | |
| US9445310B2 (en) | Mobile communication system, network device, and mobile communication method | |
| EP3503668A1 (en) | Link establishing method and device and wireless communication system | |
| US11509546B2 (en) | Method for feedback of streaming session | |
| KR20140018776A (en) | Method and apparatus for adjusting mobility parameter | |
| US20180109982A1 (en) | User equipment and network access method | |
| US9967814B2 (en) | Automatic tracking of mobile device camping failure to an access point | |
| US20040219921A1 (en) | Method of releasing a connection between a mobile user terminal and a network | |
| CN111165068B (en) | User equipment, network node and method for use therein | |
| CN111935853B (en) | Protocol data unit session state indication method, terminal device and storage medium | |
| CN113473440A (en) | Method and wireless communication device for idle mode mobility management | |
| US10070370B1 (en) | Apparatus, systems and methods for initiating a cell selection | |
| CN113411913B (en) | Communication method and terminal equipment | |
| EP2903388A1 (en) | Radio link failure | |
| CN112806049B (en) | Radio resource management measuring method, system, terminal device and storage medium | |
| CN112449386B (en) | Information record reporting method and device | |
| US20150094063A1 (en) | Devices and methods for facilitating optimized hand down operations in hybrid access terminals | |
| US10383169B2 (en) | Base station and terminal connection management method of base station | |
| KR102114954B1 (en) | Method of Release of UE connection and base-station operating the same | |
| CN115696479A (en) | Slice-based cell reselection method and related equipment | |
| CN115804148A (en) | Network switching method, device, equipment and storage medium |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |