Sidelink monitoring methods, terminals, communication system, and storage medium

Abstract

The present disclosure relates to sidelink monitoring methods, terminals, a communication system, and a storage medium. A method comprises: a first terminal sending first information to a second terminal, wherein the first information is used for indicating at least one sidelink discontinuous reception (SL DRX) configuration, the at least one SL DRX configuration is used by the second terminal to determine a first activation time, and the first activation time is used by the second terminal to monitor a sidelink. The monitoring of the sidelink by the second terminal can be effectively reduced, thereby reducing the energy consumption.

Description

Sidelink monitoring method, terminal, communication system and storage medium Technical Field

[0001] The present disclosure relates to the field of communication technologies, and in particular to a sidelink monitoring method, a terminal, a communication system, and a storage medium. Background Art

[0002] In order to support direct communication between UEs (user equipment), a sidelink communication mode is introduced. According to the corresponding relationship between the sending UE and the receiving UE, three transmission modes are supported on the sidelink: unicast, multicast and broadcast.

[0003] Summary of the Invention

[0004] The current sidelink monitoring control method may cause the UE to monitor additional sidelink channels.

[0005] The embodiments of the present disclosure provide a sidelink monitoring method, a terminal, a communication system, and a storage medium.

[0006] According to a first aspect of an embodiment of the present disclosure, a sidelink monitoring method is proposed, the method comprising:

[0007] The first terminal sends first information to the second terminal, where the first information is used to indicate at least one set of sidelink discontinuous reception SL DRX configuration, and the at least one set of SL DRX configuration is used by the second terminal to determine a first activation time, and the first activation time is used by the second terminal to monitor the sidelink.

[0008] According to a second aspect of an embodiment of the present disclosure, a sidelink monitoring method is proposed, the method comprising:

[0009] The second terminal receives first information sent by the first terminal, where the first information is used to indicate at least one set of sidelink discontinuous reception (SL DRX) configuration;

[0010] determining a first activation time according to the at least one set of SL DRX configurations;

[0011] The sidelink is monitored according to the first activation time.

[0012] According to a third aspect of an embodiment of the present disclosure, a first terminal is provided, the first terminal including:

[0013] The transceiver module is configured to send first information to the second terminal, where the first information is used to indicate at least one set of sidelink discontinuous reception SL DRX configuration, and the at least one set of SL DRX configuration is used by the second terminal to determine a first activation time, and the first activation time is used by the second terminal to monitor the sidelink.

[0014] According to a fourth aspect of an embodiment of the present disclosure, a second terminal is provided, the second terminal including:

[0015] The transceiver module is configured to receive first information sent by a first terminal, where the first information is used to indicate at least one set of sidelink discontinuous reception (SL DRX) configuration;

[0016] a processing module configured to determine a first activation time according to the at least one set of SL DRX configurations;

[0017] The monitoring module is configured to monitor the sidelink transmission according to the first activation time.

[0018] According to a fifth aspect of an embodiment of the present disclosure, a first terminal is provided, including:

[0019] one or more processors;

[0020] The first terminal is used to execute the sidelink monitoring method described in the first aspect.

[0021] According to a sixth aspect of an embodiment of the present disclosure, a second terminal is provided, characterized by comprising:

[0022] one or more processors;

[0023] The second terminal is used to execute the sidelink monitoring method described in the second aspect.

[0024] According to the seventh aspect of an embodiment of the present disclosure, a communication system is proposed, characterized in that it includes a first terminal and a second terminal, wherein the first terminal is configured to implement the side link monitoring method described in the first aspect, and the second terminal is configured to implement the side link monitoring method described in the second aspect.

[0025] According to an eighth aspect of an embodiment of the present disclosure, a storage medium is proposed, which stores instructions, and is characterized in that when the instructions are executed on a communication device, the communication device executes the side link monitoring method as described in the first aspect or the second aspect.

[0026] This can effectively reduce the monitoring of the side link by the second terminal and reduce energy consumption. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following drawings required for describing the embodiments are introduced. The following drawings are merely some embodiments of the present disclosure and do not impose specific limitations on the protection scope of the present disclosure.

[0028] FIG1A is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure.

[0029] FIG1B is another exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure.

[0030] FIG2 is an exemplary interactive diagram of a sidelink monitoring method provided according to an embodiment of the present disclosure.

[0031] FIG3A is an exemplary flowchart of a sidelink monitoring method according to an embodiment of the present disclosure.

[0032] FIG3B is an exemplary flowchart of a sidelink monitoring method according to an embodiment of the present disclosure.

[0033] FIG3C is an exemplary flowchart of a sidelink monitoring method according to an embodiment of the present disclosure.

[0034] FIG3D is an exemplary flowchart of a sidelink monitoring method according to an embodiment of the present disclosure.

[0035] FIG4A is an exemplary flowchart of a sidelink monitoring method according to an embodiment of the present disclosure.

[0036] FIG4B is an exemplary flowchart of a sidelink monitoring method according to an embodiment of the present disclosure.

[0037] FIG5 is an exemplary interactive diagram of a sidelink monitoring method provided according to an embodiment of the present disclosure.

[0038] FIG6A is an exemplary flowchart of a sidelink monitoring method according to an embodiment of the present disclosure.

[0039] FIG6B is an exemplary flowchart of a sidelink monitoring method according to an embodiment of the present disclosure.

[0040] FIG7A is a schematic diagram of an exemplary structure of a first terminal provided according to an embodiment of the present disclosure.

[0041] FIG7B is a schematic diagram of an exemplary structure of a first terminal provided according to an embodiment of the present disclosure.

[0042] FIG8A is a schematic diagram of an exemplary structure of a communication device provided according to an embodiment of the present disclosure.

[0043] FIG8B is a schematic diagram of an exemplary structure of a chip provided according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0044] The embodiments of the present disclosure provide a sidelink monitoring method, a terminal, a communication system, and a storage medium.

[0045] In a first aspect, an embodiment of the present disclosure provides a sidelink monitoring method, the method comprising:

[0046] The first terminal sends first information to the second terminal, where the first information is used to indicate at least one set of sidelink discontinuous reception (SL DRX) configuration, and the at least one set of SL DRX configuration is used by the second terminal to determine a first activation time, and the first activation time is used by the second terminal to monitor the sidelink.

[0047] In the above embodiment, the first information is sent to the second terminal by the first terminal, and at least one set of SL DRX configuration is indicated to the second terminal through the first information, so that the second terminal can determine the activation time based on the at least one set of SL DRX configuration, and realize discontinuous reception of the side link based on the at least one set of SL DRX configuration, which can effectively reduce the second terminal's monitoring of the side link and reduce energy consumption.

[0048] In combination with some embodiments of the first aspect, in some embodiments, the first activation time is used for the second terminal to monitor the physical sidelink control channel (Physical Sidelink Control Channel, PSCCH) and / or the physical sidelink shared channel (Physical Sidelink Shared Channel, PSSCH).

[0049] In the above embodiment, the second terminal can monitor PSCCH and / or PSSCH, and can ensure that the sidelink control information (Sidelink Control Information, SCI) or the second stage SCI can be reliably received based on the discontinuous reception of the sidelink while ensuring low energy consumption.

[0050] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0051] A first identifier is sent to the second terminal, where the first identifier is used to indicate the service corresponding to each of the at least one set of SL DRX configurations, and the service includes at least one of the following: unicast service, broadcast service, and multicast service.

[0052] In the above embodiment, the first terminal can indicate to the second terminal the service corresponding to each set of SL DRX configuration in the first information through the first identifier, which not only enables the second terminal to make a more reasonable selection of SL DRX configuration for different services, but also can indicate different SL DRX configurations for unicast services, broadcast services, and multicast services respectively, thereby ensuring the reliability of the second terminal's discontinuous reception of different services.

[0053] In conjunction with some embodiments of the first aspect, in some embodiments, the method includes:

[0054] receiving third information sent by the network device, where the third information is used to indicate a multicast or broadcast configuration message;

[0055] receiving second information sent by the second terminal, where the second information is used to indicate a first multicast or broadcast service required by the second terminal;

[0056] determining a DRX configuration and / or a group radio network temporary identity (G-RNTI) corresponding to the first multicast or broadcast service in the multicast or broadcast configuration message;

[0057] A second activation time is determined according to the DRX configuration and / or the G-RNTI, where the second activation time is used for the first terminal to monitor a physical downlink control channel (PDCCH) corresponding to the G-RNTI sent by the network device.

[0058] In the above embodiment, the second terminal can indicate the multicast or broadcast service it needs through the second information, and the first terminal can then determine the corresponding DRX configuration and / or G-RNTI from the multicast or broadcast configuration message indicated by the network device based on the multicast or broadcast service required by the second terminal, and determine the activation time based on the DRX configuration and / or G-RNTI, and enable the second terminal to monitor the PDCCH sent by the network device based on the second activation time and G-RNTI, while ensuring that the first terminal and the second terminal can reliably perform non-continuous communication, further reducing the power consumption of the second terminal.

[0059] In conjunction with some embodiments of the first aspect, in some embodiments, the method includes:

[0060] receiving third information sent by the network device, where the third information is used to indicate a multicast or broadcast configuration message;

[0061] The at least one set of SL DRX configurations is determined according to the multicast or broadcast configuration message.

[0062] In the above embodiment, the first terminal can determine at least one set of SL DRX configurations based on the multicast or broadcast configuration message indicated by the network device through the third information, and indicate the at least one set of SL DRX configurations to the second terminal through the first information, which can effectively ensure the reliability of the discontinuous reception of the side link of the second terminal.

[0063] In combination with some embodiments of the first aspect, in some embodiments, the first terminal is in any of the following states: connected state, idle state, inactive state.

[0064] In the above embodiment, when the first terminal is in a connected state, an idle state or an inactivated state, at least one set of SL DRX configurations indicated by the first information can be determined based on a multicast or broadcast configuration message, which can effectively ensure the reliability of the at least one set of SL DRX configurations indicated by the first information, and further ensure the reliability of the discontinuous reception of the side link of the second terminal.

[0065] In conjunction with some embodiments of the first aspect, in some embodiments, before the first terminal sends the first information to the second terminal, the method includes:

[0066] receiving fourth information sent by the network device, where the fourth information is used to indicate a third SL DRX configuration and a terminal identifier, where the third SL DRX configuration corresponds to the terminal identifier;

[0067] Determine that the terminal identifier corresponds to the second terminal, and determine that the at least one set of SL DRX configuration is the third SL DRX configuration.

[0068] In the above embodiment, at least one set of SL DRX configurations indicated by the first information can be determined based on the fourth information sent by the network device, so that the SL DRX configuration adopted by the second terminal can be indicated by the network device, ensuring that the second terminal can reliably realize discontinuous reception of the side link.

[0069] In combination with some embodiments of the first aspect, in some embodiments, the first terminal is in a connected state.

[0070] In the above embodiment, when the first terminal is in a connected state, the SL DRX configuration included in the first information sent to the second terminal can be determined based on the third SL DRX configuration indicated by the fourth information of the network device and the terminal identifier, which can effectively ensure the reliability of at least one set of SL DRX configurations, thereby further ensuring the reliability of the discontinuous reception of the side link of the second terminal.

[0071] In conjunction with some embodiments of the first aspect, in some embodiments, the method includes:

[0072] Receive fifth information sent by the second terminal, where the fifth information is used to indicate a first SL DRX configuration, where the first SL DRX configuration is a SL DRX configuration rejected by the second terminal among the SL DRX configurations indicated by the first information.

[0073] In the above embodiment, by receiving the fifth information sent by the second terminal, the first terminal can accurately learn the SL DRX configuration rejected by the second terminal in the first information, thereby ensuring the reliability of the sidelink discontinuous reception of the second terminal.

[0074] In combination with some embodiments of the first aspect, in some embodiments, the first activation time is determined without using the first SL DRX configuration.

[0075] In the above embodiment, it can be ensured that the second terminal or the first terminal does not use these SL DRX configurations rejected by the second terminal to determine the first activation time, effectively ensuring that the second terminal is not activated at the time corresponding to these SL DRX configurations, and effectively reducing the power consumption of the second terminal.

[0076] In conjunction with some embodiments of the first aspect, in some embodiments, the method includes:

