Communication method, terminal, network device, and storage medium

Abstract

The present disclosure relates to a communication method, a terminal, a network device, and a storage medium. The method comprises: sending request information to a network device on the basis of a sensing task, the request information being related to the sensing task, wherein the request information is used for requesting the establishment of a radio resource control (RRC) connection or requesting the restoration of the RRC connection. By means of the method of the present disclosure, in a scenario where a connection is triggered by a sensing task, a terminal can send request information related to the sensing task, such that a network device can quickly process connection establishment related to the sensing task, thereby reducing latency, and meeting the latency requirements for the sensing task.

Description

Communication method, terminal, network device and storage medium TECHNICAL FIELD

[0001] The present disclosure relates to the technical field of communication, and particularly relates to a communication method, a terminal, a network device and a storage medium. BACKGROUND

[0002] Integrated Sensing And Communication (ISAC) technology can obtain required information by using sensing technology in a communication system. In ISAC, a transmitting device transmits radio waves, a receiving device receives the radio waves, and relevant information of a reflector is determined according to changes in the radio waves caused by the reflector being blocked in the transmission process.

[0003] SUMMARY

[0004] In a scenario in which a terminal initiates a sensing task, the terminal needs to initiate establishment of a Radio Resource Control (RRC) connection to a network side, and a delay in establishing the RRC connection according to related technologies can not meet requirements of the sensing task.

[0005] Embodiments of the present disclosure provide a communication method, a terminal, a network device and a storage medium.

[0006] In a first aspect, embodiments of the present disclosure provide a communication method, executed by a terminal, and the method comprises:

[0007] sending, to a network device, request information based on a sensing task, the request information being related to the sensing task, wherein the request information is used to request establishment of a Radio Resource Control (RRC) connection or request RRC connection recovery.

[0008] In a second aspect, embodiments of the present disclosure provide a communication method, executed by a network device, and the method comprises:

[0009] receiving request information sent by a terminal, wherein the request information is related to a sensing task, and the request information is used to request establishment of a Radio Resource Control (RRC) connection or request RRC connection recovery.

[0010] In a third aspect, embodiments of the present disclosure provide a terminal device, comprising:

[0011] a transceiver module, configured to send, to a network device, request information based on a sensing task, the request information being used to request establishment of a Radio Resource Control (RRC) connection or request RRC connection recovery.

[0012] In a fourth aspect, embodiments of the present disclosure provide a network device, comprising:

[0013] a transceiving module, configured to receive request information sent by the terminal, wherein the request information is related to the perception task, and the request information is used to request establishment of a radio resource control (RRC) connection or request RRC connection recovery.

[0014] In a fifth aspect, an embodiment of the present disclosure provides a communication device, comprising:

[0015] one or more processors;

[0016] The communication device is configured to implement the method in the first aspect or the second aspect.

[0017] In a sixth aspect, an embodiment of the present disclosure provides a storage medium, which stores instructions, wherein,

[0018] When the instructions run on the communication device, the communication device executes the method in the first aspect or the second aspect.

[0019] In a seventh aspect, an embodiment of the present disclosure provides a program product, wherein,

[0020] When the program product is executed by the communication device, the communication device executes the method in the first aspect or the second aspect.

[0021] In the embodiments of the present disclosure, in the scenario of connection triggered by a perception task, the terminal can send request information related to the perception task, so that the network device can quickly process the connection establishment related to the perception task, reduce the latency, and meet the demand of the perception task for the latency. BRIEF DESCRIPTION OF DRAWINGS

[0022] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following describes the drawings required for the embodiments, and the following drawings are only some embodiments of the present disclosure, and do not specifically limit the protection scope of the present disclosure.

[0023] FIGS. 1a-1b are one exemplary schematic diagram of an architecture of a communication system according to an embodiment of the present disclosure;

[0024] FIGS. 2a-2b are one exemplary interactive schematic diagram of a method according to an embodiment of the present disclosure;

[0025] FIG. 2c is an information element schematic diagram according to an embodiment of the present disclosure;

[0026] FIGS. 3a-3b are one exemplary flowchart of a method according to an embodiment of the present disclosure;

[0027] FIGS. 4a-4b are one exemplary flowchart of a method according to an embodiment of the present disclosure;

[0028] FIG. 5a is a structural schematic diagram of a terminal according to an embodiment of the present disclosure;

[0029] FIG. 5b is a structural schematic diagram of a network device according to an embodiment of the present disclosure;

[0030] FIG. 6a is a schematic diagram of a communication device according to an embodiment of the present disclosure;

[0031] FIG. 6b is a schematic diagram of a communication device according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0032] Embodiments of the present disclosure provide a communication method, a terminal, a network device and a storage medium.

[0033] In a first aspect, embodiments of the present disclosure provide a communication method performed by a terminal, the method comprising:

[0034] sending, to a network device, request information based on a perception task, the request information being related to the perception task, wherein the request information is used to request establishment of a radio resource control (RRC) connection or request RRC connection recovery.

[0035] In the above embodiments, in the scenario of connection triggered by a perception task, the terminal can send request information related to the perception task, so that the network device can quickly process the connection establishment related to the perception task, reduce the latency, and meet the demand of the perception task for latency.

[0036] In combination with the embodiments of the first aspect, in some embodiments, the request information comprises a third message (MSG3) cause, wherein in a case where the MSG3 cause value is a first value, the MSG3 cause indicates that the RRC connection establishment cause and / or the RRC connection recovery cause is the perception task.

[0037] In combination with the embodiments of the first aspect, in some embodiments, the request information is sent through MSG3.

[0038] In combination with the embodiments of the first aspect, in some embodiments, the perception task is associated with at least one of the following: a unified access control (UAC) access category (AC), a UAC access identity (AI).

[0039] wherein a parameter value of the UAC access category is a second value, and a parameter value of the UAC access identity is a third value.

[0040] In combination with the embodiments of the first aspect, in some embodiments, before the request information is sent to the network device, the method further comprises:

[0041] performing an access attempt corresponding to the sensing task, wherein the access attempt corresponds to a UAC access type.

[0042] With reference to the embodiments of the first aspect, in some embodiments, the method further includes:

[0043] obtaining a UAC parameter related to the second value, the UAC parameter including at least one of:

[0044] a barring factor;

[0045] a barring duration;

[0046] a bitmap of UAC access identities.

[0047] With reference to the embodiments of the first aspect, in some embodiments, before sending the request information to the network device, the method further includes:

[0048] determining whether to allow performing the access procedure according to the UAC parameter.

[0049] With reference to the embodiments of the first aspect, in some embodiments, determining whether to allow performing the access procedure according to the UAC parameter includes:

[0050] in the bitmap of UAC access identities, if a bit value corresponding to a UAC access identity associated with the sensing task is a fourth value, determining to allow performing the access procedure; or

[0051] in the bitmap, if the bit value corresponding to the UAC access identity associated with the sensing task is a fifth value, determining whether to allow performing the access procedure based on a barring factor.

[0052] With reference to the embodiments of the first aspect, in some embodiments, determining whether to allow performing the access procedure based on the barring factor includes:

[0053] generating a first random number, and determining to allow performing the access procedure when the first random number is less than the barring factor; or

[0054] generating a second random number, and determining to allow performing the access procedure after a first duration when the first random number is greater than or equal to the barring factor, wherein the first duration is determined according to the second random number and a barring duration.

[0055] With reference to the embodiments of the first aspect, in some embodiments, the UAC access type AC and / or the UAC access identity AI corresponds to a MSG3 cause.

[0056] With reference to the embodiments of the first aspect, in some embodiments, the method further includes:

[0057] Receive configuration information sent by the network device, the configuration information comprising a random access priority parameter corresponding to the sensing task.

[0058] In some embodiments combined with the embodiments of the first aspect, the method further comprises:

[0059] Initiating a random access procedure to the network device according to the random access priority parameter corresponding to the sensing task.

[0060] In some embodiments combined with the embodiments of the first aspect, the random access priority parameter comprises at least one of:

[0061] a power ramping step size;

[0062] a scaling factor of a back-off indicator (BI);

[0063] an initial target received power;

[0064] a maximum number of preamble transmissions;

[0065] wherein the power ramping step size is greater than a sixth value, and / or the maximum number of preamble transmissions is less than a seventh value; the sixth value is greater than or equal to a power ramping step size of a random access procedure other than the random access procedure corresponding to the sensing task, and the seventh value is greater than or equal to a maximum number of preamble transmissions of the other random access procedure.

[0066] In some embodiments combined with the embodiments of the first aspect, the random access priority parameter is associated with at least one of:

[0067] a sensing-related event triggering the random access;

[0068] a MSG3 cause associated with the sensing task;

[0069] a UAC access type associated with the sensing task;

[0070] a UAC access identity associated with the sensing task.

[0071] In some embodiments combined with the embodiments of the first aspect, the method further comprises:

[0072] Sending indication information to the network device, the indication information being used to indicate sensing information supported by the terminal.

[0073] In some embodiments combined with the embodiments of the first aspect, the sensing information is at least one of:

[0074] a sensing mode;

[0075] a sensing capability;

[0076] sensing frequency domain information.

[0077] With reference to the first aspect, in some embodiments, the network device is an access network device or a sensing function control node.

[0078] In a second aspect, the embodiments of the present disclosure provide a communication method, performed by a network device, the method comprising:

[0079] receiving request information sent by a terminal, wherein the request information is related to a sensing task, and the request information is used to request establishment of a radio resource control (RRC) connection or request RRC connection recovery.

[0080] In the above embodiments, the network device can quickly process or control the connection establishment related to the sensing task according to the request information related to the sensing task, so as to reduce the latency and meet the demand of the sensing task for the latency.

