WO2019161543A1 - 对媒体接入控制层的控制单元进行确认的方法、装置和通信系统 - Google Patents

对媒体接入控制层的控制单元进行确认的方法、装置和通信系统 Download PDF

Info

Publication number
WO2019161543A1
WO2019161543A1 PCT/CN2018/077046 CN2018077046W WO2019161543A1 WO 2019161543 A1 WO2019161543 A1 WO 2019161543A1 CN 2018077046 W CN2018077046 W CN 2018077046W WO 2019161543 A1 WO2019161543 A1 WO 2019161543A1
Authority
WO
WIPO (PCT)
Prior art keywords
mac
unit
network
configuration
acknowledgement
Prior art date
Application number
PCT/CN2018/077046
Other languages
English (en)
French (fr)
Inventor
史玉龙
张磊
Original Assignee
富士通株式会社
史玉龙
张磊
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 富士通株式会社, 史玉龙, 张磊 filed Critical 富士通株式会社
Priority to JP2020536537A priority Critical patent/JP2021510950A/ja
Priority to CN201880065535.3A priority patent/CN111194573A/zh
Priority to PCT/CN2018/077046 priority patent/WO2019161543A1/zh
Publication of WO2019161543A1 publication Critical patent/WO2019161543A1/zh
Priority to US16/910,763 priority patent/US20200322943A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22—Parsing or analysis of headers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0078—Avoidance of errors by organising the transmitted data in a format specifically designed to deal with errors, e.g. location
    • H04L1/0079—Formats for control data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H04L1/1685—Details of the supervisory signal the supervisory signal being transmitted in response to a specific request, e.g. to a polling signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1854—Scheduling and prioritising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/28—Timers or timing mechanisms used in protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • H04W72/566—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient
    • H04W72/569—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient of the traffic information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/188—Time-out mechanisms
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path