[0077] Determine that the first terminal is in a connected state, and send the fifth information and a terminal identifier corresponding to the second terminal to a network device.

[0078] In the above embodiment, the first terminal can send the SL DRX configuration rejected by the second terminal and the terminal identifier of the second terminal to the network device when it is determined that it is in a connected state, so that the network device can be aware of the SL DRX configuration rejected by the second terminal, and can avoid the network device sending information to the second terminal through the side link when the second terminal is in an inactive state, thereby effectively ensuring the reliability of the side link discontinuous reception of the second terminal.

[0079] In conjunction with some embodiments of the first aspect, in some embodiments, the method includes:

[0080] Receive sixth information sent by the second terminal, where the fifth information is used to indicate a second SL DRX configuration, and the second SL DRX configuration is an SL DRX configuration accepted by the second terminal among the SL DRX configurations indicated by the first information.

[0081] In the above embodiment, by receiving the sixth information sent by the second terminal, the first terminal can accurately know the SL DRX configuration accepted by the second terminal in the first information, thereby ensuring the reliability of the sidelink discontinuous reception of the second terminal.

[0082] In combination with some embodiments of the first aspect, in some embodiments, the first activation time is determined using the second SL DRX configuration.

[0083] In the above embodiment, it can be ensured that the second terminal or the first terminal uses the SL DRX configurations accepted by the second terminal to determine the first activation time, effectively ensuring that the second terminal can be activated only at the time corresponding to these SL DRX configurations, effectively reducing the power consumption of the second terminal.

[0084] In conjunction with some embodiments of the first aspect, in some embodiments, the method includes:

[0085] Determine that the first terminal is in a connected state, and send the sixth information and a terminal identifier corresponding to the second terminal to a network device.

[0086] In the above embodiment, the first terminal can send the SL DRX configuration accepted by the second terminal and the terminal identification of the second terminal to the network device when it is determined that it is in a connected state, so that the network device can be aware of the SL DRX configuration accepted by the second terminal, and can ensure that the network device sends information to the second terminal through the side link only when the second terminal is in an activated state, thereby effectively ensuring the reliability of the side link discontinuous reception of the second terminal.

[0087] In a second aspect, an embodiment of the present disclosure provides a sidelink monitoring method, the method comprising:

[0088] The second terminal receives first information sent by the first terminal, where the first information is used to indicate at least one set of sidelink discontinuous reception (SL DRX) configuration;

[0089] determining a first activation time according to the at least one set of SL DRX configurations;

[0090] The sidelink is monitored according to the first activation time.

[0091] In combination with some embodiments of the second aspect, in some embodiments, the first activation time is used for the second terminal to monitor at least one of the following: a physical sidelink control channel PSCCH; a physical sidelink shared channel PSSCH.

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

[0093] Receive a first identifier sent by the first terminal, where the first identifier is used to indicate the service corresponding to each of the at least one set of SL DRX configurations, and the service includes at least one of the following: unicast service, broadcast service, and multicast service.

[0094] In conjunction with some embodiments of the second aspect, in some embodiments, the method includes:

[0095] Sending second information to the first terminal, where the second information is used to indicate a first multicast or broadcast service corresponding to the second terminal;

[0096] The first multicast or broadcast service is used by the first terminal to determine the DRX configuration and / or group radio network temporary identifier G-RNTI corresponding to the first multicast or broadcast service in a multicast or broadcast configuration message, where the multicast or broadcast configuration message is indicated by a network device through third information;

[0097] The DRX configuration and / or the G-RNTI are used by the first terminal to determine a second activation time, and the second activation time is used by the first terminal to monitor a PDCCH corresponding to the G-RNTI and sent by the network device.

[0098] In combination with some embodiments of the second aspect, in some embodiments, the at least one set of SL DRX configuration is determined by the first terminal based on a multicast or broadcast configuration message, and the multicast or broadcast configuration message is indicated by the network device through third information.

[0099] In combination with some embodiments of the second aspect, in some embodiments, the first terminal is in any of the following states: connected state, idle state, and inactive state.

[0100] In combination with some embodiments of the second aspect, in some embodiments, the at least one set of SL DRX configuration is a third SL DRX configuration, the first information is determined when the first terminal determines that the terminal identifier corresponds to the second terminal, and the terminal identifier and the third SL DRX configuration are indicated by the network device to the first terminal through fourth information or third information.

[0101] In combination with some embodiments of the second aspect, in some embodiments, the first terminal is in a connected state.

[0102] In conjunction with some embodiments of the second aspect, in some embodiments, the method includes:

[0103] Fifth information is sent to the first terminal, where the fifth information is used to indicate a first SL DRX configuration, where the first SL DRX configuration is a SL DRX configuration rejected by the second terminal among the SL DRX configurations indicated by the first information.

[0104] In combination with some embodiments of the second aspect, in some embodiments, the first activation time is determined without using the first SL DRX configuration.

[0105] In conjunction with some embodiments of the second aspect, in some embodiments, the method includes:

[0106] The sixth information sent to the first terminal is used to indicate a second SL DRX configuration, and the second SL DRX configuration is an SL DRX configuration accepted by the second terminal among the SL DRX configurations indicated by the first information.

[0107] In combination with some embodiments of the second aspect, in some embodiments, the first activation time is determined using the second SL DRX configuration.

[0108] In a third aspect, an embodiment of the present disclosure proposes a first terminal, which includes at least one of a transceiver module and a processing module; wherein the first terminal is used to execute an optional implementation method of the first aspect.

[0109] In a fourth aspect, an embodiment of the present disclosure proposes a second terminal, which includes at least one of a transceiver module and a processing module; wherein the second terminal is used to execute the optional implementation method of the second aspect.

[0110] In a fifth aspect, an embodiment of the present disclosure provides a first terminal, including:

[0111] one or more processors;

[0112] The first terminal is used to execute the method described in the optional implementation manner of the first aspect.

[0113] In a sixth aspect, an embodiment of the present disclosure provides a second terminal, including:

[0114] one or more processors;

[0115] The second terminal is used to execute the method described in the optional implementation manner of the second aspect.

[0116] In the seventh aspect, an embodiment of the present disclosure proposes a communication system, comprising a first terminal and a second terminal, wherein the first terminal is configured to implement the method described in the optional implementation manner of the first aspect, and the second terminal is configured to implement the method described in the optional implementation manner of the second aspect.

[0117] In an eighth aspect, an embodiment of the present disclosure proposes a storage medium storing instructions. When the instructions are executed on a communication device, the communication device executes the method described in the optional implementation of the first aspect or the second aspect.

[0118] In a ninth aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the method described in the optional implementation manner of the first aspect or the second aspect.

[0119] In a tenth aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the method described in the xth aspect and the optional implementation of the first and second aspects.

[0120] In an eleventh aspect, an embodiment of the present disclosure provides a chip or a chip system, wherein the chip or chip system includes a processing circuit configured to execute the method described in the optional implementation of the first and second aspects above.

[0121] It is understandable that the above-mentioned terminal, access network device, first network element, second network element, core network device, communication system, storage medium, program product, computer program, chip or chip system are all used to perform the method proposed in the embodiment of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding method and will not be repeated here.

[0122] The present disclosure provides a sidelink monitoring method, terminal, communication system, and storage medium. In some embodiments, the terms "sidelink monitoring method," "information processing method," and "communication method" are interchangeable; the terms "sidelink monitoring method apparatus," "information processing apparatus," and "communication apparatus" are interchangeable; and the terms "information processing system," "communication system," and "communication system" are interchangeable.

[0123] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0124] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0125] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0126] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0127] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0128] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0129] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0130] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0131] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0132] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0133] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0134] In some embodiments, terms such as "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", and "above" can be replaced with each other, and terms such as "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", and "below" can be replaced with each other.

[0135] In some embodiments, devices and equipment can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they can also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject", etc.

[0136] In some embodiments, "network" can be interpreted as devices included in the network, such as access network equipment, core network equipment, etc.

[0137] In some embodiments, "access network device (AN device)" may also be referred to as "radio access network device (RAN device)", "base station (BS)", "radio base station", "fixed station", and in some embodiments may also be understood as "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission and / or reception point (TRP)" "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)", etc.

[0138] In some embodiments, "terminal" or "terminal device" may be referred to as "user equipment (UE)", "user terminal" "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc.

[0139] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0140] In some embodiments, data, information, etc. may be obtained with the user's consent.

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

[0142] FIG1A is a schematic diagram illustrating the architecture of a communication system according to an embodiment of the present disclosure. As shown in FIG1A , a communication system 100 includes a first terminal 101 and a second terminal 102 .

[0143] In some embodiments, the terminal 101 includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer, 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 a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and at least one of a wireless terminal device in a smart home, but is not limited thereto.

[0144] FIG1B is another schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure. As shown in FIG1B , a communication system 100 includes a first terminal 101 , a second terminal 102 , and a network device 103 .

[0145] In some embodiments, the network device 103 may include at least one of an access network device and a core network device.

[0146] In some embodiments, the access network device is, for example, a node or device that accesses a terminal to a wireless network. The access network device may include an evolved NodeB (eNB), a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved nodeB (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band 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, and at least one of an access node in a Wi-Fi system, but is not limited thereto.

[0147] In some embodiments, the technical solution of the present disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within the access network devices involved in the embodiments of the present disclosure can be transformed into internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.

[0148] In some embodiments, the access network device can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

[0149] In some embodiments, the core network device may be a single device including a first network element, a second network element, etc., or may be a plurality of devices or a group of devices, each including all or part of the first network element, the second network element, etc. The network element may be virtual or physical. The core network may include, for example, at least one of an evolved packet core (EPC), a 5G core network (5GCN), and a next generation core (NGC).

[0150] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0151] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1A or FIG1B , or a portion of the subject, but are not limited thereto. The subjects shown in FIG1A or FIG1B are examples. The communication system may include all or part of the subjects in FIG1A or FIG1B , or may include other subjects other than those in FIG1A or FIG1B . The number and form of the subjects are arbitrary. The subjects may be physical or virtual. The connection relationship between the subjects is an example. The subjects may be connected or disconnected. The connection may be in any manner, directly or indirectly, and wired or wireless.

[0152] The 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 (registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X), systems utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0153] In some embodiments of the present disclosure, in order to support direct communication between UEs, a sidelink communication mode is introduced, and the interface between UEs can be PC-5. According to the corresponding relationship between the sending and receiving UEs, three transmission modes are supported on the sidelink, namely unicast, multicast and broadcast. The sending UE sends sidelink control information (SCI) on the physical sidelink control channel (PSCCH) and sends the second stage SCI on the physical sidelink shared channel (PSSCH), which carries the resource location of the transmission data and the source and destination identifiers, etc. After receiving the SCI, the receiving UE determines whether to receive the corresponding data and which process it corresponds to based on the source UE and destination UE identifiers therein. In a unicast connection, each UE corresponds to a destination identifier. In a multicast connection, each UE can belong to one or more groups, each group corresponds to a destination identifier, and in a broadcast, all UEs correspond to at least one destination identifier.

[0154] In some embodiments, sidelink discontinuous reception (DRX) is introduced to save power in sidelink UEs. The receiving UE monitors the second-stage SCI on the PSCCH and PSSCH channels only during the active time, thereby achieving energy savings. The transmitting UE can transmit sidelink data only during the receiving UE's active time, avoiding data loss. The active time includes the duration of the wakeup timer, inactivity timer, and retransmission timer.

[0155] In some embodiments, the SL DRX configuration includes a sidelink DRX cycle, a starting offset, and a timer duration, including a sidelink on-duration timer, a sidelink inactivity timer, a sidelink round-trip timer (sidelink RTT timer), and a sidelink retransmission timer.

[0156] In some embodiments, a unicast SL DRX is sent from a transmitting UE to a receiving UE, and the receiving UE may send auxiliary information to the transmitting UE, the auxiliary information including a recommended SL DRX configuration. Only one set of SL DRX may be sent.

[0157] In some embodiments, a UE may not be directly connected to the base station but may communicate with the base station through the relay of another UE. The UE that is not connected to the base station may be called a remote UE, and the UE that provides relay function may be called a relay UE. The remote UE and the relay UE communicate through sidelink unicast. This architecture is called U2N (UE to NW) relay.

