WO2023206250A1 - 消息发送方法、消息接收方法、装置、设备及存储介质 - Google Patents

消息发送方法、消息接收方法、装置、设备及存储介质 Download PDF

Info

Publication number
WO2023206250A1
WO2023206250A1 PCT/CN2022/089941 CN2022089941W WO2023206250A1 WO 2023206250 A1 WO2023206250 A1 WO 2023206250A1 CN 2022089941 W CN2022089941 W CN 2022089941W WO 2023206250 A1 WO2023206250 A1 WO 2023206250A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
type
lcid
message
information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2022/089941
Other languages
English (en)
French (fr)
Inventor
牟勤
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Xiaomi Mobile Software Co Ltd
Original Assignee
Beijing Xiaomi Mobile Software Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Xiaomi Mobile Software Co Ltd filed Critical Beijing Xiaomi Mobile Software Co Ltd
Priority to CN202280001437.XA priority Critical patent/CN117322117A/zh
Priority to PCT/CN2022/089941 priority patent/WO2023206250A1/zh
Priority to EP22939102.4A priority patent/EP4518549A4/en
Priority to US18/860,363 priority patent/US20250358858A1/en
Publication of WO2023206250A1 publication Critical patent/WO2023206250A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols

Definitions

  • the present disclosure relates to the field of communications, and in particular to a message sending method, message receiving method, device, equipment and storage medium.
  • LTE Long Term Evolution
  • MTC Machine-Type Communication
  • NB-IoT Narrow Band-Internet of Things
  • the above-mentioned NB-IoT technology supports a maximum rate of several hundred kB
  • the above-mentioned MTC technology supports a maximum rate of several MB.
  • some businesses have emerged, such as smart home, wearable devices, and industrial sensing measurement services. These businesses usually require rates of tens to 100MB.
  • the above two major technologies of NB-IoT and MTC can no longer meet the requirements. the needs of these businesses.
  • UE user equipment
  • 5G New Radio NR
  • UE user equipment
  • 3GPP Third Generation Partnership Project
  • RedCap UE the terminal type of lightweight terminal
  • an early indication mechanism was introduced for RedCap UE. This mechanism is a mechanism for reporting terminal type and terminal capabilities during the random access process.
  • Embodiments of the present disclosure provide a message sending method, a message receiving method, an apparatus, a device, and a storage medium.
  • the technical solutions are as follows:
  • a message sending method is provided, the method is executed by a first type terminal, the method includes:
  • the type information of the first type terminal is different from the type information of the second type terminal and the type information of the third type terminal, and the terminal capabilities of the second type terminal and the third type terminal are both greater than the Terminal capabilities of the first type of terminal.
  • a message receiving method is provided, the method is performed by a network device, and the method includes:
  • the type information of the first type terminal is different from the type information of the second type terminal and the type information of the third type terminal, and the terminal capabilities of the second type terminal and the third type terminal are both greater than the Terminal capabilities of the first type of terminal.
  • a message sending device includes:
  • a sending module configured to send message 3 in the random access process to the network device, where the message 3 carries type information indicating the first type of terminal;
  • the type information of the first type terminal is different from the type information of the second type terminal and the type information of the third type terminal, and the terminal capabilities of the second type terminal and the third type terminal are both greater than the Terminal capabilities of the first type of terminal.
  • a message receiving device includes:
  • the second receiving module is configured to receive message 3 sent by the terminal during the random access process
  • the second processing module is configured to determine that the terminal is the first type terminal based on the type information of the first type terminal carried in the message 3;
  • the type information of the first type terminal is different from the type information of the second type terminal and the type information of the third type terminal, and the terminal capabilities of the second type terminal and the third type terminal are both greater than the Terminal capabilities of the first type of terminal.
  • a terminal where the terminal includes:
  • transceiver coupled to said processor
  • the processor is configured to execute executable instructions to implement the message sending method described in each aspect above.
  • a network device where the network device includes:
  • transceiver coupled to said processor
  • the processor is configured to execute executable instructions to implement the message receiving method described in each aspect above.
  • a computer-readable storage medium stores at least one instruction, at least a program, a code set or an instruction set, and the at least one instruction, The at least one program, the code set or the instruction set is loaded and executed by the processor to implement the message sending method as described in the above aspects, or the message receiving method as described in the above aspects.
  • a computer program product (or computer program) including computer instructions stored in a computer-readable storage medium;
  • the processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device performs the message sending method as described in the above aspects, or, as The message receiving methods described in the above aspects.
  • a chip is provided.
  • the chip includes editable logic circuits and/or program instructions. When the chip is run, it is used to implement the message sending method described in each aspect above, Or, the message receiving method as described in the above aspects.
  • the first type terminal is a type of terminal whose terminal capabilities are smaller than those of the second type terminal and the third type terminal; when the first type terminal sends the message 3 in the random access process to the network device, Message 3 can carry type information of the first type terminal, and the type information of the first type terminal is different from the type information of the second type terminal. That is, a type message specific to the first type terminal can be used to implement random access.
  • the terminal type of the first type of terminal is reported during the entry process. For example, the eRedCap UE can use its own type information to report the terminal type, that is, this method supports the eRedCap UE to report its own terminal type.
  • Figure 1 is a schematic diagram of a communication system according to an exemplary embodiment
  • Figure 2 is a flow chart of a message sending method according to an exemplary embodiment
  • Figure 3 is a schematic structural diagram of an UL MAC PDU according to an exemplary embodiment
  • Figure 4 is a schematic structural diagram of a MAC sub-header according to an exemplary embodiment
  • Figure 5 is a schematic structural diagram of a MAC sub-header according to another exemplary embodiment
  • Figure 6 is a flow chart of a message sending method according to another exemplary embodiment
  • Figure 7 is a flow chart of a message sending method according to another exemplary embodiment
  • Figure 8 is a flow chart of a message sending method according to another exemplary embodiment
  • Figure 9 is a flow chart of a message receiving method according to an exemplary embodiment
  • Figure 10 is a flow chart of a message receiving method according to another exemplary embodiment
  • Figure 11 is a flow chart of a message receiving method according to another exemplary embodiment
  • Figure 12 is a flow chart of a message receiving method according to another exemplary embodiment
  • Figure 13 is a block diagram of a message sending device according to an exemplary embodiment
  • Figure 14 is a block diagram of a message receiving device according to an exemplary embodiment
  • Figure 15 is a schematic structural diagram of a terminal according to an exemplary embodiment
  • Figure 16 is a schematic structural diagram of a network device according to an exemplary embodiment.
  • MTC massive machine type communications
  • NB-IoT NB-IoT
  • the above-mentioned NB-IoT technology supports a maximum rate of several hundred kB
  • the above-mentioned MTC technology supports a maximum rate of several MB.
  • some businesses have emerged, such as smart home, wearable devices, and industrial sensing measurement services. These businesses usually require rates of tens to 100MB.
  • the above two major technologies of NB-IoT and MTC can no longer meet the requirements. the needs of these businesses.
  • UE user equipment
  • 3GPP third generation partnership project
  • the terminal type of lightweight terminal Reduced Capability UE, RedCap UE
  • an early indication mechanism was introduced for RedCap UE.
  • This mechanism is to report the terminal type during the random access process.
  • the mechanism of terminal capabilities For example, during the random access process, the terminal indicates the terminal type through message 1 (Message 1, Msg.1), or message A (Message A, Msg.A), or message 3 (Message 3, Msg.3).
  • the enhanced lightweight terminal (enhanced Reduced Capability UE, eRedCap UE) terminal type was also introduced in 3GPP R18.
  • eRedCap UE further reduces the terminal bandwidth compared to RedCap UE.
  • the terminal bandwidth of eRedCap UE is reduced from 20MHz to 5MHz; in addition, eRedCap UE is compared with RedCap UE.
  • UE also further reduces the terminal's data processing time and peak rate. Therefore, the earlyindication mechanism of RedCap UE does not apply to eRedCap UE. Therefore, in order to solve the technical problem of reporting the terminal type of eRedCap UE, this application provides a message sending method and a message receiving method, as shown in the following embodiment.
  • Figure 1 shows a block diagram of a communication system provided by an exemplary embodiment of the present disclosure.
  • the communication system may include: an access network 12 and a user terminal 14.
  • the access network 12 includes several network devices 120 .
  • Network equipment (also called access network equipment) 120 may be a base station, which is a device deployed in the access network to provide wireless communication functions for user terminals (referred to as "terminals") 14.
  • Base stations can include various forms of macro base stations, micro base stations, relay stations, access points, etc.
  • the names of equipment with base station functions may be different.
  • eNodeB or eNB in the LTE system, it is called eNodeB or eNB; in the 5G NR system, it is called gNodeB or gNB.
  • the description "base station” may change.
  • the above-mentioned devices that provide wireless communication functions for the user terminal 14 are collectively referred to as network equipment.
  • the user terminal 14 may include various handheld devices with wireless communication functions, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to wireless modems, as well as various forms of user equipment, mobile stations (Mobile Station, MS) , terminal device (terminal device) and so on.
  • mobile stations Mobile Station, MS
  • terminal device terminal device
  • the network device 120 and the user terminal 14 communicate with each other through some air interface technology, such as the Uu interface.
  • uplink communication refers to sending signals to the network device 120
  • downlink communication refers to sending signals to the user terminal 14.
  • the user terminal 14 reports its terminal type to the network device 120 during the random access process.
  • the user terminal 14 may be a first type terminal, a second type terminal, or a third type terminal; the first type terminal, the second type terminal, and the third type terminal are three types of terminals corresponding to different terminal capabilities.
  • GSM Global System of Mobile Communication
  • CDMA Code Division Multiple Access
  • WCDMA broadband code division multiple access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • LTE-A Advanced Long Term Evolution
  • NR New Radio
  • UMTS Universal Mobile Telecommunication System
  • WiMAX Worldwide Interoperability for Microwave Access
  • WLAN Wireless Local Area Networks
  • WiFi Wireless Fidelity
  • Figure 2 shows a flow chart of a message sending method provided by an exemplary embodiment of the present disclosure.
  • the method is applied in the communication system shown in Figure 1 and is executed by a first type terminal.
  • the method includes:
  • Step 201 Send message 3 in the random access process to the network device, where message 3 carries type information indicating the first type of terminal.
  • the type information of the first type terminal is different from the type information of the second type terminal and the type information of the third type terminal.
  • the terminal capabilities of the second type terminal and the third type terminal are both greater than the terminal capabilities of the first type terminal.
  • the terminal capability of the second type terminal is smaller than the terminal capability of the third type terminal.
  • terminal capabilities include terminal bandwidth (Band Width).
  • the terminal bandwidth supported by the first type terminal is smaller than the terminal bandwidth supported by the second type terminal and the third type terminal.
  • the terminal bandwidth of the second type terminal is also smaller than the terminal bandwidth supported by the third type terminal.
  • the first type terminal is an eRedCap UE
  • the second type terminal is a RedCap UE
  • the third type terminal is a normal terminal.
  • Normal terminals are terminals defined in the 5G NR system, which include other terminals in the 5G NR system except eRedCap UE and RedCap UE.
  • the terminal capability also includes at least one of the terminal's peak rate (including uplink peak rate and downlink peak rate), mobility, delay, and supported frequency band.
  • peak rate including uplink peak rate and downlink peak rate
  • mobility including uplink peak rate and downlink peak rate
  • delay and supported frequency band.
  • the terminal type information includes a logical channel identifier (Logical Channel IDentifier, LCID).
  • LCID Logical Channel IDentifier
  • the type information of the first type terminal includes the first LCID
  • the type information of the second type terminal includes the second LCID
  • the type information of the third type terminal includes the third LCID; the first LCID, the second LCID, and the third LCID.
  • the LCIDs are all different, and the second LCID and the third LCID are also different.
  • the first LCID is used to indicate eRedCap UE
  • the second LCID is used to indicate RedCap UE
  • the third LCID is used to indicate normal terminal.
  • Message 3 includes an LCID information field, and the LCID information field is used to indicate the terminal type; for example, the LCID information field carries the first LCID, or the second LCID, or the third LCID.
  • the first LCID is carried in the LCID information field of message 3.
  • the first type terminal maps the first LCID to the LCID information field in message 3, and sends message 3 to the network device.
  • Message 3 contains the Common Control Channel (Common Control Channel, CCCH) Service Data Unit (SDU), where the CCCH SDU is included in the Media Access Control (Media Access Control, MAC) SDU, and each MAC SDU corresponds to There is a MAC subheader (subheader), and the MAC subheader contains the LCID information field.
  • CCCH Common Control Channel
  • MAC Media Access Control
  • FIG. 3 it shows a UL MAC PDU 300 provided by an exemplary embodiment.
  • UL refers to uplink (UpLink)
  • PDU refers to protocol data unit (Protocol Data Unit).
  • a UL MAC PDU 300 is composed of one or more MAC subPDU 301, and subPDU is a sub-protocol data unit.
  • MAC subPDU301 includes: MAC subPDU3011 includes MAC subheader and MAC SDU; MAC subPDU3012 includes MAC subheader and MAC control element (Control Element, CE); MAC subPDU3013 includes MAC subheader and padding.
  • a UL MAC PDU may or may not have MAC subPDU3013.
  • FIG. 4 it shows a schematic structural diagram of a MAC subheader 400 provided by an exemplary embodiment.
  • the MAC subheader 400 includes R/F/LCID/L.
  • Figure 5 which shows a schematic structural diagram of a MACsubheader 500 provided by another exemplary embodiment, the MACsubheader 500 includes R/LCID.
  • R is a reserved bit; F is used to indicate the length of the L field; L is used to indicate the length of the corresponding MAC SDU or MAC CE, in bytes; LCID refers to the logical channel identifier, and LCID is used to indicate the corresponding MAC SDU Logical channel instance.
  • the LCID values (LCID values) in the Uplink Shared Channel (UL-SCH) are reserved values (Reserved), and the Reserved index (Index) range is: 33- 51, binary representation is 100001-110011.
  • the index of the first LCID can be any value from 33-51.
  • the first type terminal is a type of terminal whose terminal capabilities are smaller than those of the second type terminal and the third type terminal; the first type terminal sends a random access message to the network device.
  • message 3 can carry type information of the first type terminal, and the type information of the first type terminal is different from the type information of the second type terminal, that is, the type information specific to the first type terminal can be used.
  • the type message is used to report the terminal type of the first type terminal during the random access process. For example, eRedCap UE can use the first LCID to report the terminal type.
  • the type information of the terminal is predefined by the protocol; for example, the type information of the first type of terminal, the type information of the second type of terminal, and the type information of the third type of terminal are predefined in the 3GPP protocol.
  • the first LCID is the type information of the first type of terminal predefined by the protocol; the second LCID is the type information of the second type of terminal predefined by the protocol; and the third LCID is the type of the third type of terminal predefined by the protocol. information.
  • the first type terminal sends the message 3 carrying the first LCID to the network device; the second type terminal sends the message 3 carrying the second LCID to the network device; and the third type terminal sends the message 3 carrying the second LCID to the network device.
  • the network device sends message 3 carrying the third LCID.
  • the terminal type information is configured by the network device for the terminal; for example, the first LCID is the type information configured by the network device for the first type of terminal.
  • the first type terminal performs step 202, as follows:
  • Step 202 Receive type information sent by the network device.
  • the first type terminal receives the type information of the first type terminal sent by the network device; for example, the eRedCap UE receives the first LCID configured by the network device.
  • the second type terminal receives the type information of the second type terminal sent by the network device.
  • the RedCap UE receives the second LCID configured by the network device
  • the third type terminal receives the third type terminal sent by the network device.
  • Type information for example, a normal terminal receives the third LCID configured by the network device.
  • the above type information is carried in the system message.
  • the first type terminal receives a system message sent by the network device, and the system message carries type information of the first type terminal; for example, the system message carries the first LCID.
  • the first type terminal may also receive type information sent by the network device before random access.
  • the first type terminal receives a system message sent by the network device, and obtains the type information of the first type terminal from the system message.
  • the message sending method provided in this embodiment allows the network device to configure its own type information for the first type terminal, thereby supporting terminal type reporting of the first type terminal.
  • step 201 in Figure 2 may include step 701, as follows:
  • Step 701 Send message 3 in the random access process to the network device.
  • Message 3 carries the second LCID and additional indication information.
  • the second LCID is an LCID shared by the first type terminal and the second type terminal.
  • the combination of the additional indication information and the second LCID is used to indicate the first type terminal; or the additional indication information is used to indicate the first type terminal.
  • the combination of the additional indication information and the second LCID is used to indicate the eRedCap UE; or the additional indication information is used to indicate the eRedCap UE.
  • the index of the second LCID is X
  • the index of the additional indication information is Y
  • the combination of the two, X+Y is used to indicate the eRedCap UE.
  • the second LCID may be predefined by the protocol; or, the second LCID may be configured by the network device for the first type terminal and the second type terminal.
  • the additional indication information may be predefined by the protocol; or, the additional indication information may be configured by the network device for the first type terminal.
  • the second LCID is carried in the LCID information field of message 3
  • the additional indication information is carried in the information field of message 3 except the LCID information field.
  • the additional indication information is carried in the MAC CE information field in message 3.
  • the information field used to carry additional indication information in message 3 is predefined by the protocol; or is configured by the network device for the first type of terminal.
  • the MAC CE information field used to carry additional indication information in message 3 is predefined by the protocol; or is configured by the network device for the first type of terminal.
  • the second LCID when message 3 carries the second LCID and does not carry additional indication information, the second LCID is used to indicate the second type of terminal, for example, the second LCID is used to indicate a RedCap UE.
  • the first type terminal and the second type terminal share the second LCID, and the first type terminal is indicated through a combination of the second LCID and the additional indication information, or through the additional indication information.
  • the first type terminal supports the terminal type reporting of the first type terminal when the first LCID cannot be used.
  • message 3 carries additional indication information, and when there is an information field for additional indication information in support message 3, the first type of terminal reports the terminal type without the need to report the terminal type through other signaling. Can save signaling overhead.
  • step 201 in Figure 2 may include the following steps: 801 to step 802, as shown in Figure 8, the steps are as follows:
  • Step 801 Send message 3 in the random access process to the network device, where message 3 carries the second LCID.
  • the above-mentioned second LCID is an LCID shared by the first type terminal and the second type terminal.
  • the second LCID may be predefined by the protocol; or, the second LCID may be configured by the network device for the first type terminal and the second type terminal.
  • the second LCID is carried in the LCID information field of message 3.
  • the LCID information field is the information field in the MACsubheader.
  • the first type terminal maps the second LCID on the LCID information field, and sends message 3 carrying the second LCID to the network device.
  • Step 802 After the random access is completed, radio resource control (Radio Resource Control, RRC) signaling is sent to the network device.
  • RRC Radio Resource Control
  • the RRC signaling carries additional indication information.
  • the additional indication information may be predefined by the protocol; or, the additional indication information may be configured by the network device for the first type terminal.
  • the first type terminal responds to the information field in message 3 that does not contain additional indication information, and after the random access is completed, sends RRC signaling to the network device.
  • the first type terminal when there is no information field for additional indication information in message 3, the first type terminal sends message 3 carrying the second LCID; after completing the random access, it sends the additional indication information to the network device through RRC signaling. Instructions.
  • the combination of the additional indication information and the second LCID is used to indicate the first type terminal; or the additional indication information is used to indicate the first type terminal.
  • the combination of the additional indication information and the second LCID is used to indicate the eRedCap UE; or the additional indication information is used to indicate the eRedCap UE.
  • the index of the additional indication information is Z, and Z is used to indicate eRedCap UE.
  • the first type terminal and the second type terminal share the second LCID, and the first type terminal is indicated through a combination of the second LCID and the additional indication information, or through the additional indication information.
  • To indicate the first type terminal support the terminal type reporting of the first type terminal when the first LCID cannot be used.
  • RRC signaling is used to send additional indication information, and the reporting of the terminal type by the first type terminal is supported when there is no information field for additional indication information in message 3.
  • Figure 9 shows a flow chart of a message receiving method provided by an exemplary embodiment of the present disclosure.
  • the method is applied in the communication system shown in Figure 1 and is executed by a network device.
  • the method includes:
  • Step 901 Receive message 3 in the random access process sent by the terminal.
  • message 3 carries the type information of the terminal.
  • message 3 may carry type information of the first type of terminal, or type information of the second type of terminal, or type information of the third type of terminal.
  • the type information of the first type terminal is different from the type information of the second type terminal and the type information of the third type terminal.
  • the terminal capabilities of the second type terminal and the third type terminal are both greater than the terminal capabilities of the first type terminal. For example, the terminal capability of the second type terminal is smaller than the terminal capability of the third type terminal.
  • the terminal capabilities include terminal bandwidth, and the terminal bandwidth supported by the first type terminal is smaller than the terminal bandwidth supported by the second type terminal and the third type terminal.
  • the terminal bandwidth of the second type terminal is also smaller than the terminal bandwidth supported by the third type terminal.
  • the terminal capabilities also include at least one of the terminal's peak rate, mobility, delay, and supported frequency bands.
  • the first type terminal is an eRedCap UE
  • the second type terminal is a RedCap UE
  • the third type terminal is a normal terminal.
  • Normal terminals are terminals defined in the 5G NR system, which include other terminals in the 5G NR system except eRedCap UE and RedCap UE.
  • the terminal type information includes LCID.
  • the type information of the first type terminal includes the first LCID
  • the type information of the second type terminal includes the second LCID
  • the type information of the third type terminal includes the third LCID; the first LCID, the second LCID, and the third LCID.
  • the LCIDs are all different, and the second LCID and the third LCID are also different.
  • the first LCID is used to indicate eRedCap UE
  • the second LCID is used to indicate RedCap UE
  • the third LCID is used to indicate normal terminal.
  • Message 3 includes an LCID information field, which is used to indicate the terminal type.
  • the first LCID is carried in the LCID information field of message 3, and the network device reads the first LCID in the LCID information field of message 3.
  • the second LCID is carried in the LCID information field of message 3, and the network device reads the second LCID in the LCID information field of message 3; or, the third LCID is carried in the LCID information field of message 3. , then the network device reads the third LCID in the LCID information field in message 3.
  • Step 902 Based on the type information of the first type terminal carried in message 3, determine that the terminal is the first type terminal.
  • the network device determines that the terminal is a first type terminal based on the first LCID carried in message 3. That is, the network device determines that the message 3 received is the first type terminal based on the first LCID.
  • message 3 carries the second LCID, which determines that the terminal is a second type terminal; or message 3 carries a third LCID, which determines that the terminal is a third type terminal.
  • the first type terminal is a type of terminal whose terminal capabilities are smaller than those of the second type terminal and the third type terminal; the network device receives the message sent by the terminal during the random access process.
  • Message 3 When message 3 carries the type information of the first type terminal, it can be determined that the terminal sending message 3 is the first type terminal, where the type information of the first type terminal and the type information of the second type terminal are both Different, that is, the type message specific to the first type terminal can be used to implement the terminal type reporting of the first type terminal during the random access process.
  • the terminal type information is predefined by the protocol; for example, the first LCID is the type information of the first type of terminal predefined by the protocol. In other embodiments, the terminal type information is configured for the terminal by the network device. As shown in Figure 10, the network device performs the following steps before receiving message 3:
  • Step 1001 Send type information of the first type terminal to the first type terminal.
  • the network device configures the first LCID for the eRedCap UE.
  • the network device configures the second LCID for the RedCap UE and configures the third LCID for the normal terminal.
  • the network device sends a system message to the first type terminal, and the system message carries type information of the first type terminal; for example, the system message carries the first LCID.
  • the network device sends terminal type information to the terminal.
  • the network device sends type information of the first type terminal to the first type terminal.
  • the network device configures its own type information for the first type terminal, thereby supporting terminal type reporting of the first type terminal.
  • step 902 in Figure 9 may include step 1102, as follows:
  • Step 1102 Based on the second LCID and additional indication information carried in message 3, determine that the terminal is a first type terminal.
  • the type information of the first type terminal includes the second LCID and additional indication information; the second LCID is the LCID shared by the first type terminal and the second type terminal; the combination of the additional indication information and the second LCID is used to indicate the first type terminal; or, additional indication information is used to indicate the first type terminal.
  • the second LCID may be predefined by the protocol; or, the second LCID may be configured by the network device for the first type terminal and the second type terminal.
  • the additional indication information may be predefined by the protocol; or, the additional indication information may be configured by the network device for the first type terminal.
  • the second LCID is carried in the LCID information field of message 3
  • the additional indication information is carried in the information field of message 3 except the LCID information field.
  • the additional indication information is carried in the MAC CE information field in message 3.
  • the information field used to carry additional indication information in message 3 is predefined by the protocol; or is configured by the network device for the first type of terminal.
  • the MAC CE information field used to carry additional indication information in message 3 is predefined by the protocol; or is configured by the network device for the first type of terminal.
  • the network device reads the second LCID from the LCID information field in message 3, and reads the additional indication information from the MAC CE information field in message 3; then, determines that the terminal is eRedCap based on the second LCID and the additional indication information.
  • the network device reads the second LCID from the LCID information field in message 3, and reads the additional indication information from the MAC CE information field in message 3; then, determines that the terminal is eRedCap based on the second LCID and the additional indication information.
  • UE User Service
  • the network device determines that the terminal is a second type terminal.
  • the first type terminal and the second type terminal share the second LCID, and the first type terminal is indicated through a combination of the second LCID and additional indication information, or through the additional indication information.
  • the first type terminal supports the terminal type reporting of the first type terminal when the first LCID cannot be used.
  • message 3 carries additional indication information, and when there is an information field for additional indication information in support message 3, the first type of terminal reports the terminal type without the need to report the terminal type through other signaling. Can save signaling overhead.
  • step 902 in Figure 9 may include steps 1202 to 1203, such as As shown in Figure 12, the steps are as follows:
  • Step 1202 After the random access is completed, receive the RRC signaling sent by the terminal.
  • the RRC signaling carries additional indication information.
  • the additional indication information may be predefined by the protocol; or, the additional indication information may be configured by the network device for the first type terminal.
  • the first type terminal responds to the information field that does not contain additional indication information in message 3. After the random access is completed, the network device will receive the RRC signaling sent by the terminal.
  • the network device will receive message 3 carrying the second LCID; after completing the random access, it will also receive message 3 carrying additional indication information.
  • RRC signaling
  • Step 1203 Based on the combination of the additional indication information and the second LCID carried in message 3, determine that the terminal is a first type terminal.
  • the above-mentioned second LCID is an LCID shared by the first type terminal and the second type terminal.
  • the second LCID may be predefined by the protocol; or, the second LCID may be configured by the network device for the first type terminal and the second type terminal.
  • the second LCID is carried in the LCID information field of message 3; the network device reads the second LCID from the LCID information field.
  • the combination of the additional indication information and the second LCID is used to indicate the first type terminal.
  • the combination of additional indication information and the second LCID is used to indicate eRedCap UE.
  • the additional indication information is used to indicate a first type terminal; then the network device may further determine that the terminal is the first type terminal based on the additional indication information.
  • additional indication information is used to indicate eRedCap UE.
  • the first type terminal and the second type terminal share the second LCID, and the first type terminal is indicated through a combination of the second LCID and additional indication information, or through the additional indication information.
  • the first type terminal supports the terminal type reporting of the first type terminal when the first LCID cannot be used.
  • RRC signaling is used to send additional indication information, which supports the reporting of the terminal type by the first type terminal when there is no information field for additional indication information in message 3.
  • the first type of terminal is defined as an eRedCap UE in the 5G NR system
  • the second type of terminal is defined as a RedCap UE in the 5G NR system
  • the third type of terminal is defined as a normal terminal in the 5G NR system.
  • eRedCap UE reports the terminal type in the following two ways:
  • the eRedCap UE uses the first LCID to indicate the terminal type in message 3 during the random access process.
  • the first LCID is different from the second LCID of the RedCap UE and the third LCID of the normal terminal.
  • eRedCap UE always uses the first LCID to indicate the terminal type.
  • the eRedCap UE may determine whether to use the first LCID according to the configuration of the network device. In the case where the network device does not configure the first LCID for the eRedCap UE, the eRedCap UE uses the second LCID and additional indication information to indicate the terminal type. Among them, the second LCID is used as the LCID shared by eRedCap UE and RedCap UE.
  • the eRedCap UE uses the second LCID in message 3; after completing the random access, the eRedCap UE sends additional indication information through RRC, indicating the eRedCap UE through the second LCID and the additional indication information, or indicating the eRedCap UE through the additional indication information. .
  • the eRedCap UE uses the second LCID and additional indication information to indicate the terminal type in message 3 during the random access process; where the second LCID is the LCID shared by the eRedCap UE and the RedCap UE.
  • eRedCap UE uses the MAC CE information field other than the information field where the second LCID is located to carry additional indication information.
  • eRedCap UE always uses the above MAC CE information field to carry additional indication information.
  • the eRedCap UE can determine whether to use the above-mentioned MAC CE information field to carry additional indication information according to the configuration of the network device.
  • the eRedCap UE uses the second LCID in message 3; after completing the random access, the eRedCap UE sends the additional indication information through RRC, using the second LCID and additional indication information to indicate the eRedCap UE, or additional indication information to indicate the eRedCap UE.
  • the message sending method provided in this embodiment can indicate the eRedCap UE through the first LCID, or the second LCID and additional indication information, and supports the reporting of the terminal type by the eRedCap UE.
  • Figure 13 shows a block diagram of a message sending device provided by an exemplary embodiment of the present disclosure.
  • the device can be implemented as part or all of the terminal through software, hardware, or a combination of the two.
  • the device includes:
  • the first sending module 1301 is configured to send message 3 in the random access process to the network device, where the message 3 carries type information indicating the first type of terminal;
  • the type information of the first type terminal is different from the type information of the second type terminal and the type information of the third type terminal, and the terminal capabilities of the second type terminal and the third type terminal are both greater than the Terminal capabilities of the first type of terminal.
  • the type information of the first type terminal includes a first LCID
  • the first LCID of the first type terminal is different from the second LCID of the second type terminal and the third LCID of the third type terminal.
  • the first LCID is carried in the LCID information field of message 3.
  • the first LCID is used to indicate an eRedCap UE
  • the second LCID is used to indicate a RedCap UE
  • the third LCID is used to indicate a normal UE.
  • the first LCID is type information configured by the network device for the first type terminal; or, the first LCID is type information of the first type terminal predefined by the protocol. .
  • the device further includes:
  • the first receiving module 502 is configured to receive a system message sent by the network device before sending message 3 in the random access process to the network device, where the system message carries the first LCID.
  • the type information of the first type terminal includes a second LCID and additional indication information
  • the second LCID is an LCID shared by the first type terminal and the second type terminal; the combination of the additional indication information and the second LCID is used to indicate the first type terminal, or, The additional indication information is used to indicate the first type terminal.
  • the second LCID is carried in the LCID information field of the message 3
  • the additional indication information is carried in the information field of the message 3 except the LCID information field.
  • the additional indication information is carried in the MACCE information field in the message 3.
  • the type information of the first type terminal includes a second LCID; the second LCID is an LCID shared by the first type terminal and the second type terminal;
  • the first sending module 1301 is configured to send RRC signaling to the network device after the random access is completed, where the RRC signaling carries additional indication information;
  • the combination of the additional indication information and the second LCID is used to indicate the first type terminal, or the additional indication information is used to indicate the first type terminal.
  • Figure 14 shows a block diagram of a message receiving device provided by an exemplary embodiment of the present disclosure.
  • the device can be implemented as part or all of the network equipment through software, hardware, or a combination of the two.
  • the device includes:
  • the second receiving module 1401 is configured to receive message 3 sent by the terminal during the random access process
  • the second processing module 1402 is configured to determine that the terminal is the first type terminal based on the type information of the first type terminal carried in the message 3;
  • the type information of the first type terminal is different from the type information of the second type terminal and the type information of the third type terminal, and the terminal capabilities of the second type terminal and the third type terminal are both greater than the Terminal capabilities of the first type of terminal.
  • the type information of the first type terminal includes a first LCID
  • the first LCID of the first type terminal is different from the second LCID of the second type terminal and the third LCID of the third type terminal.
  • the first LCID is carried in the LCID information field of message 3.
  • the first LCID is used to indicate an eRedCap UE
  • the second LCID is used to indicate a RedCap UE
  • the third LCID is used to indicate a normal UE.
  • the first LCID is type information of the first type terminal predefined by the protocol.
  • the device includes:
  • the second sending module 1403 is configured to send the first LCID to the first type terminal.
  • the second sending module 1403 is configured to send a system message to the first type terminal, where the system message carries the first LCID.
  • the type information of the first type terminal includes a second LCID and additional indication information
  • the second LCID is an LCID shared by the first type terminal and the second type terminal; the combination of the additional indication information and the second LCID is used to indicate the first type terminal, or, The additional indication information is used to indicate the first type terminal.
  • the second LCID is carried in the LCID information field of the message 3
  • the additional indication information is carried in the information field of the message 3 except the LCID information field.
  • the additional indication information is carried in the MACCE information field in the message 3.
  • the type information of the first type terminal includes a second LCID; the second LCID is an LCID shared by the first type terminal and the second type terminal;
  • the second receiving module 1401 is configured to receive RRC signaling sent by the terminal after the random access is completed, where the RRC signaling carries additional indication information;
  • the second processing module 1402 is configured to determine that the terminal is the first type terminal based on a combination of the additional indication information and the second LCID.
  • the type information of the first type terminal includes a second LCID; the second LCID is an LCID shared by the first type terminal and the second type terminal;
  • the second receiving module 1401 is configured to receive RRC signaling sent by the terminal after the random access is completed, where the RRC signaling carries additional indication information;
  • the second processing module 1402 is configured to determine that the terminal is the first type terminal based on the additional indication information.
  • Figure 15 shows a schematic structural diagram of a UE provided by an exemplary embodiment of the present disclosure.
  • the UE includes: a processor 1501, a receiver 1502, a transmitter 1503, a memory 1504 and a bus 1505.
  • the processor 1501 includes one or more processing cores.
  • the processor 1501 executes various functional applications and information processing by running software programs and modules.
  • the receiver 1502 and the transmitter 1503 can be implemented as a communication component, and the communication component can be a communication chip.
  • Memory 1504 is connected to processor 1501 through bus 1505.
  • the memory 1504 can be used to store at least one instruction, and the processor 1501 is used to execute the at least one instruction to implement each step in the above method embodiment.
  • memory 1504 may be implemented by any type of volatile or non-volatile storage device, or combination thereof, including but not limited to: magnetic or optical disks, electrically erasable programmable Read-only memory (EEPROM, Electrically Erasable Programmable Read Only Memory), Erasable Programmable Read-Only Memory (EPROM, Erasable Programmable Read Only Memory), Static Random-Access Memory (SRAM, Static Random-Access Memory), Read-Only Memory (ROM, Read Only Memory), magnetic memory, flash memory, programmable read-only memory (PROM, Programmable Read Only Memory).
  • EEPROM Electrically Erasable Programmable Read Only Memory
  • EPROM Erasable Programmable Read Only Memory
  • SRAM Static Random-Access Memory
  • ROM Read-Only Memory
  • magnetic memory flash memory
  • PROM programmable read-only memory
  • a non-transitory computer-readable storage medium including instructions such as a memory including instructions, is also provided, and the above instructions can be executed by a processor of the UE to complete the above message sending method.
  • the non-transitory computer-readable storage medium may be ROM, random access memory (RAM, Random-Access Memory), compact disc read-only memory (CD-ROM, Compact Disc-Read Only Memory), magnetic tape, Floppy disks and optical data storage devices, etc.
  • a non-transitory computer-readable storage medium enables the UE to perform the above message sending method when instructions in the non-transitory computer storage medium are executed by a processor of the UE.
  • Figure 16 is a block diagram of a network device 1600 according to an exemplary embodiment.
  • the network device 1600 may be a base station.
  • Network device 1600 may include: processor 1601, receiver 1602, transmitter 1603, and memory 1604.
  • the receiver 1602, the transmitter 1603 and the memory 1604 are respectively connected to the processor 1601 through a bus.
  • the processor 1601 includes one or more processing cores, and the processor 1601 executes the message receiving method provided by the embodiment of the present disclosure by running software programs and modules.
  • Memory 1604 may be used to store software programs and modules. Specifically, the memory 1604 can store the operating system 16041 and at least one application module 16042 required for the function.
  • the receiver 1602 is used to receive communication data sent by other devices, and the transmitter 1603 is used to send communication data to other devices.
  • An exemplary embodiment of the present disclosure also provides a computer-readable storage medium.
  • the computer-readable storage medium stores at least one instruction, at least a program, a code set or an instruction set.
  • the at least one instruction, the At least a section of the program, the code set or the instruction set is loaded and executed by the processor to implement the message sending method or the message receiving method provided by each of the above method embodiments.
  • An exemplary embodiment of the present disclosure also provides a computer program product, the computer program product includes computer instructions, the computer instructions are stored in a computer-readable storage medium; the processor of the computer device reads from the computer-readable storage medium The computer instructions are read from the medium, and the processor executes the computer instructions, so that the computer device performs the message sending method or the message receiving method as provided in each of the above method embodiments.
  • first, second, etc. are used to describe various information, but this information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other and do not imply a specific order or importance. In fact, expressions such as “first” and “second” can be used interchangeably.
  • first message frame may also be called a second message frame, and similarly, the second message frame may also be called a first message frame.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本公开公开了一种消息发送方法、消息接收方法、装置、设备及存储介质，属于通信领域。该方法包括：向网络设备发送随机接入过程中的消息3，消息3携带有用于指示第一类型终端的类型信息；其中，第一类型终端的类型信息与第二类型终端的类型信息、第三类型终端的类型信息均不同，第二类型终端与第三类型终端的终端能力均大于第一类型终端的终端能力。该方法用于支持第一类型终端对终端类型的上报。