Definitions

  • the present application relates to the field of communications, and in particular, to a method, an apparatus, and a communication system for confirming a control unit of a medium access control layer.
  • 5G communication systems support Massive Machine Type Communications (mMTC) services and ultra-reliable-low latency communications (Ultra-Reliable and Low Latency Communications, URLLC) business.
  • Massive Machine Type Communications mMTC
  • ultra-reliable-low latency communications Ultra-Reliable and Low Latency Communications, URLLC
  • the reliability of the configuration signaling of the control unit (MAC CE, Media Access Control Control Element) of the existing media access control layer is much lower than the reliability of the data transmission of the URLLC. If the reliability of the MAC CE is not enhanced, the configuration of the URLLC may be incorrect, or a large configuration delay may occur, or the configuration of the network device and the terminal device may be inconsistent. Low latency and high reliability requirements cannot be achieved. In addition, the MAC CE associated with the URLLC service needs to have higher reliability than other MAC CEs.
  • An embodiment of the present application provides a method, a device, and a communication system for confirming a control unit (MAC CE) of a medium access control layer, where a first device that receives a MAC CE sends a message for confirming that the first device successfully receives the The MAC CE confirms the MAC CE, thereby improving the reliability of the MAC CE.
  • MAC CE control unit
  • a device for confirming a control unit (MAC CE, Media Access Control Element) of a media access control layer includes: a receiving unit that receives the MAC CE sent by the second device; and a first sending unit that sends an acknowledgement MAC CE for confirming that the first receiving unit successfully receives the MAC CE.
  • MAC CE Media Access Control Control Element
  • an apparatus for confirming a control unit (MAC CE, Media Access Control Element) of a medium access control layer includes a second sending unit, configured to send a MAC CE to the first device, and a second receiving unit, configured to receive an acknowledgement MAC CE sent by the first device to confirm that the first device successfully receives the MAC CE .
  • MAC CE Media Access Control Control Element
  • a communication system comprising a first device and a second device, the first device comprising the media MAC CE as described in the first aspect of the above embodiment The device for acknowledgment, the second device comprising means for confirming the media MAC CE as described in the second aspect of the above embodiment.
  • the beneficial effects of the embodiments of the present application are that the reliability of the MAC CE can be improved.
  • FIG. 1 is a schematic diagram of a communication system of the present application.
  • FIG. 2 is a schematic diagram of a method for confirming a MAC CE according to Embodiment 1 of the present application
  • FIG. 3 is a schematic diagram of a method for confirming a MAC CE according to Embodiment 2 of the present application.
  • FIG. 4 is a schematic diagram of an apparatus for confirming a MAC CE according to Embodiment 3 of the present application.
  • FIG. 5 is a schematic diagram of an apparatus for confirming a MAC CE according to Embodiment 4 of the present application.
  • FIG. 6 is a schematic structural diagram of a network device according to Embodiment 6 of the present application.
  • FIG. 7 is a schematic structural diagram of a terminal device according to Embodiment 6 of the present application.
  • FIG. 8 is a schematic diagram of a method for configuring configuration in RRC configuration signaling according to Embodiment 8 of the present application.
  • FIG. 9 is a schematic diagram of a method for configuring a configuration in an RRC configuration signaling according to Embodiment 9 of the present application.
  • FIG. 10 is a schematic diagram of an apparatus for configuring a configuration in an RRC configuration signaling according to Embodiment 10 of the present application;
  • FIG. 11 is a schematic diagram of an apparatus for configuring a configuration in an RRC configuration signaling according to Embodiment 11 of the present application;
  • FIG. 12 is a schematic diagram showing the configuration of a terminal device according to Embodiment 12 of the present application.
  • FIG. 13 is a schematic diagram showing the configuration of a network device according to Embodiment 13 of the present application.
  • the terms “first”, “second”, etc. are used to distinguish different elements from the title, but do not indicate the spatial arrangement or chronological order of the elements, and these elements should not be used by these terms. Limited.
  • the term “and/or” includes any and all combinations of one or more of the associated listed terms.
  • the terms “comprising,” “comprising,” “having,” or “an” are used to distinguish different elements from the title, but do not indicate the spatial arrangement or chronological order of the elements, and these elements should not be used by these terms. Limited.
  • the term “and/or” includes any and all combinations of one or more of the associated listed terms.
  • the term “communication network” or “wireless communication network” may refer to a network that conforms to any communication standard such as Long Term Evolution (LTE), Enhanced Long Term Evolution (LTE-A, LTE- Advanced), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), and the like.
  • LTE Long Term Evolution
  • LTE-A Enhanced Long Term Evolution
  • WCDMA Wideband Code Division Multiple Access
  • HSPA High-Speed Packet Access
  • the communication between devices in the communication system may be performed according to any phase of the communication protocol, and may include, for example but not limited to, the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, and future. 5G, New Radio (NR), etc., and/or other communication protocols currently known or to be developed in the future.
  • the term "network device” refers to, for example, a device in a communication system that accesses a terminal device to a communication network and provides a service for the terminal device.
  • the network device may include but is not limited to the following devices: a base station (BS, Base Station), an access point (AP, Access Point), a transmission and reception point (TRP), a broadcast transmitter, and a mobility management entity (MME, Mobile). Management Entity), gateway, server, Radio Network Controller (RNC), Base Station Controller (BSC), and so on.
  • BS Base Station
  • AP access point
  • TRP transmission and reception point
  • MME mobility management entity
  • Management Entity gateway
  • server Radio Network Controller
  • BSC Base Station Controller
  • the base station may include, but is not limited to, a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), and a 5G base station (gNB), and the like, and may further include a Remote Radio Head (RRH). , Remote Radio Unit (RRU), relay or low power node (eg femto, pico, etc.).
  • RRH Remote Radio Head
  • RRU Remote Radio Unit
  • base station may include some or all of their functions, and each base station may provide communication coverage for a particular geographic area.
  • the term "cell” can refer to a base station and/or its coverage area, depending on the context in which the term is used.
  • the term "user equipment” (UE) or “terminal equipment” (TE) refers to, for example, a device that accesses a communication network through a network device and receives a network service.
  • the terminal device may be fixed or mobile, and may also be referred to as a mobile station (MS, Mobile Station), a terminal, a subscriber station (SS, Subscriber Station), an access terminal (AT, Access Terminal), a station, and the like.
  • the terminal device may include but is not limited to the following devices: a cellular phone (Cellular Phone), a personal digital assistant (PDA, Personal Digital Assistant), a wireless modem, a wireless communication device, a handheld device, a machine type communication device, a laptop computer, Cordless phones, smart phones, smart watches, digital cameras, and more.
  • a cellular phone Cellular Phone
  • PDA Personal Digital Assistant
  • wireless modem Wireless Fidelity
  • a wireless communication device a handheld device
  • a machine type communication device a laptop computer
  • Cordless phones smart phones, smart watches, digital cameras, and more.
  • the terminal device may be a device or device that performs monitoring or measurement, and may include, but is not limited to, a Machine Type Communication (MTC) terminal.
  • MTC Machine Type Communication
  • FIG. 1 is a schematic diagram of a communication system of the present application, schematically illustrating a case where a terminal device and a network device are taken as an example.
  • the communication system 100 may include a network device 101 and a terminal device 102 (for the sake of simplicity, Figure 1 shows only one terminal device as an example).
  • an existing service or a service that can be implemented in the future can be performed between the network device 101 and the terminal device 102.
  • these services include, but are not limited to, enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and high reliability low latency communication (URLLC, Ultra-Reliable and Low- Latency Communication), and more.
  • eMBB enhanced mobile broadband
  • mMTC massive machine type communication
  • URLLC Ultra-Reliable and Low- Latency Communication
  • the terminal device 102 can transmit data to the network device 101, for example, using an authorized or unauthorized transfer mode.
  • the terminal device 101 can receive data sent by one or more terminal devices 102, and feed back information to the terminal device 102, for example, confirm ACK/non-acknowledgement NACK information, etc., and the terminal device 102 can confirm the end of the transmission process according to the feedback information, or can further Perform new data transfer or data retransmission.
  • the network device 101 can transmit information related to system information to the terminal device 102, and the terminal device 102 detects the received information to implement downlink synchronization, and the network device 101 establish connection.
  • the present application is not limited thereto, and the transmitting end and/or the receiving end may also be other. device of.
  • the present application is applicable not only to signal transmission between a network device and a terminal device but also to signal transmission between two terminal devices.
  • Embodiment 1 of the present application provides a method for confirming a control unit (MAC CE, Media Access Control Element) of a medium access control layer, which is performed by a first device.
  • MAC CE Media Access Control Control Element
  • FIG. 2 is a schematic diagram of a method for confirming a MAC CE in this embodiment. As shown in FIG. 2, the method includes:
  • Step 201 The first device receives the MAC CE sent by the second device.
  • Step 202 The first device sends an acknowledgement MAC CE for confirming that the first device successfully receives the MAC CE.
  • the first device sends the acknowledgement MAC CE, thereby being able to confirm that the first device successfully receives the MAC CE, thereby improving the reliability of the MAC CE.
  • the first device is a device that receives the MAC CE and sends an acknowledgement MAC CE, and the first device may be one of a network device and a terminal device.
  • the second device is a device that sends a MAC CE and receives an acknowledgement MAC CE, and the second device may be the other of the network device and the terminal device.
  • the first device and the second device communicate and form a communication system.
  • the first device when the first device is indicated by the second device, the first device may send the acknowledgement MAC CE; further, when the first device is not indicated by the second device, the first device This confirmation MAC CE is not sent. Thereby, the second device can indicate to each MAC CE, so that the first device sends an acknowledgement MAC CE to the MAC CE.
  • the MAC CE sent by the second device is used to indicate that the first device sends the acknowledgement MAC CE.
  • a field of the data part or subheader part of the MAC CE sent by the second device is used to indicate that the first device sends the acknowledgement MAC CE.
  • a field of the data part or the sub-header part of the MAC CE sent by the second device is set to 1, the first device is instructed to send the acknowledgement MAC CE to the MAC CE; When the field is set to 0, the first device does not send an acknowledgment MAC CE for the MAC CE.
  • the opposite is also possible.
  • the logical channel identifier (LCID) used by the MAC CE sent by the second device is used to indicate that the first device sends the acknowledgement MAC CE.
  • each MAC CE may correspond to at least two LCIDs, such as LCID1 and LCID2.
  • the first device sends an acknowledgement MAC CE to the MAC CE.
  • the first device does not send an acknowledgement MAC CE to the MAC CE.
  • the location of the MAC CE sent by the second device in the Media Access Control Protocol Data Unit (MAC PDU) of the medium access control layer received by the first device is used to indicate the first The device sends the acknowledgement MAC CE.
  • the first A device sends an acknowledgement MAC CE to the MAC CE; in addition, when the MAC CE received by the first device is in front of the entire MAC PDU, that is, before the MAC SDU, the first device does not send an acknowledgement to the MAC CE.
  • MAC CE the opposite is also possible.
  • other information sent by the second device may also be used to indicate that the first device sends the acknowledgement MAC CE.
  • the first device when the first device is configured by the first device and the network device in the second device, the first device sends the acknowledgement MAC CE.
  • the first device when the first device is a terminal device, and the second device is a network device, the first device may be configured by the network device as the second device; when the first device is a network device, the second device When it is a terminal device, the first device itself can be configured by the network device as the first device. Thereby, the first device can send the acknowledgement MAC CE according to the configuration of the network device, without the second device not being instructed for each MAC CE.
  • the network device may configure the first device to be: when the first device receives the first network signaling or the duration indicated by the first network signaling, Send a confirmation MAC CE.
  • the first network signaling may be, for example, physical layer signaling, or MAC CE, or Radio Resource Control (RRC) signaling, or other network signaling.
  • RRC Radio Resource Control
  • the time indicated by the first network signaling may be, for example, a time of a system frame, a subframe, or a time slot, or a symbol position indicated by the first network signaling.
  • the length of the duration may be determined by a timer configured by the network device, and/or the network device configures the first device to be at the time of receiving the second network signaling or indicated by the second network signaling At the moment, the end of the confirmation MAC CE is sent.
  • the second network signaling may be, for example, physical layer signaling, or MAC CE, or Radio Resource Control (RRC) signaling, or other network signaling.
  • RRC Radio Resource Control
  • the time indicated by the second network signaling may be, for example, a time of a system frame, a subframe, or a time slot, or a symbol position indicated by the second network signaling.
  • the first device is configured by the network device to start from a time when the first device receives the first network signaling, or from a system frame, a subframe, and a time indicated by the first network signaling.
  • the time at which the slot or the symbol position or the like starts the first device sends the acknowledgement MAC CE to the received MAC CE; and, at the time when the first device receives the first network signaling, or at the first network signaling
  • the first device starts a timer, the parameters of the timer are configured by the network device; and, during the running of the timer, the first The device sends a confirmation MAC CE to the received MAC CE.
  • the first device is further configured by the network device to: when the timer expires or is not running, the first device does not send an acknowledgement MAC CE to the received MAC CE.
  • the first device is further configured by the network device to: at a time when the first device receives the second network signaling, or in a system frame, a subframe, a time slot or a symbol indicated by the second network signaling At the moment of the location, etc., the first device stops transmitting the acknowledgement MAC CE to the received MAC CE, and further, if the timer is still running, the first device may also stop the timer.
  • the network device when the network device configures the first device with a logical channel having a threshold higher than a predetermined priority, the first device sends the acknowledge MAC CE.
  • the network device may configure or predefine a priority threshold.
  • the first device When the first device has a logical channel higher than the priority threshold, for example, when the first device has a service of the URLLC, the first device Sending an acknowledgement MAC CE to the received MAC CE; further, when the first device does not have a logical channel higher than the priority threshold, the first device does not send an acknowledgement MAC CE to the received MAC CE .
  • the acknowledgement MAC CE sent by the first device has a different data format from the MAC CE received by the first device, and/or content of different data portions, and/or different sub-head portions. Content, whereby the acknowledgment MAC CE can be distinguished from the MAC CE.
  • the data format of the acknowledgement MAC CE may include a data portion and a sub-header portion of the 0-bit, wherein the value of the LCID field of the sub-header portion and the LCID used by the MAC CE confirmed by the acknowledgement MAC CE The values are the same. Thereby, the byte overhead of the data portion of the acknowledgment MAC CE can be saved.
  • the LCID used by the activated and deactivated MAC CE of the repeated transmission may be configured as "111000" by the network device.
  • the data format of the acknowledged MAC CE is 0.
  • the activation, deactivation of the MAC CE confirms the MAC CE.
  • the data format of the acknowledgment MAC CE includes a data part and a sub-header, wherein the value of the LCID field of the data part is the same as the value of the LCID used by the acknowledgment MAC CE for the MAC CE.
  • the value of the LCID field of the subheader is a predetermined value.
  • the LCID used by the activated and deactivated MAC CE of the retransmission is configured by the network device as "111000".
  • the data format of the acknowledgment MAC CE is: the data part. Contains an LCID field, the value is set to "111000”, and the sub-header uses an LCID with a predetermined value, such as "110111”.
  • the second device receives the MACID field of the sub-header as "110111” and the LCID field of the data part is the MAC CE of "111000", it is determined that the MAC CE is to confirm the activation of the repeated transmission and the deactivated MAC CE. Confirm the MAC CE.
  • the data format of the acknowledgment MAC CE includes a sub-header portion and a data portion of 0 bits, wherein the value of the LCID field of the sub-header portion is a predetermined value.
  • the LCID used by the activated, deactivated MAC CE for repeated transmissions is configured by the network device as "111000".
  • the acknowledgment MAC CE data format is when the first device sends an acknowledgment MAC CE to the MAC CE during a configured period of time after the second device sends the MAC CE, for example, during a pre-configured window or timer permitting period.
  • the data portion is 0 bits, and the sub-header portion uses an LCID having a predetermined value, such as "110111”.
  • the second device determines that the MAC CE is a duplicate when the LC CE field of the sub-header is "110111" and the length of the data part is 0, after receiving the activated and deactivated MAC CE of the retransmission.
  • the activation of the transmission, the deactivation of the MAC CE confirms the MAC CE.
  • the first device sends an acknowledgement MAC CE to the received MAC CE, thereby being able to confirm that the first device successfully receives the MAC CE, thereby improving the reliability of the MAC CE. Furthermore, the acknowledgment MAC CE is distinguished from the MAC CE, whereby the acknowledgment MAC CE can be easily identified.
  • the second embodiment provides a method for confirming a MAC CE, which is performed by a second device.
  • FIG. 3 is a schematic diagram of a method for confirming a MAC CE in the second embodiment. As shown in FIG. 3, the method includes:
  • Step 301 The second device sends a MAC CE to the first device, and
  • Step 302 The second device receives the acknowledgement MAC CE sent by the first device to confirm that the first device successfully receives the MAC CE.
  • the second device receives the acknowledgement MAC CE sent by the first device to confirm that the first device successfully receives the MAC CE, thereby improving the reliability of the MAC CE.
  • the first device when the second device performs the indication, the first device sends the acknowledgement MAC CE.
  • the MAC CE sent by the second device is used to indicate that the first device sends the acknowledgement MAC CE; or a field of the data portion or the sub-header portion of the MAC CE is used to perform the indication; or
  • the logical channel identifier (LCID) used by the MAC CE is used to perform the indication; or the Media Access Control Protocol Data Unit (MAC PDU) of the medium access control layer received by the MAC CE at the first device The location in is used to make this indication.
  • LCID logical channel identifier
  • MAC PDU Media Access Control Protocol Data Unit
  • the first device when the first device and the network device in the second device configure the first device, the first device sends the acknowledge MAC CE.
  • the network device configures the first device to send an acknowledgement MAC CE for the duration of the time when the first network signaling is received or the time indicated by the first network signaling; wherein the duration is The length is determined by a timer configured by the network device, and/or the network device further configures the first device to end sending at a time when the second network signaling is received or when the second network signaling indicates This confirms the MAC CE.
  • the first device when the network device configures the first device with a logical channel having a threshold higher than a predetermined priority, the first device sends the acknowledge MAC CE.
  • the acknowledgment MAC CE has a different data format from the MAC CE, and/or content of different data portions, and/or content of different sub-head portions.
  • the data format of the acknowledgment MAC CE includes a data portion and a sub-head portion of the 0-bit, wherein the value of the LCID field of the sub-header is the same as the value of the LCID used by the MAC CE confirmed by the acknowledgment MAC CE;
  • the data format of the acknowledgment MAC CE includes a data part and a sub-header, wherein the value of the LCID field of the data part is the same as the value of the LCID used by the acknowledgment MAC CE for the MAC CE, and the sub-header part
  • the value of the LCID field is a predetermined value; or the data format of the acknowledgment MAC CE includes a data portion and a sub-head portion of 0 bits, and the value of the LCID field of the sub-head portion is a predetermined value.
  • Embodiment 1 the description of the same parts as those of Embodiment 1 can be referred to Embodiment 1, and this embodiment will not be described again.
  • the second device receives the acknowledgement MAC CE sent by the first device for the received MAC CE, thereby being able to confirm that the first device successfully receives the MAC CE, thereby improving the reliability of the MAC CE. Furthermore, the acknowledgment MAC CE is distinguished from the MAC CE, whereby the acknowledgment MAC CE can be easily identified by the second device.
  • Embodiment 3 provides an apparatus for confirming a MAC CE. Since the principle of solving the problem is similar to the method of Embodiment 1, the specific implementation may refer to the implementation of the method of Embodiment 1, and the description of the same portions is not repeated.
  • the apparatus 400 includes a first receiving unit 401 and a first transmitting unit 402.
  • the first receiving unit 401 is configured to receive the MAC CE sent by the second device, and the first sending unit 402 is configured to send an acknowledgement MAC CE for confirming that the first receiving unit successfully receives the MAC CE.
  • the apparatus 400 may further include: a first control unit 403.
  • the first sending unit 402 is controlled to send the acknowledgement MAC CE.
  • the first control unit 403 determines, according to the MAC CE sent by the second device, that the first device is instructed by the second device to send the acknowledgement MAC CE. For example, the first control unit 403 determines the indication according to a field of the data part or the sub-header part of the MAC CE; or the first control unit determines the indication according to the logical channel identifier (LCID) used by the MAC CE; or The first control unit determines the indication according to a location of the MAC CE in a Media Access Control Protocol Data Unit (MAC PDU) of the medium access control layer received by the first device.
  • LCID logical channel identifier
  • MAC PDU Media Access Control Protocol Data Unit
  • control unit 403 when the control unit 403 is configured by the first device and the network device in the second device, the control unit 403 controls the first sending unit 402 to send the acknowledgement MAC CE.
  • the network device configures the control unit to perform control to control the time when the first receiving unit 401 receives the first network signaling or the time indicated by the first network signaling
  • the first transmitting unit 402 transmits the acknowledgement MAC CE.
  • the length of the duration is determined by a timer configured by the network device; or the control unit is further configured by the network device to perform control at a time when the first receiving unit receives the second network signaling or At the time indicated by the second network signaling, the first transmitting unit is controlled to end sending the acknowledgement MAC CE.
  • control unit 403 is configured by the network device to perform control such that when the network device configures the first device with a logical channel having a threshold higher than a predetermined priority, the control unit 403 controls the The first transmitting unit 402 transmits the acknowledgement MAC CE.
  • the device 400 may further have a configuration unit (not shown) configured to configure the control unit 403 such that the control unit 403 is configured to perform the above control. .
  • the acknowledgment MAC CE has a different data format from the MAC CE, and/or content of different data portions, and/or content of different sub-head portions.
  • the data format of the acknowledgment MAC CE includes a data portion and a sub-head portion of the 0-bit, wherein the value of the LCID field of the sub-header is the same as the value of the LCID used by the MAC CE confirmed by the acknowledgment MAC CE;
  • the data format of the acknowledgment MAC CE includes a data part and a sub-header, wherein the value of the LCID field of the data part is the same as the value of the LCID used by the acknowledgment MAC CE for the MAC CE, and the sub-header part
  • the value of the LCID field is a predetermined value; or the data format of the acknowledgment MAC CE includes a data portion and a sub-head portion of 0 bits, and the value of the LCID field of the sub-head portion is a predetermined value.
  • the first device sends an acknowledgement MAC CE to the received MAC CE, thereby being able to confirm that the first device successfully receives the MAC CE, thereby improving the reliability of the MAC CE. Furthermore, the acknowledgment MAC CE is distinguished from the MAC CE, whereby the acknowledgment MAC CE can be easily identified.
  • Embodiment 4 provides an apparatus for confirming a MAC CE. Since the principle of solving the problem is similar to the method of the second embodiment, the specific implementation may refer to the implementation of the method of the second embodiment, and the description of the same portions is not repeated.
  • Fig. 5 is a schematic diagram of an apparatus for confirming a MAC CE in the fourth embodiment.
  • the apparatus 500 includes a second transmitting unit 501 and a second receiving unit 502.
  • the second sending unit 501 is configured to send the MAC CE to the first device
  • the second receiving unit 502 is configured to receive the acknowledgement sent by the first device to confirm that the first device successfully receives the MAC CE.
  • MAC CE MAC CE
  • the apparatus 500 further has a first indication unit 503, and when the first indication unit 503 indicates, the first device sends the confirmation MAC CE.
  • the first indication unit 503 sets the MAC CE sent by the second device to instruct the first device to send the acknowledgement MAC CE. For example, the first indication unit 503 sets a field of the data part or the sub-header part of the MAC CE to perform the indication; or the logical channel identifier (LCID) used by the first indication unit 503 for the MAC CE. The setting is made to perform the indication; or the first indication unit 503 sets the location of the MAC CE in the Protocol Data Unit (MAC PDU) of the Medium Access Control Layer to perform the indication.
  • MAC PDU Protocol Data Unit
  • the first device when the network device in the first device and the second device is configured, the first device sends the acknowledgement MAC CE.
  • the device 500 may further have a configuration unit 504.
  • the configuration unit 504 in the embodiment 4 and the configuration unit in the embodiment 3 refer to the same configuration unit.
  • the configuration unit 504 configures the first device to send the acknowledgement MAC CE for the duration of the time when the first network signaling is received or the time indicated by the first network signaling.
  • the length of the duration is determined by a timer configured by the configuration unit; and/or the configuration unit 504 configures the time when the first device receives the second network signaling or the second network signaling indicates At the moment, the confirmation MAC CE is sent.
  • the configuration unit 504 configures a logical channel for the first device, and configures the first device to: when the configuration unit 504 configures the first device with a threshold higher than a predetermined priority The first device sends the acknowledgment MAC CE when the channel is logical.
  • the acknowledgment MAC CE has a different data format from the MAC CE, and/or content of different data portions, and/or content of different sub-head portions.
  • the data format of the acknowledgment MAC CE includes a data portion and a sub-head portion of the 0-bit, wherein the value of the LCID field of the sub-header is the same as the value of the LCID used by the MAC CE confirmed by the acknowledgment MAC CE;
  • the data format of the acknowledgment MAC CE includes a data part and a sub-header, wherein the value of the LCID field of the data part is the same as the value of the LCID used by the acknowledgment MAC CE for the MAC CE, and the sub-header part
  • the value of the LCID field is a predetermined value; or the data format of the acknowledgment MAC CE includes a data portion and a sub-head portion of 0 bits, and the value of the LCID field of the sub-head portion is a predetermined value.
  • the second device receives the acknowledgement MAC CE sent by the first device for the received MAC CE, thereby being able to confirm that the first device successfully receives the MAC CE, thereby improving the reliability of the MAC CE. Furthermore, the acknowledgment MAC CE is distinguished from the MAC CE, whereby the acknowledgment MAC CE can be easily identified by the second device.
  • the embodiment 5 provides a device, which is a first device.
  • the method for solving the problem is similar to the method of the embodiment 1. Therefore, the specific implementation may be implemented by referring to the method of the embodiment 1. Repeat the explanation.
  • the first device may be a network device or a terminal device.
  • FIG. 6 is a schematic structural diagram of a network device according to an embodiment of the present invention.
  • network device 600 can include a central processing unit (CPU) 601 and memory 602; and memory 602 is coupled to central processor 601.
  • the memory 62 can store various data; in addition, a program for data processing is stored, and the program is executed under the control of the central processing unit 801.
  • the functionality of device 400 can be integrated into central processor 601.
  • the central processing unit 601 can be configured to implement the method for confirming the MAC CE of Embodiment 1.
  • central processor 601 can be configured to control such that network device 600 performs the method of embodiment 1.
  • the device 400 may be configured separately from the central processing unit 601.
  • the device 400 may be configured as a chip connected to the central processing unit 601, such as the unit shown in FIG. Control is implemented to implement the functionality of device 400.
  • the network device 600 may further include: a transceiver 603, an antenna 604, and the like; wherein the functions of the foregoing components are similar to the prior art, and details are not described herein again. It should be noted that the network device 600 does not have to include all the components shown in FIG. 6; in addition, the network device 600 may further include components not shown in FIG. 6, and reference may be made to the prior art.
  • FIG. 7 is a schematic structural diagram of a terminal device according to an embodiment of the present application.
  • the terminal device 700 may include a central processing unit (CPU) 701 and a memory 702; the memory 702 is coupled to the central processing unit 701.
  • the memory 702 can store various data; in addition, a program for data processing is stored, and the program is executed under the control of the central processing unit 701 to confirm the MAC CE.
  • the functionality of apparatus 400 of embodiment 3 may be integrated into central processor 701.
  • the central processing unit 701 can be configured to implement the method for confirming the MAC CE described in Embodiment 1.
  • the central processing unit 701 can be configured to perform control so that the terminal device 700 performs the method of Embodiment 1.
  • the above device 400 may be configured separately from the central processing unit 701.
  • the device 400 may be configured as a chip connected to the central processing unit 701, such as the unit shown in FIG. 7, through the central processing unit 701. Control is implemented to implement the functionality of device 400.
  • the terminal device 700 may further include a communication module 703, an input unit 704, a display 706, an audio processor 705, an antenna 709, a power source 708, and the like.
  • the functions of the above components are similar to those of the prior art, and are not described herein again. It should be noted that the terminal device 700 does not have to include all the components shown in FIG. 7; in addition, the terminal device 700 may further include components not shown in FIG. 7, and reference may be made to the prior art.
  • the first device sends an acknowledgement MAC CE to the received MAC CE, thereby being able to confirm that the first device successfully receives the MAC CE, thereby improving the reliability of the MAC CE. Furthermore, the acknowledgment MAC CE is distinguished from the MAC CE, whereby the acknowledgment MAC CE can be easily identified.
  • the sixth embodiment provides a device, and the device is a second device.
  • the method for solving the problem is similar to the method of the second embodiment. Therefore, the specific implementation may be implemented by referring to the method of the second embodiment. Repeat the explanation.
  • the second device may be a network device, and the schematic diagram of the network device may be the same as that of FIG. 6.
  • the functionality of apparatus 500 of embodiment 4 may be integrated into central processor 601 of network device 600.
  • the central processing unit 601 can be configured to implement the method for confirming the MAC CE of Embodiment 2.
  • central processor 601 can be configured to control such that network device 600 performs the method of embodiment 2.
  • the foregoing apparatus 500 may be configured separately from the central processing unit 601.
  • the apparatus 500 may be configured as a chip connected to the central processing unit 601, such as the unit shown in FIG. 6, through the central processing unit 601. Control is implemented to implement the functionality of device 500.
  • the second device may also be a terminal device, and the schematic diagram of the terminal device may be the same as that of FIG. 7.
  • the functionality of the apparatus 500 of Embodiment 4 may be integrated into the central processor 701 of the terminal device 700.
  • the central processing unit 701 can be configured to implement the method for confirming the MAC CE described in Embodiment 2.
  • the central processing unit 701 can be configured to perform control such that the terminal device 700 performs the method of the second embodiment.
  • the above device 500 may be configured separately from the central processing unit 701.
  • the device 500 may be configured as a chip connected to the central processing unit 701, such as the unit shown in FIG. 7, through the central processing unit 701. Control is implemented to implement the functionality of device 500.
  • the second device receives the acknowledgement MAC CE sent by the first device for the received MAC CE, thereby being able to confirm that the first device successfully receives the MAC CE, thereby improving the reliability of the MAC CE. Furthermore, the acknowledgment MAC CE is distinguished from the MAC CE, whereby the acknowledgment MAC CE can be easily identified by the second device.
  • the seventh embodiment provides a communication system, which includes at least the first device in the embodiment 5 and the second device in the embodiment 6, wherein the first device may be a network device, and the second device may be a terminal device Alternatively, the first device may be a terminal device, and the second device may be a network device.
  • the first device may be a terminal device
  • the second device may be a network device.
  • the second device receives the acknowledgement MAC CE sent by the first device for the received MAC CE, thereby being able to confirm that the first device successfully receives the MAC CE, thereby improving the reliability of the MAC CE. Furthermore, the acknowledgment MAC CE is distinguished from the MAC CE, whereby the acknowledgment MAC CE can be easily identified by the second device.
  • the embodiment of the present invention further provides a storage medium storing a computer readable program, wherein the computer readable program causes the device for confirming the MAC CE or the first device to perform the method for confirming the MAC CE described in Embodiment 1 .
  • the embodiment of the present invention further provides a computer readable program, wherein when the program is executed in a device or a first device that confirms a MAC CE, the program causes the device or the first device that confirms the MAC CE to perform the implementation.
  • the embodiment of the present invention further provides a storage medium storing a computer readable program, wherein the computer readable program causes the device or the second device that confirms the MAC CE to perform the method for determining the cache status report of Embodiment 2.
  • the embodiment of the present invention further provides a computer readable program, wherein when the program is executed in a device or a second device that confirms the MAC CE, the program causes the device or the second device that confirms the MAC CE to perform the implementation.
  • Embodiment 8 of the present application provides a method for configuring a configuration in a Radio Resource Control (RRC) configuration signaling, which is performed by a terminal device.
  • RRC Radio Resource Control
  • the network device cannot know the physical moment of transmitting a certain RRC configuration signaling and the physical resources used, and thus cannot accurately know the moment when the terminal device successfully receives the RRC configuration signaling, thereby causing the network device and the terminal.
  • the time when the new configuration is applied to the side is not synchronized, which in turn causes the configuration of the network device and the terminal device to be inconsistent over a period of time.
  • the terminal device may have applied a configuration that does not match the network device, resulting in an error in data transmission.
  • the mismatched configuration of the terminal device during this time period cannot be tolerated for the URLLC service.
  • the method for configuring the configuration in the RRC configuration signaling in this embodiment can avoid a data transmission error caused by the time mismatch of the configuration in the RRC configuration signaling applied by the network device and the terminal device.
  • FIG. 8 is a schematic diagram of a method for configuring a configuration in an RRC configuration signaling according to this embodiment. As shown in FIG. 8, the method includes:
  • Step 801 The terminal device receives the RRC configuration signaling sent by the network device;
  • Step 802 The terminal device starts to apply the configuration in the RRC configuration signaling at a time indicated by the network device or at a predefined time.
  • the terminal device starts to apply the configuration in the RRC configuration signaling at the time indicated by the network device or at a predefined time. Therefore, it is possible to avoid the time when the configuration in the RRC configuration signaling is not applied by the network device and the terminal device. The data transmission error caused by the match.
  • the terminal device may start to apply the configuration in the RRC configuration signaling at the time indicated by the network device, where the time indicated by the network device may be at least two candidate moments. a moment.
  • the candidate moment may include a first moment, where the terminal device successfully receives the RRC configuration signaling, or the terminal device sends or downlinks the RRC configuration signaling
  • the time of the corresponding RRC configuration success (RRC complete) message; and/or the alternative time may include a second time, which is a time indicated by the network device or a predefined time, for example, the second time may It is a specific system frame number, a specific subframe number, a specific slot position, a specific symbol position, and the like.
  • the RRC configuration signaling is reconfiguration setting signaling for resources used by the terminal device's URLLC service.
  • the RRC configuration signaling has a field for indicating whether the terminal device applies the configuration in the RRC configuration signaling at the first time or the second time. If the field is set to the first value, the terminal device starts to apply the configuration at the first moment, for example, when the RRC signaling is successfully received, or when the UE sends or submits the RRC letter to the lower layer.
  • the time at which the first symbol position of the first subframe of the odd-numbered subframe in each system frame number (SFN) is pre-configured is used as the second time.
  • the terminal device starts to apply the configuration in the RRC configuration signaling at the time indicated by the network device or at a predefined time. Therefore, it is possible to avoid the time when the configuration in the RRC configuration signaling is not applied by the network device and the terminal device. The data transmission error caused by the match.
  • the embodiment 9 provides a method for configuring a configuration in a radio resource control (RRC) configuration signaling, which is performed by a network device.
  • RRC radio resource control
  • FIG. 9 is a schematic diagram of a method for applying a configuration in RRC configuration signaling in Embodiment 9. As shown in FIG. 9, the method includes:
  • Step 901 The network device applies a configuration in the RRC configuration signaling sent by the network device.
  • the time at which the network device applies the configuration is determined by the service related to the configuration.
  • the service refers to a high-reliability and low-latency service, for example, an Ultra Reliable & Low Latency Communication (URLLC) service.
  • URLLC Ultra Reliable & Low Latency Communication
  • the network device applies the configuration earlier than the terminal device if the service is to be initiated, or the RRC configuration signaling is sent before the service is initiated.
  • the network device can initiate the determination of the service; if the service is initiated by the terminal device, the network The device is able to listen to determine the origin of the service.
  • the application of the configuration by the network device earlier than the terminal device refers to applying the configuration at a time when the network device sends or sends the RRC configuration signaling to the lower layer.
  • the network device is configured earlier than the terminal device application for the URLLC service. Even if the application time of the configuration is different for the network device and the terminal device, the data of the URLLC service to be initiated can be transmitted under the correct configuration, thereby ensuring the data reliability of the URLLC service.
  • the URLLC service of the terminal device has not yet started, but the URLLC service is to be initiated, and the network device prepares for the URLLC service by using the RRC configuration signaling, and sends the RRC configuration signaling to the network device when the network device sends the RRC configuration signaling.
  • the network device can apply the configuration.
  • the network device applies the configuration later than the terminal device if the service is about to end or the RRC configuration signaling is sent after the service is initiated or in progress. Applying the configuration to the terminal device later than the terminal device means that the configuration is applied when the network side receives the RRC complete message corresponding to the RRC configuration message.
  • the network device is later than the terminal device application configuration used after stopping the URLLC service. Even if the application time of the configuration is different for the network device and the terminal device, the data of the ongoing URLLC service can be transmitted under the correct configuration, thereby ensuring the data reliability of the URLLC service.
  • the URLLC of the terminal device has been started and is in progress.
  • the network device changes the relevant configuration of the resource through the RRC configuration.
  • the network device can receive the RRC corresponding to the RRC configuration signaling. The configuration is applied at the moment of the complete message.
  • the method may further include:
  • Step 902 The network device sends RRC configuration signaling to the terminal device;
  • Step 903 The network device indicates a moment when the terminal device starts to apply the configuration in the RRC configuration signaling.
  • the network device may instruct the terminal device to start applying the configuration in the RRC configuration signaling at one of the at least two alternate moments.
  • the candidate moment includes a first moment, where the terminal device successfully receives the RRC configuration signaling, or the terminal device sends or reports the lower layer corresponding to the RRC configuration signaling.
  • the RRC configuration succeeds (RRC complete) message; and/or the alternate time includes a second time, which is a time indicated by the network device or a predefined time.
  • first time and the second time reference may be made to Embodiment 8, and this embodiment is not repeated.
  • the network device may be configured earlier than the terminal device application for the URLLC service, and/or later than the configuration of the terminal device application after stopping the URLLC service, thereby ensuring the URLLC service to be initiated and/or The data of the ongoing URLLC service can be transmitted under the correct configuration to ensure the data reliability of the URLLC service.
  • the network device instructs the terminal device to start applying the configuration in the RRC configuration signaling, thereby avoiding A data transmission error caused by a mismatch in the configuration of the configuration in the RRC configuration signaling by the network device and the terminal device.
  • the embodiment 10 provides an apparatus for applying a configuration in Radio Resource Control (RRC) configuration signaling, which is applied to a terminal device. Since the principle of solving the problem is similar to the method of the embodiment 8, the specific implementation may refer to the implementation of the method of the embodiment 8, and the description of the same portions is not repeated.
  • RRC Radio Resource Control
  • FIG. 10 is a schematic diagram of an apparatus for configuring a configuration in RRC configuration signaling according to the tenth embodiment.
  • the device 1000 includes a third receiving unit 1001 and a first application unit 1002.
  • the third receiving unit 1001 is configured to receive the RRC configuration signaling sent by the network device, where the first application unit 1002 is configured to start in the RRC configuration signaling at the time indicated or predefined by the network device. The configuration is applied to the terminal device.
  • the first application unit 1002 starts to apply the configuration in the RRC configuration signaling at a time indicated by the network device, where the time indicated by the network device is one of at least two candidate moments. .
  • the candidate moment includes a first moment, where the terminal device successfully receives the RRC configuration signaling, or the terminal device sends or reports the lower layer corresponding to the RRC configuration signaling.
  • the RRC configuration succeeds (RRC complete) message; and/or the alternate time includes a second time, which is a time indicated by the network device or a predefined time.
  • the terminal device starts to apply the configuration in the RRC configuration signaling at the time indicated by the network device or at a predefined time. Therefore, it is possible to avoid the time when the configuration in the RRC configuration signaling is not applied by the network device and the terminal device. The data transmission error caused by the match.
  • the embodiment 11 provides an apparatus for applying a configuration in Radio Resource Control (RRC) configuration signaling, which is applied to a network device. Since the principle of solving the problem is similar to the method of the embodiment 9, the specific implementation may refer to the implementation of the method of the embodiment 9, and the description of the same portions is not repeated.
  • RRC Radio Resource Control
  • FIG. 11 is a schematic diagram of an apparatus for configuring a configuration in RRC configuration signaling according to the eleventh embodiment. As shown in FIG. 11, the device 1100 includes a second application unit 1101.
  • the second application unit 1101 is configured to apply the configuration in the RRC configuration signaling sent by the network device to the network device, where the time when the second application unit 1101 applies the configuration is related to the configuration.
  • This service refers to, for example, Ultra Reliable & Low Latency Communication (URLLC) services.
  • URLLC Ultra Reliable & Low Latency Communication
  • the second application unit applies the configuration to the network device earlier than the terminal device.
  • the second application unit applies the configuration to the network device earlier than the terminal device, and the application is applied at a time when the network device sends or sends the RRC configuration signaling to the lower layer.
  • the second application unit when the service is about to end, or the RRC configuration signaling is sent after the service is initiated or in progress, applies the configuration to the network device later than the terminal device.
  • the applying the configuration to the network device later than the terminal device refers to applying the configuration when the network device receives the RRC complete message corresponding to the RRC configuration message.
  • the apparatus 1100 further includes: a third transmitting unit 1102 and a second indicating unit 1103.
  • the third sending unit 1102 is configured to send the RRC configuration signaling to the terminal device
  • the second instructing unit 1103 is configured to instruct the terminal device to start applying the configuration in the RRC configuration signaling.
  • the second indication unit 1103 instructs the terminal device to start applying the configuration in the RRC configuration signaling at one of the at least two candidate moments.
  • the candidate moment includes a first moment, where the terminal device successfully receives the RRC configuration signaling, or the terminal device sends or downlinks the RRC configuration corresponding to the RRC configuration signaling successfully. (RRC complete) the time of the message; and/or, the alternate time includes a second time, which is a time indicated by the network device or predefined.
  • the buffer status report received by the device receiving the buffer status report can indicate the correspondence between the cache size and the logical channel group included in the cache status report, so that the terminal device and the network device adopt a consistent and clear manner.
  • the technical solution determines the correspondence between the logical channel group and the cache size included in the BSR.
  • the network device may be configured earlier than the terminal device application for the URLLC service, and/or later than the configuration of the terminal device application after stopping the URLLC service, thereby ensuring the URLLC service to be initiated and/or The data of the ongoing URLLC service can be transmitted under the correct configuration to ensure the data reliability of the URLLC service.
  • the network device instructs the terminal device to start applying the configuration in the RRC configuration signaling, thereby avoiding A data transmission error caused by a mismatch in the configuration of the configuration in the RRC configuration signaling by the network device and the terminal device.
  • the embodiment 12 provides a terminal device.
  • the principle of the device is similar to that of the embodiment 8. Therefore, the specific implementation may be implemented by referring to the method in the embodiment 8.
  • FIG. 12 is a schematic diagram showing the structure of a terminal device according to an embodiment of the present invention.
  • the terminal device 1200 can include a central processing unit (CPU) 1201 and a memory 1202; the memory 1202 is coupled to the central processing unit 1201.
  • the memory 1202 can store various data; in addition, a program for data processing is stored, and the program is executed under the control of the central processing unit 1201.
  • the functionality of apparatus 1000 of embodiment 10 may be integrated into central processor 1201.
  • the central processing unit 1201 may be configured to implement the method for configuring the configuration in the RRC configuration signaling described in Embodiment 8.
  • the central processing unit 1201 can be configured to perform control such that the terminal device 1200 performs the method of the eighth embodiment.
  • the above device 1200 can be configured separately from the central processing unit 1201.
  • the device 1000 can be configured as a chip connected to the central processing unit 1201, such as the unit shown in FIG. 12, through the central processing unit 1201. Control is implemented to implement the functionality of device 1000.
  • the terminal device 1200 may further include a communication module 1203, an input unit 1204, a display 1206, an audio processor 1205, an antenna 1209, a power source 1208, and the like.
  • the functions of the above components are similar to those of the prior art, and are not described herein again. It should be noted that the terminal device 1200 does not have to include all the components shown in FIG. 12; in addition, the terminal device 1200 may further include components not shown in FIG. 12, and reference may be made to the related art.
  • the terminal device starts to apply the configuration in the RRC configuration signaling at the time indicated by the network device or at a predefined time. Therefore, it is possible to avoid the time when the configuration in the RRC configuration signaling is not applied by the network device and the terminal device. The data transmission error caused by the match.
  • the embodiment 13 provides a network device.
  • the principle of the device is similar to that of the embodiment 9. Therefore, the specific implementation may be implemented by referring to the method in the embodiment 9.
  • FIG. 13 is a schematic structural diagram of a network device according to an embodiment of the present invention.
  • network device 1300 can include a central processing unit (CPU) 1301 and memory 1302; and memory 1302 is coupled to central processing unit 1301.
  • the memory 1302 can store various data; in addition, a program for data processing is stored, and the program is executed under the control of the central processing unit 1301.
  • the functionality of device 1100 can be integrated into central processor 1301.
  • the central processing unit 1301 may be configured to implement the method of configuring the configuration in the RRC configuration signaling of Embodiment 9.
  • central processor 1301 can be configured to control such that network device 1300 performs the method of embodiment 9.
  • the above device 1100 can be configured separately from the central processing unit 1301.
  • the device 1100 can be configured as a chip connected to the central processing unit 1301, such as the unit shown in FIG. 13, through the central processing unit 1301. Controls to implement the functionality of device 1100.
  • the network device 1300 may further include: a transceiver 1303, an antenna 1304, and the like; wherein the functions of the foregoing components are similar to the prior art, and details are not described herein again. It should be noted that the network device 1300 does not have to include all the components shown in FIG. 13; in addition, the network device 1300 may further include components not shown in FIG. 13, and reference may be made to the prior art.
  • the network device may be configured earlier than the terminal device application for the URLLC service, and/or later than the configuration of the terminal device application after stopping the URLLC service, thereby ensuring the URLLC service to be initiated and/or The data of the ongoing URLLC service can be transmitted under the correct configuration to ensure the data reliability of the URLLC service.
  • the network device instructs the terminal device to start applying the configuration in the RRC configuration signaling, thereby avoiding A data transmission error caused by a mismatch in the configuration of the configuration in the RRC configuration signaling by the network device and the terminal device.
  • the embodiment 14 provides a communication system, which includes at least the terminal device in the embodiment 12 and the network device in the embodiment 13, and the content thereof is incorporated herein, and details are not described herein again.
  • the present embodiment it is possible to avoid a data transmission error caused by the time mismatch of the configuration in the RRC configuration signaling applied by the network device and the terminal device.
  • the embodiment of the present invention further provides a storage medium storing a computer readable program, wherein the computer readable program causes a device or a terminal device that applies the configuration in the RRC configuration signaling to perform the application RRC configuration signaling described in Embodiment 8.
  • the embodiment of the present invention further provides a computer readable program, wherein when the program is executed in a device or a terminal device configured in a RRC configuration signaling, the program causes the configured device in the RRC configuration signaling or The terminal device performs the method of configuring the configuration in the RRC configuration signaling described in Embodiment 8.
  • the embodiment of the present invention further provides a storage medium storing a computer readable program, wherein the computer readable program causes a device or a terminal device that applies the configuration in the RRC configuration signaling to perform the application RRC configuration signaling described in Embodiment 9.
  • the embodiment of the present invention further provides a computer readable program, wherein when the program is executed in a device or a terminal device configured in a RRC configuration signaling, the program causes the configured device in the RRC configuration signaling or The terminal device performs the method of configuring the configuration in the RRC configuration signaling described in Embodiment 9.
  • the above apparatus and method of the present invention may be implemented by hardware or by hardware in combination with software.
  • the present invention relates to a computer readable program that, when executed by a logic component, enables the logic component to implement the apparatus or components described above, or to cause the logic component to implement the various methods described above Or steps.
  • the present invention also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, or the like.
  • Each processing method in each device described in connection with the embodiments of the present invention may be directly embodied as hardware, a software module executed by a processor, or a combination of both.
  • one or more of the functional block diagrams shown in Figures 4, 5, 10, 11 and/or one or more combinations of functional block diagrams may correspond to various software modules of a computer program flow, or may correspond to Various hardware modules.
  • These software modules may correspond to the respective steps shown in Figures 2, 3, 8, and 9, respectively.
  • These hardware modules can be implemented, for example, by curing these software modules using a Field Programmable Gate Array (FPGA).
  • FPGA Field Programmable Gate Array
  • the software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.
  • a storage medium can be coupled to the processor to enable the processor to read information from, and write information to, the storage medium; or the storage medium can be an integral part of the processor.
  • the processor and the storage medium can be located in an ASIC.
  • the software module can be stored in the memory of the mobile terminal or in a memory card that can be inserted into the mobile terminal.
  • the software module can be stored in the MEGA-SIM card or a large-capacity flash memory device.
  • One or more of the functional block diagrams described with respect to Figures 4, 5, 10, 11 and/or one or more combinations of functional block diagrams may be implemented as a general purpose processor, digital signal processing for performing the functions described herein. (DSP), application specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or any suitable combination thereof.
  • DSP digital signal processing
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • One or more of the functional block diagrams described with respect to Figures 4, 5, 10, 11 and/or one or more combinations of functional block diagrams may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, A plurality of microprocessors, one or more microprocessors in communication with the DSP, or any other such configuration.
  • An apparatus for configuring a configuration in a Radio Resource Control (RRC) configuration signaling comprising:
  • a third receiving unit configured to receive RRC configuration signaling sent by the network device
  • a first application unit configured to start applying the configuration in the RRC configuration signaling to the terminal device at a time indicated by the network device or at a predefined time.
  • the first application unit starts to apply the configuration in the RRC configuration signaling at a time indicated by the network device, where the time indicated by the network device is one of the at least two candidate moments.
  • the candidate moment includes a first moment, where the terminal device successfully receives the RRC configuration signaling, or the terminal device sends or downlinks the RRC configuration corresponding to the RRC configuration signaling to succeed (RRC Complete) The moment of the message.
  • the alternate moment includes a second moment, which is an indicated or predefined time of the network device.
  • a device for configuring a configuration in a Radio Resource Control (RRC) configuration signaling comprising:
  • a second application unit configured to apply, to the network device, a configuration in the RRC configuration signaling sent by the network device
  • the time at which the second application unit applies the configuration is determined by the service related to the configuration.
  • This service refers to the Ultra Reliable & Low Latency Communication (URLLC) service.
  • URLLC Ultra Reliable & Low Latency Communication
  • the second application unit applies the configuration to the network device earlier than the terminal device.
  • Applying the configuration to the network device earlier than the terminal device refers to applying the configuration at a time corresponding to the network device transmitting or delivering the RRC configuration signaling to the lower layer.
  • the second application unit applies the configuration to the network device later than the terminal device.
  • Applying the configuration to the network device later than the terminal device refers to applying the configuration when the network device receives the RRC complete message corresponding to the RRC configuration message.
  • a third sending unit configured to send RRC configuration signaling to the terminal device
  • a second indication unit configured to indicate a moment when the terminal device starts to apply the configuration in the RRC configuration signaling.
  • the second indication unit instructs the terminal device to start applying the configuration in the RRC configuration signaling at one of at least two candidate moments.
  • the candidate moment includes a first moment, where the terminal device successfully receives the RRC configuration signaling, or the terminal device sends or downlinks the RRC configuration corresponding to the RRC configuration signaling to succeed (RRC Complete) The moment of the message.
  • the alternate moment includes a second moment, which is an indicated or predefined time of the network device.
  • a communication system comprising a terminal device and a network device, the device having the device of one of the supplementary notes 1-4, the network device having the device of one of the supplementary notes 5-14.
  • a device for confirming a control unit (MAC CE, Media Access Control Control Element) of a medium access control layer comprising:
  • a second sending unit configured to send a MAC CE to the first device
  • a second receiving unit configured to receive an acknowledgement MAC CE sent by the first device to confirm that the first device successfully receives the MAC CE.
  • the device further has an indication unit, when the indication unit indicates, the first device sends the confirmation MAC CE; or
  • the first device sends the acknowledge MAC CE.
  • the indication unit sets the MAC CE sent by the second device to instruct the first device to send the acknowledge MAC CE.
  • the indication unit sets a field of the data portion or the sub-header portion of the MAC CE to perform the indication.
  • the indication unit sets a logical channel identifier (LCID) used by the MAC CE to perform the indication.
  • LCID logical channel identifier
  • the indication unit sets a location of the MAC CE in a Media Access Control Protocol Data Unit (MAC PDU) of the medium access control layer to perform the indication.
  • MAC PDU Media Access Control Protocol Data Unit
  • the second device is the network device, and the second device further has a configuration unit,
  • the configuration unit configures the first device to send the acknowledgement MAC CE for a duration of time when the first network signaling is received or the time indicated by the first network signaling.
  • the length of the duration is determined by a timer configured by the configuration unit.
  • the configuration unit configures the first device to end sending the acknowledgement MAC CE at a time when the second network signaling is received or a time indicated by the second network signaling.
  • the second device is the network device, the device further has a configuration unit, the configuration unit configures a logical channel for the first device, and configures the first device as:
  • the configuration unit configures the first device with a logical channel having a threshold higher than a predetermined priority
  • the first device sends the acknowledgement MAC CE.
  • the acknowledgment MAC CE has a different data format from the MAC CE, and/or content of different data portions, and/or content of different sub-head portions.
  • the data format of the acknowledgement MAC CE includes a data portion and a sub-head portion of 0 bits.
  • the value of the LCID field of the sub-header is the same as the value of the LCID used by the MAC CE confirmed by the acknowledgement MAC CE.
  • the data format of the acknowledged MAC CE includes a data part and a sub-header part
  • the value of the LCID field of the data part is the same as the value of the LCID used by the MAC CE confirmed by the acknowledgement MAC CE.
  • the value of the LCID field of the sub-header is a predetermined value.
  • the data format of the acknowledgement MAC CE includes a data portion and a sub-head portion of 0 bits.
  • the value of the LCID field of the sub-header is a predetermined value.