[0158] In some embodiments, even if the remote UE cannot receive the base station signal, the remote UE can still maintain communication with the network through the relay UE, thereby expanding the coverage of the network.

[0159] In some embodiments, a UE in a connected state, an idle state, or an inactive state can receive a broadcast service (Broadcast Service) sent by a base station.

[0160] In some embodiments, the base station sends a multicast broadcast service broadcast configuration (MBSBroadcastConfiguration) message on the multicast broadcast service control channel (MBS Control Channel, MCCH), which carries a multicast broadcast service information list (MBSSessionInfoList) provided by the current cell, a DRX configuration list (drx-ConfigPTM-List) and a neighboring cell list (MBSNeighbourCellList) providing multicast broadcast services.

[0161] In some embodiments, the multicast broadcast service list may carry one or more multicast or broadcast service information, each of which indicates a temporary mobile group identity (TMGI), a group radio network temporary identity (G-RNTI), a broadcast service radio bearer configuration, a list of neighboring cells supporting this multicast broadcast service, and a DRX configuration for this multicast broadcast service. TMGI is used to identify a multicast or broadcast service, and the broadcast service radio bearer configuration indicates PDCP and RLC configuration. Optionally, the DRX configuration for the multicast broadcast service is an index identifier used to determine a DRX configuration in the drx-ConfigPTM-List.

[0162] In some embodiments, in order to save power consumption of the UE on the Uu interface, the network device may configure discontinuous reception (DRX) for the UE.

[0163] In some embodiments, the UE needs to continuously monitor the PDCCH. The base station sends control information on the PDCCH to schedule uplink and downlink resources for the UE. To save UE energy, the DRX function is introduced. The UE determines whether to be active based on the DRX configuration. In the active state, the UE needs to monitor the PDCCH. In the sleep state, the UE does not need to monitor the PSCCH. This reduces the time the UE monitors the PDCCH, thereby saving power.

[0164] In the above embodiment, the remote UE may need to receive unicast, broadcast, and multicast services simultaneously. However, the arrival period and latency requirements for these three services may differ. Using only one SL DRX configuration to control sidelink monitoring may cause the UE to monitor additional sidelink channels, resulting in power consumption.

[0165] FIG2 is an interactive diagram of a sidelink monitoring method according to an embodiment of the present disclosure. As shown in FIG2 , the embodiment of the present disclosure relates to a sidelink monitoring method, which is applied to a communication system including a network device 103, a first terminal 101, and a second terminal 102. The method includes:

[0166] Step S2101 : The network device 103 sends third information (eg, an MBS broadcast configuration message) to the first terminal 101 .

[0167] In some embodiments, the first terminal 101 may be a relay terminal or a relay UE. Optionally, the second terminal 102 or other terminal may be connected to the first terminal 101 via a sidelink communication. Optionally, the second terminal 102 or other terminal may exchange information with the network device 103 via the first terminal 101. Optionally, the second terminal 102 and other terminals connected to the first terminal 101 via the sidelink may be remote terminals, remote UEs, or associated peer UEs. The disclosed embodiments do not limit the names of the first terminal 101 and the second terminal 102.

[0168] In some embodiments, the third information is used to indicate a multicast or broadcast configuration message. Optionally, the third information is used to indicate an MBS broadcast configuration message. Optionally, the third information includes the MBS broadcast configuration message. Optionally, the third information may be a Multicast Broadcast Service Control Channel (MCCH). Optionally, the third information is carried by the MCCH.

[0169] In some embodiments, the third information may be, for example, "MBS broadcast configuration message", or "MBS broadcast configuration indication information", or "multicast broadcast service control information". The embodiment of the present disclosure does not limit the name of the third information.

[0170] Optionally, the MBS broadcast configuration message may include at least one of the following provided by the current cell: a multicast broadcast service information list (MBSSessionInfoList), a DRX configuration list (drx-ConfigPTM-List) and a neighboring cell list providing multicast broadcast services (MBSNeighbourCellList).

[0171] Optionally, the multicast broadcast service information list may include one or more multicast broadcast service information. Optionally, each multicast broadcast service information may include at least one of the following: a temporary mobile group identity (TMGI), a group RNTI (G-RNTI), a broadcast service radio bearer configuration, a list of neighboring cells supporting this multicast broadcast service, and a DRX configuration for this multicast broadcast service. Optionally, a multicast broadcast service may correspond to an index identifier, which may be used to determine a DRX configuration corresponding to the multicast broadcast service in the DRX configuration list.

[0172] In some embodiments, the first terminal 101 receives third information sent by the network device 103 .

[0173] Step S2102 : The second terminal 102 sends second information (eg, TMGI) to the first terminal 101 .

[0174] In some embodiments, the second information indicates a first multicast or broadcast service required by second terminal 102. Alternatively, the second information may indicate a Multimedia Broadcast Service (MBS) required by second terminal 102. These MBSs may be referred to as first MBSs. Alternatively, the second information may indicate a Time-Travel Info (TMGI) corresponding to second terminal 102. Alternatively, the second information may be a TMGI corresponding to second terminal 102. Alternatively, first terminal 101 may determine the first MBS corresponding to second terminal 102 based on the TMGI corresponding to second terminal 102.

[0175] In some embodiments, the second information may be "TMGI indication information" or "MBS indication information", etc. The embodiment of the present disclosure does not limit the name of the second information.

[0176] In some embodiments, the first multicast or broadcast service includes one or more MBSs. For example, the first multicast or broadcast service may include a multicast service and a broadcast service. Accordingly, the second information may be used to indicate multiple MBSs. Alternatively, the second information may include multiple TMGIs.

[0177] In some embodiments, the first terminal 101 sends third information to the second terminal 102 .

[0178] Step S2103: The first terminal 101 determines the DRX configuration and / or G-RNTI.

[0179] In some embodiments, the DRX configuration and / or G-RNTI is the DRX configuration and / or G-RNTI corresponding to the first multicast or broadcast service in the multicast or broadcast configuration message. Optionally, the first terminal 101 determines the DRX configuration and / or G-RNTI corresponding to the first multicast or broadcast service in the multicast or broadcast configuration message. Optionally, the group to which the second terminal 102 belongs is the group corresponding to the G-RNTI.

[0180] In some embodiments, the first terminal 101 determines the corresponding DRX configuration and / or G-RNTI in the multicast or broadcast configuration message based on the second information, such as TMGI.

[0181] Optionally, the first multicast or broadcast service is used by the first terminal 101 to determine the DRX configuration and / or group radio network temporary identifier G-RNTI corresponding to the first multicast or broadcast service in the multicast or broadcast configuration message. Optionally, the multicast or broadcast configuration message is indicated by the network device 103 through third information.

[0182] Step S2104: The first terminal 101 determines a second activation time.

[0183] In some embodiments, the second activation time may be determined based on the DRX configuration determined in step S2103. Optionally, the DRX configuration may include one or more of the following: a DRX cycle, a start offset, and a timer duration. Optionally, the timer duration may include one or more of the following: an on-duration timer, an inactivity timer, a round-trip timer (RTT timer), and a retransmission timer. Optionally, the first terminal 101 may determine its activation time and sleep time based on the information in the DRX configuration.

[0184] In some embodiments, the first terminal 101 is in an active state during the second activation time. Optionally, the first terminal 101 is in a sleep state outside the second activation time.

[0185] Step S2105: The first terminal 101 monitors the PDCCH according to the second activation time.

[0186] In some embodiments, the first terminal 101 monitors the PDCCH sent by the network device 103 according to the second activation time. Optionally, the first terminal 101 monitors all PDCCHs sent by the network device 103 according to the second activation time. Optionally, the first terminal 101 receives all PDCCHs sent by the network device 103 according to the second activation time.

[0187] In some embodiments, the first terminal 101 monitors the PDCCH corresponding to the G-RNTI sent by the network device 103 according to the second activation time. Optionally, the first terminal 101 receives the PDCCH corresponding to the G-RNTI sent by the network device 103 according to the second activation time.

[0188] Optionally, the DRX configuration and / or the G-RNTI are used by the first terminal 101 to determine the second activation time. Optionally, the second activation time is used by the first terminal 101 to monitor a PDCCH corresponding to the G-RNTI and sent by the network device 103.

[0189] Step S2106: The first terminal 101 determines first information according to the multicast or broadcast configuration message.

[0190] In some embodiments, the first terminal 101 determines at least one set of SL DRX configurations indicated by the first information based on the multicast or broadcast configuration message. In some embodiments, the first information may include at least one set of SL DRX configurations. In some embodiments, the first terminal 101 may arbitrarily select one or more configurations from the DRX configuration list included in the MBS broadcast configuration as the SL DRX configuration indicated by the first information. Optionally, the first terminal 101 may select one or more DRX configurations corresponding to the first multicast or broadcast service from the DRX configuration list as the SL DRX configuration indicated by the first information.

[0191] In some embodiments, the at least one set of SL DRX configurations indicated by the first information includes an SL DRX configuration corresponding to a multicast service, an SL DRX configuration corresponding to a multicast service, and at least one of an SL DRX configuration corresponding to a multicast service. Optionally, the same type of service may correspond to one or more SL DRX configurations. For example, the at least one set of SL DRX configurations indicated by the first information includes five SL DRX configurations, three of which correspond to broadcast services and two correspond to multicast services.

[0192] In some embodiments, the first terminal 101 may also determine the service corresponding to each set of SL DRX configurations indicated by the first information according to the multicast or broadcast configuration message. Optionally, the first terminal 101 determines at least one set of SL DRX configurations and the first identifier indicated by the first information according to the multicast or broadcast configuration message.

[0193] In some embodiments, step S2101 and / or step S2106 are applicable to the first terminal 101 in a connected state, an idle state, or an inactive state. Optionally, the first terminal 101 is in any of the following states: connected state, idle state, or inactive state. Optionally, step S2101 and / or step S2106 can be performed when the first terminal 101 is in any of the following states: connected state, idle state, or inactive state.

[0194] Step S2107 , the network device 103 sends fourth information to the first terminal 101 .

[0195] In some embodiments, the fourth information is used to indicate a third SL DRX configuration and a terminal identifier. Optionally, the third SL DRX configuration corresponds to the terminal identifier.

[0196] Optionally, the terminal identifier can uniquely identify the terminal. For example, the first terminal 101 is connected to multiple terminals via a sidelink, and the first terminal 101 can determine which terminal among the multiple terminals the terminal corresponding to the terminal identifier is based on the terminal identifier.

[0197] In some embodiments, the fourth information may be used to indicate a terminal identifier corresponding to each terminal and one or more SL DRX configurations corresponding to each terminal identifier. Optionally, the multiple terminal identifiers include a terminal identifier corresponding to the first terminal 101, and the one or more SL DRX configurations corresponding to each terminal identifier include a third SL DRX configuration.

[0198] In some embodiments, the fourth information may be "SL DRX configuration indication information" or "network configuration information" or "network configuration indication" or "SL DRX configuration indication". The embodiment of the present disclosure does not limit the name of the fourth information.

[0199] In some embodiments, the third SL DRX configuration may include one or more SL DRX configurations. The present disclosure does not limit the number of the third SL DRX configurations. For example, the third SL DRX configuration may include five SL DRX configurations, of which three SL DRX configurations correspond to broadcast services and two configurations correspond to multicast services.

[0200] In some embodiments, the fourth information may also be used to indicate the first identifier. Optionally, the fourth information is used to indicate the third SL DRX configuration, the terminal identifier, and the first identifier. Optionally, the first identifier corresponds to the terminal identifier. Optionally, the first identifier may be used to indicate the service corresponding to each SL DRX configuration in the third SL DRX configuration. Optionally, the service includes at least one of the following: a unicast service, a broadcast service, and a multicast service. In step S2108, the first terminal 101 determines that the terminal identifier corresponds to the second terminal 102 and determines the first information.

[0201] In some embodiments, the first terminal 101 determines that the terminal identifier corresponds to the second terminal 102, and determines that the at least one set of SL DRX configurations indicated by the first information is a third SL DRX configuration.

