WO2019153350A1 - 一种通信方法、通信设备及计算机程序存储介质 - Google Patents

一种通信方法、通信设备及计算机程序存储介质 Download PDF

Info

Publication number
WO2019153350A1
WO2019153350A1 PCT/CN2018/076527 CN2018076527W WO2019153350A1 WO 2019153350 A1 WO2019153350 A1 WO 2019153350A1 CN 2018076527 W CN2018076527 W CN 2018076527W WO 2019153350 A1 WO2019153350 A1 WO 2019153350A1
Authority
WO
WIPO (PCT)
Prior art keywords
deployment mode
anchor carrier
configuration information
carrier
band deployment
Prior art date
Application number
PCT/CN2018/076527
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 CN201880089049.5A priority Critical patent/CN111771407B/zh
Priority to CN202311548765.4A priority patent/CN117769025A/zh
Priority to PCT/CN2018/076527 priority patent/WO2019153350A1/zh
Priority to JP2020542999A priority patent/JP7073511B2/ja
Priority to EP18905486.9A priority patent/EP3745789A4/en
Publication of WO2019153350A1 publication Critical patent/WO2019153350A1/zh
Priority to US16/990,672 priority patent/US12028879B2/en

Links

Images

Classifications

    • 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
    • H04L5/0092—Indication of how the channel is divided
    • 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/53—Allocation or scheduling criteria for wireless resources based on regulatory allocation policies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H04L27/26—Systems using multi-frequency codes
    • H04L27/2601—Multicarrier modulation systems
    • H04L27/2602—Signal structure
    • H04L27/2605—Symbol extensions, e.g. Zero Tail, Unique Word [UW]
    • H04L27/2607—Cyclic extensions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/005—Transmission of information for alerting of incoming communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
    • 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