[0081] With reference to the second aspect, in some embodiments, the request information comprises a third message (MSG3) cause, wherein, when the MSG3 cause value is a first value, the MSG3 cause indicates an RRC connection establishment cause and / or an RRC connection recovery cause.

[0082] With reference to the second aspect, in some embodiments, the request information is sent through the MSG3.

[0083] With reference to the second aspect, in some embodiments, the sensing task is associated with at least one of the following: a unified access control (UAC) access type (AC) and a UAC access identity (AI).

[0084] wherein a parameter value of the UAC access type is a second value, and a parameter value of the UAC access identity is a third value.

[0085] With reference to the second aspect, in some embodiments, the UAC parameter related to the second value comprises at least one of the following:

[0086] a barring factor;

[0087] a barring duration;

[0088] a bitmap of the UAC access identity.

[0089] With reference to the second aspect, in some embodiments, the UAC parameter is used to determine whether the terminal is allowed to perform an access procedure.

[0090] With reference to the second aspect, in some embodiments, in the bitmap of the UAC access identity, when a bit value corresponding to a UAC access identity associated with the sensing task is a fourth value, the terminal is allowed to perform the access procedure; or,

[0091] In the bitmap, if the bit value corresponding to the UAC access identity associated with the sensing task is the fifth value, it is determined whether to allow the terminal to perform the access procedure based on the barring factor.

[0092] In some embodiments of the second aspect, the terminal is allowed to perform the access procedure when the first random number is less than the barring factor; or,

[0093] When the first random number is greater than or equal to the barring factor, the terminal is allowed to perform the access procedure after a first time length, the first time length being determined according to the second random number and a barring time length.

[0094] In some embodiments of the second aspect, the UAC access type AC and / or the UAC access identity AI correspond to the MSG3 cause.

[0095] In some embodiments of the second aspect, the method further comprises:

[0096] sending configuration information to the terminal, the configuration information including a random access priority parameter corresponding to the sensing task.

[0097] In some embodiments of the second aspect, the random access priority parameter includes at least one of:

[0098] a power ramping step;

[0099] a scaling factor of a backoff indication BI;

[0100] an initial target received power;

[0101] a maximum number of preamble transmissions;

[0102] wherein the power ramping step is greater than a sixth value, and / or the maximum number of preamble transmissions is less than a seventh value; the sixth value being greater than or equal to a power ramping step of another random access procedure other than the random access procedure corresponding to the sensing task, and the seventh value being greater than or equal to a maximum number of preamble transmissions of the other random access procedure.

[0103] In some embodiments of the second aspect, the random access priority parameter is associated with at least one of:

[0104] a sensing-related event triggering the random access;

[0105] a MSG3 cause associated with the sensing task;

[0106] a UAC access type associated with the sensing task;

[0107] a UAC access identity associated with the sensing task.

[0108] In combination with the embodiments of the second aspect, in some embodiments, the method further includes:

[0109] receiving indication information sent by the terminal, the indication information being used to indicate sensing information supported by the terminal.

[0110] In combination with the embodiments of the second aspect, in some embodiments, the sensing information is at least one of the following:

[0111] a sensing mode;

[0112] a sensing capability;

[0113] sensing frequency domain information.

[0114] In combination with the embodiments of the second aspect, in some embodiments, the network device is an access network device or a sensing function control node.

[0115] In a third aspect, the embodiments of the present disclosure provide a terminal device, including:

[0116] a transceiver, configured to send request information to a network device based on a sensing task, the request information being related to the sensing task, wherein the request information is used to request establishment of a radio resource control (RRC) connection or request RRC connection recovery.

[0117] In a fourth aspect, the embodiments of the present disclosure provide a network device, including:

[0118] a transceiver, configured to receive request information sent by a terminal, wherein the request information is related to a sensing task, and the request information is used to request establishment of a radio resource control (RRC) connection or request RRC connection recovery.

[0119] In a fifth aspect, the embodiments of the present disclosure provide a communication device, including:

[0120] one or more processors;

[0121] The communication device is configured to implement the method in the first aspect or the second aspect.

[0122] In a sixth aspect, the embodiments of the present disclosure provide a storage medium, which stores instructions, wherein,

[0123] When the instructions run on the communication device, the communication device is caused to perform the method in the first aspect or the second aspect.

[0124] In a seventh aspect, the embodiments of the present disclosure provide a program product, wherein,

[0125] When the program product is executed by a communication device, the communication device is caused to perform the method in the first aspect or the second aspect.

[0126] In an eighth aspect, the embodiments of the present disclosure provide a computer program which, when running on a computer, causes the computer to perform the method described in the first aspect and the optional implementation manners of the second aspect.

[0127] In a ninth aspect, the embodiments of the present disclosure provide a chip or chip system. The chip or chip system comprises processing circuitry configured to perform the method described in the first aspect and the optional implementation manners of the second aspect.

[0128] It can be understood that the terminal, the network device, the communication system, the storage medium, the program product, the computer program, the chip or the chip system are all used to perform the method proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding method, which will not be described here.

[0129] The embodiments of the present disclosure are not exhaustive, but only illustrate some embodiments, and are not specific limitations on the protection scope of the present disclosure. In the case of no contradiction, each step in an embodiment can be implemented as an independent embodiment, and the steps can be combined arbitrarily, for example, the scheme after removing some steps in an embodiment can also be implemented as an independent embodiment, and the order of the steps in an embodiment can be exchanged arbitrarily, in addition, the optional implementation manners in an embodiment can be combined arbitrarily; in addition, the embodiments can be combined arbitrarily, for example, some or all steps of different embodiments can be combined arbitrarily, an embodiment can be combined with the optional implementation manners of other embodiments.

[0130] In each embodiment of the present disclosure, the terms and / or descriptions between the embodiments are consistent if there is no special description and logical conflict, and can be referred to each other, and the technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0131] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments, and not as a limitation on the present disclosure.

[0132] In the embodiments of the present disclosure, unless otherwise specified and logically contradictory, the elements expressed in singular form, such as "one", "one", "the", "the above", "the", "the above", "this" and the like, can represent "one and only one", and can also represent "one or more", "at least one" and the like. For example, in the case of using articles such as "a", "an", "the" and the like in English, the noun after the article can be understood as singular expression, and can also be understood as plural expression.

[0133] In the embodiments of the present disclosure, "a plurality of" means two or more.

[0134] In some embodiments, the terms "at least one of," "one or more of," "a plurality of," "multiple," and the like can be used interchangeably.

[0135] In some embodiments, the recitations "at least one of A, B," "A and / or B," "in one case A, in another case B," "in response to a case A, in response to a case B," and the like can include the following technical solutions according to the case: in some embodiments A (A is executed regardless of B); in some embodiments B (B is executed regardless of A); in some embodiments, A and B are selectively executed (A and B are selectively executed); in some embodiments, A and B (A and B are executed). When there are more branches such as A, B, C, and the like, the above is similar.

[0136] In some embodiments, the recitations "A or B" and the like can include the following technical solutions according to the case: in some embodiments A (A is executed regardless of B); in some embodiments B (B is executed regardless of A); in some embodiments, A and B are selectively executed (A and B are selectively executed). When there are more branches such as A, B, C, and the like, the above is similar.

[0137] The prefix words "first", "second", and the like in the embodiments of the present disclosure are merely used to distinguish different description objects, and do not constitute a limitation on the position, order, priority, quantity, or content of the description objects. The description of the description objects should refer to the description in the context of the claims or embodiments, and should not constitute an additional limitation because of the use of the prefix words. For example, the description objects are "fields", and the ordinal words before "fields" in "first field" and "second field" do not limit the position or order between "fields", and "first" and "second" do not limit whether the "fields" modified thereby are in the same message or not, nor limit the order of "first field" and "second field". For another example, the description objects are "levels", and the ordinal words before "levels" in "first level" and "second level" do not limit the priority between "levels". For another example, the quantity of the description objects is not limited by the ordinal words, and can be one or more. For example, "first device", wherein the quantity of "devices" can be one or more. In addition, the objects modified by different prefix words can be the same or different, for example, the description objects are "devices", and "first device" and "second device" can be the same device or different devices, and the types thereof can be the same or different; for another example, the description objects are "information", and "first information" and "second information" can be the same information or different information, and the content thereof can be the same or different.

[0138] In some embodiments, "comprising", "including", "to indicate", "carrying", can be interpreted as directly carrying A, or indirectly indicating A.

[0139] In some embodiments, the terms "in response to", "in response to determining", "in the case of", "when", "when", "if", "if" and the like can be replaced with each other.

[0140] In some embodiments, the terms "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", "above" and the like can be replaced with each other, and the terms "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", "below" and the like can be replaced with each other.

[0141] In some embodiments, the apparatus and device can be interpreted as physical or virtual, and its name is not limited to the name described in the embodiments, and in some cases can also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject" and the like.

[0142] In some embodiments, "network" can be interpreted as an apparatus included in the network, such as an access network device, a core network device, and the like.

[0143] In some embodiments, an “access network device (AN device)” can also be referred to as a “radio access network device (RAN device),” a “base station (BS),” a “radio base station,” a “fixed station,” and in some embodiments can also be understood as a “node,” an “access point,” a “transmission point (TP),” a “reception point (RP),” a “transmission / reception point (TRP),” a “panel,” an “antenna panel,” an “antenna array,” a “cell,” a “macro cell,” a “small cell,” a “femto cell,” a “pico cell,” a “sector,” a “cell group,” a “serving cell,” a “carrier,” a “component carrier,” a “bandwidth part (BWP),” and the like.

[0144] In some embodiments, a "terminal" or "terminal device" can be referred to as a "user equipment" (UE), a "user terminal," a "mobile station" (MS), a "mobile terminal" (MT), a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, and / or the like.

[0145] In some embodiments, data, information and / or the like can be obtained in compliance with laws and regulations of a country where the data, information and / or the like is obtained.