[0202] In some embodiments, the first terminal 101 determines that the at least one SL DRX configuration indicated by the first information is the third SL DRX configuration when determining that the terminal identifier corresponds to the second terminal 102. Optionally, in response to the terminal identifier corresponding to the second terminal 102, the first terminal 101 determines that the at least one SL DRX configuration indicated by the first information is the third SL DRX configuration.

[0203] In some embodiments, the fourth information may be used to indicate multiple terminal identifiers and one or more SL DRX configurations corresponding to the multiple terminal identifiers. Optionally, the first terminal 101 may determine the terminal identifier corresponding to the second terminal 102 among the multiple terminal identifiers, and further, based on the terminal identifier corresponding to the second terminal 102, determine that the one or more SL DRX configurations corresponding to the terminal identifier are at least one SL DRX configuration indicated by the first information.

[0204] Optionally, the first terminal 101 may further send corresponding SL DRX configurations to the multiple terminals respectively based on the multiple terminal identifiers. For example, the fourth information may also be used to indicate the terminal identifier corresponding to the third terminal and one or more sets of SL DRX configurations corresponding to the terminal identifier. The first terminal 101 may then determine that the terminal identifier corresponds to the third terminal, and determine the information to be sent to the third terminal, where the information is used to indicate one or more sets of SL DRX configurations corresponding to the terminal identifier corresponding to the third terminal.

[0205] In some embodiments, the first identifier indicated by the fourth information may be used to indicate the service corresponding to each set of SL DRX configuration indicated by the first information.

[0206] In some embodiments, step S2107 and / or step S2108 are applicable to the first terminal 101 in a connected state. Optionally, the first terminal 101 is in a connected state. Optionally, step S2107 and / or step S2108 can be performed when the first terminal 101 is in a connected state.

[0207] Step S2109 : The first terminal 101 sends first information to the second terminal 102 .

[0208] In some embodiments, the first information may be determined based on step S2106. In some embodiments, the first information may be determined based on step S2108. Alternatively, the first information may be determined by the first terminal 101 itself, or indicated by upper layer signaling, or pre-agreed based on a protocol. This disclosure is not limited to this.

[0209] In some embodiments, the first information may be "SL DRX configuration indication information" or "SL DRX configuration information" or "sidelink DRX assistance information". The embodiment of the present disclosure does not limit the name of the first information.

[0210] In some embodiments, the first information may include a SL DRX configuration sequence, the sequence including multiple SL DRX configuration identifiers, each SL DRX configuration identifier being used to indicate a set of SL DRX configurations. Optionally, the SL DRX configuration may be a configuration in a DRX configuration list in a multicast or broadcast configuration message. Optionally, the SL DRX configuration identifier is used to indicate a corresponding configuration in the DRX configuration list.

[0211] In some embodiments, the first information is used to indicate at least one set of SL DRX configurations. Optionally, the at least one set of SL DRX configurations includes SL DRX configurations corresponding to different services. For example, the at least one set of SL DRX configurations may include SL DRX configurations corresponding to multicast services and SL DRX configurations corresponding to broadcast services. Optionally, the first information is used to instruct the first terminal 101 to determine the first activation time based on the at least one set of SL DRX configurations indicated by the first information.

[0212] Step S2110 : The first terminal 101 sends a first identifier to the second terminal 102 .

[0213] In some embodiments, the first identifier is used to indicate the service corresponding to each set of SL DRX configurations in at least one set of SL DRX configurations indicated by the first information. Optionally, the second terminal 102 can determine the service corresponding to each set of SL DRX configurations in at least one set of SL DRX configurations indicated by the first information based on the first identifier. Optionally, the service includes at least one of the following: unicast service, broadcast service, and multicast service. For example, if the first information indicates only one set of SL DRX configurations, the service corresponding to the SL DRX configuration may be any one of a unicast service, a broadcast service, and a multicast service, for example, a multicast service. If the first information indicates multiple sets of SL DRX configurations, the services corresponding to the multiple sets of SL DRX configurations may be one or more of a unicast service, a broadcast service, and a multicast service, for example, multiple sets of SL DRX configurations may all correspond to broadcast services, or, a part of the multiple sets of SL DRX configurations may correspond to broadcast services, and another part may correspond to multicast services.

[0214] In some embodiments, the first identifier may be an identifier sequence, which includes multiple service indexes, each service index being used to indicate the service corresponding to the corresponding SL DRX configuration. For example, the first identifier is [3, 1, 2], where service index 1 can be used to indicate that the corresponding SL DRX configuration corresponds to a unicast service, service index 2 can be used to indicate that the corresponding SL DRX configuration corresponds to a multicast service, and service index 3 can be used to indicate that the corresponding SL DRX configuration corresponds to a broadcast service. If at least one set of SL DRX configurations indicated by the first information includes SL DRX configuration 1, SL DRX configuration 2, and SL DRX configuration 3 in sequence, the second terminal 102 can determine that SL DRX configuration 1 corresponds to a broadcast service, SL DRX configuration 2 corresponds to a unicast service, and SL DRX configuration 2 corresponds to a multicast service.

[0215] In some embodiments, the first identifier may be determined based on the first multicast or broadcast configuration message. Alternatively, the first identifier may be indicated by the network device 103 via the fourth information. Alternatively, the first identifier may be determined by the first terminal 101 itself, or indicated via upper layer signaling, or pre-agreed based on a protocol. This disclosure is not limited in this regard.

[0216] Step S2111: The second terminal 102 sends fifth information to the first terminal 101.

[0217] In some embodiments, the fifth information is used to indicate the first SL DRX configuration. Optionally, the fifth information may be used to indicate that the first SL DRX is rejected. Optionally, the fifth information may be used to indicate that the first SL DRX is rejected by the second terminal 102. Optionally, the first SL DRX configuration is the SL DRX configuration rejected by the second terminal 102 among the SL DRX configurations indicated by the first information. Optionally, the number of SL DRX configurations in the first SL DRX configuration may be one or more sets, which is not limited in the embodiments of the present disclosure.

[0218] In some embodiments, the fifth information may be a "rejection indication" or "rejection configuration information". The embodiment of the present disclosure does not limit the name of the fifth information.

[0219] In some embodiments, the second terminal 102 may reject all SL DRX configurations indicated by the first information. Optionally, the first SL DRX configuration includes all SL DRX configurations indicated by the first information. For example, the fifth information may be a bit, which may be used to indicate that the second terminal 102 rejects all SL DRX configurations indicated by the first information. Accordingly, if the first terminal 101 receives the fifth information, that is, the first terminal 101 receives the bit, it can be determined that the second terminal 102 rejects all SL DRX configurations indicated by the first information.

[0220] In some embodiments, the first terminal 101 may reject part of the SL DRX configuration indicated by the first information. Optionally, the first SL DRX configuration includes part of the SL DRX configuration indicated by the first information. Optionally, the fifth information may include multiple SL DRX configuration identifiers, each SL DRX configuration identifier is used to indicate a set of SL DRX configurations rejected by the second terminal 102. Optionally, the fifth information may include a SL DRX configuration sequence, which may include multiple SL DRX configuration identifiers, each SL DRX configuration identifier is used to indicate a set of SL DRX configurations rejected by the second terminal 102. Optionally, the SL DRX configuration identifier is used to indicate a corresponding configuration in the DRX configuration list.

[0221] In some embodiments, the first terminal 101 receives fifth information sent by the second terminal 102. Optionally, the first terminal 101 determines, based on the fifth information, the SL DRX configuration rejected by the second terminal 102 among the SL DRX configurations indicated by the first information.

[0222] Step S2112 : The first terminal 101 sends the fifth information and the terminal identifier to the network device 103 .

[0223] In some embodiments, the first terminal 101 determines that it is in a connected state and sends the fifth information and the terminal identifier to the network device 103. Optionally, when the first terminal 101 determines that it is in a connected state, it sends the fifth information and the terminal identifier to the network device 103. Optionally, the terminal identifier is the terminal identifier corresponding to the second terminal 102. Optionally, the network device 103 may determine the SL DRX configuration rejected by the second terminal 102 based on the fifth information and the terminal identifier.

[0224] In some embodiments, the network device 103 receives the fifth information and the terminal identification sent by the first terminal 101. Optionally, the fifth information and the terminal identification are sent when the first terminal 101 determines that it is in a connected state.

[0225] Step S2113 : The second terminal 102 sends sixth information to the first terminal 101 .

[0226] In some embodiments, the sixth information is used to indicate a second SL DRX configuration. Optionally, the fifth information may be used to indicate that the second SL DRX is accepted. Optionally, the fifth information may be used to indicate that the first SL DRX is accepted by the second terminal 102. Optionally, the second SL DRX configuration is the SL DRX configuration accepted by the second terminal 102 among the SL DRX configurations indicated by the first information. Optionally, the number of SL DRX configurations in the second SL DRX configuration may be one or more sets, which is not limited in the present embodiment.

[0227] In some embodiments, the sixth information may be an "acceptance indication" or a "confirmation indication" or a "receive configuration information". The embodiment of the present disclosure does not limit the name of the sixth information.

[0228] In some embodiments, the first terminal 101 may accept all SL DRX configurations indicated by the first information. Optionally, the second SL DRX configuration includes all SL DRX configurations indicated by the first information. For example, the sixth information may be a bit, which may be used to indicate that the second terminal 102 accepts all SL DRX configurations indicated by the first information. Accordingly, if the first terminal 101 receives the fifth information, that is, the first terminal 101 receives the bit, it can be determined that the second terminal 102 accepts all SL DRX configurations indicated by the first information.

[0229] In some embodiments, the first terminal 101 may reject part of the SL DRX configuration indicated by the first information. Optionally, the second SL DRX configuration includes part of the SL DRX configuration indicated by the first information. Optionally, the first terminal 101 only accepts one set of SL DRX configurations corresponding to the same service. For example, if the SL DRX configuration indicated by the first information includes 5 sets of SL DRX configurations, of which 3 sets of SL DRX configurations correspond to broadcast services and 2 sets of configurations correspond to multicast services, the first terminal 101 may only accept one set of SL DRX configurations corresponding to the broadcast service and / or one set of SL DRX configurations corresponding to the multicast service.

[0230] In some embodiments, the sixth information may include multiple SL DRX configuration identifiers, each of which is used to indicate a set of SL DRX configurations accepted by the second terminal 102. The sixth information may include an SL DRX configuration sequence, which may include multiple SL DRX configuration identifiers, each of which is used to indicate a set of SL DRX configurations accepted by the second terminal 102. Optionally, the SL DRX configuration identifier is used to indicate a corresponding configuration in a DRX configuration list.

[0231] In some embodiments, the fifth information in step S2111 and the sixth information in step S2113 may be the same bit. When the bit has different values, the bit may be the fifth information or the sixth information. For example, when the value of the bit is 0, the bit may be the fifth information. In this case, the bit may be used to indicate that the second terminal 102 rejects all SL DRX configurations indicated by the first information, that is, the first SL DRX configuration includes all SL DRX configurations indicated by the first information; when the value of the bit is 1, the bit may be the sixth information. In this case, the bit may be used to indicate that the second terminal 102 accepts all SL DRX configurations indicated by the first information, that is, the second SL DRX configuration includes all SL DRX configurations indicated by the first information.

[0232] In some embodiments, the first terminal 101 receives sixth information sent by the second terminal 102. Optionally, the first terminal 101 determines, based on the sixth information, the SL DRX configuration accepted by the second terminal 102 among the SL DRX configurations indicated by the first information.

[0233] Step S2114 : The first terminal 101 sends the sixth information and the terminal identifier to the network device 103 .

[0234] In some embodiments, the first terminal 101 determines that it is in a connected state and sends the sixth information and the terminal identifier to the network device 103. Optionally, when the first terminal 101 determines that it is in a connected state, it sends the sixth information and the terminal identifier to the network device 103. Optionally, the terminal identifier is the terminal identifier corresponding to the second terminal 102. Optionally, the network device 103 may determine the SL DRX configuration accepted by the second terminal 102 based on the sixth information and the terminal identifier.

[0235] In some embodiments, the network device 103 receives the sixth information and the terminal identification sent by the first terminal 101. Optionally, the sixth information and the terminal identification are sent when the first terminal 101 determines that it is in a connected state.

[0236] Step S2115: The second terminal 102 determines a first activation time.

