DETAILED ACTION
This communication is in response to the claims filed on 03/06/2024.
Application No: 18/689,630
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
Notice of Pre-AIA or AIA Status
In the event the determination of the status of the application as subject to AIA 35 U. S. C. 102 and 103 (or as subject to pre-AIA 35 U. S. C. 102 and 103) is incorrect, any correction of the statutory basis for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
Claim Rejections - 35 USC § 103
The following is a quotation of 35 U. S. C. 103 which forms the basis for all obviousness rejections set forth in this Office action:
A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102 of this title, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made.
The factual inquiries set forth in Graham v. John Deere Co., 383 U. S. 1, 148 USPQ 459 (1966), that are applied for establishing a background for determining obviousness under 35 U. S. C. 103 are summarized as follows:
1. Determining the scope and contents of the prior art.
2. Ascertaining the differences between the prior art and the claims at issue.
3. Resolving the level of ordinary skill in the pertinent art.
4. Considering objective evidence present in the application indicating obviousness or nonobviousness.
Claims 1-3, 5-10, 12-15, and 17-20 are rejected under 35 U. S. C. 103 as being unpatentable over BULAKCI et al. ( WO 2023001652 A1 in view of KANNEATH et al. (WO 2022233694 A1).
Regarding claim 1, BULAKCI teaches a Radio Access Network (RAN) Intelligent Controller (RIC) ([0023], Fig. 6, e.g. In addition to 3 GPP technology, the Open-Radio Access Networks (O-RAN) Alliance is developing technology to provide open radio access networks. [0023] The Near-RT RIC 352 may, through the E2 interface 360, communicate with one or more E2 Nodes, such as E2 node 315 (open control unit (O-CU) control plane (O-CU-CP), O- CU user plane (O-CU-UP), open distributed unit (O-DU), and open evolved NodeB (O-eNB)) for time sensitive management and control of the radio resources, such as interference management, handover management, Quality of Service (QoS) management, and radio connection management (i.e. a network comprising RAN intelligent controller (RIC) ), comprising:
a memory configured to store instructions executable by a processor ([0054], e.g. The network node 400 may include a network interface 402, a processor 420, and a memory 404, in accordance with some example embodiments. The network interface 402 may include wired and/or wireless transceivers to enable access to other nodes including base stations, other network nodes, the Internet, other networks, and/or other nodes (i.e. a memory configured to store instructions executable by a processor)); and the processor configured to execute the instructions stored in the memory and thereby cause the RIC to:
receive a mobility history information of a User Equipment (UE) ([0024], e.g. The RAN UE context (e.g., in 3GPP) and the UE context relevant information (e.g., in ORAN) may be stored in a central entity, such as a serving base station (e.g., a gNB-CU-CP) or a Near-RT RIC. In case of mobility for an RRC connected UE 105 for example, the RAN UE context needs to be exchanged over P2P interfaces, such as the Xn, in a distributed way to support the UE’s mobility (i.e. receive a mobility history information of a User Equipment. [0036] When the HO preparation request is received by a target node, the target node can retrieve the UE context information and other intelligence information from the (R)AN DSF in the background, without affecting the HO latency. In some embodiments, UE context information is enriched with history information such that it can be used by, for example, artificial intelligence and/or machine learning to identify )); and
a subscriber identifier (ID) of the UE from a base station wherein the base station is where the UE is connected ([0030], Fig. 2, Fig. 6b, e.g. In some example embodiments, the UE context information may be saved in the (R)AN DSF with an associated identifier, such as a UE ID to be identifiable by any authorized network node (i.e. SIM ID), entity in the (R)AN, and/or core and/or management system (e.g., OAM). And, this identifier may be allocated by any authorized network node in the network in the form of, for example, a gNB-CU UE FI AP ID, a gNB-CU-CP UE El AP ID, an AMF UE NGAP ID, or any other type of identifier allocated by, for example a base station. [0064] The apparatus 10 may comprise memory, such as a subscriber identity module (SIM) 38, a removable user identity module (R-UIM), an eUICC, an UICC, U-SIM, and/or the like, which may store information elements related to a mobile subscriber (i.e. receiving history from a subscriber identifier (ID) of the UE associated with a base station) );
store the mobility history information of the UE based on the subscriber ID of the UE ([0030], e.g. In some example embodiments, the UE context information may be saved in the (R)AN DSF with an associated identifier (i.e. SIM or IMEI identification), such as a UE ID to be identifiable by any authorized network node, entity in the (R)AN, and/or core and/or management system (e.g., OAM). [0064] The apparatus 10 may comprise memory, such as a subscriber identity module (SIM) 38, a removable user identity module (R-UIM), an eUICC, an UICC, U-SIM, and/or the like (i.e. store the mobility history information of the UE based on the subscriber ID of the UE)).
BULAKCI teaches a method for retrieving context information for a user equipment in response to the retrieve request from a network node based on the context key; and sending the context information to the network node. However BULAKCI differs from the claimed invention in not specifically and clearly describing wherein
determine a priority cell list based on the mobility history information of the UE.
However, in the analogous field of endeavor, KANNEATH teaches wherein
determine a priority cell list based on the mobility history information of the UE ([page 26, lines 9-18], e.g. As an example, if UE-B is in a first cell and the mobility history information indicates that UE-B has moved to a second cell from the first cell in the past, then the second cell may be given a higher priority compared to other cells (i.e. determine a priority cell list based on the mobility history)).
Therefore, it would have been obvious to one of ordinary skill in the art before the effective filing date of the invention to implement the method of KANNEATH within the method of BULAKCI. The motivation to combine references is that the combined system provides optimization of the usage of network resources. A terminal device may be utilized to enable better usage of resources and enhanced user experience to a user of the terminal device (See KANNEATH [Page 1, lines 5-8).
Regarding claim 2, BULAKCI in view of KANNEATH teaches all the limitations of claim 1. BULAKCI further teaches wherein the processor is configured to: map the mobility history information with the subscriber ID of the UE ([0036], e.g. Moreover, the UE context information stored in the (R)AN DSF may be categorized per UE or categorized per UE group. In other words, the UE context information may map to a single UE or may map to a group of UEs. An example for a group of UEs can be in the scenario of vehicle-to-anything (V2X) communications, such as a V2X platooning use case. [0024] The RAN UE context (e.g., in 3GPP) and the UE context relevant information (e.g., in ORAN) may be stored in a central entity, such as a serving base station (e.g., a gNB-CU-CP) or a Near-RT RIC. (i.e. map the mobility history information with the subscriber ID of the UE)).
KANNEATH further teaches wherein store the mapped mobility history information for determining the priority cell list ([page 26, lines 9-18], e.g. As an example, if UE-B is in a first cell and the mobility history information indicates that UE-B has moved to a second cell from the first cell in the past, then the second cell may be given a higher priority compared to other cells (i.e. store the mapped mobility history information for determining the priority cell list)).
The motivation to combine reference of KANNEATH within the method of BULAKCI before the effective filing date of the invention is that the new method provides fulfilling the need for improving the deployment and performance of communication systems, the concept of “plug-and-play” (e/g)NodeBs may be introduced. A network which may be able to use “plug-and-play” (e/g)NodeBs, may include, in addition to Home (e/g)NodeBs (H(e/g)nodeBs), a home node B gateway, or HNB-GW (not shown in FIG. 1). A HNB Gateway (HNB-GW), which may be installed within an operator’s network, may aggregate traffic from a large number of HNBs back to a core network (See KANNEATH page 15, lines 26-31).
Regarding claim 3, BULAKCI in view of KANNEATH teaches all the limitations of claim 1. KANNEATH further teaches wherein the processor is configured to: determine the priority cell list based on the mobility history information, wherein the mobility history information of the UE comprises information regarding one or more cells of a plurality of cells visited by the UE during an inactive state or an idle state or in connected state; and transmit the priority cell list to the base station [page 26, lines 9-18], e.g. UE-B identifies 806 one or more cells and/or one or more carriers with a higher probability to be the next serving cell and/or carrier. The one or more cells and/or the one or more carriers may be identified, for example, based on the mobility history information of UE-B. For example, the mobility history information may comprise handovers and cell re-selections associated with UE-B (i.e. transmit the priority cell list to the base station). The mobility history information may also comprise the time that UE-B has spent in a given cell, …. As an example, if UE-B is in a first cell and the mobility history information indicates that UE-B has moved to a second cell from the first cell in the past, then the second cell may be given a higher priority compared to other cells, … . (i.e. cells visited by the UE during an inactive state or an idle state or in connected state; and transmit the priority cell list to the base station)).
The motivation to combine reference of KANNEATH within the method of BULAKCI before the effective filing date of the invention is that the new method provides fulfilling the need for improving the deployment and performance of communication systems, the concept of “plug-and-play” (e/g)NodeBs may be introduced. A network which may be able to use “plug-and-play” (e/g)NodeBs, may include, in addition to Home (e/g)NodeBs (H(e/g)nodeBs), a home node B gateway, or HNB-GW (not shown in FIG. 1). A HNB Gateway (HNB-GW), which may be installed within an operator’s network, may aggregate traffic from a large number of HNBs back to a core network (See KANNEATH page 15, lines 26-31).
Regarding claim 5, BULAKCI in view of KANNEATH teaches all the limitations of claim 1. BULAKCI further teaches wherein the mobility history information and the subscriber ID are received by the RIC from the base station using one of a first message and a second message via E2 interface ([0022], e.g. when the user equipment (UE) 105 is in RRC CONNECTED state, the UE’s 105 context (e.g., UE state information, security information, UE capability information, etc.) is kept by or within the RAN 110 and may be transmitted over a P2P interface, such as the Xn interface (see, e.g., 3GPP TS 38.300) between a source base station (e.g., source gNB) and a target base station (e.g., during mobility events) [0023] Both Non-RT RIC and Near-RT RIC employ SB A principles and utilize SBI for communicating internally and with each other. However, as shown in FIG. 3, the ORAN also employs P2P interfaces, such as the E2 interface towards E2 Nodes, rather than a service-based architecture including service-based interfaces (SBI) (i.e. mobility history information and the subscriber ID are received by the RIC from the base station using one of a first message and a second message via E2 interface)).
Regarding claim 6, BULAKCI in view of KANNEATH teaches all the limitations of claim 1. BULAKCI further teaches wherein the priority cell list and the subscriber ID are transmitted to the base station using a first message via E2 interface ([0023], Fig. 2, Fig. 4, e.g. However, as shown in FIG. 3, the ORAN also employs P2P interfaces, such as the E2 interface towards E2 Nodes, rather than a service-based architecture including service-based interfaces (SBI). [0046] At 502, the source gNB base station 402A may update the UE context information stored at the (R)AN DSF 450 over the SBI 142. For example, the UE context information for UE 405 A may be updated by sending, via the SBI interface, a message to the (R)AN DSF 450, so the (R)AN DSF can store the updated UE context information for a given UE, such as UE 405A and/or UEs 405B-C. This message may include a key, such as an identifier, to the stored UE context information being updated. For example, the identifier may be one or more of the following: a UE ID, a gNB ID, an E2 Node ID). [0048] At 504, the UE 405 A may be handed over from the source gNB base station 402Ato the target gNB base station 402B (i.e. handover requires priority cell list, therefore cell list also transmitted). This may cause or trigger a need for the updates in the context information for the UE 405 A. As noted, the UE context information may include UE capability information, UE identity information, a UE mobility state, user security parameters, UE historical information regarding mobility state, and the like (i.e. the priority cell list and the subscriber ID are transmitted to the base station using a first message via E2 interface)).
Regarding claim 7, BULAKCI in view of KANNEATH teaches all the limitations of claim 1. BULAKCI further teaches wherein the priority cell list and the subscriber ID are transmitted to the base station using a second message via E2 interface ([0023], Fig. 2, Fig. 4, e.g. However, as shown in FIG. 3, the ORAN also employs P2P interfaces, such as the E2 interface towards E2 Nodes, rather than a service-based architecture including service-based interfaces (SBI). [0048], e.g. At 504, the UE 405 A may be handed over from the source gNB base station 402Ato the target gNB base station 402B (i.e. handover requires priority cell list, therefore cell list also transmitted). This may cause or trigger a need for the updates in the context information for the UE 405 A. As noted, the UE context information may include UE capability information, UE identity information, a UE mobility state, user security parameters, UE historical information regarding mobility state, and the like (i.e. the priority cell list and the subscriber ID are transmitted to the base station using a second message via E2 interface)).
Regarding claim 8, BULAKCI teaches a method ([0023], Fig. 6, e.g. In addition to 3 GPP technology, the Open-Radio Access Networks (O-RAN) Alliance is developing technology to provide open radio access networks (i.e. a method steps executed by a RAN). [0023] The Near-RT RIC 352 may, through the E2 interface 360, communicate with one or more E2 Nodes, such as E2 node 315 (open control unit (O-CU) control plane (O-CU-CP), O- CU user plane (O-CU-UP), open distributed unit (O-DU), and open evolved NodeB (O-eNB)) for time sensitive management and control of the radio resources, such as interference management, handover management, Quality of Service (QoS) management, and radio connection management (i.e. a network comprising RAN intelligent controller (RIC) ), comprising:
receiving, by a Radio Access Network (RAN) Intelligent Controller (RIC), a mobility history information of a User Equipment (UE) ([0024], e.g. The RAN UE context (e.g., in 3GPP) and the UE context relevant information (e.g., in ORAN) may be stored in a central entity, such as a serving base station (e.g., a gNB-CU-CP) or a Near-RT RIC. In case of mobility for an RRC connected UE 105 for example, the RAN UE context needs to be exchanged over P2P interfaces, such as the Xn, in a distributed way to support the UE’s mobility (i.e. receive a mobility history information of a User Equipment. [0036] When the HO preparation request is received by a target node, the target node can retrieve the UE context information and other intelligence information from the (R)AN DSF in the background, without affecting the HO latency. In some embodiments, UE context information is enriched with history information such that it can be used by, for example, artificial intelligence and/or machine learning to identify )), and
a subscriber identifier (ID) of the UE from a base station, wherein the base station is where the UE is connected ([0030], Fig. 2, Fig. 6b, e.g. In some example embodiments, the UE context information may be saved in the (R)AN DSF with an associated identifier, such as a UE ID to be identifiable by any authorized network node (i.e. SIM ID), entity in the (R)AN, and/or core and/or management system (e.g., OAM). And, this identifier may be allocated by any authorized network node in the network in the form of, for example, a gNB-CU UE FI AP ID, a gNB-CU-CP UE El AP ID, an AMF UE NGAP ID, or any other type of identifier allocated by, for example a base station. [0064] The apparatus 10 may comprise memory, such as a subscriber identity module (SIM) 38, a removable user identity module (R-UIM), an eUICC, an UICC, U-SIM, and/or the like, which may store information elements related to a mobile subscriber (i.e. receiving history from a subscriber identifier (ID) of the UE associated with a base station) );
storing, by the RIC, the mobility history information of the UE based on the subscriber ID of the UE ([0030], e.g. In some example embodiments, the UE context information may be saved in the (R)AN DSF with an associated identifier (i.e. SIM or IMEI identification), such as a UE ID to be identifiable by any authorized network node, entity in the (R)AN, and/or core and/or management system (e.g., OAM). [0064] The apparatus 10 may comprise memory, such as a subscriber identity module (SIM) 38, a removable user identity module (R-UIM), an eUICC, an UICC, U-SIM, and/or the like (i.e. store the mobility history information of the UE based on the subscriber ID of the UE)).
BULAKCI teaches a method for retrieving context information for a user equipment in response to the retrieve request from a network node based on the context key; and sending the context information to the network node. However BULAKCI differs from the claimed invention in not specifically and clearly describing wherein
determining, by the RIC, a priority cell list based on the mobility history information of the UE.
However, in the analogous field of endeavor, KANNEATH teaches wherein
determine a priority cell list based on the mobility history information of the UE ([page 26, lines 9-18], e.g. As an example, if UE-B is in a first cell and the mobility history information indicates that UE-B has moved to a second cell from the first cell in the past, then the second cell may be given a higher priority compared to other cells (i.e. determine a priority cell list based on the mobility history)).
Therefore, it would have been obvious to one of ordinary skill in the art before the effective filing date of the invention to implement the method of KANNEATH within the method of BULAKCI. The motivation to combine references is that the combined system provides optimization of the usage of network resources. A terminal device may be utilized to enable better usage of resources and enhanced user experience to a user of the terminal device (See KANNEATH [Page 1, lines 5-8).
Regarding claim 9, BULAKCI in view of KANNEATH teaches all the limitations of claim 8. BULAKCI further teaches wherein mapping, by the RIC, the mobility history information with the subscriber ID of the UE ([0036], e.g. Moreover, the UE context information stored in the (R)AN DSF may be categorized per UE or categorized per UE group. In other words, the UE context information may map to a single UE or may map to a group of UEs. An example for a group of UEs can be in the scenario of vehicle-to-anything (V2X) communications, such as a V2X platooning use case. [0024] The RAN UE context (e.g., in 3GPP) and the UE context relevant information (e.g., in ORAN) may be stored in a central entity, such as a serving base station (e.g., a gNB-CU-CP) or a Near-RT RIC. (i.e. map the mobility history information with the subscriber ID of the UE)).
`KANNEATH further teaches wherein storing, by the RIC, the mapped mobility history information for determining the priority cell list ([page 26, lines 9-18], e.g. As an example, if UE-B is in a first cell and the mobility history information indicates that UE-B has moved to a second cell from the first cell in the past, then the second cell may be given a higher priority compared to other cells (i.e. store the mapped mobility history information for determining the priority cell list)).
The motivation to combine reference of KANNEATH within the method of BULAKCI before the effective filing date of the invention is that the new method provides fulfilling the need for improving the deployment and performance of communication systems, the concept of “plug-and-play” (e/g)NodeBs may be introduced. A network which may be able to use “plug-and-play” (e/g)NodeBs, may include, in addition to Home (e/g)NodeBs (H(e/g)nodeBs), a home node B gateway, or HNB-GW (not shown in FIG. 1). A HNB Gateway (HNB-GW), which may be installed within an operator’s network, may aggregate traffic from a large number of HNBs back to a core network (See KANNEATH page 15, lines 26-31).
Regarding claim 10, BULAKCI in view of KANNEATH teaches all the limitations of claim 8. KANNEATH further teaches wherein comprising: determining, by the RIC, the priority cell list based on the mobility history information, wherein the mobility history information of the UE comprises information regarding one or more cells of a plurality of cells visited by the UE during an inactive state or an idle state or in connected state; and transmitting, by the RIC, the priority cell list to the base station [page 26, lines 9-18], e.g. UE-B identifies 806 one or more cells and/or one or more carriers with a higher probability to be the next serving cell and/or carrier. The one or more cells and/or the one or more carriers may be identified, for example, based on the mobility history information of UE-B. For example, the mobility history information may comprise handovers and cell re-selections associated with UE-B (i.e. transmit the priority cell list to the base station). The mobility history information may also comprise the time that UE-B has spent in a given cell, …. As an example, if UE-B is in a first cell and the mobility history information indicates that UE-B has moved to a second cell from the first cell in the past, then the second cell may be given a higher priority compared to other cells, … . (i.e. cells visited by the UE during an inactive state or an idle state or in connected state; and transmit the priority cell list to the base station)).
The motivation to combine reference of KANNEATH within the method of BULAKCI before the effective filing date of the invention is that the new method provides fulfilling the need for improving the deployment and performance of communication systems, the concept of “plug-and-play” (e/g)NodeBs may be introduced. A network which may be able to use “plug-and-play” (e/g)NodeBs, may include, in addition to Home (e/g)NodeBs (H(e/g)nodeBs), a home node B gateway, or HNB-GW (not shown in FIG. 1). A HNB Gateway (HNB-GW), which may be installed within an operator’s network, may aggregate traffic from a large number of HNBs back to a core network (See KANNEATH page 15, lines 26-31).
Regarding claim 12, BULAKCI in view of KANNEATH teaches all the limitations of claim 8. BULAKCI further teaches wherein the mobility history information and the subscriber ID are received by the RIC from the base station using one of a first message and a second message via E2 interface ([0022], e.g. when the user equipment (UE) 105 is in RRC CONNECTED state, the UE’s 105 context (e.g., UE state information, security information, UE capability information, etc.) is kept by or within the RAN 110 and may be transmitted over a P2P interface, such as the Xn interface (see, e.g., 3GPP TS 38.300) between a source base station (e.g., source gNB) and a target base station (e.g., during mobility events) [0023] Both Non-RT RIC and Near-RT RIC employ SB A principles and utilize SBI for communicating internally and with each other. However, as shown in FIG. 3, the ORAN also employs P2P interfaces, such as the E2 interface towards E2 Nodes, rather than a service-based architecture including service-based interfaces (SBI) (i.e. mobility history information and the subscriber ID are received by the RIC from the base station using one of a first message and a second message via E2 interface)).
Regarding claim 13, BULAKCI in view of KANNEATH teaches all the limitations of claim 8. BULAKCI further teaches wherein the priority cell list and the subscriber ID are transmitted to the base station using a first message via E2 interface ([0023], Fig. 2, Fig. 4, e.g. However, as shown in FIG. 3, the ORAN also employs P2P interfaces, such as the E2 interface towards E2 Nodes, rather than a service-based architecture including service-based interfaces (SBI). [0046] At 502, the source gNB base station 402A may update the UE context information stored at the (R)AN DSF 450 over the SBI 142. For example, the UE context information for UE 405 A may be updated by sending, via the SBI interface, a message to the (R)AN DSF 450, so the (R)AN DSF can store the updated UE context information for a given UE, such as UE 405A and/or UEs 405B-C. This message may include a key, such as an identifier, to the stored UE context information being updated. For example, the identifier may be one or more of the following: a UE ID, a gNB ID, an E2 Node ID). [0048] At 504, the UE 405 A may be handed over from the source gNB base station 402Ato the target gNB base station 402B (i.e. handover requires priority cell list, therefore cell list also transmitted). This may cause or trigger a need for the updates in the context information for the UE 405 A. As noted, the UE context information may include UE capability information, UE identity information, a UE mobility state, user security parameters, UE historical information regarding mobility state, and the like (i.e. the priority cell list and the subscriber ID are transmitted to the base station using a first message via E2 interface)).
Regarding claim 14, BULAKCI in view of KANNEATH teaches all the limitations of claim 8. BULAKCI further teaches wherein the priority cell list and the subscriber ID are transmitted to the base station using a second message via E2 interface ([0023], Fig. 2, Fig. 4, e.g. However, as shown in FIG. 3, the ORAN also employs P2P interfaces, such as the E2 interface towards E2 Nodes, rather than a service-based architecture including service-based interfaces (SBI). [0048], e.g. At 504, the UE 405 A may be handed over from the source gNB base station 402Ato the target gNB base station 402B (i.e. handover requires priority cell list, therefore cell list also transmitted). This may cause or trigger a need for the updates in the context information for the UE 405 A. As noted, the UE context information may include UE capability information, UE identity information, a UE mobility state, user security parameters, UE historical information regarding mobility state, and the like (i.e. the priority cell list and the subscriber ID are transmitted to the base station using a second message via E2 interface)).
Regarding claim 15, BULAKCI teaches a base station ([0023], Fig. 6, e.g. In addition to 3 GPP technology, the Open-Radio Access Networks (O-RAN) Alliance is developing technology to provide open radio access networks. [0023] The Near-RT RIC 352 may, through the E2 interface 360, communicate with one or more E2 Nodes (i.e. base station), such as E2 node 315 (open control unit (O-CU) control plane (O-CU-CP), O- CU user plane (O-CU-UP), open distributed unit (O-DU), and open evolved NodeB (O-eNB)) for time sensitive management and control of the radio resources, such as interference management, handover management, Quality of Service (QoS) management, and radio connection management (i.e. a network comprising RAN intelligent controller (RIC) ), comprising: comprising:
a memory configured to store instructions executable by a processor; and the processor configured to execute the instructions stored in the memory ([0054], e.g. The network node 400 may include a network interface 402, a processor 420, and a memory 404, in accordance with some example embodiments. The network interface 402 may include wired and/or wireless transceivers to enable access to other nodes including base stations, other network nodes, the Internet, other networks, and/or other nodes (i.e. a memory configured to store instructions executable by a processor)); and the processor configured to execute the instructions stored in the memory ), and
thereby cause the base station where a User Equipment (UE) is connected to:
receive a mobility history information of the UE ([0024], e.g. The RAN UE context (e.g., in 3GPP) and the UE context relevant information (e.g., in ORAN) may be stored in a central entity, such as a serving base station (e.g., a gNB-CU-CP) or a Near-RT RIC. In case of mobility for an RRC connected UE 105 for example, the RAN UE context needs to be exchanged over P2P interfaces, such as the Xn, in a distributed way to support the UE’s mobility (i.e. receive a mobility history information of a User Equipment. [0036] When the HO preparation request is received by a target node, the target node can retrieve the UE context information and other intelligence information from the (R)AN DSF in the background, without affecting the HO latency. In some embodiments, UE context information is enriched with history information such that it can be used by, for example, artificial intelligence and/or machine learning to identify )); and
a subscriber identifier (ID) of the UE from the UE ([0030], Fig. 2, Fig. 6b, e.g. In some example embodiments, the UE context information may be saved in the (R)AN DSF with an associated identifier, such as a UE ID to be identifiable by any authorized network node (i.e. SIM ID), entity in the (R)AN, and/or core and/or management system (e.g., OAM). And, this identifier may be allocated by any authorized network node in the network in the form of, for example, a gNB-CU UE FI AP ID, a gNB-CU-CP UE El AP ID, an AMF UE NGAP ID, or any other type of identifier allocated by, for example a base station. [0064] The apparatus 10 may comprise memory, such as a subscriber identity module (SIM) 38, a removable user identity module (R-UIM), an eUICC, an UICC, U-SIM, and/or the like, which may store information elements related to a mobile subscriber (i.e. receiving history from a subscriber identifier (ID) of the UE associated with a base station) );
transmit the mobility history information and the subscriber ID of the UE to a Radio Access Network (RAN) Intelligent Controller (RIC) [0022], e.g. when the user equipment (UE) 105 is in RRC CONNECTED state, the UE’s 105 context (e.g., UE state information, security information, UE capability information, etc.) is kept by or within the RAN 110 and may be transmitted over a P2P interface, such as the Xn interface (see, e.g., 3GPP TS 38.300) between a source base station (e.g., source gNB) and a target base station (e.g., during mobility events) [0023] Both Non-RT RIC and Near-RT RIC employ SB A principles and utilize SBI for communicating internally and with each other. However, as shown in FIG. 3, the ORAN also employs P2P interfaces, such as the E2 interface towards E2 Nodes, rather than a service-based architecture including service-based interfaces (SBI) (i.e. mobility history information and the subscriber ID are received by the RIC from the base station using one of a first message and a second message via E2 interface)).
BULAKCI teaches a method for retrieving context information for a user equipment in response to the retrieve request from a network node based on the context key; and sending the context information to the network node. However BULAKCI differs from the claimed invention in not specifically and clearly describing wherein
receive a priority cell list from the RIC, wherein the RIC determines the priority cell list based on the mobility history information of the UE; and perform paging based on the priority cell list.
However, in the analogous field of endeavor, KANNEATH teaches wherein
receive a priority cell list from the RIC, wherein the RIC determines the priority cell list based on the mobility history information of the UE [page 26, lines 9-18], e.g. As an example, if UE-B is in a first cell and the mobility history information indicates that UE-B has moved to a second cell from the first cell in the past, then the second cell may be given a higher priority compared to other cells (i.e. determine a priority cell list based on the mobility history). [page 26, lines 9-18], e.g. UE-B identifies 806 one or more cells and/or one or more carriers with a higher probability to be the next serving cell and/or carrier. The one or more cells and/or the one or more carriers may be identified, for example, based on the mobility history information of UE-B. For example, the mobility history information may comprise handovers and cell re-selections associated with UE-B (i.e. transmit the priority cell list to the base station)); and
perform paging based on the priority cell list ([page 18, lines 11-18], e.g. the UE may need to periodically switch to NWK-B for RRC idle mode operations. The idle mode activities, which can be managed with periodic gaps, may comprise idle mode paging monitoring at the serving cell, SIB reception, and/or serving cell and neighbour cell RRM measurements of idle mode. In other words, the UE may need gaps for example for paging monitoring, SIB reception, and/or serving cell and neighbour cell measurements. Out of these activities, the gaps needed for paging monitoring may be determined and fixed by the paging occasion of NWK-B. [page 25, lines 18-21], Fig. 8, For example, UE-B may divide the gaps by giving a higher priority (i.e. a higher portion of the gaps) to the carriers and/or cells that it has identified 806 to have a higher probability to be the next serving cell and/or carrier (i.e. a cell and/or carrier with a higher priority to be re-selected) (i.e. perform paging based on the priority cell list)).
Therefore, it would have been obvious to one of ordinary skill in the art before the effective filing date of the invention to implement the method of KANNEATH within the method of BULAKCI. The motivation to combine references is that the combined system provides optimization of the usage of network resources. A terminal device may be utilized to enable better usage of resources and enhanced user experience to a user of the terminal device (See KANNEATH [Page 1, lines 5-8).
Regarding claim 17, BULAKCI in view of KANNEATH teaches all the limitations of claim 15. KANNEATH further teaches wherein the paging is performed when at least one of signaling message or data is received by the base station for the UE during an inactive state ([page 19, lines 13-16], e.g. In FIG. 2, UE-A 211 and UE-B 212 denote the protocol stacks of the UE for the first USIM and the second USIM, respectively. UE-A is in RRC connected mode 201 with a first base station of a first network (NWK-A) 220. UE-B is in RRC idle mode 202 (or RRC inactive mode) with a second base station of a second network (NWK-B) 230. UE-B determines 203 that periodic gaps are needed in order to perform fixed activities such as paging monitoring for NWK-B. UE-A transmits 204 a gap request message to the first base station to request a gap pattern from NWK-A for the paging monitoring on behalf of UE-B (i.e. the paging is performed when at least one of signaling message is received)).
The motivation to combine reference of KANNEATH within the method of BULAKCI before the effective filing date of the invention is that the new method provides fulfilling the need for improving the deployment and performance of communication systems, the concept of “plug-and-play” (e/g)NodeBs may be introduced. A network which may be able to use “plug-and-play” (e/g)NodeBs, may include, in addition to Home (e/g)NodeBs (H(e/g)nodeBs), a home node B gateway, or HNB-GW (not shown in FIG. 1). A HNB Gateway (HNB-GW), which may be installed within an operator’s network, may aggregate traffic from a large number of HNBs back to a core network (See KANNEATH page 15, lines 26-31).
Regarding claim 18, BULAKCI in view of KANNEATH teaches all the limitations of claim 15. KANNEATH further teaches wherein the mobility history information of the UE comprises information regarding one or more cells of a plurality of cells visited by the UE during an inactive state or an idle state or in connected state [page 26, lines 9-18], e.g. UE-B identifies 806 one or more cells and/or one or more carriers with a higher probability to be the next serving cell and/or carrier. The one or more cells and/or the one or more carriers may be identified, for example, based on the mobility history information of UE-B. For example, the mobility history information may comprise handovers and cell re-selections associated with UE-B (i.e. transmit the priority cell list to the base station). The mobility history information may also comprise the time that UE-B has spent in a given cell, …. As an example, if UE-B is in a first cell and the mobility history information indicates that UE-B has moved to a second cell from the first cell in the past, then the second cell may be given a higher priority compared to other cells, … . (i.e. cells visited by the UE during an connected state; and transmit the priority cell list to the base station)).
The motivation to combine reference of KANNEATH within the method of BULAKCI before the effective filing date of the invention is that the new method provides fulfilling the need for improving the deployment and performance of communication systems, the concept of “plug-and-play” (e/g)NodeBs may be introduced. A network which may be able to use “plug-and-play” (e/g)NodeBs, may include, in addition to Home (e/g)NodeBs (H(e/g)nodeBs), a home node B gateway, or HNB-GW (not shown in FIG. 1). A HNB Gateway (HNB-GW), which may be installed within an operator’s network, may aggregate traffic from a large number of HNBs back to a core network (See KANNEATH page 15, lines 26-31).
Regarding claim 19, BULAKCI in view of KANNEATH teaches all the limitations of claim 15. KANNEATH further teaches wherein the processor is configured to: set a timer for a predefined time period ([page 22, lines 5-9], e.g. UE-A may retry 507 the gap request on behalf of UE-B for example upon or after a handover in UE-A, or when one of the current services in UE-A is deactivated (i.e. a PDU session is released), or based on a timer (i.e. a timer is set for a predefined time period)); and
perform the paging [page 23, lines 1-5], e.g. if a handover is performed for UE-A, then the second gap request message 507 may be transmitted to a third base station instead of or in addition to the first base station. The first base station or the third base station may transmit 508 an RRC message to UE-A to accept the gap request of the second gap request message 507. UE-B may then use the gap pattern for paging monitoring for NWK-B (i.e. paging or the paging in one or more cells based on next highest priority)),
in one or more cells based on at least one of successful paging or the paging in one or more cells based on next highest priority of the priority cell list within the predefined time period ([page 26, lines 9-17], e.g. UE-B identifies 806 one or more cells and/or one or more carriers with a higher probability to be the next serving cell and/or carrier. The one or more cells and/or the one or more carriers may be identified, for example, based on the mobility history information of UE-B. For example, the mobility history information may comprise handovers and cell re-selections associated with UE-B. The mobility history information may also comprise the time that UE-B has spent in a given cell. As an example, if UE-B is in a first cell and the mobility history information indicates that UE-B has moved to a second cell from the first cell in the past, then the second cell may be given a higher priority compared to other cells (i.e. determining one or more cells based on next highest priority of the priority cell list within the predefined time period)).
The motivation to combine reference of KANNEATH within the method of BULAKCI before the effective filing date of the invention is that the new method provides fulfilling the need for improving the deployment and performance of communication systems, the concept of “plug-and-play” (e/g)NodeBs may be introduced. A network which may be able to use “plug-and-play” (e/g)NodeBs, may include, in addition to Home (e/g)NodeBs (H(e/g)nodeBs), a home node B gateway, or HNB-GW (not shown in FIG. 1). A HNB Gateway (HNB-GW), which may be installed within an operator’s network, may aggregate traffic from a large number of HNBs back to a core network (See KANNEATH page 15, lines 26-31).
Regarding claim 20, BULAKCI teaches a non-transitory computer readable medium including instructions for performing operation ([0066], e.g. In the context of this document, a “computer-readable storage medium” may be any non-transitory media that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer or data processor circuitry; computer-readable medium may comprise a non-transitory computer-readable storage medium ), comprising:
receive a mobility history information of a User Equipment (UE) [0024], e.g. The RAN UE context (e.g., in 3GPP) and the UE context relevant information (e.g., in ORAN) may be stored in a central entity, such as a serving base station (e.g., a gNB-CU-CP) or a Near-RT RIC. In case of mobility for an RRC connected UE 105 for example, the RAN UE context needs to be exchanged over P2P interfaces, such as the Xn, in a distributed way to support the UE’s mobility (i.e. receive a mobility history information of a User Equipment. [0036] When the HO preparation request is received by a target node, the target node can retrieve the UE context information and other intelligence information from the (R)AN DSF in the background, without affecting the HO latency. In some embodiments, UE context information is enriched with history information such that it can be used by, for example, artificial intelligence and/or machine learning to identify )); and
a subscriber identifier (ID) of the UE from a base station, wherein the base station is where the UE is connected ([0030], Fig. 2, Fig. 6b, e.g. In some example embodiments, the UE context information may be saved in the (R)AN DSF with an associated identifier, such as a UE ID to be identifiable by any authorized network node (i.e. SIM ID), entity in the (R)AN, and/or core and/or management system (e.g., OAM). And, this identifier may be allocated by any authorized network node in the network in the form of, for example, a gNB-CU UE FI AP ID, a gNB-CU-CP UE El AP ID, an AMF UE NGAP ID, or any other type of identifier allocated by, for example a base station. [0064] The apparatus 10 may comprise memory, such as a subscriber identity module (SIM) 38, a removable user identity module (R-UIM), an eUICC, an UICC, U-SIM, and/or the like, which may store information elements related to a mobile subscriber (i.e. receiving history from a subscriber identifier (ID) of the UE associated with a base station) );
store the mobility history information of the UE based on the subscriber ID of the UE ([0030], e.g. In some example embodiments, the UE context information may be saved in the (R)AN DSF with an associated identifier (i.e. SIM or IMEI identification), such as a UE ID to be identifiable by any authorized network node, entity in the (R)AN, and/or core and/or management system (e.g., OAM). [0064] The apparatus 10 may comprise memory, such as a subscriber identity module (SIM) 38, a removable user identity module (R-UIM), an eUICC, an UICC, U-SIM, and/or the like (i.e. store the mobility history information of the UE based on the subscriber ID of the UE)).
BULAKCI teaches a method for retrieving context information for a user equipment in response to the retrieve request from a network node based on the context key; and sending the context information to the network node. However BULAKCI differs from the claimed invention in not specifically and clearly describing wherein
determine a priority cell list based on the mobility history information of the UE.
However, in the analogous field of endeavor, KANNEATH teaches wherein
determine a priority cell list based on the mobility history information of the UE ([page 26, lines 9-18], e.g. As an example, if UE-B is in a first cell and the mobility history information indicates that UE-B has moved to a second cell from the first cell in the past, then the second cell may be given a higher priority compared to other cells (i.e. determine a priority cell list based on the mobility history)).
Therefore, it would have been obvious to one of ordinary skill in the art before the effective filing date of the invention to implement the method of KANNEATH within the method of BULAKCI. The motivation to combine references is that the combined system provides optimization of the usage of network resources. A terminal device may be utilized to enable better usage of resources and enhanced user experience to a user of the terminal device (See KANNEATH [Page 1, lines 5-8).
Allowable Subject Matter
Claims 4, 11 and 16 are objected to as being dependent upon a rejected base claim, but would be allowable, if rewritten in independent form including all of the limitations of the base claim and any intervening claims, and amending claims to overcome any objection(s) and /or rejection(s) set forth in this Office action.
Prior Art Record
The prior art made of record and not relied upon is considered pertinent
to applicant’s disclosure.
Brisebois; Arthur Richard ( US-20140315576-A1) - FEMTO CELL VISITATION HISTORY FOR LOCATION BASED SERVICES.
Kim; Sangwon (US-20190373442-A1) - METHOD FOR REPORTING MOBILITY HISTORY OF TERMINAL AND APPARATUS FOR SUPPORTING SAME.
Kim; Woo Seong (US-10834655-B2) - Method and device for preserving mobility information in terminal state transition and effectively re-accessing in heterogeneous cell network in mobile communication system.
ARSHAD; Malik Wahaj (US-20220295257-A1) - ENHANCEMENTS IN MOBILITY HISTORY INFORMATION.
JUNG; Sangyeob ()US-20230084366-A1 - METHOD AND DEVICE FOR COLLECTING AND REPORTING MOBILITY HISTORY INFORMATION IN NEXT-GENERATION MOBILE COMMUNICATION SYSTEM.
Liu; Huichun (US-12309649-B2) - User equipment (UE) mobility history information management.
Xu; Jian (US-12414199-B2) - Method and apparatus for mobility management in wireless communication system.
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to Mahendra Patel whose telephone number is (571) 270-7499. The examiner can normally be reached on 9:30 AM to 5:30 PM (EST) .
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, Applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Anthony Addy can be reached on (571) 272-7795(571) 272-7795. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of an application may be obtained from the Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAIR only. For more information about the PAIR system, see http://pair-direct.uspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free) ? If you would like assistance from a USPTO customer Service Representative or access to the automated information system, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/MAHENDRA R PATEL/ Primary Examiner, Art Unit 2645
Prosecution Insights