DETAILED ACTION
This is in response to US App. 18/457,013. Claims 1-20 have been examined.
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 Objections
Claims 10, 13, 14, and 18 are objected to because of the following informalities: claim 10 should end with a period instead of with a semi-colon. The use of “and/or” in claims 10, 13, 14, and 18 makes the limitations at issue in these claims unclear in scope. Appropriate correction is required.
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-20 are rejected under 35 U.S.C. 102(a)(2) as being unpatentable by Ying et al. (US 2023/0189393; hereafter Ying).
Regarding Claim 1,
A communication method, comprising:
sending, by a terminal device, request information to a network device, wherein the request information is configured to indicate a first transmission requirement, and the request information is access stratum information [Ying: 0076; in a mode in which a network device schedules a PC5 communication resource for PC5 communication of the terminal device, when the UE needs to send data through the PC5 interface, the UE requests and obtains a corresponding PC5 communication resource from the RAN node through the Uu interface; 0042; the second terminal device searches for the transmission requirement of the first V2X service from transmission requirements of all V2X services stored in the second terminal device, or learns of the transmission requirement of the first V2X service by interacting with another device (for example, a network device); 0098; in a possible implementation, when an application layer of the first terminal device triggers the first V2X service, for example, when a V2X message that needs to be sent for the first V2X service is generated, a V2X layer of the first terminal device may obtain the transmission requirement (the service requirement and/or the message pattern) of the first V2X service, and send the transmission requirement to an access stratum (AS) of the first terminal device; the access stratum of the first terminal device determines the first DRX parameter based on the transmission requirement of the first V2X service; in a possible implementation, further, the V2X layer of the first terminal device may send DRX indication information to the access stratum of the first terminal device, to indicate the access stratum of the first terminal device to obtain the DRX parameter for the first terminal device].
Note:
Specification teaches that “the present disclosure proposes that the terminal device sends the request information of the access stratum (AS) layer …” [para. 0037]. Access stratum information has been construed as information request coming from AS layer.
Regarding Claim 2,
further comprising: receiving, by the terminal device, first indication information from the network device, wherein the first indication information is configured to indicate a first corresponding relationship between at least one transmission requirement and at least one transmission resource, and determining, by the terminal device, the first transmission requirement from the at least one transmission requirement, wherein a transmission resource corresponding to the first transmission requirement in the at least one transmission resource is a first transmission resource [Ying: 0042; the second terminal device searches for the transmission requirement of the first V2X service from transmission requirements of all V2X services stored in the second terminal device, or learns of the transmission requirement of the first V2X service by interacting with another device (for example, a network device); 0099; … the V2X layer of the first terminal device obtains the service requirement of the first V2X service (for example, the QoS parameter of the PC5 QoS flow for transmitting the first V2X service) …; 0100; a mapping relationship between the following policy/parameter information may be configured on the first terminal device: a V2X service type (for example, a provider service identifier (PSID) or an application identifier (ITS-AID)) and/or a V2X application requirement (for example, a priority requirement, a reliability requirement, a delay requirement, or a range requirement) of the V2X service type, and a PC5 QoS parameter (namely, a 5G QoS identifier (PC5 5QI), PQI) and/or another parameter (for example, a maximum flow bit rate (MFBR)/(GFBR)); the terminal device may obtain a corresponding PC5 QoS parameter based on a service type of a V2X service triggered by the application layer and/or the V2X application requirement of the V2X service type, and the foregoing mapping relationship stored on the terminal device].
Regarding Claim 3,
wherein the first indication information is dedicated information of the terminal device, public information, or dedicated information of a group of terminal devices, wherein the group of terminal devices comprises the terminal device [Ying: 0042; the second terminal device searches for the transmission requirement of the first V2X service from transmission requirements of all V2X services stored in the second terminal device, or learns of the transmission requirement of the first V2X service by interacting with another device (for example, a network device); 0099; … the V2X layer of the first terminal device obtains the service requirement of the first V2X service (for example, the QoS parameter of the PC5 QoS flow for transmitting the first V2X service)].
Regarding Claim 4,
wherein the request information is configured to request that the first transmission resource corresponding to the first transmission requirement is configured for transmission data [Ying: 0098; in a possible implementation, further, the V2X layer of the first terminal device may send DRX indication information to the access stratum of the first terminal device, to indicate the access stratum of the first terminal device to obtain the DRX parameter for the first terminal device].
Regarding Claim 5,
further comprising: receiving, by the terminal device, first response information from the network device, wherein the first response information is configured to configure the first transmission resource or to confirm that the first transmission resource is configured for transmission data, and the first transmission resource is a transmission resource that meets the first transmission requirement [Ying: 0100; a mapping relationship between the following policy/parameter information may be configured on the first terminal device: a V2X service type (for example, a provider service identifier (PSID) or an application identifier (ITS-AID)) and/or a V2X application requirement (for example, a priority requirement, a reliability requirement, a delay requirement, or a range requirement) of the V2X service type, and a PC5 QoS parameter (namely, a 5G QoS identifier (PC5 5QI), PQI) and/or another parameter (for example, a maximum flow bit rate (MFBR)/(GFBR)); the terminal device may obtain a corresponding PC5 QoS parameter based on a service type of a V2X service triggered by the application layer and/or the V2X application requirement of the V2X service type, and the foregoing mapping relationship stored on the terminal device].
Regarding Claim 6,
wherein the first transmission resource is a dynamic grant resource, a configuration grant resource, an aperiodic resource, a periodic resource, or a semi-persistent resource [Ying: 0092; the message pattern may also be referred to as a service pattern, and may be a sending frequency or a sending period for sending a V2X message … a period of sending a V2X message for any V2X service by the first terminal device may be 100 ms; 0097; a PC5 QoS flow for transmitting the first V2X service is the first PC5 QoS flow and the second PC5 QoS flow. If a delay included in the QoS parameter of the first PC5 QoS flow does not exceed 80 ms and the message pattern of the first V2X service is the sending period of 100 ms, the first terminal device may determine the DRX parameter corresponding to the first PC5 QoS flow as 70 ms, 60 ms, or the like].
Regarding Claim 7,
wherein the first transmission requirement is configured to configure, adjust or indicate at least one of: a parameter of a radio bearer, a rate of a data radio bearer (DRB), DRB reliability, a transmission parameter, a parameter of QoS, a parameter of a logical channel, a transmission delay, and the first transmission resource [Ying: 0099; … the V2X layer of the first terminal device obtains the service requirement of the first V2X service (for example, the QoS parameter of the PC5 QoS flow for transmitting the first V2X service)].
Regarding Claim 8,
wherein the first transmission requirement corresponds to QoS of a non-access stratum, or the first transmission requirement is a transmission requirement of the access stratum [Ying: 0098; in a possible implementation, when an application layer of the first terminal device triggers the first V2X service, for example, when a V2X message that needs to be sent for the first V2X service is generated, a V2X layer of the first terminal device may obtain the transmission requirement (the service requirement and/or the message pattern) of the first V2X service, and send the transmission requirement to an access stratum (AS) of the first terminal device; the access stratum of the first terminal device determines the first DRX parameter based on the transmission requirement of the first V2X service; in a possible implementation, further, the V2X layer of the first terminal device may send DRX indication information to the access stratum of the first terminal device, to indicate the access stratum of the first terminal device to obtain the DRX parameter for the first terminal device].
Regarding Claim 9,
wherein the first transmission requirement corresponds to a requirement of a radio resource bearer, a requirement of a protocol data unit (PDU) session, a requirement of a QoS flow, or a transmission requirement of the terminal device [Ying: 0042; the second terminal device searches for the transmission requirement of the first V2X service from transmission requirements of all V2X services stored in the second terminal device, or learns of the transmission requirement of the first V2X service by interacting with another device (for example, a network device); 0099; … the V2X layer of the first terminal device obtains the service requirement of the first V2X service (for example, the QoS parameter of the PC5 QoS flow for transmitting the first V2X service)].
Regarding Claim 10,
further comprising: sending, by the terminal device, second indication information to the network device, wherein the second indication information is configured to indicate capability information of the terminal device or indicate that the terminal device is of a target type, and the second indication information comprises one or more of: information that the terminal device supports group data transmission, information that the terminal device supports transmission of training data, information that the terminal device supports collection of training data, information that the terminal device supports sending the request information, information that the terminal device is connected to a target application layer or a target agent [Ying: 0098; in a possible implementation, when an application layer of the first terminal device triggers the first V2X service, for example, when a V2X message that needs to be sent for the first V2X service is generated, a V2X layer of the first terminal device may obtain the transmission requirement (the service requirement and/or the message pattern) of the first V2X service, and send the transmission requirement to an access stratum (AS) of the first terminal device; the access stratum of the first terminal device determines the first DRX parameter based on the transmission requirement of the first V2X service; 0100; the terminal device may obtain a corresponding PC5 QoS parameter based on a service type of a V2X service triggered by the application layer and/or the V2X application requirement of the V2X service type, and the foregoing mapping relationship stored on the terminal device], information that the terminal device is of an artificial intelligence type, and information that the terminal device supports a target agent; and/or receiving, by the terminal device, configuration information from the network device, wherein the configuration information is configured to configure a resource bearing the request information;
Regarding Claim 11,
wherein the request information is carried in at least one of an RRC message, a MAC CE, and a physical layer signaling; and/or the request information is one of assistance information of the terminal device, a measurement report, a scheduling request (SR) message, a random access message, and dedicated information for requesting a transmission resource [Ying: 0131; the first terminal device may further send, to the network device, the first DRX parameter accepted by the second terminal device (the case 1), send, to the network device, the second DRX parameter re-determined by the second terminal device (the case 2), or send the first DRX parameter applicable to the first terminal device and the second DRX parameter applicable to the second network device to the network device (the case 3); for example, the parameter or the parameters is/are sent to the network device by using a radio resource control (RRC) message, so that the network device schedules a PC5 communication resource for the first V2X service of the first terminal device and the second terminal device based on the DRX parameter for performing PC5 communication of the first V2X service by the first terminal device and the second terminal device].
Regarding Claim 12,
wherein the request information comprises one or more of: indication information for requesting to change a transmission requirement, the first transmission requirement, identification information of the first transmission requirement, a requirement or configuration information of the first transmission resource, identification information of the first transmission resource, a value of a transmission parameter, a value range of the transmission parameter, and level information of the transmission parameter, wherein the first transmission resource is a resource that meets the first transmission requirement, and the transmission parameter comprises one or more of: a rate of a data radio bearer (DRB), DRB reliability, and a transmission delay [Ying: 0098; in a possible implementation, further, the V2X layer of the first terminal device may send DRX indication information to the access stratum of the first terminal device, to indicate the access stratum of the first terminal device to obtain the DRX parameter for the first terminal device].
Regarding Claim 13,
wherein the level information of the transmission parameter has a second corresponding relationship with one or more of one value of the transmission parameter, one value range of the transmission parameter, the first transmission resource, and the identification information of the first transmission resource [Ying: 0101; when determining the first DRX parameter of the first V2X service, the first terminal device may further determine the first DRX parameter based on the transmission requirement of the first V2X service and a transmission requirement (the transmission requirement may be a service requirement and/or a message pattern, or may be a specific DRX parameter) of one or more third V2X services that are being performed by the first terminal device; the third V2X service that is being performed by the first terminal device may be one or more of a V2X service in unicast PC5 communication between the first terminal device and another terminal device (which is not the second terminal device), a V2X service in multicast PC5 communication that is being performed by the first terminal device, and a V2X service in broadcast PC5 communication that is being performed by the first terminal device]; and/or the value of the transmission parameter or the value range of the transmission parameter have a third corresponding relationship with one or more of the first transmission resource and the identification information of the first transmission resource; wherein the second corresponding relationship and/or the third corresponding relationship are defined by a protocol, pre-configured by the network device, or pre-configured by a core-network device.
Regarding Claim 14,
wherein the request information is configured to request a temporary resource, and the first transmission resource is valid for a first time interval [Ying: 0090; a first terminal device determines a first DRX parameter based on a transmission requirement of a first V2X service; 0091; the transmission requirement includes a service requirement and/or a message pattern; 0092; in this embodiment of this application, the message pattern may also be referred to as a service pattern, and may be a sending frequency or a sending period for sending a V2X message … in an example, a message pattern used by the first terminal device to perform any V2X service may be 100 ms, that is, a period of sending a V2X message for any V2X service by the first terminal device may be 100 ms], or wherein the first transmission requirement is a temporary requirement, and the first transmission requirement is valid for a second time interval; wherein the request information comprises the first time interval or the second time interval, and/or the first time interval or the second time interval is preconfigured by a core-network device, and/or the first time interval or the second time interval is preconfigured by the network device.
Regarding Claim 15,
wherein the sending, by the terminal device, the request information to the network device, comprising: sending, by the terminal device, the request information to the network device in response to a trigger condition being met, wherein the trigger condition comprises one or more of: a current transmission resource not meeting the first transmission requirement, a target object not supporting transmission of group data or training data, a variation of a transmission requirement being greater than or equal to a threshold value, and a third indication information being received, wherein the target object is an application layer, an agent, or a target cell, and the third indication information is configured to indicate change of the agent [Ying: 0099-0100; in an example, that the V2X layer of the first terminal device obtains the service requirement of the first V2X service (for example, the QoS parameter of the PC5 QoS flow for transmitting the first V2X service) includes: … the terminal device may obtain a corresponding PC5 QoS parameter based on a service type of a V2X service triggered by the application layer and/or the V2X application requirement of the V2X service type, and the foregoing mapping relationship stored on the terminal device].
Regarding Claim 16,
wherein before the sending, by the terminal device, the request information to the network device, the method further comprises: receiving, by the terminal device, fourth indication information from the network device, wherein the fourth indication information is configured to indicate that the terminal device is allowed or enabled to send the request information [Ying: 0042; the second terminal device searches for the transmission requirement of the first V2X service from transmission requirements of all V2X services stored in the second terminal device, or learns of the transmission requirement of the first V2X service by interacting with another device (for example, a network device); 0098; in a possible implementation, when an application layer of the first terminal device triggers the first V2X service, for example, when a V2X message that needs to be sent for the first V2X service is generated, a V2X layer of the first terminal device may obtain the transmission requirement (the service requirement and/or the message pattern) of the first V2X service, and send the transmission requirement to an access stratum (AS) of the first terminal device; the access stratum of the first terminal device determines the first DRX parameter based on the transmission requirement of the first V2X service].
Regarding Claim 17,
wherein the fourth indication information comprises a third time interval, and the third time interval is a minimum time interval for which the terminal device sends the request information for indicating the first transmission requirement [Ying: 0094; For determining of the first DRX parameter, the first DRX parameter needs to meet the message pattern and/or the service requirement of the first V2X service; if only the service requirement is considered, it is assumed that the service requirement of the message pattern of the first V2X service is that a delay does not exceed 50 ms; in an example, the service requirement of the first V2X service of the first terminal device is that a delay does not exceed 50 ms; in this case, the first DRX parameter may be set to 30 ms, and a wake-up time period is 5 ms. In this case, in a worst case (a V2X message is generated after a sleep state is entered), a time period of 25 ms (the service requirement 50 ms minus (the first DRX cycle 30 ms minus 5 ms)) may still be obtained to transmit the V2X message; in this way, the V2X message can be easily sent to a second terminal device within 50 ms].
Regarding Claim 18,
wherein the first transmission requirement is an uplink transmission requirement, and the first transmission resource corresponding to the first transmission requirement is an uplink transmission resource; and/or the first transmission requirement is a downlink transmission requirement, and the first transmission resource corresponding to the first transmission requirement is a downlink transmission resource [Ying: 0098; when a V2X message that needs to be sent for the first V2X service is generated, a V2X layer of the first terminal device may obtain the transmission requirement (the service requirement and/or the message pattern) of the first V2X service, and send the transmission requirement to an access stratum (AS) of the first terminal device; the access stratum of the first terminal device determines the first DRX parameter based on the transmission requirement of the first V2X service … in a possible implementation, further, the V2X layer of the first terminal device may send DRX indication information to the access stratum of the first terminal device, to indicate the access stratum of the first terminal device to obtain the DRX parameter for the first terminal device; 0102; the first terminal device sends the first DRX parameter to the second terminal device, and the second terminal device receives the first DRX parameter; 0103; the first DRX parameter is used by the first terminal device and the second terminal device to perform PC5 communication of the first V2X service].
Regarding Claim 19, which recites a communication device having the same claim limitations as those in claim 1 above, the same rationale of rejection as presented in claim 1 is applicable.
Regarding Claim 20, which recites a non-transitory computer-readable storage medium, comprising a computer program having the same claim limitations as those in claim 1 above, the same rationale of rejection as presented in claim 1 is applicable.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure. See Jing (US 2023/0026021) [para. 0048].
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