Abstract

本申请提供一种对媒体接入控制层的控制单元进行确认的方法、装置、以及通信系统。该方法包括：第一设备接收第二设备发送的MAC CE；以及该第一设备发送用于确认所述第一设备成功接收到所述MAC CE的确认MAC CE。根据本申请，能够提高MAC CE的可靠性。

Description

对媒体接入控制层的控制单元进行确认的方法、装置和通信系统 技术领域
本申请涉及通信领域，特别涉及一种对媒体接入控制层的控制单元进行确认的方法、装置、以及通信系统。
背景技术
近年，基于移动通信网络的各类数据应用和服务快速增长，被移动通信网络服务的终端也从传统的以人为使用主体的智能手机终端扩展到更多的以机器为主体的其它类型终端。
为了适应这样的变化趋势，未来移动通信网络需要具备提供更灵活、更多样服务的能力，以满足不同终端设备、不同服务的需求。例如，除传统增强移动宽带(enhanced Mobile Broadband,eMBB)业务之外，5G通信系统还支持海量机器类型通信(Massive Machine Type Communications,mMTC)业务以及超高可靠-低时延通信(Ultra-Reliable and Low Latency Communications,URLLC)业务。
应该注意，上面对技术背景的介绍只是为了方便对本申请的技术方案进行清楚、完整的说明，并方便本领域技术人员的理解而阐述的。不能仅仅因为这些方案在本申请的背景技术部分进行了阐述而认为上述技术方案为本领域技术人员所公知。
发明内容
尽管现有技术对数据传输的可靠性进行了很多增强，但是对数据传输方式和资源进行配置的信令的可靠性增强还不够。
例如，现有媒体接入控制层的控制单元(MAC CE，Media Access Control Control Element)配置信令的可靠性远低于URLLC的数据传输可靠性。如果不对MAC CE的可靠性进行增强，可能导致URLLC相关的配置发生错误，或者产生较大的配置时延，或者导致网络设备侧和终端设备侧对配置的理解不一致，最终都会导致URLLC的数据传输不能达到低时延高可靠性的要求。此外，与URLLC业务相关的MAC CE需要比其他MAC CE具有更高的可靠性。
本申请实施例提供一种对媒体接入控制层的控制单元(MAC CE)进行确认的方 法、装置以及通信系统，接收到MAC CE的第一设备发送用于确认该第一设备成功接收到该MAC CE的确认MAC CE，由此，提高MAC CE的可靠性。
根据本申请实施例的第一方面，提供了一种对媒体接入控制层的控制单元(MAC CE，Media Access Control Control Element)进行确认的装置，设置于第一设备，该装置包括：第一接收单元，其接收第二设备发送的MAC CE；以及第一发送单元，其发送用于确认该第一接收单元成功接收到该MAC CE的确认MAC CE。
根据本申请实施例的第二方面，提供了一种一种对媒体接入控制层的控制单元(MAC CE，Media Access Control Control Element)进行确认的装置，被设置于第二设备，该装置包括：第二发送单元，其用于向第一设备发送MAC CE；以及第二接收单元，其用于接收该第一设备发送的用于确认该第一设备成功接收到该MAC CE的确认MAC CE。
根据本申请实施例的第三方面，提供了一种通信系统，该通信系统包括第一设备和第二设备，该第一设备包括如上述实施例的第一方面所述的对媒体MAC CE进行确认的装置，该第二设备包括如上述实施例的第二方面所述的对媒体MAC CE进行确认的装置。
本申请实施例的有益效果在于：能够提高MAC CE的可靠性。
参照后文的说明和附图，详细公开了本申请的特定实施方式，指明了本申请的原理可以被采用的方式。应该理解，本申请的实施方式在范围上并不因而受到限制。在所附权利要求的条款的范围内，本申请的实施方式包括许多改变、修改和等同。
针对一种实施方式描述和/或示出的特征可以以相同或类似的方式在一个或更多个其它实施方式中使用，与其它实施方式中的特征相组合，或替代其它实施方式中的特征。
应该强调，术语“包括/包含”在本文使用时指特征、整件、步骤或组件的存在，但并不排除一个或更多个其它特征、整件、步骤或组件的存在或附加。
附图说明
在本申请实施例的一个附图或一种实施方式中描述的元素和特征可以与一个或更多个其它附图或实施方式中示出的元素和特征相结合。此外，在附图中，类似的标号表示几个附图中对应的部件，并可用于指示多于一种实施方式中使用的对应部件。
所包括的附图用来提供对本申请实施例的进一步的理解，其构成了说明书的一部分，用于例示本申请的实施方式，并与文字描述一起来阐释本申请的原理。显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。在附图中：
图1是本申请的通信系统的一个示意图；
图2是本申请实施例1的对MAC CE进行确认的方法的一个示意图；
图3是本申请实施例2的对MAC CE进行确认的方法的一个示意图；
图4是本申请实施例3的对MAC CE进行确认的装置的一个示意图；
图5是本申请实施例4的对MAC CE进行确认的装置的一个示意图；
图6是本申请实施例6的网络设备构成示意图；
图7是本申请实施例6的终端设备的构成示意图；
图8是本申请实施例8的应用RRC配置信令中的配置的方法的一个示意图；
图9是本申请实施例9的应用RRC配置信令中的配置的方法的一个示意图；
图10是本申请实施例10的应用RRC配置信令中的配置的装置的一个示意图；
图11是本申请实施例11的应用RRC配置信令中的配置的装置的一个示意图；
图12是本申请实施例12的终端设备构成的一个示意图；
图13是本申请实施例13的网络设备构成的一个示意图。
具体实施方式
参照附图，通过下面的说明书，本申请的前述以及其它特征将变得明显。在说明书和附图中，具体公开了本申请的特定实施方式，其表明了其中可以采用本申请的原则的部分实施方式，应了解的是，本申请不限于所描述的实施方式，相反，本申请包括落入所附权利要求的范围内的全部修改、变型以及等同物。下面结合附图对本申请的各种实施方式进行说明。这些实施方式只是示例性的，不是对本申请的限制。
在本申请实施例中，术语“第一”、“第二”等用于对不同元素从称谓上进行区分，但并不表示这些元素的空间排列或时间顺序等，这些元素不应被这些术语所限制。术语“和/或”包括相关联列出的术语的一种或多个中的任何一个和所有组合。术语“包含”、“包括”、“具有”等是指所陈述的特征、元素、元件或组件的存在，但并不排除存在或添加一个或多个其他特征、元素、元件或组件。
在本申请实施例中，单数形式“一”、“该”等包括复数形式，应广义地理解为“一种”或“一类”而并不是限定为“一个”的含义；此外术语“该”应理解为既包括单数形式也包括复数形式，除非上下文另外明确指出。此外术语“根据”应理解为“至少部分根据……”，术语“基于”应理解为“至少部分基于……”，除非上下文另外明确指出。
在本申请实施例中，术语“通信网络”或“无线通信网络”可以指符合如下任意通信标准的网络，例如长期演进(LTE，Long Term Evolution)、增强的长期演进(LTE-A，LTE-Advanced)、宽带码分多址接入(WCDMA，Wideband Code Division Multiple Access)、高速报文接入(HSPA，High-Speed Packet Access)等等。
并且，通信系统中设备之间的通信可以根据任意阶段的通信协议进行，例如可以包括但不限于如下通信协议：1G(generation)、2G、2.5G、2.75G、3G、4G、4.5G以及未来的5G、新无线(NR，New Radio)等等，和/或其他目前已知或未来将被开发的通信协议。
在本申请实施例中，术语“网络设备”例如是指通信系统中将终端设备接入通信网络并为该终端设备提供服务的设备。网络设备可以包括但不限于如下设备：基站(BS，Base Station)、接入点(AP、Access Point)、发送接收点(TRP，Transmission Reception Point)、广播发射机、移动管理实体(MME，Mobile Management Entity)、网关、服务器、无线网络控制器(RNC，Radio Network Controller)、基站控制器(BSC，Base Station Controller)等等。
其中，基站可以包括但不限于：节点B(NodeB或NB)、演进节点B(eNodeB或eNB)以及5G基站(gNB)，等等，此外还可包括远端无线头(RRH，Remote Radio Head)、远端无线单元(RRU，Remote Radio Unit)、中继(relay)或者低功率节点(例如femto、pico等等)。并且术语“基站”可以包括它们的一些或所有功能，每个基站可以对特定的地理区域提供通信覆盖。术语“小区”可以指的是基站和/或其覆盖区域，这取决于使用该术语的上下文。
在本申请实施例中，术语“用户设备”(UE，User Equipment)或者“终端设备”(TE，Terminal Equipment)例如是指通过网络设备接入通信网络并接收网络服务的设备。终端设备可以是固定的或移动的，并且也可以称为移动台(MS，Mobile Station)、终端、用户台(SS，Subscriber Station)、接入终端(AT，Access Terminal)、站，等等。
其中，终端设备可以包括但不限于如下设备：蜂窝电话(Cellular Phone)、个人 数字助理(PDA，Personal Digital Assistant)、无线调制解调器、无线通信设备、手持设备、机器型通信设备、膝上型计算机、无绳电话、智能手机、智能手表、数字相机，等等。
再例如，在物联网(IoT，Internet of Things)等场景下，终端设备还可以是进行监控或测量的机器或装置，例如可以包括但不限于：机器类通信(MTC，Machine Type Communication)终端、车载通信终端、设备到设备(D2D，Device to Device)终端、机器到机器(M2M，Machine to Machine)终端，等等。
以下通过示例对本申请实施例的场景进行说明，但本申请不限于此。
图1是本申请的通信系统的一示意图，示意性说明了以终端设备和网络设备为例的情况，如图1所示，通信系统100可以包括网络设备101和终端设备102(为简单起见，图1仅以一个终端设备为例进行说明)。
在本申请实施例中，网络设备101和终端设备102之间可以进行现有的业务或者未来可实施的业务。例如，这些业务包括但不限于：增强的移动宽带(eMBB，enhanced Mobile Broadband)、大规模机器类型通信(mMTC，massive Machine Type Communication)和高可靠低时延通信(URLLC，Ultra-Reliable and Low-Latency Communication)，等等。
其中，终端设备102可以向网络设备101发送数据，例如使用授权或免授权传输方式。终端设备101可以接收一个或多个终端设备102发送的数据，并向终端设备102反馈信息，例如确认ACK/非确认NACK信息等，终端设备102根据反馈信息可以确认结束传输过程、或者还可以再进行新的数据传输，或者可以进行数据重传。
此外，在终端设备102接入网络设备101之前，网络设备101可以向终端设备102发送与系统信息有关的信息，终端设备102对接收到的信息进行检测，以实现下行同步，并与网络设备101建立连接。
以下以将通信系统中的网络设备和终端设备中的一者作为发送端，将另一者作为接收端为例进行说明，但本申请不限于此，发送端和/或接收端还可以是其他的设备。例如，本申请不仅适用于网络设备和终端设备之间的信号传输，还可以适用于两个终端设备之间的信号传输。
实施例1
本申请实施例1提供一种对媒体接入控制层的控制单元(MAC CE，Media Access Control Control Element)进行确认的方法，该方法由第一设备执行。
图2是本实施例的对MAC CE进行确认的方法的一个示意图，如图2所示，该方法包括：
步骤201、第一设备接收第二设备发送的MAC CE；
步骤202、该第一设备发送用于确认该第一设备成功接收到该MAC CE的确认MAC CE。
根据本实施例，第一设备发送确认MAC CE，由此，能够确认该第一设备成功接收到MAC CE，从而提高MAC CE的可靠性。
在本实施例中，第一设备是接收MAC CE并发送确认MAC CE的设备，该第一设备可以是网络设备和终端设备中的一者。第二设备是发送MAC CE并接收确认MAC CE的设备，该第二设备可以是网络设备和终端设备中的另一者。第一设备和第二设备进行通信，并构成通信系统。
在本实施例中，当该第一设备被该第二设备指示时，该第一设备可以发送该确认MAC CE；此外，当该第一设备不被该第二设备指示时，该第一设备不发送该确认MAC CE。由此，该第二设备能够针对各MAC CE进行指示，以使该第一设备对该MAC CE发送确认MAC CE。
在一个实施方式中，该第二设备发送的该MAC CE被用于指示该第一设备发送该确认MAC CE。
例如，该第二设备发送的该MAC CE的数据部分或子头(subheader)部分的一个字段被用于指示该第一设备发送该确认MAC CE。在一个实例中，该第二设备发送的该MAC CE的数据部分或子头部分的一个字段被设置为1时，指示该第一设备发送对该MAC CE的确认MAC CE；此外，当该一个字段被设置为0时，该第一设备不发送对该MAC CE的确认MAC CE。反之亦可。
又例如，该第二设备发送的该MAC CE使用的逻辑信道标识(LCID)被用于指示该第一设备发送该确认MAC CE。在一个实例中，每个MAC CE可以对应至少两个LCID，如LCID1和LCID2，当该第一设备接收到的该MAC CE使用LCID1时，该第一设备发送对该MAC CE的确认MAC CE；此外，当该第一设备接收到的该MAC CE使用LCID2时，该第一设备不发送对该MAC CE的确认MAC CE。
再例如，该第二设备发送的该MAC CE在该第一设备接收到的媒体接入控制层的协议数据单元(Media Access Control Protocol Data Unit，MAC PDU)中的位置被用于指示该第一设备发送该确认MAC CE。在一个实例中，当该第一设备接收到的该MAC CE在整个MAC PDU的后面，即在媒体接入控制层的服务数据单元(Media Access Control Service Data Unit，MAC SDU)之后时，该第一设备发送对该MAC CE的确认MAC CE；此外，当该第一设备接收到的MAC CE在整个MAC PDU的前面，即在MAC SDU之前时，该第一设备不发送对该MAC CE的确认MAC CE。反之亦可。
在本实施例中，该第二设备发送的其他信息也可以被用于指示该第一设备发送该确认MAC CE。
在本实施例中，当该第一设备被该第一设备和该第二设备中的网络设备配置时，该第一设备发送该确认MAC CE。其中，当该第一设备是终端设备，该第二设备是网络设备时，可以由作为该第二设备的网络设备对第一设备进行配置；当该第一设备是网络设备，该第二设备是终端设备时，可以由作为该第一设备的网络设备对该第一设备自身进行配置。由此，该第一设备能够根据网络设备的配置来发送该确认MAC CE，而无需该第二设备针对各MAC CE进行指示。
在一个实施方式中，该网络设备可以将该第一设备配置为：当该第一设备在收到第一网络信令的时刻或该第一网络信令所指示的时刻起的持续时间内，发送确认MAC CE。其中，该第一网络信令例如可以是：物理层信令，或MAC CE，或无线资源控制(Radio Resource Control，RRC)信令，或其它网络信令。该第一网络信令所指示的时刻例如可以是：该第一网络信令所指示的系统帧、或子帧、或时隙、或符号位置等的时刻。
例如，该持续时间的长度可以由该网络设备配置的定时器决定，和/或该网络设备将该第一设备配置为在收到第二网络信令的时刻或该第二网络信令所指示的时刻，结束发送该确认MAC CE。其中，该第二网络信令例如可以是：物理层信令，或MAC CE，或无线资源控制(Radio Resource Control，RRC)信令，或其它网络信令。该第二网络信令所指示的时刻例如可以是：该第二网络信令所指示的系统帧、或子帧、或时隙、或符号位置等的时刻。
在一个实例中，该第一设备被该网络设备配置为：从该第一设备收到第一网络信 令的时刻开始，或者从该第一网络信令所指示的系统帧、子帧、时隙或符号位置等的时刻开始，该第一设备对接收到的MAC CE发送该确认MAC CE；并且，在该第一设备收到第一网络信令的时刻，或者在该第一网络信令所指示的系统帧、子帧、时隙或符号位置等的时刻，该第一设备启动一个定时器，该定时器的参数由该网络设备配置；并且，在该定时器运行期间，该第一设备对接收到的MAC CE发送确认MAC CE。此外，该第一设备还被该网络设备配置为：当该定时器超时或没有运行时，该第一设备不对接收到的MAC CE发送确认MAC CE。此外，该第一设备还被该网络设备配置为：在该第一设备收到第二网络信令的时刻，或者在该第二网络信令所指示的系统帧、子帧、时隙或符号位置等的时刻，该第一设备停止对接收到的MAC CE发送确认MAC CE，此外，如果该定时器仍在运行，该第一设备还可以停止该定时器。
在本实施例中，当该网络设备为该第一设备配置了具有高于预定优先级阈值的逻辑信道时，该第一设备发送该确认MAC CE。在一个实施方式中，网络设备可以配置或预定义一个优先级阈值，当该第一设备具有高于该优先级阈值的逻辑信道时，例如该第一设备具有URLLC的业务时，该第一设备发送对接收到的该MAC CE的确认MAC CE；此外，当该第一设备不具有高于该优先级阈值的逻辑信道时，该第一设备不发送对接收到的该MAC CE的确认MAC CE。
在本实施例中，该第一设备发送的确认MAC CE与该第一设备接收的该MAC CE具有不同的数据格式，和/或不同的数据部分的内容，和/或不同的子头部分的内容，由此，可以将该确认MAC CE与该MAC CE区分开。
在一个实施方式中，确认MAC CE的数据格式可以包括0比特的数据部分和子头部分，其中，该子头部分的LCID字段的取值与该确认MAC CE所确认的该MAC CE所使用的LCID取值相同。由此，能够节省该确认MAC CE的数据部分的字节开销。
例如，重复传输的激活、去激活的MAC CE使用的LCID可以被网络设备配置为“111000”，当第一设备需要对该MAC CE发送确认MAC CE时，该确认MAC CE的数据格式为具有0比特的数据部分，并在子头中使用“111000”作为LCID；第二设备接收到子头的LCID字段为“111000”并且数据部分长度为0的MAC CE时，判定该MAC CE是对重复传输的激活、去激活的MAC CE进行确认的确认MAC CE。
在另一个实施方式中，该确认MAC CE的数据格式包括数据部分和子头部分， 其中，该数据部分的LCID字段的取值与该确认MAC CE所确认的该MAC CE所使用的LCID取值相同，该子头部分的LCID字段的取值为预定取值。由此，各确认MAC CE具有统一的数据格式。
例如，重复传输的激活、去激活的MAC CE使用的LCID被网络设备配置为“111000”，当该第一设备对该MAC CE发送确认MAC CE时，该确认MAC CE的数据格式为：数据部分包含一个LCID字段，取值设置为“111000”，并且，子头部分使用具有预定取值的LCID，例如“110111”。第二设备在接收到子头的LCID字段为“110111”，并且数据部分的LCID字段为“111000”的MAC CE时，判定该MAC CE是对重复传输的激活、去激活的MAC CE进行确认的确认MAC CE。
在又一个实施方式中，该确认MAC CE的数据格式包括子头部分和0比特的数据部分，其中，该子头部分的LCID字段的取值为预定取值。由此，各确认MAC CE具有统一的数据格式，并且，能够节省该确认MAC CE的数据部分的字节开销。
例如，重复传输的激活、去激活的MAC CE使用的LCID被网络设备配置为“111000”。在第二设备发送该MAC CE之后的一段配置的时间内，例如一个预配置的窗口或定时器允许期间，该第一设备对该MAC CE发送确认MAC CE时，该确认MAC CE的数据格式为：数据部分为0比特，并且，子头部分使用具有预定取值的LCID，例如“110111”。该第二设备在发送重复传输的激活、去激活的MAC CE后一段时间内，接收到子头的LCID字段为“110111”并且数据部分长度为0的MAC CE时，判定该MAC CE是对重复传输的激活、去激活的MAC CE进行确认的确认MAC CE。
根据本实施例，第一设备针对接收到的MAC CE发送确认MAC CE，由此，能够确认该第一设备成功接收到该MAC CE，从而提高MAC CE的可靠性。此外，该确认MAC CE区别于该MAC CE，由此，该确认MAC CE能够被容易地识别。
实施例2
本实施例2提供一种对MAC CE进行确认的方法，该方法由第二设备执行。
图3是本实施例2中对MAC CE进行确认的方法的示意图，如图3所示，该方法包括：
步骤301、第二设备向第一设备发送MAC CE；以及
步骤302、第二设备接收该第一设备发送的用于确认该第一设备成功接收到该MAC CE的确认MAC CE。
根据本实施例，该第二设备接收该第一设备发送的用于确认该第一设备成功接收到该MAC CE的确认MAC CE，从而提高MAC CE的可靠性。
在本实施例中，关于第一设备和第二设备的说明，可以参考实施例1。
在本实施例中，当该第二设备进行了指示时，该第一设备发送该确认MAC CE。例如，该第二设备发送的该MAC CE被用于指示该第一设备发送该确认MAC CE；或者，该MAC CE的数据部分或子头部分的一个字段被用于进行该指示；或者，该MAC CE使用的逻辑信道标识(LCID)被用于进行该指示；或者，该MAC CE在该第一设备接收到的媒体接入控制层的协议数据单元(Media Access Control Protocol Data Unit，MAC PDU)中的位置被用于进行该指示。
在本实施例中，当该第一设备和该第二设备中的网络设备对该第一设备进行了配置时，该第一设备发送该确认MAC CE。例如，网络设备将该第一设备配置为，在收到第一网络信令的时刻或该第一网络信令所指示的时刻起的持续时间内，发送确认MAC CE；其中，该持续时间的长度由该网络设备配置的定时器决定，和/或，该网络设备还将该第一设备配置为在收到第二网络信令的时刻或该第二网络信令所指示的时刻，结束发送该确认MAC CE。
在本实施例中，当网络设备为该第一设备配置了具有高于预定优先级阈值的逻辑信道时，该第一设备发送该确认MAC CE。
在本实施例中，该确认MAC CE与该MAC CE具有不同的数据格式，和/或不同的数据部分的内容，和/或不同的子头部分的内容。例如，该确认MAC CE的数据格式包括0比特的数据部分和子头部分，其中，该子头部分的LCID字段的取值与该确认MAC CE所确认的该MAC CE所使用的LCID取值相同；或者，该确认MAC CE的数据格式包括数据部分和子头部分，其中，该数据部分的LCID字段的取值与该确认MAC CE所确认的该MAC CE所使用的LCID取值相同，该子头部分的LCID字段的取值为预定取值；或者，该确认MAC CE的数据格式包括0比特的数据部分和子头部分，该子头部分的LCID字段的取值为预定取值。
在本实施例中，与实施例1相同部分的说明，可以参考实施例1，本实施例不再进行说明。
根据本实施例，第二设备接收第一设备针对接收到的MAC CE发送的确认MAC CE，由此，能够确认该第一设备成功接收到该MAC CE，从而提高MAC CE的可靠性。此外，该确认MAC CE区别于该MAC CE，由此，该确认MAC CE能够被第二设备容易地识别。
实施例3
本实施例3提供一种对MAC CE进行确认的装置。由于该装置解决问题的原理与实施例1的方法类似，因此其具体的实施可以参考实施例1的方法的实施，内容相同之处不再重复说明。
图4是本实施例3的对MAC CE进行确认的装置的一个示意图。如图4所示，装置400包括：第一接收单元401和第一发送单元402。
在本实施例中，第一接收单元401用于接收第二设备发送的MAC CE；第一发送单元402用于发送用于确认该第一接收单元成功接收到该MAC CE的确认MAC CE。
在本实施例中，如图4所示，该装置400还可以包括：第一控制单元403。
在本实施例中，当该控制单元403判定为该第一设备被该第二设备指示时，控制该第一发送单元402发送该确认MAC CE。
在一个实施方式中，该第一控制单元403根据该第二设备发送的该MAC CE判定该第一设备被该第二设备指示发送该确认MAC CE。例如，该第一控制单元403根据该MAC CE的数据部分或子头部分的一个字段判定该指示；或者，该第一控制单元根据该MAC CE使用的逻辑信道标识(LCID)判定该指示；或者，该第一控制单元根据该MAC CE在该第一设备接收到的媒体接入控制层的协议数据单元(Media Access Control Protocol Data Unit，MAC PDU)中的位置判定该指示。
在另一个实施方式中，当控制单元403被该第一设备和该第二设备中的网络设备配置时，该控制单元403控制第一发送单元402发送该确认MAC CE。
例如，该网络设备将该控制单元配置为进行如下控制：在该第一接收单元401收到第一网络信令的时刻或该第一网络信令所指示的时刻起的持续时间内，控制该第一发送单元402发送该确认MAC CE。其中，该持续时间的长度由该网络设备配置的定时器决定；或者，该控制单元还被该网络设备配置为进行如下控制：在该第一接收单元收到第二网络信令的时刻或该第二网络信令所指示的时刻，控制该第一发送单元 结束发送该确认MAC CE。
在又一个实施方式中，该控制单元403被该网络设备配置为进行如下控制：当该网络设备为该第一设备配置了具有高于预定优先级阈值的逻辑信道时，该控制单元403控制该第一发送单元402发送该确认MAC CE。
此外，当该第一设备是网络设备时，该装置400还可以具有配置单元(未图示)，该配置单元对该控制单元403进行配置，从而使该控制单元403被配置为进行上述的控制。
在实施例中，该确认MAC CE与该MAC CE具有不同的数据格式，和/或不同的数据部分的内容，和/或不同的子头部分的内容。例如，该确认MAC CE的数据格式包括0比特的数据部分和子头部分，其中，该子头部分的LCID字段的取值与该确认MAC CE所确认的该MAC CE所使用的LCID取值相同；或者，该确认MAC CE的数据格式包括数据部分和子头部分，其中，该数据部分的LCID字段的取值与该确认MAC CE所确认的该MAC CE所使用的LCID取值相同，该子头部分的LCID字段的取值为预定取值；或者，该确认MAC CE的数据格式包括0比特的数据部分和子头部分，该子头部分的LCID字段的取值为预定取值。
根据本实施例，第一设备针对接收到的MAC CE发送确认MAC CE，由此，能够确认该第一设备成功接收到该MAC CE，从而提高MAC CE的可靠性。此外，该确认MAC CE区别于该MAC CE，由此，该确认MAC CE能够被容易地识别。
实施例4
本实施例4提供一种对MAC CE进行确认的装置。由于该装置解决问题的原理与实施例2的方法类似，因此其具体的实施可以参考实施例2的方法的实施，内容相同之处不再重复说明。
图5是本实施例4的对MAC CE进行确认的装置的一个示意图。如图5所示，装置500包括：第二发送单元501和第二接收单元502。
在本实施例中，第二发送单元501用于向第一设备发送MAC CE；第二接收单元502用于接收该第一设备发送的用于确认该第一设备成功接收到该MAC CE的确认MAC CE。
在本实施例中，如图5所示，该装置500还具有第一指示单元503，当第一指示 单元503进行了指示时，该第一设备发送该确认MAC CE。
在一个实施方式中，该第一指示单元503对该第二设备发送的该MAC CE进行设置，以指示该第一设备发送该确认MAC CE。例如，该第一指示单元503对该MAC CE的数据部分或子头部分的一个字段进行设置，以进行该指示；或者，该第一指示单元503对该MAC CE使用的逻辑信道标识(LCID)进行设置，以进行该指示；或者，该第一指示单元503对该MAC CE在媒体接入控制层的协议数据单元(MAC PDU)中的位置进行设置，以进行该指示。
在本实施例中，在该第一设备和该第二设备中的网络设备进行了配置时，该第一设备发送该确认MAC CE。其中，如图5所示，在该第二设备是该网络设备时，该装置500还可以具有配置单元504。实施例4中的配置单元504与实施例3中该的配置单元是指同一个配置单元。
在一个实施方式中，该配置单元504配置该第一设备在收到第一网络信令的时刻或该第一网络信令所指示的时刻起的持续时间内，发送该确认MAC CE。其中，该持续时间的长度由该配置单元配置的定时器决定；和/或，该配置单元504配置该第一设备在收到第二网络信令的时刻或该第二网络信令所指示的时刻，结束发送该确认MAC CE。
在另一个实施方式中，该配置单元504为该第一设备配置逻辑信道，并且，将该第一设备配置为：当该配置单元504为该第一设备配置了具有高于预定优先级阈值的逻辑信道时，该第一设备发送该确认MAC CE。
在实施例中，该确认MAC CE与该MAC CE具有不同的数据格式，和/或不同的数据部分的内容，和/或不同的子头部分的内容。例如，该确认MAC CE的数据格式包括0比特的数据部分和子头部分，其中，该子头部分的LCID字段的取值与该确认MAC CE所确认的该MAC CE所使用的LCID取值相同；或者，该确认MAC CE的数据格式包括数据部分和子头部分，其中，该数据部分的LCID字段的取值与该确认MAC CE所确认的该MAC CE所使用的LCID取值相同，该子头部分的LCID字段的取值为预定取值；或者，该确认MAC CE的数据格式包括0比特的数据部分和子头部分，该子头部分的LCID字段的取值为预定取值。
根据本实施例，第二设备接收第一设备针对接收到的MAC CE发送的确认MAC CE，由此，能够确认该第一设备成功接收到该MAC CE，从而提高MAC CE的可靠 性。此外，该确认MAC CE区别于该MAC CE，由此，该确认MAC CE能够被第二设备容易地识别。
实施例5
本实施例5提供一种设备，该设备为第一设备，由于该设备解决问题的原理于实施例1的方法类似，因此其具体的实施可以参考实施例1的方法实施，内容相同之处不再重复说明。
在本实施例中，该第一设备可以是网络设备，也可以是终端设备。
图6是本发明实施例的网络设备构成示意图。如图6所示，网络设备600可以包括：中央处理器(CPU)601和存储器602；存储器602耦合到中央处理器601。其中该存储器62可存储各种数据；此外还存储数据处理的程序，并且在中央处理器801的控制下执行该程序。
在一个实施方式中，装置400的功能可以被集成到中央处理器601中。其中，中央处理器601可以被配置为实现实施例1的对MAC CE进行确认的方法。
例如，中央处理器601可以被配置为进行控制，以使网络设备600执行实施例1的方法。
另外，该中央处理器601的其他配置方式可以参考实施例1，此处不再赘述。
在另一个实施方式中，上述装置400可以与中央处理器601分开配置，例如，可以将装置400配置为与中央处理器601连接的芯片，如图6所示的单元，通过中央处理器601的控制来实现装置400的功能。
此外，如图6所示，网络设备600还可以包括：收发机603和天线604等；其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，网络设备600也并不是必须要包括图6中所示的所有部件；此外，网络设备600还可以包括图6中没有示出的部件，可以参考现有技术。
图7是本申请实施例的终端设备的构成示意图。如图7所示，终端设备700可以包括：中央处理器(CPU)701和存储器702；存储器702耦合到中央处理器701。其中该存储器702可存储各种数据；此外还存储数据处理的程序，并且在中央处理器701的控制下执行该程序，以对MAC CE进行确认。
在一个实施方式中，实施例3的装置400的功能可以被集成到中央处理器701 中。其中，中央处理器701可以被配置为实现实施例1所述的对MAC CE进行确认的方法。
例如，中央处理器701可以被配置为进行控制，以使终端设备700执行实施例1的方法。
另外，该中央处理器701的其他配置方式可以参考实施例1，此处不再赘述。
在另一个实施方式中，上述装置400可以与中央处理器701分开配置，例如，可以将装置400配置为与中央处理器701连接的芯片，如图7所示的单元，通过中央处理器701的控制来实现装置400的功能。
此外，如图7所示，终端设备700还可以包括通信模块703、输入单元704、显示器706、音频处理器705、天线709和电源708等。其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，终端设备700也并不是必须要包括图7中所示的所有部件；此外，终端设备700还可以包括图7中没有示出的部件，可以参考现有技术。
根据本实施例，第一设备针对接收到的MAC CE发送确认MAC CE，由此，能够确认该第一设备成功接收到该MAC CE，从而提高MAC CE的可靠性。此外，该确认MAC CE区别于该MAC CE，由此，该确认MAC CE能够被容易地识别。
实施例6
本实施例6提供一种设备，该设备为第二设备，由于该设备解决问题的原理于实施例2的方法类似，因此其具体的实施可以参考实施例2的方法实施，内容相同之处不再重复说明。
在本实施例中，该第二设备可以是网络设备，该网络设备的示意图可以与图6相同。
在一个实施方式中，实施例4的装置500的功能可以被集成到网络设备600的中央处理器601中。其中，中央处理器601可以被配置为实现实施例2的对MAC CE进行确认的方法。
例如，中央处理器601可以被配置为进行控制，以使网络设备600执行实施例2的方法。
另外，该中央处理器601的其他配置方式可以参考实施例2，此处不再赘述。
在另一个实施方式中，上述装置500可以与中央处理器601分开配置，例如，可以将装置500配置为与中央处理器601连接的芯片，如图6所示的单元，通过中央处理器601的控制来实现装置500的功能。
在本实施例中，该第二设备也可以是终端设备，该终端设备的示意图可以与图7相同。
在一个实施方式中，实施例4的装置500的功能可以被集成到终端设备700的中央处理器701中。其中，中央处理器701可以被配置为实现实施例2所述的对MAC CE进行确认的方法。
例如，中央处理器701可以被配置为进行控制，以使终端设备700执行实施例2的方法。
另外，该中央处理器701的其他配置方式可以参考实施例2，此处不再赘述。
在另一个实施方式中，上述装置500可以与中央处理器701分开配置，例如，可以将装置500配置为与中央处理器701连接的芯片，如图7所示的单元，通过中央处理器701的控制来实现装置500的功能。
根据本实施例，第二设备接收第一设备针对接收到的MAC CE发送的确认MAC CE，由此，能够确认该第一设备成功接收到该MAC CE，从而提高MAC CE的可靠性。此外，该确认MAC CE区别于该MAC CE，由此，该确认MAC CE能够被第二设备容易地识别。
实施例7
本实施例7提供一种通信系统，其至少包括实施例5中的第一设备和实施例6中的第二设备，其中，该第一设备可以是网络设备，该第二设备可以是终端设备，或者，该第一设备可以是终端设备，该第二设备可以是网络设备。实施例5和实施例6的内容被合并于此，此处不再赘述。
根据本实施例，第二设备接收第一设备针对接收到的MAC CE发送的确认MAC CE，由此，能够确认该第一设备成功接收到该MAC CE，从而提高MAC CE的可靠性。此外，该确认MAC CE区别于该MAC CE，由此，该确认MAC CE能够被第二设备容易地识别。
本发明实施例还提供一种存储有计算机可读程序的存储介质，其中该计算机可读 程序使得对MAC CE进行确认的装置或第一设备执行实施例1所述的对MAC CE进行确认的方法。
本发明实施例还提供一种计算机可读程序，其中当在对MAC CE进行确认的装置或第一设备中执行该程序时，该程序使得该对MAC CE进行确认的装置或第一设备执行实施例1该的对MAC CE进行确认的方法。
本发明实施例还提供一种存储有计算机可读程序的存储介质，其中该计算机可读程序使得对MAC CE进行确认的装置或第二设备执行实施例2该的确定缓存状态报告的方法。
本发明实施例还提供一种计算机可读程序，其中当在对MAC CE进行确认的装置或第二设备中执行该程序时，该程序使得该对MAC CE进行确认的装置或第二设备执行实施例2所述的对MAC CE进行确认的方法。
实施例8
本申请实施例8提供一种应用无线资源控制(Radio Resource Control，RRC)配置信令中的配置的方法，该方法由终端设备执行。
在现有技术中，网络设备无法知道传输某个RRC配置信令的物理时刻和使用的物理资源，因而无法准确知道终端设备成功接收该RRC配置信令的时刻，从而导致该网络设备和该终端侧应用新配置的时刻不同步，进而造成该网络设备和该终端设备在一段时间内应用的配置不一致。该段时间内，该终端设备可能应用了与网络设备不匹配的配置，导致数据传输发生错误。这段时间内该终端设备应用的该不匹配的配置，对于URLLC业务是无法容忍的。
本实施例的应用RRC配置信令中的配置的方法能够避免由于网络设备和终端设备应用RRC配置信令中的配置的时刻不匹配所造成的数据传输错误。
图8是本实施例的应用RRC配置信令中的配置的方法的一个示意图，如图8所示，该方法包括：
步骤801、终端设备接收网络设备发送的RRC配置信令；以及
步骤802、该终端设备在该网络设备指示的或预定义的时刻开始应用该RRC配置信令中的配置。
根据本实施例，终端设备在该网络设备指示的或预定义的时刻开始应用该RRC 配置信令中的配置，因此，能够避免由于网络设备和终端设备应用RRC配置信令中的配置的时刻不匹配所造成的数据传输错误。
在本实施例的步骤802中，该终端设备可以在该网络设备指示的时刻开始应用该RRC配置信令中的配置，其中，该网络设备指示的该时刻可以是至少两个备选时刻中的一个时刻。
在本实施例中，该备选时刻可以包括第一时刻，该第一时刻是该终端设备成功接收该RRC配置信令的时刻，或该终端设备发送或向下层递交与该RRC配置信令所对应的RRC配置成功(RRC complete)消息的时刻；和/或，该备选时刻可以包括第二时刻，该第二时刻是该网络设备指示的或预定义的时刻，例如，该第二时刻可以是特定的系统帧号、特定的子帧号、特定的时隙位置、特定的符号位置等的时刻。
在一个实例中，RRC配置信令是对终端设备的URLLC业务所使用资源的重配置设置信令。该RRC配置信令中有一个字段用于指示终端设备在第一时刻还是第二时刻应用该RRC配置信令中的配置。如果该字段设置为第一取值，则终端设备会在第一时刻开始应用该配置，该第一时刻例如是，在成功接收该RRC信令的时刻或在UE发送或向下层递交该RRC信令所对应的RRC complete消息的时刻；如果该字段设置为第二取值，则该终端设备会在第二时刻应用该配置，该第二时刻可以是网络设备指示的特定时刻，例如，网络设备预配置每一个系统帧号(System Frame Number SFN)中的奇数号子帧的第一个子帧的第一个符号位置的时刻作为第二时刻。
根据本实施例，终端设备在该网络设备指示的或预定义的时刻开始应用该RRC配置信令中的配置，因此，能够避免由于网络设备和终端设备应用RRC配置信令中的配置的时刻不匹配所造成的数据传输错误。
实施例9
本实施例9提供一种应用无线资源控制(Radio Resource Control，RRC)配置信令中的配置的方法，该方法由网络设备执行。
图9是本实施例9中应用RRC配置信令中的配置的方法的一个示意图，如图9所示，该方法包括：
步骤901、网络设备应用该网络设备发送的RRC配置信令中的配置。
在本实施例中，该网络设备应用该配置的时刻由与该配置有关的业务决定。其中， 该业务是指高可靠性低时延业务，例如，超可靠性低时延(Ultra Reliable&Low Latency Communication，URLLC)业务。
在一个实施方式中，在该业务将要发起，或该RRC配置信令在该业务发起前发送的情况下，该网络设备早于该终端设备应用该配置。其中，对于该业务将要发起的判定，可以参考现有技术，例如：由网络设备发起该业务的情况下，网络设备能够对该业务将要发起进行判定；由终端设备发起该业务的情况下，网络设备能够进行监听，从而对该业务将要发起进行判定。
在上述实施方式中，该网络设备早于该终端设备应用该配置是指在网络设备发送或者向下层递交该RRC配置信令所对应的时刻应用该配置。
根据上述实施方式，可以保证网络设备早于终端设备应用为URLLC业务进行的配置。即使网络设备和终端设备对该配置的应用时刻不相同，也可以保证将要发起的URLLC业务的数据可以在正确的配置下进行传输，进而保证URLLC业务的数据可靠性。
例如，终端设备的URLLC业务还没有开始，而是将要发起URLLC业务，网络设备通过该RRC配置信令为URLLC业务做准备，在网络设备发送该RRC配置信令的情况下，在该网络设备发送或者向下层递交该RRC配置信令的时刻，该网络设备可以应用该配置。
在另一个实施方式中，在该业务将要结束，或该RRC配置信令在该业务发起后或进行中发送的情况下，该网络设备晚于该终端设备应用该配置。其中，该网络设备晚于该终端设备应用该配置是指在网络侧接收到与该RRC配置消息所对应的RRC complete消息的时刻应用该配置。
根据上述实施方式，可以保证网络设备晚于终端设备应用在停止URLLC业务后使用的配置。即使网络设备和终端设备对该配置的应用时刻不相同，也可以保证正在进行的URLLC业务的数据可以在正确的配置下进行传输，进而保证URLLC业务的数据可靠性。
例如，终端设备的URLLC已经开始而且正在进行，当该URLLC业务将要结束时，网络设备通过该RRC配置更改资源的相关配置，此时网络设备可以在接收到与该RRC配置信令所对应的RRC complete消息的时刻应用该配置。
在本实施例中，如图9所示，该方法还可以包括：
步骤902、网络设备向终端设备发送RRC配置信令；以及
步骤903、该网络设备指示该终端设备开始应用该RRC配置信令中的配置的时刻。
在本实施例的步骤902中，该网络设备可以指示该终端设备在至少两个备选时刻中的一个时刻开始应用该RRC配置信令中的配置。
在本实施例中，该备选时刻包括第一时刻，该第一时刻是该终端设备成功接收该RRC配置信令的时刻，或该终端设备发送或向下层递交与该RRC配置信令所对应的RRC配置成功(RRC complete)消息的时刻；和/或，该备选时刻包括第二时刻，该第二时刻是该网络设备指示的或预定义的时刻。关于第一时刻和第二时刻的说明，可以参考实施例8，本实施例不再重复。
根据本实施例，网络设备可以早于终端设备应用为URLLC业务进行的配置，和/或晚于终端设备应用在停止URLLC业务后使用的配置，由此，可以保证将要发起的URLLC业务和/或正在进行的URLLC业务的数据可以在正确的配置下进行传输，进而保证URLLC业务的数据可靠性；此外，该网络设备指示终端设备开始应用该RRC配置信令中的配置的时刻，因此，能够避免由于网络设备和终端设备应用RRC配置信令中的配置的时刻不匹配所造成的数据传输错误。
实施例10
本实施例10提供一种应用无线资源控制(Radio Resource Control，RRC)配置信令中的配置的装置，应用于终端设备。由于该装置解决问题的原理与实施例8的方法类似，因此其具体的实施可以参考实施例8的方法的实施，内容相同之处不再重复说明。
图10是本实施例10的应用RRC配置信令中的配置的装置的一个示意图。如图10所示，装置1000包括第三接收单元1001和第一应用单元1002。
在本实施例中，第三接收单元1001用于接收网络设备发送的RRC配置信令；第一应用单元1002用于在该网络设备指示的或预定义的时刻开始将该RRC配置信令中的配置应用于终端设备。
在本实施例中，该第一应用单元1002在该网络设备指示的时刻开始应用该RRC配置信令中的配置，其中，该网络设备指示的该时刻是至少两个备选时刻中的一个时 刻。
在本实施例中，该备选时刻包括第一时刻，该第一时刻是该终端设备成功接收该RRC配置信令的时刻，或该终端设备发送或向下层递交与该RRC配置信令所对应的RRC配置成功(RRC complete)消息的时刻；和/或，该备选时刻包括第二时刻，该第二时刻是该网络设备指示的或预定义的时刻。
根据本实施例，终端设备在该网络设备指示的或预定义的时刻开始应用该RRC配置信令中的配置，因此，能够避免由于网络设备和终端设备应用RRC配置信令中的配置的时刻不匹配所造成的数据传输错误。
实施例11
本实施例11提供一种应用无线资源控制(Radio Resource Control，RRC)配置信令中的配置的装置，应用于网络设备。由于该装置解决问题的原理与实施例9的方法类似，因此其具体的实施可以参考实施例9的方法的实施，内容相同之处不再重复说明。
图11是本实施例11的应用RRC配置信令中的配置的装置的一个示意图。如图11所示，装置1100包括第二应用单元1101。
在本实施例中，第二应用单元1101用于将该网络设备发送的RRC配置信令中的配置应用于该网络设备，其中，该第二应用单元1101应用该配置的时刻由与该配置有关的业务决定。该业务例如是指超可靠性低时延(Ultra Reliable&Low Latency Communication，URLLC)业务。
在本实施例中，在该业务将要发起，或该RRC配置信令在该业务发起前发送的情况下，该第二应用单元早于该终端设备将该配置应用于该网络设备。其中，该第二应用单元早于该终端设备将该配置应用于该网络设备是指在网络设备发送或者向下层递交该RRC配置信令所对应的时刻应用该配置。
在本实施例中，在该业务将要结束，或该RRC配置信令在该业务发起后或进行中发送的情况下，该第二应用单元晚于该终端设备将该配置应用于该网络设备。其中，该第二应用单元晚于该终端设备将该配置应用于该网络设备是指在网络设备接收到与该RRC配置消息所对应的RRC complete消息的时刻应用该配置。
在本实施例中，如图11所示，该装置1100还包括：第三发送单元1102和第二 指示单元1103。
在本实施例中，第三发送单元1102用于向该终端设备发送RRC配置信令；第二指示单元1103用于指示该终端设备开始应用该RRC配置信令中的配置的时刻。
在本实施例中，该第二指示单元1103指示该终端设备在至少两个备选时刻中的一个时刻开始应用该RRC配置信令中的配置。其中，该备选时刻包括第一时刻，该第一时刻是该终端设备成功接收该RRC配置信令的时刻，或该终端设备发送或向下层递交与该RRC配置信令所对应的RRC配置成功(RRC complete)消息的时刻；和/或，该备选时刻包括第二时刻，该第二时刻是该网络设备指示的或预定义的时刻。
根据本实施例，接收缓存状态报告的装置接收的缓存状态报告能够指示该缓存状态报告中包含的缓存大小与逻辑信道组之间的对应关系，便于终端设备和网络设备采用一致的、且明确的技术方案来确定逻辑信道组与BSR中包含的缓存大小之间的对应关系。
根据本实施例，网络设备可以早于终端设备应用为URLLC业务进行的配置，和/或晚于终端设备应用在停止URLLC业务后使用的配置，由此，可以保证将要发起的URLLC业务和/或正在进行的URLLC业务的数据可以在正确的配置下进行传输，进而保证URLLC业务的数据可靠性；此外，该网络设备指示终端设备开始应用该RRC配置信令中的配置的时刻，因此，能够避免由于网络设备和终端设备应用RRC配置信令中的配置的时刻不匹配所造成的数据传输错误。
实施例12
本实施例12提供一种终端设备，由于该设备解决问题的原理与实施例8的方法类似，因此其具体的实施可以参考实施例8的方法实施，内容相同之处不再重复说明。
图12是本发明实施例的终端设备构成示意图。如图12所示，终端设备1200可以包括：中央处理器(CPU)1201和存储器1202；存储器1202耦合到中央处理器1201。其中该存储器1202可存储各种数据；此外还存储数据处理的程序，并且在中央处理器1201的控制下执行该程序。
在一个实施方式中，实施例10的装置1000的功能可以被集成到中央处理器1201中。其中，中央处理器1201可以被配置为实现实施例8所述的应用RRC配置信令中的配置的方法。
例如，中央处理器1201可以被配置为进行控制，以使终端设备1200执行实施例8的方法。
另外，该中央处理器1201的其他配置方式可以参考实施例8，此处不再赘述。
在另一个实施方式中，上述装置1200可以与中央处理器1201分开配置，例如，可以将装置1000配置为与中央处理器1201连接的芯片，如图12所示的单元，通过中央处理器1201的控制来实现装置1000的功能。
此外，如图12所示，终端设备1200还可以包括通信模块1203、输入单元1204、显示器1206、音频处理器1205、天线1209和电源1208等。其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，终端设备1200也并不是必须要包括图12中所示的所有部件；此外，终端设备1200还可以包括图12中没有示出的部件，可以参考现有技术。
根据本实施例，终端设备在该网络设备指示的或预定义的时刻开始应用该RRC配置信令中的配置，因此，能够避免由于网络设备和终端设备应用RRC配置信令中的配置的时刻不匹配所造成的数据传输错误。
实施例13
本实施例13提供一种网络设备，由于该设备解决问题的原理与实施例9的方法类似，因此其具体的实施可以参考实施例9的方法实施，内容相同之处不再重复说明。
图13是本发明实施例的网络设备构成示意图。如图13所示，网络设备1300可以包括：中央处理器(CPU)1301和存储器1302；存储器1302耦合到中央处理器1301。其中该存储器1302可存储各种数据；此外还存储数据处理的程序，并且在中央处理器1301的控制下执行该程序。
在一个实施方式中，装置1100的功能可以被集成到中央处理器1301中。其中，中央处理器1301可以被配置为实现实施例9的应用RRC配置信令中的配置的方法。
例如，中央处理器1301可以被配置为进行控制，以使网络设备1300执行实施例9的方法。
另外，该中央处理器1301的其他配置方式可以参考实施例9，此处不再赘述。
在另一个实施方式中，上述装置1100可以与中央处理器1301分开配置，例如，可以将装置1100配置为与中央处理器1301连接的芯片，如图13所示的单元，通过 中央处理器1301的控制来实现装置1100的功能。
此外，如图13所示，网络设备1300还可以包括：收发机1303和天线1304等；其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，网络设备1300也并不是必须要包括图13中所示的所有部件；此外，网络设备1300还可以包括图13中没有示出的部件，可以参考现有技术。
根据本实施例，网络设备可以早于终端设备应用为URLLC业务进行的配置，和/或晚于终端设备应用在停止URLLC业务后使用的配置，由此，可以保证将要发起的URLLC业务和/或正在进行的URLLC业务的数据可以在正确的配置下进行传输，进而保证URLLC业务的数据可靠性；此外，该网络设备指示终端设备开始应用该RRC配置信令中的配置的时刻，因此，能够避免由于网络设备和终端设备应用RRC配置信令中的配置的时刻不匹配所造成的数据传输错误。
实施例14
本实施例14提供一种通信系统，其至少包括实施例12中的终端设备和实施例13中的网络设备，将其内容合并于此，此处不再赘述。
根据本实施例，能够避免由于网络设备和终端设备应用RRC配置信令中的配置的时刻不匹配所造成的数据传输错误。
本发明实施例还提供一种存储有计算机可读程序的存储介质，其中该计算机可读程序使得应用RRC配置信令中的配置的装置或终端设备执行实施例8所述的应用RRC配置信令中的配置的方法。
本发明实施例还提供一种计算机可读程序，其中当在应用RRC配置信令中的配置的装置或终端设备中执行该程序时，该程序使得该应用RRC配置信令中的配置的装置或终端设备执行实施例8所述的应用RRC配置信令中的配置的方法。
本发明实施例还提供一种存储有计算机可读程序的存储介质，其中该计算机可读程序使得应用RRC配置信令中的配置的装置或终端设备执行实施例9所述的应用RRC配置信令中的配置的方法。
本发明实施例还提供一种计算机可读程序，其中当在应用RRC配置信令中的配置的装置或终端设备中执行该程序时，该程序使得该应用RRC配置信令中的配置的 装置或终端设备执行实施例9所述的应用RRC配置信令中的配置的方法。
本发明以上的装置和方法可以由硬件实现，也可以由硬件结合软件实现。本发明涉及这样的计算机可读程序，当该程序被逻辑部件所执行时，能够使该逻辑部件实现上文所述的装置或构成部件，或使该逻辑部件实现上文所述的各种方法或步骤。本发明还涉及用于存储以上程序的存储介质，如硬盘、磁盘、光盘、DVD、flash存储器等。
结合本发明实施例描述的在各装置中的各处理方法可直接体现为硬件、由处理器执行的软件模块或二者组合。例如，图4、5、10、11中所示的功能框图中的一个或多个和/或功能框图的一个或多个组合，既可以对应于计算机程序流程的各个软件模块，亦可以对应于各个硬件模块。这些软件模块，可以分别对应于图2、3、8、9所示的各个步骤。这些硬件模块例如可利用现场可编程门阵列(FPGA)将这些软件模块固化而实现。
软件模块可以位于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、移动磁盘、CD-ROM或者本领域已知的任何其它形式的存储介质。可以将一种存储介质耦接至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息；或者该存储介质可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。该软件模块可以存储在移动终端的存储器中，也可以存储在可插入移动终端的存储卡中。例如，若设备(例如移动终端)采用的是较大容量的MEGA-SIM卡或者大容量的闪存装置，则该软件模块可存储在该MEGA-SIM卡或者大容量的闪存装置中。
针对图4、5、10、11描述的功能框图中的一个或多个和/或功能框图的一个或多个组合，可以实现为用于执行本申请所描述功能的通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或其它可编程逻辑器件、分立门或晶体管逻辑器件、分立硬件组件、或者其任意适当组合。针对图4、5、10、11描述的功能框图中的一个或多个和/或功能框图的一个或多个组合，还可以实现为计算设备的组合，例如，DSP和微处理器的组合、多个微处理器、与DSP通信结合的一个或多个微处理器或者任何其它这种配置。
以上结合具体的实施方式对本发明进行了描述，但本领域技术人员应该清楚，这些描述都是示例性的，并不是对本发明保护范围的限制。本领域技术人员可以根据本 发明的原理对本发明做出各种变型和修改，这些变型和修改也在本发明的范围内。
本申请还提供如下的附记：
1.一种应用无线资源控制(Radio Resource Control，RRC)配置信令中的配置的装置，包括：
第三接收单元，其用于接收网络设备发送的RRC配置信令；以及
第一应用单元，其用于在该网络设备指示的或预定义的时刻开始将该RRC配置信令中的配置应用于终端设备。
2.如附记1所述的装置，其中，
该第一应用单元，在该网络设备指示的时刻开始应用该RRC配置信令中的配置，其中，该网络设备指示的该时刻是至少两个备选时刻中的一个时刻。
3.如附记2所述的装置，其中，
该备选时刻包括第一时刻，该第一时刻是该终端设备成功接收该RRC配置信令的时刻，或该终端设备发送或向下层递交与该RRC配置信令所对应的RRC配置成功(RRC complete)消息的时刻。
4.如附记2所述的装置，其中，
该备选时刻包括第二时刻，该第二时刻是该网络设备指示的或预定义的时刻。
5.一种应用无线资源控制(Radio Resource Control，RRC)配置信令中的配置的装置，包括：
第二应用单元，其用于将该网络设备发送的RRC配置信令中的配置应用于该网络设备，
其中，该第二应用单元应用该配置的时刻由与该配置有关的业务决定。
6.如附记5所述的装置，其中，
该业务是指超可靠性低时延(Ultra Reliable&Low Latency Communication，URLLC)业务。
7.如附记5所述的装置，其中，
在该业务将要发起，或该RRC配置信令在该业务发起前发送的情况下，该第二应用单元早于该终端设备将该配置应用于该网络设备。
8.如附记7所述的装置，其中，
该第二应用单元早于该终端设备将该配置应用于该网络设备是指在网络设备发 送或者向下层递交该RRC配置信令所对应的时刻应用该配置。
9.如附记5所述的装置，其中，
在该业务将要结束，或该RRC配置信令在该业务发起后或进行中发送的情况下，该第二应用单元晚于该终端设备将该配置应用于该网络设备。
10.如附记9所述的装置，其中，
该第二应用单元晚于该终端设备将该配置应用于该网络设备是指在网络设备接收到与该RRC配置消息所对应的RRC complete消息的时刻应用该配置。
11.如附记5所述的装置，其中，该装置还包括：
第三发送单元，其用于向该终端设备发送RRC配置信令；以及
第二指示单元，其用于指示该终端设备开始应用该RRC配置信令中的配置的时刻。
12.如附记11所述的装置，其中，
该第二指示单元指示该终端设备在至少两个备选时刻中的一个时刻开始应用该RRC配置信令中的配置。
13.如附记12所述的装置，其中，
该备选时刻包括第一时刻，该第一时刻是该终端设备成功接收该RRC配置信令的时刻，或该终端设备发送或向下层递交与该RRC配置信令所对应的RRC配置成功(RRC complete)消息的时刻。
14.如附记12所述的装置，其中，
该备选时刻包括第二时刻，该第二时刻是该网络设备指示的或预定义的时刻。
15.一种通信系统，该通信系统包括终端设备和网络设备，该终端设备具有附记1-4之一所述的装置，该网络设备具有附记5-14之一所述的装置。
16.一种对媒体接入控制层的控制单元(MAC CE，Media Access Control Control Element)进行确认的装置，被设置于第二设备，该装置包括：
第二发送单元，其用于向第一设备发送MAC CE；以及
第二接收单元，其用于接收所述第一设备发送的用于确认所述第一设备成功接收到所述MAC CE的确认MAC CE。
17.如附记16所述的装置，其中，
所述装置还具有指示单元，当所述指示单元进行了指示时，所述第一设备发送所 述确认MAC CE；或者
所述第一设备和所述第二设备中的网络设备进行了配置时，所述第一设备发送所述确认MAC CE。
18.如附记17所述的装置，其中，
所述指示单元对所述第二设备发送的所述MAC CE进行设置，以指示所述第一设备发送所述确认MAC CE。
19.如附记18所述的装置，其中，
所述指示单元对所述MAC CE的数据部分或子头部分的一个字段进行设置，以进行所述指示。
20.如附记18所述的装置，其中，
所述指示单元对所述MAC CE使用的逻辑信道标识(LCID)进行设置，以进行所述指示。
21.如附记18所述的装置，其中，
所述指示单元对所述MAC CE在媒体接入控制层的协议数据单元(Media Access Control Protocol Data Unit，MAC PDU)中的位置进行设置，以进行所述指示。
22.如附记17所述的装置，其中，
所述第二设备是所述网络设备，所述第二设备还具有配置单元，
所述配置单元配置所述第一设备在收到第一网络信令的时刻或该第一网络信令所指示的时刻起的持续时间内，发送所述确认MAC CE。
23.如附记22所述的装置，其中，
所述持续时间的长度由所述配置单元配置的定时器决定。
24.如附记22所述的装置，其中，
所述配置单元配置所述第一设备在收到第二网络信令的时刻或该第二网络信令所指示的时刻，结束发送所述确认MAC CE。
25.如附记17所述的装置，其中，
所述第二设备是所述网络设备，所述装置还具有配置单元，所述配置单元为所述第一设备配置逻辑信道，并且，将所述第一设备配置为：
当所述配置单元为所述第一设备配置了具有高于预定优先级阈值的逻辑信道时，所述第一设备发送所述确认MAC CE。
26.如附记16所述的装置，其中，
所述确认MAC CE与所述MAC CE具有不同的数据格式，和/或不同的数据部分的内容，和/或不同的子头部分的内容。
27.如附记26所述的装置，其中，
所述确认MAC CE的数据格式包括0比特的数据部分和子头部分，
其中，所述子头部分的LCID字段的取值与所述确认MAC CE所确认的所述MAC CE所使用的LCID取值相同。
28.如附记26所述的装置，其中，
所述确认MAC CE的数据格式包括数据部分和子头部分，
其中，所述数据部分的LCID字段的取值与所述确认MAC CE所确认的所述MAC CE所使用的LCID取值相同，
所述子头部分的LCID字段的取值为预定取值。
29.如附记26所述的装置，其中，
所述确认MAC CE的数据格式包括0比特的数据部分和子头部分，
所述子头部分的LCID字段的取值为预定取值。