[0146] In some embodiments, data, information and / or the like can be obtained after obtaining consent of a user.

[0147] In addition, each element, each row, or each column in the table of the embodiments of the present disclosure can be implemented as an independent embodiment, and a combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0148] FIGS. 1a-1b are schematic diagrams of an architecture of a communication system 100, according to embodiments of the present disclosure.

[0149] As shown in FIG. 1a, the communication system 100 includes a transmitting device 1101, a receiving device 1102, and a reflector 1103. The communication system 100 can be an ISAC system. The transmitting device 1101, i.e., a wireless signal transmitting end, can be used to transmit radio waves or sensing reference signals. The receiving device 1102, i.e., a wireless signal receiving end, can be used to receive radio waves or sensing reference signals. During the transmission of radio waves or sensing reference signals, the transmission of radio waves can be blocked by some objects (i.e., the reflector 1103), thereby producing wireless transmission effects such as reflection, diffraction, transmission, phase change, Doppler shift, signal strength change, etc. during the transmission of radio waves. The receiving device 1102 can obtain information about the reflector 1103, such as coordinate information, speed information, signal strength, or behavior pattern information of the reflector 1103, by receiving radio waves and comparing the transmitting signals and the receiving signals of the radio waves, or recording the historical change information of the receiving signals.

[0150] In some embodiments, the transmitting device 1101 can be a terminal 101 or a network device 102, and the receiving device 1102 can be a terminal 101 or a network device 102. For example, as shown in FIG. 1b, the communication system 100 of the ISAC includes a terminal 101 and a network device 102, where the terminal 101 can act as the receiving device 1102 of the ISAC, and the network device 102 can act as the transmitting device 1101 of the ISAC; or the terminal 101 can act as the transmitting device 1101 of the ISAC, and the network device 102 can act as the receiving device 1102 of the ISAC.

[0151] Optionally, the terminal 101 includes at least one of a mobile phone, a wearable device, an Internet of Things device, a communication-enabled car, a smart car, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in smart grid, a wireless terminal device in transportation safety, a wireless terminal device in smart city, a wireless terminal device in smart home, etc., but is not limited thereto.

[0152] Optionally, the network device 102 can include at least one of an access network device, a core network device, a sensing function node. Among them, the sensing function node can be a sensing function control (SF-C) node, the SF-C node can be a separate node or a function entity arranged in the core network device, and the embodiments of the present disclosure are not limited thereto.

