DETAILED ACTION
This is in response to Applicant’s reply dated 8/5/26. Claims 1, 3-12, 14-19 and 23 have been examined. Claims 2, 13, 20-22 and 24-26 have been cancelled.
Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA . 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 (i.e., changing from AIA to pre-AIA ) 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 § 102
The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a)(2) the claimed invention was described in a patent issued under section 151, or in an application for patent published or deemed published under section 122(b), in which the patent or application, as the case may be, names another inventor and was effectively filed before the effective filing date of the claimed invention.
Claim(s) 1, 3-12, 14-19 and 23 are rejected under 35 U.S.C. 102(a)(2) as being unpatentable by Ishii (US 2025/0063483).
Regarding Claim 1 (Currently Amended),
A method for processing network slices, applied to a network device, the method comprising:
mapping, based on first information of a serving cell, at least one network slice supported by a neighboring cell into at least one slice group, the first information representing mapping relationships between network slices and slice groups [Ishii: 0153; in still yet another of its example aspects the technology disclosed herein concerns an access node which supports one or more network slices … the processor circuitry is configured to generate neighboring cell information configured to be used by the wireless terminal to perform a cell reselection procedure; the neighboring cell information comprises an identity of a neighboring cell; network slice support information indicating one or more network slices supported in the neighboring cell; and mapping configuration referencing information referring to a corresponding mapping configuration to be used for the network slice support information; in a case that the mapping configuration referencing information refers to a mapping configuration that was configured to and is stored in the wireless terminal, upon receipt of the neighboring cell information by the wireless terminal the stored mapping configuration is configured to be retrieved and used for mapping the at least one network slice group index to one or more corresponding network slice identifiers; 0271; each of the one or more network slice identifiers is associated with a radio band(s) and an area scope indication; the radio band(s) indicate a frequency domain interval(s) on which a network slice identified by the each of the one or more network slice identifiers is supported; the area scope indication indicates an area in which the network slices is supported on the radio band(s); 0296; Act 22A-3 comprises receiving, from a first cell, a message comprising network slice band association … the network slice band association information may comprise one or more network slice identifiers, each of the one or more network slice identifiers identifying a network slice … Act 22A-6 comprises determining whether or not the network slice band association information needs to be reacquired from the second cell; the determination is based on the area scope indication in the stored network slice band association information, the area scope indication corresponding to the selected at least one network slice. If the second cell is within the area indicated by the area scope indication, as shown in Act 22A-7, a reacquisition procedure is initiated to reacquire the network slice band association information from the second cell; 0370; Fig. 35B], and
sending second information, the second information at least comprising at least one slice group identifier and a frequency priority of the at least one slice group [Ishii: 0249; Fig. 14; the access node 28 may, for example, be a gNB. Act 14-1 comprises generating an RRC message comprising network slice band association information … the network slice band association information may comprise a list of network slice identifiers, each of the network slice identifiers identifying a network slice, each of some of the network slice identifiers being associated with a corresponding radio band(s); 0271; each of the one or more network slice identifiers is associated with a radio band(s) and an area scope indication; the radio band(s) indicate a frequency domain interval(s) on which a network slice identified by the each of the one or more network slice identifiers is supported; the area scope indication indicates an area in which the network slices is supported on the radio band(s); 0146; each of the one or more frequency priorities indicates a priority of the each of the one or more radio frequencies associated with one corresponding set of the one or more sets of identities of network slices comprised in the one or more neighboring cell information elements for the each of the one or more radio frequencies; 0149; in an example embodiment and mode, the access node comprises processor circuitry and transmitter circuitry; the processor circuitry is configured to generate dedicated frequency priority information associated with a network slice; 0296; Fig. 22A; the network slice band association information may comprise one or more network slice identifiers, each of the one or more network slice identifiers identifying a network slice, each of the one or more network slice identifiers being associated with a radio band(s) and an area scope indication, the radio band(s) indicating a frequency domain interval(s) on which a network slice identified by the each of the one or more network slice identifiers is supported, the area scope indication indicating an area in which the network slices is supported on the radio band(s); 0411; specifically, for a desired or intended slice, the wireless terminal may select/reselect a cell based on cell selection/reselection criteria that take into account the priority of radio bands/frequencies with regard to the desired or intended slices].
Regarding Claim 3,
wherein the first information corresponds to one or more tracking areas (TAs) [Ishii: 0271; in the example embodiment and mode of FIG. 19, the network slice band association information comprises one or more network slice identifiers. Each of the one or more network slice identifiers serves to identify a network slice. Each of the one or more network slice identifiers is associated with a radio band(s) and an area scope indication; 0272; the area scope indicator, also herein referred to as “area scope”, may indicate an area(s)/coverage(s), such as one or more PLMNs, one or more tracking/registration areas, one or more cells …; for example, the area scope may comprise a list of tracking area identities or cell identities … if the area scope is type “Registration Area”, the validity area may be the current registration area (specified by one or more tracking area identities (TAIs) or tracking area codes (TACs))].
Regarding Claim 4,
further comprising: acquiring the mapping relationships between the network slices and the slice groups [Ishii: 0296; Act 22A-3 comprises receiving, from a first cell, a message comprising network slice band association … the network slice band association information may comprise one or more network slice identifiers, each of the one or more network slice identifiers identifying a network slice … Act 22A-6 comprises determining whether or not the network slice band association information needs to be reacquired from the second cell; the determination is based on the area scope indication in the stored network slice band association information, the area scope indication corresponding to the selected at least one network slice. If the second cell is within the area indicated by the area scope indication, as shown in Act 22A-7, a reacquisition procedure is initiated to reacquire the network slice band association information from the second cell; 0370; Fig. 35B].
Regarding Claim 5,
wherein acquiring the mapping relationships between the network slices and the slice groups comprises: receiving the mapping relationships between the network slices and the slice groups configured by a network management device; or receiving the mapping relationships between the network slices and the slice groups sent by a core network device [Ishii: 0481; in the particular example implementation shown in FIG. 52, the mapping of a network slice group to one or more network slice identifiers occurs in the management entity 26(52), and in particular is the mapping is generated by customized mapping configuration generator 360. But in another example implementation, a unit comparable to customized mapping configuration generator 360 is provided in access node 28(52), e.g., in node processor circuitry 70(52); the mapping, referred as a mapping configuration, may comprise one or more groups, each group comprising an index, or an identifier, of the group, a group index, and one or more S-NSSAIs that belong to the group].
Regarding Claim 6,
wherein in a case of receiving the mapping relationships between the network slices and the slice groups configured by the network management device, the method further comprises: sending, to the core network device, a subset or a universal set of the mapping relationships between the network slices and the slice groups configured by the network management device [Ishii: 0503; the AMF may also generate a Registration Accept message comprising the Allowed NSSAI, the Configured NSSAI and/or the NSSRG information. The AMF may further generate a customized mapping configuration from the Configured NSSAI and incorporate the customized mapping information into the Registration Accept message; 0502; upon receiving the Registration Request message, as act 57-5 the serving cell, a cell served by an access node, may package the Registration Request message into an inter-node (gNB-AMF) message container, such as one of the messages per 3GPP TS 38.413 NG Application Protocol (NGAP), and send it to an AMF of the serving PLMN; 0395; That is, in principle, one or more subsets of the serving cell network slice information in a system information block, preferably a system information block which carries minimum SI, may be shared by the neighboring cell network slice information by referencing, in a case that the serving cell and the neighboring cell share a common network slice(s) within a same PLMN(s); 0475; in the example embodiment and mode of FIG. 52, the management entity 26(52) may comprise customized mapping configuration generator 360; the customized configuration mapping generator 360 may be realized or comprised by core network entity processor circuitry 80(52); 0476; the access node 28(52) of the example embodiment and mode of FIG. 52 comprises node processor circuitry 70(52), node transceiver circuitry 72, and interface 74 to core network (CN) 24; 0477; or example, node processor circuitry 70(52) is shown as including network slice group indices memory 364 from which the network slice group index message generator 365 may obtain the network slice group index for inclusion in a particular system information block; 0481; in the particular example implementation shown in FIG. 52, the mapping of a network slice group to one or more network slice identifiers occurs in the management entity 26(52), and in particular is the mapping is generated by customized mapping configuration generator 360. But in another example implementation, a unit comparable to customized mapping configuration generator 360 is provided in access node 28(52), e.g., in node processor circuitry 70(52); the mapping, referred as a mapping configuration, may comprise one or more groups, each group comprising an index, or an identifier, of the group, a group index, and one or more S-NSSAIs that belong to the group].
Regarding Claim 7,
further comprising: acquiring the at least one network slice supported by the neighboring cell [Ishii: 0153; in still yet another of its example aspects the technology disclosed herein concerns an access node which supports one or more network slices … the processor circuitry is configured to generate neighboring cell information configured to be used by the wireless terminal to perform a cell reselection procedure; the neighboring cell information comprises an identity of a neighboring cell; network slice support information indicating one or more network slices supported in the neighboring cell].
Regarding Claim 8,
wherein acquiring the at least one network slice supported by the neighboring cell comprises: receiving the at least one network slice supported by the neighboring cell sent by a network device of the neighboring cell [Ishii: 0153; in still yet another of its example aspects the technology disclosed herein concerns an access node which supports one or more network slices … the processor circuitry is configured to generate neighboring cell information configured to be used by the wireless terminal to perform a cell reselection procedure; the neighboring cell information comprises an identity of a neighboring cell; network slice support information indicating one or more network slices supported in the neighboring cell; 0395; That is, in principle, one or more subsets of the serving cell network slice information in a system information block, preferably a system information block which carries minimum SI, may be shared by the neighboring cell network slice information by referencing, in a case that the serving cell and the neighboring cell share a common network slice(s) within a same PLMN(s); 0156; FIG. 1 shows by vertical dotted lines that the radio access network (RAN) 22 and core network (CN) 24 may possibly be utilized by plural PLMNs such as PLMN1-PLMNj; 0793; the neighboring cell information may be generated by neighboring cell information generator 550(98) of the access node 28(98) of FIG. 98].
Regarding Claim 9,
further comprising: in a case that at least one slice of the at least one network slice supported by the neighboring cell cannot be mapped into slice group(s) based on the first information, sending third information to a core network device, wherein the third information is at least used for requesting to assign mapping relationship(s) to the at least one slice that cannot be mapped into the slice group(s); and receiving new mapping relationship(s) sent by the core network device; and mapping the at least one slice that cannot be mapped into the slice group(s) into slice group(s) by using the new mapping relationship(s) [Ishii: 0600; Act 72-3 comprises determining, based on the area scope information and the at least one area identity, whether or not the mapping configuration is valid in the second cell. The determination of act 72-3 may be performed by mapping configuration validation controller 412 The mapping configuration may be valid in the second cell in a case that the at least one area identity is indicated by the area scope information. Otherwise, it may be invalid in the second cell, which may result in initiating a registration procedure to obtain a new mapping configuration; 0805; the UE initiates a PLMN selection to select a PLMN different from a currently serving PLMN, in a case that a desired network slice(s) is not supported in any radio bands for a currently serving PLMN; 0560; in addition, during the cell selection procedure, candidate cells on the at least one carrier frequency specified in the carrier frequency list associated with the at least one of the network slices in the Rejected NSSAI may be evaluated, and a strongest suitable cell among the evaluated candidate cells may be selected; 0370; the message may be further used by the wireless terminal 30(26) to initiate a cell reselection procedure to select a second cell operated on the second radio band, in a case that the at least one network slice is supported on the second radio band but not supported on the first radio band. In addition, the message may be further used by the wireless terminal 30(26) to initiate a PLMN selection procedure to select a PLMN different from a currently serving PLMN, in a case that at least one network slice is not supported in any radio band(s)].
Regarding Claim 10,
further comprising: updating the first information by using the new mapping relationship(s) [Ishii: 0600; Act 72-3 comprises determining, based on the area scope information and the at least one area identity, whether or not the mapping configuration is valid in the second cell. The determination of act 72-3 may be performed by mapping configuration validation controller 412 The mapping configuration may be valid in the second cell in a case that the at least one area identity is indicated by the area scope information. Otherwise, it may be invalid in the second cell, which may result in initiating a registration procedure to obtain a new mapping configuration].
Regarding Claim 11,
wherein the second information is broadcast [Ishii: 0188; RAN may broadcast barring control information (i.e. a list of barring parameters associated with operator-defined access categories) to minimize the impact of congested slices; 0227; n the example embodiment and mode of FIG. 9A the network slice band association information may be broadcasted in system information, e.g. in one or more system information blocks, SIBs; 0279; FIG. 19B shows an example embodiment and mode of the generic system of FIG. 19A in which the network slice band association information, NSBAI, including the area scope indication is carried in system information transmitted by access node 28 … thus, in the example embodiment and mode of FIG. 19B the message 155 is broadcasted system information].
Regarding Claim 12 (Currently Amended),
A method for processing network slices, applied to a terminal, the method comprising:
receiving second information, the second information at least comprising at least one slice group identifier of a neighboring cell and a frequency priority of the at least one slice group; determining at least one network slice supported by the neighboring cell based on the second information and fourth information, the fourth information representing mapping relationships between network slices and slice groups [Ishii: 0152; in still yet another of its example aspects the technology disclosed herein concerns a wireless terminal which supports one or more network slices. Each of the one or more network slices provides a designated service. In an example embodiment and mode the wireless terminal comprises receiver circuitry and processor circuitry. The receiver circuitry is configured to receive: (1) in a first registration area, a mapping configuration configuring one or more network slice groups for the first registration area; and (2) in a second registration area, neighboring cell information. The neighboring cell information comprises an identity of a neighboring cell; network slice support information indicating one or more network slices supported in the neighboring cell and including at least one network slice group index; and mapping configuration referencing information referencing information referring to a corresponding mapping configuration to be used for the network slice support information; upon receipt of the neighboring cell information, retrieve and use the stored mapping configuration to map the at least one network slice group index to one or more corresponding network slice identifiers, in a case that the stored mapping configuration is referred by the mapping configuration referencing information and is preserved in the wireless terminal; and (c) perform a cell reselection procedure based on the neighboring cell information; 0249; Fig. 14; the access node 28 may, for example, be a gNB. Act 14-1 comprises generating an RRC message comprising network slice band association information … the network slice band association information may comprise a list of network slice identifiers, each of the network slice identifiers identifying a network slice, each of some of the network slice identifiers being associated with a corresponding radio band(s); 0271; each of the one or more network slice identifiers is associated with a radio band(s) and an area scope indication; the radio band(s) indicate a frequency domain interval(s) on which a network slice identified by the each of the one or more network slice identifiers is supported; the area scope indication indicates an area in which the network slices is supported on the radio band(s); 0296; Act 22A-3 comprises receiving, from a first cell, a message comprising network slice band association … the network slice band association information may comprise one or more network slice identifiers, each of the one or more network slice identifiers identifying a network slice … Act 22A-6 comprises determining whether or not the network slice band association information needs to be reacquired from the second cell; the determination is based on the area scope indication in the stored network slice band association information, the area scope indication corresponding to the selected at least one network slice. If the second cell is within the area indicated by the area scope indication, as shown in Act 22A-7, a reacquisition procedure is initiated to reacquire the network slice band association information from the second cell; 0370; Fig. 35B; 0146; each of the one or more frequency priorities indicates a priority of the each of the one or more radio frequencies associated with one corresponding set of the one or more sets of identities of network slices comprised in the one or more neighboring cell information elements for the each of the one or more radio frequencies; 0149; in an example embodiment and mode, the access node comprises processor circuitry and transmitter circuitry; the processor circuitry is configured to generate dedicated frequency priority information associated with a network slice; 0296; Fig. 22A; the network slice band association information may comprise one or more network slice identifiers, each of the one or more network slice identifiers identifying a network slice, each of the one or more network slice identifiers being associated with a radio band(s) and an area scope indication, the radio band(s) indicating a frequency domain interval(s) on which a network slice identified by the each of the one or more network slice identifiers is supported, the area scope indication indicating an area in which the network slices is supported on the radio band(s); 0411; specifically, for a desired or intended slice, the wireless terminal may select/reselect a cell based on cell selection/reselection criteria that take into account the priority of radio bands/frequencies with regard to the desired or intended slices]; and
performing cell reselection based on the at least one network slice supported by the neighboring cell [Ishii: 0152; upon receipt of the neighboring cell information, retrieve and use the stored mapping configuration to map the at least one network slice group index to one or more corresponding network slice identifiers, in a case that the stored mapping configuration is referred by the mapping configuration referencing information and is preserved in the wireless terminal; and (c) perform a cell reselection procedure based on the neighboring cell information].
Regarding Claim 14-19, which recite the same claim limitations as those in claims 3-5 and 7-11 above, the same rationale of rejection as presented in claims 3-5 and 7-11 is applicable.
Regarding Claim 23, which recites a terminal having the same claim limitations as those in claim 12 above, the same rationale of rejection as presented in claim 12 is applicable.
Response to Arguments
Applicant's arguments filed 8/5/26 have been fully considered but they are not persuasive.
Applicant argues regarding claims 1 and 12 on pages 6-8 of the Remarks section that Ishii does not teach a frequency priority of the at least one slice group.
Examiner’s Response:
Ishii teaches that ach of the one or more frequency priorities indicates a priority of the each of the one or more radio frequencies associated with one corresponding set of the one or more sets of identities of network slices comprised in the one or more neighboring cell information elements for the each of the one or more radio frequencies [Ishii: 0146]. In an example embodiment and mode, the access node comprises processor circuitry and transmitter circuitry; the processor circuitry is configured to generate dedicated frequency priority information associated with a network slice [Ishii: 0149]. In other words, a frequency priority information is not only associated with a network slice but also associated with a corresponding set of network slices. Thus, a frequency priority information being associated with a network slice as well as a corresponding set of network slices in Ishii reads on a frequency priority of the at least one “slice group”.
Conclusion
THIS ACTION IS MADE FINAL. Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a).
A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any nonprovisional extension fee (37 CFR 1.17(a)) pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to SAAD A WAQAS whose telephone number is (571)270-5642. The examiner can normally be reached 8:30 - 5:00 PM.
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, Marcus Smith can be reached at (571) 270-1096. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
SAAD A. WAQAS
Primary Examiner
Art Unit 2468
/Saad A. Waqas/Primary Examiner, Art Unit 2468