Description

消息发送方法、消息接收方法、装置、设备及存储介质 技术领域
本公开涉及通信领域，特别涉及一种消息发送方法、消息接收方法、装置、设备及存储介质。
背景技术
在长期演进(Long Term Evolution，LTE)系统中，为了支持物联网业务，提出了机器类型通信(Machine-Type Communication，MTC)和窄带物联网(Narrow Band-Internet of Things，NB-IoT)两大技术，这两大技术主要是针对低速率、高时延的应用场景，比如抄表、环境监测等场景。
上述NB-IoT技术最大支持几百kB的速率，上述MTC技术最大支持几MB的速率。随着物联网业务的发展，出现了一些业务，比如智能家居、可穿戴设备和工业传感测量等业务，这些业务通常要求几十到100MB的速率，上述NB-IoT和MTC两大技术已经无法满足这些业务的需求。
因此，在5G新空口(New Radio，NR)中提出了一种新型用户终端(User Equipment，UE)，以覆盖支持上述这些业务的物联网设备的需求。在第三代合作伙伴计划(third Generation Partnership Project，3GPP)的R17版本中引入了轻量化终端(Reduced Capability UE，RedCap UE)这一终端类型，且针对RedCap UE引入了提前指示(earlyindication)机制，这一机制是在随机接入过程中上报终端类型、以及终端能力的机制。
发明内容
本公开实施例提供了一种消息发送方法、消息接收方法、装置、设备及存储介质。所述技术方案如下：
根据本公开实施例的一个方面，提供了一种消息发送方法，所述方法由第一类型终端执行，所述方法包括：
向网络设备发送随机接入过程中的消息3，所述消息3携带有用于指示所述第一类型终端的类型信息；
其中，所述第一类型终端的类型信息与第二类型终端的类型信息、第三类 型终端的类型信息均不同，所述第二类型终端与所述第三类型终端的终端能力均大于所述第一类型终端的终端能力。
根据本公开实施例的另一方面，提供了一种消息接收方法，所述方法由网络设备执行，所述方法包括：
接收终端发送的随机接入过程中的消息3；
基于所述消息3携带的第一类型终端的类型信息，确定所述终端为所述第一类型终端；
其中，所述第一类型终端的类型信息与第二类型终端的类型信息、第三类型终端的类型信息均不同，所述第二类型终端与所述第三类型终端的终端能力均大于所述第一类型终端的终端能力。
根据本公开实施例的另一方面，提供了一种消息发送装置，所述装置包括：
发送模块，被配置为向网络设备发送随机接入过程中的消息3，所述消息3携带有用于指示第一类型终端的类型信息；
其中，所述第一类型终端的类型信息与第二类型终端的类型信息、第三类型终端的类型信息均不同，所述第二类型终端与所述第三类型终端的终端能力均大于所述第一类型终端的终端能力。
根据本公开实施例的另一方面，提供了一种消息接收装置，所述装置包括：
第二接收模块，被配置为接收终端发送的随机接入过程中的消息3；
第二处理模块，被配置为基于所述消息3携带的第一类型终端的类型信息，确定所述终端为所述第一类型终端；
其中，所述第一类型终端的类型信息与第二类型终端的类型信息、第三类型终端的类型信息均不同，所述第二类型终端与所述第三类型终端的终端能力均大于所述第一类型终端的终端能力。
根据本公开实施例的另一方面，提供了一种终端，所述终端包括：
处理器；
与所述处理器相连的收发器；
其中，所述处理器被配置执行可执行指令以实现如上各个方面所述的消息发送方法。
根据本公开实施例的另一方面，提供了一种网络设备，所述网络设备包括：
处理器；
与所述处理器相连的收发器；
其中，所述处理器被配置执行可执行指令以实现如上各个方面所述的消息 接收方法。
根据本公开实施例的另一方面，提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有至少一条指令、至少一段程序、代码集或指令集，所述至少一条指令、所述至少一段程序、所述代码集或指令集由处理器加载并执行以实现如上述各个方面所述的消息发送方法，或者，如上述各个方面所述的消息接收方法。
根据本公开实施例的另一方面，提供了一种计算机程序产品(或者计算机程序)，所述计算机程序产品(或者计算机程序)包括计算机指令，所述计算机指令存储在计算机可读存储介质中；计算机设备的处理器从所述计算机可读存储介质中读取所述计算机指令，所述处理器执行所述计算机指令，使得所述计算机设备执行如上各个方面所述的消息发送方法，或者，如上述各个方面所述的消息接收方法。
根据本公开实施例的另一方面，提供了一种芯片，所述芯片包括可编辑逻辑电路和/或程序指令，当所述芯片运行时，用于实现如上各个方面所述的消息发送方法，或者，如上述各个方面所述的消息接收方法。
本公开实施例提供的技术方案可以包括以下有益效果：
在上述消息发送方法中，第一类型终端是终端能力小于第二类型终端与第三类型终端的终端能力的一类终端；第一类型终端向网络设备发送随机接入过程中的消息3时，可以在消息3中携带第一类型终端的类型信息，且第一类型终端的类型信息与第二类型终端的类型信息均不同，也即可以使用专属于第一类型终端的类型消息，实现随机接入过程中第一类型终端的终端类型上报。示例性的，eRedCap UE可以使用专属于自身的类型信息进行终端类型上报，也即该方法支持eRedCap UE对自身的终端类型的上报。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限制本公开。
附图说明
为了更清楚地说明本公开实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本公开的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是根据一示例性实施例示出的通信系统的示意图；
图2是根据一示例性实施例示出的消息发送方法的流程图；
图3是根据一示例性实施例示出的UL MAC PDU的结构示意图；
图4是根据一示例性实施例示出的MAC子头部的结构示意图；
图5是根据另一示例性实施例示出的MAC子头部的结构示意图；
图6是根据另一示例性实施例示出的消息发送方法的流程图；
图7是根据另一示例性实施例示出的消息发送方法的流程图；
图8是根据另一示例性实施例示出的消息发送方法的流程图；
图9是根据一示例性实施例示出的消息接收方法的流程图；
图10是根据另一示例性实施例示出的消息接收方法的流程图；
图11是根据另一示例性实施例示出的消息接收方法的流程图；
图12是根据另一示例性实施例示出的消息接收方法的流程图；
图13是根据一示例性实施例示出的消息发送装置的框图；
图14是根据一示例性实施例示出的消息接收装置的框图；
图15是根据一示例性实施例示出的终端的结构示意图；
图16是根据一示例性实施例示出的网络设备的结构示意图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本公开相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本公开的一些方面相一致的装置和方法的例子。
在LTE系统中，为了支持物联网业务，提出了MTC和NB-IoT两大技术，这两大技术主要是针对低速率、高时延的应用场景，比如抄表、环境监测等场景。
上述NB-IoT技术最大支持几百kB的速率，上述MTC技术最大支持几MB的速率。随着物联网业务的发展，出现了一些业务，比如智能家居、可穿戴设备和工业传感测量等业务，这些业务通常要求几十到100MB的速率，上述NB-IoT和MTC两大技术已经无法满足这些业务的需求。
目前，在第三代合作伙伴计划(third Generation Partnership Project，3GPP)中提出了一种新型用户终端(User Equipment，UE)，以覆盖支持上述这些业务 的物联网设备的需求。在3GPP的R17版本中引入了轻量化终端(Reduced Capability UE，RedCap UE)这一终端类型，且针对RedCap UE引入了提前指示(earlyindication)机制，这一机制是在随机接入过程中上报终端类型、以及终端能力的机制。比如，终端在随机接入过程中通过消息1(Message 1，Msg.1)、或者消息A(Message A，Msg.A)、或者消息3(Message 3，Msg.3)来进行终端类型的指示。
针对5G新空口(New Radio，NR)，还在3GPP的R18中引入了增强型轻量级终端(enhanced Reduced Capability UE，eRedCap UE)这一终端类型。其中，eRedCap UE相对于RedCap UE进一步缩减了终端带宽，例如，在随机接入频率范围1(Frequency Range 1，FR1)下，eRedCap UE的终端带宽从20MHz缩减至5MHz；另外，eRedCap UE相对于RedCap UE还进一步降低了终端的数据处理时间和峰值速率等。因此，RedCap UE的earlyindication机制并不适用于eRedCap UE。所以，为了解决上报eRedCap UE的终端类型这一技术问题，本申请提供了消息发送方法和消息接收方法，如下实施例所示。
图1示出了本公开一个示例性实施例提供的通信系统的框图，该通信系统可以包括：接入网12和用户终端14。
接入网12中包括若干个网络设备120。网络设备(又称接入网设备)120可以是基站，所述基站是一种部署在接入网中用以为用户终端(简称为“终端”)14提供无线通信功能的装置。基站可以包括各种形式的宏基站，微基站，中继站，接入点等等。在采用不同的无线接入技术的系统中，具备基站功能的设备的名称可能会有所不同，例如在LTE系统中，称为eNodeB或者eNB；在5G NR系统中，称为gNodeB或者gNB。随着通信技术的演进，“基站”这一描述可能会变化。为方便本公开实施例中的描述，上述为用户终端14提供无线通信功能的装置统称为网络设备。
用户终端14可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其他处理设备，以及各种形式的用户设备，移动台(Mobile Station，MS)，终端设备(terminal device)等等。为方便描述，上面提到的设备统称为用户终端。网络设备120与用户终端14之间通过某种空口技术互相通信，例如Uu接口。
示例性的，网络设备120与用户终端14之间存在两种通信场景：上行通信场景与下行通信场景。其中，上行通信是指向网络设备120发送信号；下行通 信是指向用户终端14发送信号。
示例性的，用户终端14在随机接入过程中向网络设备120上报自身的终端类型。其中，上述用户终端14可以是第一类型终端、或者第二类型终端、或者第三类型终端；第一类型终端、第二类型终端和第三类型终端是不同终端能力对应的三种类型终端。
本公开实施例的技术方案可以应用于各种通信系统，例如：全球移动通讯(Global System of Mobile Communication，GSM)系统、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)系统、LTE频分双工(Frequency Division Duplex，FDD)系统、LTE时分双工(Time Division Duplex，TDD)系统、先进的长期演进(Advanced Long Term Evolution，LTE-A)系统、新无线(New Radio，NR)系统、NR系统的演进系统、非授权频段上的LTE(LTE-based access to Unlicensed spectrum，LTE-U)系统、NR-U系统、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、全球互联微波接入(Worldwide Interoperability for Microwave Access，WiMAX)通信系统、无线局域网(Wireless Local Area Networks，WLAN)、无线保真(Wireless Fidelity，WiFi)、下一代通信系统或其他通信系统等。
通常来说，传统的通信系统支持的连接数有限，也易于实现，然而，随着通信技术的发展，移动通信系统将不仅支持传统的通信，还将支持例如，设备到设备(Device to Device，D2D)通信，机器到机器(Machine to Machine，M2M)通信，机器类型通信(Machine Type Communication，MTC)，车辆间(Vehicle to Vehicle，V2V)通信以及车联网(Vehicle to Everything，V2X)系统等。本公开实施例也可以应用于这些通信系统。
图2示出了本公开一个示例性实施例提供的消息发送方法的流程图，该方法应用于图1所示的通信系统中，由第一类型终端执行，该方法包括：
步骤201，向网络设备发送随机接入过程中的消息3，消息3携带有用于指示第一类型终端的类型信息。
其中，第一类型终端的类型信息与第二类型终端的类型信息、第三类型终端的类型信息均不同，第二类型终端与第三类型终端的终端能力均大于第一类型终端的终端能力。
示例性的，第二类型终端的终端能力还小于第三类型终端的终端能力。
示例性的，终端能力包括终端带宽(Band Width)，第一类型终端支持的终端带宽小于第二类型终端和第三类型终端支持的终端带宽。第二类型终端的终端带宽还小于第三类型终端支持的终端带宽。
可选地，第一类型终端为eRedCap UE，第二类型终端为RedCap UE，第三类型终端为正常终端。正常终端是5G NR系统中定义的终端，其包括5G NR系统中除eRedCap UE和RedCap UE之外的其它终端。
示例性的，终端能力还包括终端的峰值速率(包括上行峰值速率和下行峰值速率)、移动性、时延、支持频段中的至少一项。
可选地，终端的类型信息包括逻辑信道标识(Logical Channel IDentifier，LCID)。示例性的，第一类型终端的类型信息包括第一LCID，第二类型终端的类型信息包括第二LCID，第三类型终端的类型信息包括第三LCID；第一LCID与第二LCID、第三LCID均不同，且第二LCID与第三LCID也不同。
示例性的，第一LCID用于指示eRedCap UE，第二LCID用于指示RedCap UE，第三LCID用于指示正常终端。
消息3中包括LCID信息域，LCID信息域用于指示终端类型；比如，在LCID信息域上承载第一LCID、或者第二LCID、或者第三LCID。在第一类型终端发送消息3的情况下，第一LCID承载在消息3的LCID信息域。示例性的，第一类型终端将第一LCID映射至消息3中的LCID信息域上，向网络设备发送消息3。
消息3包含了公共控制信道(Common Control Channel，CCCH)服务数据单元(Service Data Unit，SDU)，其中，CCCH SDU是包含在媒体访问控制(Media Access Control，MAC)SDU内，每个MAC SDU对应有MAC子头部(subheader)，MAC subheader中包含LCID信息域。
示例性的，如图3所示，其示出了一个示例性实施例提供的一个UL MAC PDU 300，UL是指上行(UpLink)，PDU是指协议数据单元(Protocol Data Unit)。一个UL MAC PDU 300是由一个或多个MACsubPDU301组成的，subPDU是子协议数据单元。MAC subPDU301包括：MAC subPDU3011包括MAC subheader和MAC SDU；MAC subPDU3012包括MAC subheader和MAC控制单元(Control Element，CE)；MAC subPDU3013包括MAC subheader和填充(padding)。一个UL MAC PDU可以存在MAC subPDU3013，也可以不存在MAC subPDU3013。
示例性的，如图4所示，其示出了一个示例性实施例提供的一个MAC  subheader400的结构示意图，MAC subheader400包括R/F/LCID/L。如图5所示，其示出了另一个示例性实施例提供的一个MACsubheader500的结构示意图，MACsubheader 500包括R/LCID。其中，R是保留比特；F用于指示L字段的长度；L用于指示相应的MAC SDU或MAC CE的长度，以字节为单位；LCID是指逻辑信道标识，LCID用于指示MAC SDU对应的逻辑信道实例。
示例性的，如表1所示，上行共享信道(UpLink-Shared Channel，UL-SCH)中的LCID取值(LCID values)为保留值(Reserved)，Reserved的索引(Index)范围为：33-51，二进制表示为100001-110011。比如，第一LCID的索引可以是33-51中的任意一个值。
表1
Index LCID values
33-51 Reserved
综上所述，本实施例提供的消息发送方法，第一类型终端是终端能力小于第二类型终端与第三类型终端的终端能力的一类终端；第一类型终端向网络设备发送随机接入过程中的消息3时，可以在消息3中携带第一类型终端的类型信息，且第一类型终端的类型信息与第二类型终端的类型信息均不同，也即可以使用专属于第一类型终端的类型消息，实现随机接入过程中第一类型终端的终端类型上报。比如，eRedCap UE可以使用专属于第一LCID进行终端类型上报。
在一些实施例中，终端的类型信息是协议预定义的；比如，3GPP协议中预定义了第一类型终端的类型信息、第二类型终端的类型信息、以及第三类型终端的类型信息。可选地，第一LCID是协议预定义的第一类型终端的类型信息；第二LCID是协议预定义的第二类型终端的类型信息；第三LCID是协议预定义的第三类型终端的类型信息。
示例性的，在随机接入过程中，第一类型终端向网络设备发送携带有第一LCID的消息3；第二类型终端向网络设备发送携带有第二LCID的消息3；第三类型终端向网络设备发送携带有第三LCID的消息3。
在另一些实施例中，终端的类型信息是由网络设备为终端配置的；比如，第一LCID是由网络设备为第一类型终端配置的类型信息。如图6所示，第一类型终端在发送消息3之前，执行步骤202，如下所示：
步骤202，接收网络设备发送的类型信息。
示例性的，第一类型终端接收网络设备发送的第一类型终端的类型信息；比如，eRedCap UE接收网络设备配置的第一LCID。
在另一些实施例中，第二类型终端接收网络设备发送的第二类型终端的类型信息，比如，RedCap UE接收网络设备配置的第二LCID；第三类型终端接收网络设备发送的第三类型终端的类型信息，比如，正常终端接收网络设备配置的第三LCID。
可选地，上述类型信息携带在系统消息中。示例性的，第一类型终端接收网络设备发送的系统消息，系统消息携带有第一类型终端的类型信息；比如，系统消息携带有第一LCID。
示例性的，第一类型终端还可以在随机接入之前，接收网络设备发送的类型信息。比如，第一类型终端在随机接入之前，接收网络设备发送的系统消息，从系统消息中获得第一类型终端的类型信息。
综上所述，本实施例提供的消息发送方法，可以由网络设备为第一类型终端配置专属于自身的类型信息，从而支持第一类型终端的终端类型上报。
存在一种情况，网络设备未配置第一类型终端的类型信息，则第一类型终端可以采用第一类型终端和第二类型终端共用的类型信息，结合附加指示信息来上报终端为第一类型终端。示例性的，如图7所示，图2中的步骤201可以包括步骤701，如下所示：
步骤701，向网络设备发送随机接入过程中的消息3，消息3携带有第二LCID和附加指示信息。
第二LCID是第一类型终端与第二类型终端共用的LCID，附加指示信息和第二LCID的组合用于指示第一类型终端；或者，附加指示信息用于指示第一类型终端。比如，附加指示信息和第二LCID的组合用于指示eRedCap UE；或者，附加指示信息用于指示eRedCap UE。示例性的，第二LCID的索引为X，附加指示信息的索引为Y，二者的组合X+Y则用于指示eRedCap UE。
可选地，第二LCID可以是由协议预定义的；或者，第二LCID可以是由网络设备为第一类型终端和第二类型终端配置的。
可选地，附加指示信息可以是由协议预定义的；或者，附加指示信息可以是由网络设备为第一类型终端配置的。
可选地，第二LCID承载在消息3的LCID信息域，附加指示信息承载在消息3除LCID信息域之外的信息域。示例性的，附加指示信息承载在消息3中的 MAC CE信息域。
可选地，消息3中用于承载附加指示信息的信息域，是由协议预定义的；或者，是由网络设备为第一类型终端配置的。比如，消息3中用于承载附加指示信息的MAC CE信息域，是由协议预定义的；或者，是由网络设备为第一类型终端配置的。
在一些实施例中，在消息3中携带第二LCID、且不携带附加指示信息的情况下，第二LCID用于指示第二类型终端，比如，第二LCID用于指示RedCap UE。
综上所述，本实施例提供的消息发送方法，第一类型终端和第二类型终端共用第二LCID，通过第二LCID和附加指示信息的组合来指示第一类型终端，或者通过附加指示信息来指示第一类型终端，支持第一类型终端在无法使用第一LCID的情况下的终端类型上报。且本实施例中通过消息3携带附加指示信息，支持消息3中存在附加指示信息的信息域的情况下，第一类型终端对终端类型的上报，无需再通过其它信令进行终端类型的上报，能够节省信令开销。
上述图7示出的实施例中在消息3中携带附加指示信息，还存在另一种情况，消息3中还可能不存在携带附加指示信息的信息域，则图2中的步骤201可以包括步骤801至步骤802，如图8所示，步骤如下：
步骤801，向网络设备发送随机接入过程中的消息3，消息3携带有第二LCID。
上述第二LCID是第一类型终端和第二类型终端共用的LCID。可选地，第二LCID可以是由协议预定义的；或者，第二LCID可以是由网络设备为第一类型终端和第二类型终端配置的。
可选地，第二LCID承载在消息3的LCID信息域。示例性的，如图3至5所示，LCID信息域是MACsubheader中的信息域。
第一类型终端在LCID信息域上映射第二LCID，向网络设备发送携带有第二LCID的消息3。
步骤802，在随机接入完成之后，向网络设备发送无线资源控制(Radio Resource Control，RRC)信令，RRC信令携带有附加指示信息。
可选地，附加指示信息可以是由协议预定义的；或者，附加指示信息可以是由网络设备为第一类型终端配置的。
第一类型终端响应于消息3中不存在附加指示信息的信息域，在随机接入完成之后，向网络设备发送RRC信令。
也即，第一类型终端在消息3中不存在附加指示信息的信息域的情况下，发送携带有第二LCID的消息3；在完成随机接入之后，再通过RRC信令向网络设备发送附加指示信息。
可选地，附加指示信息和第二LCID的组合用于指示第一类型终端；或者，附加指示信息用于指示第一类型终端。比如，附加指示信息和第二LCID的组合用于指示eRedCap UE；或者，附加指示信息用于指示eRedCap UE。示例性的，附加指示信息的索引为Z，Z即用于指示eRedCap UE。
综上所述，本实施例提供的消息发送方法，第一类型终端和第二类型终端共用第二LCID，通过第二LCID和附加指示信息的组合来指示第一类型终端，或者通过附加指示信息来指示第一类型终端，支持第一类型终端在无法使用第一LCID的情况下的终端类型上报。且本实施例中采用RRC信令发送附加指示信息，支持消息3中不存在附加指示信息的信息域的情况下，第一类型终端对终端类型的上报。
图9示出了本公开一个示例性实施例提供的消息接收方法的流程图，该方法应用于图1所示的通信系统中，由网络设备执行，该方法包括：
步骤901，接收终端发送的随机接入过程中的消息3。
上述消息3中携带有终端的类型信息。比如，消息3中可以携带有第一类型终端的类型信息，或者第二类型终端的类型信息，或者第三类型终端的类型信息。
其中，第一类型终端的类型信息与第二类型终端的类型信息、第三类型终端的类型信息均不同，第二类型终端与第三类型终端的终端能力均大于第一类型终端的终端能力。示例性的，第二类型终端的终端能力还小于第三类型终端的终端能力。
示例性的，终端能力包括终端带宽，第一类型终端支持的终端带宽小于第二类型终端和第三类型终端支持的终端带宽。第二类型终端的终端带宽还小于第三类型终端支持的终端带宽。示例性的，终端能力还包括终端的峰值速率、移动性、时延、支持频段中的至少一项。
可选地，第一类型终端为eRedCap UE，第二类型终端为RedCap UE，第三类型终端为正常终端。正常终端是5G NR系统中定义的终端，其包括5G NR系统中除eRedCap UE和RedCap UE之外的其它终端。
可选地，终端的类型信息包括LCID。示例性的，第一类型终端的类型信息 包括第一LCID，第二类型终端的类型信息包括第二LCID，第三类型终端的类型信息包括第三LCID；第一LCID与第二LCID、第三LCID均不同，且第二LCID与第三LCID也不同。示例性的，第一LCID用于指示eRedCap UE，第二LCID用于指示RedCap UE，第三LCID用于指示正常终端。
消息3中包括LCID信息域，LCID信息域用于指示终端类型。第一LCID承载在消息3的LCID信息域，则网络设备在消息3中的LCID信息域读取到第一LCID。在另一些实施例中，第二LCID承载在消息3的LCID信息域，则网络设备在消息3中的LCID信息域读取到第二LCID；或者，第三LCID承载在消息3的LCID信息域，则网络设备在消息3中的LCID信息域读取到第三LCID。
步骤902，基于消息3携带的第一类型终端的类型信息，确定终端为第一类型终端。
示例性的，网络设备基于消息3携带的第一LCID，确定终端为第一类型终端。也即，网络设备基于第一LCID确定接收到的是第一类型终端的消息3。
在另一些实施例中，在消息3中携带的是第二LCID，确定终端为第二类型终端；或者，在消息3中携带的是第三LCID，确定终端为第三类型终端。
综上所述，本实施例提供的消息接收方法，第一类型终端是终端能力小于第二类型终端与第三类型终端的终端能力的一类终端；网络设备接收终端发送随机接入过程中的消息3，在消息3中携带第一类型终端的类型信息的情况下，可以确定发送消息3的终端是第一类型终端，其中，第一类型终端的类型信息与第二类型终端的类型信息均不同，也即可以使用专属于第一类型终端的类型消息，实现随机接入过程中第一类型终端的终端类型上报。
在一些实施例中，终端的类型信息是协议预定义的；比如，第一LCID是协议预定义的第一类型终端的类型信息。在另一些实施例中，终端的类型信息是由网络设备为终端配置的，如图10所示，网络设备在接收消息3之前，执行如下步骤：
步骤1001，向第一类型终端发送第一类型终端的类型信息。
示例性的，网络设备为eRedCap UE配置第一LCID。在另一些实施例中，网络设备为RedCap UE配置第二LCID，以及为正常终端配置第三LCID。
可选地，网络设备向第一类型终端发送系统消息，系统消息携带有第一类型终端的类型信息；比如，系统消息携带有第一LCID。
示例性的，网络设备在随机接入之前，向终端发送终端的类型信息。比如， 网络设备在随机接入之前，向第一类型终端发送第一类型终端的类型信息。
综上所述，本实施例提供的消息接收方法，网络设备为第一类型终端配置专属于自身的类型信息，从而支持第一类型终端的终端类型上报。
存在一种情况，网络设备未配置第一类型终端的类型信息，且配置了第一类型终端和第二类型终端共用的类型信息，结合附加指示信息来完成终端类型的上报。示例性的，如图11所示，图9中的步骤902可以包括步骤1102，如下所示：
步骤1102，基于消息3携带的第二LCID和附加指示信息，确定终端为第一类型终端。
也即，第一类型终端的类型信息包括第二LCID和附加指示信息；第二LCID是第一类型终端和第二类型终端共用的LCID；附加指示信息和第二LCID的组合用于指示第一类型终端；或者，附加指示信息用于指示第一类型终端。
可选地，第二LCID可以是由协议预定义的；或者，第二LCID可以是由网络设备为第一类型终端和第二类型终端配置的。
可选地，附加指示信息可以是由协议预定义的；或者，附加指示信息可以是由网络设备为第一类型终端配置的。
可选地，第二LCID承载在消息3的LCID信息域，附加指示信息承载在消息3除LCID信息域之外的信息域。示例性的，附加指示信息承载在消息3中的MAC CE信息域。
可选地，消息3中用于承载附加指示信息的信息域，是由协议预定义的；或者，是由网络设备为第一类型终端配置的。比如，消息3中用于承载附加指示信息的MAC CE信息域，是由协议预定义的；或者，是由网络设备为第一类型终端配置的。
示例性的，网络设备从消息3中的LCID信息域读取第二LCID，以及从消息3中的MAC CE信息域读取附加指示信息；之后，基于第二LCID和附加指示信息确定终端为eRedCap UE。
在一些实施例中，在消息3中携带第二LCID、且不携带附加指示信息的情况下，网络设备确定终端为第二类型终端。
综上所述，本实施例提供的消息接收方法，第一类型终端和第二类型终端共用第二LCID，通过第二LCID和附加指示信息的组合来指示第一类型终端，或者通过附加指示信息来指示第一类型终端，支持第一类型终端在无法使用第 一LCID的情况下的终端类型上报。且本实施例中通过消息3携带附加指示信息，支持消息3中存在附加指示信息的信息域的情况下，第一类型终端对终端类型的上报，无需再通过其它信令进行终端类型的上报，能够节省信令开销。
还存在一种情况，网络设备未配置第一类型终端的第一LCID，且消息3中不存在携带附加指示信息的信息域，则图9中的的步骤902可以包括步骤1202至步骤1203，如图12所示，步骤如下：
步骤1202，在随机接入完成之后，接收终端发送的RRC信令，RRC信令携带有附加指示信息。
可选地，附加指示信息可以是由协议预定义的；或者，附加指示信息可以是由网络设备为第一类型终端配置的。
第一类型终端响应于消息3中不存在附加指示信息的信息域，在随机接入完成之后，网络设备会接收到终端发送的RRC信令。
也即，在消息3中不存在附加指示信息的信息域的情况下，网络设备会接收到携带有第二LCID的消息3；在完成随机接入之后，还会接收到携带有附加指示信息的RRC信令。
步骤1203，基于附加指示信息和消息3中携带的第二LCID的组合，确定终端为第一类型终端。
上述第二LCID是第一类型终端和第二类型终端共用的LCID。可选地，第二LCID可以是由协议预定义的；或者，第二LCID可以是由网络设备为第一类型终端和第二类型终端配置的。可选地，第二LCID承载在消息3的LCID信息域；网络设备从LCID信息域读取到第二LCID。
示例性的，附加指示信息和第二LCID的组合用于指示第一类型终端。比如，附加指示信息和第二LCID的组合用于指示eRedCap UE。
在一些实施例中，附加指示信息用于指示第一类型终端；则网络设备还可以基于附加指示信息确定终端为所述第一类型终端。比如，附加指示信息用于指示eRedCap UE。
综上所述，本实施例提供的消息接收方法，第一类型终端和第二类型终端共用第二LCID，通过第二LCID和附加指示信息的组合来指示第一类型终端，或者通过附加指示信息来指示第一类型终端，支持第一类型终端在无法使用第一LCID的情况下的终端类型上报。且本实施例中采用RRC信令发送附加指示信息，支持消息3中不存在附加指示信息的信息域的情况下，第一类型终端对 终端类型的上报。
示例性的，定义第一类型终端为5G NR系统中的eRedCap UE，定义第二类型终端为5G NR系统中的RedCap UE，定义第三类型终端为5G NR系统中的正常终端。
eRedCap UE对终端类型的上报，可以包括如下两种方式：
方式一：
eRedCap UE在随机接入过程中的消息3中使用第一LCID指示终端类型，第一LCID不同于RedCap UE的第二LCID、以及正常终端的第三LCID。
在一种情况下，eRedCap UE始终使用第一LCID指示终端类型。
在另一种情况下，eRedCap UE可以根据网络设备的配置确定是否使用第一LCID。在网络设备未配置第一LCID给eRedCap UE的情况下，eRedCap UE使用第二LCID和附加指示信息指示终端类型。其中，第二LCID作为eRedCap UE与RedCap UE共用的LCID。首先，eRedCap UE在消息3中使用第二LCID；在完成随机接入之后，eRedCap UE通过RRC进行发送附加指示信息，通过第二LCID和附加指示信息指示eRedCap UE，或者通过附加指示信息指示eRedCap UE。
方式二：
eRedCap UE在随机接入过程中的消息3中使用第二LCID和附加指示信息指示终端类型；其中，第二LCID是eRedCap UE与RedCap UE共用的LCID。
比如，eRedCap UE使用除第二LCID所在信息域之外的MAC CE信息域承载附加指示信息。
在一种情况下，eRedCap UE始终使用上述MAC CE信息域承载附加指示信息。
在另一种情况下，eRedCap UE可以根据网络设备的配置确定是否使用上述MAC CE信息域承载附加指示信息。在网络设备未配置用于承载附加指示信息的信息域的情况下，eRedCap UE在消息3中使用第二LCID；在完成随机接入之后，eRedCap UE通过RRC进行发送附加指示信息，通过第二LCID和附加指示信息指示eRedCap UE，或者通过附加指示信息指示eRedCap UE。
综上所述，本实施例提供的消息发送方法，可以通过第一LCID、或者第二LCID和附加指示信息来指示eRedCap UE，支持eRedCap UE对终端类型的上报。
图13示出了本公开一个示例性实施例提供的消息发送装置的框图，该装置可以通过软件、硬件或者二者的结合实现成为终端的一部分或者全部，该装置包括：
第一发送模块1301，被配置为向网络设备发送随机接入过程中的消息3，所述消息3携带有用于指示第一类型终端的类型信息；
其中，所述第一类型终端的类型信息与第二类型终端的类型信息、第三类型终端的类型信息均不同，所述第二类型终端与所述第三类型终端的终端能力均大于所述第一类型终端的终端能力。
在一些实施例中，所述第一类型终端的类型信息包括第一LCID；
其中，所述第一类型终端的第一LCID与所述第二类型终端的第二LCID、所述第三类型终端的第三LCID均不同。
在一些实施例中，所述第一LCID承载在所述消息3的LCID信息域。
在一些实施例中，所述第一LCID用于指示eRedCap UE，所述第二LCID用于指示RedCap UE，所述第三LCID用于指示正常UE。
在一些实施例中，所述第一LCID是由所述网络设备为所述第一类型终端配置的类型信息；或者，所述第一LCID是协议预定义的所述第一类型终端的类型信息。
在一些实施例中，该装置还包括：
第一接收模块502，被配置为向网络设备发送随机接入过程中的消息3之前，接收所述网络设备发送的系统消息，所述系统消息携带有所述第一LCID。
在一些实施例中，所述第一类型终端的类型信息包括第二LCID和附加指示信息；
其中，所述第二LCID是所述第一类型终端和所述第二类型终端共用的LCID；所述附加指示信息和所述第二LCID的组合用于指示所述第一类型终端，或，所述附加指示信息用于指示所述第一类型终端。
在一些实施例中，所述第二LCID承载在所述消息3的LCID信息域，所述附加指示信息承载在所述消息3除所述LCID信息域之外的信息域。
在一些实施例中，所述附加指示信息承载在所述消息3中的MACCE信息域。
在一些实施例中，所述第一类型终端的类型信息包括第二LCID；所述第二LCID是所述第一类型终端和所述第二类型终端共用的LCID；
第一发送模块1301，被配置为在随机接入完成之后，向所述网络设备发送 RRC信令，所述RRC信令携带有附加指示信息；
其中，所述附加指示信息和所述第二LCID的组合用于指示所述第一类型终端，或，所述附加指示信息用于指示所述第一类型终端。
图14示出了本公开一个示例性实施例提供的消息接收装置的框图，该装置可以通过软件、硬件或者二者的结合实现成为网络设备的一部分或者全部，该装置包括：
第二接收模块1401，被配置为接收终端发送的随机接入过程中的消息3；
第二处理模块1402，被配置为基于所述消息3携带的第一类型终端的类型信息，确定所述终端为所述第一类型终端；
其中，所述第一类型终端的类型信息与第二类型终端的类型信息、第三类型终端的类型信息均不同，所述第二类型终端与所述第三类型终端的终端能力均大于所述第一类型终端的终端能力。
在一些实施例中，所述第一类型终端的类型信息包括第一LCID；
其中，所述第一类型终端的第一LCID与所述第二类型终端的第二LCID、所述第三类型终端的第三LCID均不同。
在一些实施例中，所述第一LCID承载在所述消息3的LCID信息域。
在一些实施例中，所述第一LCID用于指示eRedCap UE，所述第二LCID用于指示RedCap UE，所述第三LCID用于指示正常UE。
在一些实施例中，所述第一LCID是协议预定义的所述第一类型终端的类型信息。
在一些实施例中，该装置包括：
第二发送模块1403，被配置为向所述第一类型终端发送所述第一LCID。
在一些实施例中，第二发送模块1403，被配置为向所述第一类型终端发送系统消息，所述系统消息携带有所述第一LCID。
在一些实施例中，所述第一类型终端的类型信息包括第二LCID和附加指示信息；
其中，所述第二LCID是所述第一类型终端和所述第二类型终端共用的LCID；所述附加指示信息和所述第二LCID的组合用于指示所述第一类型终端，或，所述附加指示信息用于指示所述第一类型终端。
在一些实施例中，所述第二LCID承载在所述消息3的LCID信息域，所述附加指示信息承载在所述消息3除所述LCID信息域之外的信息域。
在一些实施例中，所述附加指示信息承载在所述消息3中的MACCE信息域。
在一些实施例中，所述第一类型终端的类型信息包括第二LCID；所述第二LCID是所述第一类型终端和所述第二类型终端共用的LCID；
第二接收模块1401，被配置为在随机接入完成之后，接收所述终端发送的RRC信令，所述RRC信令携带有附加指示信息；
第二处理模块1402，被配置为基于所述附加指示信息和所述第二LCID的组合，确定所述终端为所述第一类型终端。
在一些实施例中，所述第一类型终端的类型信息包括第二LCID；所述第二LCID是所述第一类型终端和所述第二类型终端共用的LCID；
第二接收模块1401，被配置为在随机接入完成之后，接收所述终端发送的RRC信令，所述RRC信令携带有附加指示信息；
第二处理模块1402，被配置为基于所述附加指示信息确定所述终端为所述第一类型终端。
图15示出了本公开一个示例性实施例提供的UE的结构示意图，该UE包括：处理器1501、接收器1502、发射器1503、存储器1504和总线1505。
处理器1501包括一个或者一个以上处理核心，处理器1501通过运行软件程序以及模块，从而执行各种功能应用以及信息处理。
接收器1502和发射器1503可以实现为一个通信组件，该通信组件可以是一块通信芯片。
存储器1504通过总线1505与处理器1501相连。
存储器1504可用于存储至少一个指令，处理器1501用于执行该至少一个指令，以实现上述方法实施例中的各个步骤。
此外，存储器1504可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，易失性或非易失性存储设备包括但不限于：磁盘或光盘，电可擦除可编程只读存储器(EEPROM，Electrically Erasable Programmable Read Only Memory)，可擦除可编程只读存储器(EPROM，Erasable Programmable Read Only Memory)，静态随时存取存储器(SRAM，Static Random-Access Memory)，只读存储器(ROM，Read Only Memory)，磁存储器，快闪存储器，可编程只读存储器(PROM，Programmable Read Only Memory)。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介 质，例如包括指令的存储器，上述指令可由UE的处理器执行以完成上述消息发送方法。例如，所述非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM，Random-Access Memory)、紧凑型光盘只读存储器(CD-ROM，Compact Disc-Read Only Memory)、磁带、软盘和光数据存储设备等。
一种非临时性计算机可读存储介质，当所述非临时性计算机存储介质中的指令由UE的处理器执行时，使得UE能够执行上述消息发送方法。
图16是根据一示例性实施例示出的一种网络设备1600的框图。该网络设备1600可以是基站。
网络设备1600可以包括：处理器1601、接收机1602、发射机1603和存储器1604。接收机1602、发射机1603和存储器1604分别通过总线与处理器1601连接。
其中，处理器1601包括一个或者一个以上处理核心，处理器1601通过运行软件程序以及模块以执行本公开实施例提供的消息接收方法。存储器1604可用于存储软件程序以及模块。具体的，存储器1604可存储操作系统16041、至少一个功能所需的应用程序模块16042。接收机1602用于接收其他设备发送的通信数据，发射机1603用于向其他设备发送通信数据。
本公开一示例性实施例还提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有至少一条指令、至少一段程序、代码集或指令集，所述至少一条指令、所述至少一段程序、所述代码集或指令集由所述处理器加载并执行以实现上述各个方法实施例提供的消息发送方法，或者，消息接收方法。
本公开一示例性实施例还提供了一种计算机程序产品，所述计算机程序产品包括计算机指令，所述计算机指令存储在计算机可读存储介质中；计算机设备的处理器从所述计算机可读存储介质中读取所述计算机指令，所述处理器执行所述计算机指令，使得所述计算机设备执行如上述各个方法实施例提供的消息发送方法，或者，消息接收方法。
应当理解的是，在本文中提及的“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。
进一步可以理解的是，术语“第一”、“第二”等用于描述各种信息，但这些信 息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开，并不表示特定的顺序或者重要程度。实际上，“第一”、“第二”等表述完全可以互换使用。例如，在不脱离本公开范围的情况下，第一消息帧也可以被称为第二消息帧，类似地，第二消息帧也可以被称为第一消息帧。
进一步可以理解的是，本公开实施例中尽管在附图中以特定的顺序描述操作，但是不应将其理解为要求按照所示的特定顺序或是串行顺序来执行这些操作，或是要求执行全部所示的操作。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本公开的其它实施方案。本公开旨在涵盖本公开的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本公开的真正范围和精神由下面的权利要求指出。
应当理解的是，本公开并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本公开的范围仅由所附的权利要求来限制。