[0153] Among them, the access network device is at least one of a node or device that accesses the terminal to the wireless network, for example, a base station in a 5G communication system, an evolved node B (eNB), a next generation evolved node B (ng-eNB), a next generation node B (gNB), a node B (NB), a home node B (HNB), a home evolved node B (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a baseband unit (BBU), a mobile switching center, a base station in a 6G communication system, an open base station (Open RAN), a cloud base station (Cloud RAN), a base station in other communication systems, an access node in a wireless fidelity (WiFi) system, but not limited thereto.

[0154] Among them, the access network device can be composed of a central unit (CU) and a distributed unit (DU), wherein the CU can also be called a control unit (control unit), and the CU-DU structure can split the protocol layer of the access network device, and the functions of part of the protocol layer are controlled by the CU, and the functions of the remaining part or all of the protocol layer are distributed in the DU and controlled by the CU, but not limited thereto.

[0155] In some embodiments, the core network device described above can be one device including one or more network elements, or can be multiple devices or device groups each including all or part of one or more network elements. The network element can be virtual or physical. The core network includes, for example, at least one of an evolved packet core (EPC), a 5G core network (5GCN), and a next generation core (NGC). Alternatively, the core network device refers to a network element with specific functions, such as an access management function (AMF), a service management function (SMF), a sensing function (SF), or a sensing network function (SNF).

[0156] In some embodiments, the transmitting device 1101 and the receiving device 1102 can be the same device or different devices.

[0157] In some embodiments, when the transmitting device 1101 and the receiving device 1102 are co-sited, this sensing method or mode can be referred to as mono-static sensing. When the transmitting device 1101 and the receiving device 1102 are not co-sited, this sensing method or mode can be referred to as bi-static sensing.

[0158] In mono-static sensing, the transmitting device 1101 and the receiving device 1102 can be the same device, such as sensing methods or modes (1) and (5) described below or shown in Table 1-1. In bi-static sensing, the transmitting device 1101 and the receiving device 1102 can be different devices, such as sensing methods or modes (2), (3), (4), and (6) shown in Table 1-1. Among them:

[0159] Mode (1): Base station self-transmission and self-reception, such as base station A transmitting wireless signals or radio waves, and base station A receiving wireless signals.

[0160] Mode (2): Base station A transmission and base station B reception, such as base station A transmitting wireless signals and base station B receiving wireless signals.

[0161] Mode (3): Base station transmission and terminal reception, such as base station A transmitting wireless signals and terminal A receiving wireless signals.

[0162] Mode (4): terminal-to-base station, for example, terminal A transmits a wireless signal, and base station A receives the wireless signal.

[0163] Mode (5): terminal-to-terminal, for example, terminal A transmits a wireless signal, and terminal A receives the wireless signal.

[0164] Mode (6): terminal A-to-terminal B, for example, terminal A transmits a wireless signal, and terminal B receives the wireless signal.

[0165] Table 1-1

[0166] In some embodiments, the technical solutions of the present disclosure can be applied to the Open RAN architecture, at this time, the interfaces between the access network devices or within the access network devices involved in the embodiments of the present disclosure can become internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces can be realized through software or programs.

[0167] It can be understood that the communication system described in the embodiments of the present disclosure is for more clearly illustrating the technical solutions of the embodiments of the present disclosure, and does not constitute a limitation on the technical solutions provided by the embodiments of the present disclosure. It can be known by those skilled in the art that, with the evolution of system architecture and the appearance of new business scenarios, the technical solutions provided by the embodiments of the present disclosure are also applicable to similar technical problems.

[0168] The following embodiments of the present disclosure can be applied to the communication system 100 shown in FIG. 1a or FIG. 1b, or part of the subject, but are not limited thereto.

[0169] The subjects shown in FIG. 1a or FIG. 1b are examples, and the communication system can include all or part of the subjects in FIG. 1a or FIG. 1b, or other subjects other than FIG. 1a. The number and form of each subject is arbitrary, and the connection relationship between each subject is an example. Each subject can be connected or not connected, and the connection can be in any way, can be direct connection or indirect connection, can be wired connection or wireless connection.

[0170] Embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (Bluetooth (registered trademark)), Public Land Mobile Network (PLMN) network, Device-to-Device (D2D) system, Machine to Machine (M2M) system, Internet of Things (IoT) system, Vehicle-to-Everything (V2X), system using other communication processing methods, next-generation system expanded based thereon, and the like. Further, a plurality of systems can be applied in combination (for example, combination of LTE or LTE-A and 5G, and the like).

[0171] The perception technology includes various types, such as laser radar, millimeter wave radar, camera, sonar detection, infrared detection, cellular network perception, and the like. The camera perception technology includes any one of the following: visual camera, time of flight (TOF) camera. The cellular network perception can be a perception technology based on 4G (such as LTE), 5G (such as NR), or 6G cellular network technology. The cellular network perception technology includes any one of the following: communication base station perception, communication terminal perception.

[0172] According to the type of the perception device, the information of the reflection body or the target object that can be acquired includes at least one of the following:

[0173] Coordinate information, such as coordinates (such as distance, horizontal angle, and vertical angle) relative to a wireless signal receiving end.

[0174] Speed information, such as moving speed and moving direction relative to a wireless signal receiving end.

[0175] Signal strength.

[0176] Behavioral pattern information, such as running, walking, approaching, falling, swinging, and the like.

[0177] Weather information, such as rain, snow, and the like.

[0178] Traffic information, such as congestion, accidents, and the like.

[0179] In the ISAC technology, when the terminal needs to initiate a perception task establishment request, the terminal in the RRC idle state (RRC_IDLE) or the RRC inactive state (RRC_INACTIVE) needs to initiate an RRC connection establishment request to the network side. In the related technology, no special processing is made for the RRC connection establishment triggered by the perception task establishment. The ISAC task establishment has certain requirements on the delay, for example, the demander of the perception result is a car, at this time, it is necessary to quickly establish the perception service and timely apply the perception result, and the delay has a higher requirement.

[0180] FIG. 2a is an interaction schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG. 2a, the embodiment of the present disclosure relates to a communication method, and the method includes:

[0181] In step S2101, the network device 102 sends an UAC configuration to the terminal 101.

[0182] In some embodiments, the network device 102 can be an access network device such as a base station, or the network device 102 is a perception function control node SF-C. Wherein,

[0183] Optionally, the network device 102 can be a base station, and the terminal 101 can initiate an RRC connection establishment procedure or an RRC connection resume procedure to the base station when the RRC layer of the terminal 101 needs to establish an ISAC task. The RRC layer can be used for communication between the terminal and the base station.

[0184] Optionally, the network device 102 can be an SF-C, and the terminal 101 can initiate an RRC connection establishment procedure or an RRC connection resume procedure to the SF-C when the ISAC service layer of the terminal 101 needs to establish an ISAC task. The ISAC service layer can be used for communication between the terminal and the SF-C.

[0185] In some embodiments, the terminal 101 needs to initiate an RRC connection establishment or an RRC connection resume to the network device 102 when an awareness task such as an ISAC task needs to be established. Before initiating the RRC connection establishment or the RRC connection resume, the terminal 101 can make an access decision based on step S2102 to determine whether an access attempt can be directly initiated or needs to be initiated after fallback.

[0186] In some embodiments, different BarringInfo sets can be included in the UAC configuration, and the terminal 101 needs to obtain the BarringInfo set corresponding to the awareness task to obtain the UAC parameter corresponding to the awareness task.

[0187] Optionally, the network device 102 can send the above UAC configuration through system broadcast.

[0188] Optionally, the terminal 101 can obtain the BarringInfo set associated with the awareness task such as the ISAC task in the system broadcast.

[0189] In some embodiments, the awareness task is associated with at least one of the following: a UAC access category (Access Category, AC), and a UAC access identity (Access Identity, AI).

[0190] In this embodiment, the UAC access category dedicated to the ISAC task can be defined or configured, and / or the UAC access identity dedicated to the ISAC task can be defined or configured.

[0191] For example, the parameter value (access category number) of the UAC access category associated with the ISAC task or the ISAC purpose access is a second value, and the ISAC task associated access category can be denoted as AC n.

[0192] For another example, the parameter value of the UAC access identity associated with the ISAC task is a third value, such as 3. As access identity 3, it indicates that the terminal accessing is ISAC service.

[0193] In some embodiments, the terminal 101 can obtain the UAC parameter related to the UAC access type associated with the ISAC task, such as the UAC parameter related to the second value, i.e., the UAC parameter related to the access category number n.

[0194] In some embodiments, there is a mapping relationship between the access attempt and the access type, and the terminal 101 can map the access attempt associated with the sensing task to the corresponding UAC access type, for example, the terminal 101 can determine that the mapped access type is AC n according to whether the access attempt is ISAC or ISAC request, and then obtain the UAC parameter corresponding to the access type AC n.

[0195] In step S2102, the terminal 101 determines whether to allow the execution of the access procedure according to the UAC parameter.

[0196] In some embodiments, the terminal 101 can obtain the UAC parameter related to the sensing task based on step S2101.

[0197] In some embodiments, the UAC parameter includes at least one of the following:

[0198] a barring factor (uac-BarringFactor);

[0199] a barring time (uac-BarringTime);

[0200] a bit map of UAC access identity (uac-BarringForAccessIdentity).

[0201] Optionally, as shown in FIG. 2c, in the bit map of the access identity, the terminal 101 can determine whether the access corresponding to different access identities is barred.

[0202] Optionally, the barring factor is used to further determine whether the access of the access identity is barred based on a random number (random) in the case that the access corresponding to the access identity is barred.

[0203] Optionally, the barring time can be used to determine the duration of barring access.

[0204] In some embodiments, the step S2102 can include the following step S2102-10 or step S2102-20, specifically:

[0205] Step S2102-10, in the bit map of UAC access identity, if the bit value corresponding to the UAC access identity associated with the sensing task is the fourth value, it is determined that the access procedure is allowed to be performed.

[0206] wherein, assuming that the access identity corresponding to the ISAC task is in the 3rd bit, the bit value in the 3rd bit can be used to determine whether the access of the ISAC task associated with the access identity is prohibited. For example, the fourth value can be 0, that is, when the bit corresponding to the access identity corresponding to the ISAC task in uac-BarringForAccessIdentity is set to 0, it means that the access corresponding to the ISAC task is allowed, or the access is not prohibited.

[0207] Step S2102-20, in the bit map, if the bit value corresponding to the UAC access identity associated with the sensing task is the fifth value, it is determined whether to perform the access procedure based on the barring factor.

[0208] wherein, the fifth value can be 1, that is, when the bit corresponding to the access identity corresponding to the ISAC task in uac-BarringForAccessIdentity is set to 1, it is necessary to further judge whether to allow access in combination with the barring factor.

[0209] When the bit value corresponding to the UAC access identity associated with the sensing task is the fifth value, the further judgment of the terminal 101 can refer to the following examples:

[0210] In this embodiment, the step S2102-20 can include that the terminal 101 generates a first random number, and when the first random number is less than the barring factor, it is determined that the access procedure is allowed to be performed.

[0211] wherein, the first random number (rand) satisfies: 0≤rand<1, if the first random number <uac-BarringFactor, it means that the access corresponding to the ISAC task is allowed, otherwise, that is, if the first random number≥uac-BarringFactor, it means that the above-mentioned access is prohibited. When the access is prohibited, the terminal 101 can further determine the duration of prohibiting the access, that is, the duration of backoff or waiting:

[0212] When the first random number is greater than or equal to the barring factor, the step S2102-20 can further include generating a second random number, and determining that the access procedure is allowed to be performed after a first duration, wherein the first duration is determined according to the second random number and the barring duration.

[0213] wherein, the second random number (rand') satisfies: 0≤rand'<1, when the terminal 101 generates the second random number, the terminal 101 can start a first timer, and the first timer can be T390.

[0214] The running time of the first timer is the first time length. For example, the running time of the first timer or the first time length = (0.7 + 0.6*rand')*uac-BarringTime.

[0215] In step S2103, when access is allowed, the terminal 101 performs an access attempt corresponding to the sensing task.

[0216] In some embodiments, in combination with the decision in step S2102, when access is allowed to be performed, the terminal 101 can perform an access attempt corresponding to the sensing task.

[0217] In some embodiments, in combination with the decision in step S2102, when access is prohibited, the terminal 101 needs to initiate an access attempt again after a certain time length.

[0218] In some embodiments, the terminal 101 performs an access attempt corresponding to the sensing task, which can at least include an initial access process, or perform a random access process corresponding to the sensing task, or other operations before the random access process; wherein the random access process corresponding to the sensing task includes, for example, an RRC connection establishment or RRC connection recovery related random access process. The present embodiment is not limited in this regard.

[0219] Optionally, the steps related to the random access process can refer to the corresponding embodiments of FIG. 2b. The embodiments of FIG. 2b can be applied to the present embodiment, such as after the terminal 101 performs an access attempt or in the process of performing an access attempt, the terminal 101 can interact with the network device 102 MSG1, MSG2, MSG3 or MSG4 and the like signaling or message.

[0220] In step S2104, the terminal 101 sends request information to the network device 102 based on the sensing task.

[0221] In some embodiments, the request information is used to request establishment of a radio resource control (RRC) connection or request RRC connection resume.

[0222] In some embodiments, the request information can be sent in a random access process, for example, sent through MSG3 in the random access process. Optionally, when the access attempt includes a random access process, step S2014 can be performed during the execution of step S2103, or steps S2103 and S2104 are performed in the same step, and the present embodiment is not limited in this regard.

[0223] In some embodiments, based on the above decision, the request information is sent when the access permission related to the perception task is performed, i.e., the request information is sent in a case related to the perception task, such as when the terminal establishes or initiates the perception task.

[0224] For example, the UAC access type AC associated with ISAC corresponds to the MSG3 cause, and / or the UAC access identity AI associated with ISAC corresponds to the MSG3 cause.

[0225] In some embodiments, the request information includes: a third message MSG3 cause, wherein in a case where the MSG3 cause value is a first value, the MSG cause indicates that the RRC connection establishment cause and / or the RRC connection recovery cause is the perception task.

[0226] In this embodiment, the MSG3 cause or the MSG3 cause value in the request information is associated with the perception task, such as the first value indicating that the connection initiation cause is the perception task.

[0227] In this embodiment, the request information can carry the MSG3 cause associated with the perception task, i.e., a new MSG3 cause is defined, and in the RRC connection establishment cause and the RRC connection recovery cause, the request for the RRC connection related to the perception task can be indicated by the MSG3 cause associated with the perception task.

[0228] Optionally, the first value is, for example, a mo-ISAC or other ISAC related field, indicating that the cause of the RRC connection establishment or the RRC connection recovery is the initial establishment of the ISAC perception task.

[0229] In an example, the value of the MSG3 cause, i.e., the first value, can be represented by a spare parameter in an information element. For example:

[0230] In some embodiments, after the terminal 101 establishes or recovers the RRC connection with the network device 102, the terminal 101 and the network device 102 can perform the perception task, and the terminal 101 can apply the perception result to perform related operations.

[0231] It is worth noting that the above first value to the fifth value are only used for differentiation in name, and any two of the first value to the fifth value can not have association or connection; or only part of them are associated, such as the fourth value and the fifth value for indicating different values of the same bit.

[0232] In some embodiments, the name of information and the like is not limited to the name described in the embodiments, and the terms of "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", and the like can be replaced with each other.

[0233] In some embodiments, "acquire", "obtain", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be replaced with each other, which can be interpreted as receiving from other subjects, acquiring from protocols, acquiring from higher layers, obtaining by processing oneself, implementing autonomously, and the like.

[0234] In some embodiments, the terms of "send", "transmit", "report", "issue", "transmit", "bidirectional transmission", "send and / or receive" can be replaced with each other.

[0235] In some embodiments, the terms of "radio", "wireless", "radio access network (RAN)", "access network (AN)", "RAN-based" and the like can be replaced with each other.

[0236] In some embodiments, the terms of "time", "time point", "time", "time position" and the like can be replaced with each other, and the terms of "time length", "time period", "time window", "window", "time" and the like can be replaced with each other.

[0237] In some embodiments, the terms of "component carrier (CC)", "cell", "frequency carrier", "carrier frequency" and the like can be replaced with each other.

[0238] In some embodiments, the terms "certain", "preset", "pre-set", "set", "indicated", "a certain", "any", "first", and the like can be replaced with each other, "certain A", "preset A", "pre-set A", "set A", "indicated A", "a certain A", "any A", "first A" can be interpreted as A specified in advance in a protocol or the like, A obtained by setting, configuration, or indication, or the like, or a certain A, a certain A, any A, or first A, but are not limited thereto.

[0239] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (Boolean value) represented by true or false, or by comparison of numerical values (for example, comparison with a predetermined value), but is not limited thereto.

[0240] In some embodiments, "not expecting to receive" can be interpreted as not receiving in the time domain resource and / or the frequency domain resource, or as not performing subsequent processing on the data or the like after receiving the data or the like; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the receiving party to respond to the content of the sending.

[0241] The method related to the embodiments of the present disclosure can include at least one of steps S2101-S2104. For example, the method includes step S2104.

[0242] In some embodiments, step S2101 is optional, and in different embodiments, one or more steps can be replaced.

[0243] In some embodiments, step S2102 is optional, and in different embodiments, one or more steps can be replaced.

[0244] In some embodiments, step S2103 is optional, or step S2103 and step S2104 can be executed synchronously.

[0245] In some embodiments, other optional implementations described before or after the description corresponding to FIG. 2a can be referred to.

[0246] In the embodiments of the present disclosure, an access category and / or an access identity specific to ISAC can be defined, so that the terminal 101 can perform ISAC-related UAC, so that the network device 102 can learn that the access is for ISAC service, which is beneficial to quickly establish access, reduce ISAC service establishment delay, meet the demand of sensing task for delay, and improve service performance.

[0247] FIG. 2b is an interaction schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG. 2b, the embodiments of the present disclosure relate to a communication method, the method comprising:

[0248] In step S2201, the network device 102 sends configuration information to the terminal 101.

[0249] In some embodiments, the configuration information comprises a random access prioritization parameter corresponding to the sensing task.

[0250] Optionally, the sensing task is used to represent an ISAC-related task or event. The random access procedure or random access channel (RACH) corresponding to the sensing task is of high priority, such as a high-priority RACH.

[0251] Optionally, the high-priority RACH of the sensing task can correspond to a dedicated random access prioritization parameter (RA-Prioritization), such as a high-priority RACH parameter.

[0252] In some embodiments, the random access prioritization parameter RA-Prioritization comprises at least one of the following:

[0253] a power ramping step (powerRampingStepHighPriority);

[0254] a backoff indication (BI) scaling factor (scalingFactorBI);

[0255] an initial target received power (preambleReceivedTargetPower);

[0256] a maximum number of preamble transmissions (preambleTransMax);

[0257] wherein the power ramping step is greater than a sixth value, and / or the maximum number of transmissions is less than a seventh value; the sixth value is greater than or equal to a power ramping step of a random access procedure other than the random access procedure corresponding to the sensing task, and the seventh value is greater than or equal to a maximum number of transmissions of the other random access procedure.

[0258] Optionally, the power ramping step is used to indicate the power increase value of the terminal 101 in the random access procedure, such as the step of the MSG1 transmission power ramping, where the terminal 101 can send a preamble through MSG1. In an example, after a RACH failure, the terminal 101 can send a preamble again through MSG1, and the difference between the power of the MSG1 sent again and the last MSG1 (such as the MSG1 corresponding to the RACH failure) can conform to the configured power ramping step.

[0259] The sixth value can be set as the power ramping step corresponding to the regular RACH or non-high priority RACH, and the sixth value can be defined by a protocol or configured by the network device. The power ramping step corresponding to the sensing task is greater than the sixth value, which can make the terminal 101 increase the transmission power in the random access procedure related to the sensing task with a larger step, and improve the success rate of the terminal 101 in the random access.

[0260] Optionally, the BI can be used to indicate the time length of the terminal 101 to back off or wait after a RACH failure, and the network device 102 can configure the BI value for the terminal 101. The scaling factor can also be referred to as a backoff factor, which is used to determine the time backoff value in the random access procedure related to the sensing task, that is, the backoff or waiting time length can be further scaled based on the BI. For example, in the random access procedure of the sensing task, the backoff time length of the terminal 101 is BI multiplied by the scaling factor; or SCALING_FACTOR_BI multiplied by PREAMBLE_BACKOFF, where SCALING_FACTOR_BI represents the scaling factor, PREAMBLE_BACKOFF represents BI, and PREAMBLE_BACKOFF is the backoff value configured by the network device 102.

[0261] The scaling factor can be used to reduce or decrease the BI, so that the terminal 101 can initiate the random access again after a shorter backoff in the random access procedure corresponding to the sensing task.

[0262] Optionally, the initial target received power is used to determine the transmission power of the terminal 101, such as the transmission power of the MSG1, and the greater the initial target received power, the greater the transmission power of the terminal 101 in sending the MSG1, so as to reduce the number of power ramping and speed up the random access procedure.

[0263] Optionally, the maximum transmission number is used to indicate the maximum transmission number of the preamble in the random access procedure. If the number of times that the terminal 101 transmits the preamble reaches the maximum transmission number, it is considered that the random access procedure fails.

[0264] The seventh value can be set as the maximum transmission number corresponding to the regular RACH or the non-high-priority RACH, and the seventh value can be defined by a protocol or configured by the network device. The maximum transmission number is set to be relatively small, so that the terminal 101 can select other candidate cells for random access as soon as possible after the random access fails, and the efficiency of successful random access is improved.

[0265] In some embodiments, the related parameters are configured by random access prioritization (RA-Prioritization):

[0266] In some embodiments, the terminal 101 receives the configuration information, and can initiate a random access procedure to the network device according to the random access prioritization parameter corresponding to the perception task, as described in the following steps S2202-S2206.

[0267] In step S2202, the terminal 101 sends MSG1 to the network device 102.

[0268] In some embodiments, in the RACH related to the perception task, MSG1 can be used to transmit a preamble.

[0269] In some embodiments, the terminal 101 can send MSG1 based on the random access prioritization parameter corresponding to the perception task in the configuration information.

[0270] In some embodiments, the random access prioritization parameter is associated with at least one of the following:

[0271] a perception-related event triggering random access;

[0272] a MSG3 cause associated with the perception task;

[0273] a UAC access type associated with the perception task;

[0274] a UAC access identity associated with the perception task.

[0275] In an example, the random access priority parameter associated with the sensing task can be associated with the sensing event triggering the RACH. For example, the event triggering the RACH is an ISAC related event, such as ISAC establishment, etc., then the terminal 101 needs to initiate the RACH procedure, the high priority RACH parameter dedicated to ISAC is used. The configuration of the specific high priority RACH parameter or the content contained therein can refer to the description of the previous step.

[0276] In an example, the random access priority parameter associated with the sensing task can be associated with the access identification associated with the sensing task, that is, the high priority RACH parameter is defined based on the access identification associated with the sensing task. Therefore, in the access associated with the sensing task, the terminal 101 can use the high priority RACH parameter dedicated to ISAC in the RACH procedure for performing the sensing task based on the access identification associated with the sensing task. The configuration of the specific high priority RACH parameter or the content contained therein can refer to the description of the previous step.

[0277] In this example, the high priority RACH parameter associated with the access identification can be defined in the following way:

[0278] In an example, the random access priority parameter associated with the sensing task can be associated with the access type or MSG3 cause associated with the sensing task, that is, the high priority RACH is defined based on the access type of the access or the MSG3 cause value. Therefore, in the access associated with the sensing task, the terminal 101 can use the high priority RACH parameter dedicated to ISAC in the RACH procedure for performing the sensing task based on the access type or MSG3 cause associated with the sensing task.

[0279] In some embodiments, the network device 102 receives the MSG1.

[0280] In step S2203, the network device 102 sends the MSG2 to the terminal 101.

[0281] In some embodiments, the MSG2 can include a random access response (RAR).

[0282] In some embodiments, the terminal 101 receives the MSG2.

[0283] In step S2204, the terminal 101 sends the MSG3 to the network device 102, and the MSG3 includes the request information.

[0284] In some embodiments, the request information can be used to request to establish a radio resource control (RRC) connection or to request RRC connection resume. For example, the request information is an RRC connection request, or the request information is an RRC connection resume request.

[0285] In some embodiments, the request information or the MSG3 can include a MSG3 cause, which is used to indicate an RRC connection establishment cause and / or an RRC connection resume cause for the sensing task.

[0286] Optionally, the MSG3 cause can be one-to-one corresponding or bound to an access type and / or an access identity.

[0287] In some embodiments, the terminal 101 can send the MSG3 according to the configuration information, such as sending the MSG3 based on a power ramping step.

[0288] In some embodiments, the network device 102 receives the MSG3 or the request information.

[0289] In step S2205, the network device 102 sends a MSG4 to the terminal 101.

[0290] In some embodiments, in the random access of the RRC connection establishment, the MSG4 can include information for demodulation.

[0291] In some embodiments, in the random access of the RRC connection resume, the MSG4 can include a resume command.

[0292] In some embodiments, the terminal 101 receives the MSG4.

[0293] In step S2206, the terminal 101 sends indication information to the network device 102.

[0294] In some embodiments, the indication information can be used to indicate sensing information supported or expected by the terminal 101.

[0295] In some embodiments, the indication information can be sent through an RRC connection establishment complete message or an RRC connection resume message, such as through a MSG5.

[0296] In some embodiments, the indication information can be sent through a separate capability information (UE capability container).

[0297] In some embodiments, the sensing information is at least one of the following:

[0298] a sensing mode;

[0299] perception capability;

[0300] perception frequency domain information.

[0301] In some embodiments, the perception mode or the perception capability can refer to Table 1-1.

[0302] In some embodiments, the perception frequency domain information can include perception frequency band resources, etc.

[0303] The method related to the embodiments of the present disclosure can include at least one of steps S2201-S2206. Alternatively, in combination with the embodiments of FIG. 2a, the random access procedure of the embodiments of the present disclosure can be performed on the basis of FIG. 2a. For example, the method can include at least one of steps S2101-S2103, and after the UAC decision based on FIG. 2a allows access, the method can further include at least one of steps S2201-S2206 (at this time, steps S2104 and S2204 can be replaced or combined with each other), or if the access step S2103 allows access, it can include the random access procedure related to FIG. 2b.

[0304] In some embodiments, step S2201 is optional, and in different embodiments, it can be replaced by one or more steps. For example, the terminal 101 can initiate the ISAC task-related random access based on the defined or default high-priority RACH parameters.

[0305] In some embodiments, step S2203 is optional, and in different embodiments, it can be replaced by one or more steps.

[0306] In some embodiments, step S2206 is optional, and in different embodiments, it can be replaced by one or more steps.

[0307] In some embodiments, other optional implementations can be described before or after the description corresponding to FIG. 2b.

[0308] In the embodiments of the present disclosure, the MSG3 cause specific to ISAC can be defined, so that the terminal 101 can perform the ISAC-related random access procedure, so that the network device 102 can know that the access cause is ISAC service, which is beneficial to quickly establish access, reduce ISAC service establishment delay, meet the needs of perception tasks for delay, and improve service performance.

[0309] FIG. 3a is a flow diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in FIG. 3a, the embodiments of the present disclosure relate to a communication method, which is performed by a terminal 101, and the above method includes:

[0310] Step S3101: receiving UAC configuration and / or configuration information.

[0311] In some embodiments, the implementation of step S3101 can refer to the implementation of step S2101 in FIG. 2a, which will not be repeated here.

[0312] In some embodiments, the implementation of step S3101 can refer to the implementation of step S2201 in FIG. 2b, which will not be repeated here.

[0313] Step S3102: determining whether to allow the execution of the access procedure according to the UAC parameter.

[0314] In some embodiments, the implementation of step S3102 can refer to the implementation of step S2102 in FIG. 2a, which will not be repeated here.

[0315] Step S3103: sending the request information (e.g., in a random access procedure).

[0316] In some embodiments, the implementation of step S3103 can refer to the implementation of step S2104 in FIG. 2a, which will not be repeated here.

[0317] In some embodiments, the implementation of step S3103 can refer to the implementation of step S2204 in FIG. 2b, which will not be repeated here.

[0318] The method related to the embodiments of the present disclosure can include at least one of steps S3101-S3103.

[0319] In some embodiments, other optional implementations can be described before or after the corresponding description of FIG. 3a.

[0320] FIG. 3b is a flow diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in FIG. 3b, the embodiments of the present disclosure relate to a communication method, which is performed by a terminal 101, and the above method includes:

[0321] Step S3201: sending request information to a network device 102 based on a sensing task.

[0322] In some embodiments, the implementation of step S3201 can refer to the implementation of step S2104 in FIG. 2a, which will not be repeated here.

[0323] In some embodiments, the implementation of step S3201 can refer to the implementation of step S2204 in FIG. 2b, which will not be repeated here.

[0324] In some embodiments, other optional implementations can be described before or after the corresponding description of FIG. 3b.

[0325] FIG. 4a is a flow diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in FIG. 4a, the embodiment of the present disclosure relates to a communication method, which is performed by the network device 102, and the above method comprises the following steps:

[0326] In step S4101, UAC configuration and / or configuration information is sent.

[0327] In some embodiments, the implementation of step S4101 can refer to the implementation of step S2101 in FIG. 2a, which will not be repeated here.

[0328] In some embodiments, the implementation of step S4101 can refer to the implementation of step S2201 in FIG. 2b, which will not be repeated here.

[0329] In step S4102, request information is received.

[0330] In some embodiments, the implementation of step S4102 can refer to the implementation of step S2104 in FIG. 2a, which will not be repeated here.

[0331] In some embodiments, the implementation of step S4102 can refer to the implementation of step S2204 in FIG. 2b, which will not be repeated here.

[0332] The method according to the embodiment of the present disclosure can comprise at least one of steps S4101-S4102.

[0333] In some embodiments, other optional implementations can be referred to the description before or after the corresponding description of FIG. 4a.

[0334] FIG. 4b is a flow diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in FIG. 4b, the embodiment of the present disclosure relates to a communication method, which is performed by the network device 102, and the above method comprises the following steps:

[0335] In step S4201, the network device 102 receives the request information sent by the terminal 101.

[0336] In some embodiments, the implementation of step S4201 can refer to the implementation of step S2104 in FIG. 2a, which will not be repeated here.

[0337] In some embodiments, the implementation of step S4201 can refer to the implementation of step S2204 in FIG. 2b, which will not be repeated here.

[0338] In some embodiments, other optional implementations can be referred to the description before or after the corresponding description of FIG. 4b.

[0339] The method provided by the embodiments of the present disclosure can enable the RRC_IDLE / INACTIVE terminal to initiate a sensing service, quickly establish an RRC connection, and further quickly establish a sensing task, thereby meeting the latency requirement of the sensing task and improving the service performance. In order to facilitate understanding of the embodiments of the present disclosure, some specific embodiments are listed as follows:

[0340] Embodiment one:

[0341] The present embodiment defines or configures an ISAC-specific MSG3 cause.

[0342] Whether the RRC (between UE and base station) layer of the terminal or the ISAC service layer (between UE and SF-C) wants to establish an ISAC task, initiates an RRC connection establishment process, or an RRC connection recovery process, the present embodiment can define a new MSG3 cause, i.e., an RRC connection establishment cause and an RRC connection recovery cause. The cause value is mo-ISAC, meaning that the cause of the RRC connection establishment or the RRC connection recovery is to initially establish an ISAC sensing task.

[0343] The configuration can be referred to as follows:

[0344] Embodiment two:

[0345] The present embodiment defines or configures an ISAC-specific UAC cat or access identity.

[0346] Whether the RRC (between UE and base station) layer of the terminal or the ISAC service layer (between UE and SF-C) wants to establish an ISAC task, initiates an RRC connection establishment process, or an RRC connection recovery process, the present embodiment can define a new MSG3 cause, i.e., an RRC connection establishment cause and an RRC connection recovery cause. The cause value is mo-ISAC, meaning that the cause of the RRC connection establishment or the RRC connection recovery is to initially establish an ISAC sensing task.

[0347] Option 1: Define an ISAC-specific UAC category.

[0348] The access category number of the ISAC access is defined as n. The access attempt is ISAC or ISAC request.

[0349] The UE obtains the UAC configuration parameters configured in the system broadcast, and the parameters include the related access configuration parameters of the access category number n. The content included in the parameters can be referred to as shown in FIG. 2c.

[0350] UE initiates RRC connection establishment or RRC connection resume due to ISAC, performs access decision according to the UAC configuration.

[0351] If the bit corresponding to the access identities in uac-BarringForAccessIdentity is set to 0, it means access is allowed, if the bit is set to 1, further decision is needed:

[0352] Generate a random number 0≤rand<1, if the random number is lower than uac-BarringFactor, it means access is allowed, otherwise, it means access is barred. If access is barred, generate a random number 0≤rand<1, start T390 and T390=(0.7+0.6*rand)*uac-BarringTime.

[0353] Further, the Access category and MSG3 cause are one-to-one corresponding.

[0354] Option 2: Define ISAC-specific UAC Access Identity.

[0355] Define a new access identity, for example, access identity 3, which means that the terminal accessing is ISAC service.

[0356] The UE acquires the UAC configuration parameters configured in the system broadcast, the contents of the parameters can refer to Figure 2c.

[0357] UE initiates RRC connection establishment or RRC connection resume due to ISAC, performs access decision according to the UAC configuration.

[0358] If the bit corresponding to the access identities (for example, 3 for ISAC) in uac-BarringForAccessIdentity is set to 0, it means access is allowed, if the bit is set to 1, further decision is needed:

[0359] Generate a random number 0≤rand<1, if the random number is lower than uac-BarringFactor, it means access is allowed, otherwise, it means access is barred. If access is barred, generate a random number 0≤rand<1, start T390 and T390=(0.7+0.6*rand)*uac-BarringTime.

[0360] Embodiment three:

[0361] This embodiment defines or configures high priority RACH for ISAC.

[0362] Option 1: Define high priority RACH based on the event triggering RACH.

[0363] If the event triggering RACH is ISAC related, such as ISAC establishment, etc., and the RACH procedure needs to be initiated, the high priority RACH parameters dedicated to ISAC are used, and the high priority RACH configuration parameters include one or more combinations of the following: power ramping step, backoff factor, initial target received power preambleReceivedTargetPower, preamble maximum transmission times preambleTransMax.

[0364] The power ramping step is used for the UE to ramp up the MSG1 transmission power in the random access procedure. The power ramping step for ISAC event triggered RACH configuration is larger than that for normal RACH, so that the random access can be quickly successful. The backoff factor is used for the UE to determine the backoff value in the random access procedure, i.e. the backoff factor SCALING_FACTOR_BI multiplied by PREAMBLE_BACKOFF, wherein PREAMBLE_BACKOFF is the backoff value given by the network. The initial received power is a parameter for setting the transmission power for sending MSG1. If this parameter is set larger, the UE can transmit with a larger power when sending MSG1 in the ISAC related random access, reducing the power ramping times and speeding up the ISAC related random access establishment process. The preamble maximum transmission times preambleTransMax is the maximum transmission times of preamble in the random access procedure. If the maximum transmission times is reached, the random process is considered to have failed. In order to quickly reduce the time interval of cell reselection, the preamble maximum transmission times preambleTransMax needs to be set relatively small, so that the UE can select other candidate cells as soon as possible.

[0365] That is, for the RACH procedure triggered for ISAC reasons, the UE uses the above configuration for power ramping and backoff avoidance in the random access procedure.

[0366] Option 2: Define high priority RACH based on access identity.

[0367] High priority RACH parameters and access identity are associated, when in access procedure, for specific access identity, corresponding high priority RACH configuration parameters are used in RACH procedure execution, RACH procedure is executed.

[0368] High priority RACH configuration parameters include one or more combinations of the following: power ramping step, backoff factor, initial target received power preambleReceivedTargetPower, preamble maximum transmission times preambleTransMax.

[0369] The power ramping step is used for the UE to step up the MSG1 sending power in the random access procedure, and the power ramping step for the ISAC event triggered RACH configuration is larger than that for the normal RACH, so that the random access can be quickly successful. The backoff factor is used for the UE to determine the backoff value in the random access procedure, that is, the backoff factor SCALING_FACTOR_BI multiplied by PREAMBLE_BACKOFF, wherein PREAMBLE_BACKOFF is the backoff value given by the network. The initial received power is a parameter for setting the sending power of sending MSG1, and if the parameter is set larger, the UE can send according to a larger power when sending MSG1 in the ISAC related random access, reduce the power ramping times, and speed up the ISAC related random access establishment process. The preamble maximum transmission times preambleTransMax is the maximum transmission times of preamble in the random access procedure, and if the maximum transmission times is reached, the random procedure is considered to fail. In order to quickly reduce the time interval of cell reselection, the preamble maximum transmission times preambleTransMax needs to be set relatively small, so that the UE can select other candidate cells as soon as possible.

[0370] That is, for the RACH procedure triggered by ISAC, the UE uses the above configuration for power ramping and backoff avoidance in the random access procedure.

[0371] Option 3: Define high priority RACH based on access category or MSG3 cause value.

[0372] High priority RACH parameters and access category or MSG3 cause are associated, when in access procedure, for specific access category or MSG3 cause, corresponding high priority RACH configuration parameters are used in RACH procedure execution, RACH procedure is executed.

[0373] The high-priority RACH configuration parameter includes one or more combinations of the following: a power ramping step, a backoff factor, an initial target received power preambleReceivedTargetPower, and a preamble maximum transmission number preambleTransMax.

[0374] The power ramping step is used for the UE to ramp up the MSG1 transmission power in the random access procedure. The power ramping step for the ISAC event triggered RACH configuration is larger than that of the normal RACH, so that the random access can be quickly successful. The backoff factor is used for the UE to determine the backoff value in the random access procedure, that is, the backoff factor SCALING_FACTOR_BI multiplied by PREAMBLE_BACKOFF, wherein PREAMBLE_BACKOFF is the backoff value given by the network. The initial received power is a parameter for setting the transmission power of MSG1. If the parameter is set to be larger, the UE can transmit MSG1 at a larger power in the ISAC related random access, reduce the power ramping number, and speed up the ISAC related random access establishment process. The preamble maximum transmission number preambleTransMax is the maximum transmission number of the preamble in the random access procedure. If the maximum transmission number is reached, the random access procedure is considered to fail. In order to quickly reduce the cell reselection time interval, the preamble maximum transmission number preambleTransMax needs to be set to be relatively small, so that the UE can select other candidate cells as soon as possible.

[0375] That is, for the RACH procedure triggered by the ISAC reason, the UE uses the above configuration for power ramping and backoff avoidance in the random access procedure.

[0376] Embodiment Four

[0377] In this embodiment, if the RRC connection establishment or the RRC connection recovery is initiated due to the ISAC reason, the supported sensing mode or the expected sensing mode is indicated in the RRC connection establishment complete message or the RRC connection recovery message. Alternatively, the supported or preferred sensing capability, sensing mode, sensing frequency band resource, and the like are carried in the UE capability container.

[0378] The embodiments of the present disclosure further provide a device for implementing any of the above methods. For example, a device is provided, which includes units or modules for implementing the steps performed by the terminal in any of the above methods. For another example, another device is provided, which includes units or modules for implementing the steps performed by the network device (such as an access network device, a core network function node, a core network device, and the like) in any of the above methods.

[0379] It should be understood that the division of each unit or module in the above apparatus is only a logical function division, and all or part of them can be integrated into a physical entity or physically separated in actual implementation. In addition, the units or modules in the apparatus can be implemented in the form of processor calling software: for example, the apparatus includes a processor connected with a memory, the memory stores instructions, and the processor calls the instructions stored in the memory to implement any of the above methods or realize the functions of the units or modules of the above apparatus, wherein the processor is a general processor such as a central processing unit (CPU) or a microprocessor, and the memory is a memory in the apparatus or a memory outside the apparatus. Alternatively, the units or modules in the apparatus can be implemented in the form of hardware circuit, and the functions of part or all of the units or modules can be realized by the design of the hardware circuit. The above hardware circuit can be understood as one or more processors; for example, in one implementation, the above hardware circuit is an application-specific integrated circuit (ASIC), and the functions of part or all of the units or modules are realized by the design of the logical relationship between the elements in the circuit; for another example, in another implementation, the above hardware circuit is a programmable logic device (PLD), and a field programmable gate array (FPGA) is taken as an example, which can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by a configuration file, so as to realize the functions of part or all of the units or modules. All units or modules of the above apparatus can be implemented in the form of processor calling software, or all units or modules can be implemented in the form of hardware circuit, or part of the units or modules are implemented in the form of processor calling software, and the remaining part is implemented in the form of hardware circuit.

[0380] In the embodiments of the present disclosure, the processor is a circuit with signal processing capability. In one implementation, the processor can be a circuit with instruction reading and running capability, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), a digital signal processor (DSP), and the like. In another implementation, the processor can implement certain functions through a logical relationship of hardware circuit, and the logical relationship of the hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In the reconfigurable hardware circuit, the processor loads a configuration document to implement the configuration of the hardware circuit. It can be understood that the processor loads instructions to implement the functions of part or all of the units or modules described above. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), and the like.

[0381] FIG. 5a is a structural schematic diagram of a terminal according to an embodiment of the present disclosure. As shown in FIG. 5a, the terminal 5100 can include at least one of a transceiver module 5101, a processing module 5102, and the like. In some embodiments, the transceiver module 5101 is configured to send, to a network device, request information related to a perception task, wherein the request information is used to request establishment of a radio resource control (RRC) connection or request RRC connection recovery.

[0382] Optionally, the transceiver module 5101 is configured to perform at least one of the communication steps, such as sending and / or receiving, performed by the terminal 101 in any of the methods described above. Details are not described herein again. Optionally, the processing module 5102 is configured to perform at least one of the other steps performed by the terminal 101 in any of the methods described above. Details are not described herein again.

[0383] FIG. 5b is a structural diagram of a network device according to an embodiment of the present disclosure. As shown in FIG. 5b, the network device 5200 can include at least one of a transceiver module 5201, a processing module 5202, and the like. In some embodiments, the transceiver module 5201 is configured to receive the request information sent by the terminal, wherein the request information is related to the perception task, and the request information is used to request to establish a radio resource control (RRC) connection or to request to resume the RRC connection.

[0384] In some embodiments, the transceiver module can include a sending module and / or a receiving module, and the sending module and the receiving module can be separate or integrated together. Optionally, the transceiver module can be replaced by a transceiver.

[0385] In some embodiments, the processing module can be one module or can include multiple sub-modules. Optionally, the multiple sub-modules are respectively configured to perform all or part of the steps required by the processing module. Optionally, the processing module can be replaced by a processor.

[0386] FIG. 6a is a structural diagram of a communication device 6100 according to an embodiment of the present disclosure. The communication device 6100 can be a network device (such as an access network device, a core network device, and the like), a terminal (such as a user equipment, and the like), a chip, a chip system, or a processor supporting the network device to implement any of the above methods, or a chip, a chip system, or a processor supporting the terminal to implement any of the above methods. The communication device 6100 can be used to implement the methods described in the above method embodiments, and details can be referred to the descriptions in the above method embodiments.

[0387] As shown in FIG. 6a, the communication device 6100 includes one or more processors 6101. The processor 6101 can be a general-purpose processor or a special-purpose processor, for example, a baseband processor or a central processing unit. The baseband processor can be configured to process a communication protocol and communication data, and the central processing unit can be configured to control a communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, and the like), execute a program, and process data of the program. Optionally, the communication device 6100 is configured to implement any of the above methods. Optionally, the one or more processors 6101 are configured to invoke instructions to cause the communication device 6100 to implement any of the above methods.