Claims (20)

  1. 一种对媒体接入控制层的控制单元(MAC CE，Media Access Control Control Element)进行确认的装置，设置于第一设备，该装置包括：
    第一接收单元，其接收第二设备发送的MAC CE；以及
    第一发送单元，其发送用于确认所述第一接收单元成功接收到所述MAC CE的确认MAC CE。
  2. 如权利要求1所述的装置，其中，所述装置还包括：
    第一控制单元，
    当所述控制单元判定为所述第一设备被所述第二设备指示时，控制所述第一发送单元发送所述确认MAC CE；或者
    当所述控制单元被所述第一设备和所述第二设备中的网络设备配置时，控制所述第一发送单元发送所述确认MAC CE。
  3. 如权利要求2所述的装置，其中，
    所述第一控制单元根据所述第二设备发送的所述MAC CE判定所述第一设备被所述第二设备指示发送所述确认MAC CE。
  4. 如权利要求3所述的装置，其中，
    所述第一控制单元根据所述MAC CE的数据部分或子头部分的一个字段判定所述指示。
  5. 如权利要求3所述的装置，其中，
    所述第一控制单元根据所述MAC CE使用的逻辑信道标识(LCID)判定所述指示。
  6. 如权利要求3所述的装置，其中，
    所述第一控制单元根据所述MAC CE在所述第一设备接收到的媒体接入控制层的协议数据单元(Media Access Control Protocol Data Unit，MAC PDU)中的位置判定所述指示。
  7. 如权利要求2所述的装置，其中，
    所述控制单元被所述网络设备配置为进行如下控制：
    在所述第一接收单元收到第一网络信令的时刻或该第一网络信令所指示的时刻起的持续时间内，控制所述第一发送单元发送所述确认MAC CE。
  8. 如权利要求7所述的装置，其中，
    所述持续时间的长度由所述网络设备配置的定时器决定。
  9. 如权利要求7所述的装置，其中，所述控制单元还被所述网络设备配置为进行如下控制：
    在所述第一接收单元收到第二网络信令的时刻或该第二网络信令所指示的时刻，控制所述第一发送单元结束发送所述确认MAC CE。
  10. 如权利要求2所述的装置，其中，
    所述控制单元被所述网络设备配置为进行如下控制：
    当所述网络设备为所述第一设备配置了具有高于预定优先级阈值的逻辑信道时，控制所述第一发送单元发送所述确认MAC CE。
  11. 如权利要求1所述的装置，其中，
    所述确认MAC CE与所述MAC CE具有不同的数据格式，和/或不同的数据部分的内容，和/或不同的子头部分的内容。
  12. 如权利要求11所述的装置，其中，
    所述确认MAC CE的数据格式包括0比特的数据部分和子头部分，
    其中，所述子头部分的逻辑信道标识(LCID)字段的取值与所述确认MAC CE所确认的所述MAC CE所使用的LCID取值相同。
  13. 如权利要求11所述的装置，其中，
    所述确认MAC CE的数据格式包括数据部分和子头部分，
    其中，所述数据部分的LCID字段的取值与所述确认MAC CE所确认的所述MAC CE所使用的LCID取值相同，
    所述子头部分的LCID字段的取值为预定取值。
  14. 如权利要求11所述的装置，其中，
    所述确认MAC CE的数据格式包括0比特的数据部分和子头部分，
    所述子头部分的LCID字段的取值为预定取值。
  15. 一种对媒体接入控制层的控制单元(MAC CE，Media Access Control Control Element)进行确认的装置，被设置于第二设备，该装置包括：
    第二发送单元，其用于向第一设备发送MAC CE；以及
    第二接收单元，其用于接收所述第一设备发送的用于确认所述第一设备成功接收 到所述MAC CE的确认MAC CE。
  16. 如权利要求15所述的装置，其中，
    所述装置还具有指示单元，当所述指示单元进行了指示时，所述第一设备发送所述确认MAC CE；或者
    所述第一设备和所述第二设备中的网络设备进行了配置时，所述第一设备发送所述确认MAC CE。
  17. 如权利要求16所述的装置，其中，
    所述第二设备是所述网络设备，所述第二设备还具有配置单元，
    所述配置单元配置所述第一设备在收到第一网络信令的时刻或该第一网络信令所指示的时刻起的持续时间内，发送所述确认MAC CE。
  18. 如权利要求16所述的装置，其中，
    所述第二设备是所述网络设备，所述装置还具有配置单元，所述配置单元为所述第一设备配置逻辑信道，并且，将所述第一设备配置为：
    当所述配置单元为所述第一设备配置了具有高于预定优先级阈值的逻辑信道时，所述第一设备发送所述确认MAC CE。
  19. 如权利要求15所述的装置，其中，
    所述确认MAC CE与所述MAC CE具有不同的数据格式，和/或不同的数据部分的内容，和/或不同的子头部分的内容。
  20. 一种通信系统，所述通信系统包括第一设备和第二设备，
    所述第一设备包括如权利要求1-14中任一项所述的对媒体接入控制层的控制单元进行确认的装置，
    所述第二设备包括如权利要求15-19中任一项所述的对媒体接入控制层的控制单元进行确认的装置。