[0237] In some embodiments, the first activation time is used for the second terminal 102 to monitor the sidelink. Alternatively, the first activation time is used for the second terminal 102 to monitor sidelink transmissions. Alternatively, the first activation time is used for the second terminal 102 to monitor information sent on the sidelink.

[0238] In some embodiments, the second terminal 102 determines the first activation time according to at least one set of SL DRX configurations indicated by the first information.

[0239] In some embodiments, the second terminal 102 determines the first activation time according to the second SL DRX configuration in the first information. Optionally, the first activation time is determined using the second SL DRX configuration.

[0240] In some embodiments, the second terminal 102 does not determine the first activation time according to the first SL DRX configuration in the first information. Optionally, the first activation time is determined without using the first SL DRX configuration.

[0241] In some embodiments, the SL DRX configuration indicated by the first information, excluding the first SL DRX configuration, may be the second SL DRX configuration. Optionally, the SL DRX configuration indicated by the first information, excluding the first SL DRX configuration, may not be the second SL DRX configuration. This is not limited in the embodiments of the present disclosure.

[0242] In some embodiments, the first activation time may include multiple activation times corresponding to different services. For example, the first activation time may include one or more of an activation time corresponding to a unicast service, an activation time corresponding to a multicast service, and an activation time corresponding to a broadcast service.

[0243] Optionally, the activation time included in the first activation time may be determined based on the SL DRX configuration received by the second terminal 102. For example, if the second terminal 102 receives a set of SL DRX configurations corresponding to the broadcast service and a set of SL DRX configurations corresponding to the multicast service, the first activation time may include the activation time determined based on the SL DRX configuration corresponding to the broadcast service and the activation time determined based on the SL DRX configuration corresponding to the multicast service.

[0244] In some embodiments, the first terminal 101 may also determine a first activation time. Optionally, the first activation time may be used for sidelink transmission by the first terminal 101. For example, the first terminal 101 may send information to the second terminal 102 only during the first activation time.

[0245] In some embodiments, the optional implementation of the first terminal 101 determining the first activation time can refer to the optional implementation of the second terminal 102 determining the first activation time described above, which will not be repeated here.

[0246] Step S2116: The second terminal 102 monitors the sidelink according to the first activation time.

[0247] In some embodiments, the second terminal 102 monitors the physical sidelink control channel PSCCH or the physical sidelink control channel PSSCH according to the first activation time. Optionally, the first activation time instructs the second terminal 102 to monitor the physical sidelink control channel PSCCH or the physical sidelink control channel PSSCH.

[0248] In some embodiments, the first terminal 101 performs a sidelink transmission according to the first activation time. Optionally, the first terminal 101 performs a sidelink transmission to the second terminal 102 according to the first activation time. Optionally, the first terminal 101 sends Sidelink Control Information (SCI) to the second terminal 102 on the PSCCH according to the first activation time, or sends second-stage SCI to the second terminal 102 on the PSSCH according to the first activation time.

[0249] In some embodiments, the second terminal 102 may be in an active state during the first activation time. Alternatively, the second terminal 102 may be in a sleep state outside the first activation time.

[0250] In some embodiments, the second terminal 102 may monitor its sidelink transmissions based on multiple activation times corresponding to different services. Alternatively, the second terminal 102 may monitor its sidelink broadcast transmissions based on the activation time of a corresponding broadcast service. Alternatively, the second terminal 102 may monitor its sidelink unicast transmissions based on the activation time of a corresponding unicast service. Alternatively, the second terminal 102 may monitor its sidelink multicast transmissions based on the activation time of a corresponding multicast service.

[0251] In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codeword", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0252] In some embodiments, terms such as "uplink", "uplink", "physical uplink" can be interchangeable with each other, and terms such as "downlink", "downlink", "physical downlink" can be interchangeable with each other, and terms such as "side", "sidelink", "side communication", "sidelink communication", "direct connection", "direct link", "direct communication", "direct link communication" can be interchangeable with each other.

[0253] In some embodiments, the terms "downlink control information (DCI)", "downlink (DL) assignment", "DL DCI", "uplink (UL) grant", "UL DCI" and the like may be used interchangeably.

[0254] In some embodiments, terms such as "physical downlink shared channel (PDSCH)" and "DL data" can be used interchangeably, and terms such as "physical uplink shared channel (PUSCH)" and "UL data" can be used interchangeably.

[0255] In some embodiments, the terms "radio", "wireless", "radio access network (RAN)", "access network (AN)", "RAN-based" and the like may be used interchangeably.

[0256] In some embodiments, terms such as "moment", "time point", "time", and "time position" can be replaced with each other, and terms such as "duration", "period", "time window", "window", and "time" can be replaced with each other.

[0257] In some embodiments, terms such as "frame", "radio frame", "subframe", "slot", "sub-slot", "mini-slot", "symbol", "symbol", and "transmission time interval (TTI)" can be used interchangeably.

[0258] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

[0259] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0260] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "a certain", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, a certain A, any A, or first A, etc., but not limited to this.

[0261] In some embodiments, the determination or judgment can be performed 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.

[0262] In some embodiments, "not expecting to receive" can be interpreted as not receiving on time domain resources and / or frequency domain resources, or as not performing subsequent processing on the data after receiving it; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the recipient to respond to the content sent.

[0263] In some embodiments, step S2106 and step S2108 may be performed alternatively. For example, if the first terminal 101 receives the fourth information sent by the network device 103, step S2108 may be performed, otherwise step S2106 may be performed. This embodiment of the present disclosure is not limited to this.

[0264] The method involved in the embodiments of the present disclosure may include at least one of steps S2101 to S2116. For example, step S2109 can be implemented as an independent embodiment, step S2115 can be implemented as an independent embodiment, steps S2101 to S2106 can be implemented as an independent embodiment, steps S2107 to S2109 can be implemented as an independent embodiment, steps S2111 to S2112 can be implemented as an independent embodiment, and steps S2113 to S2114 can be implemented as an independent embodiment, but are not limited thereto.

[0265] In some embodiments, steps S2101 and S2102 may be executed in the same order or simultaneously, steps S2111 and S2113 may be executed in the same order or simultaneously, steps S2112 and S2114 may be executed in the same order or simultaneously, steps S2111 to S2112 and steps S2113 to S2114 may be executed in the same order or simultaneously, or one of them may be executed alternatively, and steps S2104 and S2106 may be executed in the same order or simultaneously. In some embodiments, steps S2101 to S2108 and steps S2110 to S2116 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0266] In some embodiments, steps S2101 to S2115 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0267] In some embodiments, step S2112 and step S2114 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0268] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 2 .

[0269] FIG3A is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG3A , the present disclosure embodiment relates to an information processing method, which is executed by the first terminal 101 and includes:

[0270] Step S3101, obtain third information.

[0271] The optional implementation of step S3101 can refer to the optional implementation of step S2101 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0272] In some embodiments, the first terminal 101 receives the third information sent by the network device 103, but is not limited thereto and may also receive the first information sent by other entities.

[0273] In some embodiments, the first terminal 101 obtains third information specified by the protocol.

[0274] In some embodiments, the first terminal 101 obtains the third information from an upper layer(s).

[0275] In some embodiments, the first terminal 101 performs processing to obtain the third information.

[0276] In some embodiments, step S3101 is omitted, and the first terminal 101 autonomously implements the function indicated by the third information, or the above function is default or by default.

[0277] Step S3102, obtaining second information.

[0278] The optional implementation of step S3102 can refer to the optional implementation of step S2102 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0279] In some embodiments, the first terminal 101 receives the second information sent by the network device 103, but is not limited thereto and may also receive the first information sent by other entities.

[0280] In some embodiments, the first terminal 101 obtains second information specified by the protocol.

[0281] In some embodiments, the first terminal 101 obtains the second information from an upper layer(s).

[0282] In some embodiments, the first terminal 101 performs processing to obtain the second information.

[0283] In some embodiments, step S3102 is omitted, and the first terminal 101 autonomously implements the function indicated by the second information, or the above function is default or by default.

[0284] Step S3103: Determine DRX configuration and / or G-RNTI.

[0285] The optional implementation of step S3103 can refer to the optional implementation of step S2103 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0286] Step S3104: Determine the second activation time.

[0287] The optional implementation of step S3104 can refer to the optional implementation of step S2104 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0288] Step S3105: monitor the PDCCH according to the second activation time.

[0289] The optional implementation of step S3105 can refer to the optional implementation of step S2105 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0290] Step S3106: Determine first information according to the multicast or broadcast configuration message.

[0291] The optional implementation of step S3106 can refer to the optional implementation of step S2106 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0292] Step S3107, sending the first information.

[0293] The optional implementation of step S3107 can refer to the optional implementation of step S2109 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0294] In some embodiments, the first terminal 101 sends the first information to the second terminal 102, but is not limited thereto. The first information may also be sent to other entities.

[0295] Step S3108: Send the first identifier.

[0296] The optional implementation of step S3108 can refer to the optional implementation of step S2110 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0297] In some embodiments, the first terminal 101 sends the first identifier to the second terminal 102, but is not limited thereto. The first identifier may also be sent to other entities.

[0298] Step S3109, obtain the fifth information.

[0299] The optional implementation of step S3109 can refer to the optional implementation of step S2111 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0300] In some embodiments, the first terminal 101 receives the fifth information sent by the network device 103, but is not limited thereto and may also receive the fifth information sent by other entities.

[0301] In some embodiments, the first terminal 101 obtains fifth information specified by the protocol.

[0302] In some embodiments, the first terminal 101 obtains the fifth information from an upper layer(s).

[0303] In some embodiments, the first terminal 101 performs processing to obtain the fifth information.

[0304] In some embodiments, step S3109 is omitted, and the first terminal 101 autonomously implements the function indicated by the fifth information, or the above function is default or by default.

[0305] Step S3110: Send the fifth information and the terminal identification.

[0306] The optional implementation of step S3110 can refer to the optional implementation of step S2112 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0307] In some embodiments, the first terminal 101 sends the fifth information and the terminal identification to the network device 103, but is not limited thereto. The fifth information and the terminal identification may also be sent to other entities.

[0308] Step S3111, obtain sixth information.

[0309] The optional implementation of step S3111 can refer to the optional implementation of step S2111 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0310] In some embodiments, the first terminal 101 receives the sixth information sent by the network device 103, but is not limited thereto and may also receive the fifth information sent by other entities.

[0311] In some embodiments, the first terminal 101 obtains fifth information specified by the protocol.

[0312] In some embodiments, the first terminal 101 obtains the sixth information from an upper layer(s).

[0313] In some embodiments, the first terminal 101 performs processing to obtain the fifth information.

[0314] In some embodiments, step S3111 is omitted, and the first terminal 101 autonomously implements the function indicated by the sixth information, or the above function is default or default.

[0315] Step S3112: Send the sixth information and the terminal identification.

[0316] The optional implementation of step S3112 can refer to the optional implementation of step S2114 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0317] In some embodiments, the first terminal 101 sends the fifth information and the terminal identification to the network device 103, but is not limited thereto. The fifth information and the terminal identification may also be sent to other entities.

[0318] Step S3113: Determine the first activation time.

[0319] The optional implementation of step S3113 can refer to the optional implementation of step S2115 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0320] In some embodiments, after determining the first activation time, the first terminal 101 may perform a sidelink transmission according to the first activation time. Optionally, the first terminal 101 may perform a sidelink transmission to the second terminal 102 according to the first activation time. Optionally, during the first activation time, the first terminal 101 may transmit data to the second terminal 102 via the PSCCH or PSSCH, such as SCI or second-stage SCI.

[0321] The method according to the embodiments of the present disclosure may include at least one of steps S3101 to S3113. For example, step S3107 may be implemented as an independent embodiment, step S3110 may be implemented as an independent embodiment, steps S3101 to S3105 may be implemented as an independent embodiment, and steps S3107 to S3113 may be implemented as an independent embodiment, but the present disclosure is not limited thereto.

[0322] In some embodiments, step S3109 and step S3111 can be exchanged in order or executed simultaneously or one of them can be executed alternatively, and step S3110 and step S3112 can be exchanged in order or executed simultaneously or one of them can be executed alternatively.