[0388] In some embodiments, the communication device 6100 further includes one or more transceivers 6102. When the communication device 6100 includes one or more transceivers 6102, the transceiver 6102 performs at least one of the communication steps of sending and / or receiving in the above-described methods, and the processor 6101 performs at least one of the other steps. In alternative embodiments, the transceiver can include a receiver and / or a transmitter, which can be separate or integrated together. Alternatively, the terms transceiver, transceiving unit, transceiver, transceiving circuit, interface circuit, interface, etc. can be replaced by each other, the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc. can be replaced by each other, and the terms receiver, receiving unit, receiver, receiving circuit, etc. can be replaced by each other.

[0389] In some embodiments, the communication device 6100 further includes one or more memories 6103 for storing data. Alternatively, all or part of the memory 6103 can also be outside the communication device 6100. In alternative embodiments, the communication device 6100 can include one or more interface circuits 6104. Alternatively, the interface circuit 6104 is connected with the memory 6103, and the interface circuit 6104 can be used to receive data from the memory 6103 or other devices, and can be used to send data to the memory 6103 or other devices. For example, the interface circuit 6104 can read the data stored in the memory 6103 and send the data to the processor 6101.

[0390] The communication device 6100 described in the above embodiments can be a network device or a terminal, but the scope of the communication device 6100 described in the present disclosure is not limited thereto, and the structure of the communication device 6100 can not be limited by Figure 6a. The communication device can be a standalone device or can be part of a larger device. For example, the communication device can be: 1) a standalone integrated circuit (IC), or a chip, or a chip system or subsystem; (2) a set of one or more ICs, which can optionally include storage components for storing data, programs; (3) an ASIC, such as a Modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, a smart terminal device, a cellular phone, a wireless device, a handset, a mobile unit, a vehicle-mounted device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0391] Figure 6b is a structural schematic diagram of a chip 6200 according to an embodiment of the present disclosure. For the case where the communication device 6100 is a chip or a chip system, the structural schematic diagram of the chip 6200 shown in Figure 6b can be referred to, but is not limited thereto.