PCT/CN2018/077046 2018-02-23 2018-02-23 对媒体接入控制层的控制单元进行确认的方法、装置和通信系统 WO2019161543A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
JP2020536537A JP2021510950A (ja) 2018-02-23 2018-02-23 媒体アクセス制御層の制御要素の確認方法、装置及び通信システム
CN201880065535.3A CN111194573A (zh) 2018-02-23 2018-02-23 对媒体接入控制层的控制单元进行确认的方法、装置和通信系统
PCT/CN2018/077046 WO2019161543A1 (zh) 2018-02-23 2018-02-23 对媒体接入控制层的控制单元进行确认的方法、装置和通信系统
US16/910,763 US20200322943A1 (en) 2018-02-23 2020-06-24 Method and Apparatus for Confirming Media Access Control Control Element and Communication System

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/077046 WO2019161543A1 (zh) 2018-02-23 2018-02-23 对媒体接入控制层的控制单元进行确认的方法、装置和通信系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/910,763 Continuation US20200322943A1 (en) 2018-02-23 2020-06-24 Method and Apparatus for Confirming Media Access Control Control Element and Communication System

Publications (1)

Publication Number Publication Date
WO2019161543A1 true WO2019161543A1 (zh) 2019-08-29

Family

ID=67686668

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/077046 WO2019161543A1 (zh) 2018-02-23 2018-02-23 对媒体接入控制层的控制单元进行确认的方法、装置和通信系统