[0323] In some embodiments, steps S3101 to S3106 and steps S3108 to S3113 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0324] In some embodiments, steps S3101 to S3105 and steps S3106 to S3113 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0325] In some embodiments, step S3110 and step S3112 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0326] FIG3B is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG3B , the present disclosure embodiment relates to an information processing method, which is executed by the first terminal 101 and includes:

[0327] Step S3201, obtain the fourth information.

[0328] The optional implementation of step S3201 can refer to the optional implementation of step S2107 in Figure 2 and other related parts in the embodiments involved in Figures 2 and 3A, and will not be repeated here.

[0329] In some embodiments, the first terminal 101 receives the fourth information sent by the network device 103, but is not limited thereto and may also receive the fourth information sent by other entities.

[0330] In some embodiments, the first terminal 101 obtains fourth information specified by the protocol.

[0331] In some embodiments, the first terminal 101 obtains the fourth information from an upper layer(s).

[0332] In some embodiments, the first terminal 101 performs processing to obtain the fourth information.

[0333] In some embodiments, step S3201 is omitted, and the first terminal 101 autonomously implements the function indicated by the fourth information, or the above function is default or default.

[0334] Step S3202: Determine that the terminal identifier corresponds to the second terminal 102 and determine the first information.

[0335] The optional implementation of step S3202 can refer to the optional implementation of step S2108 in Figure 2 and other related parts in the embodiments involved in Figures 2 and 3A, and will not be repeated here.

[0336] Step S3203, sending the first information.

[0337] The optional implementation of step S3203 can refer to step S2109 of Figure 2, the optional implementation of step S3107 of Figure 3A, and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.

[0338] In some embodiments, the first terminal 101 sends the first information to the second terminal 102, but is not limited thereto. The first information may also be sent to other entities.

[0339] Step S3204: Send the first identifier.

[0340] The optional implementation of step S3204 can refer to step S2110 of Figure 2, the optional implementation of step S3108 of Figure 3A, and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.

[0341] In some embodiments, the first terminal 101 sends the first identifier to the second terminal 102, but is not limited thereto. The first identifier may also be sent to other entities.

[0342] Step S3205, obtain the fifth information.

[0343] The optional implementation of step S3204 can refer to step S2111 in Figure 2, the optional implementation of step S3109 in Figure 3A, and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.

[0344] Step S3206: Send the fifth information and the terminal identification.

[0345] The optional implementation of step S3206 can refer to step S2112 of Figure 2, the optional implementation of step S3110 of Figure 3A, and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.

[0346] Step S3207, obtain sixth information.

[0347] The optional implementation of step S3207 can refer to step S2113 of Figure 2, the optional implementation of step S3111 of Figure 3A, and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.

[0348] Step S3208: Send the sixth information and the terminal identification.

[0349] The optional implementation of step S3208 can be found in step S2114 of FIG. 2 , the optional implementation of step S3112 of FIG. 3A , and other related parts in the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0350] Step S3209: determine the first activation time.

[0351] The optional implementation of step S3209 can refer to step S2115 of Figure 2, the optional implementation of step S3113 of Figure 3A, and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.

[0352] The method according to the embodiments of the present disclosure may include at least one of steps S3201 to S3209. For example, step S3203 may be implemented as an independent embodiment, step S3203 and step S3204 may be implemented as independent embodiments, steps S3201 to S3203 may be implemented as independent embodiments, and steps S3205 to S3209 may be implemented as independent embodiments, but the present invention is not limited thereto.

[0353] In some embodiments, step S3205 and step S3206 may be executed in an interchanged order or simultaneously or one of them may be executed alternatively.

[0354] In some embodiments, steps S3201 to S3202 and steps S3204 to S3209 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0355] In some embodiments, steps S3102 to S3209 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0356] In some embodiments, step S3206 and step S32208 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0357] In the embodiment of the present disclosure, step S3201 and step S3202 may be combined with step S3107 to step S3113 in FIG. 3A , but is not limited thereto.

[0358] FIG3C is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG3C , the present disclosure embodiment relates to an information processing method, which is executed by the first terminal 101 and includes:

[0359] Step S3301, determine the first information.

[0360] The optional implementation of step S3301 can be found in steps S2101 and S2106, as well as steps S2107 and S2108 in Figure 2, steps S3101 and S3106 in Figure 3A, the optional implementation of steps S3201 and S3202 in Figure 3B, and other related parts in the embodiments involved in Figures 2, 3A, and 3B, which will not be repeated here.

[0361] Step S3302, sending the first information.

[0362] The optional implementation of step S3301 can be found in step S2109 of Figure 2, step S3107 of Figure 3A, the optional implementation of step S3203 of Figure 3B, and other related parts in the embodiments involved in Figures 2, 3A, and 3B, which will not be repeated here.

[0363] Step S3303: Determine the first activation time.

[0364] The optional implementation of step S3303 can be found in step S2115 of Figure 2, step S3113 of Figure 3A, the optional implementation of step S3209 of Figure 3B, and other related parts in the embodiments involved in Figures 2, 3A, and 3B, which will not be repeated here.

[0365] The method involved in the embodiments of the present disclosure may include at least one of steps S3301 to S3303. For example, step S3301 can be implemented as an independent embodiment, step S3303 can be implemented as an independent embodiment, steps S3301 to S3302 can be implemented as an independent embodiment, and steps S3302 to S3303 can be implemented as an independent embodiment, but are not limited thereto.

[0366] In some embodiments, step S3301 and step S3303 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0367] In the embodiment of the present disclosure, step S3301 may be combined with steps S3107 to S3113 in FIG. 3A , and step S3301 may be combined with steps S3203 to S3209 in FIG. 3B , but is not limited thereto.

[0368] FIG3D is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG3D , the present disclosure embodiment relates to an information processing method, which is executed by the first terminal 101 and includes:

[0369] Step S3401, sending the first information.

[0370] The optional implementation of step S3401 can be found in step S2109 of Figure 2, step S3107 of Figure 3A, step S3203 of Figure 3B, the optional implementation of step S3302 of Figure 3C, and other related parts in the embodiments involved in Figures 2, 3A, 3B, and 3C, which will not be repeated here.

[0371] In some embodiments, the first information is used to indicate at least one set of sidelink discontinuous reception SL DRX configuration, and the at least one set of SL DRX configuration is used for the second terminal 102 to determine a first activation time, and the first activation time is used for the second terminal 102 to monitor the sidelink.

[0372] In some embodiments, the first activation time is used for the second terminal 102 to monitor at least one of the following: a physical sidelink control channel PSCCH; a physical sidelink shared channel PSSCH.

[0373] In some embodiments, the method further comprises:

[0374] A first identifier is sent to the second terminal 102, where the first identifier is used to indicate the service corresponding to each of the at least one SL DRX configurations indicated by the first information, where the service includes at least one of the following: unicast service, broadcast service, and multicast service.

[0375] In some embodiments, the method comprises:

[0376] receiving third information sent by the network device 103, where the third information is used to indicate a multicast or broadcast configuration message;

[0377] receiving second information sent by the second terminal 102, where the second information is used to indicate a first multicast or broadcast service required by the second terminal 102;

[0378] Determine a DRX configuration and / or a group radio network temporary identifier G-RNTI corresponding to the first multicast or broadcast service in the multicast or broadcast configuration message;

[0379] A second activation time is determined according to the DRX configuration and / or the G-RNTI, where the second activation time is used for the first terminal 101 to monitor the PDCCH corresponding to the G-RNTI sent by the network device 103 .

[0380] In some embodiments, the method comprises:

[0381] receiving third information sent by the network device 103, where the third information is used to indicate a multicast or broadcast configuration message;

[0382] At least one set of SL DRX configurations indicated by the first information is determined according to the multicast or broadcast configuration message.

[0383] In some embodiments, the first terminal 101 is in any of the following states: connected state, idle state, and inactive state.

[0384] In some embodiments, before the first terminal 101 sends the first information to the second terminal 102, the method includes:

[0385] receiving fourth information sent by the network device 103, where the fourth information is used to indicate a third SL DRX configuration and a terminal identifier, where the third SL DRX configuration corresponds to the terminal identifier;

[0386] It is determined that the terminal identifier corresponds to the second terminal 102, and it is determined that the at least one set of SL DRX configuration indicated by the first information is a third SL DRX configuration.

[0387] In some embodiments, the first terminal 101 is in a connected state.

[0388] In some embodiments, the method comprises:

[0389] Fifth information sent by the second terminal 102 is received, where the fifth information is used to indicate a first SL DRX configuration, where the first SL DRX configuration is a SL DRX configuration rejected by the second terminal 102 among the SL DRX configurations indicated by the first information.

[0390] In some embodiments, the first activation time is determined without using the first SL DRX configuration.

[0391] In some embodiments, the method comprises:

[0392] It is determined that the first terminal 101 is in a connected state, and the fifth information and the terminal identifier corresponding to the second terminal 102 are sent to the network device 103.

[0393] In some embodiments, the method comprises:

[0394] The sixth information sent by the second terminal 102 is received, where the fifth information is used to indicate a second SL DRX configuration, and the second SL DRX configuration is the SL DRX configuration accepted by the second terminal 102 among the SL DRX configurations indicated by the first information.

[0395] In some embodiments, the first activation time is determined using the second SL DRX configuration.

[0396] In some embodiments, the method comprises:

[0397] It is determined that the first terminal 101 is in a connected state, and the sixth information and the terminal identifier corresponding to the second terminal 102 are sent to the network device 103.

[0398] FIG4A is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG4A , the present disclosure embodiment relates to an information processing method, which is executed by the second terminal 102 and includes:

[0399] Step S4101, sending the second information.

[0400] The optional implementation of step S4101 can refer to the optional implementation of step S2102 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0401] In some embodiments, the second terminal 102 sends the second information to the first terminal 101, but is not limited thereto and the second information may also be sent to other entities.

[0402] Optionally, the second information is used to indicate a first multicast or broadcast service required by the second terminal 102. Optionally, the second information is used by the first terminal 101 to determine the DRX configuration and / or the G-RNTI. For optional implementations, see the optional implementations of step S2103 in FIG. 2 and other related portions of the embodiment involved in FIG. 2 , and will not be further described here.

[0403] Step S4102, obtaining first information.

[0404] The optional implementation of step S4102 can refer to the optional implementation of step S2109 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0405] In some embodiments, the second terminal 102 receives the first information sent by the first terminal 101, but is not limited thereto and may also receive the first information sent by other entities.

[0406] In some embodiments, the second terminal 102 obtains first information specified by a protocol.

[0407] In some embodiments, the second terminal 102 obtains the first information from an upper layer(s).

[0408] In some embodiments, the second terminal 102 performs processing to obtain the second information.

[0409] In some embodiments, step S4102 is omitted, and the second terminal 102 autonomously implements the function indicated by the first information, or the above function is default or by default.

[0410] Step S4103: Obtain the first identifier.

[0411] The optional implementation of step S4103 can refer to the optional implementation of step S2110 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0412] In some embodiments, the second terminal 102 receives the first identifier sent by the first terminal 101, but is not limited thereto and may also receive the first identifier sent by other entities.

[0413] In some embodiments, the second terminal 102 obtains a first identifier specified by a protocol.

[0414] In some embodiments, the second terminal 102 obtains the first identifier from an upper layer(s).

[0415] In some embodiments, the second terminal 102 performs processing to obtain the first identifier.

[0416] In some embodiments, step S4102 is omitted, and the second terminal 102 autonomously implements the function indicated by the first identifier, or the above function is default or by default.

[0417] Step S4104, sending the fifth information.

[0418] The optional implementation of step S4104 can refer to the optional implementation of step S2111 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0419] In some embodiments, the second terminal 102 sends the fifth information to the first terminal 101, but is not limited thereto. The fifth information may also be sent to other entities.

[0420] Optionally, the fifth information is used by the first terminal 101 to determine the SL DRX configuration rejected by the second terminal 102. Optionally, the fifth information is used to instruct the first terminal 101 to send the fifth information and the terminal identifier to the network device 103. Optionally, the terminal identifier is the terminal identifier of the second terminal 102. For optional implementation methods, please refer to the optional implementation methods of step S2112 of Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0421] Step S4105, sending the sixth information.

[0422] The optional implementation of step S4104 can refer to the optional implementation of step S2113 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0423] In some embodiments, the second terminal 102 sends the sixth information to the first terminal 101, but is not limited thereto. The sixth information may also be sent to other entities.

