Information transmission method, terminal, network equipment and storage medium
Patent Information
- Application Number
- CN202480034744.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-03-27
- Publication Date
- 2026-01-02
Smart Images

Figure CN121264166A_ABST
Abstract
Description
Information transmission method, terminal, network device and storage medium Technical Field
[0001] The present disclosure relates to the field of communication technologies, and in particular to an information transmission method, terminal, network device, and storage medium. Background Art
[0002] For non-terrestrial networks (NTN), downlink coverage issues are more severe than for terrestrial networks (TN) due to the higher altitude of satellites. Therefore, research is needed to enhance downlink coverage. Random access message 4 (Msg4), as one of the downlink messages, also requires coverage enhancement in certain scenarios.
[0003] Summary of the Invention
[0004] The embodiments of the present disclosure provide an information transmission method, access network equipment, terminal, and storage medium, which to a certain extent solve the coverage problem in certain scenarios.
[0005] According to a first aspect of an embodiment of the present disclosure, a method for transmitting information is provided, the method being executed by a terminal, the method including:
[0006] Sending a message three Msg3 containing indication information to the network device, wherein the indication information is used to indicate whether the terminal supports the repetition capability of message four Msg4.
[0007] According to a second aspect of an embodiment of the present disclosure, a method for transmitting information is provided, the method being executed by a network device, the method comprising:
[0008] Receiving a message 3 (Msg3) sent by a terminal containing indication information, wherein the indication information is used to indicate whether the terminal supports a repetition capability of message 4 (Msg4);
[0009] The terminal supports Msg4 repetition and repeatedly sends Msg4 to the terminal.
[0010] According to a third aspect of an embodiment of the present disclosure, a method for transmitting information is provided. The method is performed by a communication system, the communication system including: a network device and a terminal. The method includes:
[0011] The terminal sends a message 3 (Msg3) containing indication information to the network device, wherein the indication information is used to indicate whether the terminal supports the repetition capability of message 4 (Msg4);
[0012] The terminal supports Msg4 repetition. The network device repeatedly sends Msg4 to the terminal.
[0013] According to a fourth aspect of an embodiment of the present disclosure, a terminal is provided, including:
[0014] The transceiver module is used to send a message three Msg3 containing indication information to the network device, wherein the indication information is used to indicate whether the terminal supports the repetition capability of message four Msg4.
[0015] According to a fifth aspect of an embodiment of the present disclosure, a network device is provided, including:
[0016] a transceiver module, configured to receive a message 3 Msg3 containing indication information sent by a terminal, wherein the indication information is used to indicate whether the terminal supports a repetition capability of a message 4 Msg4;
[0017] The terminal supports Msg4 repetition, and the transceiver module is further configured to repeatedly send Msg4 to the terminal.
[0018] According to a sixth aspect of an embodiment of the present disclosure, a terminal is provided, characterized by comprising:
[0019] one or more processors;
[0020] The terminal is used to execute the transmission control method according to any one of claims 1 to 7.
[0021] According to a seventh aspect of an embodiment of the present disclosure, a network device is provided, characterized in that it includes:
[0022] one or more processors;
[0023] The network device is used to execute the transmission control method according to any one of claims 8 to 14.
[0024] According to the eighth aspect of an embodiment of the present disclosure, a communication system is proposed, characterized in that it includes a network device and a terminal, wherein the network device is configured to implement the information transmission method described in the second aspect, and the terminal is configured to implement the information transmission method described in the first aspect.
[0025] According to the ninth 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 information transmission method described in any one of the first and second aspects. BRIEF DESCRIPTION OF THE DRAWINGS
[0026] 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.
[0027] FIG1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure;
[0028] 2A-2C are interactive schematic diagrams illustrating a method for transmitting information according to an embodiment of the present disclosure;
[0029] 3A-3B are flowcharts illustrating a method for transmitting information according to an embodiment of the present disclosure;
[0030] 4A-4B are schematic flow diagrams of a method for transmitting information according to an embodiment of the present disclosure;
[0031] FIG5 is an interactive schematic diagram of an information transmission method according to an embodiment of the present disclosure;
[0032] FIG6A is a schematic structural diagram of a terminal proposed in an embodiment of the present disclosure;
[0033] FIG6B is a schematic diagram of the structure of a network device proposed in an embodiment of the present disclosure;
[0034] FIG7A is a schematic structural diagram of a communication device proposed in an embodiment of the present disclosure;
[0035] FIG7B is a schematic diagram of the structure of the chip proposed in an embodiment of the present disclosure. DETAILED DESCRIPTION
[0036] The embodiments of the present disclosure provide an information transmission method, a terminal, a network device, and a storage medium.
[0037] In a first aspect, an embodiment of the present disclosure provides a method for transmitting information, the method being executed by a terminal, the method comprising:
[0038] Sending a message three Msg3 containing indication information to the network device, wherein the indication information is used to indicate whether the terminal supports the repetition capability of message four Msg4.
[0039] In the above embodiment, the terminal indicates to the network device via Msg3 whether the terminal supports the Msg4 repetition capability, thereby providing conditions and basis for the network device to repeatedly send Msg4 to the terminal, thereby enhancing the downlink transmission of the terminal and improving the downlink coverage performance of the terminal.
[0040] In combination with some embodiments of the first aspect, in some embodiments, the indication information is carried by the extended logical channel identifier LCID field in the MAC subheader of the media access control MAC service data unit SDU, wherein the MAC SDU contains uplink common control channel UL CCCH information.
[0041] In the above embodiment, the terminal does not need to extend Msg3, but reuses the LCID in Msg3 to indicate whether it supports the Msg4 repetition capability. The indication method is flexible and occupies fewer resources.
[0042] In conjunction with some embodiments of the first aspect, in some embodiments, the indication information is further used to indicate the type of the terminal
[0043] In the above embodiment, the terminal indicates to the network device through Msg3 whether the terminal supports the Msg4 repetition capability and the type of the terminal, so that the network device can repeatedly send Msg4 to the terminal according to the type and capability of the terminal to enhance the downlink transmission of the terminal and further improve the downlink coverage performance of the terminal.
[0044] In conjunction with some embodiments of the first aspect, in some embodiments, the type of the terminal includes any one of the following:
[0045] Capability restricted terminal RedCap UE, enhanced capability restricted terminal eRedCap UE, non-capability restricted terminal, non-enhanced capability restricted terminal, capability restricted non-terrestrial network terminal, enhanced capability restricted non-terrestrial network terminal, non-capability restricted non-terrestrial network terminal, non-enhanced capability restricted non-terrestrial network terminal, capability restricted terrestrial network terminal, enhanced capability restricted terrestrial network terminal, non-capability restricted terrestrial network terminal, non-enhanced capability restricted terrestrial network terminal.
[0046] In the above embodiment, various types of terminals can indicate to the network device whether they support the Msg4repetition capability as needed, thereby providing conditions for the network device to enhance downlink transmission for various types of terminals and further improving the downlink coverage performance of the terminals.
[0047] In combination with some embodiments of the first aspect, in some embodiments, the indication information is further used to indicate the size of the common control channel CCCH.
[0048] In the above embodiment, the terminal can jointly indicate multiple dimensional information through the indication information in Msg3, thereby providing a basis and conditions for the network device to increase downlink coverage for the terminal according to the multiple dimensional information.
[0049] In combination with some embodiments of the first aspect, in some embodiments, the size of the CCCH includes any one of the following: 48 bits, 64 bits.
[0050] In conjunction with some embodiments of the first aspect, in some embodiments, different indication information is used to indicate one or more of the following:
[0051] The CCCH size is 48 bits, the terminal is a non-eRedCap UE, and Msg4 repetition is supported;
[0052] The CCCH size is 64 bits, the terminal is a non-eRedCap UE, and Msg4 repetition is supported;
[0053] The CCCH size is 48 bits, the terminal is a RedCap UE, and Msg4 repetition is supported;
[0054] The CCCH size is 64 bits, the terminal is a RedCap UE, and Msg4 repetition is supported;
[0055] The CCCH size is 48 bits, the terminal is an eRedCap UE, and it supports Msg4 repetition;
[0056] The CCCH size is 64 bits, the terminal is an eRedCap UE, and Msg4 repetition is supported;
[0057] The CCCH size is 48 bits, the terminal is a RedCap UE or eRedCap UE, and supports Msg4 repetition;
[0058] The CCCH size is 64 bits, the terminal is a RedCap UE or eRedCap UE, and supports Msg4 repetition.
[0059] In a second aspect, an embodiment of the present disclosure provides a method for transmitting information, the method being performed by a network device, the method comprising:
[0060] Receiving a message 3 (Msg3) sent by a terminal containing indication information, wherein the indication information is used to indicate whether the terminal supports a repetition capability of message 4 (Msg4);
[0061] The terminal supports Msg4 repetition and repeatedly sends Msg4 to the terminal.
[0062] In combination with some embodiments of the second aspect, in some embodiments, the indication information is carried by the extended logical channel identifier LCID field in the MAC subheader of the media access control MAC service data unit SDU, wherein the MAC SDU contains uplink common control channel ULCCCH information.
[0063] In combination with some embodiments of the second aspect, in some embodiments, the indication information is also used to indicate the type of the terminal.
[0064] In conjunction with some embodiments of the second aspect, in some embodiments, the type of the terminal includes any one of the following:
[0065] Capability restricted terminal RedCap UE, enhanced capability restricted terminal eRedCap UE, non-capability restricted terminal, non-enhanced capability restricted terminal, capability restricted non-terrestrial network terminal, enhanced capability restricted non-terrestrial network terminal, non-capability restricted non-terrestrial network terminal, non-enhanced capability restricted non-terrestrial network terminal, capability restricted terrestrial network terminal, enhanced capability restricted terrestrial network terminal, non-capability restricted terrestrial network terminal, non-enhanced capability restricted terrestrial network terminal.
[0066] In combination with some embodiments of the second aspect, in some embodiments, the indication information is also used to indicate the size of a common control channel CCCH.
[0067] In combination with some embodiments of the second aspect, in some embodiments, the size of the CCCH includes any one of the following: 48 bits, 64 bits.
[0068] In conjunction with some embodiments of the second aspect, in some embodiments, different indication information is used to indicate one or more of the following:
[0069] The CCCH size is 48 bits, the terminal is a non-eRedCap UE, and Msg4 repetition is supported;
[0070] The CCCH size is 64 bits, the terminal is a non-eRedCap UE, and Msg4 repetition is supported;
[0071] The CCCH size is 48 bits, the terminal is a RedCap UE, and it supports Msg4 repetition;
[0072] The CCCH size is 64 bits, the terminal is a RedCap UE, and Msg4 repetition is supported;
[0073] The CCCH size is 48 bits, the terminal is an eRedCap UE, and Msg4 repetition is supported;
[0074] The CCCH size is 64 bits, the terminal is an eRedCap UE, and Msg4 repetition is supported;
[0075] The CCCH size is 48 bits, the terminal is a RedCap UE or eRedCap UE, and supports Msg4 repetition;
[0076] The CCCH size is 64 bits, the terminal is a RedCap UE or eRedCap UE, and supports Msg4 repetition.
[0077] In a third aspect, an embodiment of the present disclosure provides a method for transmitting information, the method being performed by a communication system comprising: a terminal and a network device, the method comprising:
[0078] The terminal sends a message 3 (Msg3) containing indication information to the network device, wherein the indication information is used to indicate whether the terminal supports the repetition capability of message 4 (Msg4);
[0079] The terminal supports Msg4 repetition. The network device repeatedly sends Msg4 to the terminal.
[0080] In a fourth aspect, an embodiment of the present disclosure provides a terminal, comprising:
[0081] The transceiver module is used to send a message three Msg3 containing indication information to the network device, wherein the indication information is used to indicate whether the terminal supports the repetition capability of message four Msg4.
[0082] In combination with some embodiments of the fourth aspect, in some embodiments, the indication information is carried by the extended logical channel identifier LCID field in the MAC subheader of the media access control MAC service data unit SDU, wherein the MAC SDU contains uplink common control channel UL CCCH information.
[0083] In combination with some embodiments of the fourth aspect, in some embodiments, the indication information is also used to indicate the type of the terminal.
[0084] In conjunction with some embodiments of the fourth aspect, in some embodiments, the type of the terminal includes any one of the following:
[0085] Capability restricted terminal RedCap UE, enhanced capability restricted terminal eRedCap UE, non-capability restricted terminal, non-enhanced capability restricted terminal, capability restricted non-terrestrial network terminal, enhanced capability restricted non-terrestrial network terminal, non-capability restricted non-terrestrial network terminal, non-enhanced capability restricted non-terrestrial network terminal, capability restricted terrestrial network terminal, enhanced capability restricted terrestrial network terminal, non-capability restricted terrestrial network terminal, non-enhanced capability restricted terrestrial network terminal.
[0086] In combination with some embodiments of the fourth aspect, in some embodiments, the indication information is also used to indicate the size of a common control channel CCCH.
[0087] In combination with some embodiments of the fourth aspect, in some embodiments, the size of the CCCH includes any one of the following: 48 bits, 64 bits.
[0088] In conjunction with some embodiments of the fourth aspect, in some embodiments, different indication information is used to indicate one or more of the following:
[0089] The CCCH size is 48 bits, the terminal is a non-eRedCap UE, and Msg4 repetition is supported;
[0090] The CCCH size is 64 bits, the terminal is a non-eRedCap UE, and Msg4 repetition is supported;
[0091] The CCCH size is 48 bits, the terminal is a RedCap UE, and Msg4 repetition is supported;
[0092] The CCCH size is 64 bits, the terminal is a RedCap UE, and Msg4 repetition is supported;
[0093] The CCCH size is 48 bits, the terminal is an eRedCap UE, and it supports Msg4 repetition;
[0094] The CCCH size is 64 bits, the terminal is an eRedCap UE, and Msg4 repetition is supported;
[0095] The CCCH size is 48 bits, the terminal is a RedCap UE or eRedCap UE, and supports Msg4 repetition;
[0096] The CCCH size is 64 bits, the terminal is a RedCap UE or eRedCap UE, and supports Msg4 repetition.
[0097] In a fifth aspect, an embodiment of the present disclosure provides a network device, comprising:
[0098] a transceiver module, configured to receive a message 3 Msg3 containing indication information sent by a terminal, wherein the indication information is used to indicate whether the terminal supports a repetition capability of a message 4 Msg4;
[0099] The terminal supports Msg4 repetition, and the transceiver module is further configured to repeatedly send Msg4 to the terminal.
[0100] In combination with some embodiments of the fifth aspect, in some embodiments, the indication information is carried by the extended logical channel identifier LCID field in the MAC subheader of the media access control MAC service data unit SDU, wherein the MAC SDU contains uplink common control channel ULCCCH information.
[0101] In combination with some embodiments of the fifth aspect, in some embodiments, the indication information is also used to indicate the type of the terminal.
[0102] With reference to some embodiments of the fifth aspect, in some embodiments, the type of the terminal includes any one of the following:
[0103] Capability restricted terminal RedCap UE, enhanced capability restricted terminal eRedCap UE, non-capability restricted terminal, non-enhanced capability restricted terminal, capability restricted non-terrestrial network terminal, enhanced capability restricted non-terrestrial network terminal, non-capability restricted non-terrestrial network terminal, non-enhanced capability restricted non-terrestrial network terminal, capability restricted terrestrial network terminal, enhanced capability restricted terrestrial network terminal, non-capability restricted terrestrial network terminal, non-enhanced capability restricted terrestrial network terminal.
[0104] In combination with some embodiments of the fifth aspect, in some embodiments, the indication information is also used to indicate the size of the common control channel CCCH.
[0105] In combination with some embodiments of the fifth aspect, in some embodiments, the size of the CCCH includes any one of the following: 48 bits, 64 bits.
[0106] In conjunction with some embodiments of the fifth aspect, in some embodiments, different indication information is used to indicate one or more of the following:
[0107] The CCCH size is 48 bits, the terminal is a non-eRedCap UE, and Msg4 repetition is supported;
[0108] The CCCH size is 64 bits, the terminal is a non-eRedCap UE, and Msg4 repetition is supported;
[0109] The CCCH size is 48 bits, the terminal is a RedCap UE, and it supports Msg4 repetition;
[0110] The CCCH size is 64 bits, the terminal is a RedCap UE, and Msg4 repetition is supported;
[0111] The CCCH size is 48 bits, the terminal is an eRedCap UE, and Msg4 repetition is supported;
[0112] The CCCH size is 64 bits, the terminal is an eRedCap UE, and Msg4 repetition is supported;
[0113] The CCCH size is 48 bits, the terminal is a RedCap UE or eRedCap UE, and supports Msg4 repetition;
[0114] The CCCH size is 64 bits, the terminal is a RedCap UE or eRedCap UE, and supports Msg4 repetition.
[0115] In a sixth aspect, an embodiment of the present disclosure proposes a terminal, which includes: one or more processors; wherein the terminal is used to execute an optional implementation of the information transmission method proposed in the first aspect.
[0116] In a seventh aspect, an embodiment of the present disclosure proposes a network device, and the above-mentioned terminal includes: one or more processors; wherein the above-mentioned network device is used to execute an optional implementation method of the information transmission method proposed in the second aspect.
[0117] In the eighth aspect, an embodiment of the present disclosure proposes a communication system, which includes: a network device and a terminal; wherein the network device is configured to execute the method described in the optional implementation manner of the second aspect, and the terminal is configured to execute the method described in the optional implementation manner of the first aspect.
[0118] In the ninth aspect, an embodiment of the present disclosure proposes a storage medium, which stores instructions. When the instructions are executed on a communication device, the communication device executes the method described in the optional implementation of the first and second aspects.
[0119] In a tenth 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 of the first and second aspects.
[0120] In an eleventh 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 optional implementation of the first and second aspects.
[0121] In a twelfth aspect, an embodiment of the present disclosure provides a chip or a chip system, which includes a processing circuit configured to execute the method described in the optional implementation of the first and second aspects above.
[0122] It is understandable that the above-mentioned access network devices, terminals, communication systems, storage media, program products, computer programs, chips, or chip systems are all used to perform the methods proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.
[0123] The present disclosure provides an information transmission method. In some embodiments, the terms "information transmission method," "transmission method," and "communication method configuration method" are interchangeable; the terms "communication device," "configuration device," and "information transmission device" are interchangeable; and the terms "communication system," "configuration system," "transmission system," and "data transmission system" are interchangeable.
[0124] 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.
[0125] 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.
[0126] 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.
[0127] 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.
[0128] In the embodiments of the present disclosure, “plurality” refers to two or more.
[0129] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.
[0130] 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.
[0131] 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.
[0132] 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.
[0133] 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.
[0134] 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.
[0135] 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.
[0136] 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.
[0137] In some embodiments, "network (or network device)" can be interpreted as a device included in the network, such as an access network device, a core network device, etc.
[0138] 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.
[0139] 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.
[0140] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.
[0141] In some embodiments, data, information, etc. may be obtained with the user's consent.
[0142] FIG1 is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.
[0143] As shown in FIG1 , a communication system 100 includes a terminal 101 and a network device 102 .
[0144] 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.
[0145] In some embodiments, the network device 102 may include at least one of an access network device 1021 and a core network device 1022 .
[0146] In some embodiments, the access network device 1021 is, for example, a node or device that accesses the 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 1021 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 1022 can be a device including one or more network elements, or can be multiple devices or device groups, each including all or part of the one or more network elements. The network element can be virtual or physical. The core network includes, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).
[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 FIG1 , or a portion thereof, but are not limited thereto. The entities shown in FIG1 are illustrative only. The communication system may include all or part of the entities shown in FIG1 , or may include other entities outside of FIG1 . The number and form of the entities are arbitrary, and the entities may be physical or virtual. The connection relationships between the entities are illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, 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 the present disclosure, in order to improve the downlink coverage of Msg4, the downlink coverage performance can be improved by Msg4 repetition. In order to facilitate the network device to know whether the terminal supports Msg4 repetition, the UE informs the network device of the terminal's support status before scheduling Msg4.
[0154] FIG2A is an interactive diagram of an information transmission method according to an embodiment of the present disclosure. As shown in FIG2A , the present disclosure embodiment relates to an information transmission method for a terminal 101 and a network device 102, and the method includes:
[0155] In step S2101, the terminal 101 sends a message 3 Msg3 containing indication information to the network device 102, wherein the indication information is used to indicate whether the terminal 101 supports the repetition capability of the message 4 Msg4, the type of the terminal, and the size of the CCCH.
[0156] In some embodiments, the network device 102 may be a base station, or may be a wireless access point (such as a wireless network access point), etc., which is not limited in the present disclosure.
[0157] In some embodiments, the terms "wireless network access point", "Wireless Fidelity Access Point", "WiFi AP", etc. can be used interchangeably.
[0158] In some embodiments, the indication information may be carried by the (Logical Channel Identification, LCID) in Msg3.
[0159] In some embodiments, the indication information is carried by an extended logical channel identifier LCID field in a MAC subheader of a media access control MAC service data unit SDU, wherein the MAC SDU includes uplink common control channel UL CCCH information.
[0160] In some embodiments, the terms "MAC", "media access control", "media access control", "media access control" and the like can be used interchangeably.
[0161] In some embodiments, the terms "service data unit", "service data unit", "SDU", etc. can be used interchangeably.
[0162] In some embodiments, terms such as "uplink common control channel", "UL CCCH", and "uplink common control channel" can be used interchangeably.
[0163] Typically, a MAC PDU consists of a header, zero or more SDUs, zero or more control elements (CEs), and possibly padding. The MAC PDU header may have one or more subheaders, each corresponding to an SDU, CE, or padding. The MAC subheader for a MAC SDU containing UL CCCH information consists of header fields such as the extension (LX) or radio resource (R) bit, the reserved (R) bit, and the LCID.
[0164] In some embodiments, the terminal 101 may carry the indication information by extending the LCID via LX.
[0165] In some embodiments, the type of terminal includes any of the following: capability-constrained terminal, enhanced capability-constrained terminal, non-capability-constrained terminal, non-enhanced capability-constrained terminal, capability-constrained non-terrestrial network terminal, enhanced capability-constrained non-terrestrial network terminal, non-capability-constrained non-terrestrial network terminal, non-enhanced capability-constrained non-terrestrial network terminal, capability-constrained terrestrial network terminal, enhanced capability-constrained terrestrial network terminal, non-capability-constrained terrestrial network terminal, non-enhanced capability-constrained terrestrial network terminal.
[0166] In some embodiments, technical terms such as "capability limited terminal", "Reduced Capability UE", "RedCap UE", "RedCap terminal" and the like can be used interchangeably.
[0167] In some embodiments, the terms "enhanced terminal", "enhanced RedCap UE", "eRedCap UE", "(e)RedCap UE", "eRedCap terminal" and the like may be used interchangeably.
[0168] In some embodiments, the terms "non-capability limited terminal", "non Reduced Capability UE", "non-RedCap UE", "non-RedCap terminal" and the like can be used interchangeably.
[0169] In some embodiments, the terms "non-enhanced terminal", "non enhanced RedCap UE", "non-eRedCap UE", "non-(e)RedCap UE", "non-eRedCap terminal" and the like can be used interchangeably.
[0170] In some embodiments, the terms "non-terrestrial network", "non-terrestrial network", "NTN", etc. may be used interchangeably.
[0171] In some embodiments, the terms "terrestrial network", "terrestrial network", "non NTN", "TN", etc. can be used interchangeably.
[0172] In some embodiments, terms such as "CCCH", "common control channel", and "common control channel" can be used interchangeably.
[0173] In some embodiments, the size of CCCH includes 48 bits and 64 bits.
[0174] In some embodiments, different indication information, that is, different LCIDs, can distinguish different terminal types, different CCCH sizes, and / or whether the Msg4 repetition capability is supported.
[0175] In some embodiments, different LCIDs may be used to indicate one or more of the following:
[0176] The CCCH size is 48 bits, the terminal is a non-eRedCap UE, and Msg4 repetition is supported;
[0177] The CCCH size is 64 bits, the terminal is a non-eRedCap UE, and Msg4 repetition is supported;
[0178] The CCCH size is 48 bits, the terminal is a RedCap UE, and Msg4 repetition is supported;
[0179] The CCCH size is 64 bits, the terminal is a RedCap UE, and Msg4 repetition is supported;
[0180] The CCCH size is 48 bits, the terminal is an eRedCap UE, and it supports Msg4 repetition;
[0181] The CCCH size is 64 bits, the terminal is an eRedCap UE, and Msg4 repetition is supported;
[0182] The CCCH size is 48 bits, the terminal is a RedCap UE or eRedCap UE, and supports Msg4 repetition;
[0183] The CCCH size is 64 bits, the terminal is a RedCap UE or eRedCap UE, and supports Msg4 repetition.
[0184] In some embodiments, terms such as "CCCH size is 48 bits, the terminal is a non-eRedCap UE, and supports Msg4 repetition", "CCCH size is 48 bits, the terminal is a non-eRedCap UE, and supports Msg4 repetition", "CCCH of size 48 bits for Msg4 repetition, except for an eRedCap UE", "CCCH size is 48 bits, the terminal supports Msg4repetition, and the terminal type is a non-eRedCap UE" can be used interchangeably.
[0185] In some embodiments, the terms "CCCH size is 64 bits, the terminal is a non-eRedCap UE, and supports Msg4 repetition", "CCCH size is 64 bits, the terminal is a non-eRedCap UE, and supports Msg4 repetition", "CCCH of size 64bits for Msg4 repetition, except for an eRedCap UE", "CCCH size is 64 bits, the terminal supports Msg4repetition, and the terminal type is a non-eRedCap UE" can be used interchangeably.
[0186] In some embodiments, terms such as "CCCH size is 48 bits, the terminal is a RedCap UE, and supports Msg4 repetition", "CCCH size is 48 bits, the terminal is a RedCap UE, and supports Msg4 repetition", "CCCH of size 48bits for Msg4 repetition of a RedCap UE", "CCCH size is 48 bits, the terminal supports Msg4 repetition, and the terminal type is RedCap UE" can be used interchangeably.
[0187] In some embodiments, terms such as "CCCH size is 64 bits, the terminal is a RedCap UE, and supports Msg4 repetition", "CCCH size is 64 bits, the terminal is a RedCap UE, and supports Msg4 repetition", "CCCH of size 64bits for Msg4 repetition of a RedCap UE", "CCCH size is 64 bits, the terminal supports Msg4 repetition, and the terminal type is RedCap UE" can be used interchangeably.
[0188] In some embodiments, the terms "CCCH size is 48 bits, the terminal is an eRedCap UE, and supports Msg4 repetition", "CCCH size is 48 bits, supports Msg4 repetition, and the terminal type is eRedCap UE", "CCCH of size 48bits for Msg4 repetition of an eRedCap UE", "CCCH size 48 bits, the terminal type is eRedCap UE, and supports Msg4 repetition" can be used interchangeably.
[0189] In some embodiments, the terms "CCCH size is 48 bits, the terminal is an eRedCap UE, and supports Msg4 repetition", "CCCH size is 64 bits, supports Msg4 repetition, and the terminal type is eRedCap UE", "CCCH of size 64bits for Msg4 repetition of an eRedCap UE", "CCCH size is 64 bits, the terminal type is eRedCap UE, and supports Msg4 repetition" can be used interchangeably.
[0190] In some embodiments, the terms "CCCH size is 48 bits, the terminal is a RedCap UE or eRedCap UE, and supports Msg4repetition", "CCCH of size 48bits for Msg4 repetition of an RedCap or eRedCap UE", "CCCH size is 48 bits, the terminal type is a RedCap UE or eRedCap UE, and supports Msg4 repetition", "CCCH size is 48 bits, the terminal supports Msg4 repetition, and the type is RedCap UE or eRedCap UE" can be used interchangeably.
[0191] In some embodiments, the terms "CCCH size is 64 bits, the terminal is a RedCap UE or eRedCap UE, and supports Msg4repetition", "CCCH of size 64bits for Msg4 repetition of an RedCap or eRedCap UE", "CCCH of size 64bits for Msg4 repetition of an RedCap or eRedCap UE", "CCCH of size 64 bits is used to indicate that the terminal type is RedCap UE or eRedCap UE and supports Msg4 repetition", "CCCH of size 64 bits is used to indicate that the terminal supports Msg4 repetition and the type is RedCap UE or eRedCap UE" can be used interchangeably.
[0192] In some embodiments, the network device 102 receives Msg3 containing indication information.
[0193] In step S2102 , the terminal 101 supports the Msg4 repetition capability, and the network device 102 repeatedly sends Msg4 to the terminal 101 .
[0194] The information transmission method involved in the embodiment of the present disclosure may include at least one of steps S2101 to S2102. For example, step S2101 may be implemented as an independent embodiment, but is not limited thereto.
[0195] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.
[0196] In the embodiments of the present disclosure, each step can also be implemented independently.
[0197] In this embodiment, the terminal sends a Msg3 containing indication information to the network device to indicate to the network device whether the terminal supports the Msg4 repetition capability, the type of the terminal and the type of UL CCCH, etc., so that the network device can repeatedly send the Msg4 of the terminal according to the indication information, thereby enhancing the downlink transmission of the terminal and improving the downlink coverage performance of the terminal.
[0198] FIG2B is an interactive diagram of an information transmission method according to an embodiment of the present disclosure. As shown in FIG2B , the present disclosure embodiment relates to an information transmission method for terminal 101 and network device 102, the method comprising:
[0199] In step S2201, the terminal 101 sends a message 3, Msg3, containing indication information to the network device 102, wherein the indication information is used to indicate whether the terminal 101 supports the Msg4 repetition capability and the type of the terminal.
[0200] In some embodiments, different indication information (different LCIDs) may be used to indicate one or more of the following:
[0201] The terminal is a non-eRedCap UE and supports Msg4 repetition; the terminal is a non-RedCap UE and supports Msg4 repetition; the terminal is an eRedCap UE and supports Msg4 repetition; the terminal is a RedCap UE and supports Msg4 repetition; the terminal is an eRedCap UE or RedCap UE and supports Msg4 repetition.
[0202] In some embodiments, terms such as "the terminal is a non-eRedCap UE and supports Msg4 repetition", "CCCH for Msg4 repetition, except for an eRedCap UE", "the terminal supports Msg4 repetition and the terminal is a non-eRedCap UE" can be used interchangeably.
[0203] In some embodiments, terms such as "the terminal is a non-RedCap UE and supports Msg4 repetition", "CCCH for Msg4 repetition, except for an RedCap UE", "the terminal supports Msg4 repetition and the terminal is a non-RedCap UE" can be used interchangeably.
[0204] In some embodiments, terms such as "the terminal is an eRedCap UE and supports Msg4 repetition", "CCCH for Msg4 repetition for an eRedCap UE", "the terminal supports Msg4 repetition, and the terminal is an eRedCap UE" can be used interchangeably.
[0205] In some embodiments, terms such as "the terminal is a RedCap UE and supports Msg4 repetition", "CCCH for Msg4 repetition for an RedCap UE", "the terminal supports Msg4 repetition, and the terminal is a RedCap UE" can be used interchangeably.
[0206] In some embodiments, terms such as "the terminal is an eRedCap UE or RedCap UE and supports Msg4 repetition", "CCCH for Msg4 repetition for an RedCap UE or e RedCap UE", "the terminal supports Msg4 repetition, and the terminal is a RedCap UE or eRedCap UE" can be used interchangeably.
[0207] In some embodiments, the network device 102 receives Msg3 containing indication information.
[0208] In step S2202 , the terminal 101 supports the Msg4 repetition capability, and the network device 102 repeatedly sends Msg4 to the terminal 101 .
[0209] The information transmission method involved in the embodiment of the present disclosure may include at least one of steps S2201 to S2202. For example, step S2201 may be implemented as an independent embodiment, but is not limited thereto.
[0210] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.
[0211] In the embodiments of the present disclosure, each step can also be implemented independently.
[0212] In this embodiment, the terminal sends a Msg3 containing indication information to the network device, indicating to the network device whether the terminal supports the Msg4 repetition capability and the type of the terminal, so that the network device can repeatedly send the Msg4 of the terminal according to the indication information, thereby enhancing the downlink transmission of the terminal and improving the downlink coverage performance of the terminal.
[0213] FIG2C is an interactive diagram of an information transmission method according to an embodiment of the present disclosure. As shown in FIG2C , the present disclosure embodiment relates to an information transmission method for terminal 101 and network device 102, the method comprising:
[0214] In step S2301, the terminal 101 sends a message 3 Msg3 containing indication information to the network device 102, wherein the indication information is used to indicate whether the terminal 101 supports the Msg4 repetition capability and the size of the CCCH.
[0215] In some implementations, different LCIDs can be used to indicate one or more of the following:
[0216] If the terminal supports Msg4 repetition, the CCCH size is 48 bits; if the terminal supports Msg4 repetition, the CCCH size is 64 bits.
[0217] In some embodiments, terms such as “the terminal supports Msg4 repetition, the CCCH size is 48 bits” and “CCCH of size 48 bits for Msg4 Repetition” may be used interchangeably.
[0218] In some embodiments, terms such as “the terminal supports Msg4 repetition, the CCCH size is 64 bits” and “CCCH of size 64 bits for Msg4 Repetition” may be used interchangeably.
[0219] In some embodiments, the network device 102 receives Msg3 containing indication information.
[0220] In step S2302 , the terminal 101 supports the Msg4 repetition capability, and the network device 102 repeatedly sends Msg4 to the terminal 101 .
[0221] The information transmission method involved in the embodiment of the present disclosure may include at least one of steps S2301 to S2302. For example, step S2301 may be implemented as an independent embodiment, but is not limited thereto.
[0222] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.
[0223] In the embodiments of the present disclosure, each step can also be implemented independently.
[0224] In this embodiment, the terminal sends a Msg3 containing indication information to the network device to indicate to the network device whether the terminal supports the Msg4 repetition capability and the size of CCCH, etc., so that the network device can repeatedly send the Msg4 of the terminal according to the indication information, thereby enhancing the downlink transmission of the terminal and improving the downlink coverage performance of the terminal.
[0225] FIG3A is a flow chart of a method for transmitting information according to an embodiment of the present disclosure. As shown in FIG3A , the embodiment of the present disclosure relates to a method for transmitting information, which is used in a terminal. The method includes:
[0226] Step S3101: Send a message 3 (Msg3) containing indication information to the network device 102, wherein the indication information is used to indicate whether the terminal 101 supports the repetition capability of the message 4 (Msg4), the type of the terminal, and the size of the CCCH.
[0227] For a detailed description of step S3101, please refer to step S2101 in the embodiment shown in FIG2A , which will not be repeated here.
[0228] In this embodiment, the terminal sends a Msg3 containing indication information to the network device to indicate to the network device whether the terminal supports the Msg4 repetition capability, the type of the terminal and at least one of the UL CCCH type, so that the network device can repeatedly send the Msg4 of the terminal according to the indication information, thereby enhancing the downlink transmission of the terminal and improving the downlink coverage performance of the terminal.
[0229] FIG3B is a flow chart of a method for transmitting information according to an embodiment of the present disclosure. As shown in FIG3B , the embodiment of the present disclosure relates to a method for transmitting information, which is used in terminal 101 and includes:
[0230] Step S3201: Send a message 3, Msg3, containing indication information to the network device 102, wherein the indication information is used to indicate whether the terminal 101 supports the Msg4 repetition capability.
[0231] In some embodiments, the indication information is carried by an extended logical channel identifier LCID field in a MAC subheader of a media access control MAC service data unit SDU, wherein the MAC SDU includes uplink common control channel UL CCCH information.
[0232] In some embodiments, the indication information is also used to indicate the type of the terminal.
[0233] In some embodiments, the type of terminal includes any of the following:
[0234] Capability-constrained terminal, enhanced capability-constrained terminal, non-capability-constrained terminal, non-enhanced capability-constrained terminal, capability-constrained non-terrestrial network terminal, enhanced capability-constrained non-terrestrial network terminal, non-capability-constrained non-terrestrial network terminal, non-enhanced capability-constrained non-terrestrial network terminal, capability-constrained terrestrial network terminal, enhanced capability-constrained terrestrial network terminal, non-capability-constrained terrestrial network terminal, non-enhanced capability-constrained terrestrial network terminal.
[0235] In some embodiments, the indication information is further used to indicate the size of the common control channel CCCH.
[0236] In some embodiments, the size of the CCCH includes any one of the following: 48 bits, 64 bits.
[0237] In some embodiments, different indication information is used to indicate one or more of the following:
[0238] The CCCH size is 48 bits, the terminal is a non-eRedCap UE, and Msg4 repetition is supported;
[0239] The CCCH size is 64 bits, the terminal is a non-eRedCap UE, and Msg4 repetition is supported;
[0240] The CCCH size is 48 bits, the terminal is a RedCap UE, and it supports Msg4 repetition;
[0241] The CCCH size is 64 bits, the terminal is a RedCap UE, and Msg4 repetition is supported;
[0242] The CCCH size is 48 bits, the terminal is an eRedCap UE, and Msg4 repetition is supported;
[0243] The CCCH size is 64 bits, the terminal is an eRedCap UE, and Msg4 repetition is supported;
[0244] The CCCH size is 48 bits, the terminal is a RedCap UE or eRedCap UE, and supports Msg4 repetition;
[0245] The CCCH size is 64 bits, the terminal is a RedCap UE or eRedCap UE, and supports Msg4 repetition.
[0246] For a detailed introduction to step S3201, please refer to the steps in the embodiments shown in Figures 2A, 2B and 2C, which will not be repeated here.
[0247] In this embodiment, the terminal indicates to the network device whether the terminal supports the Msg4 repetition capability by sending Msg3 containing indication information to the network device, thereby providing a basis and conditions for the network device to repeatedly send Msg4 to the terminal, thereby enhancing the downlink transmission of the terminal and improving the downlink coverage performance of the terminal.
[0248] FIG4A is a flow chart of a method for transmitting information according to an embodiment of the present disclosure. As shown in FIG4A , the embodiment of the present disclosure relates to a method for transmitting information, which is used in a network device 102 and includes:
[0249] Step S4101: receiving a message 3 Msg3 including indication information sent by the terminal 101, wherein the indication information is used to indicate whether the terminal 101 supports the repetition capability of the message 4 Msg4, the type of the terminal, and the size of the CCCH.
[0250] Step S4201: Terminal 101 supports the Msg4 repetition capability and repeatedly sends Msg4 to Terminal 101.
[0251] For a detailed description of step S4101 and step S4102, reference may be made to step S2101 and step S2102 in the embodiment shown in FIG2A , which will not be repeated here.
[0252] The information transmission method involved in the embodiment of the present disclosure may include at least one of steps S4101 to S4102. For example, step S4101 may be implemented as an independent embodiment, but is not limited thereto.
[0253] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.
[0254] In the embodiments of the present disclosure, each step can also be implemented independently.
[0255] In this embodiment, after receiving Msg3 containing indication information sent by the terminal, the network device can repeatedly send Msg4 to the terminal based on whether the terminal supports Msg4 repetition capability, the type of the terminal and the size of CCCH, thereby enhancing the downlink transmission of the terminal and improving the downlink coverage performance of the terminal.
[0256] FIG4B is a flow chart of a method for transmitting information according to an embodiment of the present disclosure. As shown in FIG4B , the embodiment of the present disclosure relates to a method for transmitting information, which is used in a network device 102 and includes:
[0257] Step S4201: receiving a message 3 Msg3 including indication information sent by the terminal 101, wherein the indication information is used to indicate whether the terminal 101 supports the repetition capability of the message 4 Msg4.
[0258] In some embodiments, the indication information is carried by an extended logical channel identifier LCID field in a MAC subheader of a media access control MAC service data unit SDU, wherein the MAC SDU includes uplink common control channel ULCCCH information.
[0259] In some embodiments, the indication information is also used to indicate the type of the terminal.
[0260] In some embodiments, the type of terminal includes any of the following:
[0261] Capability-constrained terminal, enhanced capability-constrained terminal, non-capability-constrained terminal, non-enhanced capability-constrained terminal, capability-constrained non-terrestrial network terminal, enhanced capability-constrained non-terrestrial network terminal, non-capability-constrained non-terrestrial network terminal, non-enhanced capability-constrained non-terrestrial network terminal, capability-constrained terrestrial network terminal, enhanced capability-constrained terrestrial network terminal, non-capability-constrained terrestrial network terminal, non-enhanced capability-constrained terrestrial network terminal.
[0262] In some embodiments, the indication information is further used to indicate the size of the common control channel CCCH.
[0263] In some embodiments, the size of the CCCH includes any one of the following: 48 bits, 64 bits.
[0264] In some embodiments, different indication information is used to indicate one or more of the following:
[0265] The CCCH size is 48 bits, the terminal is a non-eRedCap UE, and Msg4 repetition is supported;
[0266] The CCCH size is 64 bits, the terminal is a non-eRedCap UE, and Msg4 repetition is supported;
[0267] The CCCH size is 48 bits, the terminal is a RedCap UE, and it supports Msg4 repetition;
[0268] The CCCH size is 64 bits, the terminal is a RedCap UE, and Msg4 repetition is supported;
[0269] The CCCH size is 48 bits, the terminal is an eRedCap UE, and Msg4 repetition is supported;
[0270] The CCCH size is 64 bits, the terminal is an eRedCap UE, and Msg4 repetition is supported;
[0271] The CCCH size is 48 bits, the terminal is a RedCap UE or eRedCap UE, and supports Msg4 repetition;
[0272] The CCCH size is 64 bits, the terminal is a RedCap UE or eRedCap UE, and supports Msg4 repetition.
[0273] For a detailed introduction to step S4201, please refer to the steps in the embodiments shown in Figures 2A, 2B and 2C, which will not be repeated here.
[0274] In this embodiment, the network device can determine whether the terminal supports the Msg4 repetition capability by receiving Msg3 containing indication information sent by the terminal, thereby providing a basis and conditions for the network device to repeatedly send Msg4 to the terminal, thereby enhancing the downlink transmission of the terminal and improving the downlink coverage performance of the terminal.
[0275] FIG5 is an interactive diagram of an information transmission method according to an embodiment of the present disclosure. As shown in FIG5 , the present disclosure embodiment relates to an information transmission method for a communication system, including: a terminal 101 and a network device 102, and the method includes:
[0276] In step S5101, the terminal 101 sends a message 3, Msg3, containing indication information to the network device 102, wherein the indication information is used to indicate whether the terminal 101 supports the Msg4 repetition capability.
[0277] In step S5102 , the terminal 101 supports the Msg4 repetition capability, and the network device 102 repeatedly sends Msg4 to the terminal 101 .
[0278] For a detailed description of steps S5101 - S5102 , please refer to the above embodiment description.
[0279] In the embodiment of the present disclosure, the terminal indicates to the network device whether it supports the Msg4 repetition capability through Msg3 containing indication information, thereby providing a basis and conditions for the network device to repeatedly send the Msg4 of the terminal, thereby enhancing the downlink transmission of the terminal and improving the downlink coverage performance of the terminal.
[0280] The following is an exemplary introduction to the above method.
[0281] The terminal carries indication information in Msg3 to indicate whether the terminal supports Msg4 repetition. The indication information uses LCID to identify whether the UE supports Msg4 repetition.
[0282] Optionally, for the LCID field in the MAC subheader of a MAC SDU containing UL CCCH, the LCID value is used to identify the MACsubPDU as a MAC SDU containing UL CCCH. To simultaneously indicate whether the UE supports Msg4 repetition, a new LCID is used, which indicates that the MACsubPDU is a MAC SDU containing UL CCCH and that the UE supports Msg4 repetition.
[0283] Optionally, the LCID is an LCID extended by the LX field.
[0284] Optional, applicable to TN cells or NTN cells.
[0285] Optional, applicable to idle / inactive / connected terminals.
[0286] Optionally, LCID is used to identify whether the UE supports Msg4 repetition, including using different LCIDs to distinguish terminal types.
[0287] Optionally, the terminal type includes one or more of the following: RedCap UE, eRedCap UE, non-eRedCap UE, RedCap NTN UE, eRedCap NTN UE, non-eRedCap NTN UE, RedCap non-NTN UE, eRedCap non-NTN UE, non-eRedCap non-NTN UE.
[0288] Optionally, different LCIDs are used to distinguish one or more of the following:
[0289] CCCH for Msg4 repetition,except for an eRedCap UE;
[0290] CCCH for Msg4 repetition for an RedCap UE;
[0291] CCCH for Msg4 repetition for an eRedCap UE;
[0292] CCCH for Msg4 repetition for an RedCap or eRedCap UE.
[0293] Optionally, the adopting of LCID to identify whether the UE supports Msg4 repetition includes adopting different LCIDs to distinguish CCCH sizes.
[0294] Optionally, different LCIDs are used to distinguish one or more of the following:
[0295] CCCH of size 48bits for Msg4 repetition
[0296] CCCH of size 64bits for Msg4 repetition
[0297] Optionally, LCID is used to identify whether the UE supports Msg4 repetition, CCCH size and UE type.
[0298] Optionally, different LCIDs are used to distinguish one or more of the following:
[0299] CCCH of size 48bits for Msg4 repetition,except for an eRedCap UE;
[0300] CCCH of size 64bits for Msg4 repetition,except for an eRedCap UE;
[0301] CCCH of size 48bits for Msg4 repetition of a RedCap UE;
[0302] CCCH of size 64bits for Msg4 repetition of a RedCap UE;
[0303] CCCH of size 48bits for Msg4 repetition of an eRedCap UE;
[0304] CCCH of size 64bits for Msg4 repetition of an eRedCap UE;
[0305] CCCH of size 48bits for Msg4 repetition of an RedCap or eRedCap UE;
[0306] CCCH of size 64bits for Msg4 repetition of an RedCap or eRedCap UE.
[0307] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, a communication 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 communication apparatus is provided, comprising units or modules for implementing each step performed by a network device (e.g., a RAN) in any of the above methods.
[0308] 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.
[0309] 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.
[0310] FIG6A is a schematic diagram of the structure of a terminal proposed in an embodiment of the present disclosure. As shown in FIG6A , the terminal 6100 may include at least one of a transceiver module 6101 and a processing module 6102. The terminal 6100 may include:
[0311] The transceiver module 6102 is configured to send a message 3 (Msg3) containing indication information to the network device, wherein the indication information is used to indicate whether the terminal supports the repetition capability of the message 4 (Msg4).
[0312] Optionally, the indication information is carried by an extended logical channel identifier LCID field in a MAC subheader of a media access control MAC service data unit SDU, wherein the MAC SDU includes uplink common control channel UL CCCH information.
[0313] Optionally, the indication information is also used to indicate the type of the terminal.
[0314] Optionally, the type of the terminal includes any one of the following:
[0315] Capability restricted terminal RedCap UE, enhanced capability restricted terminal eRedCap UE, non-capability restricted terminal, non-enhanced capability restricted terminal, capability restricted non-terrestrial network terminal, enhanced capability restricted non-terrestrial network terminal, non-capability restricted non-terrestrial network terminal, non-enhanced capability restricted non-terrestrial network terminal, capability restricted terrestrial network terminal, enhanced capability restricted terrestrial network terminal, non-capability restricted terrestrial network terminal, non-enhanced capability restricted terrestrial network terminal.
[0316] Optionally, the indication information is also used to indicate the size of a common control channel CCCH.
[0317] Optionally, the size of the CCCH includes any one of the following: 48 bits, 64 bits.
[0318] Optionally, the different indication information is used to indicate one or more of the following:
[0319] The CCCH size is 48 bits, the terminal is a non-eRedCap UE, and Msg4 repetition is supported;
[0320] The CCCH size is 64 bits, the terminal is a non-eRedCap UE, and Msg4 repetition is supported;
[0321] The CCCH size is 48 bits, the terminal is a RedCap UE, and it supports Msg4 repetition;
[0322] The CCCH size is 64 bits, the terminal is a RedCap UE, and Msg4 repetition is supported;
[0323] The CCCH size is 48 bits, the terminal is an eRedCap UE, and Msg4 repetition is supported;
[0324] The CCCH size is 64 bits, the terminal is an eRedCap UE, and Msg4 repetition is supported;
[0325] The CCCH size is 48 bits, the terminal is a RedCap UE or eRedCap UE, and supports Msg4 repetition;
[0326] The CCCH size is 64 bits, the terminal is a RedCap UE or eRedCap UE, and supports Msg4 repetition.
[0327] FIG6B is a schematic diagram of the structure of a network device according to an embodiment of the present disclosure. As shown in FIG6B , the network device 6200 may include at least one of a transceiver module 6201 and a processing module 6202. The network device 6200 may include:
[0328] The transceiver module 6202 is configured to receive a message 3 (Msg3) containing indication information sent by a terminal, wherein the indication information is used to indicate whether the terminal supports a repetition capability of a message 4 (Msg4);
[0329] The terminal supports Msg4 repetition, and the transceiver module 6202 is used to repeatedly send Msg4 to the terminal.
[0330] Optionally, the indication information is carried by an extended logical channel identifier LCID field in a MAC subheader of a media access control MAC service data unit SDU, wherein the MAC SDU includes uplink common control channel ULCCCH information.
[0331] Optionally, the indication information is also used to indicate the type of the terminal.
[0332] Optionally, the type of the terminal includes any one of the following:
[0333] Capability restricted terminal RedCap UE, enhanced capability restricted terminal eRedCap UE, non-capability restricted terminal, non-enhanced capability restricted terminal, capability restricted non-terrestrial network terminal, enhanced capability restricted non-terrestrial network terminal, non-capability restricted non-terrestrial network terminal, non-enhanced capability restricted non-terrestrial network terminal, capability restricted terrestrial network terminal, enhanced capability restricted terrestrial network terminal, non-capability restricted terrestrial network terminal, non-enhanced capability restricted terrestrial network terminal.
[0334] Optionally, the indication information is also used to indicate the size of a common control channel CCCH.
[0335] Optionally, the size of the CCCH includes any one of the following: 48 bits, 64 bits.
[0336] Optionally, different indication information is used to indicate one or more of the following:
[0337] The CCCH size is 48 bits, the terminal is a non-eRedCap UE, and Msg4 repetition is supported;
[0338] The CCCH size is 64 bits, the terminal is a non-eRedCap UE, and Msg4 repetition is supported;
[0339] The CCCH size is 48 bits, the terminal is a RedCap UE, and it supports Msg4 repetition;
[0340] The CCCH size is 64 bits, the terminal is a RedCap UE, and Msg4 repetition is supported;
[0341] The CCCH size is 48 bits, the terminal is an eRedCap UE, and Msg4 repetition is supported;
[0342] The CCCH size is 64 bits, the terminal is an eRedCap UE, and Msg4 repetition is supported;
[0343] The CCCH size is 48 bits, the terminal is a RedCap UE or eRedCap UE, and supports Msg4 repetition;
[0344] The CCCH size is 64 bits, the terminal is a RedCap UE or eRedCap UE, and supports Msg4 repetition.
[0345] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, and the transmitting module and the receiving module may be separate or integrated. Optionally, the transceiver module may be interchangeable with the transceiver.
[0346] 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.
[0347] Figure 7A is a schematic diagram of the structure of a communication device 7100 proposed in an embodiment of the present disclosure. Communication device 7100 can be a network device, a terminal, a chip, a chip system, or a processor that supports an access 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 7100 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.
[0348] As shown in FIG7A , the communication device 7100 includes one or more processors 7101. The processor 7101 may be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control a communication device (e.g., 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 7100 is used to perform any of the above methods.
[0349] In some embodiments, the communication device 7100 further includes one or more memories 7102 for storing instructions. Optionally, all or part of the memories 7102 may be located outside the communication device 7100.
[0350] In some embodiments, the communication device 7100 further includes one or more transceivers 7103. When the communication device 7100 includes one or more transceivers 7103, the transceiver 7103 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., step S2101, step S2102, etc., but not limited thereto).
[0351] 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.
[0352] In some embodiments, the communication device 7100 may include one or more interface circuits 7104. Optionally, the interface circuit 7104 is connected to the memory 7102. The interface circuit 7104 may be configured to receive signals from the memory 7102 or other devices, and may be configured to send signals to the memory 7102 or other devices. For example, the interface circuit 7104 may read instructions stored in the memory 7102 and send the instructions to the processor 7101.
[0353] [Corrected 12.04.2024 according to Rule 91] The communication device 7100 described in the above embodiment may be a terminal, a network device, or a third entity, but the scope of the communication device 7100 described in this disclosure is not limited thereto, and the structure of the communication device 7100 may not be limited to FIG. 7A. 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.
[0354] 7B is a schematic diagram of the structure of a chip 7200 proposed in an embodiment of the present disclosure. If the communication device 7100 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 7200 shown in FIG7B , but the present disclosure is not limited thereto.
[0355] The chip 7200 includes one or more processors 7201 , and the chip 7200 is configured to execute any of the above methods.
[0356] In some embodiments, the chip 7200 further includes one or more interface circuits 7202. Optionally, the interface circuit 7202 is connected to the memory 7203. The interface circuit 7202 can be used to receive signals from the memory 7203 or other devices, and can be used to send signals to the memory 7203 or other devices. For example, the interface circuit 7202 can read instructions stored in the memory 7203 and send the instructions to the processor 7201.
[0357] In some embodiments, the interface circuit 7202 performs at least one of the communication steps such as sending and / or receiving in the above method (eg, step S2101 and step S2102 , but not limited thereto).
[0358] In some embodiments, terms such as interface circuit, interface, transceiver pin, and transceiver may be used interchangeably.
[0359] In some embodiments, the chip 7200 further includes one or more memories 7203 for storing instructions. Alternatively, all or part of the memories 7203 may be located outside the chip 7200.
[0360] The present disclosure also proposes a storage medium having instructions stored thereon. When the instructions are executed on the communication device 7100, the communication device 7100 executes 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.
[0361] The present disclosure also provides a program product, which, when executed by the communication device 7100, enables the communication device 7100 to perform any of the above methods. Optionally, the program product is a computer program product.
[0362] 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 method for transmitting information, characterized in that: The method is executed by a terminal, and includes: Sending a message three Msg3 containing indication information to the network device, wherein the indication information is used to indicate whether the terminal supports the repetition capability of message four Msg4.
2. The method according to claim 1, wherein The indication information is carried by an extended logical channel identifier LCID field in a MAC subheader of a media access control MAC service data unit SDU, wherein the MAC SDU includes uplink common control channel UL CCCH information.
3. The method according to claim 1, wherein The indication information is also used to indicate the type of the terminal.
4. The method according to claim 3, wherein The terminal type includes any of the following: Capability restricted terminal RedCap UE, enhanced capability restricted terminal eRedCap UE, non-capability restricted terminal, non-enhanced capability restricted terminal, capability restricted non-terrestrial network terminal, enhanced capability restricted non-terrestrial network terminal, non-capability restricted non-terrestrial network terminal, non-enhanced capability restricted non-terrestrial network terminal, capability restricted terrestrial network terminal, enhanced capability restricted terrestrial network terminal, non-capability restricted terrestrial network terminal, non-enhanced capability restricted terrestrial network terminal.
5. The method according to any one of claims 1 to 4, characterized in that: The indication information is also used to indicate the size of the common control channel CCCH.
6. The method according to claim 5, wherein The size of the CCCH includes any one of the following: 48 bits, 64 bits.
7. The method according to claim 5 or 6, wherein: Different instructions are used to indicate one or more of the following: The CCCH size is 48 bits, the terminal is a non-eRedCap UE, and Msg4 repetition is supported; The CCCH size is 64 bits, the terminal is a non-eRedCap UE, and Msg4 repetition is supported; The CCCH size is 48 bits, the terminal is a RedCap UE, and it supports Msg4 repetition; The CCCH size is 64 bits, the terminal is a RedCap UE, and Msg4 repetition is supported; The CCCH size is 48 bits, the terminal is an eRedCap UE, and Msg4 repetition is supported; The CCCH size is 64 bits, the terminal is an eRedCap UE, and Msg4 repetition is supported; The CCCH size is 48 bits, the terminal is a RedCap UE or eRedCap UE, and supports Msg4 repetition; The CCCH size is 64 bits, the terminal is a RedCap UE or eRedCap UE, and supports Msg4 repetition.
8. A method for transmitting information, characterized in that: The method is performed by a network device, and includes: Receiving a message 3 (Msg3) sent by a terminal containing indication information, wherein the indication information is used to indicate whether the terminal supports a repetition capability of message 4 (Msg4); The terminal supports Msg4 repetition and repeatedly sends Msg4 to the terminal.
9. The method according to claim 8, wherein The indication information is carried by an extended logical channel identifier LCID field in a MAC subheader of a media access control MAC service data unit SDU, wherein the MAC SDU includes uplink common control channel ULCCCH information.
10. The method according to claim 8, wherein The indication information is also used to indicate the type of the terminal.
11. The method according to claim 10, wherein The terminal type includes any of the following: Capability restricted terminal RedCap UE, enhanced capability restricted terminal eRedCap UE, non-capability restricted terminal, non-enhanced capability restricted terminal, capability restricted non-terrestrial network terminal, enhanced capability restricted non-terrestrial network terminal, non-capability restricted non-terrestrial network terminal, non-enhanced capability restricted non-terrestrial network terminal, capability restricted terrestrial network terminal, enhanced capability restricted terrestrial network terminal, non-capability restricted terrestrial network terminal, non-enhanced capability restricted terrestrial network terminal.
12. The method according to any one of claims 8 to 11, characterized in that: The indication information is also used to indicate the size of the common control channel CCCH.
13. The method according to claim 12, wherein: The size of the CCCH includes any one of the following: 48 bits, 64 bits.
14. The method according to claim 12 or 13, wherein: Different instructions are used to indicate one or more of the following: The CCCH size is 48 bits, the terminal is a non-eRedCap UE, and Msg4 repetition is supported; The CCCH size is 64 bits, the terminal is a non-eRedCap UE, and Msg4 repetition is supported; The CCCH size is 48 bits, the terminal is a RedCap UE, and Msg4 repetition is supported; The CCCH size is 64 bits, the terminal is a RedCap UE, and Msg4 repetition is supported; The CCCH size is 48 bits, the terminal is an eRedCap UE, and it supports Msg4 repetition; The CCCH size is 64 bits, the terminal is an eRedCap UE, and Msg4 repetition is supported; The CCCH size is 48 bits, the terminal is a RedCap UE or eRedCap UE, and supports Msg4 repetition; The CCCH size is 64 bits, the terminal is a RedCap UE or eRedCap UE, and supports Msg4 repetition.
15. A method for transmitting information, characterized in that: The method is performed by a communication system, and includes: The terminal sends a message 3 (Msg3) containing indication information to the network device, wherein the indication information is used to indicate whether the terminal supports the repetition capability of message 4 (Msg4); The terminal supports Msg4 repetition. The network device repeatedly sends Msg4 to the terminal.
16. A terminal, characterized in that: The terminal includes: The transceiver module is used to send a message three Msg3 containing indication information to the network device, wherein the indication information is used to indicate whether the terminal supports the repetition capability of message four Msg4.
17. A network device, characterized in that: The network equipment includes: a transceiver module, configured to receive a message 3 Msg3 containing indication information sent by a terminal, wherein the indication information is used to indicate whether the terminal supports a repetition capability of a message 4 Msg4; The terminal supports Msg4 repetition, and the transceiver module is further configured to repeatedly send Msg4 to the terminal.
18. A terminal, characterized in that: include: one or more processors; The terminal is used to execute the transmission control method according to any one of claims 1 to 7.
19. A network device, characterized in that: include: one or more processors; The network device is used to execute the transmission control method according to any one of claims 8 to 14.
20. A communication system, characterized in that: It comprises a network device and a terminal, wherein the terminal is configured to implement the information transmission method according to any one of claims 1 to 7, and the network device is configured to implement the information transmission method according to any one of claims 8 to 14.
21. [Corrected 12.04.2024 according to Rule 91] A storage medium storing instructions, characterized in that When the instruction is executed on a communication device, the communication device is caused to execute the information transmission method according to any one of claims 1 to 14.