Country Status (4)

Country Link
US (1) US20200322943A1 (zh)
JP (1) JP2021510950A (zh)
CN (1) CN111194573A (zh)
WO (1) WO2019161543A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111436065B (zh) * 2019-01-11 2021-10-26 大唐移动通信设备有限公司 一种数据发送和指示数据发送的方法及设备
CN114599114A (zh) * 2020-12-07 2022-06-07 上海朗帛通信技术有限公司 一种被用于中继无线通信中的方法和装置
CN113507346A (zh) * 2021-06-03 2021-10-15 北京中联国成科技有限公司 一种基于5g的远程通信方法及装置
WO2024034472A1 (ja) * 2022-08-08 2024-02-15 株式会社デンソー 通信装置、基地局及び通信方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102123440A (zh) * 2010-01-08 2011-07-13 中兴通讯股份有限公司 控制头的确认方法和系统
CN103857041A (zh) * 2012-11-30 2014-06-11 华为技术有限公司 接收信息的方法、发送信息的方法、基站和用户设备
CN105429736A (zh) * 2015-11-02 2016-03-23 电信科学技术研究院 一种发送和接收反馈的方法及设备
US20170310433A1 (en) * 2016-04-25 2017-10-26 Ofinno Technologies, Llc Scheduling Request Process in a Wireless Device and Wireless Network

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
BRPI1013144B1 (pt) * 2009-06-15 2021-03-02 Guangdong Oppo Mobile Telecommunications Corp., Ltd método e sistema para a operação de recepção descontínua para agregação de portadora avançada de evolução de longo prazo
KR101644882B1 (ko) * 2009-07-28 2016-08-02 엘지전자 주식회사 다중반송파 지원 광대역 무선 통신 시스템에서의 반송파 관리 절차 수행 방법 및 장치
CN104115437A (zh) * 2012-02-11 2014-10-22 Vid拓展公司 用于视频感知的混合自动重复请求的方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102123440A (zh) * 2010-01-08 2011-07-13 中兴通讯股份有限公司 控制头的确认方法和系统
CN103857041A (zh) * 2012-11-30 2014-06-11 华为技术有限公司 接收信息的方法、发送信息的方法、基站和用户设备
CN105429736A (zh) * 2015-11-02 2016-03-23 电信科学技术研究院 一种发送和接收反馈的方法及设备
US20170310433A1 (en) * 2016-04-25 2017-10-26 Ofinno Technologies, Llc Scheduling Request Process in a Wireless Device and Wireless Network