[0424] Optionally, the fifth information is used by the first terminal 101 to determine the SL DRX configuration accepted by the second terminal 102. Optionally, the fifth information is used to instruct the first terminal 101 to send the sixth information and the terminal identifier to the network device 103. Optionally, the terminal identifier is the terminal identifier of the second terminal 102. For optional implementation methods, please refer to the optional implementation methods of step S2114 in Figure 2 and other related parts of the embodiment involved in Figure 2, and will not be repeated here.

[0425] Step S4106: Determine the first activation time.

[0426] The optional implementation of step S4106 can refer to the optional implementation of step S2115 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0427] Step S4107: monitor the sidelink according to the first activation time.

[0428] The optional implementation of step S4107 can refer to the optional implementation of step S2116 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0429] The method involved in the embodiments of the present disclosure may include at least one of steps S4101 to S4107. For example, step S4102 can be implemented as an independent embodiment, step S4101 can be implemented as an independent embodiment, steps S4101 to S4102 can be implemented as independent embodiments, step S4102, step S4104, and step S4107 can be implemented as independent embodiments, and step S4102, step S4105, and step S4107 can be implemented as independent embodiments, but the present invention is not limited thereto.

[0430] In some embodiments, step S4104 and step S4105 may be executed in an interchanged order or simultaneously or one of them may be executed alternatively.

[0431] In some embodiments, step S4101 and steps S4103 to S4106 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0432] In some embodiments, steps S4101 to S4105 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0433] FIG4B is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG4B , the present disclosure embodiment relates to an information processing method, which is executed by the second terminal 102 and includes:

[0434] Step S4201, obtain first information.

[0435] The optional implementation of step S4201 can refer to step S2109 in Figure 2, the optional implementation of step S4102 in Figure 4A, and other related parts in the embodiments involved in Figures 2 and 4A, which will not be repeated here.

[0436] Step S4202: Determine the first activation time.

[0437] The optional implementation of step S4202 can refer to step S2115 of Figure 2, the optional implementation of step S4106 of Figure 4A, and other related parts in the embodiments involved in Figures 2 and 4A, which will not be repeated here.

[0438] Step S4203: monitor the sidelink according to the first activation time.

[0439] The optional implementation of step S4203 can refer to step S2116 of Figure 2, the optional implementation of step S4107 of Figure 4A, and other related parts in the embodiments involved in Figures 2 and 4A, which will not be repeated here.

[0440] In some embodiments, the first activation time is used for the second terminal 102 to monitor at least one of the following: a physical sidelink control channel PSCCH; a physical sidelink shared channel PSSCH.

[0441] In some embodiments, the method further comprises:

[0442] Receive a first identifier sent by the first terminal 101, where the first identifier is used to indicate the service corresponding to each set of SL DRX configurations in at least one set of SL DRX configurations indicated by the first information, where the service includes at least one of the following: unicast service, broadcast service, and multicast service.

[0443] In some embodiments, the method comprises:

[0444] Sending second information to the first terminal 101, where the second information is used to indicate a first multicast or broadcast service corresponding to the second terminal 102;

[0445] The first multicast or broadcast service is used by the first terminal 101 to determine the DRX configuration and / or group radio network temporary identifier G-RNTI corresponding to the first multicast or broadcast service in the multicast or broadcast configuration message, where the multicast or broadcast configuration message is indicated by the network device 103 through third information;

[0446] The DRX configuration and / or G-RNTI is used by the first terminal 101 to determine a second activation time, and the second activation time is used by the first terminal 101 to monitor the PDCCH corresponding to the G-RNTI sent by the network device 103 .

[0447] In some embodiments, the at least one set of SL DRX configurations indicated by the first information is determined by the first terminal 101 according to a multicast or broadcast configuration message, and the multicast or broadcast configuration message is indicated by the network device 103 through the third information.

[0448] In some embodiments, the first terminal 101 is in any of the following states: connected state, idle state, and inactive state.

[0449] In some embodiments, at least one set of SL DRX configuration indicated by the first information is a third SL DRX configuration, the first information is determined when the first terminal 101 determines that the terminal identifier corresponds to the second terminal 102, and the terminal identifier and the third SL DRX configuration are indicated to the first terminal 101 by the network device 103 through the fourth information or the third information.

[0450] In some embodiments, the first terminal 101 is in a connected state.

[0451] In some embodiments, the method comprises:

[0452] Fifth information is sent to the first terminal 101, where the fifth information is used to indicate a first SL DRX configuration, where the first SL DRX configuration is the SL DRX configuration rejected by the second terminal 102 among the SL DRX configurations indicated by the first information.

[0453] In some embodiments, the first activation time is determined without using the first SL DRX configuration.

[0454] In some embodiments, the method comprises:

[0455] The sixth information sent to the first terminal 101 is used to indicate a second SL DRX configuration. The second SL DRX configuration is a SL DRX configuration accepted by the second terminal 102 among the SL DRX configurations indicated by the first information.

[0456] In some embodiments, the first activation time is determined using the second SL DRX configuration.

[0457] The method involved in the embodiments of the present disclosure may include at least one of steps S4201 to S4203. For example, step S4201 may be implemented as an independent embodiment, step S4203 may be implemented as an independent embodiment, steps S4201 to S4202 may be implemented as independent embodiments, and steps S4202 and S4103 may be implemented as independent embodiments, but are not limited thereto.

[0458] In some embodiments, step S4201 and step S4202 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0459] In some embodiments, steps S4202 to S4203 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0460] FIG5A is an interactive diagram of an information processing method according to an embodiment of the present disclosure. As shown in FIG5A , the present disclosure embodiment relates to an information processing method for a communication system 100, the method comprising:

[0461] Step S5101: The first terminal 101 sends first information to the second terminal 102.

[0462] For the optional implementation of step S5101, please refer to step S2109 of Figure 2, step S3107 of Figure 3A, step S3203 of Figure 3B, step S3302 of Figure 3C, step S3401 of Figure 3D, step S4102 of Figure 4A, optional implementation of step S4201 of Figure 4B, and other related parts in the embodiments involved in Figures 2, 3A, 3B, 3C, 3D, 4A, and 4B, which will not be repeated here.

[0463] Step S5102: The second terminal 102 determines a first activation time.

[0464] The optional implementation of step S5102 can be found in step S2115 of Figure 2, step S4106 of Figure 4A, the optional implementation of step S4202 of Figure 4B, and other related parts in the embodiments involved in Figures 2, 3A, 3B, 3C, 3D, 4A, and 4B, which will not be repeated here.

[0465] Step S5103: The second terminal 102 monitors the sidelink according to the first activation time.

[0466] The optional implementation of step S5103 can be found in step S2116 of Figure 2, step S4107 of Figure 4A, the optional implementation of step S4203 of Figure 4B, and other related parts in the embodiments involved in Figures 2, 3A, 3B, 3C, 3D, 4A, and 4B, which will not be repeated here.

[0467] In some embodiments, the above method may include the method described in the above embodiments of the communication system side, the first terminal side, the second terminal side, etc., which will not be repeated here.

[0468] FIG6A is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG6A , the embodiment of the present disclosure relates to an information processing method for a remote UE, the method comprising:

[0469] Step S6101: Receive a sidelink discontinuous reception configuration sent by a relay UE, which may be one or more sets of configurations. Determine a sidelink activation time according to the SL DRX configuration, and monitor the sidelink transmission of the relay UE.

[0470] In some embodiments, monitoring the sidelink transmission includes monitoring the PSCCH or the PSSCH.

[0471] In some embodiments, the remote UE receives a first identifier indicating that each set of SL DRX configurations corresponds to a service.

[0472] In some embodiments, the service comprises a multicast or broadcast service.

[0473] In some embodiments, it is determined that the received SLDRX configuration is rejected, and a rejection indication is sent to the relay UE, which may carry the received SLDRX configuration identifier, indicating that the corresponding SLDRX configuration is rejected, and the rejected SLDRX configuration is not used to determine the sidelink activation time.

[0474] In some embodiments, the remote UE may reject one or more received SLDRX configurations.

[0475] In some embodiments, the remote UE may not carry the SL DRX configuration identifier, which indicates that all received SL DRX configurations are rejected.

[0476] In some embodiments, the remote UE determines to accept the received SL DRX configuration and sends an acknowledgment to the relay UE, which may carry the received SL DRX configuration identifier, indicating the accepted SL DRX configuration, and uses the accepted SL DRX configuration to determine the sidelink activation time.

[0477] In some embodiments, the remote UE may not carry the SL DRX configuration identifier, which means accepting all received SL DRX configurations.

[0478] FIG6B is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG6B , the embodiment of the present disclosure relates to an information processing method for relaying UE, the method comprising:

[0479] Step S6201: Send sidelink discontinuous reception configuration to the remote UE, which may be one or more sets of configurations.

[0480] In some embodiments, the relay UE sends a first identifier to the remote UE, indicating that each set of SL DRX configuration corresponds to a service.

[0481] In some embodiments, the relay UE receives a TMGI sent by a remote UE, determines a corresponding DRX configuration and / or G-RNTI in a multicast broadcast service broadcast configuration (MBSBroadcastConfiguration) message based on the TMGI, determines an activation time based on the DRX configuration, and monitors a PDCCH corresponding to the G-RNTI sent by the network.

[0482] In some embodiments, the relay UE receives an SLDRX configuration or SL DRX configuration and a first identifier, as well as a corresponding remote UE identifier, sent by a base station. The relay UE sends the received SL DRX configuration or SL DRX configuration and the first identifier to the corresponding remote UE. Optionally, this solution is applicable to a relay UE in a connected state.

[0483] In some embodiments, the relay UE determines the SL DRX configuration according to the corresponding DRX configuration in the multicast broadcast service broadcast configuration (MBSBroadcastConfiguration) message, or determines the SL DRX configuration and the first identifier. Optionally, the solution can be applied to the relay UE in a connected state, an idle state or an inactive state.

[0484] In some embodiments, the relay UE receives a rejection indication sent by the remote UE and does not use the rejected SL DRX configuration to determine the sidelink activation time of the remote UE.

[0485] In some embodiments, when the relay UE is in a connected state, a rejection indication and a remote UE identifier are reported to the base station.

[0486] In some embodiments, the relay UE receives a confirmation indication sent by the remote UE and uses the received SL DRX configuration to determine the sidelink activation time of the remote UE.

[0487] In some embodiments, when the relay UE is in a connected state, the confirmation indication and the remote UE identifier are reported to the base station.

[0488] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a network device 103 (e.g., an access network device, a core network function node, a core network device, etc.) in any of the above methods.

[0489] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0490] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit. The logical relationship of the above-mentioned 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 a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. 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), etc.

[0491] Figure 7A is a schematic diagram of the structure of a first terminal according to an embodiment of the present disclosure. As shown in Figure 7A, the first terminal 7100 may include at least one of a transceiver module 7101 and a processing module 7102. In some embodiments, the transceiver module 101 is configured to send first information to a second terminal, where the first information indicates at least one set of sidelink discontinuous reception (SL DRX) configurations, which are used by the second terminal to determine a first activation time, which is used by the second terminal to monitor the sidelink.

[0492] Optionally, the transceiver module 7101 is configured to execute at least one of the communication steps (e.g., step S2101, step S2102, step S2107, step S2109, step S2110, step S2111, step S2112, step S2113, and step S2114, but not limited thereto) performed by the first terminal in any of the above methods, which are not described in detail here. Optionally, the processing module 7102 is configured to execute at least one of the other steps (e.g., step S2103, step S2104, step S2106, step S2108, and step S2115, but not limited thereto) performed by the first terminal in any of the above methods, which are not described in detail here.

[0493] Figure 7B is a schematic diagram of the structure of an access network device proposed in an embodiment of the present disclosure. As shown in Figure 7B, the second terminal 7200 may include at least one of a transceiver module 7201, a processing module 7202, and a monitoring module 7203. In some embodiments, the transceiver module 7201 is configured to receive first information sent by the first terminal, where the first information indicates at least one set of sidelink discontinuous reception (SL DRX) configurations. The processing module 7202 is configured to determine a first activation time based on the at least one set of SL DRX configurations. The monitoring module 7203 is configured to monitor sidelink transmissions according to the first activation time.