Definitions

  • the present application relates to the field of communications, and more particularly to a communication method, a communication device, and a computer program storage medium.
  • the Internet of Things In the 5G new radio (NR) project in the 5th generation of mobile communication technology (5th-generation, 5G), the Internet of Things (IOT) will become an important application in the future communication field. It may cover areas such as smart meter reading, medical test monitoring, logistics inspection, industrial inspection and monitoring, automotive networking, smart communities, and wearable device communication.
  • a typical cellular Internet of Things is a narrowband Internet of Things (NB-IOT).
  • the operator has certain restrictions on the deployment mode of the anchor carrier and the non-anchor carrier.
  • the supported carrier deployment combination can be extended (combining 4 unsupported carrier deployments into 4 supported carrier deployment combinations).
  • the existing NB-IOT terminal can only support the traditional deployment mode and cannot support the new deployment mode combination. If a new carrier is configured directly in the corresponding carrier configuration, this will result in incompatible (old) NB-IOT terminals.
  • the present application provides a communication method, a communication device, and a computer program storage medium, which can avoid the impact of a new carrier deployment mode combination on an NB-IOT terminal in an existing network.
  • the first aspect provides a communication method, including: the network device sends first configuration information to the terminal device, where the first configuration information includes non-anchor carrier configuration information, and when the anchor carrier is in an independent deployment mode, the non-anchor The point carrier is applied to the in-band deployment mode or the guard band deployment mode. When the anchor carrier is in the in-band deployment mode or the guard band deployment mode, the non-anchor carrier is applied to the independent deployment mode.
  • the network device provides configuration information of the non-anchor carrier for the terminal device, and the carrier can be applied to the four new deployment modes, thereby preventing the NB-IOT terminal in the existing network from supporting the carrier deployment mode. Enhancements caused by incompatibilities.
  • the method further includes: the network device sending the first configuration information and the second configuration information to the terminal device, where the second configuration information includes configuration information of the non-anchor carrier, when the anchor When the point carrier is in the in-band deployment mode, the non-anchor carrier is applied to the in-band deployment mode or the protection band deployment mode. When the anchor carrier is in the protection band deployment mode, the non-anchor carrier is applied to the in-band deployment mode or the protection band deployment. Mode, when the anchor carrier is in the independent deployment mode, the non-anchor carrier is applied to the independent deployment mode.
  • the network device provides two configuration information of the non-anchor carrier to the terminal device, and the configuration information of the first non-anchor carrier can make the carrier applicable to the four new deployment modes, and the second non-anchor
  • the configuration information of the carrier can make the carrier applicable to the old deployment mode combination, thereby avoiding the incompatibility problem caused by the enhancement of the carrier deployment mode in the NB-IOT terminal in the existing network.
  • the non-anchor carrier when the anchor carrier is in the independent deployment mode, the non-anchor carrier is applied to the in-band deployment mode, and the non-anchor carrier configuration information in the first configuration information includes the following long-term evolution.
  • LTE cell information if the physical cell of the non-anchor carrier is the same as the ID of the LTE cell, the LTE cell information includes symbol number information occupied by the LTE cell control channel; or the non-anchor carrier to The reference signal of the LTE center frequency point.
  • the network device can provide corresponding non-anchor carrier configuration information for use by the terminal device, so that the enhanced carrier deployment mode combination can be supported.
  • the non-anchor carrier when the anchor carrier is in the independent deployment mode, the non-anchor carrier is applied to the in-band deployment mode, and the non-anchor carrier configuration information in the first configuration information includes the following long-term evolution.
  • LTE cell information if the physical cell of the non-anchor carrier is different from the ID of the LTE cell, the LTE cell information includes symbol number information occupied by the LTE cell control channel; or the LTE cell reference signal Port information of the CRS.
  • the network device can provide corresponding non-anchor carrier configuration information for use by the terminal device, so that the enhanced carrier deployment mode combination can be supported.
  • the non-anchor carrier configuration information when the non-anchor carrier carrier is applied to the protection band deployment mode or the independent deployment mode, includes first indication information, where the first indication information includes: Instructing the non-anchor carrier to be applied to the guard band deployment mode; or indicating that the non-anchor carrier is applied to the independent deployment mode.
  • the non-anchor carrier when the anchor carrier is in an independent deployment mode, the non-anchor carrier is applied in an in-band deployment mode or a guard band deployment mode, when the anchor carrier is an in-band deployment mode or a guard band deployment.
  • the non-anchor carrier is applied to the independent deployment mode, including: when the anchor carrier is in the independent deployment mode, the non-anchor carrier used for paging is applied to the in-band deployment mode or the protection band deployment mode;
  • the anchor carrier is a guard band deployment mode or an in-band deployment mode, and the non-anchor carrier for paging is applied to the independent deployment mode.
  • the non-anchor carrier when the anchor carrier is in an independent deployment mode, the non-anchor carrier is applied in an in-band deployment mode or a guard band deployment mode, when the anchor carrier is an in-band deployment mode or a guard band deployment.
  • the non-anchor carrier is applied to the independent deployment mode, including: when the anchor carrier is in the independent deployment mode, the non-anchor carrier used for random access is applied to the in-band deployment mode or the protection band deployment mode;
  • the anchor carrier is a guard band deployment mode or an in-band deployment mode, and the non-anchor carrier for random access is applied to the independent deployment mode.
  • the non-anchor carrier when the anchor carrier is in an independent deployment mode, the non-anchor carrier is applied in an in-band deployment mode or a guard band deployment mode, when the anchor carrier is an in-band deployment mode or a guard band deployment.
  • the non-anchor carrier In the mode, the non-anchor carrier is applied to the independent deployment mode, and the non-anchor carrier used to carry the multicast service is applied to the in-band deployment mode or the protection band deployment mode when the anchor carrier is in the independent deployment mode.
  • the anchor carrier is in a guard band deployment mode or an in-band deployment mode, the non-anchor carrier used to carry the multicast service is applied to the independent deployment mode.
  • the configuration information of the non-anchor carrier is carried on the system information block SIB22.
  • the configuration information of the non-anchor carrier is carried on the multimedia broadcast multicast service control channel SC-MCCH.
  • the sum of the number of carriers configured in the first configuration information and the number of carriers configured in the second configuration information is not greater than a maximum number of carriers configured in the second configuration information.
  • a second aspect provides a communication method, including: receiving, by a terminal device, first configuration information sent by a network device, where the first configuration information includes non-anchor carrier configuration information, when the anchor carrier is in an independent deployment mode, The anchor carrier is applied to the in-band deployment mode or the guard band deployment mode. When the anchor carrier is in the in-band deployment mode or the guard band deployment mode, the non-anchor carrier is applied to the independent deployment mode.
  • the method further includes: receiving, by the terminal device, first configuration information and second configuration information sent by the network device, where the second configuration information includes configuration information of the non-anchor carrier, when the anchor point When the carrier is in the in-band deployment mode, the non-anchor carrier is applied to the in-band deployment mode or the protection band deployment mode. When the anchor carrier is in the protection band deployment mode, the non-anchor carrier is applied to the in-band deployment mode or the protection band deployment mode. When the anchor carrier is in the independent deployment mode, the non-anchor carrier is applied to the independent deployment mode.
  • the non-anchor carrier when the anchor carrier is in the independent deployment mode, the non-anchor carrier is applied to the in-band deployment mode, and the non-anchor carrier configuration information in the first configuration information includes the following long-term evolution.
  • LTE cell information if the physical cell of the non-anchor carrier is the same as the ID of the LTE cell, the LTE cell information includes symbol number information occupied by the LTE cell control channel; or the non-anchor carrier to The reference signal of the LTE center frequency point.
  • the non-anchor carrier when the anchor carrier is in the independent deployment mode, the non-anchor carrier is applied to the in-band deployment mode, and the non-anchor carrier configuration information in the first configuration information includes the following long-term evolution.
  • LTE cell information if the physical cell of the non-anchor carrier is different from the ID of the LTE cell, the LTE cell information includes symbol number information occupied by the LTE cell control channel; or the LTE cell reference signal Port information of the CRS.
  • the non-anchor carrier configuration information when the non-anchor carrier carrier is applied to the protection band deployment mode or the independent deployment mode, includes first indication information, where the first indication information includes: Instructing the non-anchor carrier to be applied to the guard band deployment mode; or indicating that the non-anchor carrier is applied to the independent deployment mode.
  • the non-anchor carrier when the anchor carrier is in an independent deployment mode, the non-anchor carrier is applied in an in-band deployment mode or a guard band deployment mode, when the anchor carrier is an in-band deployment mode or a guard band deployment.
  • the non-anchor carrier In the mode, the non-anchor carrier is applied to the independent deployment mode, including: the terminal device serially connecting the first configuration information to the second configuration information to form third configuration information; The third configuration information is selected as a non-anchor carrier for paging, and when the anchor carrier is in an independent deployment mode, the non-anchor carrier for paging is applied to an in-band deployment mode or a protection band deployment mode.
  • the anchor carrier is in a guard band deployment mode or an in-band deployment mode, the non-anchor carrier for paging is applied to an independent deployment mode.
  • the non-anchor carrier when the anchor carrier is in an independent deployment mode, the non-anchor carrier is applied in an in-band deployment mode or a guard band deployment mode, when the anchor carrier is an in-band deployment mode or a guard band deployment.
  • the non-anchor carrier In the mode, the non-anchor carrier is applied to the independent deployment mode, including: the terminal device serially connecting the first configuration information to the second configuration information to form third configuration information; The third configuration information is used to select a non-anchor carrier for random access.
  • the non-anchor carrier for random access is applied to an in-band deployment mode or a guard band.
  • Deployment mode when the anchor carrier is a guard band deployment mode or an in-band deployment mode, the non-anchor carrier for random access is applied to an independent deployment mode.
  • the non-anchor carrier when the anchor carrier is in an independent deployment mode, the non-anchor carrier is applied in an in-band deployment mode or a guard band deployment mode, when the anchor carrier is an in-band deployment mode or a guard band deployment.
  • the non-anchor carrier is applied to the independent deployment mode, including: the terminal device serially connecting the first configuration information to the second configuration information to form third configuration information; The non-anchor carrier for transmitting the multicast service is selected in the third configuration information, and when the anchor carrier is in the independent deployment mode, the non-anchor carrier used for transmitting the multicast service is applied to the in-band deployment mode or The guard band deployment mode; when the anchor carrier is a guard band deployment mode or an in-band deployment mode, the non-anchor carrier for transmitting the multicast service is applied to the independent deployment mode.
  • the configuration information of the non-anchor carrier is carried on the system information block SIB22.
  • the configuration information of the non-anchor carrier is carried on the multimedia broadcast multicast service control channel SC-MCCH.
  • the sum of the number of carriers configured in the first configuration information and the number of carriers configured in the second configuration information is not greater than a maximum number of carriers configured in the second configuration information.
  • a communication device comprising: at least one processor and a communication interface, wherein the communication interface is used for information interaction between the communication device and other communication devices, when the program instructions are at the When executed in a processor, the communication device is implemented in any one of the possible implementations of the first aspect or the first aspect and the method of any one of the second aspect or the second aspect A function on any of the following devices: the network device and the terminal device.
  • a computer program storage medium having program instructions that, when executed directly or indirectly, cause the first aspect or any one of the possible implementations of the first aspect And the function of the method described in any one of the following aspects, or any one of the possible implementations of the second aspect, is implemented on: the network device and the terminal device.
  • a chip system comprising at least one processor, enabling any one of the first aspect or the first aspect when the program instructions are executed in the at least one processor And the function of the method described in any one of the following aspects, or any one of the possible implementations of the second aspect, is implemented on: the network device and the terminal device.
  • a communication system comprising: the communication device as provided in the third aspect.
  • FIG. 1 is a schematic flowchart of a communication method provided by an embodiment of the present application.
  • FIG. 2 is a schematic flowchart of a communication method provided by another embodiment of the present application.
  • FIG. 3 is a schematic flowchart of a communication method provided by another embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of a communication device according to an embodiment of the present application.
  • NB-IoT narrow band internet of things
  • GSM global mobile communication
  • CDMA code division multiple access
  • WCDMA wideband code division multiple access
  • general packet radio service general packet radio service, GPRS
  • LTE long term evolution
  • LTE frequency division duplex FDD
  • TDD LTE time division duplex
  • UMTS universal mobile telecommunication system
  • WiMAX worldwide interoperability for microwave access
  • the embodiment of the present application does not specifically limit the type of the terminal device, and may be, for example, a user equipment, an access terminal, a terminal device, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, and a user terminal. , wireless network device, user agent or user device.
  • the terminal may include, but is not limited to, a mobile station (MS), a mobile telephone, a user equipment (UE), a handset, a portable device, a cellular phone, a cordless phone, a session.
  • Session initiation protocol SIP
  • WLL wireless local loop
  • PDA personal digital assistant
  • RFID radio frequency identification
  • Handheld devices with wireless communication capabilities computing devices or other devices connected to wireless modems, in-vehicle devices, wearable devices, Internet of Things, terminal devices in vehicle networks, and terminal devices in future 5G networks or future evolving public land mobiles
  • PLMN public land mobile network
  • the terminal device may also be a wearable device.
  • a wearable device which can also be called a wearable smart device, is a general term for applying wearable technology to intelligently design and wear wearable devices such as glasses, gloves, watches, clothing, and shoes.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are more than just a hardware device, but they also implement powerful functions through software support, data interaction, and cloud interaction.
  • Generalized wearable smart devices include full-featured, large-size, non-reliable smartphones for full or partial functions, such as smart watches or smart glasses, and focus on only one type of application, and need to work with other devices such as smartphones. Use, such as various smart bracelets for smart signs monitoring, smart jewelry, etc.
  • the embodiment of the present application does not specifically limit the type of the network device, and may be any device used for communication with the terminal device, and the network device may be, for example, a global system of mobile communication (GSM) or a code division multiple access (A base transceiver station (BTS) in a code division multiple access (CDMA) system may also be a base station (NodeB, NB) in a wideband code division multiple access (WCDMA) system, or may be a long term evolution.
  • GSM global system of mobile communication
  • a base transceiver station (BTS) in a code division multiple access (CDMA) system may also be a base station (NodeB, NB) in a wideband code division multiple access (WCDMA) system, or may be a long term evolution.
  • GSM global system of mobile communication
  • BTS code division multiple access
  • CDMA code division multiple access
  • NodeB, NB base station
  • WCDMA wideband code division multiple access
  • eNB evolved base station
  • LTE long term evolution
  • CRAN cloud radio access network
  • the network device may be a relay station, an access point, an in-vehicle device, a wearable device, and a network device in a future 5G network or a network device in a future evolved PLMN network.
  • the network device may be composed of a centralized unit (CU) and a distributed unit (DU).
  • CU centralized unit
  • DU distributed unit
  • One CU can be connected to one DU, or multiple DUs can share one CU, which can save costs and facilitate network expansion.
  • the severing of CU and DU can be divided according to the protocol stack.
  • RRC radio resource control
  • SDAP service data adaptation protocol
  • packet data convergence protocol The (packet data convergence protocol, PDCP) layer is deployed in the CU, and the remaining Radio Link Control (RLC) layer, media access control (MAC) layer, and physical layer are deployed in the DU.
  • RRC radio resource control
  • SDAP service data adaptation protocol
  • PDCP packet data convergence protocol
  • the (packet data convergence protocol, PDCP) layer is deployed in the CU, and the remaining Radio Link Control (RLC) layer, media access control (MAC) layer, and physical layer are deployed in the DU.
  • RLC Radio Link Control
  • MAC media access control
  • the carrier deployment mode may be a standalone deployment mode.
  • the independent carrier deployment mode may be independent of other communication systems, for example, independent.
  • the carrier deployment bandwidth of the deployment mode can be completely decoupled from the long term evolution (LTE) cell.
  • the carrier deployment mode may be a guard band deployment mode (guardband), and the carrier of the protection band deployment mode may not occupy resources of other communication systems.
  • the carrier in the protection band deployment mode may not occupy LTE resources and may be deployed. On resource blocks that are not used in the LTE edge guard band.
  • the carrier deployment may also be an inband deployment mode (inband), and the in-band deployment mode carrier may be deployed in the working bandwidth of other communication systems.
  • an in-band deployment mode carrier may be deployed in LTE work. In the bandwidth.
  • the embodiment of the present application does not specifically limit the classification of the carriers mentioned, and may classify the carriers into different types according to different information carried on the carrier.
  • a carrier carrying a synchronization signal and a system broadcast may be referred to as an anchor carrier.
  • a carrier carrying unicast transmission, paging, and random access may be referred to as a non-anchor carrier.
  • carrier deployment modes standalone, guardband, inband
  • carrier carrier anchor carrier, non-anchor carrier
  • the existing NB-IOT version (Rel-13/14) has three deployment modes for an anchor carrier and a non-anchor carrier.
  • Anchor carrier and non-anchor carrier development combinations anchor carrier and non-anchor carrier three carrier deployment modes (standalone deployment mode standalone, protection band)
  • the deployment mode guardband and the inband deployment mode inband there are four deployment modes that are not supported.
  • the non-anchor carrier is in-band deployment mode or protection.
  • deployment mode anchor carrier is in-band deployment mode or protection band deployment mode
  • non-anchor carrier is independent deployment mode.
  • FIG. 1 is a schematic flowchart of a communication method provided by an embodiment of the present application.
  • the method of Figure 1 includes:
  • Step 110 The network device sends first configuration information to the terminal device, where the first configuration information includes non-anchor carrier configuration information.
  • the network device may provide configuration information of the non-anchor carrier for the terminal device, and the non-anchor carrier may be applied to the four new carrier deployment combinations instead of directly configuring the new carrier configuration.
  • Carrier so that the NB-IOT terminal incompatibility problem in the live network caused by the enhancement of the carrier deployment mode can be avoided.
  • the network device may send the first configuration information to the terminal device, where the first configuration information may include configuration information included in each non-anchor carrier.
  • the first configuration information may also be referred to as a first configuration information list.
  • the non-anchor carrier in the first configuration information may be applied to at least one of the following four new carrier deployment modes.
  • the non-anchor carrier in the first configuration information can be applied to the in-band deployment mode. If the anchor carrier is in the independent deployment mode, the non-anchor carrier in the first configuration information may be applied to the guard band deployment mode. If the anchor carrier is in the in-band deployment mode, the non-anchor carrier in the first configuration information can be applied to the independent deployment mode. If the anchor carrier is in the guard band deployment mode, the non-anchor carrier in the first configuration information can be applied to the independent deployment mode. That is, the scenario in which the non-anchor carrier in the first configuration information can be applied includes at least one of the four combinations of carrier deployments mentioned in Table 1 above.
  • the configuration information of the non-anchor carrier that can be included in the first configuration information is not specifically limited in the embodiment of the present application, and may be any configuration information about a non-anchor carrier that can be used by the terminal device.
  • the network device may send the LTE cell in the configuration information of each non-anchor carrier.
  • the configuration information of the non-anchor carrier may include the number of symbols occupied by the LTE cell control channel.
  • the configuration information of the non-anchor carrier may further include the non-anchor carrier to the LTE center frequency. Point reference signal.
  • the configuration information of the non-anchor carrier may further include the cell-specific reference signal of the LTE ( Port information of the cell-specific reference signal (CRS).
  • PCI physical cell ID
  • CRS cell-specific reference signal
  • the non-anchor point in the first configuration information may include first indication information, where the first indication information may indicate whether the deployment mode of the anchor carrier of the terminal device is an independent deployment mode or a protection band deployment mode.
  • the configuration information of the non-anchor carrier in the first configuration information mentioned in the embodiment of the present application is described in more detail below with reference to specific signaling.
  • the “inband Carrier Info-r13” in the above signaling may be used to indicate configuration information of a carrier, and the carrier may be applied to an in-band deployment mode.
  • the "entea Control Region Size-r13" in the above signaling may be used to indicate that if the deployment mode of the anchor carrier is an independent deployment mode, and the non-anchor carrier can be applied to the in-band deployment mode, the configuration of the non-anchor carrier
  • the information may include symbol number information occupied by the LTE cell control channel.
  • the "samePCI-Indicator-r13" in the above signaling may be used to indicate that when the deployment mode of the anchor carrier is an independent deployment mode, and the non-anchor carrier can be applied to the in-band deployment mode, the PCI of the non-anchor carrier
  • the configuration information that the non-anchor carrier can include when the IDs of the LTE cells are the same or different.
  • the "samePCI-r13" and the "index To Mid PRB-r13" in the above signaling may be used to indicate that if the PCI of the non-anchor carrier is the same as the ID of the LTE cell, the configuration information of the non-anchor carrier may include The reference signal of the non-anchor carrier to the LTE center frequency.
  • the "different PCI-r13" and “eutra-Num CRS-Ports-r13" in the above signaling may be used to indicate the configuration information of the non-anchor carrier if the PCI of the non-anchor carrier is the same as the ID of the LTE cell. Port information of the LTE cell CRS may be included.
  • the "Cond non-anchor-guardband-or-standalone" in the above signaling may be used to indicate that the non-anchor carrier is used if the deployment mode of the non-anchor carrier can be an independent deployment mode or a guard band deployment mode.
  • the configuration information may include indication information, where the indication information may be used to indicate whether the deployment mode of the non-anchor carrier is an independent deployment mode or a protection band deployment mode.
  • non-anchor-inband in the above signaling may be used to indicate that the field is mandatory to indicate that the non-anchor carrier can be applied to the in-band deployment mode, otherwise the field does not exist. (The field is mandatory present if the non-anchor carrier is an inband carrier; otherwise it is not present.)
  • non-anchor-guardband-or-standalone in the above signaling may be used to indicate that the field mandatory indicates whether the non-anchor carrier can be applied to the guard band deployment mode or the independent deployment mode, otherwise the field does not exist. . (The field is mandatory present if the non-anchor carrier is an guardband or standalone carrier; otherwise sure it is not present.)
  • anchor-guardband-or-standalone in the above signaling can be used to indicate that the field mandatory indicates whether the anchor carrier can be applied to the guard band deployment mode or the independent deployment mode, otherwise the field does not exist. (The field is mandatory present if operation Mode Info is set to guardband or standalone in the MIB; otherwise it is not present.)
  • the network device sends the configuration information of the non-anchor carrier for the terminal device, so that the NB-IOT terminal incompatibility problem in the live network caused by the enhancement of the carrier deployment mode can be avoided.
  • the method of FIG. 1 further includes: the network device may send the first configuration information and the second configuration information to the terminal device, where the first configuration information and the second configuration information may include a non-anchor carrier Configuration information.
  • the non-anchor carrier in the first configuration information may be applied to at least one of the four new carrier deployment combinations mentioned above (for example, at least one of the four invalid combinations mentioned in Table 1 when the anchor
  • the non-anchor carrier is applied to the in-band deployment mode or the protection band deployment mode.
  • the non-anchor carrier is applied to the independent deployment mode.
  • the non-anchor carrier in the second configuration information may be applied to the old carrier deployment combination (for example, at least one of the five valid combinations mentioned in Table 1, when the anchor carrier is in the in-band deployment mode, the non-anchor point The carrier is applied to the in-band deployment mode or the protection band deployment mode.
  • the non-anchor carrier is applied to the in-band deployment mode or the protection band deployment mode.
  • the anchor carrier is in the independent deployment mode
  • Non-anchor carrier is applied to the independent deployment mode
  • the network device sends the configuration information of the non-anchor carrier that can be applied to the new deployment combination and the old deployment to the terminal device for use by the terminal device, thereby avoiding enhancement of the carrier deployment mode.
  • the network device may send configuration information of the non-anchor carrier for paging to the terminal device, where configuration information that the non-anchor carrier can include may be referred to above, where not Let me repeat).
  • the anchor carrier is in the independent deployment mode, the non-anchor carrier can be applied to the in-band deployment mode or the protection band deployment mode.
  • the anchor carrier is in the guard band deployment mode or the in-band deployment mode, the non-anchor carrier can be applied to the independent deployment mode.
  • the terminal device may receive configuration information of the non-anchor carrier transmitted by the network device, and may receive the paging according to the corresponding configuration information of the non-anchor carrier.
  • the network device may send configuration information for random access to the terminal device.
  • the anchor carrier When the anchor carrier is in the independent deployment mode, the non-anchor carrier can be applied to the in-band deployment mode or the protection band deployment mode.
  • the anchor carrier When the anchor carrier is in the guard band deployment mode or the in-band deployment mode, the non-anchor carrier can be applied to the independent deployment mode.
  • the terminal device may receive configuration information of a non-anchor carrier transmitted by the network device, and may randomly select an uplink carrier that initiates random access.
  • the configuration information of the non-anchor carrier transmitted by the network device to the terminal device may be carried on a system information block (SIB) 22.
  • the network device may transmit the configuration information of the non-anchor carrier to the terminal device by broadcasting the SIB 22.
  • the base station (eNB) in FIG. 2 may correspond to the network device in the above, and the user equipment (UE) may correspond to the terminal device in the above.
  • the carrier configuration information list that the eNB may broadcast to the UE system may be carried on the SIB 22. It may include a downlink carrier configuration list (dl-confilist), a downlink carrier configuration list enhanced version (dl-confilist-enh), an uplink carrier configuration list (ul-confilist), and an uplink carrier configuration list enhanced version (ul-confilist-enh).
  • the above four carrier configuration lists may include configuration information of each non-anchor carrier, and the above four carrier configuration lists are respectively described in detail below.
  • the non-anchor carrier in the downlink carrier configuration list (dl-confilist) can be applied to at least one of the five valid combinations as mentioned in Table 1, which can be used for paging.
  • the non-anchor carrier in the uplink carrier configuration list (ul-confilist) can be applied to at least one of the five valid combinations as mentioned in Table 1, which can be used for random access.
  • the carrier deployment mode for paging can be an in-band deployment mode (inband) or a guardband deployment mode (guardband) non-anchor carrier (non-
  • the configuration information of the anchor carrier is configured in a downlink configuration list enhanced version (dl-confilist-enh, that is, the first configuration information or the first configuration information list as mentioned above), and the non-anchor carrier can be applied to, for example, Table 1. At least one of the four invalid combinations mentioned in the above.
  • the deployment mode of the anchor carrier can be an inband deployment mode or a guardband deployment mode (guardband)
  • the carrier deployment mode for paging can be a standalone non-anchor carrier (non-anchor carrier) (non-anchor carrier) (non-anchor carrier).
  • the configuration information of the anchor carrier is configured in a downlink configuration list enhanced version (dl-confilist-enh, that is, the first configuration information or the first configuration information list as mentioned above), and the non-anchor carrier can be applied to, for example, Table 1. At least one of the four invalid combinations mentioned in the above.
  • the carrier deployment mode for random access can be a non-anchor carrier (inband) or a guardband deployment mode (guardband).
  • the configuration information of the -anchor carrier is configured in an uplink configuration list enhanced version (ul-confilist-enh, that is, the first configuration information or the first configuration information list as mentioned above), and the non-anchor carrier can be applied to, for example, a table. At least one of the four invalid combinations mentioned in 1.
  • the deployment mode of the anchor carrier can be an inband deployment mode or a guardband deployment mode (guardband)
  • the carrier deployment mode for random access can be a standalone non-anchor carrier (non-anchor carrier).
  • the configuration information of the -anchor carrier is configured in a downlink configuration list enhanced version (ul-confilist-enh, that is, the first configuration information or the first configuration information list as mentioned above), and the non-anchor carrier can be applied to, for example, a table. At least one of the four invalid combinations mentioned in 1.
  • the UE may acquire two uplink carrier lists and two downlink carrier lists in the SIB 22, and may generate a new downlink carrier list for paging and an uplink carrier list for random access.
  • the UE may select its own paging request in the downlink carrier configuration list (dl-confilist), and may configure a non-anchor carrier according to the carrier configuration list.
  • the configuration information receives the page.
  • the UE may randomly select an uplink carrier that can initiate random access in an uplink carrier configuration list (ul-confilist).
  • ul-confilist an uplink carrier configuration list
  • the UE may connect the downlink carrier configuration list enhanced version (dl-confilist-enh) to the downlink carrier configuration list (dl-confilist) to generate one.
  • dl-confilist enhanced version
  • the UE may select its own paging request in the new downlink carrier configuration list, and may receive the paging according to the configuration information of the non-anchor carrier in the carrier configuration list.
  • the UE may connect the uplink carrier configuration list enhanced version (ul-confilist-enh) to the uplink carrier configuration list (ul-confilist) to generate a new uplink.
  • Carrier configuration list The UE may randomly select an uplink carrier that can initiate random access in the new uplink carrier configuration list.
  • non-anchor carrier in the uplink carrier configuration list enhanced version (ul-confilist-enh) and the downlink carrier configuration list enhanced version (dl-confilist-enh) of the system broadcast can be applied to the following carrier deployment mode combinations.
  • the non-anchor carrier for paging or random access can be applied to the in-band deployment mode or the protection band deployment mode.
  • the anchor carrier deployment mode is the in-band deployment mode or the guard band deployment mode
  • the non-anchor carrier for paging or random access can be applied to the independent deployment mode.
  • the enhanced carrier configuration list (eg, ul-confilist-enh and dl-confilist-enh) can be configured with the number of non-anchor carriers and the original carrier configuration list (eg, ul-confilist and dl-confilist)
  • the sum of the number of non-anchor carriers that can be configured in the original carrier configuration list cannot be greater than the maximum value of the non-anchor carrier that can be configured in the original carrier configuration list.
  • the “DL-ConfigCommonList-NB-r14” in the above signaling may be used to indicate the original downlink carrier configuration list.
  • the "UL-ConfigCommonList-NB-r14" in the above signaling may be used to indicate the original uplink carrier configuration list.
  • the "dl-ConfigList-Enh-r15" in the above signaling can be used to indicate an enhanced version of the downlink carrier configuration list.
  • the "ul-ConfigList-Enh-r15" in the above signaling can be used to represent an enhanced version of the uplink carrier configuration list.
  • the "DL-ConfigCommonList-NB-r14" in the above signaling may be used to indicate that the relevant configuration information of the non-anchor carrier in the original downlink carrier configuration list may be used to undertake paging. (List of DL non-anchor carriers and associated configuration that can be used for paging and/or random access.)
  • the "dl-ConfigList-Enh-r15" in the above signaling indicates that the evolved universal mobile telecommunication system terrestrial radio access network (EUTRAN) can be configured in the dl-ConfigList-Enh.
  • EUTRAN evolved universal mobile telecommunication system terrestrial radio access network
  • a non-anchor carrier that can be applied to a standalone deployment mode or an in-band deployment mode/protection band deployment mode.
  • EUTRAN configures DL non-anchor carriers for which the mode of operation, standalone or inband/guardband, is different from the anchor carrier in dl-ConfigList-Enh.
  • the " dl-ConfigList-Enh-r15 DL-ConfigCommonList-NB-r14 " in the above signaling may be used to indicate that if the UE can support the enhancement of the carrier deployment mode, the enhanced downlink carrier configuration list and the original downlink may be used.
  • the carrier configuration list is concatenated to form a new carrier configuration list that can be used to undertake paging.
  • the sum of the enhanced carrier configuration list and the number of non-anchor carriers that can be configured in the original carrier configuration list cannot be greater than the maximum value of the non-anchor carrier that can be configured in the original carrier configuration list.
  • dl-ConfigList-Enh appends dl-ConfigList-Enh to the end of dl-ConfigList to create a single list for paging and/or random access.
  • the total maximum number of non-anchor carriers in dl-ConfigList and dl-ConfigList-Enh is maxNonAnchorCarriers-NB-r14.
  • the " ul-ConfigList-Enh-r15 UL-ConfigCommonList-NB-r14 " used in the above signaling can refer to the description of the signaling " dl-ConfigList-Enh-r15 DL-ConfigCommonList-NB-r14 ", here No longer.
  • the network device when the anchor carrier is in an independent deployment mode, and the non-anchor carrier for carrying the multicast service is applied to the in-band deployment mode or the protection band deployment mode, the network device may broadcast to the terminal device. A list of business configuration information.
  • the network device may broadcast the service configuration information list to the terminal device.
  • the multicast service can be configured in the service configuration information list.
  • the service configuration information list sent by the network device to the terminal device may be carried on a multimedia broadcast multicast service control channel (SC-MCCH).
  • SC-MCCH multimedia broadcast multicast service control channel
  • the network device may transmit the service configuration information list to the terminal device by broadcasting the SC-MCCH.
  • the service configuration information list that the eNB may broadcast to the UE system may be carried on the SC-MCCH, and may include an original service configuration information list (sc-mtch-InfoList) and an enhanced version of the service configuration information list (sc - mtch-InfoList-Enh), the configuration information of the non-anchor carrier where each service in the service configuration information list is located can be referred to the description above, and details are not described herein again.
  • the above two types of service configuration information lists are described in detail below.
  • the multicast service that can be configured in the original service configuration information list (sc-mtch-InfoList) can be sent on the non-anchor carrier, and the non-anchor carrier can be applied to the five valid combinations mentioned in Table 1. At least one kind.
  • the non-anchor carrier for carrying the multicast service may be applied to an inband deployment mode or a guardband deployment mode (guardband), which may be more
  • the broadcast service configuration is sent in the enhanced service configuration information list (sc-mtch-InfoList-Enh).
  • the anchor carrier deployment mode is in-band deployment mode (inband) or guard band deployment mode (guardband)
  • the non-anchor carrier used to carry the multicast service can be applied to the standalone deployment mode (standalone), which can be more
  • the broadcast service configuration is sent in the enhanced service configuration information list (sc-mtch-InfoList-Enh).
  • the UE may obtain an original service configuration information list (sc-mtch-InfoList) and an enhanced service configuration information list (sc-mtch-InfoList-Enh) carried on the SC-MCCH, and may be corresponding according to the service ID.
  • the corresponding configuration information is used on the carrier to receive the multicast service.
  • non-anchor carrier in which the multicast service can be transmitted in the enhanced service configuration information list (sc-mtch-InfoList-Enh) of the system broadcast can be applied to the following carrier deployment mode combination.
  • the non-anchor carrier used to transmit the multicast service may be applied to the in-band deployment mode or the protection band deployment mode.
  • the deployment mode of the anchor carrier is the in-band deployment mode or the guard band deployment mode
  • the non-anchor carrier used to transmit the multicast service can be applied to the independent deployment mode.
  • the sum of the number of multicast services that can be configured in the enhanced service configuration information list (sc-mtch-InfoList-Enh) and the number of services in the original service configuration information list (sc-mtch-InfoList) cannot be greater than The maximum number of services that can be configured in the original service configuration information list.
  • the multicast service list transmitted on the SC-MCCH mentioned in the embodiment of the present application is described in more detail below with reference to specific signaling.
  • the “sc-mtch-InfoList-r14” in the above signaling may be used to indicate a legacy service configuration information list (sc-mtch-InfoList) carried on the SC-MCCH, and the list may be provided for sending.
  • Configuration information of the carrier of the multicast service Provides the configuration of each SC-MTCH in the current cell.
  • the "sc-mtch-InfoList-Enh-r15" in the above signaling may be used to represent an enhanced service configuration information list (sc-mtch-InfoList-Enh) carried on the SC-MCCH.
  • the EUTRAN may configure a non-anchor carrier that is different from the deployment mode of the anchor carrier in the sc-mtch-InfoList-Enh, and the non-anchor carrier may be applied in an independent deployment mode or an in-band deployment mode/protection band deployment mode. (EUTRAN configures the downlink non-anchor carriers for which the mode of operation, standalone or inband/guardband, is different from the anchor carrier in sc-mtch-InfoList-Enh.)
  • SC-MTCH-InfoList-NB-r14 in the above signaling may be used to indicate that the enhanced service configuration information list (sc-mtch-InfoList-Enh) can be used.
  • a list of new service configuration information is formed by concatenating with the original service configuration information list (sc-mtch-InfoList).
  • the terminal device may send support for carrier deployment mode enhancements to the network device (eg, may be a base station or a positioning server).
  • the positioning server can perform positioning measurement for the terminal device by configuring the frequency point according to the supported capability sent by the terminal device.
  • the method for enhancing the carrier deployment mode between the network device and the terminal device is designed, so that the incompatibility problem caused by the enhancement of the carrier deployment mode in the NB-IOT terminal in the existing network can be avoided.
  • the communication method provided by the embodiment of the present invention is described in detail below with reference to FIG. 1 to FIG. 3 .
  • the communication device provided by the embodiment of the present invention will be described in detail below with reference to FIG. 4 .
  • FIG. 4 is a schematic structural diagram of a communication device according to an embodiment of the present invention.
  • the communication device 400 of FIG. 4 can perform the communication method described in any of the embodiments of FIGS. 1-3.
  • the communication device 400 of FIG. 4 can include at least one processor 410 and a communication interface 420.
  • the communication interface 420 is configured to perform information interaction between the communication device 400 and other communication devices, and when the program instructions are executed in the at least one processor 410, cause the communication device 400 to implement the communication method described in any of the above embodiments.
  • the term "and/or” is merely an association relationship describing an associated object, indicating that there may be three relationships.
  • a and/or B may indicate that A exists separately, and A and B exist simultaneously, and B cases exist alone.
  • the character "/" in this article generally indicates that the contextual object is an "or" relationship.
  • the computer program product includes one or more computer instructions.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transmission to another website site, computer, server or data center via wired (eg coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (such as a digital video disc (DVD)), or a semiconductor medium (such as a solid state disk (SSD)).
  • a magnetic medium for example, a floppy disk, a hard disk, a magnetic tape
  • an optical medium such as a digital video disc (DVD)
  • a semiconductor medium such as a solid state disk (SSD)
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
  • the technical solution of the present application which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
  • the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program code. .

Landscapes

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

Abstract

本申请提供了一种通信方法、通信设备及计算机程序存储介质，所述通信方法包括：网络设备向终端设备发送第一配置信息，所述第一配置信息包括非锚点载波配置信息，当锚点载波为独立部署模式时，非锚点载波应用于带内部署模式或保护带部署模式，当锚点载波为带内部署模式或保护带部署模式时，非锚点载波应用于独立部署模式。上述技术方案中，设计了新的载波部署模式组合的使用方法，从而可以避免现网中NB-IOT终端因支持载波部署模式的增强而造成的不兼容问题。

Description

一种通信方法、通信设备及计算机程序存储介质 技术领域
本申请涉及通信领域，并且更具体地，涉及一种通信方法、通信设备及计算机程序存储介质。
背景技术
在第五代移动通信技术(5th-generation，5G)中5G新空口(new radio，NR)项目中，物联网(internet of things，IOT)将成为未来通信领域的一项重要应用。可能涵盖智能抄表、医疗检测监控、物流检测、工业检测监控、汽车联网、智能社区以及可穿戴设备通信等领域。一种典型的蜂窝物联网是窄带物联网(narrow band-IOT，NB-IOT)。
在现有的NB-IOT版本中，为了减少终端的复杂度，运营商对于锚点载波和非锚点载波的部署模式有一定限制。在NB-IOT最新的讨论中，希望可以扩展支持的载波部署组合(将4个不支持的载波部署组合变为4个支持的载波部署组合)。但是由于上述新的部署模式组合需要在新版本中实现，而现有的NB-IOT终端只能支持传统的部署模式，无法支持新的部署模式组合。如果直接在相应的载波配置中配置新的载波，这样会造成老版本的(现有的)NB-IOT终端不兼容。
因此，如何可以避免新的载波部署模式组合对于现网中的NB-IOT终端的影响成为亟需要解决的问题。
发明内容
本申请提供一种通信方法、通信设备及计算机程序存储介质，可以避免新的载波部署模式组合对于现网中的NB-IOT终端的影响。
第一方面，提供了一种通信方法，包括：网络设备向终端设备发送第一配置信息，所述第一配置信息包括非锚点载波配置信息，当锚点载波为独立部署模式时，非锚点载波应用于带内部署模式或保护带部署模式，当锚点载波为带内部署模式或保护带部署模式时，非锚点载波应用于独立部署模式。
上述技术方案中，网络设备提供了非锚点载波的配置信息供终端设备使用，可以使得载波可应用于4种新的部署模式，从而可以避免现网中NB-IOT终端因支持载波部署模式的增强而造成的不兼容问题。
在一种可能的实现方式中，所述方法还包括：网络设备向终端设备发送所述第一配置信息和第二配置信息，所述第二配置信息包括非锚点载波的配置信息，当锚点载波为带内部署模式时，非锚点载波应用于带内部署模式或保护带部署模式，当锚点载波为保护带部署模式时，非锚点载波应用于带内部署模式或保护带部署模式，当锚点载波为独立部署模式时，非锚点载波应用于独立部署模式。
上述技术方案中，网络设备向终端设备提供非锚点载波的两种配置信息，第一种非 锚点载波的配置信息可以使得载波可应用于4种新的部署模式，第二种非锚点载波的配置信息可以使得载波可应用于旧的部署模式组合，从而可以避免现网中NB-IOT终端因支持载波部署模式的增强而造成的不兼容问题。
在一种可能的实现方式中，所述当锚点载波为独立部署模式时，非锚点载波应用于带内部署模式，所述第一配置信息中的非锚点载波配置信息包括以下长期演进LTE小区信息：如果所述非锚点载波的物理小区与所述LTE小区的ID相同，所述LTE小区信息包括所述LTE小区控制信道占用的符号数信息；或者，所述非锚点载波到所述LTE中心频点的参考信号。
上述技术方案中，网络设备可以提供相应的非锚点载波配置信息供终端设备使用，从而可以支持增强的载波部署模式组合。
在一种可能的实现方式中，所述当锚点载波为独立部署模式时，非锚点载波应用于带内部署模式，所述第一配置信息中的非锚点载波配置信息包括以下长期演进LTE小区信息：如果所述非锚点载波的物理小区与所述LTE小区的ID不相同，所述LTE小区信息包括所述LTE小区控制信道占用的符号数信息；或者，所述LTE小区参考信号CRS的端口信息。
上述技术方案中，网络设备可以提供相应的非锚点载波配置信息供终端设备使用，从而可以支持增强的载波部署模式组合。
在一种可能的实现方式中，当所述非锚点载波应用于保护带部署模式或独立部署模式时，所述非锚点载波配置信息包括第一指示信息，所述第一指示信息包括：指示所述非锚点载波应用于保护带部署模式；或者，指示所述非锚点载波应用于独立部署模式。
在一种可能的实现方式中，所述当锚点载波为独立部署模式时，非锚点载波应用于带内部署模式或保护带部署模式，当锚点载波为带内部署模式或保护带部署模式时，非锚点载波应用于独立部署模式，包括：当所述锚点载波为独立部署模式时，用于寻呼的非锚点载波应用于带内部署模式或保护带部署模式；当所述锚点载波为保护带部署模式或带内部署模式，用于寻呼的非锚点载波应用于独立部署模式。
在一种可能的实现方式中，所述当锚点载波为独立部署模式时，非锚点载波应用于带内部署模式或保护带部署模式，当锚点载波为带内部署模式或保护带部署模式时，非锚点载波应用于独立部署模式，包括：当所述锚点载波为独立部署模式时，用于随机接入的非锚点载波应用于带内部署模式或保护带部署模式；当所述锚点载波为保护带部署模式或带内部署模式，用于随机接入的非锚点载波应用于独立部署模式。
在一种可能的实现方式中，所述当锚点载波为独立部署模式时，非锚点载波应用于带内部署模式或保护带部署模式，当锚点载波为带内部署模式或保护带部署模式时，非锚点载波应用于独立部署模式，包括：当所述锚点载波为独立部署模式时，用于承载多播业务的非锚点载波应用于带内部署模式或保护带部署模式；当所述锚点载波为保护带部署模式或带内部署模式，用于承载多播业务的非锚点载波应用于独立部署模式。
在一种可能的实现方式中，所述非锚点载波的配置信息承载在系统信息块SIB22上。
在一种可能的实现方式中，所述非锚点载波的配置信息承载在多媒体广播组播服务控制信道SC-MCCH上。
在一种可能的实现方式中，所述第一配置信息中配置的载波数量与所述第二配置信 息中配置的载波数量之和不大于所述第二配置信息中配置的载波数量的最大值。
第二方面，提供了一种通信方法，包括：终端设备接收网络设备发送的第一配置信息，所述第一配置信息包括非锚点载波配置信息，当锚点载波为独立部署模式时，非锚点载波应用于带内部署模式或保护带部署模式，当锚点载波为带内部署模式或保护带部署模式时，非锚点载波应用于独立部署模式。
在一种可能的实现方式中，所述方法还包括：终端设备接收网络设备发送的第一配置信息和第二配置信息，所述第二配置信息包括非锚点载波的配置信息，当锚点载波为带内部署模式时，非锚点载波应用于带内部署模式或保护带部署模式，当锚点载波为保护带部署模式时，非锚点载波应用于带内部署模式或保护带部署模式，当锚点载波为独立部署模式时，非锚点载波应用于独立部署模式。
在一种可能的实现方式中，所述当锚点载波为独立部署模式时，非锚点载波应用于带内部署模式，所述第一配置信息中的非锚点载波配置信息包括以下长期演进LTE小区信息：如果所述非锚点载波的物理小区与所述LTE小区的ID相同，所述LTE小区信息包括所述LTE小区控制信道占用的符号数信息；或者，所述非锚点载波到所述LTE中心频点的参考信号。
在一种可能的实现方式中，所述当锚点载波为独立部署模式时，非锚点载波应用于带内部署模式，所述第一配置信息中的非锚点载波配置信息包括以下长期演进LTE小区信息：如果所述非锚点载波的物理小区与所述LTE小区的ID不相同，所述LTE小区信息包括所述LTE小区控制信道占用的符号数信息；或者，所述LTE小区参考信号CRS的端口信息。
在一种可能的实现方式中，当所述非锚点载波应用于保护带部署模式或独立部署模式时，所述非锚点载波配置信息包括第一指示信息，所述第一指示信息包括：指示所述非锚点载波应用于保护带部署模式；或者，指示所述非锚点载波应用于独立部署模式。
在一种可能的实现方式中，所述当锚点载波为独立部署模式时，非锚点载波应用于带内部署模式或保护带部署模式，当锚点载波为带内部署模式或保护带部署模式时，非锚点载波应用于独立部署模式，包括：所述终端设备将所述第一配置信息串接在所述第二配置信息之后，形成第三配置信息；所述终端设备在所述第三配置信息中选取用于寻呼的非锚点载波，当所述锚点载波为独立部署模式时，所述用于寻呼的非锚点载波应用于带内部署模式或保护带部署模式；当所述锚点载波为保护带部署模式或带内部署模式，所述用于寻呼的非锚点载波应用于独立部署模式。
在一种可能的实现方式中，所述当锚点载波为独立部署模式时，非锚点载波应用于带内部署模式或保护带部署模式，当锚点载波为带内部署模式或保护带部署模式时，非锚点载波应用于独立部署模式，包括：所述终端设备将所述第一配置信息串接在所述第二配置信息之后，形成第三配置信息；所述终端设备在所述第三配置信息中选取用于随机接入的非锚点载波，当所述锚点载波为独立部署模式时，所述用于随机接入的非锚点载波应用于带内部署模式或保护带部署模式；当所述锚点载波为保护带部署模式或带内部署模式，所述用于随机接入的非锚点载波应用于独立部署模式。
在一种可能的实现方式中，所述当锚点载波为独立部署模式时，非锚点载波应用于带内部署模式或保护带部署模式，当锚点载波为带内部署模式或保护带部署模式时，非 锚点载波应用于独立部署模式，包括：所述终端设备将所述第一配置信息串接在所述第二配置信息之后，形成第三配置信息；所述终端设备在所述第三配置信息中选取用于发送多播业务的非锚点载波，当所述锚点载波为独立部署模式时，所述用于发送多播业务的非锚点载波应用于带内部署模式或保护带部署模式；当所述锚点载波为保护带部署模式或带内部署模式，所述用于发送多播业务的非锚点载波应用于独立部署模式。
在一种可能的实现方式中，所述非锚点载波的配置信息承载在系统信息块SIB22上。
在一种可能的实现方式中，所述非锚点载波的配置信息承载在多媒体广播组播服务控制信道SC-MCCH上。
在一种可能的实现方式中，所述第一配置信息中配置的载波数量与所述第二配置信息中配置的载波数量之和不大于所述第二配置信息中配置的载波数量的最大值。
第三方面，提供了一种通信设备，所述通信设备包括：至少一个处理器和通信接口，所述通信接口用于所述通信设备与其他通信设备进行信息交互，当程序指令在所述至少一个处理器中执行时，使得所述通信设备实现第一方面或第一方面的任意一种可能的实现方式中以及第二方面或第二方面的任意一种可能的实现方式中所述的方法在如下任一设备上的功能：所述网络设备和所述终端设备。
第四方面，提供了一种计算机程序存储介质，所述计算机程序存储介质具有程序指令，当所述程序指令被直接或者间接执行时，使得第一方面或第一方面的任意一种可能的实现方式中以及第二方面或第二方面的任意一种可能的实现方式中所述的方法在如下任一设备上的功能得以实现：所述网络设备和所述终端设备。
第五方面，提供了一种芯片系统，所述芯片系统包括至少一个处理器，当程序指令在所述至少一个处理器中执行时，使得第一方面或第一方面的任意一种可能的实现方式中以及第二方面或第二方面的任意一种可能的实现方式中所述的方法在如下任一设备上的功能得以实现：所述网络设备和所述终端设备。
第六方面，提供了一种通信系统，所述通信系统包括：如第三方面提供的通信设备。
附图说明
图1是本申请实施例提供的通信方法的示意性流程图。
图2是本申请另一实施例提供的通信方法的示意性流程图。
图3是本申请另一实施例提供的通信方法的示意性流程图。
图4是本申请实施例提供的通信设备的示意性结构图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种要求终端低复杂度、低功耗的通信系统，例如：基于蜂窝的窄带物联网(narrow band internet of things，NB-IoT)系统、全球移动通讯(global system of mobile communication，GSM)系统、码分多址(code division multiple access，CDMA)系统、宽带码分多址(wideband code division multiple access，WCDMA)系统、通用分组无线业务(general packet radio service，GPRS)、长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时 分双工(time division duplex，TDD)、通用移动通信系统(universal mobile telecommunication system，UMTS)、全球互联微波接入(worldwide interoperability for microwave access，WiMAX)通信系统、未来的第五代(5th generation，5G)系统或新无线(new radio，NR)等。
本申请实施例对终端设备的类型不做具体限定，例如可以是用户设备、接入终端、终端设备、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、无线网络设备、用户代理或用户装置。终端可以包括但不限于移动台(mobile station，MS)、移动电话(mobile telephone)、用户设备(user equipment，UE)、手机(handset)、便携设备(portable equipment)、蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字处理(personal digital assistant，PDA)、物流用的射频识别(radio frequency identification，RFID)终端设备，具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它设备、车载设备、可穿戴设备、物联网、车辆网中的终端设备以及未来5G网络中的终端设备或者未来演进的公共陆地移动网络(public land mobile network，PLMN)网络中的终端设备等。
作为示例而非限定，在本发明实施例中，该终端设备还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
本申请实施例对网络设备的类型不做具体限定，可以是用于与终端设备通信的任何设备，该网络设备例如可以是全球移动通讯(global system of mobile communication，GSM)或码分多址(code division multiple access，CDMA)中的基站(base transceiver station，BTS)，也可以是宽带码分多址(wideband code division multiple access，WCDMA)系统中的基站(NodeB，NB)，还可以是长期演进(long term evolution，LTE)系统中的演进型基站(evolutional Node B，eNB或eNodeB)，还可以是云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器，或者该网络设备例如可以为中继站、接入点、车载设备、可穿戴设备以及未来5G网络中的网络设备或者未来演进的PLMN网络中的网络设备等。
作为一种可能的方式，网络设备可以由集中式单元(centralized unit,CU)和分布式单元(distributed unit,DU)构成。一个CU可以连接一个DU，或者也可以多个DU共用一个CU，可以节省成本，以及易于网络扩展。CU和DU的切分可以按照协议栈切分，其中一种可能的方式是将无线资源控制(radio resource control，RRC)、服务数据映射协议栈(service data adaptation protocol，SDAP)以及分组数据汇聚协议(packet data convergence protocol，PDCP)层部署在CU，其余的无线链路控制(Radio Link Control，RLC)层、介质访问控制(media access control，MAC)层以及物理层部署在DU。
本申请实施例对提及的载波的部署模式不做具体限定，作为一个示例，载波的部署模式可以是独立部署模式(standalone)，独立的载波部署模式可以不依赖于其他通信系统，例如，独立部署模式的载波部署带宽可以与长期演进(long term evolution，LTE)小区完全解耦。作为另一个示例，载波的部署模式可以是保护带部署模式(guardband)，保护带部署模式的载波可以不占用其他通信系统的资源，例如，保护带部署模式的载波可以不占用LTE资源，可以部署在LTE边缘保频带中未使用的资源块上。作为另一个示例，载波的部署还可以是带内部署模式(inband)，带内部署模式的载波可以部署在其他通信系统的工作带宽中，例如，带内部署模式的载波可以部署在LTE的工作带宽中。
本申请实施例对提及的载波的分类不做具体限制，可以根据载波上承载的信息的不同，将该载波分为不同的类型。作为一个示例，可以将承载同步信号、系统广播的载波称为锚点载波(anchor carrier)。作为另一个示例，可以将承载单播传输、寻呼和随机接入的载波称为非锚点载波(non-anchor carrier)。
下面以载波的三种部署模式(standalone、guardband、inband)以及载波两种分类(anchor carrier、non-anchor carrier)为例进行说明。
上文指出，为了减少终端的复杂度，现有的NB-IOT版本(Rel-13/14)中对于锚点载波(anchor carrier)以及非锚点载波(non-anchor carrier)的三种部署模式组合有一定的限制。如下表1所示的锚点载波和非锚点载波的部署组合(anchor and non-anchor carrier development combinations)，锚点载波和非锚点载波的三种载波部署模式(独立部署模式standalone、保护带部署模式guardband、带内部署模式inband)的组合中，有4种部署模式为不支持(invalid)，其分别为：锚点载波为独立部署模式时，非锚点载波为带内部署模式或保护带部署模式；锚点载波为带内部署模式或保护带部署模式，非锚点载波为独立部署模式。
表1锚点载波和非锚点载波的部署组合
Figure PCTCN2018076527-appb-000001
在最新的讨论中，希望可以将上述4种invalid的载波部署组合变为可以支持(valid)的载波部署组合。如果直接在相应的载波配置中配置上述4种支持的载波部署组合，会造成老版本的(现有的)NB-IOT终端不兼容。
下面对本申请实施例提供的通信方法进行详细描述。
图1是本申请实施例提供的通信方法的示意性流程图。图1的方法包括：
步骤110：网络设备向终端设备发送第一配置信息，所述第一配置信息包括非锚点载波配置信息。
本申请实施例中，网络设备可以提供非锚点载波的配置信息供终端设备使用，该非锚点载波可以应用于4种新的载波部署组合，而不是直接在相应的载波配置中配置新的载波，从而可以避免为了实现载波部署模式的增强而造成的现网中NB-IOT终端不兼容问题。
本申请实施例中网络设备可以向终端设备发送第一配置信息，该第一配置信息可以包括每一个非锚点载波所包含的配置信息，第一配置信息也可以称为第一配置信息列表。第一配置信息中的非锚点载波可以应用于以下4种新的载波部署模式中的至少一种。
如果锚点载波为独立部署模式时，第一配置信息中的非锚点载波可以应用于带内部署模式。如果锚点载波为独立部署模式时，第一配置信息中的非锚点载波可以应用于保护带部署模式。如果锚点载波为带内部署模式时，第一配置信息中的非锚点载波可以应用于独立部署模式。如果锚点载波为保护带部署模式时，第一配置信息中的非锚点载波可以应用于独立部署模式。也就是说，在第一配置信息中的非锚点载波可以应用的场景包括上文表1中提及的4种invalid的载波部署组合中的至少一种。
本申请实施例中对第一配置信息中可以包括的非锚点载波的配置信息不做具体限定，可以是任何有关可以供终端设备使用的非锚点载波的配置信息。
可选地，在一些实施例中，如果锚点载波的部署模式为独立部署模式，非锚点载波为带内部署模式时，网络设备可以在每一个非锚点载波的配置信息中发送LTE小区的相关信息。作为一个示例，该非锚点载波的配置信息可以包括该LTE小区控制信道所占用的符号数信息。作为另一个示例，如果该非锚点载波的物理小区ID(physical cell ID，PCI)与LTE小区的ID相同时，该非锚点载波的配置信息还可以包括该非锚点载波到LTE中心频点的参考信号。作为另一个示例，如果该非锚点载波的物理小区ID(physical cell ID，PCI)与LTE小区的ID不相同时，该非锚点载波的配置信息还可以包括该LTE的小区固有参考信号(cell-specific reference signal，CRS)的端口信息。
可选地，在一些实施例中，如果锚点载波的部署模式为独立部署模式，非锚点载波的部署模式为独立部署模式或者保护带部署模式时，该第一配置信息中的非锚点载波配置信息可以包括第一指示信息，该第一指示信息可以指示终端设备该锚点载波的部署模式是独立部署模式还是保护带部署模式。
下面结合具体的信令更加详细的描述本申请实施例中提及的第一配置信息中的非锚点载波的配置信息。
Figure PCTCN2018076527-appb-000002
Figure PCTCN2018076527-appb-000003
具体的，上文信令中的“inband Carrier Info-r13”可以用于表示载波的配置信息，该载波可以应用于带内部署模式。
上文信令中的“entea Control Region Size-r13”可以用于表示如果锚点载波的部署模式为独立部署模式，非锚点载波可应用于带内部署模式时，该非锚点载波的配置信息可以包括LTE小区控制信道所占用的符号数信息。
上文信令中的“samePCI-Indicator-r13”可以用于表示当锚点载波的部署模式为独立部署模式，非锚点载波可应用于带内部署模式时，该非锚点载波的PCI与LTE小区的ID相同或不相同时，该非锚点载波可以包括的配置信息。
上文信令中的“samePCI-r13”、“index To Mid PRB-r13”可以用于表示如果该非锚点载波的PCI与LTE小区的ID相同时，该非锚点载波的配置信息可以包括该非锚点载波到LTE中心频点的参考信号。
上文信令中的“differentPCI-r13”、“eutra-Num CRS-Ports-r13”可以用于表示如果该非锚点载波的PCI与LTE小区的ID相同时，该非锚点载波的配置信息可以包括LTE小区CRS的端口信息。
上文信令中的“Cond non-anchor-guardband-or-standalone”可以用于表示如果非锚点载波的部署模式可以是独立部署模式，也可以是保护带部署模式时，该非锚点载波的配置信息可以包括指示信息，该指示信息可以用于指示该非锚点载波的部署模式是独立部署模式还是保护带部署模式。
上文信令中的“non-anchor-inband”可以用于表示该字段强制性表示了非锚点载波可以应用于带内部署模式，否则该字段是不存在的。(The field is mandatory present if the non-anchor carrier is an inband carrier；otherwise it is not present.)
上文信令中的“non-anchor-guardband-or-standalone”可以用于表示该字段强制性表示了非锚点载波可以应用于保护带部署模式还是独立部署模式，否则该字段是不存在的。(The field is mandatory present if the non-anchor carrier is an guardband or standalone carrier；otherwise it is not present.)
上文信令中的“anchor-guardband-or-standalone”可以用于表示该字段强制性表示了锚点载波可以应用于保护带部署模式还是独立部署模式，否则该字段是不存在的。(The  field is mandatory present if operation Mode Info is set to guardband or standalone in the MIB；otherwise it is not present.)
本申请实施例中，网络设备发送非锚点载波的配置信息供终端设备使用，从而可以避免为了实现载波部署模式的增强而造成的现网中NB-IOT终端不兼容问题。
可选地，在一些实施例中，图1的方法还包括：网络设备可以向终端设备发送第一配置信息和第二配置信息，其中第一配置信息以及第二配置信息可以包括非锚点载波的配置信息。第一配置信息中的非锚点载波可以应用于上文提及的4种新的载波部署组合中的至少一种(例如表1中提及的4种invalid组合中的至少一种，当锚点载波为独立部署模式时，非锚点载波应用于带内部署模式或保护带部署模式，当锚点载波为带内部署模式或保护带部署模式时，非锚点载波应用于独立部署模式)第二配置信息中的非锚点载波可以应用于旧的载波部署组合(例如表1中提及的5种valid组合中的至少一种，当锚点载波为带内部署模式时，非锚点载波应用于带内部署模式或保护带部署模式，当锚点载波为保护带部署模式时，非锚点载波应用于带内部署模式或保护带部署模式，当锚点载波为独立部署模式时，非锚点载波应用于独立部署模式)
本申请实施例中，网络设备将可以应用于新的部署组合与旧的部署组合的非锚点载波的配置信息分别发送给终端设备，供终端设备使用，从而可以避免为了实现载波部署模式的增强而造成的现网中NB-IOT终端不兼容问题。
可选地，在一些实施例中，网络设备可以向终端设备发送用于寻呼的非锚点载波的配置信息(其中非锚点载波可以包括的配置信息可以参见上文的描述，此处不再赘述)。当锚点载波为独立部署模式时，该非锚点载波可以应用于带内部署模式或保护带部署模式。当锚点载波为保护带部署模式或带内部署模式时，该非锚点载波可以应用于独立部署模式。
可选地，在一些实施例中，终端设备可以接收网络设备发送的非锚点载波的配置信息，并且可以根据该非锚点载波的相应配置信息接收寻呼。
可选地，在一些实施例中，网络设备可以向终端设备发送用于随机接入的配置信息。当锚点载波为独立部署模式时，该非锚点载波可以应用于带内部署模式或保护带部署模式。当锚点载波为保护带部署模式或带内部署模式时，该非锚点载波可以应用于独立部署模式。
可选地，在一些实施例中，终端设备可以接收网络设备发送的非锚点载波的配置信息，并且可以随机选取发起随机接入的上行载波。
可选地，在一些实施例中，网络设备向终端设备发送的非锚点载波的配置信息可以承载在系统信息块(system information block，SIB)22上。作为一个示例，网络设备可以通过广播SIB22，可以将非锚点载波的配置信息发送给终端设备。
下面结合具体的例子，更加详细的描述本申请实施例中提及的用于寻呼或随机接入的非锚点的配置信息的发送和使用方法。应注意，图2的例子仅仅是为了帮助本领域技术人员理解本申请实施例，而非要将申请实施例限制于所示例的具体数值或具体场景。本领域技术人员根据所给出的图2的例子，显然可以进行各种等价的修改或变化，这样的修改和变化也落入本申请实施例的范围内。
应理解，图2中的基站(eNB)可以对应于上文中的网络设备，用户设备(user  equipment，UE)可以对应于上文中的终端设备。
步骤210中：eNB可以向UE系统广播的载波配置信息列表可以承载在SIB22上。可以包括下行载波配置列表(dl-confilist)、下行载波配置列表增强版(dl-confilist-enh)、上行载波配置列表(ul-confilist)、上行载波配置列表增强版(ul-confilist-enh)。上述4种载波配置列表可以包括每一个非锚点载波的配置信息，下面分别对上述4种载波配置列表进行详细描述。
下行载波配置列表(dl-confilist)中的非锚点载波可以应用于如表1中提及的5种valid组合中的至少一种，该非锚点载波可以用于寻呼。
上行载波配置列表(ul-confilist)中的非锚点载波可以应用于如表1中提及的5种valid组合中的至少一种，该非锚点载波可以用于随机接入。
如果锚点载波的部署模式可以是独立部署模式(standalone)，可以将用于寻呼的载波部署模式为带内部署模式(inband)或保护带部署模式(guardband)的非锚点载波(non-anchor carrier)的配置信息配置在下行配置列表增强版(dl-confilist-enh，也就是如上文提及的第一配置信息或第一配置信息列表)，该非锚点载波可以应用于例如表1中提及的4种invalid组合中的至少一种。
如果锚点载波的部署模式可以是带内部署模式(inband)或保护带部署模式(guardband)，可以将用于寻呼的载波部署模式为独立部署模式(standalone)的非锚点载波(non-anchor carrier)的配置信息配置在下行配置列表增强版(dl-confilist-enh，也就是如上文提及的第一配置信息或第一配置信息列表)，该非锚点载波可以应用于例如表1中提及的4种invalid组合中的至少一种。
如果锚点载波的部署模式可以是独立部署模式(standalone)，可以将用于随机接入的载波部署模式为带内部署模式(inband)或保护带部署模式(guardband)的非锚点载波(non-anchor carrier)的配置信息配置在上行配置列表增强版(ul-confilist-enh，也就是如上文提及的第一配置信息或第一配置信息列表)，该非锚点载波可以应用于例如表1中提及的4种invalid组合中的至少一种。
如果锚点载波的部署模式可以是带内部署模式(inband)或保护带部署模式(guardband)，可以将用于随机接入的载波部署模式为独立部署模式(standalone)的非锚点载波(non-anchor carrier)的配置信息配置在下行配置列表增强版(ul-confilist-enh，也就是如上文提及的第一配置信息或第一配置信息列表)，该非锚点载波可以应用于例如表1中提及的4种invalid组合中的至少一种。
UE可以获取SIB22中的两个上行载波列表以及两个下行载波列表，并可以生成新的用于寻呼的下行载波列表以及用于随机接入的上行载波列表。
具体的，如果该UE是现网中的NB-IOT终端设备，UE可以在下行载波配置列表(dl-confilist)中选取自身的寻呼请求，并且可以根据该载波配置列表中的非锚点载波的配置信息接收寻呼。
如果该UE是现网中的NB-IOT终端设备，UE可以在上行载波配置列表(ul-confilist)中随机选取可以发起随机接入的上行载波。
具体的，如果该UE是新版本的NB-IOT网络终端设备，UE可以将下行载波配置列表增强版(dl-confilist-enh)串接在下行载波配置列表(dl-confilist)之后，可以生成一个 新的下行载波配置列表。UE可以在新的下行载波配置列表中选取自身的寻呼请求，并且可以根据该载波配置列表中的非锚点载波的配置信息接收寻呼。
如果该UE是新版本的NB-IOT网络终端设备，UE可以将上行载波配置列表增强版(ul-confilist-enh)串接在上行载波配置列表(ul-confilist)之后，可以生成一个新的上行载波配置列表。UE可以在新的上行载波配置列表中随机选取可以发起随机接入的上行载波。
应理解，系统广播的上行载波配置列表增强版(ul-confilist-enh)以及下行载波配置列表增强版(dl-confilist-enh)中的非锚点载波可以应用于下列载波部署模式组合。
如果锚点载波的部署模式为独立部署模式，用于寻呼或随机接入的非锚点载波可以应用于带内部署模式或保护带部署模式。
如果锚点载波的部署模式为带内部署模式或保护带部署模式，用于寻呼或随机接入的非锚点载波可以应用于独立部署模式。
应理解，增强版的载波配置列表(例如，ul-confilist-enh以及dl-confilist-enh)中可以配置的非锚点载波数量与原有的载波配置列表(例如，ul-confilist以及dl-confilist)中可以配置的非锚点载波数量之和，不能大于原有的载波配置列表中可以配置的非锚点载波的最大值。
下面结合具体的信令更加详细的描述本申请实施例中提及的SIB22中的载波配置列表。
Figure PCTCN2018076527-appb-000004
具体的，上文信令中的“DL-ConfigCommonList-NB-r14”可以用于表示原有的下行载波配置列表。
上文信令中的“UL-ConfigCommonList-NB-r14”可以用于表示原有的上行载波配置列表。
上文信令中的“dl-ConfigList-Enh-r15”可以用于表示增强版的下行载波配置列表。
上文信令中的“ul-ConfigList-Enh-r15”可以用于表示增强版的上行载波配置列表。
上文信令中的“DL-ConfigCommonList-NB-r14”可以用于表示原有的下行载波配置列表中的非锚点载波的相关配置信息可以用于承接寻呼。(List of DL non-anchor carriers and associated configuration that can be used for paging and/or random access.)
上文信令中的“dl-ConfigList-Enh-r15”表示演进的通用移动通信系统陆地无线接入网(evolved universal mobile telecommunication system terrestrial radio access network，EUTRAN)可以在dl-ConfigList-Enh中配置一个可以应用于独立部署模式或带内部署模式/保护带部署模式的非锚点载波。(EUTRAN configures DL non-anchor carriers for which the mode of operation,standalone or inband/guardband,is different from the anchor carrier in dl-ConfigList-Enh.)
上文信令中的“ dl-ConfigList-Enh-r15 DL-ConfigCommonList-NB-r14”可以用于表示如果UE可以支持载波部署模式的增强，可以将增强版的下行载波配置列表与原有的下行载波配置列表串接形成一个新的载波配置列表，可以用于承接寻呼。增强版的载波配置列表与原有的载波配置列表中可以配置的非锚点载波数量之和，不能大于原有的载波配置列表中可以配置的非锚点载波的最大值。(If the UE supports operation mode enhancements,it appends dl-ConfigList-Enh to the end of dl-ConfigList to create a single list for paging and/or random access.The total maximum number of non-anchor carriers in dl-ConfigList and dl-ConfigList-Enh is maxNonAnchorCarriers-NB-r14.)
上文信令中用于的“ ul-ConfigList-Enh-r15 UL-ConfigCommonList-NB-r14”可以参考信令“ dl-ConfigList-Enh-r15 DL-ConfigCommonList-NB-r14”的相关描述，此处不再赘述。
可选地，在一些实施例中，当锚点载波为独立部署模式，用于承载多播业务的非锚点载波应用于带内部署模式或保护带部署模式时，网络设备可以向终端设备广播业务配置信息列表。当锚点载波为保护带部署模式或带内部署模式，用于承载多播业务的非锚点载波应用于独立部署模式时，网络设备可以向终端设备广播业务配置信息列表。该业务配置信息列表中可以对上述多播业务进行配置。
可选地，在一些实施例中，网络设备向终端设备发送的业务配置信息列表可以承载在多媒体广播组播服务控制信道(multimedia broadcast multicast service control channel，SC-MCCH)上。作为一个示例，网络设备可以通过广播SC-MCCH，可以将业务配置信息列表发送给终端设备。
下面结合具体的例子，更加详细的描述本申请实施例中提及的多播业务。应注意，图3的例子仅仅是为了帮助本领域技术人员理解本申请实施例，而非要将申请实施例限制于所示例的具体数值或具体场景。本领域技术人员根据所给出的图3的例子，显然可以进行各种等价的修改或变化，这样的修改和变化也落入本申请实施例的范围内。
在步骤310中：eNB可以向UE系统广播的业务配置信息列表可以承载在SC-MCCH上，可以包括原有的业务配置信息列表(sc-mtch-InfoList)以及增强版的业务配置信息列表(sc-mtch-InfoList-Enh)，业务配置信息列表中的每一个业务所在的非锚点载波的配置信息可以参见上文的描述，此处不再赘述。下面分别对上述2种业务配置信息列表进行详细描述。
原有业务配置信息列表(sc-mtch-InfoList)中可以配置的多播业务可以在非锚点载波上发送，给非锚点载波可以应用于如表1中提及的5种valid组合中的至少一种的。
如果锚点载波的部署模式是独立部署模式(standalone)，可以将用于承载多播业务的非锚点载波应用于带内部署模式(inband)或保护带部署模式(guardband)，可以将该多播业务配置在增强版的业务配置信息列表(sc-mtch-InfoList-Enh)中发送。
如果锚点载波的部署模式是带内部署模式(inband)或保护带部署模式(guardband)，可以将用于承载多播业务的非锚点载波应用于独立部署模式(standalone)，可以将该多播业务配置在增强版的业务配置信息列表(sc-mtch-InfoList-Enh)中发送。
UE可以获取SC-MCCH上承载的原有业务配置信息列表(sc-mtch-InfoList)以及增强版业务配置信息列表(sc-mtch-InfoList-Enh)，并且可以根据业务的ID，可以在相应的载波上使用相应的配置信息来接收多播业务。
应理解，系统广播的增强版业务配置信息列表(sc-mtch-InfoList-Enh)中可以发送多播业务的非锚点载波可以应用于下列载波部署模式组合。
如果锚点载波的部署模式为独立部署模式，用于发送多播业务的非锚点载波可以应用于带内部署模式或保护带部署模式。
如果锚点载波的部署模式为带内部署模式或保护带部署模式，用于发送多播业务的非锚点载波可以应用于独立部署模式。
应理解，增强版业务配置信息列表(sc-mtch-InfoList-Enh)中可以配置的多播业务的数量与原有业务配置信息列表(sc-mtch-InfoList)中的业务数量之和，不能大于原有业务配置信息列表中可以配置的业务数量的最大值。
下面结合具体的信令更加详细的描述本申请实施例中提及的承载在SC-MCCH上发送的多播业务列表。
Figure PCTCN2018076527-appb-000005
具体的，上文信令中的“sc-mtch-InfoList-r14”可以用于表示承载在SC-MCCH上的原有业务配置信息列表(sc-mtch-InfoList)，该列表可以提供用于发送多播业务的载波的配置信息。(Provides the configuration of each SC-MTCH in the current cell.)
上文信令中的“sc-mtch-InfoList-Enh-r15”可以用于表示承载在SC-MCCH上的增强版业务配置信息列表(sc-mtch-InfoList-Enh)。EUTRAN可以在该sc-mtch-InfoList-Enh中配置与锚点载波的部署模式不相同的非锚点载波，该非锚点载波可以应用于独立部署 模式或带内部署模式/保护带部署模式。(EUTRAN configures the downlink non-anchor carriers for which the mode of operation,standalone or inband/guardband,is different from the anchor carrier in sc-mtch-InfoList-Enh.)
具体的，上文信令中的“ sc-mtch-InfoList-Enh-r15 SC-MTCH-InfoList-NB-r14”可以用于表示可以将增强版业务配置信息列表(sc-mtch-InfoList-Enh)与原有业务配置信息列表(sc-mtch-InfoList)串接形成一个新的业务配置信息列表。
可选地，在一些实施例中，对于定位业务，终端设备可以向网络设备(例如，可以是基站或定位服务器)发送对于载波部署模式增强的支持能力。定位服务器可以根据终端设备发送的支持的能力为终端设备配置频点进行定位测量。
本申请实施例中，设计了网络设备与终端设备之间对于载波部署模式增强的使用方法，从而可以避免现网中NB-IOT终端因支持载波部署模式的增强而造成的不兼容问题。
上文结合图1-图3，详细描述了本发明实施例提供的通信方法，下面将结合图4，详细描述本发明实施例提供的通信设备。
图4是本发明实施例提供的通信设备的示意性结构图。图4中的通信设备400可以执行图1-图3的任一实施例描述的通信方法。图4的通信设备400可以包括至少一个处理器410和通信接口420。通信接口420用于所述通信设备400与其他通信设备进行信息交互，当程序指令在所述至少一个处理器410中执行时，使得所述通信设备400实现上文任一实施例描述的通信方法在如下任一设备上的功能：所述网络设备和所述终端设备。
应理解，在本发明实施例中，术语“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系。例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其他任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如数字视频光盘(digital video disc，DVD))、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认 为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (26)

  1. 一种通信方法，其特征在于，包括：
    网络设备向终端设备发送第一配置信息，所述第一配置信息包括非锚点载波配置信息，当锚点载波为独立部署模式时，非锚点载波应用于带内部署模式或保护带部署模式，当锚点载波为带内部署模式或保护带部署模式时，非锚点载波应用于独立部署模式。
  2. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    网络设备向终端设备发送所述第一配置信息和第二配置信息，所述第二配置信息包括非锚点载波的配置信息，当锚点载波为带内部署模式时，非锚点载波应用于带内部署模式或保护带部署模式，当锚点载波为保护带部署模式时，非锚点载波应用于带内部署模式或保护带部署模式，当锚点载波为独立部署模式时，非锚点载波应用于独立部署模式。
  3. 如权利要求1或2所述的方法，其特征在于，所述当锚点载波为独立部署模式时，非锚点载波应用于带内部署模式，所述第一配置信息中的非锚点载波配置信息包括以下长期演进LTE小区信息：
    如果所述非锚点载波的物理小区与所述LTE小区的ID相同，所述LTE小区信息包括所述LTE小区控制信道占用的符号数信息；或者，
    所述非锚点载波到所述LTE中心频点的参考信号。
  4. 如权利要求1至3中任一项所述的方法，其特征在于，所述当锚点载波为独立部署模式时，非锚点载波应用于带内部署模式，所述第一配置信息中的非锚点载波配置信息包括以下长期演进LTE小区信息：
    如果所述非锚点载波的物理小区与所述LTE小区的ID不相同，所述LTE小区信息包括所述LTE小区控制信道占用的符号数信息；或者，
    所述LTE小区参考信号CRS的端口信息。
  5. 如权利要求1至4中任一项所述的方法，其特征在于，当所述非锚点载波应用于保护带部署模式或独立部署模式时，所述非锚点载波配置信息包括第一指示信息，所述第一指示信息包括：
    指示所述非锚点载波应用于保护带部署模式；或者，
    指示所述非锚点载波应用于独立部署模式。
  6. 如权利要求1至5中任一项所述的方法，其特征在于，所述当锚点载波为独立部署模式时，非锚点载波应用于带内部署模式或保护带部署模式，当锚点载波为带内部署模式或保护带部署模式时，非锚点载波应用于独立部署模式，包括：
    当所述锚点载波为独立部署模式时，用于寻呼的非锚点载波应用于带内部署模式或保护带部署模式；
    当所述锚点载波为保护带部署模式或带内部署模式，用于寻呼的非锚点载波应用于独立部署模式。
  7. 如权利要求1至5中任一项所述的方法，其特征在于，所述当锚点载波为独立部署模式时，非锚点载波应用于带内部署模式或保护带部署模式，当锚点载波为带内部署模式或保护带部署模式时，非锚点载波应用于独立部署模式，包括：
    当所述锚点载波为独立部署模式时，用于随机接入的非锚点载波应用于带内部署模式或保护带部署模式；
    当所述锚点载波为保护带部署模式或带内部署模式，用于随机接入的非锚点载波应用于独立部署模式。
  8. 如权利要求1至5中任一项所述的方法，其特征在于，所述当锚点载波为独立部署模式时，非锚点载波应用于带内部署模式或保护带部署模式，当锚点载波为带内部署模式或保护带部署模式时，非锚点载波应用于独立部署模式，包括：
    当所述锚点载波为独立部署模式时，用于承载多播业务的非锚点载波应用于带内部署模式或保护带部署模式；
    当所述锚点载波为保护带部署模式或带内部署模式，用于承载多播业务的非锚点载波应用于独立部署模式。
  9. 如权利要求6或7所述的方法，其特征在于，所述非锚点载波的配置信息承载在系统信息块SIB22上。
  10. 如权利要求8所述的方法，其特征在于，所述非锚点载波的配置信息承载在多媒体广播组播服务控制信道SC-MCCH上。
  11. 如权利要求1至10中任一项所述的方法，其特征在于，所述第一配置信息中配置的载波数量与所述第二配置信息中配置的载波数量之和不大于所述第二配置信息中配置的载波数量的最大值。
  12. 一种通信方法，其特征在于，包括：
    终端设备接收网络设备发送的第一配置信息，所述第一配置信息包括非锚点载波配置信息，当锚点载波为独立部署模式时，非锚点载波应用于带内部署模式或保护带部署模式，当锚点载波为带内部署模式或保护带部署模式时，非锚点载波应用于独立部署模式。
  13. 如权利要求12所述的方法，其特征在于，所述方法还包括：
    终端设备接收网络设备发送的第一配置信息和第二配置信息，所述第二配置信息包括非锚点载波的配置信息，当锚点载波为带内部署模式时，非锚点载波应用于带内部署模式或保护带部署模式，当锚点载波为保护带部署模式时，非锚点载波应用于带内部署模式或保护带部署模式，当锚点载波为独立部署模式时，非锚点载波应用于独立部署模式。
  14. 如权利要求12或13所述的方法，其特征在于，所述当锚点载波为独立部署模式时，非锚点载波应用于带内部署模式，所述第一配置信息中的非锚点载波配置信息包括以下长期演进LTE小区信息：
    如果所述非锚点载波的物理小区与所述LTE小区的ID相同，所述LTE小区信息包括所述LTE小区控制信道占用的符号数信息；或者，
    所述非锚点载波到所述LTE中心频点的参考信号。
  15. 如权利要求12至14中任一项所述的方法，其特征在于，所述当锚点载波为独立部署模式时，非锚点载波应用于带内部署模式，所述第一配置信息中的非锚点载波配置信息包括以下长期演进LTE小区信息：
    如果所述非锚点载波的物理小区与所述LTE小区的ID不相同，所述LTE小区信息包括所述LTE小区控制信道占用的符号数信息；或者，
    所述LTE小区参考信号CRS的端口信息。
  16. 如权利要求12至15中任一项所述的方法，其特征在于，当所述非锚点载波应用于保护带部署模式或独立部署模式时，所述非锚点载波配置信息包括第一指示信息，所述第一指示信息包括：
    指示所述非锚点载波应用于保护带部署模式；或者，
    指示所述非锚点载波应用于独立部署模式。
  17. 如权利要求12至16中任一项所述的方法，其特征在于，所述当锚点载波为独立部署模式时，非锚点载波应用于带内部署模式或保护带部署模式，当锚点载波为带内部署模式或保护带部署模式时，非锚点载波应用于独立部署模式，包括：
    所述终端设备将所述第一配置信息串接在所述第二配置信息之后，形成第三配置信息；
    所述终端设备在所述第三配置信息中选取用于寻呼的非锚点载波，当所述锚点载波为独立部署模式时，所述用于寻呼的非锚点载波应用于带内部署模式或保护带部署模式；
    当所述锚点载波为保护带部署模式或带内部署模式，所述用于寻呼的非锚点载波应用于独立部署模式。
  18. 如权利要求12至16中任一项所述的方法，其特征在于，所述当锚点载波为独立部署模式时，非锚点载波应用于带内部署模式或保护带部署模式，当锚点载波为带内部署模式或保护带部署模式时，非锚点载波应用于独立部署模式，包括：
    所述终端设备将所述第一配置信息串接在所述第二配置信息之后，形成第三配置信息；
    所述终端设备在所述第三配置信息中选取用于随机接入的非锚点载波，当所述锚点载波为独立部署模式时，所述用于随机接入的非锚点载波应用于带内部署模式或保护带部署模式；
    当所述锚点载波为保护带部署模式或带内部署模式，所述用于随机接入的非锚点载波应用于独立部署模式。
  19. 如权利要求12至16中任一项所述的方法，其特征在于，所述当锚点载波为独立部署模式时，非锚点载波应用于带内部署模式或保护带部署模式，当锚点载波为带内部署模式或保护带部署模式时，非锚点载波应用于独立部署模式，包括：
    所述终端设备将所述第一配置信息串接在所述第二配置信息之后，形成第三配置信息；
    所述终端设备在所述第三配置信息中选取用于发送多播业务的非锚点载波，当所述锚点载波为独立部署模式时，所述用于发送多播业务的非锚点载波应用于带内部署模式或保护带部署模式；
    当所述锚点载波为保护带部署模式或带内部署模式，所述用于发送多播业务的非锚点载波应用于独立部署模式。
  20. 如权利要求17或18所述的方法，其特征在于，所述非锚点载波的配置信息承载在系统信息块SIB22上。
  21. 如权利要19所述的方法，其特征在于，所述非锚点载波的配置信息承载在多媒体广播组播服务控制信道SC-MCCH上。
  22. 如权利要求12至21中任一项所述的方法，其特征在于，所述第一配置信息中配 置的载波数量与所述第二配置信息中配置的载波数量之和不大于所述第二配置信息中配置的载波数量的最大值。
  23. 一种通信设备，其特征在于，所述通信设备包括：
    至少一个处理器和通信接口，所述通信接口用于所述通信设备与其他通信设备进行信息交互，当程序指令在所述至少一个处理器中执行时，使得所述通信设备实现如权利要求1至22中任一所述的方法中在如下任一设备上的功能：所述网络设备和所述终端设备。
  24. 一种计算机程序存储介质，其特征在于，所述计算机程序存储介质具有程序指令，当所述程序指令被直接或者间接执行时，使得如权利要求1至22中任一所述的方法中在如下任一设备上的功能得以实现：所述网络设备和所述终端设备。
  25. 一种芯片系统，其特征在于，所述芯片系统包括至少一个处理器，当程序指令在所述至少一个处理器中执行时，使得如权利要求1至22中任一所述的方法中在如下任一设备上的功能得以实现：所述网络设备和所述终端设备。
  26. 一种通信系统，其特征在于，所述通信系统包括：如权利要求23所述的通信设备。
PCT/CN2018/076527 2018-02-12 2018-02-12 一种通信方法、通信设备及计算机程序存储介质 WO2019153350A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
CN201880089049.5A CN111771407B (zh) 2018-02-12 2018-02-12 一种通信方法、通信设备及计算机程序存储介质
CN202311548765.4A CN117769025A (zh) 2018-02-12 2018-02-12 一种通信方法、通信设备及计算机程序存储介质
PCT/CN2018/076527 WO2019153350A1 (zh) 2018-02-12 2018-02-12 一种通信方法、通信设备及计算机程序存储介质
JP2020542999A JP7073511B2 (ja) 2018-02-12 2018-02-12 通信方法、通信デバイス、およびコンピュータプログラム記憶媒体
EP18905486.9A EP3745789A4 (en) 2018-02-12 2018-02-12 COMMUNICATION PROCESS AND DEVICE AS WELL AS COMPUTER PROGRAM RECORDING MEDIA
US16/990,672 US12028879B2 (en) 2018-02-12 2020-08-11 Communication method, communications device, and computer program storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/076527 WO2019153350A1 (zh) 2018-02-12 2018-02-12 一种通信方法、通信设备及计算机程序存储介质

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/990,672 Continuation US12028879B2 (en) 2018-02-12 2020-08-11 Communication method, communications device, and computer program storage medium

Publications (1)

Publication Number Publication Date
WO2019153350A1 true WO2019153350A1 (zh) 2019-08-15

Family

ID=67548703

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/076527 WO2019153350A1 (zh) 2018-02-12 2018-02-12 一种通信方法、通信设备及计算机程序存储介质

Country Status (5)

Country Link
US (1) US12028879B2 (zh)
EP (1) EP3745789A4 (zh)
JP (1) JP7073511B2 (zh)
CN (2) CN111771407B (zh)
WO (1) WO2019153350A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022057447A1 (en) * 2020-09-21 2022-03-24 Telefonaktiebolaget Lm Ericsson (Publ) Method, apparatus of scheduling resource for terminal device

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017123405A1 (en) * 2016-01-15 2017-07-20 Qualcomm Incorporated Raster design for narrowband operation for machine type communications
WO2017213795A1 (en) * 2016-06-06 2017-12-14 Qualcomm Incorporated Multicast and/or broadcast for enhanced machine type communications and/or narrowband internet-of-things

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6981207B1 (en) * 2000-01-11 2005-12-27 Ecora Software Corporation Automatic documentation of configurable systems by outputting explanatory information of configuration parameters in a narrative format and configuration parameters differences
EP1305909A2 (en) * 2000-03-20 2003-05-02 Pingtel Corporation Method and system for combining configuration parameters for an entity profile
US7493532B2 (en) * 2005-10-14 2009-02-17 Lsi Corporation Methods and structure for optimizing SAS domain link quality and performance
JP5158958B2 (ja) * 2008-07-31 2013-03-06 パナソニック株式会社 Ｏｆｄｍシンボル検出方法、ｏｆｄｍ受信装置、集積回路および回路モジュール
US20100130218A1 (en) * 2008-11-21 2010-05-27 Interdigital Patent Holdings, Inc. Method and apparatus for supporting aggregation of multiple component carriers
AU2012214168B2 (en) * 2011-02-11 2015-09-24 Interdigital Patent Holdings, Inc. Multi-carrier HSDPA control metho and apparatus
CN102843723B (zh) * 2011-06-23 2017-09-12 中兴通讯股份有限公司 一种联合传输的方法、系统及锚点网元
CN103378897B (zh) * 2012-04-23 2017-12-22 中兴通讯股份有限公司 实现cmmb分集接收的方法及装置
US10149125B1 (en) * 2015-04-10 2018-12-04 Sprint Spectrum L.P. Dynamic adjustment of uplink coordinated multipoint service
WO2017133702A1 (zh) * 2016-02-05 2017-08-10 中兴通讯股份有限公司 传输信息的方法及装置
US10912089B2 (en) * 2016-04-01 2021-02-02 Telefonaktiebolaget Lm Ericsson (Publ) Dynamically configuring NB-IoT carriers
EP3453207A1 (en) 2016-05-02 2019-03-13 Intel IP Corporation Methods for multi-carrier operation with multiple anchor carriers in narrow-band internet-of-things
CN113207177B (zh) * 2016-05-12 2022-12-13 Oppo广东移动通信有限公司 传输系统信息的方法、基站和终端
US11582792B2 (en) * 2016-08-12 2023-02-14 Telefonaktiebolaget Lm Ericsson (Publ) DCI formats for non-anchor operations
US11265726B2 (en) * 2016-11-18 2022-03-01 Telefonaktiebolaget Lm Ericsson (Publ) Flexible standalone spectrum for NB-IoT
CN109451791B (zh) * 2017-07-28 2021-08-31 北京小米移动软件有限公司 一种混合自动重传请求结果的反馈方法及装置
CN111557079B (zh) * 2018-01-03 2022-06-21 联想(北京)有限公司 非锚定载波频率偏移指示

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017123405A1 (en) * 2016-01-15 2017-07-20 Qualcomm Incorporated Raster design for narrowband operation for machine type communications
WO2017213795A1 (en) * 2016-06-06 2017-12-14 Qualcomm Incorporated Multicast and/or broadcast for enhanced machine type communications and/or narrowband internet-of-things

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Rel-14 dedicated carrier configuration R2-1700770", 17 February 2017 (2017-02-17), XP051211471 *
HUAWEI ET AL.: "On downlink TDD NB-IoT R1-1719477", 3GPP TSG RAN WG1 MEETING #91, pages 20171201, XP051369175 *
HUAWEI ET AL.: "Revised WID on Further NB-IoT enhancements RP-172063", 3GPP TSG RAN MEETING #77, pages 20170914, XP051669283 *
See also references of EP3745789A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022057447A1 (en) * 2020-09-21 2022-03-24 Telefonaktiebolaget Lm Ericsson (Publ) Method, apparatus of scheduling resource for terminal device

Also Published As

Publication number Publication date
CN111771407B (zh) 2023-11-17
US12028879B2 (en) 2024-07-02
EP3745789A1 (en) 2020-12-02
CN111771407A (zh) 2020-10-13
US20200374886A1 (en) 2020-11-26
CN117769025A (zh) 2024-03-26
JP2021513293A (ja) 2021-05-20
EP3745789A4 (en) 2021-01-27
JP7073511B2 (ja) 2022-05-23

Similar Documents

Publication Publication Date Title
WO2018192552A1 (zh) 重复传输的方法及装置
CN112867073B (zh) 一种传输策略的方法、pcf网元及计算机存储介质
WO2020200034A1 (zh) 一种网络接入的方法和装置
CN107820728A (zh) 随机接入的方法和装置
EP4271123A2 (en) Rrc connection method and terminal
JP7019793B2 (ja) 無線通信方法、ネットワーク機器及び端末装置
TW201642683A (zh) 在支援iops之無線通訊系統內執行自動公共陸地行動網路選擇之方法
US20200100207A1 (en) Paging method and paging appartus
WO2020019987A1 (zh) 一种物联网中传输eUICC数据的方法、装置
JP2020533829A (ja) ページング方法、端末装置及びネットワーク機器
WO2016045097A1 (zh) D2d信号跳频方法及基站
WO2020119615A1 (zh) 一种通信方法、装置及计算机可读存储介质
CN111587607B (zh) 终端装置、基站装置以及方法
US11438105B2 (en) Information transmission on a control channel
US12028879B2 (en) Communication method, communications device, and computer program storage medium
US20240022649A1 (en) Data processing method and data processing device
CN114731544B (zh) 一种基于网络切片的数据传输方法、装置和系统
CN113302965A (zh) 无线通信的方法和无线通信装置
WO2018027932A1 (zh) 发现邻小区的方法和终端设备
WO2020143615A1 (zh) 小区无线网络临时标识的配置方法及设备
WO2023030458A1 (zh) 小区重选方法和通信装置
US11765698B2 (en) Concurrent multi-band operation of a peer-to-peer link
WO2022147796A1 (zh) 无线通信方法和终端设备
WO2023013738A1 (ja) 装置及び方法
US20230354264A1 (en) Base station, user equipment, and network node

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: 18905486

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020542999

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018905486

Country of ref document: EP

Effective date: 20200828