Claims (27)

  1. 一种消息发送方法，其特征在于，所述方法由第一类型终端执行，所述方法包括：
    向网络设备发送随机接入过程中的消息3，所述消息3携带有用于指示所述第一类型终端的类型信息；
    其中，所述第一类型终端的类型信息与第二类型终端的类型信息、第三类型终端的类型信息均不同，所述第二类型终端与所述第三类型终端的终端能力均大于所述第一类型终端的终端能力。
  2. 根据权利要求1所述的方法，其特征在于，所述第一类型终端的类型信息包括第一逻辑信道标识LCID；
    其中，所述第一类型终端的第一LCID与所述第二类型终端的第二LCID、所述第三类型终端的第三LCID均不同。
  3. 根据权利要求2所述的方法，其特征在于，所述第一LCID承载在所述消息3的LCID信息域。
  4. 根据权利要求2所述的方法，其特征在于，所述第一LCID用于指示增强型轻量级终端eRedCap UE，所述第二LCID用于指示轻量级终端RedCap UE，所述第三LCID用于指示正常UE。
  5. 根据权利要求2至4任一所述的方法，其特征在于，
    所述第一LCID是由所述网络设备为所述第一类型终端配置的类型信息；或者，
    所述第一LCID是协议预定义的所述第一类型终端的类型信息。
  6. 根据权利要求5所述的方法，其特征在于，所述向网络设备发送随机接入过程中的消息3之前，包括：
    接收所述网络设备发送的系统消息，所述系统消息携带有所述第一LCID。
  7. 根据权利要求1所述的方法，其特征在于，所述第一类型终端的类型信息 包括第二LCID和附加指示信息；
    其中，所述第二LCID是所述第一类型终端和所述第二类型终端共用的LCID；所述附加指示信息和所述第二LCID的组合用于指示所述第一类型终端，或，所述附加指示信息用于指示所述第一类型终端。
  8. 根据权利要求7所述的方法，其特征在于，所述第二LCID承载在所述消息3的LCID信息域，所述附加指示信息承载在所述消息3除所述LCID信息域之外的信息域。
  9. 根据权利要求8所述的方法，其特征在于，所述附加指示信息承载在所述消息3中的媒体访问控制控制单元MACCE信息域。
  10. 根据权利要求1所述的方法，其特征在于，所述第一类型终端的类型信息包括第二LCID；所述第二LCID是所述第一类型终端和所述第二类型终端共用的LCID；
    所述方法还包括：
    在随机接入完成之后，向所述网络设备发送无线资源控制RRC信令，所述RRC信令携带有附加指示信息；
    其中，所述附加指示信息和所述第二LCID的组合用于指示所述第一类型终端，或，所述附加指示信息用于指示所述第一类型终端。
  11. 一种消息接收方法，其特征在于，所述方法由网络设备执行，所述方法包括：
    接收终端发送的随机接入过程中的消息3；
    基于所述消息3携带的第一类型终端的类型信息，确定所述终端为所述第一类型终端；
    其中，所述第一类型终端的类型信息与第二类型终端的类型信息、第三类型终端的类型信息均不同，所述第二类型终端与所述第三类型终端的终端能力均大于所述第一类型终端的终端能力。
  12. 根据权利要求11所述的方法，其特征在于，所述第一类型终端的类型信息包括第一LCID；
    其中，所述第一类型终端的第一LCID与所述第二类型终端的第二LCID、所述第三类型终端的第三LCID均不同。
  13. 根据权利要求12所述的方法，其特征在于，所述第一LCID承载在所述消息3的LCID信息域。
  14. 根据权利要求12所述的方法，其特征在于，所述第一LCID用于指示eRedCap UE，所述第二LCID用于指示RedCap UE，所述第三LCID用于指示正常UE。
  15. 根据权利要求12至14任一所述的方法，其特征在于，所述第一LCID是协议预定义的所述第一类型终端的类型信息。
  16. 根据权利要求12至14任一所述的方法，其特征在于，所述方法还包括：
    向所述第一类型终端发送所述第一LCID。
  17. 根据权利要求16所述的方法，其特征在于，所述向所述第一类型终端发送所述第一LCID，包括：
    向所述第一类型终端发送系统消息，所述系统消息携带有所述第一LCID。
  18. 根据权利要求11所述的方法，其特征在于，所述第一类型终端的类型信息包括第二LCID和附加指示信息；
    其中，所述第二LCID是所述第一类型终端和所述第二类型终端共用的LCID；所述附加指示信息和所述第二LCID的组合用于指示所述第一类型终端，或，所述附加指示信息用于指示所述第一类型终端。
  19. 根据权利要求18所述的方法，其特征在于，所述第二LCID承载在所述消息3的LCID信息域，所述附加指示信息承载在所述消息3除所述LCID信息域之外的信息域。
  20. 根据权利要求19所述的方法，其特征在于，所述附加指示信息承载在所述消息3中的MACCE信息域。
  21. 根据权利要求11所述的方法，其特征在于，所述第一类型终端的类型信息包括第二LCID；所述第二LCID是所述第一类型终端和所述第二类型终端共用的LCID；
    所述方法还包括：
    在随机接入完成之后，接收所述终端发送的RRC信令，所述RRC信令携带有附加指示信息；
    基于所述附加指示信息和所述第二LCID的组合，确定所述终端为所述第一类型终端。
  22. 根据权利要求11所述的方法，其特征在于，所述第一类型终端的类型信息包括第二LCID；所述第二LCID是所述第一类型终端和所述第二类型终端共用的LCID；
    所述方法还包括：
    在随机接入完成之后，接收所述终端发送的RRC信令，所述RRC信令携带有附加指示信息；
    基于所述附加指示信息确定所述终端为所述第一类型终端。
  23. 一种消息发送装置，其特征在于，所述装置包括：
    第一发送模块，被配置为向网络设备发送随机接入过程中的消息3，所述消息3携带有用于指示第一类型终端的类型信息；
    其中，所述第一类型终端的类型信息与第二类型终端的类型信息、第三类型终端的类型信息均不同，所述第二类型终端与所述第三类型终端的终端能力均大于所述第一类型终端的终端能力。
  24. 一种消息接收装置，其特征在于，所述装置包括：
    第二接收模块，被配置为接收终端发送的随机接入过程中的消息3；
    第二处理模块，被配置为基于所述消息3携带的第一类型终端的类型信息，确定所述终端为所述第一类型终端；
    其中，所述第一类型终端的类型信息与第二类型终端的类型信息、第三类型终端的类型信息均不同，所述第二类型终端与所述第三类型终端的终端能力均大于所述第一类型终端的终端能力。
  25. 一种终端，其特征在于，所述终端包括：
    处理器；
    与所述处理器相连的收发器；
    其中，所述处理器被配置执行可执行指令以实现如权利要求1至10任一所述的消息发送方法。
  26. 一种网络设备，其特征在于，所述网络设备包括：
    处理器；
    与所述处理器相连的收发器；
    其中，所述处理器被配置执行可执行指令以实现如权利要求11至22任一所述的消息接收方法。
  27. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有至少一条指令、至少一段程序、代码集或指令集，所述至少一条指令、所述至少一段程序、所述代码集或指令集由处理器加载并执行以实现如权利要求1至10任一所述的消息发送方法，或者，如权利要求11至22任一所述的消息接收方法。