Also Published As

Publication number Publication date
US20200322943A1 (en) 2020-10-08
CN111194573A (zh) 2020-05-22
JP2021510950A (ja) 2021-04-30

Similar Documents

Publication Publication Date Title
AU2017389025B2 (en) Method for reporting multi-connection transmission capability, method for configuring multi-connection transmission mode, method for preventing retransmission of data, UE and base station
US11184811B2 (en) Method and device for anchor replacement
CN107113291B (zh) 演进的数据压缩方案信令
CN111149419B (zh) 用于rrc恢复/暂停时的nr pdcp保留的方法和设备
WO2018170885A1 (zh) 网络连接恢复方法及其装置、通信系统
WO2019161543A1 (zh) 对媒体接入控制层的控制单元进行确认的方法、装置和通信系统
WO2019136678A1 (zh) 上行信号发送方法、上行信号接收方法、装置和系统
WO2018112871A1 (zh) 数据发送/接收装置、方法以及通信系统
TW201225571A (en) Wireless communication method for transmitting a sequence of data units between a wireless device and a network
WO2007126192A1 (en) Data transmission method in mobile communications system
US10433205B2 (en) Network node, method therein, computer program, and carrier comprising the computer program for retransmitting an RLC PDU
WO2019019133A1 (zh) 命令指示方法及装置、信息交互方法及装置
WO2020061844A1 (zh) 信号发送方法、信号接收方法及装置
WO2014166053A1 (zh) 一种通讯方法和终端
WO2018201473A1 (zh) 激活命令的确认装置、数据传输模式的上报装置及方法
US11653409B2 (en) Method and apparatus for setting discontinuous reception value in wireless communication system
WO2020191751A1 (zh) 波束失败恢复方法、装置和通信系统
TW202226879A (zh) 降低多分支傳輸中封包延遲的方法和裝置
US20230199895A1 (en) Methods and apparatus for data transmission in new radio (nr) inactive state
WO2021056702A1 (zh) 上行信号的发送和接收方法以及装置
WO2014101061A1 (zh) 控制上行载波聚合的方法、用户设备和基站
WO2022082666A1 (en) Methods, apparatuses, and media for operating point-to-multipoint radio bearer
WO2008111820A1 (en) Method of managing data blocks during handover
WO2017177440A1 (zh) 状态指示的传输装置、方法以及通信系统
WO2020191726A1 (zh) 系统信息请求的发送方法、装置和系统

Legal Events

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

Ref document number: 18907296

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020536537

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18907296

Country of ref document: EP

Kind code of ref document: A1