Wireless communication system, base station, mobile station, and method of wireless communication
A base station includes a memory and a processor coupled to the memory and configured to transmit, when a state transition of a mobile station is performed, a first control signal to the mobile station, and perform control to simultaneously transmit the first control signal and a second control signal different from the first control signal to the mobile station when a first state transition, which causes a state of the mobile station to transfer from a first state to a second state, is performed, and then a second state transition, which causes the state of the mobile station to transfer from the second state to a third state, is performed.
Latest FUJITSU LIMITED Patents:
- Connection control device, communication system, and connection control method
- Contention window adjustment method and apparatus and communication system
- Method and apparatus for decentralized supervised learning in NLP applications
- Dynamic classification of time-series categorical data
- APPARATUS FOR IDENTIFYING ITEMS, METHOD FOR IDENTIFYING ITEMS AND ELECTRONIC DEVICE
This application is a continuation application of U.S. patent application Ser. No. 17/018,823 filed on Sep. 11, 2020, now pending, which is a continuation application of International Application PCT/JP2018/010318, filed on Mar. 15, 2018 and designating the U.S., the entire contents of each are incorporated herein by reference.
FIELDThe present disclosure relates to a wireless communication system, a base station, a mobile station, and a method of wireless communication.
BACKGROUNDIn current networks, the traffic of mobile terminals (smartphones, for example) occupies most of network resources. The traffic used by a mobile terminal (hereinafter, denoted as “a mobile station”) tends to increase in the future.
Meanwhile, in accordance with development of Internet of Things (IoT) services (traffic systems, smart meters, and monitoring systems for apparatuses and the like, for example), it is demanded to deal with services having various requirements. Given these circumstances, in next generation (the 5th generation mobile communication (5G), for example) communication standards, it is demanded for technologies to achieve higher data rate, larger capacity, and lower latency are demanded in addition to the 4th generation mobile communication (4G) standard technologies (Non Patent Document 1 to 11, for example). The next generation communication standards are technically under study by working groups of 3rd Generation Partnership Project (3GPP) (TSG-RAN WG1, TSG-RAN WG2, and the like, for example) (Non Patent Document 12 to 40, for example).
5G supports various kinds of services. 5G assumes support of many use cases classified into enhanced Mobile Broadband (eMBB), massive Machine Type Communications (MTC), and Ultra-Reliable and Low Latency Communications (URLLC), for example. In 5G, employment of New Radio Access Technology (RAT) is under study as a new communication technique. New RAT is denoted as “NR.” In Long Term Evolution (LTE), for example, a mobile station is called user equipment (UE), and a base station is called evolved Node B (eNB), whereas in NR, the base station is called 5G NB (a 5G base station) or gNB.
In a wireless communication system, Radio Resource Control (RRC) layer processing is executed. In the RRC layer processing, configuration, changing, releasing, and the like of connection between a wireless station (UE) and an opposite wireless station (gNB) are performed. In 3GPP, for example, an RRC connected mode and an RRC idle mode are specified as states of the RRC layer (Non Patent Document 9, for example). The RRC connected mode is a state in which data communication is able to be performed between the UE and the gNB, for example. The RRC idle mode is a state in which data communication is unable to be performed between the UE and the gNB, for example.
The UE transmits and receives an RRC message as a message about the state transition to and from the gNB when transitioning from the RRC idle mode to the RRC connected mode, for example. In this case, information on data communication is informed to the gNB and stored thereby by a message transmitted from the UE. The information on data communication includes information on the position of the UE, communication capability, various kinds of parameters, and the identifier (terminal ID) of the UE.
The UE, in the RRC connected mode, transmits and receives a non-access stratum (NAS) message to and from the gNB. The gNB transmits an RRC message as a message about the state transition to the UE when causing the UE to transition from the RRC connected mode to the RRC inactive mode, for example.
The UE, in the RRC inactive mode, can resume the RRC connected mode by transmitting a resume request to the gNB at the time of occurrence of data, for example. The UE transitions to the RRC inactive mode, for example, whereby the information on data communication is stored by the gNB, and thus the UE does not have to inform the information on data communication to the gNB at the time of resumption of the RRC connected mode.
-
- Non Patent Document 1: 3GPP TS36.211 V14.4.0, September 2017
- Non Patent Document 2: 3GPP TS36.212 V14.4.0, September 2017
- Non Patent Document 3: 3GPP TS36.213 V14.4.0, September 2017
- Non Patent Document 4: 3GPP TS36.214 V14.4.0, September 2017
- Non Patent Document 5: 3GPP TS36.300 V14.4.0, September 2017
- Non Patent Document 6: 3GPP TS36.321 V14.4.0,
- Non Patent Document 7: 3GPP TS36.322 V14.1.0, September 2017
- Non Patent Document 8: 3GPP TS36.323 V14.4.0, September 2017
- Non Patent Document 9: 3GPP TS36.331 V14.4.0, September 2017
- Non Patent Document 10: 3GPP TS36.413 V14.4.0, September 2017
- Non Patent Document 11: 3GPP TS36.423 V14.4.0, September 2017
- Non Patent Document 12: 3GPP TS37.324 V1.1.1, November 2017
- Non Patent Document 13: 3GPP TS37.340 V2.0.0, December 2017
- Non Patent Document 14: 3GPP TS36.425 V14.0.0, March 2017
- Non Patent Document 15: 3GPP TS38.201 V2.0.0, December 2017
- Non Patent Document 16: 3GPP TS38.202 V2.0.0, December 2017
- Non Patent Document 17: 3GPP TS38.211 V2.0.0, December 2017
- Non Patent Document 18: 3GPP TS38.212 V1.2.1, December 2017
- Non Patent Document 19: 3GPP TS38.213 V2.0.0,
- Non Patent Document 20: 3GPP TS38.214 V2.0.0, December 2017
- Non Patent Document 21: 3GPP TS38.215 V2.0.0, December 2017
- Non Patent Document 22: 3GPP TS38.300 V2.0.0, December 2017
- Non Patent Document 23: 3GPP TS38.321 V2.0.0, December 2017
- Non Patent Document 24: 3GPP TS38.322 V2.0.0, December 2017
- Non Patent Document 25: 3GPP TS38.323 V2.0.0, December 2017
- Non Patent Document 26: 3GPP TS38.331 V0.4.0, December 2017
- Non Patent Document 27: 3GPP TS38.401 V1.0.0, December 2017
- Non Patent Document 28: 3GPP TS38.410 V0.6.0, December 2017
- Non Patent Document 29: 3GPP TS38.413 V0.5.0, December 2017
- Non Patent Document 30: 3GPP TS38.420 V0.5.0, December 2017
- Non Patent Document 31: 3GPP TS38.423 V0.5.0, December 2017
- Non Patent Document 32: 3GPP TS38.470 V1.0.0,
- Non Patent Document 33: 3GPP TS38.473 V1.0.0, December 2017
- Non Patent Document 34: 3GPP TR38.801 V14.0.0, April 2017
- Non Patent Document 35: 3GPP TR38.802 V14.2.0, September 2017
- Non Patent Document 36: 3GPP TR38.803 V14.2.0, September 2017
- Non Patent Document 37: 3GPP TR38.804 V14.0.0, April 2017
- Non Patent Document 38: 3GPP TR38.900 V14.3.1, July 2017
- Non Patent Document 39: 3GPP TR38.912 V14.1.0, June 2017
- Non Patent Document 40: 3GPP TR38.913 V14.3.0, June 2017
- Non Patent Document 41: “New SID Proposal: Study on New Radio Access Technology”, NTT Docomo, RP-160671, 3GPP TSG RAN Meeting #71 Goteborg, Sweden, 7-10 Mar. 2016
According to an aspect of the embodiments, a base station includes: a memory; and a processor coupled to the memory and configured to: transmit, when a state transition of a mobile station is performed, a first control signal to the mobile station, and perform control to simultaneously transmit the first control signal and a second control signal different from the first control signal to the mobile station when a first state transition, which causes a state of the mobile station to transfer from a first state to a second state, is performed, and then a second state transition, which causes the state of the mobile station to transfer from the second state to a third state, is performed.
The object and advantages of the disclosure will be realized and attained by means of the elements and combinations particularly pointed out in the claims.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are not restrictive of the disclosure.
In 3GPP, discussions about introduction of the RRC inactive mode have just begun, and it has not been discussed so deeply. Thus, in 3GPP, when the RRC inactive mode is introduced, there is a possibility that some problems or malfunctions that have not been known in the world will occur. It is important whether a state transition delay can be reduced, for example. To reduce the state transition delay in particular, it is important to reduce the number of messages transmitted and received between the UE and the gNB. These have not been studied almost at all. Consequently, there have not been any methods that reduce the state transition delay as introduction of the RRC inactive mode.
In one aspect, the embodiments provide a wireless communication system, a base station, a mobile station, and a method of wireless communication capable of reducing the state transition delay.
The following describes embodiments of a wireless communication system, a mobile station, a base station, and a method of wireless communication disclosed by the present application in detail based on the accompanying drawings. The following embodiments do not limit the disclosed technology.
First Embodiment[Wireless Communication System]
The wireless communication apparatus 1 has a communication unit 11 and a controller 14.
The communication unit 11 performs wireless communication with the wireless communication apparatus 2. The communication unit 11 transmits and receives a control signal as a message to and from the wireless communication apparatus 2, for example.
Specifically, the communication unit 11 has a transmitter 12 and a receiver 13.
The transmitter 12, when a state transition of the wireless communication apparatus 2 is performed, transmits a first control signal as a message about the state transition to the wireless communication apparatus 2. The transmitter 12 transmits the first control signal to the wireless communication apparatus 2 when a first state transition, which causes the state of the wireless communication apparatus 2 to transfer from a first state to a second state, is performed, for example. The transmitter 12 transmits a second control signal as a message different from the first control signal to the wireless communication apparatus 2 when the state of the wireless communication apparatus 2 has transferred to the second state.
The receiver 13 receives the first control signal transmitted from the wireless communication apparatus 2 when the state transition of the wireless communication apparatus 2 is performed. The receiver 13 receives the first control signal transmitted from the wireless communication apparatus 2 when the first state transition is performed, for example. The receiver 13 receives the second control signal transmitted from the wireless communication apparatus 2 when the wireless communication apparatus 2 has transferred to the second state.
The controller 14 comprehensively controls operation of the wireless communication apparatus 1. The controller 14 performs control to transmit the first control signal and the second control signal simultaneously (piggybacked on each other) to the wireless communication apparatus 2 when the first state transition is performed, and then a second state transition, which causes the state of the wireless communication apparatus 2 to transfer from the second state to a third state, is performed.
The wireless communication apparatus 2 has a communication unit 21 and a controller 24.
The communication unit 21 performs wireless communication with the wireless communication apparatus 1. The communication unit 21 transmits and receives a control signal as a message to and from the wireless communication apparatus 1, for example.
Specifically, the communication unit 21 has a transmitter 22 and a receiver 23.
The transmitter 22 transmits the first control signal to the wireless communication apparatus 1 when the state transition of the wireless communication apparatus 2 is performed. The transmitter 22 transmits the first control signal to the wireless communication apparatus 1 when the first state transition is performed, for example. The transmitter 22 transmits the second control signal to the wireless communication apparatus 1 when the state of the wireless communication apparatus 2 has transferred to the second state.
The receiver 23 receives the first control signal transmitted from the wireless communication apparatus 1 when the state transition of the wireless communication apparatus 2 is performed. The receiver 23 receives the first control signal transmitted from the wireless communication apparatus 1 when the first state transition is performed, for example. The receiver 23 receives the second control signal transmitted from the wireless communication apparatus 1 when the state of the wireless communication apparatus 2 has transferred to the second state.
The controller 24 comprehensively controls operation of the wireless communication apparatus 2. The controller 24 performs control to simultaneously receive the first control signal and the second control signal from the wireless communication apparatus 1 when the first state transition is performed, and then the second state transition is performed.
According to the foregoing description, in the wireless communication system according to the first embodiment, the communication unit 11 of the wireless communication apparatus 1 transmits the first control signal to the wireless communication apparatus 2 when the state transition of the wireless communication apparatus 2 is performed. The first control signal is a message about the state transition. First, the communication unit 11 of the wireless communication apparatus 1 performs the first state transition, which causes the state of the wireless communication apparatus 2 to transition from the first state to the second state. Subsequently, the controller 14 of the wireless communication apparatus 1 performs control to transmit a third control signal to the wireless communication apparatus 2 when the second state transition, which causes the state of the wireless communication apparatus 2 to transition from the second state to the third state, is performed. The third control signal is a control signal transmitted simultaneously with the first control signal and the second control signal (piggybacked thereon), for example. The second control signal is a message different from the first control signal. In 3GPP, when an RRC inactive mode is introduced, there is a possibility that some problems or malfunctions that have not been known in the world will occur. It is important whether a state transition delay can be reduced, for example. To reduce the state transition delay in particular, it is important to reduce the number of messages transmitted and received between user equipment (UE) and a g Node B (gNB). Therefore, in the wireless communication system according to the first embodiment, the wireless communication apparatus 1 simultaneously transmits the first and second control signals as messages to the wireless communication apparatus 2 and can thereby reduce the state transition delay.
Second Embodiment[Wireless Communication System]
The following describes a second embodiment.
[gNB 10]
The communication unit 11 performs wireless communication with the UE 20. The controller 14 comprehensively controls operation of the gNB 10.
Specifically, the controller 14 is a processing unit processing a baseband signal, for example, and includes a physical (PHY) controller 15, a medium access control (MAC) controller 16, a radio resource control (RRC) controller 17, and a call connection controller 18.
The PHY controller 15 processes signals when wireless transmission is performed. The PHY controller 15 determines a modulation coding scheme for wireless signals, for example. The MAC controller 16 performs processing about data scheduling.
The RRC controller 17 controls operation of the gNB 10. The RRC controller 17 performs setting of wireless resource parameters for use in communication (call setting, for example) and communication state management of the gNB 10, for example. The RRC controller 17 performs handover processing for connecting the UE 20 to an appropriate gNB.
The RRC controller 17 controls the communication unit 11 so as to transmit and receive messages to and from the UE 20.
The RRC controller 17 controls the communication unit 11 so as to transmit and receive an RRC message to and from the UE 20 when performing the first state transition, which causes the state of the UE 20 to transit from an RRC idle mode to an RRC connected mode, for example. The RRC idle mode is an exemplary “first state,” whereas the RRC connected mode is an exemplary “second state.” The RRC message is an exemplary “first control signal.”
The RRC controller 17 controls the communication unit 11 so as to transmit and receive a Non-Access Stratum (NAS) message to and from the UE 20 in the RRC connected mode, for example. The NAS message is an exemplary “second control signal.”
The RRC controller 17 controls the communication unit 11 so as to simultaneously transmit the RRC message and the NAS message to the UE 20 when the second state transition, which causes the state of the UE 20 to transit from the RRC connected mode to an RRC inactive mode, is performed, for example. The RRC inactive mode is an exemplary “third state.” Simultaneous transmission of the RRC message and the NAS message will be described in Solution described below.
The call connection controller 18 determines the type and traffic type of the UE 20 and, based on a determination result, controls management of an RRC state by the RRC controller 17.
[UE 20]
The communication unit 21 performs wireless communication with the gNB 10. The controller 24 comprehensively controls operation of the communication unit 21.
Specifically, the controller 24 is a processing unit processing a baseband signal, for example, and includes a PHY controller 25, a MAC controller 26, an RRC controller 27, and a call connection controller 28.
The PHY controller 25 processes signals when wireless transmission is performed. The PHY controller 25 performs wireless transmission in accordance with the modulation coding scheme for wireless signals informed by the gNB 10, for example. The MAC controller 26 performs processing about data scheduling based on wireless resources and timing indicated by the gNB 10.
The RRC controller 27 controls operation of the UE 20. The RRC controller 27 performs configuration of wireless resource parameters for use in communication (call setting, for example) and communication state management of the UE 20, for example. The RRC controller 27 performs handover processing for connecting to an appropriate gNB 10.
The RRC controller 27 controls the communication unit 21 to transmit and receive messages to and from the gNB 10.
The RRC controller 27 controls the communication unit 21 so as to transmit and receive the RRC message to and from the gNB 10 when the first state transition, which causes the state of the UE 20 to transfer from the RRC idle mode to the RRC connected mode, is performed, for example.
The RRC controller 27 controls the communication unit 21 so as to transmit and receive the NAS message to and from the gNB 10 in the RRC connected mode, for example.
The RRC controller 27 controls the communication unit 21 so as to simultaneously receive the RRC message and the NAS message from the gNB 10 when the second state transition, which causes the state of the UE 20 to transfer from the RRC connected mode to the RRC inactive mode, is performed, for example. Simultaneous reception of the RRC message and the NAS message transmitted from the gNB 10 will be described in Solution described below.
The call connection controller 28 controls management of an RRC state by the RRC controller 27 in accordance with the type and traffic type of the UE 20.
[State Transition]
The following describes a case in which the gNB 10 causes the state of the UE 20 to transition to the RRC inactive mode “RRC INACTIVE” at the time of configuration of data communication.
First, in the RRC idle mode “RRC IDLE,” the UE 20 transmits “Random Access Preamble” as a message RA Msg1 to the gNB 10 (Step S1). The gNB 10 receives the message RA Msg1 “Random Access Preamble” transmitted from the UE 20.
The gNB 10 transmits “Random Access Response” as a message RA Msg2 to the UE 20 in response to the received message RA Msg1 “Random Access Preamble” (Step S2). The UE 20 receives the message RA Msg2 “Random Access Response” transmitted from the gNB 10.
Next, the UE 20 transmits “RRC Connection Establishment Request” as a message RA Msg3 (RRC message) to the gNB 10 (Step S3). The gNB 10 receives the message RA Msg3 “RRC Connection Establishment Request” transmitted from the UE 20.
The message RA Msg3 “RRC Connection Establishment Request” includes information on data communication. The information on data communication includes information on the position of the UE, communication capability, various kinds of parameters, and the identifier (terminal ID) of the UE. The gNB 10 stores the information on data communication. Then, the gNB 10 recognizes which UE 20 has been connected by the stored information on data communication and transmits “RRC Connection Establishment” as a message RA Msg4 (RRC message) to the UE 20 (Step S4). The UE 20 receives the message RA Msg4 “RRC Connection Establishment” transmitted from the gNB 10.
Next, the UE 20 transmits “RRC Connection Establishment Complete” as a message RA Msg5 (RRC message) to the gNB 10 in response to the received message RA Msg4 “RRC Connection Establishment” (Step S5). Then, the UE 20 transfers from the RRC idle mode “RRC IDLE” to the RRC connected mode “RRC CONNECTED.”
In the RRC connected mode “RRC CONNECTED,” the UE 20 transmits “NAS Attach Request” as an NAS message to the gNB 10 (Step S6). The gNB 10 receives the NAS message “NAS Attach Request” transmitted from the UE 20 and transmits the NAS message “NAS Attach Request” to a 5th generation (5G) core network (hereinafter, denoted as “the 5GC”).
Next, the gNB 10 receives “NAS Attach Accept” as an NAS message from the 5GC and transmits the NAS message “NAS Attach Accept” to the UE 20 (Step S7). The UE 20 receives the NAS message “NAS Attach Accept” transmitted from the gNB 10.
Next, the UE 20 transmits “NAS Attach Complete” as an NAS message to the gNB 10 (Step S8). The gNB 10 receives the NAS message “NAS Attach Complete” transmitted from the UE 20 and transmits the NAS message “NAS Attach Complete” to the 5GC.
Then, the gNB 10 causes the state of the UE 20 to transfers from the RRC connected mode “RRC CONNECTED” to the RRC inactive mode “RRC INACTIVE.” In this case, in 3GPP, a technique applying a sub mode of the RRC connected mode may be used, for example.
The sub mode of the RRC connected mode is described in Non Patent Document 5 and 9 using “Cell selection/Cell reselection,” “Paging Monitoring,” or the like, for example. In the following, the sub mode of the RRC connected mode is denoted as “the RRC-light connection mode.”
Similarly, also for the example illustrated in
The UE 20 transfers to the RRC inactive mode, for example, whereby the information on data communication is stored by the gNB 10, and thus the UE 20 does not have to inform the information on data communication to the gNB 10 at the time of resumption of the RRC connected mode.
[Problem]
The following describes a problem when the RRC inactive mode is introduced. Note that this problem has newly been found out by the inventor of the present disclosure after studying introduction of the RRC inactive mode and has not conventionally been known.
When the RRC inactive mode is introduced, it is important whether the state transition delay can be reduced, for example. However, in the state transitions described above, many messages are transmitted and received between the UE 20 and the gNB 10. Specifically, in
[Solution]
Given these circumstances, in the wireless communication system according to the second embodiment, the gNB 10 simultaneously transmits the RRC message and the NAS massage to the UE 20 when the state of the UE 20 is caused to transfer from the RRC connected mode to the RRC inactive mode. The following describes this point with reference to a specific example.
First, in the RRC idle mode “RRC IDLE,” the UE 20 transmits “Random Access Preamble” as the message RA Msg1 to the gNB 10 (Step S101). The gNB 10 receives the message RA Msg1 “Random Access Preamble” transmitted from the UE 20.
The gNB 10 transmits “Random Access Response” as the message RA Msg2 to the UE 20 in response to the received message RA Msg1 “Random Access Preamble” (Step S102). The UE 20 receives the message RA Msg2 “Random Access Response” transmitted from the gNB 10.
Next, the UE 20 transmits “RRC Connection Establishment Request” as the message RA Msg3 (RRC message) including information on data communication to the gNB 10 (Step S103). The gNB 10 receives the message RA Msg3 “RRC Connection Establishment Request” including the information on data communication transmitted from the UE 20.
The gNB 10 stores the information on data communication included in the message RA Msg3 “RRC Connection Establishment Request.” Then, the gNB 10 recognizes which UE 20 has been connected by the stored information on data communication and transmits “RRC Connection Setup” as the message RA Msg4 (RRC message) to the UE 20 (Step S104). The UE 20 receives the message RA Msg4 “RRC Connection Setup” transmitted from the gNB 10.
Next, the UE 20 transmits “RRC Connection Setup Complete” as the message RA Msg5 (RRC message) to the gNB 10 in response to the received message RA Msg4 “RRC Connection Setup” (Step S105). Then, the UE 20 transfers from the RRC idle mode “RRC IDLE” to the RRC connected mode “RRC CONNECTED.”
In the RRC connected mode “RRC CONNECTED,” the UE 20 transmits “NAS Attach Request” as the NAS message to the gNB 10 (Step S106). The gNB 10 receives the NAS message “NAS Attach Request” transmitted from the UE 20 and transmits the NAS message “NAS Attach Request” to the 5GC.
The gNB 10 receives “NAS Attach Accept” as the NAS message from the 5GC. Then, the gNB 10 simultaneously transmits the RRC message “RRC Release” including the indication information “Suspend Indicator” and the NAS message “NAS Attach Accept” to the UE 20 (Step S107).
There is a need to verify whether the gNB 10 can simultaneously transmit the RRC message “RRC Release” and the NAS message “NAS Attach Accept” to the UE 20. Section 4.2.2 of Non Patent Document 9 states that the piggyback of the NAS message in a downlink is used only for “bearer establishment,” “modification,” and “release,” for example. More specifically, it is specified that these are used only for procedures on which the states of NAS and AS depend. That is to say, in the present embodiment, there is a possibility that the gNB 10 is not able to transmit the RRC message “RRC Release” carried on the NAS message “NAS Attach Accept” to the UE 20. This is because “NAS Attach Accept” is a message that makes the state of NAS a connected state, whereas “RRC Release” is a message that makes the state of AS a released state, which are different from each other. Consequently, to enable the messages to simultaneously be transmitted, specifications such as “state transition” and “power saving” may be needed, for example.
Next, the UE 20 simultaneously receives the RRC message “RRC Release” including the indication information “Suspend Indicator” and the NAS message “NAS Attach Request” from the gNB 10. In this case, the UE 20 transmits “NAS Attach Complete” as the NAS message to the gNB 10 (Step S108). The gNB 10 receives the NAS message “NAS Attach Complete” from the UE 20 and transmits the NAS message “NAS Attach Complete” to the 5GC. The UE 20 transitions from the RRC connected mode “RRC CONNECTED” to the RRC inactive mode “RRC INACTIVE” based on the indication information “Suspend Indicator.”
The UE 20, in the RRC inactive mode “RRC INACTIVE,” can resume the RRC connected mode “RRC CONNECTED” by transmitting the resume request “Resume Request” (not illustrated) to the gNB 10 at the time of occurrence of data, for example. The UE 20 transfers to the RRC inactive mode, for example, whereby the information on data communication is stored by the gNB 10, and thus the UE 20 does not have to inform the information on data communication to the gNB 10 at the time of resumption of the RRC connected mode.
According to the foregoing description, in the wireless communication system according to the second embodiment, the communication unit 11 of the gNB 10 transmits the RRC message to the UE 20 when the state transition of the UE 20 is performed. First, the communication unit 11 of the gNB 10 transmits the RRC message to the UE 20 when the first state transition, which causes the state of the UE 20 to transfer from the RRC idle mode “RRC IDLE” to the RRC connected mode “RRC CONNECTED,” is performed. Subsequently, the controller 14 of the gNB 10 performs control to simultaneously transmit the RRC message and the NAS message to the UE 20 when the second state transition, which causes the state of the UE 20 to transfer from the RRC connected mode to the RRC inactive mode “RRC INACTIVE”, is performed. The RRC message transmitted simultaneously with the NAS message in the second state transition includes the indication information “Suspend Indicator” indicating the transition to the RRC inactive mode. In the wireless communication system according to the second embodiment, the gNB 10 transmits the RRC message including the indication information “Suspend Indicator” and the NAS message simultaneously (piggybacked on each other) to the UE 20, whereby the state transition delay is reduced. Consequently, the wireless communication system according to the second embodiment can reduce the state transition delay.
Third EmbodimentIn the second embodiment, whether the indication information “Suspend Indicator” is added to the RRC message is determined by the gNB 10. In this case, the UE 20 transfers from the RRC connected mode to the RRC inactive mode upon reception of the indication information “Suspend Indicator” from the gNB 10. However, this is not limiting. In a third embodiment, for example, the UE 20 requests the indication information “Suspend Indicator” from the gNB 10 and transfers from the RRC connected mode to the RRC inactive mode upon reception of the indication information “Suspend Indicator” responsive to the request from the gNB 10. The third embodiment can thereby reduce the state transition delay and besides achieve power saving for the UE 20. In the third embodiment, the same parts as those of the second embodiment are denoted by the same symbols, and descriptions thereof are omitted. The third embodiment can be combined with the first embodiment to the extent that the processing details do not conflict with each other.
First, Steps S101 and S102 described above are executed.
Next, the UE 20 transmits the message RA Msg3 “RRC Connection Establishment Request” including the information on data communication and request information “Inactive Preference” to the gNB 10 (Step S103). The request information “Inactive Preference” is information for requesting the indication information “Suspend Indicator” from the gNB 10. The gNB 10 receives the message RA Msg3 “RRC Connection Establishment Request” from the UE 20. The gNB 10 stores the information on data communication and the request information “Inactive Preference” included in the received message RA Msg3 “RRC Connection Establishment Request.”
Next, Steps S104 to S106 described above are executed.
The gNB 10 receives the NAS message “NAS Attach Accept” from the 5GC. Then, the gNB 10 simultaneously transmits the RRC message “RRC Release” including the indication information “Suspend Indicator” and the NAS message “NAS Attach Accept” to the UE 20 based on the stored request information “Inactive Preference” (Step S107).
Subsequently, Step S108 described above is executed.
The gNB 10 can add the request information “Inactive Preference” to the message RA Msg3 “RRC Connection Establishment Request.” The message RA Msg3 is transmitted from the UE 20 by a physical uplink shared channel (PUSCH), for example. Given these circumstances, in 5G, reducing the number of bits of cyclic redundancy checking (CRC) to be added to the message RA Msg3 (PUSCH) from 24 bits to 8 to 16 bits, for example, is being considered. When the number of bits of CRC is reduced, it is easy to add the request information “Inactive Preference” to its free space.
Although the UE 20 adds the request information “Inactive Preference” to the message RA Msg3 “RRC Connection Establishment Request” in the third embodiment, this is not limiting. The UE 20 may add the request information “Inactive Preference” to the message RA Msg5 “RRC Connection Setup Complete,” for example.
According to the foregoing description, in the wireless communication system according to the third embodiment, the communication unit 11 of the gNB 10 transmits the RRC message to the UE 20 when the state transition of the UE 20 is performed. First, the communication unit 11 of the gNB 10 transmits the RRC message to the UE 20 when the first state transition, which causes the state of the UE 20 to transfer from the RRC idle mode “RRC IDLE” to the RRC connected mode “RRC CONNECTED,” is performed. Subsequently, the controller 14 of the gNB 10 performs control to simultaneously transmit the RRC message and the NAS message to the UE 20 when the second state transition, which causes the state of the UE 20 to transition from the RRC connected mode to the RRC inactive mode “RRC INACTIVE,” is performed. The RRC message transmitted simultaneously with the NAS message in the second state transition includes the indication information “Suspend Indicator” indicating the transition to the RRC inactive mode. In the wireless communication system according to the third embodiment, the gNB 10 simultaneously transmits the RRC message including the indication information “Suspend Indicator” and the NAS message to the UE 20, whereby the state transition delay is reduced by at least by 10 ms. Consequently, the wireless communication system according to the third embodiment can reduce the state transition delay.
In the wireless communication system according to the third embodiment, the communication unit 11 of the gNB 10 receives, from the UE 20, the RRC message including the request information “Inactive Preference” requesting the indication information “Suspend Indicator” in the first state transition. In this case, the controller 14 of the gNB 10 performs control to simultaneously transmit the RRC message including the indication information “Suspend Indicator” and the NAS message to the UE 20 based on the request information “Inactive Preference” in the second state transition. Thus, the UE 20 requests the indication information “Suspend Indicator” from the gNB 10 and transitions from the RRC connected mode to the RRC inactive mode upon reception of the indication information “Suspend Indicator” responsive to the request from the gNB 10. The wireless communication system according to the third embodiment can thereby reduce the state transition delay and besides achieve power saving for the UE 20.
Fourth EmbodimentAlthough the RRC message “RRC Release” transmitted simultaneously with the NAS message “NAS Attach Accept” includes “Suspend Indicator” as the indication information in the third embodiment, this is not limiting. The RRC message “RRC Release” transmitted simultaneously with the NAS message “NAS Attach Accept” may include a flag as the indication information, for example. In the fourth embodiment, the same parts as those of the third embodiment are denoted by the same symbols, and descriptions thereof are omitted. The fourth embodiment can be combined with the first embodiment to the extent that the processing details do not conflict with each other.
First, Steps S101 to S106 described above are executed.
The gNB 10 receives the NAS message “NAS Attach Accept” from the 5GC. Then, the gNB 10 simultaneously transmits the RRC message “RRC Release” including “flag” as the indication information and the NAS message “NAS Attach Accept” to the UE 20 based on the stored request information “Inactive Preference” (Step S107). The indication information “flag” represents information “idle” indicating a transition to the RRC idle mode “RRC IDLE” or information “inactive” indicating a transition to the RRC inactive mode “RRC INACTIVE.”
Subsequently, Step S108 described above is executed.
According to the foregoing description, in the wireless communication system according to the fourth embodiment, the communication unit 11 of the gNB 10 receives, from the UE 20, the RRC message including the request information “Inactive Preference” requesting the indication information “Suspend Indicator” in the first state transition. In this case, the controller 14 of the gNB 10 performs control to simultaneously transmit the RRC message including the indication information “flag” and the NAS message to the UE 20 based on the request information “Inactive Preference” in the second state transition. Thus, the UE 20 requests the indication information “flag” from the gNB 10 and transitions from the RRC connected mode to the RRC inactive mode upon reception of the indication information “flag” responsive to the request from the gNB 10. The wireless communication system according to the fourth embodiment can thereby reduce the state transition delay and besides achieve power saving for the UE 20 like the third embodiment.
The following specifically describes a reduction in the state transition delay with reference to the third embodiment, for example, as the effect of the wireless communication systems according to the second to fourth embodiments.
In
In the example illustrated in
In the present embodiment, a probability of the gNB 10 adding the indication information “Suspend Indicator” to the RRC message “RRC Release” is set to 0.8. In this case, a needed time g(x) from the RRC idle mode to the RRC inactive mode is represented by g(x)=20+20+(0.8×10+(1−0.8)×x)=48+0.2×x.
In
[Modification]
In the second to fourth embodiments, the gNB 10 causes the state of the UE 20 to transfer to the RRC inactive mode “RRC INACTIVE” at the time of configuration of data communication. In the third and fourth embodiments, for example, the UE 20 requests the indication information “Suspend Indicator” from the gNB 10 and transitions to the RRC inactive mode upon reception of the indication information “Suspend Indicator” from the gNB 10 at the time of setting of data communication. As a modification of the example illustrated in
First, in the RRC idle mode “RRC IDLE,” the UE 20 transmits the message RA Msg1 “Random Access Preamble” to the gNB 10 (Step S201). The gNB 10 receives the message RA Msg1 “Random Access Preamble” transmitted from the UE 20.
The gNB 10 transmits the message RA Msg2 “Random Access Response” to the UE 20 in response to the received message RA Msg1 “Random Access Preamble” (Step S202). The UE 20 receives the message RA Msg2 “Random Access Response” transmitted from the gNB 10.
Next, the UE 20 transmits the message RA Msg3 “RRC Connection Establishment Request” including the information on data communication and the request information “Inactive Preference” to the gNB 10 (Step S203). The gNB 10 receives the message RA Msg3 “RRC Connection Establishment Request” from the UE 20. The gNB 10 stores the information on data communication and the request information “Inactive Preference” included in the received message RA Msg3 “RRC Connection Establishment Request.”
The gNB 10 recognizes which UE 20 has been connected by the stored information on data communication and transmits the message RA Msg4 “RRC Connection Setup” to the UE 20 (Step S204). The UE 20 receives the message RA Msg4 “RRC Connection Setup” transmitted from the gNB 10.
Next, the UE 20 transmits the message RA Msg5 “RRC Connection Setup Complete” to the gNB 10 in response to the received message RA Msg4 “RRC Connection Setup” (Step S205). Then, the UE 20 transitions from the RRC idle mode “RRC IDLE” to the RRC connected mode “RRC CONNECTED.”
In the RRC connected mode “RRC CONNECTED,” the UE 20 transmits the NAS message “NAS Attach Request” to the gNB 10 (Step S206). The gNB 10 receives the NAS message “NAS Attach Request” transmitted from the UE 20 and transmits the NAS message “NAS Attach Request” to the 5GC.
Next, the gNB 10 receives the NAS message “NAS Attach Accept” from the 5GC and transmits the NAS message “NAS Attach Accept” to the UE 20 (Step S207). The UE 20 receives the NAS message “NAS Attach Accept” transmitted from the gNB 10.
Next, the UE 20 transmits “NAS Attach Complete” as the NAS message to the gNB 10 (Step S208). The gNB 10 receives the NAS message “NAS Attach Complete” transmitted from the UE 20 and transmits the NAS message “NAS Attach Complete” to the 5GC.
Next, the UE 20 performs data communication with the gNB 10 (refer to “Data” in
At the time of end of data communication, the gNB 10 transmits the RRC message “RRC Release” including the indication information “Suspend Indicator” to the UE 20 based on the stored request information “Inactive Preference” (Step S209). The UE 20 receives the RRC message “RRC Release” including the indication information “Suspend Indicator” from the gNB 10. The UE 20 transfers from the RRC connected mode to the RRC inactive mode in response to the indication information “Suspend Indicator” included in the received RRC message “RRC Release.”
Thus, in the modification, the UE 20 requests the indication information “Suspend Indicator” from the gNB 10 at the time of configuration of data communication, and the UE 20 transfers to the RRC inactive mode upon reception of the indication information “Suspend Indicator” from the gNB 10 at the time of end of data communication. The medication can thereby achieve more power saving for the UE 20 than the example illustrated in
The components in the embodiments are not necessarily needed to be physically configured as illustrated. That is to say, specific modes of distribution and consolidation of the parts are not limited to those illustrated, and the whole or part thereof can be configured by functionally or physically distributing or consolidating any units in accordance with various kinds of loads or use conditions.
Further, the whole or any part of various kinds of processing performed by the apparatuses may be executed on a central processing unit (CPU) (or a microcomputer such as a micro processing unit (MPU) or a micro controller unit (MCU)). The whole or any part of the various kinds of processing may be executed on a computer program analytically executed on the CPU (or the microcomputer such as the MPU or the MCU) or on hardware by a wired logic.
The gNB 10 and the UE 20 of the embodiments can be implemented by the following hardware configuration, for example.
The various kinds of processing performed by the gNB 10 of the embodiments may be implemented by executing computer programs stored in various kinds of memories such as a non-volatile storage medium by the processor 101. That is to say, the memory 102 may store therein computer programs corresponding to respective pieces of processing executed by respective components, and the processor 101 may execute the computer programs. The respective components correspond to the functions of the controller 14. The communication unit 11 is implemented by the RF circuit 103.
Although one processor 101 executes the various kinds of processing performed by the gNB 10 of the embodiments, this is not limiting; a plurality of processors may execute them.
The various kinds of processing performed by the UE 20 of the embodiments may be implemented by executing computer programs stored in various kinds of memories such as a non-volatile storage medium by the processor 201. That is to say, the memory 202 may store therein computer programs corresponding to respective pieces of processing executed by respective components, and the processor 201 may execute the computer programs. The respective components correspond to the functions of the controller 24. The communication unit 21 is implemented by the RF circuit 203.
Although one processor 201 executes the various kinds of processing performed by the UE 20 of the embodiments, this is not limiting; a plurality of processors may execute them.
One aspect can reduce a state transition delay.
All examples and conditional language provided herein are intended for the pedagogical purposes of aiding the reader in understanding the disclosure and the concepts contributed by the inventors to further the art, and are not to be construed as limitations to such specifically recited examples and conditions, nor does the organization of such examples in the specification relate to a showing of the superiority and inferiority of the disclosure. Although one or more embodiments of the present disclosure have been described in detail, it should be understood, that the various changes, substitutions, and alterations could be made hereto without departing from the spirit and scope of the disclosure.
Claims
1. A base station comprising:
- a communicator configured to communicate to a terminal; and
- a processor configured to: control to transmit first information that is information of a first layer when a first state transition of a mobile station, which causes a state of the mobile station to transfer from a first state to a second state, is performed, and control to transmit second information that is information of the first layer and third information that is information of a second layer when a second state transition of the mobile station, which causes the state of the mobile station to transfer from the second state to a third state, is performed.
2. The base station according to claim 1, wherein
- the first layer is a RRC layer, and
- the second layer is a NAS layer.
3. The base station according to claim 1, wherein
- the first state is a RRC IDLE state,
- the second state is a RRC CONNECTED state, and
- the third state is a RRC INACTIVE state.
4. The base station according to claim 1, wherein the second information includes indication information indicating a transition to the third state.
5. The base station according to claim 1, wherein
- the communicator is further configured to receive, from the mobile station, request information requesting the indication information in the first state transition, and
- the processor is further configured to simultaneously transmit the second information and the third information to the mobile station according to the request information.
6. The base station according to claim 1, wherein
- the second state transition is performed after performing the first state transition.
7. A mobile station comprising:
- a communicator configured to communicate to a base station; and
- a processor configured to: control to perform a first state transition which transfer from a first state to a second state when the communicator receives first information that is information of a first layer from the base station, and control to perform a second state transition which transfer from the second state to a third state when the communicator receives second information that is information of the first layer and third information that is information of a second layer from the base station.
8. The terminal according to claim 7, wherein
- the first layer is a RRC layer, and
- the second layer is a NAS layer.
9. The terminal according to claim 7, wherein
- the first state is a RRC IDLE state,
- the second state is a RRC CONNECTED state, and
- the third state is a RRC INACTIVE state.
10. The terminal according to claim 7, wherein the second information includes indication information indicating a transition to the third state.
11. The terminal according to claim 10, wherein
- the communicator is further configured to transmit, to the base station, request information requesting the indication information in the first state transition, and
- the communicator is further configured to receive the second information and the third information that are simultaneously transmitted according to the request information.
12. The terminal according to claim 7, wherein
- the second state transition is performed after performing the first state transition.
13. A wireless communication system comprising a first wireless communication apparatus and a second wireless communication apparatus,
- the first wireless communication apparatus includes a communicator configured to communicate to the second wireless communication apparatus; and a processor configured to: control to transmit first information that is information of a first layer when a first state transition of a wireless communication apparatus, which causes a state of the wireless communication apparatus to transfer from a first state to a second state, is performed, and control to transmit second information that is information of the first layer and third information that is information of a second layer when a second state transition of a wireless communication apparatus, which causes the state of the wireless communication apparatus to transfer from the second state to a third state, is performed.
6456604 | September 24, 2002 | Lee et al. |
9007930 | April 14, 2015 | Furukawa |
10750380 | August 18, 2020 | Fujishiro |
10965039 | March 30, 2021 | Chandler et al. |
20100069128 | March 18, 2010 | Cheng |
20100316103 | December 16, 2010 | Schoppmeier |
20110026294 | February 3, 2011 | Tsukamoto |
20140023132 | January 23, 2014 | Pandey et al. |
20150043403 | February 12, 2015 | Tarradell et al. |
20150080006 | March 19, 2015 | Ohta |
20150099506 | April 9, 2015 | Iwai et al. |
20160309241 | October 20, 2016 | Ljung |
20160309379 | October 20, 2016 | Pelletier |
20170325281 | November 9, 2017 | Hong et al. |
20170332362 | November 16, 2017 | Li et al. |
20180198495 | July 12, 2018 | Davydov |
20180199397 | July 12, 2018 | Skillermark |
20180220486 | August 2, 2018 | Tseng et al. |
20190058565 | February 21, 2019 | Au |
20190191483 | June 20, 2019 | Ryoo et al. |
20190268831 | August 29, 2019 | Lee |
20200099432 | March 26, 2020 | Maattanen et al. |
20200200860 | June 25, 2020 | Hong |
20200367081 | November 19, 2020 | Shi |
20210160946 | May 27, 2021 | Oak et al. |
20220053448 | February 17, 2022 | Velev et al. |
20220070759 | March 3, 2022 | Wirth et al. |
2016-146661 | August 2016 | JP |
2016-527848 | September 2016 | JP |
2015/021284 | February 2015 | WO |
- International Search Report and Written Opinion of the International Searching Authority issued by the Japan Patent Office for corresponding International Patent Application No. PCT/JP2018/010318, dated Jun. 5, 2018, with an English translation.
- 3GPP TS 36.211 V14.4.0, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation (Release 14), Sep. 2017.
- 3GPP TS 36.212 V14.4.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding, (Release 14)”, Sep. 2017.
- 3GPP TS 36.213 V14.4.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures, (Release 14)”, Sep. 2017.
- 3GPP TS 36.214 V14.4.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer; Measurements, (Release 14)”, Dec. 2017.
- 3GPP TS 36.300 V14.4.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 14)”, Sep. 2017.
- 3GPP TS 36.321 V14.4.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification, (Release 14)”, Sep. 2017.
- 3GPP TS 36.322 V14.1.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Link Control (RLC) protocol specification (Release 14)”, Sep. 2017.
- 3GPP TS 36.323 V14.4.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data Convergence Protocol (PDCP) specification, (Release 14)”, Sep. 2017.
- 3GPP TS 36.331 V14.4.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification, (Release 14)”, Sep. 2017.
- 3GPP TS 36.413 V14.4.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-Utran); S1 Application Protocol (S1AP), (Release 14)”, Sep. 2017.
- 3GPP TS 36.423 V14.4.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 application protocol (X2AP)”, Sep. 2017.
- 3GPP TS 37.324 V1.1.1, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; E-UTRA and NR; Service Data Adaptation Protocol (SDAP) specification (Release 15)”, Nov. 2017.
- 3GPP TS 37.340 V2.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Stage 2 (Release 15)”, Dec. 2017.
- 3GPP TS 36.425 V14.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 interface user plane protocol (Release 14)”, Mar. 2017.
- 3GPP TS 38.201 V2.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer; General description (Release 15)”, Dec. 2017.
- 3GPP TS 38.202 V2.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Services provided by the physical layer (Release 15)”, Dec. 2017.
- 3GPP TS 38.211 V2.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical channels and modulation (Release 15)”, Dec. 2017.
- 3GPP TS 38.212 V1.2.1, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Multiplexing and channel coding (Release 15)”, Dec. 2017.
- 3GPP TS 38.213 V2.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for control (Release 15)”, Dec. 2017.
- 3GPP TS 38.214 V2.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for data (Release 15)”, Dec. 2017.
- 3GPP TS 38.215 V2.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer measurements (Release 15)”, Dec. 2017.
- 3GPP TS 38.300 V2.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2 (Release 15)”, Dec. 2017.
- 3GPP TS 38.321 V2.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Medium Access Control (MAC) protocol specification (Release 15)”, Dec. 2017.
- 3GPP TS 38.322 V2.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Link Control (RLC) protocol specification (Release 15)”, Dec. 2017.
- 3GPP TS 38.323 V2.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Packet Data Convergence Protocol (PDCP) specification, (Release 15)”, Dec. 2017.
- 3GPP TS 38.331 V0.4.0, “3rd Generation Partnership Project Technical Specification Group Radio Access Network NR Radio Resource Control (RRC) Protocol specification, (Release 15)”, Dec. 2017.
- 3GPP TS 38.401 V1.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Architecture description, (Release 15)”, Dec. 2017.
- 3GPP TS 38.410 V0.6.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; NG general aspect and principles, (Release 15)”, Dec. 2017.
- 3GPP TS 38.413 V0.5.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG Radio Access Network (NG-RAN); NG Application Protocol (NGAP), (Release 15)”, Dec. 2017.
- 3GPP TS 38.420 V0.5.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Xn general aspects and principles, (Release 15)”, Dec. 2017.
- 3GPP TS 38.423 V0.5.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG Radio Access Network (NG-RAN); Xn application protocol (XnAP), (Release 15)”, Dec. 2017.
- 3GPP TS 38.470 V1.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; F1 general aspects and principles, (Release 15)”, Dec. 2017.
- 3GPP TS 38.473 V1.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; F1 application protocol (F1AP), (Release 15)”, Dec. 2017.
- 3GPP TR 38.801 V14.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on new radio access technology: Radio access architecture and interfaces (Release 14)”, Mar. 2017.
- 3GPP TR 38.802 V14.2.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on New Radio Access Technology Physical Layer Aspects (Release 14)”, Sep. 2017.
- 3GPP TR 38.803 V14.2.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on new radio access technology: Radio Frequency (RF) and co-existence aspects (Release 14)”, Sep. 2017.
- 3GPP TR 38.804 V14.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on New Radio Access Technology; Radio Interface Protocol Aspects (Release 14)”, Mar. 2017.
- 3GPP TR 38.900 V14.3.1, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on channel model for frequency spectrum above 6 GHz (Release 14)”, Jul. 2017.
- 3GPP TR 38.912 V14.1.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on New Radio (NR) access technology (Release 14)”, Jun. 2017.
- 3GPP TR 38.913 V14.3.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on Scenarios and Requirements for Next Generation Access Technologies; (Release 14)”, Jun. 2017.
- NTT DOCOMO, “New SID Proposal:Study on New Radio Access Technology”, Agenda Item: 9.1, 3GPP TSG-RAN Meeting #71, RP-160671, Göteborg, Sweden, Mar. 7-Mar. 10, 2016.
- 3GPP TR 36.912 V16.0.0, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Feasibility study for Further Advancements for E-UTRA (LTE-Advanced) (Release 16)”, Jul. 2020.
- Huawei et al., “UE behaviour upon leaving PRC_Connected state”, Agenda Item: 10.4.1.3.5, 3GPP TSG-RAN WG2 Meeting #101, R2-1803247, Athens, Greece, Feb. 26-Mar. 2, 2018.
- Asustek, “State transition from RRC_Connected to RRC_Inactive”, Agenda Item: 10.4.1.3.5, 3GPP TSG-RAN WG2 Meeting #101, R2-1801895, Athens, Greece, Feb. 26-Mar. 2, 2018.
- Extended European search report with supplementary European search report and the European search opinion issued by the European Patent Office for corresponding European Patent Application No. 18909455.0-1231, dated Feb. 23, 2021.
- ZTE, “Remaining issues for quick release of RRC connection in FeNB-IoT”, Agenda Item: 9.13.6, 3GPP TSG-RAN WG2 Meeting #100, R2-1712329, Reno, Nevada, Nov. 27-Dec. 1, 2017.
- Non-Final Office Action issued by the United States Patent and Trademark Office for corresponding U.S. Appl. No. 17/018,823, dated Aug. 25, 2021.
- Final Office Action issued by the United States Patent and Trademark Office for corresponding U.S. Appl. No. 17/018,823, dated Mar. 11, 2022.
- Notice of Allowance issued by the United States Patent and Trademark Office for corresponding U.S. Appl. No. 17/018,823, dated Aug. 3, 2022.
- First Notification of Office Action and Search Report issued by the China National Intellectual Property Administration for corresponding Chinese Patent Application No. 201880091207.0, dated Mar. 28, 2023, with an English translation.
- Communication pursuant to Article 94(3) EPC issued by the European Patent Office for corresponding European Patent Application No. 18 909 455.0-1215, dated Feb. 8, 2023.
Type: Grant
Filed: Nov 2, 2022
Date of Patent: Jan 9, 2024
Patent Publication Number: 20230052566
Assignee: FUJITSU LIMITED (Kawasaki)
Inventors: Yoshiaki Ohta (Yokohama), Yoshihiro Kawasaki (Kawasaki), Takayoshi Ode (Yokohama), Jianming Wu (Kawasaki)
Primary Examiner: Andrew Wendell
Application Number: 17/979,053
International Classification: H04W 76/20 (20180101); H04W 76/27 (20180101);