PCT/CN2022/089941 2022-04-28 2022-04-28 消息发送方法、消息接收方法、装置、设备及存储介质 Ceased WO2023206250A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
CN202280001437.XA CN117322117A (zh) 2022-04-28 2022-04-28 消息发送方法、消息接收方法、装置、设备及存储介质
PCT/CN2022/089941 WO2023206250A1 (zh) 2022-04-28 2022-04-28 消息发送方法、消息接收方法、装置、设备及存储介质
EP22939102.4A EP4518549A4 (en) 2022-04-28 2022-04-28 Message sending method and apparatus, message reception method and apparatus, device and storage medium
US18/860,363 US20250358858A1 (en) 2022-04-28 2022-04-28 Message sending method and apparatus, message reception method and apparatus, device and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/089941 WO2023206250A1 (zh) 2022-04-28 2022-04-28 消息发送方法、消息接收方法、装置、设备及存储介质

Publications (1)

Publication Number Publication Date
WO2023206250A1 true WO2023206250A1 (zh) 2023-11-02

Family

ID=88516780

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/089941 Ceased WO2023206250A1 (zh) 2022-04-28 2022-04-28 消息发送方法、消息接收方法、装置、设备及存储介质

Country Status (4)

Country Link
US (1) US20250358858A1 (zh)
EP (1) EP4518549A4 (zh)
CN (1) CN117322117A (zh)
WO (1) WO2023206250A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112055999A (zh) * 2018-04-30 2020-12-08 三星电子株式会社 发送和接收消息3协议数据单元的装置和方法
CN113424575A (zh) * 2019-02-13 2021-09-21 苹果公司 消息3(msg3)中针对版本16(rel-16)增强型机器类型通信(emtc)和窄带物联网(nb-iot)的质量报告的设计
WO2022081071A1 (en) * 2020-10-16 2022-04-21 Telefonaktiebolaget Lm Ericsson (Publ) Early indication for reduced capability devices

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4429294A4 (en) * 2021-11-01 2025-01-01 Beijing Xiaomi Mobile Software Co., Ltd. Random access method and apparatus and storage medium

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112055999A (zh) * 2018-04-30 2020-12-08 三星电子株式会社 发送和接收消息3协议数据单元的装置和方法
CN113424575A (zh) * 2019-02-13 2021-09-21 苹果公司 消息3(msg3)中针对版本16(rel-16)增强型机器类型通信(emtc)和窄带物联网(nb-iot)的质量报告的设计
WO2022081071A1 (en) * 2020-10-16 2022-04-21 Telefonaktiebolaget Lm Ericsson (Publ) Early indication for reduced capability devices

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "RAN1 aspects for RAN2-led features for RedCap", 3GPP DRAFT; R1-2104183, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20210519 - 20210527, 12 May 2021 (2021-05-12), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP052010671 *
See also references of EP4518549A4 *