[0494] Optionally, the transceiver module 7201 is used to execute at least one of the communication steps such as sending and / or receiving performed by the second terminal in any of the above methods (for example, step S2102, step S2109, step S2110, step S2111, step S2113, step S2112, but not limited thereto), which are not described in detail here. Optionally, the processing module 7202 is used to execute other steps (for example, step S2115, but not limited thereto) performed by the second terminal in any of the above methods, which are not described in detail here. Optionally, the monitoring module 7203 is used to execute other steps (for example, step S2116, but not limited thereto) performed by the second terminal in any of the above methods, which are not described in detail here.

[0495] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module. The transmitting module and the receiving module may be separate or integrated. Optionally, the transceiver module may be interchangeable with the transceiver. Optionally, the transceiver module may also be interchangeable with the monitoring module.

[0496] In some embodiments, the processing module can be a single module or can include multiple submodules. Optionally, the multiple submodules respectively execute all or part of the steps required to be executed by the processing module. Optionally, the processing module can be interchangeable with the processor.

[0497] Figure 8A is a schematic diagram of the structure of a communication device 8100 proposed in an embodiment of the present disclosure. Communication device 8100 can be a network device (e.g., an access network device, a core network device, etc.), a terminal (e.g., a user device, a first terminal, a second terminal, etc.), a chip, a chip system, or a processor that supports a network device to implement any of the above methods, or a chip, a chip system, or a processor that supports a terminal to implement any of the above methods. Communication device 8100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0498] As shown in Figure 8A, the communication device 8100 includes one or more processors 8101. The processor 8101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. The communication device 8100 is used to perform any of the above methods.

[0499] In some embodiments, the communication device 8100 further includes one or more memories 8102 for storing instructions. Optionally, all or part of the memories 8102 may be located outside the communication device 8100.

[0500] In some embodiments, the communication device 8100 further includes one or more transceivers 8103. When the communication device 8100 includes one or more transceivers 8103, the transceiver 8103 performs at least one of the communication steps (e.g., steps S2101, S2102, S2107, S2109, S2110, S2111, S2112, S2113, S2114, and S2116, but not limited thereto) in the above method, and the processor 8101 performs at least one of the other steps (e.g., steps S2103, S2104, S2106, S2108, and S2115, but not limited thereto). In some embodiments, the step of monitoring a link (e.g., a sidelink or a downlink) in the above method may be performed by the transceiver 8103 in cooperation with the processor 8101 (e.g., step S2116, but not limited thereto).

[0501] In some embodiments, a transceiver may include a receiver and / or a transmitter. The receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0502] In some embodiments, the communication device 8100 may include one or more interface circuits 8104. Optionally, the interface circuit 8104 is connected to the memory 8102. The interface circuit 8104 may be configured to receive signals from the memory 8102 or other devices, and may be configured to send signals to the memory 8102 or other devices. For example, the interface circuit 8104 may read instructions stored in the memory 8102 and send the instructions to the processor 8101.

[0503] The communication device 8100 described in the above embodiment may be a network device or a terminal, but the scope of the communication device 8100 described in the present disclosure is not limited thereto, and the structure of the communication device 8100 may not be limited by FIG. 8A. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data or programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0504] FIG8B is a schematic diagram of the structure of a chip 8200 according to an embodiment of the present disclosure. If the communication device 8100 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 8200 shown in FIG8B , but the present disclosure is not limited thereto.

[0505] The chip 8200 includes one or more processors 8201 , and the chip 8200 is configured to execute any of the above methods.

[0506] In some embodiments, the chip 8200 further includes one or more interface circuits 8202. Optionally, the interface circuit 8202 is connected to the memory 8203. The interface circuit 8202 can be used to receive signals from the memory 8203 or other devices, and can be used to send signals to the memory 8203 or other devices. For example, the interface circuit 8202 can read instructions stored in the memory 8203 and send the instructions to the processor 8201.

[0507] In some embodiments, the interface circuit 8202 executes at least one of the communication steps such as sending and / or receiving in the above method (for example, step S2101, step S2102, step S2107, step S2109, step S2110, step S2111, step S2112, step S2113, step S2114, step S2116, but not limited to these), and the processor 8201 executes at least one of the other steps (for example, step S2103, step S2104, step S2106, step S2108, step S2115, but not limited to these).

[0508] In some embodiments, terms such as interface circuit, interface, transceiver pin, and transceiver may be used interchangeably.

[0509] In some embodiments, the chip 8200 further includes one or more memories 8203 for storing instructions. Alternatively, all or part of the memories 8203 may be outside the chip 8200.

[0510] The present disclosure also proposes a storage medium having instructions stored thereon, which, when executed on the communication device 8100, causes the communication device 8100 to execute any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto, and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto, and may also be a temporary storage medium.

[0511] The present disclosure also provides a program product, which, when executed by the communication device 8100, enables the communication device 8100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0512] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

Claims

1. A sidelink monitoring method, characterized in that: The method comprises: The first terminal sends first information to the second terminal, where the first information is used to indicate at least one set of sidelink discontinuous reception SL DRX configuration, and the at least one set of SL DRX configuration is used by the second terminal to determine a first activation time, and the first activation time is used by the second terminal to monitor the sidelink.

2. The method according to claim 1, characterized in that The first activation time is used for the second terminal to monitor at least one of the following: a physical sidelink control channel PSCCH; a physical sidelink shared channel PSSCH.

3. The method according to claim 1 or 2, characterized in that: The method further comprises: A first identifier is sent to the second terminal, where the first identifier is used to indicate the service corresponding to each of the at least one set of SL DRX configurations, and the service includes at least one of the following: unicast service, broadcast service, and multicast service.

4. The method according to any one of claims 1 to 3, characterized in that: The method comprises: receiving third information sent by the network device, where the third information is used to indicate a multicast or broadcast configuration message; receiving second information sent by the second terminal, where the second information is used to indicate a first multicast or broadcast service required by the second terminal; Determine a DRX configuration and / or a group radio network temporary identifier G-RNTI corresponding to the first multicast or broadcast service in the multicast or broadcast configuration message; A second activation time is determined according to the DRX configuration and / or the G-RNTI, where the second activation time is used for the first terminal to monitor a physical downlink control channel PDCCH corresponding to the G-RNTI and sent by the network device.

5. The method according to any one of claims 1 to 4, characterized in that: The method comprises: receiving third information sent by the network device, where the third information is used to indicate a multicast or broadcast configuration message; The at least one set of SL DRX configuration is determined according to the multicast or broadcast configuration message.

6. The method according to claim 5, characterized in that The first terminal is in any of the following states: connected state, idle state, and inactive state.

7. The method according to any one of claims 1 to 4, characterized in that: Before the first terminal sends the first information to the second terminal, the method includes: receiving fourth information sent by the network device, where the fourth information is used to indicate a third SL DRX configuration and a terminal identifier, where the third SL DRX configuration corresponds to the terminal identifier; Determine that the terminal identifier corresponds to the second terminal, and determine that the at least one set of SL DRX configuration is the third SL DRX configuration.

8. The method according to claim 7, characterized in that The first terminal is in a connected state.

9. The method according to any one of claims 1 to 8, characterized in that: The method comprises: Receive fifth information sent by the second terminal, where the fifth information is used to indicate a first SL DRX configuration, and the first SL DRX configuration is a SL DRX configuration rejected by the second terminal among the SL DRX configurations indicated by the first information.

10. The method according to claim 9, characterized in that The method comprises: Determine that the first terminal is in a connected state, and send the fifth information and a terminal identifier corresponding to the second terminal to a network device.

11. The method according to any one of claims 1 to 10, comprising: Receive sixth information sent by the second terminal, where the fifth information is used to indicate a second SL DRX configuration, and the second SL DRX configuration is a SL DRX configuration accepted by the second terminal among the SL DRX configurations indicated by the first information.

12. The method according to claim 11, characterized in that The first activation time is determined using the second SL DRX configuration.

13. The method according to claim 11 or 12, characterized in that: The method comprises: Determine that the first terminal is in a connected state, and send the sixth information and a terminal identifier corresponding to the second terminal to a network device.

14. A sidelink monitoring method, characterized in that: The method comprises: The second terminal receives first information sent by the first terminal, where the first information is used to indicate at least one set of sidelink discontinuous reception (SL DRX) configuration; determining a first activation time according to the at least one set of SL DRX configurations; The sidelink is monitored according to the first activation time.

15. The method according to claim 14, characterized in that The first activation time is used for the second terminal to monitor at least one of the following: a physical sidelink control channel PSCCH; a physical sidelink shared channel PSSCH.

16. The method according to claim 14 or 15, characterized in that The method further comprises: Receive a first identifier sent by the first terminal, where the first identifier is used to indicate the service corresponding to each of the at least one set of SL DRX configurations, and the service includes at least one of the following: unicast service, broadcast service, and multicast service.

17. The method according to any one of claims 14 to 16, characterized in that: The method comprises: Sending second information to the first terminal, where the second information is used to indicate a first multicast or broadcast service corresponding to the second terminal; The first multicast or broadcast service is used by the first terminal to determine the DRX configuration and / or the group radio network temporary identifier G-RNTI corresponding to the first multicast or broadcast service in a multicast or broadcast configuration message, where the multicast or broadcast configuration message is indicated by a network device through third information; The DRX configuration and / or the G-RNTI are used by the first terminal to determine a second activation time, and the second activation time is used by the first terminal to monitor a physical downlink control channel PDCCH corresponding to the G-RNTI and sent by the network device.

18. The method according to any one of claims 14 to 16, characterized in that: The at least one set of SL DRX configuration is determined by the first terminal according to a multicast or broadcast configuration message, and the multicast or broadcast configuration message is indicated by the network device through third information.

19. The method according to claim 18, characterized in that The first terminal is in any of the following states: connected state, idle state, and inactive state.

20. The method according to any one of claims 14 to 16, characterized in that: The at least one set of SL DRX configuration is a third SL DRX configuration, the first information is determined when the first terminal determines that the terminal identifier corresponds to the second terminal, and the terminal identifier and the third SL DRX configuration are indicated to the first terminal by the network device through the fourth information or the third information.

21. The method according to claim 20, characterized in that The first terminal is in a connected state.

22. The method according to any one of claims 14 to 21, characterized in that: The method comprises: Fifth information is sent to the first terminal, where the fifth information is used to indicate a first SL DRX configuration, and the first SL DRX configuration is a SL DRX configuration rejected by the second terminal among the SL DRX configurations indicated by the first information.

23. The method according to any one of claims 14 to 22, comprising: The sixth information is sent to the first terminal, where the sixth information is used to indicate a second SL DRX configuration, and the second SL DRX configuration is a SL DRX configuration accepted by the second terminal among the SL DRX configurations indicated by the first information.

24. The method according to claim 23, characterized in that The first activation time is determined using the second SL DRX configuration.

25. A first terminal, characterized in that: The first terminal includes: The transceiver module is configured to send first information to the second terminal, wherein the first information is used to indicate at least one set of sidelink discontinuous reception SL DRX configuration, and the at least one set of SL DRX configuration is used by the second terminal to determine a first activation time, and the first activation time is used by the second terminal to monitor the sidelink.

26. A second terminal, characterized in that: The second terminal includes: A transceiver module is configured to receive first information sent by a first terminal, where the first information is used to indicate at least one set of sidelink discontinuous reception (SL DRX) configuration; a processing module configured to determine a first activation time according to the at least one set of SL DRX configurations; The monitoring module is configured to monitor the sidelink transmission according to the first activation time.

27. A first terminal, characterized in that: include: one or more processors; The first terminal is used to execute the sidelink monitoring method described in any one of claims 1-13.

28. A second terminal, characterized in that: include: one or more processors; The second terminal is used to execute the side link monitoring method described in any one of claims 14-24.

29. A communication system, characterized in that: It comprises a first terminal and a second terminal, wherein the first terminal is configured to implement the side link monitoring method described in any one of claims 1-13, and the second terminal is configured to implement the side link monitoring method described in any one of claims 14-24.

30. A storage medium storing instructions, characterized in that: When the instruction is executed on the communication device, the communication device executes the sidelink monitoring method as described in any one of claims 1-13 or 14-24.

Images