[0392] The chip 6200 includes one or more processors 6201. The chip 6200 is configured to perform any of the above methods.

[0393] In some embodiments, chip 6200 further includes one or more interface circuits 6202. Optionally, the terms interface circuits, interface, transceiver pin, etc. can replace each other. In some embodiments, chip 6200 further includes one or more memories 6203 for storing data. Optionally, all or part of memory 6203 can be outside chip 6200. Optionally, interface circuit 6202 is connected with memory 6203, and interface circuit 6202 can be used to receive data from memory 6203 or other devices, and interface circuit 6202 can be used to send data to memory 6203 or other devices. For example, interface circuit 6202 can read data stored in memory 6203 and send the data to processor 6201.

[0394] In some embodiments, interface circuit 6202 performs at least one of the communication steps such as sending and / or receiving in the above-mentioned methods. The communication steps such as sending and / or receiving performed by interface circuit 6202 in the above-mentioned methods refer to that interface circuit 6202 performs data interaction between processor 6201, chip 6200, memory 6203 or transceiver devices. In some embodiments, processor 6201 performs at least one of the other steps.

[0395] The modules and / or devices described in each embodiment of virtual device, physical device, chip, etc. can be combined or separated as appropriate. Optionally, part or all of the steps can also be performed by multiple modules and / or devices, which are not limited here.