Also Published As

Publication number Publication date
EP4518549A4 (en) 2025-06-04
EP4518549A1 (en) 2025-03-05
CN117322117A (zh) 2023-12-29
US20250358858A1 (en) 2025-11-20

Similar Documents

Publication Publication Date Title
CN106576236B (zh) 无线设备、网络节点及其中用于发送包括对无线设备的限制的指示的消息的方法
WO2023134678A1 (zh) 通信方法和通信装置
JP7612012B2 (ja) セカンダリセルをアクティブ化する方法、装置、デバイス及び記憶媒体
WO2020047856A1 (zh) 配置信息的传输方法和终端设备
US12133286B2 (en) Method and apparatus for identifying user equipment capability in sidelink transmission
CA3066924C (en) Resource scheduling method, terminal device, and network device
CN112088570B (zh) 一种信息传输方法、设备及存储介质
CN116455533A (zh) 通信方法和通信装置
CN111869281B (zh) 定位测距方法、装置、通信设备及存储介质
US12193018B2 (en) Method and device based on duplicate data transmission
WO2023206251A1 (zh) 随机接入资源配置方法、随机接入方法、装置及存储介质
CN114793363B (zh) 资源指示方法、终端设备和网络设备
WO2025232783A1 (zh) 通信方法和通信装置
WO2022141071A1 (zh) 小数据传输方法、装置、设备及介质
WO2023206250A1 (zh) 消息发送方法、消息接收方法、装置、设备及存储介质
CN114845416B (zh) 信息确定方法、装置、设备及存储介质
CN112203306B (zh) 终端、通信方法、装置及存储介质
WO2023173431A1 (zh) 邻小区测量方法、装置、设备、介质及程序产品
WO2021138955A1 (zh) 通知发送时间信息的方法以及装置
US20240073735A1 (en) Qos control method, access network device, and terminal device
WO2022236526A1 (zh) 载波确定方法、装置、设备及存储介质
WO2022236558A1 (zh) 用于数据传输的方法、装置、设备及存储介质

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 202280001437.X

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22939102

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202427089258

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 2022939102

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2022939102

Country of ref document: EP

Effective date: 20241128

WWP Wipo information: published in national office

Ref document number: 18860363

Country of ref document: US