[0396] The disclosure further proposes a storage medium, and the above-mentioned storage medium stores instructions, when the above-mentioned instructions run on communication device 6100, the above-mentioned instructions make communication device 6100 perform any one of the above-mentioned methods. Optionally, the above-mentioned storage medium is an electronic storage medium. Optionally, the above-mentioned storage medium is a computer readable storage medium, but is not limited to this, and it can also be a storage medium readable by other devices. Optionally, the above-mentioned storage medium can be a non-transitory storage medium, but is not limited to this, and it can also be a transitory storage medium.

[0397] The disclosure further proposes a program product, and the above-mentioned program product is executed by communication device 6100, and the above-mentioned program product makes communication device 6100 perform any one of the above-mentioned methods. Optionally, the above-mentioned program product is a computer program product.

[0398] The disclosure further proposes a computer program, and when the computer program runs on a computer, the computer program makes the computer perform any one of the above-mentioned methods. Industrial applicability

[0399] In a scenario where the terminal triggers a connection by a sensing task, the terminal can send request information related to the sensing task, so that the network device can quickly process the connection establishment related to the sensing task, reduce the latency, and meet the requirement of the sensing task for the latency.

Claims

A communication method performed by a terminal, the method comprising: sending, to a network device, request information based on a sensing task, the request information being related to the sensing task, wherein the request information is used to request establishment of a radio resource control (RRC) connection or request RRC connection resume. The method of claim 1, wherein the request information comprises a third message (MSG3) cause, wherein, in a case that the MSG3 cause has a first value, the MSG3 cause indicates that an RRC connection establishment cause and / or an RRC connection resume cause is the sensing task. The method of claim 2, wherein the request information is sent via a MSG3. The method of any one of claims 1-3, wherein the sensing task is associated with at least one of: a unified access control (UAC) access category (AC), and a UAC access identity (AI); wherein a parameter value of the UAC access category is a second value, and a parameter value of the UAC access identity is a third value. The method of claim 4, wherein, Before sending the request information to the network device, the method further comprises: performing an access attempt corresponding to the sensing task, wherein the access attempt corresponds to the UAC access category. The method of claim 4 or 5, wherein, The method further comprises: obtaining a UAC parameter related to the second value, the UAC parameter comprising at least one of: a barring factor; a barring duration; a bitmap of UAC access identities. The method of claim 6, wherein, Before sending the request information to the network device, the method further comprises: determining, according to the UAC parameter, whether to allow performing an access procedure. The method of claim 7, wherein, The determining, according to the UAC parameter, whether to allow performing an access procedure, comprises: in the bitmap of UAC access identities, if a bit value corresponding to a UAC access identity associated with the sensing task is a fourth value, determining to allow performing the access procedure; or in the bitmap, if the bit value corresponding to the UAC access identity associated with the sensing task is a fifth value, determining, based on the barring factor, whether to allow performing the access procedure. The method of claim 8, wherein, The determining, based on the barring factor, whether to allow performing the access procedure, comprises: generating a first random number, and determining to allow performing the access procedure when the first random number is less than the barring factor; or generating a second random number, and determining to allow performing the access procedure after a first duration, wherein the first duration is determined according to the second random number and the barring duration. The method of any one of claims 4-9, wherein the UAC access category (AC) and / or the UAC access identity (AI) corresponds to a MSG3 cause. The method of any one of claims 1 to 10, wherein, The method further comprises: receiving configuration information sent by the network device, the configuration information comprising a random access priority parameter corresponding to the sensing task. The method of claim 11, wherein, The method further comprises: initiating, to the network device, a random access procedure according to the random access priority parameter corresponding to the sensing task. The method of claim 11 or 12, wherein, The random access priority parameter comprises at least one of: a power ramping step; a scaling factor of a backoff indication (BI); an initial target received power; a maximum number of preamble transmissions; and a random access priority. The power ramping step is greater than a sixth value, and / or the maximum number of transmissions is less than a seventh value; the sixth value is greater than or equal to a power ramping step of other random access procedures except for the random access procedure corresponding to the sensing task, and the seventh value is greater than or equal to a maximum number of transmissions of the other random access procedures. The method of any one of claims 11 to 13, wherein, The random access priority parameter is associated with at least one of the following: a sensing-related event triggering random access; an MSG3 cause associated with the sensing task; an UAC access type associated with the sensing task; an UAC access identity associated with the sensing task. The method of any one of claims 1 to 14, wherein, The method further includes: sending, to the network device, indication information indicating sensing information supported by the terminal. The method of claim 15, wherein, The sensing information is at least one of the following: a sensing mode; a sensing capability; sensing frequency domain information. The method of any one of claims 1-16, wherein the network device is an access network device or a sensing function control node. A communication method, performed by a network device, the method comprising: receiving request information sent by a terminal, wherein the request information is related to a sensing task, and the request information is used to request establishment of a radio resource control (RRC) connection or request RRC connection recovery. The method of claim 18, wherein the request information includes a third message (MSG3) cause, and when the MSG3 cause value is a first value, the MSG3 cause indicates an RRC connection establishment cause and / or an RRC connection recovery cause. The method of claim 19, wherein the request information is sent through an MSG3. The method of any one of claims 18-20, wherein the sensing task is associated with at least one of the following: a unified access control (UAC) access type (AC) and a UAC access identity (AI); wherein a parameter value of the UAC access type is a second value, and a parameter value of the UAC access identity is a third value. The method of claim 21, wherein, The UAC parameter related to the second value includes at least one of the following: a barring factor; a barring time length; a bitmap of the UAC access identity. The method of claim 22, wherein the UAC parameter is used to determine whether to allow the terminal to perform an access procedure. The method of claim 23, wherein in the bitmap of the UAC access identity, when a bit value corresponding to a UAC access identity associated with a sensing task is a fourth value, the terminal is allowed to perform an access procedure; or in the bitmap, if a bit value corresponding to a UAC access identity associated with a sensing task is a fifth value, whether to allow the terminal to perform an access procedure is determined based on the barring factor. The method of claim 24, wherein when a first random number is less than the barring factor, the terminal is allowed to perform an access procedure; or when the first random number is greater than or equal to the barring factor, the terminal is allowed to perform an access procedure after a first time length, which is determined according to a second random number and the barring time length. The method of any one of claims 21-25, wherein The UAC access type AC and / or the UAC access identity AI correspond to a MSG3 cause. The method of any one of claims 18 to 26, wherein, The method further includes: sending configuration information to the terminal, the configuration information including a random access priority parameter corresponding to the sensing task. The method of claim 27, wherein, The random access priority parameter includes at least one of: a power ramping step; a backoff indication BI scaling factor; an initial target received power; a maximum number of preamble transmissions; wherein the power ramping step is greater than a sixth value, and / or the maximum number of preamble transmissions is less than a seventh value; the sixth value is greater than or equal to a power ramping step of a random access procedure other than the random access procedure corresponding to the sensing task, and the seventh value is greater than or equal to a maximum number of preamble transmissions of the other random access procedure. The method of claim 27 or 28, wherein, The random access priority parameter is associated with at least one of: a sensing-related event triggering random access; a MSG3 cause associated with the sensing task; a UAC access type associated with the sensing task; a UAC access identity associated with the sensing task. The method of any one of claims 18 to 29, wherein, The method further includes: receiving indication information sent by the terminal, the indication information being used to indicate sensing information supported by the terminal. The method of claim 30, wherein, The sensing information is at least one of: a sensing mode; a sensing capability; sensing frequency domain information. The method of any one of claims 18-31, wherein The network device is an access network device or a sensing function control node. A terminal device, comprising: a transceiver module configured to send request information related to a sensing task to a network device, the request information being used to request establishment of a radio resource control (RRC) connection or request RRC connection recovery. A network device, comprising: a transceiver module configured to receive request information sent by a terminal, the request information being related to a sensing task, the request information being used to request establishment of a radio resource control (RRC) connection or request RRC connection recovery. A communication device, comprising: one or more processors; wherein the communication device is configured to implement the method of any one of claims 1-17 or any one of claims 18-32. A storage medium storing instructions, wherein when the instructions run on a communication device, the communication device is caused to perform the method of any one of claims 1-17 or any one of claims 18-32. A program product, wherein when the program product is executed by a communication device, the communication device is caused to perform the method of any one of claims 1-17 or any one of claims 18-32.

Images