WO2021174401A1 - 通信方法及设备 - Google Patents

通信方法及设备 Download PDF

Info

Publication number
WO2021174401A1
WO2021174401A1 PCT/CN2020/077500 CN2020077500W WO2021174401A1 WO 2021174401 A1 WO2021174401 A1 WO 2021174401A1 CN 2020077500 W CN2020077500 W CN 2020077500W WO 2021174401 A1 WO2021174401 A1 WO 2021174401A1
Authority
WO
WIPO (PCT)
Prior art keywords
network device
type
terminal device
indication information
handover
Prior art date
Application number
PCT/CN2020/077500
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 PCT/CN2020/077500 priority Critical patent/WO2021174401A1/zh
Priority to EP20922584.6A priority patent/EP4109969A4/en
Priority to CN202080097717.6A priority patent/CN115211173A/zh
Priority to PCT/CN2020/130932 priority patent/WO2021174913A1/zh
Publication of WO2021174401A1 publication Critical patent/WO2021174401A1/zh
Priority to US17/901,413 priority patent/US20220417811A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/06—Reselecting a communication resource in the serving access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0016—Hand-off preparation specially adapted for end-to-end data sessions
    • 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/0037—Inter-user or inter-terminal allocation
    • H04L5/0041—Frequency-non-contiguous
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/00835—Determination of neighbour cell lists
    • H04W36/008355—Determination of target cell based on user equipment [UE] properties, e.g. UE service capabilities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/16—Performing reselection for specific purposes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/12—Access restriction or access information delivery, e.g. discovery data delivery using downlink control channel

Definitions

  • This application relates to the field of communication technology, and in particular to a communication method and device.
  • “Support of reduced capability NR devices” is one of the new research areas proposed by the 3rd generation partnership project (3GPP) in Release 17.
  • "Support for NR equipment with reduced performance” is a function that supports narrow bandwidth and lower peak data rate scenarios. It mainly provides lightweight communication for high-end machine type communication (MTC) equipment. lightweight communications).
  • a terminal device with weaker capabilities applicable to this scenario may be referred to as a reduced-capability UE (reduced-capability UE) or a low-capability UE.
  • the bandwidth supported by the reduced performance UE is generally below 20MHz
  • the peak data rate supported is generally 5-10Mb/s
  • the requirements for performance such as delay and reliability are reduced.
  • Such equipment mainly includes: wearable devices, surveillance cameras, industrial sensors, etc.
  • the UE reports the uplink and downlink bandwidth it supports through a bitmap containing 10 bits.
  • the 10 bits correspond to whether the UE supports a bandwidth of 5MHz, 10MHz, 15MHz, 20MHz, 25MHz, 30MHz, 40MHz, 50MHz, 60MHz, 80MHz.
  • all UEs need to support 100MHz bandwidth. Therefore, although there is no bit indicating whether the UE supports 100MHz bandwidth in the bitmap reported by the UE, legacy network devices all default to the UE supporting 100MHz bandwidth. In other words, the legacy network device considers that the bandwidth supported by the UE is the bandwidth reported by the UE in the bitmap and 100MHz.
  • UEs with reduced performance cannot support 100MHz and only support the bandwidth reported in the bitmap. Therefore, if the reduced-performance UE works in a network device under the current protocol, that is, a cell of a legacy network device, the network device will misjudge the ability of the reduced-performance UE, such as assigning a BWP that is not within its supported bandwidth, which may lead to degradation. Performance UE cannot work normally.
  • the embodiments of the present application provide a communication method and device, which can prevent a degraded UE from staying in a legacy network device, or avoid a degraded UE from switching to a legacy network device.
  • an embodiment of the present application provides a communication method.
  • the method includes: the first network device determines that the type of the first terminal device is the first type, and the first network device sends a handover request message, where the handover request message includes the first type.
  • An indication information where the first indication information includes the identification information of the first type; the first network device receives a handover confirmation message or a handover preparation failure message.
  • the first network device includes the first indication information in the handover request message, and the first indication information includes the first type of identification information.
  • the second network device sends a handover preparation failure message to the first network device when the second network device does not support the terminal device of the first type.
  • the second network device supports the terminal device of the first type, proceed according to the existing handover procedure, and send a handover confirmation message to the first network device when it is finally determined that the handover is approved.
  • this application involves multiple types of terminal devices, and the first type is one of the multiple types.
  • the multiple types of terminal devices may be divided according to the capabilities of the terminal devices.
  • the multiple types of terminal devices may include a first type and a second type.
  • the capability of the terminal device of the first type is lower than the capability of the terminal device of the second type.
  • the terminal device of the first type may be a reduced-performance UE
  • the terminal device of the second type may be a terminal device with a higher capability than that of the reduced-performance UE.
  • the terminal device of the second type may be a legacy UE.
  • the identification information of the first type refers to any information that can be used to identify the first type.
  • the identification information of the first type may be a name of the first type.
  • different types may correspond to different indexes. In this way, the identification information of the first type may be an index corresponding to the first type.
  • the first indication information further includes key value indication information, and the key value indication information is used to instruct the second network device to reject the handover under the first condition.
  • the first condition may be that the second network device does not support the first type of terminal device.
  • the "not supported” here can include two situations. The first situation is that the second network device can identify the first type of identification information, but the second network device does not support the first type of terminal device. The second situation is that the second network device cannot recognize the identification information of the first type.
  • the handover request message includes a new IE or field.
  • the name of the new IE or field is reduced capability UE.
  • This IE or field is used as the first indication information.
  • the IE or field includes identification information of the first type and key value indication information.
  • the name of the IE or the field is the first type of identification information
  • the key value of the IE or the field can take the value "reject" or "ignore", that is, the key value indication information, indicating that the second network device cannot recognize the IE Or whether the field or the identification information carried by the IE or the field cannot be identified or rejected or ignored.
  • the key value of the IE or field is set to "reject".
  • the second network device rejects the handover behavior and sends a handover failure message to the first network device. If the second network device can identify the IE or field, the second network device can continue to perform according to the existing handover procedure, and when it is finally determined that the handover is approved, it sends a handover confirmation message to the first network device. Therefore, it is possible to effectively prevent the first network device from switching the performance-degraded UE to the legacy network device.
  • the first network device may also provide services for the second terminal device, and the second terminal device is a second type of terminal device (for example, legacy UE).
  • the first network device can also support the second type of terminal device.
  • the first network device receiving the handover confirmation message or the handover preparation failure message includes: the first network device receives the handover confirmation message from the second network device, and the second network device supports the first network device. Type of terminal device; or, the first network device receives a first handover preparation failure message from a second network device, where the first handover preparation failure message includes failure information corresponding to the first type, and the second network device The first type of terminal device is not supported.
  • the failure cause (failure cause value) carried in the first handover preparation failure message indicates that the handover failed due to not supporting the first type.
  • the first network device sending the handover request message includes: the first network device sends the handover request message to the second network device; or, the first network device uses the access and mobility management function AMF The device sends the handover request message to the second network device.
  • the first network device when an Xn interface connection is established between the first network device and the second network device, the first network device sends the handover request message to the second network device.
  • the first network device and the second network device perform the switching process through the NG interface, that is, the first network device sends the switch to the second network device through the AMF device Request message.
  • the first network device sends a handover request message to the AMF, and the handover request message includes the first indication information (for example, the aforementioned new IE or field).
  • the first indication information may be added to the fifth indication information that can be transparently transmitted to the AMF, and the fifth indication information may be, for example, Handover Required Transfer IE. Since the fifth indication information is a transparent IE for the AMF, the AMF does not interpret the fifth indication information, but directly includes it in the handover request message and sends it to the second network device. The second network device interprets all the content included in the fifth instruction information.
  • the second network device can recognize the first indication information (for example, it can recognize the new IE/field, or the identification information carried by the new IE/field), proceed according to the existing protocol, and finally agree to switch At this time, a handover confirmation message is sent to the AMF, and the AMF sends a handover command message to the first network device. If the second network device cannot recognize the first indication information (for example, cannot recognize the above new IE/field, or cannot recognize the identification information carried by the new IE/field), the second network device rejects the switching behavior and sends the switching to AMF In the failure message, the AMF sends a handover preparation failure message to the first network device.
  • the first indication information for example, it can recognize the new IE/field, or the identification information carried by the new IE/field
  • an embodiment of the present application provides a communication method, the method includes: a second network device receives a handover request message, the handover request message includes first indication information, and the first indication information includes a first type of identifier Information, the first type is the first type of the terminal device; or the first type is the type of the first terminal device; the second network device sends a handover confirmation message or a handover preparation failure message.
  • the first indication information includes the first type of identification information.
  • the second network device sends a handover preparation failure message to the first network device when the second network device does not support the terminal device of the first type.
  • the second network device supports the terminal device of the first type, proceed according to the existing handover procedure, and send a handover confirmation message to the first network device when it is finally determined that the handover is approved.
  • the handover request message further includes capability information of the first terminal device, and the type of the first terminal device is the first type.
  • the capability information may include one or more of the following: maximum transmission bandwidth, transmission rate, reliability, delay tolerance, number of antennas, or battery life, etc.
  • the first indication information further includes key value indication information, and the key value indication information is used to instruct the second network device to reject the handover under the first condition.
  • the second network device receiving the handover request message includes: the second network device receives the handover request message sent by the first network device; or, the second network device uses the access and mobility management function AMF device Receive a handover request message from the first network device.
  • an embodiment of the present application provides a communication method, including: a network device generates a system message, the system message includes second indication information, the second indication information is used to indicate a first type, and the first type It is the first type of terminal equipment; the network equipment sends the system message.
  • the first terminal device is in an idle state, for example, the first terminal device may be in the process of cell selection or cell reselection.
  • the second indication information is used to indicate the first type.
  • the terminal device of the first type may be a performance-reduced UE.
  • the second indication information indicates that the network device supports the first type of terminal device, or the second indication information indicates whether the network device supports the first type of terminal device.
  • the system message is a system message block SIB1.
  • the terminal device determines that the network device supports the reduced-performance UE, and there is a new IE or field in the SIB1. It can also be said that the terminal device determines that the network device supports the UE with reduced performance according to the presence of the above-mentioned IE or field in the SIB1. Otherwise, it is determined that the network device does not support the reduced performance UE.
  • the attributes of the new IE or field may be an enumeration type, for example, ⁇ ture/false ⁇ may be enumerated, ⁇ supported/notSupported ⁇ may be enumerated, or enumeration may not be used.
  • the terminal device determines that the network device supports the UE with reduced performance, the aforementioned IE or field exists in the SIB1, and the indication information in the aforementioned IE or field is preset information (for example, true or supported). It can also be said that the terminal device determines that the network device supports the UE with reduced performance based on the presence of the above IE or field in the SIB1 and the indication information in the above IE or field being preset information. Otherwise, it is determined that the network device does not support the reduced performance UE.
  • the terminal device determines that the network device supports a reduced-performance UE, the foregoing IE or field exists in the SIB1, and the foregoing IE or field indicates that the type of terminal device supported by the network device includes the first type. It can also be said that the terminal device determines that the network device supports the degraded UE based on the presence of the above IE or field in the SIB1, and the above IE or field indicating that the type of terminal device supported by the network device includes the first type. Otherwise, it is determined that the network device does not support the reduced performance UE.
  • an embodiment of the present application provides a communication method.
  • the method includes: a terminal device receives a system message from a network device; the terminal device acquires second indication information contained in the system message, and the second indication information is used for Indicates the first type, and the first type is the first type of the terminal device.
  • the system message is a system message block SIB1.
  • the method further includes: determining whether to camp in the cell of the network device according to the second indication information.
  • the terminal device determines the cell where the network device resides, and the above-mentioned IE or field exists in the SIB1. It can also be said that the terminal device determines the cell where the network device resides according to the presence of the above-mentioned IE or field in the SIB1. Otherwise, it is determined not to camp on the cell of the network device.
  • the terminal device determines the cell where the network device resides, the above IE or field exists in the SIB1, and the indication information in the above IE or field is preset information (for example, true or supported). It can also be said that the terminal device determines the cell where the network device resides according to the presence of the above IE or field in the SIB1 and the indication information in the above IE or field is preset information. Otherwise, it is determined not to camp on the cell of the network device.
  • the terminal device determines the cell where the network device resides, the above IE or field exists in the SIB1, and the above IE or field indicates that the type of terminal device supported by the network device includes the first type. It can also be said that the terminal device determines the cell where the network device resides according to the presence of the above IE or field in the SIB1, and the above IE or field indicates that the type of terminal device supported by the network device includes the first type. Otherwise, it is determined not to camp on the cell of the network device.
  • the system message further includes: frequency band information and bandwidth information supported by the network device; and determining whether to reside in the cell of the network device according to the second indication information includes: The second indication information and the frequency band information and bandwidth information supported by the network device determine whether to reside in the cell of the network device.
  • the second indication information is used to indicate the first type.
  • the terminal device can learn whether the network device supports the network device according to the second indication information in the system message.
  • the terminal device of the first type further determines whether to reside in the cell of the network device. For a reduced-performance UE, if it is determined according to the received system message that the network device does not support the reduced-performance UE, it does not reside in the cell of the network device; only when it is determined that the network device supports the reduced-performance UE, the network device As the candidate for cell selection, the cell can avoid degrading performance UE staying in legacy network equipment.
  • the network device is a network device corresponding to a neighboring cell of the serving cell of the first terminal device; the method further includes: the first terminal device sends the second indication information to the serving cell Corresponding network equipment. Or, the first terminal device sends the determination result corresponding to the second indication information to the second network device.
  • the determination result is a result obtained by the first terminal device judging whether the first network device supports the terminal device of the first type according to the second indication information.
  • the first terminal device carries the second indication information or the determination result corresponding to the second indication information in a CGI procedure report (procedure report) and measurement report (measurement report) and sends it.
  • CGI procedure report procedure report
  • measurement report measurement report
  • the first terminal device sends the detected PCI of the first cell to the second network device. If the second network device finds that the PCI of the first cell reported by the first terminal device is not recognizable, it instructs the first terminal device to obtain neighbor cell information corresponding to the PCI.
  • the first terminal device receives the SIB1 of the first cell, and generates a CGI procedure report according to the neighbor cell information parsed from the SIB1.
  • the first terminal device sends the CGI procedure report to the second network device.
  • the CGI procedure report includes one or more of the PLMN list, RANAC, TAC, cell ID, frequency band list, and second indication information.
  • the second network device when the second network device initiates a handover, it will use the information obtained from the CGI procedure report, including information about whether other network devices support or support UEs with reduced performance, as a judgment condition to select the target network device. Therefore, it is possible to avoid switching the performance-degraded UE to legacy network equipment.
  • an embodiment of the present application provides a communication method, the method includes: a first terminal device generates capability information, the capability information includes third indication information, and the third indication information is used to indicate Type, the type of the first terminal device is the first type or the second type; the first terminal device sends the capability information to the network device.
  • the method before the first terminal device generates the capability information, the method further includes: the first terminal device receives the capability request message from the network device.
  • the first terminal device includes the third indication information in the capability information to indicate the type of the first terminal device, so that the network device can determine the type of the first terminal device according to the received capability information. Therefore, the network device can adopt different processing methods according to the type of the first terminal device. For example, if the type of the first terminal device is the first type (reduced performance UE), the bandwidth supported by the first terminal device is considered to be the bandwidth reported through bitmap or other forms. When the first terminal device needs to switch, the first terminal device needs to be switched. A terminal device switches to a network device that supports UEs with reduced performance. If the type of the first terminal device is the second type (for example, legacy UE), the bandwidth of the first terminal device is considered to be the bandwidth and 100 MHz reported by bitmap or other forms.
  • the type of the first terminal device is the second type (for example, legacy UE)
  • the bandwidth of the first terminal device is considered to be the bandwidth and 100 MHz reported by bitmap or other forms.
  • an embodiment of the present application provides a communication method.
  • the method includes: a network device receives capability information from a first terminal device, where the capability information includes third indication information; and the network device determines according to the third indication information
  • the type of the first terminal device is the first type or the second type.
  • the method before the network device receives the capability information from the first terminal device, the method further includes: sending a capability request message to the first terminal device.
  • the first terminal device includes the third indication information in the capability information to indicate the type of the first terminal device, so that the network device can determine the type of the first terminal device according to the received capability information. Therefore, the network device can adopt different processing methods according to the type of the first terminal device. For example, if the type of the first terminal device is the first type (reduced performance UE), the bandwidth supported by the first terminal device is considered to be the bandwidth reported through bitmap or other forms. When the first terminal device needs to switch, the first terminal device needs to be switched. A terminal device switches to a network device that supports UEs with reduced performance. If the type of the first terminal device is the second type (for example, legacy UE), the bandwidth of the first terminal device is considered to be the bandwidth and 100 MHz reported by bitmap or other forms.
  • the type of the first terminal device is the second type (for example, legacy UE)
  • the bandwidth of the first terminal device is considered to be the bandwidth and 100 MHz reported by bitmap or other forms.
  • an embodiment of the present application provides a communication method, the method includes: a first network device sends an Xn interface establishment request message to a second network device, the Xn interface establishment request message includes inquiry information, and the inquiry information Used to inquire whether the second network device supports the first type of terminal device; the first network device receives an Xn interface establishment response message or an Xn interface establishment failure message from the second network device; wherein, the Xn interface establishment response message includes Fourth indication information, where the fourth indication information is used to indicate whether the second network device supports terminal devices of the first type.
  • an embodiment of the present application provides a communication method, the method includes: a second network device receives an Xn interface establishment request message from a first network device, the Xn interface establishment request message includes inquiry information, and the inquiry information Used to inquire whether the second network device supports the first type of terminal device; the second network device sends an Xn interface establishment response message or an Xn interface establishment failure message to the first network device; wherein the Xn interface establishment response message includes Fourth indication information, where the fourth indication information is used to indicate whether the second network device supports terminal devices of the first type.
  • the first network device can learn whether the second network device supports the first type of terminal device according to the fourth indication information.
  • the first network device may also store the fourth indication information.
  • the first network device needs to initiate a switch to the terminal device of the first type, it can determine which target network device to switch the terminal device of the first type to according to the stored fourth indication information of each network device. Therefore, it is avoided that the terminal device of the first type is switched to the network device that does not support the first type.
  • an embodiment of the present application provides a communication device.
  • the communication device may be a first network device or an element in the first network device, such as a chip or an integrated circuit.
  • the communication device may include: a processing unit, a sending unit, and a receiving unit.
  • the processing unit is used to determine that the type of the first terminal device is the first type;
  • the sending unit is used to send a handover request message, where the handover request message includes first indication information, and the first indication information includes the first type
  • the receiving unit is used to receive the handover confirmation message or the handover preparation failure message.
  • the first indication information further includes key value indication information, and the key value indication information is used to instruct the second network device to reject the handover under the first condition.
  • the receiving unit is specifically configured to: receive a handover confirmation message from a second network device, which supports the terminal device of the first type; or, receive a handover confirmation message from a second network device.
  • a first handover preparation failure message of the device where the first handover preparation failure message includes failure information corresponding to the first type, and the second network device does not support the first type of terminal device.
  • the sending unit is specifically configured to: send the handover request message to the second network device; or, send the handover request message to the second network device through the access and mobility management function AMF device information.
  • an embodiment of the present application provides a communication device, which can be used as a second network device.
  • the communication device may include: a receiving unit and a sending unit.
  • the receiving unit is configured to receive a handover request message, the handover request message includes first indication information, the first indication information includes identification information of a first type, and the first type is the first type of the terminal device; or The first type is the type of the first terminal device; the sending unit is used to send a handover confirmation message or a handover preparation failure message.
  • the handover request message further includes capability information of the first terminal device, and the type of the first terminal device is the first type.
  • the first indication information further includes key value indication information, and the key value indication information is used to instruct the second network device to reject the handover under the first condition.
  • the receiving unit is specifically configured to: receive the handover request message sent by the first network device; or, receive the handover request message from the first network device through the access and mobility management function AMF device.
  • an embodiment of the present application provides a communication device.
  • the communication device may include a processing unit and a sending unit.
  • the processing unit is used to generate a system message, the system message includes second indication information, the second indication information is used to indicate a first type, and the first type is the first type of the terminal device; the sending unit is used to Send the system message.
  • the system message is a system message block SIB1.
  • an embodiment of the present application provides a communication device.
  • the communication device may be a first terminal device or an element in the first terminal device, such as a chip or an integrated circuit.
  • the communication device may include: a receiving unit and a processing unit.
  • the receiving unit is used to receive a system message from a network device; the processing unit is used to obtain second indication information contained in the system message, the second indication information is used to indicate a first type, and the first type is a terminal The first type of equipment.
  • the system message is a system message block SIB1.
  • the processing unit is further configured to determine whether to camp in the cell of the network device according to the second indication information.
  • system message further includes: frequency band information and bandwidth information supported by the network device; the processing unit is specifically configured to: according to the second indication information and the frequency band supported by the network device Information and bandwidth information to determine whether to camp in the cell of the network device.
  • the network device is a network device corresponding to a neighboring cell of the serving cell of the first terminal device; the communication device further includes a sending unit, and the sending unit is configured to: send the second indication information To the network device corresponding to the serving cell.
  • an embodiment of the present application provides a communication device.
  • the communication device may be a first terminal device or an element in the first terminal device, such as a chip or an integrated circuit.
  • the communication device may include: a processing unit and a sending unit.
  • the processing unit is configured to generate capability information, the capability information includes third indication information, the third indication information is used to indicate the type of the first terminal device, and the type of the first terminal device is the first type or the first type. Type two; the sending unit is used to send the capability information to the network device.
  • the communication device further includes a receiving unit, and the receiving unit is configured to receive a capability request message from the network device.
  • an embodiment of the present application provides a communication device.
  • the communication device may include: a receiving unit and a processing unit.
  • the receiving unit is configured to receive capability information from the first terminal device, the capability information includes third indication information;
  • the processing unit is configured to determine that the type of the first terminal device is the first type according to the third indication information Or the second type.
  • the communication device further includes a sending unit, and the sending unit is configured to send a capability request message to the first terminal device.
  • an embodiment of the present application provides a communication device.
  • the communication device may be a first network device or an element in the first network device, such as a chip or an integrated circuit.
  • the communication device may include a sending unit and a receiving unit.
  • the sending unit is configured to send an Xn interface establishment request message to the second network device, the Xn interface establishment request message includes query information, and the query information is used to query whether the second network device supports the first type of terminal
  • the receiving unit is configured to receive an Xn interface establishment response message or an Xn interface establishment failure message from the second network device; wherein the Xn interface establishment response message includes fourth indication information, and the fourth indication information is used to indicate the Whether the second network device supports the terminal device of the first type.
  • an embodiment of the present application provides a communication device.
  • the communication device may be a second network device or an element in the second network device, such as a chip or an integrated circuit.
  • the communication device may include a receiving unit and a transmitting unit.
  • the receiving unit is configured to receive an Xn interface establishment request message from the first network device, the Xn interface establishment request message includes query information, and the query information is used to query whether the second network device supports the first type of terminal
  • the sending unit is configured to send an Xn interface establishment response message or an Xn interface establishment failure message to the first network device; wherein the Xn interface establishment response message includes fourth indication information, and the fourth indication information is used to indicate the Whether the second network device supports the terminal device of the first type.
  • an embodiment of the present application provides a communication device, including at least one memory and at least one processor, the at least one memory is used to store a computer program, and the at least one processor is used to download from the at least one memory Invoke and run the computer program, so that the at least one processor runs the computer program to execute the computer program as described in any one of the first aspect, the second aspect, the third aspect, the sixth aspect, the seventh aspect, and the eighth aspect.
  • an embodiment of the present application provides a communication device, including at least one memory and at least one processor, the at least one memory is used for storing a computer program, and the at least one processor is used for downloading from the at least one memory Invoking and running the computer program, so that the at least one processor runs the computer program to execute the communication method according to any one of the fourth aspect and the fifth aspect.
  • an embodiment of the present application provides a computer storage medium, the computer storage medium includes a computer program, and the computer program is used to implement aspects such as the first, second, third, sixth, and sixth aspects.
  • the communication method according to any one of the seventh aspect and the eighth aspect, or the communication method according to any one of the fourth aspect and the fifth aspect is implemented.
  • an embodiment of the present application provides a chip or chip system.
  • the chip or chip system includes at least one processor and a communication interface.
  • the communication interface and the at least one processor are interconnected through a wire, and the at least one processor is used to run a computer program.
  • instructions to perform the communication method according to any one of the first, second, third, sixth, seventh, and eighth aspects, or as in the fourth and fifth aspects Any of the communication methods.
  • the communication interface in the chip can be an input/output interface, a pin, or a circuit.
  • the chip or chip system described above in this application further includes at least one memory, and instructions are stored in the at least one memory.
  • the memory may be a storage unit inside the chip, for example, a register, a cache, etc., or a storage unit of the chip (for example, a read-only memory, a random access memory, etc.).
  • an embodiment of the present application provides a communication system, which includes the communication device according to any one of the ninth aspect and the communication device according to any one of the tenth aspect;
  • the communication system includes the communication device according to any one of the eleventh aspect and the communication device according to any one of the twelfth aspect;
  • the communication system includes the communication device according to any one of the thirteenth aspect and the communication device according to any one of the fourteenth aspect;
  • the communication system includes the communication device according to any one of the fifteenth aspect and the communication device according to any one of the sixteenth aspect.
  • FIG. 1A is a schematic diagram of a network architecture that may be involved in an embodiment of this application;
  • FIG. 1B is a schematic diagram of another network architecture that may be involved in an embodiment of this application.
  • FIG. 2 is a schematic diagram of the bandwidth supported by the UE and legacy network equipment with reduced performance in an embodiment of the application;
  • FIG. 3 is a schematic flowchart of a communication method provided by an embodiment of this application.
  • FIG. 4 is a schematic flowchart of a communication method provided by an embodiment of this application.
  • FIG. 5 is a schematic flowchart of a communication method provided by an embodiment of this application.
  • FIG. 6 is a schematic flowchart of a communication method provided by an embodiment of this application.
  • FIG. 7 is a schematic diagram of the interaction process of an ANR scenario provided by an embodiment of this application.
  • FIG. 8 is a schematic flowchart of a communication method provided by an embodiment of this application.
  • FIG. 9 is a schematic flowchart of a communication method provided by an embodiment of this application.
  • FIG. 10 is a schematic structural diagram of a network device provided by an embodiment of this application.
  • FIG. 11 is a schematic structural diagram of a terminal device provided by an embodiment of this application.
  • FIG. 12 is a schematic structural diagram of a network device provided by an embodiment of this application.
  • FIG. 13 is a schematic structural diagram of a terminal device provided by an embodiment of this application.
  • the communication system may be, for example, a global system of mobile communication (GSM) system, code division multiple access (CDMA) system, and wideband code division multiple access (wideband code division multiple access).
  • GSM global system of mobile communication
  • CDMA code division multiple access
  • WCDMA wideband code division multiple access
  • GPRS general packet radio service
  • LTE long term evolution
  • LTE-A LTE advanced
  • LTE frequency division duplex frequency division duplex
  • FDD LTE time division duplex
  • UMTS universal mobile telecommunication system
  • 5G fifth generation mobile networks
  • 5G new Air interface
  • 6G 6th generation mobile networks
  • the following describes the network architecture that may be involved in the embodiments of the present application in conjunction with FIG. 1A and FIG. 1B. It should be noted that the network architecture and business scenarios described in the embodiments of the present application are intended to illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. A person of ordinary skill in the art knows that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are equally applicable to similar technical problems.
  • FIG. 1A is a schematic diagram of a network architecture that may be involved in an embodiment of this application.
  • the network architecture includes: network equipment and terminal equipment.
  • the terminal device can reside in the cell of the network device through the cell selection process.
  • FIG. 1B is a schematic diagram of another network architecture that may be involved in an embodiment of this application.
  • the network architecture includes: access and mobility management function (AMF), first network equipment, second network equipment, and terminal equipment.
  • the first network device and the second network device communicate through an Xn interface (Xn interface), and the AMF communicates with the network device through an NG interface (NG interface).
  • Xn interface Xn interface
  • NG interface NG interface
  • the communication system may connect the terminal device to the original cell (the first cell).
  • the communication link of a cell of a network device is transferred to a new cell (a cell of a second network device).
  • Switching can be divided into switching based on Xn interface and switching based on NG interface. In other words, switching can be performed directly between two network devices. When the Xn interface cannot be established, the two network devices can also exchange handover signaling through AMF.
  • the network device in the embodiment of the present application may be a device that connects a terminal device to a wireless network.
  • the device may be a base station, or various wireless access points, or may refer to a device that communicates with a terminal device through one or more sectors on an air interface in an access network.
  • the base station can be used to convert received air frames and IP packets into each other, and act as a router between the terminal device and the rest of the access network, where the rest of the access network can include an Internet Protocol (IP) network.
  • IP Internet Protocol
  • the base station can also coordinate the attribute management of the air interface.
  • the base station can be a base station (BTS) in global system of mobile communication (GSM) or code division multiple access (CDMA), or it can be a broadband code division multiple access (BTS).
  • GSM global system of mobile communication
  • CDMA code division multiple access
  • BTS broadband code division multiple access
  • the base station (nodeB, NB) in wideband code division multiple access (WCDMA) can also be an evolved base station (evolutional node B, eNB or eNodeB) in long term evolution (LTE), or a relay station or access point It can also be the base station gNB in the 5G network, the transmission reception point (TRP) in the NR network, or the generation node B (gNB), or the base station in other network systems in the future, etc., here Not limited.
  • the terminal device in the embodiments of the present application may be a wireless terminal or a wired terminal.
  • the wireless terminal may be a device that provides voice and/or other service data connectivity to the user, a handheld device with wireless connection function, or a wireless terminal connected to a wireless terminal. Other processing equipment for the modem.
  • a wireless terminal can communicate with one or more core networks via a wireless access network.
  • the wireless terminal can be a mobile terminal, such as a mobile phone (or called a "cellular" phone) and a computer with a mobile terminal. For example, it can be a portable, Pocket, handheld, computer built-in or vehicle-mounted mobile devices that exchange language and/or data with the wireless access network.
  • Wireless terminal can also be called system, subscriber unit (subscriber unit), subscriber station (subscriber station), mobile station (mobile station), mobile station (mobile), remote station (remote station), remote terminal (remote terminal), connection Access terminal (access terminal), user terminal (user terminal), user agent (user agent), user equipment (user device or user equipment), and sensors with network access functions are not limited here.
  • the new research area "Support for NR equipment with reduced performance" proposed by 3GPP in Release 17, is a function that supports scenarios with narrower bandwidth and lower peak data rates, mainly for high-end machine-type communications ( Machine type communication (MTC) equipment provides lightweight communications.
  • MTC Machine type communication
  • a terminal device with weaker capabilities applicable to this scenario may be referred to as a reduced-capability UE (reduced-capability UE) or a low-capability UE.
  • Such equipment mainly includes: wearable devices, surveillance cameras, industrial sensors, etc.
  • a terminal device with a strong capability is referred to as a traditional UE, which may also be referred to as a normal/legacy UE.
  • reduced performance UE is a type of low-cost, low-complexity and more energy-efficient terminal equipment.
  • the capabilities of the terminal equipment include one or more of the following: maximum transmission bandwidth, transmission rate, reliability, delay tolerance, number of antennas, or battery life, etc.
  • the capabilities of different types of terminal devices are different.
  • the performance-reduced UE has one or more of the following features:
  • reduced performance UE supports a narrower bandwidth, and the narrower bandwidth is a bandwidth lower than a predetermined threshold.
  • the threshold is 100 MHz.
  • One type supports a maximum bandwidth of 20MHz, and the other type supports a maximum bandwidth of 5MHz. It should be noted that the foregoing classification of performance-reduced UEs is only an exemplary description, and is not limited.
  • reduced performance UEs support reduced peak data rates, for example, generally 5-10 Mb/s.
  • the bandwidth supported by the UE with reduced performance is reduced.
  • the reduced performance UE supports 5MHz RF bandwidth, which is smaller than the bandwidth of the legacy UE in Release 15.
  • Legacy UE in Release 15 supports 100MHz bandwidth.
  • the terminal device reports the uplink and downlink bandwidth supported by itself to the network device through a bitmap containing 10 bits.
  • the 10 bits respectively correspond to whether the terminal device supports 5MHz, 10MHz, 15MHz, 20MHz, 25MHz, 30MHz, 40MHz, 50MHz, 60MHz, 80MHz bandwidth.
  • all terminal devices need to support 100MHz bandwidth. Therefore, although there is no bit indicating whether or not to support 100MHz bandwidth in the bitmap reported by the terminal device, the network device will default to the terminal device supporting the 100MHz bandwidth. In other words, the network device considers that the bandwidth supported by the terminal device is the bandwidth reported by the terminal device in the bitmap and 100MHz.
  • UEs with reduced performance cannot support 100MHz and only support the bandwidth reported in the bitmap. Therefore, if the degraded UE works on a network device that does not currently support NR Light, the network equipment will overestimate the capability of the degraded UE because such a UE supports a 100MHz bandwidth by default.
  • the network equipment may allow the UE to work with this network and allocate resources to it due to the default reduced capability UE supporting 100MHz, which may cause the reduced performance UE to fail to work normally on the allocated resources. Therefore, for UEs with reduced performance, network equipment needs to be improved so that the network equipment can support UEs with reduced performance.
  • network devices that do not support NR Light are referred to as “legacy/normal network devices", or “network devices that do not support UEs with reduced performance”.
  • the legacy network equipment will default to the bandwidth supported by all terminal equipment as the bandwidth reported by the terminal equipment in the bitmap and 100MHz.
  • a network device that supports a reduced-performance UE is referred to as a “network device that supports a reduced-performance UE”. It can be understood that a network device that supports a reduced-performance UE can identify the reduced-performance UE through the capability information reported by the terminal device and grasp the true capability of the terminal device.
  • network devices that support reduced-performance UEs consider their bandwidth as the reported bandwidth for reduced-performance UEs.
  • the method of reporting bandwidth can include reporting through the original bitmap or reporting through other forms; networks that support reduced-performance UEs For legacy UE, the device considers its bandwidth to be the bandwidth reported in the bitmap and 100MHz; or, for legacy UE, the network device that supports reduced performance UE considers its bandwidth to be the bandwidth reported by bitmap or other forms and 100M .
  • FIG. 2 is a schematic diagram of the bandwidth supported by the UE and legacy network equipment with reduced performance in an embodiment of the application.
  • the legacy network equipment defaults to a reduced-performance UE supporting a bandwidth of 100 MHz, and it is possible to allocate uplink and downlink resources that the reduced-performance UE may not be able to support for such terminal devices. If the degraded UE resides in the legacy network device or is switched to the legacy network device, the legacy network device degrades the performance by default.
  • the UE supports 100MHz, and it will be wrongly judged to degrade the capability of the performance UE.
  • legacy network equipment may allocate the bandwidth part (Band Width Part, BWP) that it cannot use to the degraded UE.
  • BWP Band Width Part
  • the BWP1, BWP2, and BWP3 shown in Figure 2 are allocated to the degraded UE, causing the degraded UE to fail to function normally. Work.
  • Cell selection scenario Based on the network architecture shown in Figure 1A, when a terminal device enters the coverage area of a network device from a power-on or blind area, it will look for a frequency allowed by the public land mobile network (PLMN) and select a suitable cell for camping. This process is called cell selection.
  • PLMN public land mobile network
  • the purpose of cell selection is to make the terminal equipment camp on the cell as soon as possible, so that the terminal equipment can receive system messages broadcast by the PLMN, initiate a random access process in the cell, receive paging on the network side, and receive cell broadcast services.
  • the cell selection process is as follows: After the terminal device is turned on, it first selects a suitable PLMN, and then selects the cell according to the determined PLMN.
  • the cell selection process includes four parts: cell search, system message reception, cell selection, and cell camping. Only after selecting a cell that satisfies the camping conditions on the PLMN can you register on the PLMN.
  • the terminal device obtains frequency and symbol synchronization (downlink synchronization) with the cell through cell search, obtains the starting position of the downlink frame, and determines the physical-layer cell identity (PCI) of the cell. After completing the cell search, the terminal device receives the system message of this cell.
  • PCI physical-layer cell identity
  • the terminal device obtains the public information of the network access layer and the non-access layer by reading the system message, so that the terminal device understands the configuration of the network before initiating a call, so as to initiate the call in an appropriate manner.
  • the terminal device can read part of the base station capability information from the system message, such as the bandwidth supported by the target base station, initial BWP, and so on. Based on the above information, the terminal equipment combines its own capabilities to determine whether its own capabilities can support camping on this base station. Next, the terminal device selects a cell that meets the S criterion to camp on based on the measurement result. Residing in the cell allows the terminal equipment to receive system information broadcast by the PLMN, initiate a random access procedure in the cell, receive paging from the network, and receive cell broadcast services.
  • the terminal device cannot know whether the network device supports the reduced performance UE. Therefore, when the reduced performance UE performs cell selection according to the above-mentioned existing process, it may choose to stay in the legacy network device. The UE cannot work normally due to reduced performance.
  • the communication system can The communication link between the terminal device and the original cell (the cell of the first network device) is transferred to the new cell (the cell of the second network device).
  • the above process is called handover.
  • the switching process is controlled by the network device.
  • the network device issues related configuration information to the terminal device.
  • the terminal device completes the switching measurement according to the configuration information and reports the measurement result to the network device based on the measurement report trigger condition.
  • the switching process is completed under the control of the network device. Ensure uninterrupted communication services.
  • the switching process based on the Xn interface is as follows: the source network device (for example, the first network device) makes a switching decision based on the measurement results reported by the terminal device and other factors.
  • the source network device selects the target network device (for example, the second network device), and sends a handover request message to the target network device.
  • the target network device judges whether to allow handover based on the obtained information; if the handover is allowed, it returns a handover confirmation message to the source network device; if the handover is not allowed, it returns a handover preparation failure message to the source network device.
  • the handover procedure based on the NG interface is similar to the handover procedure based on the Xn interface. The difference is that the handover signaling between the source network device and the target network device needs to be forwarded by the core network device AMF.
  • the source network device when the source network device sends a handover request message to the target network device, it is not sure whether the target network device supports the reduced performance UE, that is, it is not sure whether the target network device is a legacy network device or supports a reduced performance UE. Network equipment. Therefore, when the terminal device to be handed over is a degraded UE, according to the existing handover procedure, the source network device may switch the degraded UE to the legacy network device, thereby causing the degraded UE to fail to work normally.
  • the automatic neighboring cell relation (ANR) function was introduced in the Release 15 version of the 3GPP protocol.
  • the network device instructs the terminal device of the serving cell to detect a new target cell, and read the global and physical IDs of the target cell (ie, global and physical IDs, for example: NR CGI/NR PCI, ECGI /PCI).
  • the neighbor cell information read by the terminal device will be reported to the network device through the global cell identifier procedure report (CGI procedure report), and the network device will store the neighbor cell information in the neighbor relationship table of the serving cell. cell relation table, NCRT). Therefore, it is avoided that the network equipment may have pilot leakage in increasing the neighboring cell relationship, which may cause the false increase of neighboring cells and affect the quality and stability of the system.
  • the terminal device resides in the cell of the first network device, that is, the cell of the first network device is the serving cell of the terminal device.
  • the terminal device detects the cell of the second network device, it reports the global and physical IDs of the detected cell (ie, global and physical IDs, for example, NR CGI/NR PCI, ECGI/PCI) to the first network device.
  • the first network device can detect, create, delete, etc., the neighbor relationship according to the information reported by the terminal device.
  • the first network device may select the target network device based on these neighbor relationships.
  • the terminal device will report the CGI procedure report corresponding to the PCI, which includes CGI, PLMN ID, tracking area code (TAC), etc.
  • the CGI procedure report received by the first network device from the terminal device does not contain information about whether the cells of other network devices support UEs with reduced performance.
  • the first network device cannot know whether the second network device is a legacy network device or a network device that supports UEs with reduced performance based on the information in the CGI procedure report. Therefore, in the subsequent handover procedure, the first network device may switch the performance-reduced UE to the legacy network device, resulting in that the performance-reduced UE cannot work normally.
  • an embodiment of the present application provides a communication method, which can prevent a degraded UE from staying in a legacy network device, or avoid a degraded UE from switching to a legacy network device.
  • FIG. 3 is a schematic flowchart of a communication method provided by an embodiment of this application.
  • the communication method of this embodiment can be applied to a handover scenario based on the Xn interface. As shown in Figure 3, the method of this embodiment includes:
  • the first network device determines that the type of the first terminal device is the first type.
  • the first network device may also be referred to as the source network device, and the second network device may also be referred to as the target network device.
  • the first terminal device is the terminal device to be switched.
  • the first terminal device is in a connected state, and a certain cell of the first network device is the current serving cell of the first terminal device.
  • the first network device makes a handover decision based on the measurement report and other information reported by the first terminal device.
  • This application involves multiple types of terminal devices, and the first type is one of the multiple types. It should be understood that there may be multiple ways to classify the types of terminal devices.
  • the multiple types of terminal devices may be divided according to the capabilities of the terminal devices.
  • the capabilities of the terminal equipment include one or more of the following: maximum transmission bandwidth, transmission rate, reliability, delay tolerance, number of antennas, or battery life, etc.
  • the capabilities of different types of terminal devices are different.
  • the multiple types of terminal devices may include a first type and a second type.
  • the capability of the terminal device of the first type is lower than the capability of the terminal device of the second type.
  • the terminal device of the first type may be a reduced-performance UE
  • the terminal device of the second type may be a terminal device with a higher capability than that of the reduced-performance UE.
  • the terminal device of the second type may be a legacy UE. From the foregoing description, it can be seen that legacy UEs are more capable of maximum transmission bandwidth and transmission rate than degraded UEs.
  • the first network device sends a handover request message (HANDOVER REQUEST message) to the second network device, where the handover request message includes first indication information, and the first indication information includes the first type of identification information.
  • a handover request message HANDOVER REQUEST message
  • the second network device sends a handover confirmation message (HANDOVER REQUEST ACKNOWLEDGE message) or a handover preparation failure message (HANDOVER PREPARRATION FAILURE message) to the first network device.
  • a handover confirmation message HANDOVER REQUEST ACKNOWLEDGE message
  • a handover preparation failure message HANDOVER PREPARRATION FAILURE message
  • the first network device sends a handover request message (HANDOVER REQUEST message) to the second network device.
  • the handover request message includes the configuration information and progress information of the ongoing service of the terminal device to be handed over.
  • the handover request message includes one or more of the following information: the progress of the current quality of service flow (QoS flow), established protocol data unit (protocol data unit, PDU) sessions (sessions) and related configurations and associations
  • QoS flow the progress of the current quality of service flow
  • PDU protocol data unit
  • sessions sessions
  • DRB data radio bearer
  • UE Security Capabilities IE security capabilities of the terminal equipment
  • AS Security Information security information of the access layer
  • the handover request message may include capability information of the first terminal device.
  • the capability information may include one or more of the following: maximum transmission bandwidth, transmission rate, reliability, delay tolerance, number of antennas, or battery life, etc.
  • the handover request message may include the capability identifier or the capability set identifier of the first terminal device. The capability identifier or the identifier of the capability set is used to indicate the capability information of the terminal device. In this way, the second network device can prepare handover resources for the first terminal device or determine whether to agree to handover according to the capability information of the first terminal device.
  • the type of the first terminal device is the first type.
  • the identification information of the first type refers to any information that can be used to identify the first type.
  • the identification information of the first type may be a name of the first type.
  • the identification information of the first type may be a reduced capability UE.
  • different types may correspond to different indexes.
  • the identification information of the first type may be an index corresponding to the first type.
  • the handover request message may include the configuration and progress information of the ongoing service of the terminal device to be handed over, such as the progress of the current quality of service flow (QoS Flow), PDU sessions (PDU Sessions) and related configurations And one or more of the associated data radio bearers (DRBs); and/or, the handover request message may include related information fields of the terminal device, such as: UE Security Capabilities (UE Security Capabilities) field, terminal The access layer security information (AS Security Information) field of the device, etc., the above-mentioned fields are used to activate the security information for the terminal device under the target network device.
  • UE Security Capabilities UE Security Capabilities
  • AS Security Information access layer security information
  • the first indication information By carrying the first indication information in the handover request message, it is used to indicate the identification information of the first type, so that when the second network device receives the handover request message, it can determine the type of terminal device to be switched according to the first indication information It is the first type. Furthermore, the second network device may determine whether to agree to the handover according to whether it supports this type of terminal device. For example, if the second network device does not support the terminal device of the first type, the handover is rejected, and a handover preparation failure message carrying a failure cause value is sent to the first network device.
  • the second network device If the second network device supports the first type of terminal device, it can proceed according to the existing handover procedure (for example, determine whether to agree to handover according to other information in the handover request message), and when it is finally determined that the handover is approved, it can proceed to the first A network device sends a handover confirmation message.
  • the existing handover procedure for example, determine whether to agree to handover according to other information in the handover request message
  • the handover confirmation message for example, determine whether to agree to handover according to other information in the handover request message
  • the first handover preparation failure message is sent to the first network device.
  • the first handover preparation failure message includes failure information corresponding to the first type.
  • the failure cause (failure cause value) carried in the first handover preparation failure message indicates that the handover failed because the first type is not supported.
  • the first handover preparation failure message includes a 1-bit information field. The different states of the information field may indicate the reason for the failure. For example, a value of 1 in the information field indicates that the handover failed due to not supporting the first type, and a value of 0 in the information field indicates that the handover failed due to other reasons.
  • the first indication information may further include key value indication information, and the key value indication information is used to instruct the second network device to reject the handover under the first condition.
  • the first condition may be that the second network device does not support the first type of terminal device.
  • the second network device rejects this handover and sends a handover preparation failure message to the first network device.
  • "not supported" here can include two situations. The first situation is that the second network device can identify the first type of identification information, but the second network device does not support the first type of terminal device. The second situation is that the second network device cannot recognize the identification information of the first type.
  • the first indication information may carry the first type of identification information and the key value indication information in multiple ways.
  • the following takes a possible implementation as an example for introduction.
  • a new IE or field may be added to the handover request message (HANDOVER REQUEST message), for example, the name of the IE or field is reduced capability UE.
  • This IE or field is used as the first indication information.
  • the IE or field includes identification information of the first type and key value indication information.
  • the IE or field definition method refers to the method defined in the 3GPP RAN 3 protocol.
  • the attributes corresponding to this IE or field are shown in Table 1. Referring to Table 1, the attributes of the IE or field may include: name attribute, presence form, and key value attribute.
  • the name of the IE or the field is the first type of identification information.
  • the Presence form of the IE or field is mandatory or optional.
  • the key value of the IE or field can take the value "reject” or "ignore", that is, the key value indication information, which means that the second network device cannot recognize the IE or the field or the identification information carried by the IE or the field is rejected. Behavior is still ignoring behavior.
  • the IE or field may also include other more attributes, such as scope attribute, type attribute, importance attribute, and so on.
  • "XXXX” in Table 1 represents the value of the attribute, and this embodiment does not limit the value of other attributes.
  • the presence attribute can be defined as “O” (Optional), indicating that the handover request message (HANDOVER REQUEST message) may optionally include this IE or field.
  • the importance attribute (Criticality) is defined as "Yes", indicating the importance of the IE or field. and many more.
  • the first terminal device to be handed over is a UE with reduced performance
  • the key value of the IE or field can be set Is "reject".
  • the second network device receives the handover request message, if the second network device cannot recognize the IE or field (for example, it cannot recognize the name of the IE or field, or cannot recognize the id name corresponding to the name of the IE or field, Or the type pointed to by the IE or the field cannot be identified.
  • the second network device is a legacy network device.
  • the second network device rejects the handover behavior and sends a handover failure message (HANDOVER PREPARATION FAILURE message) to the first network device. ). If the second network device can identify the IE or field (in this case, the second network device is a network device that supports UEs with reduced performance), the second network device can continue to perform according to the existing handover procedure, and finally agree to handover At this time, a handover confirmation message (HANDOVER REQUEST ACKNOWLEDGE message) is sent to the first network device. Therefore, it is possible to effectively prevent the first network device from switching the performance-degraded UE to the legacy network device.
  • a handover confirmation message HANDOVER REQUEST ACKNOWLEDGE message
  • the first network device is a network device that currently provides services for the first terminal device, that is, the first network device supports a first type of terminal device (degraded performance UE).
  • the first network device may also provide services for the second terminal device, and the second terminal device is a second type of terminal device (for example, legacy UE).
  • the first network device can also support the second type of terminal device.
  • the communication method provided in this embodiment includes: the first network device determines that the type of the first terminal device is the first type, and the first network device sends a handover request message to the second network device, where the handover request message includes first indication information ,
  • the first indication information includes the identification information of the first type, so that after the second network device receives the handover request message, when the second network device does not support the terminal device of the first type, the first network device Send a handover preparation failure message, when the second network device supports the first type of terminal device, proceed according to the existing handover procedure, and send a handover confirmation message to the first network device when it is finally determined that the handover is approved.
  • FIG. 4 is a schematic flowchart of a communication method provided by an embodiment of this application.
  • the communication method of this embodiment can be applied to a handover scenario based on an NG interface.
  • the method of this embodiment includes:
  • the first network device determines that the type of the first terminal device is the first type.
  • the first network device sends a handover request message (HANDOVER REQUIRED message) to the AMF device, where the handover request message includes first indication information, and the first indication information includes the first type of identification information.
  • a handover request message HANDOVER REQUIRED message
  • the AMF device sends a handover request message (HANDOVER REQUEST message) to the second network device, where the handover request message includes the first indication information.
  • a handover request message HANDOVER REQUEST message
  • the second network device sends a handover confirmation message (HANDOVER REQUEST ACKNOWLEDGE message) or a handover failure message (HANDOVER FAILURE message) to the AMF device.
  • a handover confirmation message HANDOVER REQUEST ACKNOWLEDGE message
  • a handover failure message HANDOVER FAILURE message
  • the AMF device sends a handover command message (HANDOVER COMMAND message) or a handover preparation failure message (HANDOVER PREPARATION FAILURE message) to the first network device.
  • a handover command message HANDOVER COMMAND message
  • a handover preparation failure message HANDOVER PREPARATION FAILURE message
  • This embodiment is similar to the embodiment shown in FIG. 3, except that this embodiment is applied to a handover scenario based on an NG interface, that is, the handover signaling between the first network device and the second network device passes through the AMF device. Forward.
  • the following describes an example in which the first terminal device is a performance-reducing UE.
  • the new IE or field shown in Table 1 is added as the first indication information to the fifth indication information that can be transparently transmitted to the AMF.
  • the fifth indication information For example, it can be Handover Required Transfer IE.
  • the fifth indication information is included in the handover request message (HANDOVER REQUIRED message) sent by the first network device to the AMF. Since the fifth indication information is a transparent IE for the AMF, the AMF does not interpret the fifth indication information, but directly includes it in the handover request message (HANDOVER REQUEST message) and sends it to the second network device. The second network device interprets all the content included in the fifth instruction information.
  • the second network device can identify the first indication information (for example, it can identify the new IE/field in Table 1, or the identification information carried by the new IE/field), it means that the second network device is a UE that supports reduced performance.
  • Network device the second network device continues to proceed according to the existing protocol, and when it is finally determined to agree to the handover, it sends a handover confirmation message (HANDOVER REQUEST ACKNOWLEDGE message) to the AMF.
  • the second network device cannot recognize the first indication information (for example, the new IE/field in Table 1 cannot be recognized, or the identification information carried by the new IE/field cannot be recognized)
  • the second network device is a legacy network device.
  • the second network device rejects the handover behavior, and sends a handover failure message (HANDOVER FAILURE message) to the AMF, and the handover failure message carries the failure cause value.
  • the AMF receives a handover confirmation message (HANDOVER REQUEST ACKNOWLEDGE message) from the second network device, it sends a handover command message (HANDOVER COMMAND message) to the first network device so that the first network device knows that the second network device is ready To switch resources, you can switch. If the AMF receives a handover failure message (HANDOVER FAILURE message) from the second network device, it sends a handover preparation failure message (HANDOVER PREPARRATION FAILURE message) to the first network device to notify the first network device that the handover preparation has failed.
  • HANDOVER FAILURE message handover failure message
  • HANDOVER PREPARRATION FAILURE message handover preparation failure message
  • the first network device If the first network device receives the handover command message (HANDOVER PREPARRATION FAILURE message) sent by the AMF, the first network device will reply to the AMF with the handover notification message (HANDOVER NOTIFY message) after the handover is completed to inform the AMF that the terminal device has been The cell identification of the network equipment, the handover is completed.
  • HANDOVER PREPARRATION FAILURE message the handover command message sent by the AMF
  • the first network device will reply to the AMF with the handover notification message (HANDOVER NOTIFY message) after the handover is completed to inform the AMF that the terminal device has been The cell identification of the network equipment, the handover is completed.
  • the communication method provided in this embodiment includes: the first network device determines that the type of the first terminal device is the first type, the first network device sends a handover request message to the AMF, and the handover request message includes first indication information, and the first indication
  • the information includes the first type of identification information, and the first indication information is included in the fifth indication information that can be transparently transmitted to the AMF, so that the AMF does not interpret the first indication information and directly includes it in the handover request
  • the message is sent to the second network device.
  • the second network device After the second network device receives the handover request message, when the second network device does not support the first type of terminal device, it sends a handover failure message to the AMF and includes the failure cause value; the AMF sends the failure cause value to the first network
  • the device sends a handover preparation failure message and includes the failure cause value or indicates whether the handover fails due to not supporting the first type.
  • the second network device supports the terminal device of the first type, proceed according to the existing handover procedure, and send a handover confirmation message to the AMF when it is finally determined that the handover is approved; the AMF sends a handover command message to the first network device.
  • FIG. 5 is a schematic flowchart of a communication method provided by an embodiment of this application.
  • the communication method in this embodiment can be applied to a cell selection scenario. As shown in Figure 5, the method of this embodiment includes:
  • S501 A network device generates a system message, where the system message includes second indication information, the second indication information is used to indicate a first type, and the first type is a type among multiple types of terminal equipment.
  • the network device sends the system message, and correspondingly, the first terminal device receives the system message.
  • S503 The first terminal device obtains the second indication information included in the system message.
  • the first terminal device is in an idle state, for example, the first terminal device may be in the process of cell selection or cell reselection.
  • System messages broadcast by network devices are cell-level information.
  • System messages can include master information blocks (MIB) and system information blocks (SIB), such as SIB1, SIB2, and so on.
  • MIB master information blocks
  • SIB system information blocks
  • the MIB contains some limited but the most important and frequently sent parameters, and the terminal device must use these parameters to obtain other system messages.
  • the MIB may include downlink system bandwidth, PHICH configuration, SFN, and so on.
  • SIBs can be used to transmit a series of parameters related to different functions.
  • SIB1 includes parameters used to determine whether a cell is suitable for cell selection
  • SIB2 includes common radio resource configuration information, and so on.
  • the second indication information in this embodiment may be included in SIB1.
  • the second indication information is used to indicate the first type, where the first type is a type among multiple types of terminal equipment.
  • the terminal device of the first type may be a performance-reduced UE.
  • the second indication information indicates that the network device supports the terminal device of the first type, or the second indication information indicates whether the network device supports the terminal device of the first type.
  • the first type of terminal device is a reduced-performance UE
  • the second indication information indicates that the network device supports the reduced-performance UE
  • the second indication information indicates that the network device supports or whether it supports the reduced-performance UE.
  • a new IE or field can be added to SIB1.
  • the attribute of the IE or field can be an enumeration (ENUMERATED ⁇ XXX ⁇ ) type, for example, it can be enumerated ⁇ ture/false ⁇ , or it can be enumerated. For example, ⁇ supported/notSupported ⁇ , or enumeration may not be used, which is not specifically limited in this embodiment.
  • the added ASN.1 is as follows. For network equipment that supports UEs with reduced performance, the following IE or fields can be added to SIB1 to indicate that the network equipment indicates UEs with reduced performance. For legacy network devices, SIB1 does not include the following IEs or fields.
  • the terminal device determines that the network device supports a reduced-performance UE, and the above-mentioned IE or field exists in the SIB1. It can also be said that the terminal device determines that the network device supports the UE with reduced performance according to the presence of the above-mentioned IE or field in the SIB1. Otherwise, it is determined that the network device does not support the reduced performance UE.
  • the terminal device After the terminal device receives the SIB1, if this IE or field exists in the SIB1, it means that the network device supports the reduced-performance UE, that is, the network device is a network device that supports the reduced-performance UE. If this IE or field does not exist in SIB1, it means that the network device does not support the reduced performance UE, that is, the network device is a legacy network device.
  • the terminal device determines that the network device supports UEs with reduced performance, the aforementioned IE or field exists in the SIB1, and the indication information in the aforementioned IE or field is preset information (for example, true or supported). It can also be said that the terminal device determines that the network device supports the UE with reduced performance based on the presence of the above IE or field in the SIB1 and the indication information in the above IE or field being preset information. Otherwise, it is determined that the network device does not support the reduced performance UE.
  • the terminal device After the terminal device receives the SIB1, if the IE or field exists in the SIB1, it judges whether the network device supports the degraded UE according to the indication information in the IE or the field. For example, if the indication information in the IE or the field is true or supported, it is determined that the network device is a network equipment that supports the UE with reduced performance; if the indication information in the IE or the field is false or notSupported, it is determined that the network device is a legacy network device.
  • the terminal device determines that the network device supports a reduced-performance UE, the above IE or field exists in the SIB1, and the above IE or field indicates that the type of terminal device supported by the network device includes the first type. It can also be said that the terminal device determines that the network device supports the degraded UE based on the presence of the above IE or field in the SIB1, and the above IE or field indicating that the type of terminal device supported by the network device includes the first type. Otherwise, it is determined that the network device does not support the reduced performance UE.
  • a new IE or field can be added to SIB1. Assuming that the name of the IE or field is UEType-Supported, the IE or field can list the information of one or more terminal devices supported by the network device. type. In this way, after receiving the SIB1, the terminal device can learn the types of one or more terminal devices supported by the network device by analyzing the SIB1.
  • a bitmap may also be used to indicate which terminal device types are supported or not supported by the network device. For example, taking the type of terminal equipment including the first type and the second type as an example, a 2-bit bitmap may be used, and the two bits respectively correspond to whether the network equipment supports the first type and the second type of terminal equipment. Or, taking the type of terminal equipment including the first type and the second type as an example, a 1-bit IE or field can be used to indicate whether the corresponding network device supports the first type of terminal equipment, if it is supported, this bit is 1, which is not supported Is 0.
  • S504 The first terminal device determines whether to camp in the cell of the network device according to the second indication information.
  • the first terminal device can determine whether the network device supports the reduced-performance UE according to the second indication information, and then determine whether to camp in the cell of the network device; if not, it will The cell is regarded as barred, that is, it is forbidden to camp in the cell. Further, the subsequent behavior of the first terminal device is performed according to the existing protocol.
  • the terminal device determines the cell where the network device resides, and the above-mentioned IE or field exists in the SIB1. It can also be said that the terminal device determines the cell where the network device resides according to the presence of the above-mentioned IE or field in the SIB1. Otherwise, it is determined not to camp on the cell of the network device.
  • the network device when the newly added IE or field is used to indicate the first type, if the above newly added IE or field does not exist in SIB1, it means that the network device does not support performance reduction UEs, so it is determined not to reside on the network The cell of the device. If the above-mentioned new IE or field exists in SIB1, it means that the network device supports UE with reduced performance. Therefore, you can continue to determine whether other cell selection conditions are met according to the existing process, and if all conditions are met, make sure to stay In the cell of the network device.
  • the terminal device determines the cell where the network device resides, the above IE or field exists in the SIB1, and the indication information in the above IE or field is preset information (for example, true or supported) . It can also be said that the terminal device determines the cell where the network device resides according to the presence of the above IE or field in the SIB1 and the indication information in the above IE or field is preset information. Otherwise, it is determined not to camp on the cell of the network device.
  • the newly added IE or field is used to indicate whether the terminal device of the first type is supported, if the newly added IE or field exists in the SIB, and the indication information in the newly added IE or field is false or notSupported , It is determined that the network device does not support the reduced performance UE, and therefore it is determined that the network device does not camp on the cell of the network device. If the newly added IE or the indication information in the field is true or supported, it is determined that the network device is a network device that supports UEs with reduced performance, and can continue to determine whether other cell selection conditions are met according to the existing process, in the case where all conditions are met Next, determine the cell where the network device resides.
  • the terminal device determines the cell where the network device resides, the above IE or field exists in the SIB1, and the above IE or field indicates that the type of terminal device supported by the network device includes the first type. It can also be said that the terminal device determines the cell where the network device resides according to the presence of the above IE or field in the SIB1, and the above IE or field indicates that the type of terminal device supported by the network device includes the first type. Otherwise, it is determined not to camp on the cell of the network device.
  • the network device when the newly added IE or field is used to indicate the type of one or more terminal devices supported by the network device, if the newly added IE or field indicates that the type of terminal device supported does not include the first type, the network is determined The device does not support the reduced performance UE, so it is determined not to camp on the cell of the network device. If the newly added IE or the field indicates that the supported terminal device types include the first type, the network device is determined to be a network device that supports UEs with reduced performance, and it can continue to determine whether other cell selection conditions are met according to the existing process. If all are satisfied, determine the cell where the network device resides.
  • SIB1 may also include frequency band information and bandwidth information supported by the network device, such as: uplink frequency band list (frequencyBandList), downlink frequency band list (frequencyBandList), carrier bandwidth (carrierBandwidth), uplink At least one or more of initial BWP (initial uplink BWP), initial downlink BWP (initial downlink BWP), etc.
  • frequencyBandList uplink frequency band list
  • frequencyBandList downlink frequency band list
  • carrier bandwidth carrier bandwidth
  • uplink At least one or more of initial BWP initial uplink BWP
  • initial downlink BWP initial downlink BWP
  • the first terminal device can determine whether to reside in the cell of the network device according to the second indication information and the frequency band information and bandwidth information.
  • the first terminal device can continue to determine whether it supports the aforementioned frequency band information and bandwidth information, etc., and determine based on the S criterion Whether to reside in the cell of the network device.
  • the first terminal device may regard the cell as barred, that is, it is forbidden to camp on the cell. The cell.
  • the first terminal device is a terminal device (legacy UE) with a stronger capability than a UE with reduced performance
  • the first terminal device can perform according to the existing cell selection process, which is not described in detail in this embodiment.
  • the communication method provided in this embodiment includes: a network device generates and sends a system message, and the system message includes second indication information, where the second indication information is used to indicate whether the network device supports the first type of terminal device or whether it supports the first type of terminal device.
  • the terminal device can learn whether the network device supports the first type of terminal device according to the second indication information in the system message, and then determine whether to reside in the cell of the network device.
  • the network device For a reduced-performance UE, if it is determined according to the received system message that the network device does not support the reduced-performance UE, it does not reside in the cell of the network device; only when it is determined that the network device supports the reduced-performance UE, the network device As the candidate for cell selection, the cell can avoid degrading performance UE staying in legacy network equipment.
  • FIG. 6 is a schematic flowchart of a communication method provided by an embodiment of this application. As shown in Figure 6, the method of this embodiment includes:
  • the first network device generates a system message, where the system message includes second indication information, where the second indication information is used to indicate a first type, and the first type is a type among multiple types of terminal equipment.
  • S602 The first network device sends the system message, and the first terminal device receives the system message.
  • S601 and S602 in this embodiment are similar to S501 and S502 in FIG. 5, and will not be repeated here.
  • the first terminal device obtains the second indication information included in the system message.
  • the application scenario of this embodiment may be the aforementioned ANR scenario.
  • the first terminal device works in the cell of the second network device, that is, a certain cell of the second network device is the serving cell of the first terminal device.
  • the first network device is a network device corresponding to a neighboring cell of a serving cell of the terminal device.
  • the first terminal device is in a connected state.
  • the second network device may instruct the first terminal device to measure the neighboring cell.
  • the first terminal device monitors the broadcast of the neighboring cell, for example, it monitors the system message (such as MIB, SIB1) broadcast by the first network device, and reads the global and physical IDs of the neighboring cell (ie, global and physical IDs, for example: NR CGI/ NR PCI, ECGI/PCI)).
  • the system message broadcast by the first network device may include second indication information, and the second indication information is used to indicate the first type.
  • the second indication information is used to indicate that the first network device supports the first type of terminal device, or the second indication information is used to indicate whether the first network device supports the first type of terminal device.
  • the first type is a reduced-performance UE
  • the second indication information indicates whether the first network device supports or supports the reduced-performance UE. That is to say, in this embodiment, by instructing the first terminal device to monitor the system message of the first network device, the second network device can obtain the first network device's ability to support the UE with reduced performance.
  • the system message in this embodiment may be SIB1.
  • the first terminal device sends the second indication information or the determination result corresponding to the second indication information to the second network device; wherein, the determination result is that the first terminal device performs a check on the first network device according to the second indication information.
  • the first terminal device may send the second indication information to the second network device.
  • the second network device is made aware of the support capability of the first network device for the terminal device of the first type.
  • first terminal device may send the second indication information to the second network device, which is not specifically limited in this embodiment, and several possible implementation manners are described below as examples.
  • the first terminal device after receiving the SIB1 from the first network device, the first terminal device sends the second indication information parsed from the SIB1 to the second network device.
  • the second indication information may be carried in a CGI procedure report (procedure report) and a measurement report (measurement report) to be sent.
  • the first terminal device determines whether the first network device supports the first type of terminal device according to the second indication information in SIB1, and sends the determination result to The second network device. For example, it is possible to add an information field (field) to the measurement report, CGI procedure report, or other reports. For example, if the result of the determination is that the first network device supports terminal devices of the first type, the newly added field can be set to 1 or true or supported. If the result of the determination is that the first network device does not support terminal devices of the first type, Set the new field to 0 or false or notsupported.
  • an information field field
  • the second network device may store the second indication information. For example, it can be stored in a neighbor cell relation table (NCRT).
  • NCT neighbor cell relation table
  • FIG. 7 is a schematic diagram of the interaction process of an ANR scenario provided by an embodiment of the application. As shown in FIG. 7, it is assumed that the first terminal device works in cell A of the second network device. The first terminal device detects the cell B of the first network device.
  • the ANR interaction process includes:
  • the first terminal device sends the detected PCI of the cell B to the second network device.
  • the first terminal device receives the SIB1 of the cell B, and generates a CGI procedure report according to the neighbor cell information parsed from the SIB1.
  • the CGI procedure report includes: PLMN list, RAN area code (RAN area code, RANAC), tracking area code (tracking area code, TAC), cell ID (Cell ID), frequency band list, and one of the second indication information Or more.
  • S704 The first terminal device sends the CGI procedure report to the second network device.
  • the first terminal device receives the SIB1 of cell B, and obtains the PLMN list, TAC, Cell ID, and frequency band list corresponding to cell B by analyzing the SIB1, and carries this information in the CGI procedure report and sends it to the second Network equipment.
  • the first terminal device may also carry the second indication information obtained by parsing the SIB1 of cell B in a CGI procedure report or other report. . In this way, after receiving the report from the UE, the second network device can learn the support capability of the first network device for the terminal device of the first type according to the second indication information carried therein.
  • the CGI procedure report in the existing ANR process is called the original CGI procedure report, and the CGI procedure report in this embodiment is called the enhanced CGI procedure report.
  • the content included in the Enhanced CGI procedure report in this embodiment is shown in Table 2.
  • the second network device initiates an Xn connection establishment request to the first network device or the first network device to the second network device to establish an Xn connection between the network devices, and this Xn connection is used for subsequent handover procedures.
  • the handover between the first network device and the second network device is performed through the NG interface, that is, the handover request message and the handover success/failure message are forwarded via the core network AMF.
  • the handover between the first network device and the second network device will be performed through the NG interface.
  • the second network device when the second network device initiates a handover, it will use the information obtained from the CGI procedure report, including information about whether other network devices support or support the first type (degraded UE), as the judgment condition to select Target network device. For example, if the type of the terminal device to be handed over is a reduced-performance UE, the second network device selects a network device that supports the reduced-performance UE (for example, the first network device) as the target network device. Therefore, it is possible to avoid switching the performance-degraded UE to the legacy network equipment.
  • the type of the terminal device to be handed over is a reduced-performance UE
  • the second network device selects a network device that supports the reduced-performance UE (for example, the first network device) as the target network device. Therefore, it is possible to avoid switching the performance-degraded UE to the legacy network equipment.
  • FIG. 8 is a schematic flowchart of a communication method provided by an embodiment of this application. As shown in Figure 8, the method of this embodiment includes:
  • the first terminal device generates capability information, where the capability information includes third indication information, and the third indication information is used to indicate the type of the first terminal device, and the type of the first terminal device is the first type or the second type. Two types.
  • S802 The first terminal device sends the capability information to the network device.
  • the network device receives the capability information from the first terminal device.
  • the network device determines, according to the third indication information in the capability information, that the type of the first terminal device is the first type or the second type.
  • the method in this embodiment can be applied to a capability interaction scenario of a terminal device.
  • the capability interaction scenarios of the terminal device may include the following two scenarios.
  • Scenario 1 The terminal device actively reports its own capability information to the network device, for example: when the terminal device attaches to the network, or the terminal device performs tracking area updating (TAU), the terminal device actively reports the capability information.
  • TAU tracking area updating
  • Scenario 2 The network device asks the terminal device for the capability information of the terminal device.
  • it may further include: S800: the network device sends a capability request message to the first terminal device, and correspondingly, the first terminal device receives the capability request message from the network device.
  • the network device will issue a capability request message (UECapabilityEnquiry) to the terminal device.
  • UECapabilityEnquiry the capability request message
  • the terminal device reports the UE capability information (UECapabilityInformation) according to the request message.
  • the terminal device of the first type may be a performance-reduced UE.
  • the terminal device of the second type may be a terminal device with a higher capability than a UE with reduced performance.
  • the terminal device of the second type may be a legacy UE.
  • the first terminal device includes third indication information in the capability information, which is used to indicate the type of the first terminal device.
  • the network device can determine the type of the first terminal device based on the received capability information. Therefore, the network device can adopt different processing methods according to the type of the first terminal device. For example, if the type of the first terminal device is the first type (reduced performance UE), the bandwidth supported by the first terminal device is considered to be the bandwidth reported through bitmap or other forms. When the first terminal device needs to switch, the first terminal device needs to be switched. A terminal device switches to a network device that supports UEs with reduced performance. If the type of the first terminal device is the second type (for example, legacy UE), the bandwidth of the first terminal device is considered to be the bandwidth and 100 MHz reported by bitmap or other forms.
  • the type of the first terminal device is the second type (for example, legacy UE)
  • the bandwidth of the first terminal device is considered to be the bandwidth and 100 MHz reported by bitmap or other forms.
  • FIG. 9 is a schematic flowchart of a communication method provided by an embodiment of this application.
  • the method in this embodiment can be applied to the scenario of establishing an Xn interface. As shown in FIG. 9, the method of this embodiment includes:
  • the first network device sends an Xn interface setup request message (XN SETUP REQUEST message) to the second network device, where the Xn interface setup request message includes query information, and the query information is used to query whether the second network device Support the first type of terminal equipment.
  • XN SETUP REQUEST message Xn interface setup request message
  • a new IE or field (such as reduced capability UE accessibility) can be added to the Xn interface setup request message (XN SETUP REQUEST message) to query the second network Whether the device supports UE with reduced performance.
  • the Xn interface establishment request message may also include application data of the first network device.
  • the application data of a network device includes but is not limited to: the ID of the network device, the AMF region information (AMF region information) corresponding to the network device, the cell and neighboring cell information of the network device, and so on.
  • the second network device can determine whether to establish an Xn interface with the first network device according to the application data of the first network device.
  • the second network device sends an Xn interface setup response message (XN SETUP RESPONSE message) or an Xn interface setup failure message (XN SETUP FAILURE message) to the first network device, where the Xn interface setup response message includes fourth indication information ,
  • the fourth indication information is used to indicate whether the second network device supports the first type of terminal device.
  • the second network device determines that the Xn interface cannot be established, the second network device sends an Xn interface establishment failure message (XN SETUP FAILURE message) to the first network device.
  • XN SETUP FAILURE message an Xn interface establishment failure message
  • the second network device sends an Xn interface establishment response message (XN SETUP RESPONSE message) to the first network device.
  • the Xn interface establishment response message includes fourth indication information.
  • the fourth indication information may have various forms, which are not limited in this embodiment. For example, 1 bit can be added to the Xn interface establishment response message, or the existing 1 bit can be reused to represent the fourth indication information. If the second network device supports the first type of terminal device, then this bit is set to 1, and if the second network device does not support the first type of terminal device, then this bit is set to 0. In this way, the first network device can learn whether the second network device supports the first type of terminal device according to the fourth indication information.
  • the Xn interface setup response message may also include the application data of the second network device.
  • the first network device can learn related information of the second network device according to the application data of the second network device.
  • the first network device may also store the application data and the fourth indication information of the second network device.
  • the first network device needs to initiate a switch to the terminal device of the first type, it can determine which target network device to switch the terminal device of the first type to according to the stored fourth indication information of each network device. For example, when the first network device needs to initiate a handover to the UE with reduced performance, it may select the network device supporting the UE with reduced performance as the target network device according to the stored fourth indication information of each network device. Therefore, it is avoided that the UE with reduced performance is switched to a network device that does not support UEs with reduced performance.
  • the embodiment of the present application provides a communication device.
  • the communication device may be a network device or an internal component of the network device, such as a chip or an integrated circuit.
  • the following takes network equipment as an example for illustration. Those skilled in the art will know that the following network equipment can be replaced with communication devices such as chips or integrated circuits.
  • FIG. 10 is a schematic structural diagram of a network device provided by an embodiment of this application. As shown in FIG. 10, the network device 10 of this embodiment may include one or more of a processing unit 11, a sending unit 12, and a receiving unit 13. The following describes the network device of this embodiment in combination with different application scenarios.
  • the network device of this embodiment can be applied to handover scenarios.
  • the network device 10 of this embodiment can be used as the first network device.
  • the network device 10 may include a processing unit 11, a sending unit 12, and a receiving unit 13.
  • the processing unit 11 is configured to determine that the type of the first terminal device is the first type
  • the sending unit 12 is configured to send a handover request message, where the handover request message includes first indication information, and the first indication information includes the first indication information.
  • the receiving unit 13 is used to receive a handover confirmation message or a handover preparation failure message.
  • the first indication information further includes key value indication information, and the key value indication information is used to instruct the second network device to reject the handover under the first condition.
  • the receiving unit 13 is specifically configured to: receive a handover confirmation message from a second network device that supports the first type of terminal device; or, receive a handover confirmation message from a second network device.
  • the sending unit 12 is specifically configured to: send the handover request message to the second network device; or, send the handover request message to the second network device through the access and mobility management function AMF device. Request message.
  • the network device of this embodiment can be used to implement the communication method executed by the first network device in the method embodiments shown in FIG. 3 and FIG.
  • the network device 10 of this embodiment can also be used as a second network device.
  • the network device 10 may include a receiving unit 13 and a sending unit 12.
  • the receiving unit 13 is configured to receive a handover request message, the handover request message includes first indication information, the first indication information includes identification information of a first type, and the first type is the first type of the terminal device; Or the first type is the type of the first terminal device; the sending unit 12 is configured to send a handover confirmation message or a handover preparation failure message.
  • the handover request message further includes capability information of the first terminal device, and the type of the first terminal device is the first type.
  • the first indication information further includes key value indication information, and the key value indication information is used to instruct the second network device to reject the handover under the first condition.
  • the receiving unit 13 is specifically configured to: receive the handover request message sent by the first network device; or, receive the handover request message from the first network device through the access and mobility management function AMF device .
  • the network device of this embodiment can be used to implement the communication method executed by the second network device in the method embodiments shown in FIG. 3 and FIG.
  • the network equipment of this embodiment can also be applied to cell selection or cell reselection or ANR scenarios.
  • the network device 10 may include a processing unit 11 and a sending unit 12.
  • the processing unit 11 is configured to generate a system message, the system message includes second indication information, the second indication information is used to indicate a first type, and the first type is the first type of the terminal device; the sending unit 12 Used to send the system message.
  • the system message is a system message block SIB1.
  • the network device of this embodiment can be used to implement the communication method executed by the network device in the method embodiments shown in FIG. 5 to FIG.
  • the network device of this embodiment can also be applied to a capability interaction scenario of a terminal device.
  • the network device 10 may include a receiving unit 13 and a processing unit 11.
  • the receiving unit 13 is configured to receive capability information from the first terminal device, and the capability information includes third indication information;
  • the processing unit 11 is configured to determine that the type of the first terminal device is the first terminal device according to the third indication information.
  • the network device 10 may further include a sending unit 12 configured to send a capability request message to the first terminal device.
  • the network device of this embodiment can be used to implement the communication method executed by the network device in the method embodiment shown in FIG.
  • the network device of this embodiment can also be applied to the scenario of establishing an Xn interface.
  • the network device 10 of this embodiment may be used as the first network device.
  • the network device 10 may include a receiving unit 13 and a sending unit 12.
  • the sending unit 12 is configured to send an Xn interface establishment request message to the second network device, the Xn interface establishment request message includes inquiry information, and the inquiry information is used to inquire whether the second network device supports the first type Terminal device;
  • the receiving unit 13 is configured to receive an Xn interface establishment response message or an Xn interface establishment failure message from the second network device; wherein the Xn interface establishment response message includes fourth indication information, and the fourth indication information is used to indicate Whether the second network device supports terminal devices of the first type.
  • the network device of this embodiment can be used to implement the communication method executed by the first network device in the method embodiment shown in FIG.
  • the network device 10 of this embodiment can also be used as a second network device.
  • the network device 10 may include a receiving unit 13 and a sending unit 12.
  • the receiving unit 13 is configured to receive an Xn interface establishment request message from the first network device, the Xn interface establishment request message includes inquiry information, and the inquiry information is used to inquire whether the second network device supports the first type of Terminal equipment;
  • the sending unit 12 is configured to send an Xn interface establishment response message or an Xn interface establishment failure message to the first network device; wherein the Xn interface establishment response message includes fourth indication information, and the fourth indication information is used to indicate Whether the second network device supports terminal devices of the first type.
  • the network device of this embodiment can be used to implement the communication method executed by the second network device in the method embodiment shown in FIG.
  • FIG. 11 is a schematic structural diagram of a terminal device provided by an embodiment of the application. As shown in FIG. 11, the terminal device 20 of this embodiment may include one or more of a processing unit 21, a sending unit 22, and a receiving unit 23. The following describes the terminal device of this embodiment in combination with different application scenarios.
  • the terminal equipment of this embodiment can be applied to cell selection or cell reselection or ANR scenarios.
  • the terminal device 10 of this embodiment can be used as the first terminal device.
  • the terminal device 10 may include a receiving unit 23 and a processing unit 21.
  • the receiving unit 23 is used to receive a system message from a network device;
  • the processing unit 21 is used to obtain the second indication information contained in the system message, and the second indication information is used to indicate the first type, and the first type It is the first type of terminal equipment.
  • the system message is a system message block SIB1.
  • the processing unit 21 is further configured to determine whether to camp in the cell of the network device according to the second indication information.
  • the system message further includes: frequency band information and bandwidth information supported by the network device; the processing unit 21 is specifically configured to: according to the second indication information and the information supported by the network device The frequency band information and bandwidth information determine whether to reside in the cell of the network device.
  • the network device is a network device corresponding to a neighboring cell of the serving cell of the first terminal device; the terminal device 10 may further include a sending unit 22, and the sending unit 22 is configured to: send the The second indication information is to the network device corresponding to the serving cell.
  • the terminal device of this embodiment can be used to implement the communication method executed by the terminal device in the method embodiments shown in FIG. 5 to FIG.
  • the terminal device of this embodiment can also be applied to the capability interaction scenario of the terminal device.
  • the terminal device 20 may include a sending unit 22 and a processing unit 21.
  • the processing unit 21 is configured to generate capability information, the capability information includes third indication information, the third indication information is used to indicate the type of the first terminal device, and the type of the first terminal device is the first type or The second type; the sending unit 22 is used to send the capability information to the network device.
  • the terminal device 20 may further include a receiving unit 23 configured to receive a capability request message from the network device.
  • the terminal device of this embodiment can be used to implement the communication method executed by the terminal device in the method embodiment shown in FIG.
  • FIG. 12 is a schematic structural diagram of a network device provided by an embodiment of this application.
  • the network device 30 of this embodiment may include: a processor 31, a memory 32, and a communication interface 33.
  • the number of processors 31 may be one or more.
  • the number of memories 32 may be one or more.
  • the memory 32 is used for storing computer programs; the communication interface 33 is used for data communication or signal communication with other network devices or terminal devices.
  • the processor 31 is configured to execute a computer program stored in the memory 32 to implement the communication method executed by the first network device in the method embodiment shown in FIGS. 3 and 4, or to implement the method implementation shown in FIGS. 3 and 4
  • the communication method executed by the second network device in the example, or the communication method executed by the network device in the method embodiment shown in FIG. 5 to FIG. 7, or the communication method executed by the network device in the method embodiment shown in FIG. Or, implement the communication method executed by the first network device in the method embodiment shown in FIG. 9, or implement the communication method executed by the second network device in the method embodiment shown in FIG. 9.
  • the memory 32 may be independent or integrated with the processor 31.
  • the network device 30 may further include: a bus 34 for connecting the memory 32 and the processor 31.
  • processing module 11 in FIG. 10 may be integrated into the processor 31 for implementation, and the receiving module 13 and the sending module 12 may be integrated into the communication interface 33 for implementation.
  • the processor 31 may be used to implement the signal processing operation of the network device in the foregoing method embodiment
  • the communication interface 33 may be used to implement the signal transceiving operation of the network device in the foregoing method embodiment.
  • the network device provided in this embodiment can be used to execute the method executed by the network device in the foregoing method embodiment, and its implementation principles and technical effects are similar, and will not be repeated here.
  • FIG. 13 is a schematic structural diagram of a terminal device provided by an embodiment of the application.
  • the terminal device 40 of this embodiment includes: a processor 41, a memory 42 and a transceiver 43.
  • the number of processors 41 may be one or more.
  • the number of memories 42 may be one or more.
  • the memory 42 is used for storing computer programs; the transceiver 43 is used for data communication or signal communication with network devices.
  • the processor 41 is configured to execute a computer program stored in the memory 42 to implement the communication method executed by the terminal device in the method embodiment shown in FIG. 5 to FIG. 7, or to implement the communication method executed by the terminal device in the method embodiment shown in FIG. Communication method.
  • the memory 42 may be independent or integrated with the processor 41.
  • the terminal device 40 may further include: a bus 44 for connecting the memory 42 and the processor 41.
  • processing module 21 in FIG. 11 may be integrated in the processor 41 for implementation, and the receiving module 23 and the sending module 22 may be integrated in the transceiver 43 for implementation.
  • the processor 41 may be used to implement the signal processing operation of the terminal device in the foregoing method embodiment
  • the transceiver 43 may be used to implement the signal transceiving operation of the terminal device in the foregoing method embodiment.
  • the terminal device provided in this embodiment can be used to execute the method executed by the terminal device in the foregoing method embodiment, and its implementation principles and technical effects are similar, and will not be repeated here.
  • the embodiment of the present application provides a computer storage medium, the computer storage medium includes a computer program, and the computer program is used to implement the method executed by the network device in the foregoing method embodiment, or implement the method executed by the terminal device in the foregoing method embodiment. Methods.
  • the embodiments of the present application also provide a chip or chip system.
  • the chip or chip system includes at least one processor and a communication interface.
  • the communication interface and the at least one processor are interconnected by wires, and the at least one processor is used to run computer programs or instructions to Implement the method executed by the network device in the foregoing method embodiment, or implement the method executed by the terminal device in the foregoing method embodiment.
  • the communication interface in the chip can be an input/output interface, a pin, or a circuit.
  • the chip or chip system described above in this application further includes at least one memory, and instructions are stored in the at least one memory.
  • the memory may be a storage unit inside the chip, for example, a register, a cache, etc., or a storage unit of the chip (for example, a read-only memory, a random access memory, etc.).
  • the embodiment of the present application also provides a computer program product, the computer program product includes computer program code, when the computer program code runs on a computer, the computer is caused to execute the method executed by the network device in the above method embodiment, or Implement the method executed by the terminal device in the above method embodiment.
  • the embodiment of the present application also provides a communication system, including a first network device and a second network device.
  • the first network device and the second network device may adopt the structure shown in FIG. 10 or FIG. 12.
  • the first network device and the second network device may implement the communication method shown in FIG. 3 or FIG. 4.
  • the first network device and the second network device may implement the communication method as shown in FIG. 9.
  • the embodiment of the present application also provides a communication system, including: a network device and a terminal device.
  • the network device may adopt the structure shown in FIG. 10 or FIG. 12
  • the terminal device may adopt the structure shown in FIG. 11 or FIG.
  • network devices and terminal devices can be used to implement the communication methods shown in Figs. 5-7.
  • network equipment and terminal equipment can be used to implement the communication method as shown in FIG. 8.
  • the disclosed device and method may be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of the modules is only a logical function division, and there may be other divisions in actual implementation, for example, multiple modules can be combined or integrated. To another system, or some features can be ignored, or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or modules, and may be in electrical, mechanical or other forms.
  • modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules can be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the functional modules in the various embodiments of the present application may be integrated into one processing unit, or each module may exist alone physically, or two or more modules may be integrated into one unit.
  • the units formed by the above-mentioned modules can be implemented in the form of hardware, or in the form of hardware plus software functional units.
  • the above-mentioned integrated modules implemented in the form of software functional modules may be stored in a computer readable storage medium.
  • the above-mentioned software function module is stored in a storage medium and includes a number of instructions to make a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (English: processor) execute the various embodiments of the present application Part of the method.
  • processor may be a central processing unit (English: central processing unit, abbreviated as: CPU), or other general-purpose processors, digital signal processors (English: digital signal processor, abbreviated as: DSP), and application-specific integrated circuits. (English: application specific integrated circuit, referred to as ASIC) etc.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like. The steps of the method disclosed in combination with the invention can be directly embodied as executed and completed by a hardware processor, or executed and completed by a combination of hardware and software modules in the processor.
  • the memory may include a high-speed RAM memory, or may also include a non-volatile storage NVM, such as at least one disk storage, and may also be a U disk, a mobile hard disk, a read-only memory, a magnetic disk, or an optical disk.
  • NVM non-volatile storage
  • the bus may be an industry standard architecture (ISA) bus, a peripheral component (PCI) bus, or an extended industry standard architecture (EISA) bus.
  • ISA industry standard architecture
  • PCI peripheral component
  • EISA extended industry standard architecture
  • the bus can be divided into address bus, data bus, control bus and so on.
  • the buses in the drawings of this application are not limited to only one bus or one type of bus.
  • the above-mentioned storage medium can be realized by any type of volatile or non-volatile storage device or their combination, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable Except programmable read only memory (EPROM), programmable read only memory (PROM), read only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read-only memory
  • EPROM erasable except programmable read only memory
  • PROM programmable read only memory
  • ROM read only memory
  • magnetic memory flash memory
  • flash memory magnetic disk or optical disk.
  • optical disk any available medium that can be accessed by a general-purpose or special-purpose computer.
  • An exemplary storage medium is coupled to the processor, so that the processor can read information from the storage medium and write information to the storage medium.
  • the storage medium may also be an integral part of the processor.
  • the processor and the storage medium may be located in application specific integrated circuits (ASIC for short).
  • ASIC application specific integrated circuits
  • the processor and the storage medium may also exist as discrete components in the electronic device or the main control device.

Landscapes

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

Abstract

本申请实施例提供一种通信方法及设备，可应用于支持降低性能(reduced capability)终端设备的通信技术领域，例如低能力UE或者MTC UE。该方法包括：第一网络设备确定第一终端设备的类型为第一类型，第一网络设备发送切换请求消息，切换请求消息包括第一指示信息，第一指示信息包含第一类型的标识信息；第一网络设备接收切换确认消息或者切换准备失败消息。通过上述过程，可以避免将第一类型的终端设备切换至不支持第一类型的网络设备中。

Description

通信方法及设备 技术领域
本申请涉及通信技术领域，尤其涉及一种通信方法及设备。
背景技术
“对降低性能的NR设备的支持(support of reduced capability NR devices)”是第三代合作伙伴计划(3rd generation partnership project,3GPP)在Release 17中提出的新研究领域之一。“对降低性能的NR设备的支持”是一种支持较窄的带宽和较低的峰值数据速率场景的功能，主要为高端机器型态通讯(machine type communication，MTC)设备提供轻量级通信(lightweight communications)。适用于该场景的能力较弱的终端设备可以称为降低性能UE(reduced capability UE)或者低能力UE。与传统UE相比，降低性能UE支持的带宽一般在20MHz以下，支持的峰值数据速率一般为5-10Mb/s，并且对于时延、可靠性等性能的要求有所降低。该类设备主要包括：可穿戴设备、监控摄像头、工业传感器等。
目前的新空口(new radio,NR)协议中，UE通过含有10个比特(bit)位的位图(bit map)上报自身支持的上下行带宽，10个bit位分别对应UE是否支持带宽5MHz、10MHz、15MHz、20MHz、25MHz、30MHz、40MHz、50MHz、60MHz、80MHz。按照目前协议要求，所有UE均需支持100MHz带宽。因此，尽管在UE上报的bit map中不存在表示UE是否支持100MHz带宽的bit位，legacy网络设备均默认UE支持100MHz带宽。也就是说，legacy网络设备认为UE支持的带宽为该UE在bit map中上报的带宽和100MHz。
对于降低性能UE而言，降低性能UE无法支持100MHz，仅支持bit map中上报的带宽。因此，若降低性能UE工作于目前协议下的网络设备，即legacy网络设备的小区，网络设备会误判降低性能UE的能力，比如为其分配不在其支持带宽范围内的BWP，可能会导致降低性能UE无法正常工作。
发明内容
本申请实施例提供一种通信方法及设备，能够避免降低性能UE驻留到legacy网络设备中，或者避免降低性能UE切换至legacy网络设备中。
第一方面，本申请实施例提供一种通信方法，该方法包括：第一网络设备确定第一终端设备的类型为第一类型，第一网络设备发送切换请求消息，所述切换请求消息包括第一指示信息，所述第一指示信息包含所述第一类型的标识信息；第一网络设备接收切换确认消息或者切换准备失败消息。
在上述方案中，第一网络设备在切换请求消息包括第一指示信息，第一指示信息包含所述第一类型的标识信息。这样，第二网络设备接收到切换请求消息后，在第二网络设备不支持第一类型的终端设备时，向第一网络设备发送切换准备失败消息。在第二网络设备 支持第一类型的终端设备时，按照现有切换流程继续进行，并在最终确定同意切换时向第一网络设备发送切换确认消息。通过上述过程，可以避免将第一类型的终端设备切换至不支持第一类型的网络设备中。
其中，本申请中涉及多个类型的终端设备，第一类型为多个类型中的一个类型。一个示例中，终端设备的多个类型可以是根据终端设备的能力划分的。可选的，终端设备的多个类型可以包括第一类型和第二类型。其中，第一类型的终端设备的能力低于第二类型的终端设备的能力。示例性的，第一类型的终端设备可以为降低性能UE，第二类型的终端设备为能力高于降低性能UE的终端设备，例如第二类型的终端设备可以为legacy UE。
第一类型的标识信息是指能够用于标识第一类型的任意信息。一个示例中，第一类型的标识信息可以为第一类型的名称。另一个示例中，不同的类型可以对应有不同的索引，这样，第一类型的标识信息可以为第一类型对应的索引。
一种可能的实现方式中，所述第一指示信息还包含关键值指示信息，所述关键值指示信息用于指示第二网络设备在第一条件下拒绝所述切换。
可选的，第一条件可以为第二网络设备不支持第一类型的终端设备。这里的“不支持”可以包括两种情况。第一种情况为第二网络设备可以识别第一类型的标识信息，但是第二网络设备不支持第一类型的终端设备。第二种情况为第二网络设备无法识别第一类型的标识信息。
一个示例中，切换请求消息包括新的IE或字段。例如，新的IE或字段的名称为reduced capability UE。该IE或字段作为第一指示信息。该IE或字段包括第一类型的标识信息和关键值指示信息。例如，该IE或字段的名称即第一类型的标识信息，该IE或字段的关键值可以取值为“reject”或者“ignore”，即关键值指示信息，表示第二网络设备无法识别该IE或字段或无法识别该IE或字段携带的标识信息时采取拒绝行为还是忽略行为。
对于切换场景而言，假设当前待切换的第一终端设备为降低性能UE，则第一网络设备生成切换请求消息时，将该IE或字段的关键值设置为“reject”。这样，第二网络设备接收到切换请求消息后，若第二网络设备无法识别该IE或字段，则第二网络设备拒绝切换行为，并向第一网络设备发送切换失败信息。若第二网络设备可以识别该IE或字段，则第二网络设备可以按照现有切换流程继续执行，并在最终确定同意切换时，向第一网络设备发送切换确认消息。因此，可以有效避免第一网络设备将降低性能UE切换至legacy网络设备中。
可选的，第一网络设备还可以为第二终端设备提供服务，第二终端设备为第二类型的终端设备(例如legacy UE)。也就是说，第一网络设备还可以支持第二类型的终端设备。
一种可能的实现方式中，第一网络设备接收切换确认消息或者切换准备失败消息，包括：第一网络设备接收来自第二网络设备的切换确认消息，所述第二网络设备支持所述第一类型的终端设备；或者，第一网络设备接收来自第二网络设备的第一切换准备失败消息，所述第一切换准备失败消息包含对应所述第一类型的失败信息，所述第二网络设备不支持所述第一类型的终端设备。
一个示例中，第一切换准备失败消息中携带的失败原因(failure cause value)指示的是由于不支持第一类型导致的切换失败。
一种可能的实现方式中，第一网络设备发送切换请求消息，包括：第一网络设备向第 二网络设备发送所述切换请求消息；或者，第一网络设备通过接入和移动性管理功能AMF设备向第二网络设备发送所述切换请求消息。
例如，在第一网络设备和第二网络设备之间建立有Xn接口连接时，第一网络设备向第二网络设备发送所述切换请求消息。在第一网络设备和第二网络设备之间没有建立Xn接口连接时，第一网络设备和第二网络设备通过NG接口进行切换流程，即第一网络设备通过AMF设备向第二网络设备发送切换请求消息。
在基于NG接口的切换场景中，第一网络设备向AMF发送切换要求消息，并在切换要求消息中包括第一指示信息(例如上述新的IE或字段)。示例性的，第一指示信息可以被添加至可对AMF透传的第五指示信息中，第五指示信息例如可以为Handover Required Transfer IE。由于第五指示信息对于AMF来说是一个透明的IE，AMF不对第五指示信息进行解读，直接将其包含在切换请求消息中发送给第二网络设备。第二网络设备解读第五指示信息中包含的全部内容。若第二网络设备可以识别该第一指示信息(例如，可以识别上述新IE/字段，或者可以识别新IE/字段携带的标识信息)，则按现有协议继续进行，并在最终确定同意切换时，向AMF发送切换确认消息，AMF向第一网络设备发送切换命令消息。若第二网络设备无法识别该第一指示信息(例如，无法识别上述新IE/字段，或者无法识别新IE/字段携带的标识信息)，则第二网络设备拒绝切换行为，并向AMF发送切换失败消息，AMF向第一网络设备发送切换准备失败消息。
第二方面，本申请实施例提供一种通信方法，该方法包括：第二网络设备接收切换请求消息，所述切换请求消息包括第一指示信息，所述第一指示信息包含第一类型的标识信息，所述第一类型为终端设备的第一类型；或者所述第一类型为第一终端设备的类型；第二网络设备发送切换确认消息或者切换准备失败消息。
在上述方案中，由于切换请求消息包括第一指示信息，第一指示信息包含所述第一类型的标识信息。这样，第二网络设备接收到切换请求消息后，在第二网络设备不支持第一类型的终端设备时，向第一网络设备发送切换准备失败消息。在第二网络设备支持第一类型的终端设备时，按照现有切换流程继续进行，并在最终确定同意切换时向第一网络设备发送切换确认消息。通过上述过程，可以避免将第一类型的终端设备切换至不支持第一类型的网络设备中。
一种可能的实现方式中，所述切换请求消息还包括第一终端设备的能力信息，所述第一终端设备的类型为所述第一类型。
其中，能力信息可以包括下述中的一种或者多种：最大传输带宽，传输速率，可靠性，时延容忍度，天线数量，或续航时间等。
一种可能的实现方式中，所述第一指示信息还包含关键值指示信息，所述关键值指示信息用于指示第二网络设备在第一条件下拒绝所述切换。
一种可能的实现方式中，第二网络设备接收切换请求消息，包括：第二网络设备接收第一网络设备发送的切换请求消息；或者，第二网络设备通过接入和移动性管理功能AMF设备接收来自第一网络设备的切换请求消息。
第三方面，本申请实施例提供一种通信方法，包括：网络设备生成系统消息，所述系统消息包括第二指示信息，所述第二指示信息用于指示第一类型，所述第一类型为终端设备的第一类型；网络设备发送所述系统消息。
上述方案的应用场景中，第一终端设备处于空闲态，例如第一终端设备可以是正在进行小区选择或小区重选。
第二指示信息用于指示第一类型。例如，第一类型的终端设备可以为降低性能UE。换句话说，第二指示信息指示的是网络设备支持第一类型的终端设备，或者，第二指示信息指示的是网络设备是否支持第一类型的终端设备。
一种可能的实现方式中，所述系统消息为系统消息块SIB1。
可选的，终端设备确定网络设备支持降低性能UE，所述SIB1中存在新的IE或者字段。也可以说，终端设备根据所述SIB1中存在上述IE或者字段，确定所述网络设备支持降低性能UE。否则，确定所述网络设备不支持降低性能UE。例如，该新的IE或字段的属性可以是枚举类型，例如可以枚举{ture/false},也可以枚举{supported/notSupported}，或者，也可以不使用枚举。
可选的，终端设备确定网络设备支持降低性能UE，所述SIB1中存在上述IE或者字段，并且上述IE或者字段中的指示信息为预设信息(例如true或者supported)。也可以说，终端设备根据所述SIB1中存在上述IE或者字段，并且上述IE或者字段中的指示信息为预设信息，确定所述网络设备支持降低性能UE。否则，确定所述网络设备不支持降低性能UE。
可选的，终端设备确定网络设备支持降低性能UE，所述SIB1中存在上述IE或者字段，并且上述IE或者字段指示所述网络设备支持的终端设备的类型包括第一类型。也可以说，终端设备根据所述SIB1中存在上述IE或者字段，并且上述IE或者字段指示所述网络设备支持的终端设备的类型包括第一类型，确定网络设备支持降低性能UE。否则，确定网络设备不支持降低性能UE。
第四方面，本申请实施例提供一种通信方法，该方法包括：终端设备接收来自网络设备的系统消息；终端设备获取所述系统消息包含的第二指示信息，所述第二指示信息用于指示第一类型，所述第一类型为终端设备的第一类型。
一种可能的实现方式中，所述系统消息为系统消息块SIB1。
一种可能的实现方式中，所述方法还包括：根据所述第二指示信息，确定是否驻留在所述网络设备的小区。
可选的，终端设备确定驻留在所述网络设备的小区，所述SIB1中存在上述IE或者字段。也可以说，终端设备根据所述SIB1中存在上述IE或者字段，确定驻留在所述网络设备的小区。否则，确定不驻留在所述网络设备的小区。
可选的，终端设备确定驻留在所述网络设备的小区，所述SIB1中存在上述IE或者字段，并且上述IE或者字段中的指示信息为预设信息(例如true或者supported)。也可以说，终端设备根据所述SIB1中存在上述IE或者字段，并且上述IE或者字段中的指示信息为预设信息，确定驻留在所述网络设备的小区。否则，确定不驻留在所述网络设备的小区。
可选的，终端设备确定驻留在所述网络设备的小区，所述SIB1中存在上述IE或者字段，并且上述IE或者字段指示所述网络设备支持的终端设备的类型包括第一类型。也可以说，终端设备根据所述SIB1中存在上述IE或者字段，并且上述IE或者字段指示所述网络设备支持的终端设备的类型包括第一类型，确定驻留在所述网络设备的小区。否则，确定不驻留在所述网络设备的小区。
一种可能的实现方式中，所述系统消息还包括：所述网络设备支持的频带信息和带宽信息；根据所述第二指示信息，确定是否驻留在所述网络设备的小区，包括：根据所述第二指示信息以及所述网络设备支持的频带信息和带宽信息，确定是否驻留在所述网络设备的小区。
上述各实现方式中，通过在系统消息中包括第二指示信息，所述第二指示信息用于指示第一类型，这样，终端设备根据系统消息中的第二指示信息，可以获知网络设备是否支持第一类型的终端设备，进而确定是否驻留在该网络设备的小区。对于降低性能UE而言，若根据接收到的系统消息确定网络设备不支持降低性能UE，则不驻留在该网络设备的小区；只有在确定网络设备支持降低性能UE时，才将该网络设备的小区作为小区选择的候选对象，从而能够避免降低性能UE驻留到legacy网络设备中。
一种可能的实现方式中，所述网络设备为第一终端设备的服务小区的邻区对应的网络设备；所述方法还包括：第一终端设备发送所述第二指示信息到所述服务小区对应的网络设备。或者，第一终端设备将所述第二指示信息对应的确定结果发送到第二网络设备。其中，所述确定结果为第一终端设备根据第二指示信息对第一网络设备是否支持第一类型的终端设备进行判断得到的结果。
可选的，第一终端设备将第二指示信息或者第二指示信息对应的确定结果携带在CGI程序报告(procedure report)、测量报告(measurement report)中发送。
一个示例中，第一终端设备向第二网络设备发送检测到的第一小区的PCI。若第二网络设备发现第一终端设备上报的第一小区的PCI不可识别，则指示第一终端设备获取该PCI对应的邻区信息。第一终端设备接收第一小区的SIB1，并根据从SIB1中解析得到的邻区信息生成CGI procedure report。第一终端设备将CGI procedure report发送给第二网络设备。
上述示例中，CGI procedure report中包括：PLMN列表、RANAC、TAC、小区ID、频段列表、第二指示信息中的一个或多个。通过将SIB1中的第二指示信息添加到CGI procedure report中，不会带来因测量或读取其他邻小区相关的信息而引起的延时。
上述示例中，当第二网络设备发起切换时，将利用从CGI procedure report中获取的信息，包括其他网络设备支持或者是否支持降低性能UE的信息，作为判断条件，以选择目标网络设备。从而可以避免将降低性能UE切换至legacy网络设备中。
第五方面，本申请实施例提供一种通信方法，该方法包括：第一终端设备生成能力信息，所述能力信息包括第三指示信息，所述第三指示信息用于指示第一终端设备的类型，所述第一终端设备的类型为第一类型或者第二类型；第一终端设备向网络设备发送所述能力信息。
一种可能的实现方式中，第一终端设备生成能力信息之前，还包括：第一终端设备从网络设备接收能力请求消息。
上述实现方式中，第一终端设备通过在能力信息中包括第三指示信息，用于指示第一终端设备的类型，使得网络设备根据接收到的能力信息，可以确定出第一终端设备的类型。从而，网络设备可以根据第一终端设备的类型采用不同的处理方式。例如，若第一终端设备的类型为第一类型(降低性能UE)，则认为第一终端设备支持的带宽为其通过bitmap或其他形式上报的带宽，在第一终端设备需要切换时，将第一终端设备切换至支持降低性 能UE的网络设备中。若第一终端设备的类型为第二类型(例如legacy UE)，则认为第一终端设备的带宽为其通过bitmap或其他形式上报的带宽和100MHz。
第六方面，本申请实施例提供一种通信方法，该方法包括：网络设备从第一终端设备接收能力信息，所述能力信息包括第三指示信息；网络设备根据所述第三指示信息，确定所述第一终端设备的类型为第一类型或者第二类型。
一种可能的实现方式中，网络设备从第一终端设备接收能力信息之前，还包括：向所述第一终端设备发送能力请求消息。
上述实现方式中，第一终端设备通过在能力信息中包括第三指示信息，用于指示第一终端设备的类型，使得网络设备根据接收到的能力信息，可以确定出第一终端设备的类型。从而，网络设备可以根据第一终端设备的类型采用不同的处理方式。例如，若第一终端设备的类型为第一类型(降低性能UE)，则认为第一终端设备支持的带宽为其通过bitmap或其他形式上报的带宽，在第一终端设备需要切换时，将第一终端设备切换至支持降低性能UE的网络设备中。若第一终端设备的类型为第二类型(例如legacy UE)，则认为第一终端设备的带宽为其通过bitmap或其他形式上报的带宽和100MHz。
第七方面，本申请实施例提供一种通信方法，该方法包括：第一网络设备向第二网络设备发送Xn接口建立请求消息，所述Xn接口建立请求消息中包括询问信息，所述询问信息用于询问所述第二网络设备是否支持第一类型的终端设备；第一网络设备从第二网络设备接收Xn接口建立应答消息或者Xn接口建立失败消息；其中，所述Xn接口建立应答消息包括第四指示信息，所述第四指示信息用于指示所述第二网络设备是否支持第一类型的终端设备。
第八方面，本申请实施例提供一种通信方法，该方法包括：第二网络设备从第一网络设备接收Xn接口建立请求消息，所述Xn接口建立请求消息中包括询问信息，所述询问信息用于询问所述第二网络设备是否支持第一类型的终端设备；第二网络设备向第一网络设备发送Xn接口建立应答消息或者Xn接口建立失败消息；其中，所述Xn接口建立应答消息包括第四指示信息，所述第四指示信息用于指示所述第二网络设备是否支持第一类型的终端设备。
该方案中，通过在Xn接口建立应答消息中包括第四指示信息，第一网络设备根据第四指示信息可以获知第二网络设备是否支持第一类型的终端设备。第一网络设备还可以对所述第四指示信息进行存储。当第一网络设备需要对第一类型的终端设备发起切换时，可以根据存储的各网络设备的第四指示信息，确定将第一类型的终端设备切换至哪个目标网络设备。从而，避免将第一类型的终端设备切换至不支持第一类型的网络设备中。
第九方面，本申请实施例提供一种通信装置，该通信装置可以为第一网络设备或者第一网络设备内的元件，例如芯片或者集成电路。该通信装置可以包括：处理单元、发送单元和接收单元。其中，处理单元用于确定第一终端设备的类型为第一类型；发送单元用于发送切换请求消息，所述切换请求消息包括第一指示信息，所述第一指示信息包含所述第一类型的标识信息；接收单元，用于接收切换确认消息或者切换准备失败消息。
一种可能的实现方式中，所述第一指示信息还包含关键值指示信息，所述关键值指示信息用于指示第二网络设备在第一条件下拒绝所述切换。
一种可能的实现方式中，所述接收单元具体用于：接收来自第二网络设备的切换确认 消息，所述第二网络设备支持所述第一类型的终端设备；或者，接收来自第二网络设备的第一切换准备失败消息，所述第一切换准备失败消息包含对应所述第一类型的失败信息，所述第二网络设备不支持所述第一类型的终端设备。
一种可能的实现方式中，所述发送单元具体用于：向第二网络设备发送所述切换请求消息；或者，通过接入和移动性管理功能AMF设备向第二网络设备发送所述切换请求消息。
第十方面，本申请实施例提供一种通信装置，该通信装置可作为第二网络设备。该通信装置可以包括：接收单元和发送单元。其中，接收单元用于接收切换请求消息，所述切换请求消息包括第一指示信息，所述第一指示信息包含第一类型的标识信息，所述第一类型为终端设备的第一类型；或者所述第一类型为第一终端设备的类型；发送单元用于发送切换确认消息或者切换准备失败消息。
一种可能的实现方式中，所述切换请求消息还包括第一终端设备的能力信息，所述第一终端设备的类型为所述第一类型。
一种可能的实现方式中，所述第一指示信息还包含关键值指示信息，所述关键值指示信息用于指示第二网络设备在第一条件下拒绝所述切换。
一种可能的实现方式中，所述接收单元具体用于：接收第一网络设备发送的切换请求消息；或者，通过接入和移动性管理功能AMF设备接收来自第一网络设备的切换请求消息。
第十一方面，本申请实施例提供一种通信装置，该通信装置可以包括：处理单元和发送单元。其中，处理单元用于生成系统消息，所述系统消息包括第二指示信息，所述第二指示信息用于指示第一类型，所述第一类型为终端设备的第一类型；发送单元用于发送所述系统消息。
一种可能的实现方式中，所述系统消息为系统消息块SIB1。
第十二方面，本申请实施例提供一种通信装置，该通信装置可以为第一终端设备或者第一终端设备内的元件，例如芯片或者集成电路。该通信装置可以包括：接收单元和处理单元。其中，接收单元用于接收来自网络设备的系统消息；处理单元用于获取所述系统消息包含的第二指示信息，所述第二指示信息用于指示第一类型，所述第一类型为终端设备的第一类型。
一种可能的实现方式中，所述系统消息为系统消息块SIB1。
一种可能的实现方式中，所述处理单元还用于：根据所述第二指示信息，确定是否驻留在所述网络设备的小区。
一种可能的实现方式中，所述系统消息还包括：所述网络设备支持的频带信息和带宽信息；所述处理单元具体用于：根据所述第二指示信息以及所述网络设备支持的频带信息和带宽信息，确定是否驻留在所述网络设备的小区。
一种可能的实现方式中，所述网络设备为第一终端设备的服务小区的邻区对应的网络设备；该通信装置还包括发送单元，所述发送单元用于：发送所述第二指示信息到所述服务小区对应的网络设备。
第十三方面，本申请实施例提供一种通信装置，该通信装置可以为第一终端设备或者第一终端设备内的元件，例如芯片或者集成电路。该通信装置可以包括：处理单元和发送 单元。其中，处理单元用于生成能力信息，所述能力信息包括第三指示信息，所述第三指示信息用于指示第一终端设备的类型，所述第一终端设备的类型为第一类型或者第二类型；发送单元用于向网络设备发送所述能力信息。
一种可能的实现方式中，该通信装置还包括接收单元，所述接收单元用于从所述网络设备接收能力请求消息。
第十四方面，本申请实施例提供一种通信装置，该通信装置可以包括：接收单元和处理单元。其中，接收单元用于从第一终端设备接收能力信息，所述能力信息包括第三指示信息；处理单元用于根据所述第三指示信息，确定所述第一终端设备的类型为第一类型或者第二类型。
一种可能的实现方式中，该通信装置还包括发送单元，所述发送单元用于向所述第一终端设备发送能力请求消息。
第十五方面，本申请实施例提供一种通信装置，该通信装置可以为第一网络设备或者第一网络设备内的元件，例如芯片或者集成电路。该通信装置可以包括发送单元和接收单元。其中，发送单元用于向第二网络设备发送Xn接口建立请求消息，所述Xn接口建立请求消息中包括询问信息，所述询问信息用于询问所述第二网络设备是否支持第一类型的终端设备；接收单元用于从第二网络设备接收Xn接口建立应答消息或者Xn接口建立失败消息；其中，所述Xn接口建立应答消息包括第四指示信息，所述第四指示信息用于指示所述第二网络设备是否支持第一类型的终端设备。
第十六方面，本申请实施例提供一种通信装置，该通信装置可以为第二网络设备或者第二网络设备内的元件，例如芯片或者集成电路。该通信装置可以包括接收单元和发送单元。其中，接收单元用于从第一网络设备接收Xn接口建立请求消息，所述Xn接口建立请求消息中包括询问信息，所述询问信息用于询问所述第二网络设备是否支持第一类型的终端设备；发送单元用于向第一网络设备发送Xn接口建立应答消息或者Xn接口建立失败消息；其中，所述Xn接口建立应答消息包括第四指示信息，所述第四指示信息用于指示所述第二网络设备是否支持第一类型的终端设备。
第十七方面，本申请实施例提供一种通信装置，包括至少一个存储器和至少一个处理器，所述至少一个存储器用于存储计算机程序，所述至少一个处理器用于从所述至少一个存储器中调用并运行所述计算机程序，使得所述至少一个处理器运行所述计算机程序执行如第一方面、第二方面、第三方面、第六方面、第七方面、第八方面中任一项所述的通信方法。
第十八方面，本申请实施例提供一种通信装置，包括至少一个存储器和至少一个处理器，所述至少一个存储器用于存储计算机程序，所述至少一个处理器用于从所述至少一个存储器中调用并运行所述计算机程序，使得所述至少一个处理器运行所述计算机程序执行如第四方面、第五方面中任一项所述的通信方法。
第十九方面，本申请实施例提供一种计算机存储介质，所述计算机存储介质包括计算机程序，所述计算机程序用于实现如第一方面、第二方面、第三方面、第六方面、第七方面、第八方面中任一项所述的通信方法，或者，实现如第四方面、第五方面中任一项所述的通信方法。
第二十方面，本申请实施例提供一种芯片或者芯片系统，该芯片或者芯片系统包括至 少一个处理器和通信接口，通信接口和至少一个处理器通过线路互联，至少一个处理器用于运行计算机程序或指令，以进行如第一方面、第二方面、第三方面、第六方面、第七方面、第八方面中任一项所述的通信方法，或者，如第四方面、第五方面中任一项所述的通信方法。
其中，芯片中的通信接口可以为输入/输出接口、管脚或电路等。
在一种可能的实现中，本申请中上述描述的芯片或者芯片系统还包括至少一个存储器，该至少一个存储器中存储有指令。该存储器可以为芯片内部的存储单元，例如，寄存器、缓存等，也可以是该芯片的存储单元(例如，只读存储器、随机存取存储器等)。
第二十一方面，本申请实施例提供一种通信系统，该通信系统包括如第九方面任一项所述的通信装置和如第十方面任一项所述的通信装置；
或者，该通信系统包括如第十一方面任一项所述的通信装置和如第十二方面任一项所述的通信装置；
或者，该通信系统包括如第十三方面任一项所述的通信装置和如第十四方面任一项所述的通信装置；
或者，该通信系统包括如第十五方面任一项所述的通信装置和如第十六方面任一项所述的通信装置。
附图说明
图1A为本申请实施例可能涉及的一种网络架构的示意图；
图1B为本申请实施例可能涉及的另一种网络架构的示意图；
图2为本申请实施例中降低性能UE和legacy网络设备支持带宽的示意图；
图3为本申请一个实施例提供的通信方法的流程示意图；
图4为本申请一个实施例提供的通信方法的流程示意图；
图5为本申请一个实施例提供的通信方法的流程示意图；
图6为本申请一个实施例提供的通信方法的流程示意图；
图7为本申请一个实施例提供的ANR场景的交互过程示意图；
图8为本申请一个实施例提供的通信方法的流程示意图；
图9为本申请一个实施例提供的通信方法的流程示意图；
图10为本申请一个实施例提供的网络设备的结构示意图；
图11为本申请一个实施例提供的终端设备的结构示意图；
图12为本申请一个实施例提供的网络设备的结构示意图；
图13为本申请一个实施例提供的终端设备的结构示意图。
具体实施方式
本申请实施例的方案可应用于各种通信系统。具体的，该通信系统可以是例如：全球移动通讯(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-A(LTE advanced)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、通用移动通信系统(universal mobile telecommunication system，UMTS)等、第五代移动通信技术(5th generation mobile networks，简称5G)通信系统、新空口(new radio，NR)通信系统以及未来的第六代移动通信技术(6th generation mobile networks，简称6G)通信系统甚至更高级的通信系统等。
下面结合图1A和图1B描述本申请实施例可能涉及的网络架构。需要说明的是，本申请实施例描述的网络架构以及业务场景是为了说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定。本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
图1A为本申请实施例可能涉及的一种网络架构的示意图。如图1A所示，该网络架构包括：网络设备和终端设备。终端设备可以通过小区选择流程驻留在网络设备的小区中。
图1B为本申请实施例可能涉及的另一种网络架构的示意图。如图1B所示，该网络架构包括：接入和移动性管理功能(access and mobility management function，AMF)、第一网络设备、第二网络设备和终端设备。第一网络设备和第二网络设备之间通过Xn接口(Xn interface)通信，AMF与网络设备之间通过NG接口(NG interface)通信。处于连接态的终端设备从第一网络设备的覆盖范围移动到第二网络设备的覆盖范围时，为了保证终端设备通信的连续性和服务的质量，通信系统可以将该终端设备与原小区(第一网络设备的小区)的通信链路转移到新的小区(第二网络设备的小区)上。上述过程被称为切换。切换可分为基于Xn接口的切换和基于NG接口的切换。也就是说，切换可在两个网络设备之间直接进行。在Xn接口不能建立时，两个网络设备还可以通过AMF进行切换信令的交互。
本申请实施例中的网络设备可以是一种将终端设备接入到无线网络的设备。该设备可以是基站，或者各种无线接入点，或者可以是指接入网中在空中接口上通过一个或多个扇区与终端设备进行通信的设备。基站可用于将收到的空中帧与IP分组进行相互转换，作为终端设备与接入网的其余部分之间的路由器，其中接入网的其余部分可包括网际协议(IP)网络。基站还可协调对空中接口的属性管理。例如，基站可以是全球移动通讯(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)，或者中继站或接入点，还可以是5G网络中的基站gNB,NR网络中的收发点(transmission reception point,TRP)或者下一代节点B(generation nodeB，gNB)，或者未来其他的网络系统中的基站等等，在此并不限定。
本申请实施例中的终端设备可以是无线终端也可以是有线终端，无线终端可以是指向用户提供语音和/或其他业务数据连通性的设备，具有无线连接功能的手持式设备、或连接到无线调制解调器的其他处理设备。无线终端可以经无线接入网与一个或多个核心网进行通信，无线终端可以是移动终端，如移动电话(或称为“蜂窝”电话)和具有移动终端的计算机，例如，可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动装置，它们与无线接入网交换语言和/或数据。例如，个人通信业务(personal communication service， PCS)电话、无绳电话、会话发起协议(session initiation protocol，SIP)话机、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)等设备。无线终端也可以称为系统、订户单元(subscriber Unit)、订户站(subscriber station)，移动站(mobile station)、移动台(mobile)、远程站(remote station)、远程终端(remote terminal)、接入终端(access terminal)、用户终端(user terminal)、用户代理(user agent)、用户设备(user device or user equipment)，具有网络接入功能的传感器，在此不作限定。
随着通信协议的演进以及应用场景的多样化，终端设备的类型也出现多种。例如，3GPP在Release 17中提出的新研究领域“对降低性能的NR设备的支持”，是一种支持较窄的带宽和较低的峰值数据速率场景的功能，主要为高端机器型态通讯(machine type communication，MTC)设备提供轻量级通信(lightweight communications)。适用于该场景的能力较弱的终端设备可以称为降低性能UE(reduced capability UE)或者低能力UE。该类设备主要包括：可穿戴设备、监控摄像头、工业传感器等。
为了描述方便，本申请实施例中将能力较强的终端设备称为传统UE，也可以称为normal/legacy UE。与legacy UE相比，降低性能UE一种低成本、低复杂度且更为节能的终端设备的类型。终端设备的能力包括下述的一种或多种：最大传输带宽、传输速率、可靠性、时延容忍度、天线数量或续航时间等。不同类型的终端设备的能力有所不同。示例性的，本申请实施例中，降低性能UE具有如下特征中的一个或多个：
(1)相比于legacy UE，降低性能UE支持较窄的带宽，所述较窄的带宽为低于预定阈值的带宽。可选的，所述阈值为100MHz。一种类型支持最大20MHz带宽，另一种类型支持最大5MHz带宽。需要说明的是，上述对降低性能UE的分类仅为示例性说明，而不作限定。
(2)相比于legacy UE，降低性能UE支持降低的峰值数据速率，例如一般为5～10Mb/s。
(3)相比于legacy UE，在相同子载波间隔(sub-carrier space，SCS)和支持一定物理资源块(physical resource block，RRB)情况下，降低性能UE所支持的带宽有所减小。例如：假设支持物理资源块为24个，子载波间隔为15kHz，则降低性能UE支持5MHz RF带宽，该带宽小于Release 15版本中的legacy UE的带宽。Release 15版本中的legacy UE支持100MHz带宽。
目前的NR协议(Release 15版本协议)中，终端设备通过含有10个比特(bit)位的位图(bit map)向网络设备上报自身支持的上下行带宽。10个bit位分别对应终端设备是否支持带宽5MHz、10MHz、15MHz、20MHz、25MHz、30MHz、40MHz、50MHz、60MHz、80MHz。按照目前的协议要求，所有的终端设备均需支持100MHz带宽。因此，尽管在终端设备上报的bit map中不存在表示是否支持100MHz带宽的bit位，网络设备也会均默认终端设备支持100MHz带宽。也就是说，网络设备认为终端设备支持的带宽为该终端设备在bit map中上报的带宽和100MHz。
对于降低性能UE而言，降低性能UE无法支持100MHz，仅支持bit map中上报的带宽。因此，若降低性能UE工作于目前不支持NR Light的网络设备，网络设备会因默认此类UE支持100MHz带宽而高估降低性能UE的能力。网络设备可能因默认降低能力UE支持100MHz而允许其工作与此网络中并为其分配资源，将可能导致降低性能UE无法在 所被分配的资源上正常工作。故而，针对降低性能UE，需要对网络设备进行改进，使得网络设备能够支持降低性能UE。
为了描述方便，本申请实施例中将不支持NR Light的网络设备称为“legacy/normal网络设备”，或者称为“不支持降低性能UE的网络设备”。legacy网络设备会默认所有终端设备支持的带宽为该终端设备在bit map中上报的带宽和100MHz。本申请实施例将支持降低性能UE的网络设备称为“支持降低性能UE的网络设备”。能够理解，支持降低性能UE的网络设备可以通过终端设备上报的能力信息识别降低性能UE并掌握终端设备的真实能力情况。也就是说，支持降低性能UE的网络设备针对降低性能UE，认为其带宽为其上报的带宽，上报带宽的方法可以包括通过原有的bit map上报或通过其他形式上报；支持降低性能UE的网络设备针对legacy UE，认为其带宽为其在bit map中上报的带宽和100MHz；或者，支持降低性能UE的网络设备针对legacy UE，认为其带宽为其通过bit map或通过其他形式上报的带宽以及100M。
基于图1A和图1B所示的网络架构，在多种业务场景中，按照目前协议实现，降低性能UE有可能会驻留在legacy网络设备中，或者，降低性能UE有可能会被切换至legacy网络设备中。图2为本申请实施例中降低性能UE和legacy网络设备支持带宽的示意图。如图2所示，legacy网络设备因默认降低性能UE支持100MHz的带宽，而有可能为此类终端设备分配降低性能UE可能无法支持的上下行资源。若降低性能UE驻留在legacy网络设备中，或者被切换至legacy网络设备中，legacy网络设备默认降低性能UE支持100MHz，会错误的判断降低性能UE的能力。例如：legacy网络设备可能会给降低性能UE分配它无法使用的带宽部分(Band Width Part，BWP)，比如为降低性能UE分配图2中所示的BWP1、BWP2、BWP3，导致降低性能UE无法正常工作。
下面结合几种可能的业务场景分别进行描述。
(1)小区选择场景。基于图1A所示的网络架构，终端设备从开机或者盲区进入网络设备的覆盖区时，将寻找公共陆地移动网(public land mobile network，PLMN)允许的频点，并选择一个合适的小区进行驻留，这个过程被称为小区选择。小区选择的目的是使终端设备尽快驻留到小区，使得终端设备可以接收PLMN广播的系统消息，并在小区内发起随机接入过程，接收网络侧的寻呼以及接收小区广播业务。
小区选择流程如下：终端设备开机后，首先要选择一个合适PLMN，然后根据确定的PLMN进行小区选择。小区选择过程包括小区搜索、系统消息接收、小区选择以及小区驻留4个部分。在该PLMN上选择满足驻留条件的小区后，才能在该PLMN上进行注册。终端设备通过小区搜索与小区取得频率和符号同步(下行同步)，获取下行帧的起始位置，并确定小区的物理小区标识(physical-layer cell identity，PCI)。完成小区搜索后，终端设备接收此小区的系统消息。终端设备通过读取系统消息获得网络接入层和非接入层的公共信息，以便终端设备在发起呼叫之前了解网络的配置情况，从而采取适当的方式发起呼叫。终端设备可从系统消息中读取一部分基站能力信息，例如：目标基站所支持的带宽、initial BWP等。基于以上信息，终端设备结合自身能力，判断自身能力是否能够支持驻留于此基站。接下来终端设备基于测量结果选择满足S准则的小区进行驻留。小区驻留使终端设备可以接受PLMN广播的系统信息，在小区内发起随机接入过程，接收网络的寻呼以及接收小区广播业务。
可见，现有的小区选择流程中，终端设备无法获知网络设备是否支持降低性能UE，因此，降低性能UE按照上述现有流程进行小区选择时，有可能会选择驻留到legacy网络设备中，从而导致降低性能UE无法正常工作。
(2)切换场景。基于图1B所示的网络架构，处于连接态的终端设备从第一网络设备的覆盖范围移动到第二网络设备的覆盖范围时，为了保证终端设备通信的连续性和服务的质量，通信系统可以将该终端设备与原小区(第一网络设备的小区)的通信链路转移到新的小区(第二网络设备的小区)上。上述过程被称为切换。切换过程由网络设备控制，网络设备向终端设备下发相关配置信息，终端设备根据配置信息完成切换测量并基于测量上报触发条件将测量结果上报给网络设备，在网络设备的控制下完成切换过程，保证不间断的通信业务。
基于Xn接口的切换流程如下：源网络设备(例如第一网络设备)根据终端设备上报的测量结果及其他因素做出切换决定。源网络设备选择目标网络设备(例如第二网络设备)，并向该目标网络设备发送切换请求消息。目标网络设备基于得到的信息判断是否允许切换；若允许切换，则向源网络设备回复切换确认消息；若不允许切换，则向源网络设备回复切换准备失败消息。
基于NG接口的切换流程与基于Xn接口的切换流程类似，不同之处在于，源网络设备和目标网络设备之间的切换信令需要经过核心网设备AMF的转发。
现有的切换流程中，源网络设备向目标网络设备发送切换请求消息时，并不确定目标网络设备是否支持降低性能UE，即，并不确定目标网络设备是legacy网络设备还是支持降低性能UE的网络设备。因此，当待切换的终端设备为降低性能UE时，按照现有的切换流程，源网络设备有可能将降低性能UE切换至legacy网络设备中，从而导致降低性能UE无法正常工作。
(3)ANR场景。为了减轻网络管理人员手动管理邻区关系(neighboring cell relation，NCR)的负担，在3GPP协议Release15版本中被引入自动邻区关系(automatic neighbor relation，ANR)功能。对于配置了ANR功能的小区，网络设备指示其服务小区的终端设备检测新的目标小区，并读取目标小区的全局和物理标识(即，global and physical IDs，例如：NR CGI/NR PCI，ECGI/PCI)。终端设备读取的邻区信息将通过全球小区识别码程序报告(cell global identifier procedure report，CGI procedure report)上报给网络设备，网络设备将邻区信息存入至服务小区的邻区关系表(neighbour cell relation table，NCRT)中。从而避免网络设备在增加邻区关系中可能存在导频泄漏等造成邻区误增，影响系统的质量和稳定性的判决。
结合图1B所示的网络架构，假设终端设备驻留在第一网络设备的小区，即第一网络设备的小区为终端设备的服务小区。当终端设备检测到第二网络设备的小区时，将检测到的小区的全局和物理标识等(即，global and physical IDs，例如，NR CGI/NR PCI，ECGI/PCI)上报给第一网络设备，这样，第一网络设备可根据终端设备上报的信息对邻区关系进行检测、创建、删除等。进而，第一网络设备在后续的切换流程中，可以基于这些邻区关系选择目标网络设备。在ANR测量上报过程中，终端设备会上报PCI所对应的CGI procedure report，其中包括CGI，PLMN ID，跟踪区域码(tracking area code，TAC)等。
可见，现有ANR流程中，第一网络设备从终端设备接收到的CGI procedure report中 没有关于其他网络设备的小区是否支持降低性能UE的信息。也就是说，第一网络设备根据CGI procedure report中的信息并无法获知第二网络设备是legacy网络设备还是支持降低性能UE的网络设备。因此，在后续的切换流程中，第一网络设备有可能会将降低性能UE切换至legacy网络设备中，从而导致降低性能UE无法正常工作。
为了解决上述问题中的至少一个，本申请实施例提供一种通信方法，能够避免降低性能UE驻留到legacy网络设备中，或者避免降低性能UE切换至legacy网络设备中。
下面结合附图以具体的几个实施例对本申请的技术方案进行详细说明。下面这几个具体的实施例可以相互结合，对于相同或相似的概念或过程在某些实施例中不再赘述。
图3为本申请一个实施例提供的通信方法的流程示意图。本实施例的通信方法可应用于基于Xn接口的切换场景中。如图3所示，本实施例的方法包括：
S301：第一网络设备确定第一终端设备的类型为第一类型。
本实施例中，第一网络设备也可以称为源网络设备，第二网络设备也可以称为目标网络设备。第一终端设备为待切换的终端设备。本实施例的应用场景中，第一终端设备处于连接态，第一网络设备的某一小区为第一终端设备当前的服务小区。第一网络设备基于第一终端设备上报的测量报告及其他信息，做出切换决定。本实施例中假设第一网络设备将第二网络设备作为目标网络设备，即，第一网络设备尝试将第一终端设备切换至第二网络设备的小区中。
本申请中涉及多个类型的终端设备，第一类型为多个类型中的一个类型。应理解，对于终端设备的类型的划分方式可以有多种。
一个示例中，终端设备的多个类型可以是根据终端设备的能力划分的。其中，终端设备的能力包括下述的一种或多种：最大传输带宽、传输速率、可靠性、时延容忍度、天线数量或续航时间等。不同类型的终端设备的能力有所不同。
可选的，终端设备的多个类型可以包括第一类型和第二类型。其中，第一类型的终端设备的能力低于第二类型的终端设备的能力。示例性的，第一类型的终端设备可以为降低性能UE，第二类型的终端设备为能力高于降低性能UE的终端设备，例如第二类型的终端设备可以为legacy UE。由前面的描述可知，legacy UE在最大传输带宽、传输速率等方面的能力高于降低性能UE。
S302：第一网络设备向第二网络设备发送切换请求消息(HANDOVER REQUEST message)，所述切换请求消息包括第一指示信息，所述第一指示信息包含所述第一类型的标识信息。
S303：第二网络设备向第一网络设备发送切换确认消息(HANDOVER REQUEST ACKNOWLEDGE message)或者切换准备失败消息(HANDOVER PREPARATION FAILURE message)。
现有的切换流程中，第一网络设备向第二网络设备发送切换请求消息(HANDOVER REQUEST message)。其中，切换请求消息中包括待切换终端设备正在进行业务的配置信息和进展信息。例如，切换请求消息包括下述信息中的一种或者多种：当前服务质量流(QoS flow)的进展，已建立的协议数据单元(protocol data unit，PDU)会话(sessions)及相关配置和关联的数据无线承载(data radio bearer，DRB)，终端设备的安全能力(UE Security  Capabilities IE)和接入层安全信息(AS Security Information)，等。这样，第二网络设备可以根据切换请求消息中携带的信息来判断是否同意切换。
一个示例性中，切换请求消息中可以包括第一终端设备的能力信息。其中，能力信息可以包括下述中的一种或者多种：最大传输带宽，传输速率，可靠性，时延容忍度，天线数量，或续航时间等。另一个示例中，切换请求消息中可以包括第一终端设备的能力标识或者能力集合的标识。能力标识或者能力集合的标识用于指示终端设备的能力信息。这样，第二网络设备可以根据第一终端设备的能力信息，为第一终端设备准备切换资源，或者确定是否同意切换。
本实施例中，第一终端设备的类型为第一类型，为了避免将第一终端设备切换至不支持第一类型的网络设备中，第一网络设备发送的切换请求消息(HANDOVER REQUEST message)中包括第一指示信息。第一指示信息包含所述第一类型的标识信息。其中，第一类型的标识信息是指能够用于标识第一类型的任意信息。一个示例中，第一类型的标识信息可以为第一类型的名称。例如，当第一类型的终端设备为降低性能UE时，第一类型的标识信息可以为reduced capability UE。另一个示例中，不同的类型可以对应有不同的索引，这样，第一类型的标识信息可以为第一类型对应的索引。可选的，所述切换请求消息中可以包含所述待切换的终端设备正在进行的业务的配置及进展信息，如当前服务质量流(QoS Flow)的进展，PDU会话(PDU Sessions)及相关配置和关联的数据无线承载(DRB)中的一个或多个；和/或，所述切换请求消息可以包含该终端设备的相关信息字段，例如：终端设备的安全能力(UE Security Capabilities)字段、终端设备的接入层安全信息(AS Security Information)字段等，上述字段用于为终端设备在目标网络设备下激活安全信息。
通过在切换请求消息中携带第一指示信息，用于指示第一类型的标识信息，使得第二网络设备在接收到切换请求消息时，可以根据第一指示信息确定出待切换的终端设备的类型为第一类型。进而，第二网络设备可以根据自身是否支持该类型的终端设备来判断是否同意切换。例如，若第二网络设备不支持第一类型的终端设备，则拒绝切换，向第一网络设备发送携带失败原因(failure cause value)的切换准备失败消息。若第二网络设备支持第一类型的终端设备，则可以按照现有的切换流程继续进行(例如，根据切换请求消息中的其他信息判断是否同意切换)，并在最终确定同意切换时，向第一网络设备发送切换确认消息。
一种可能的实现方式中，若第二网络设备不支持第一类型的终端设备，则向第一网络设备发送第一切换准备失败消息。一个示例中，所述第一切换准备失败消息包含对应所述第一类型的失败信息。例如，第一切换准备失败消息中携带的失败原因(failure cause value)指示的是由于不支持第一类型导致的切换失败。另一个示例中，所述第一切换准备失败消息包括1比特的信息域。该信息域的不同状态可以指示失败原因，例如该信息域为1表示由于不支持第一类型导致切换失败，该信息域为0表示由于其他原因导致切换失败。
一种可能的实施方式中，第一指示信息中还可以包括关键值指示信息，所述关键值指示信息用于指示第二网络设备在第一条件下拒绝所述切换。可选的，第一条件可以为第二网络设备不支持第一类型的终端设备。也就是说，若第二网络设备不支持或者无法识别第一类型的终端设备，则第二网络设备拒绝本次切换，向第一网络设备发送切换准备失败消 息。其中，这里的“不支持”可以包括两种情况。第一种情况为第二网络设备可以识别第一类型的标识信息，但是第二网络设备不支持第一类型的终端设备。第二种情况为第二网络设备无法识别第一类型的标识信息。
应理解，本实施例中，第一指示信息中携带第一类型的标识信息和关键值指示信息的方式可以有多种。下面以一种可能的实施方式为例进行介绍。
示例性的，可以在切换请求消息(HANDOVER REQUEST message)中添加一个新的IE或字段(field)，例如，IE或字段的名称为reduced capability UE。该IE或字段作为第一指示信息。该IE或字段包括第一类型的标识信息和关键值指示信息。可选的，该IE或字段的定义方式参照3GPP RAN 3协议中定义的方式。该IE或字段所对应的属性如表1所示。参见表1，该IE或字段的属性可以包括：名称属性、存在(Presence)形式，关键值属性。其中IE或字段的名称即第一类型的标识信息。该IE或字段的Presence形式为必选(mandatory)或可选(Optional)。该IE或字段的关键值可以取值为“reject”或者“ignore”，即关键值指示信息，表示第二网络设备无法识别该IE或字段或无法识别该IE或字段携带的标识信息时采取拒绝行为还是忽略行为。
另外，参见表1，该IE或字段中还可以包括其他更多的属性，例如：范围属性、类型属性、重要性属性等。表1中“XXXX”表示属性的取值，本实施例对于其他属性的取值不做限定。例如：存在属性(Presence)可以被定义为“O”(Optional)，表示切换请求消息(HANDOVER REQUEST message)可选包含该IE或字段。重要性属性(Criticality)被定义为“Yes”，表示该IE或字段的重要性。等等。
对于本实施例的切换场景而言，假设当前待切换的第一终端设备为降低性能UE，则第一网络设备生成切换请求消息(HANDOVER REQUEST message)时，可以将该IE或字段的关键值设置为“reject”。这样，第二网络设备接收到切换请求消息后，若第二网络设备无法识别该IE或字段(例如无法识别该IE或字段的名称，或者无法识别该IE或字段的名称所对应的id名称，或者无法识别该IE或字段所指向的type，该情况下说明第二网络设备为legacy网络设备)，则第二网络设备拒绝切换行为，并向第一网络设备发送切换失败信息(HANDOVER PREPARATION FAILURE message)。若第二网络设备可以识别该IE或字段(该情况下说明第二网络设备为支持降低性能UE的网络设备)，则第二网络设备可以按照现有切换流程继续执行，并在最终确定同意切换时，向第一网络设备发送切换确认消息(HANDOVER REQUEST ACKNOWLEDGE message)。因此，可以有效避免第一网络设备将降低性能UE切换至legacy网络设备中。
表1
Figure PCTCN2020077500-appb-000001
本实施例中，第一网络设备是当前为第一终端设备提供服务的网络设备，也就是说，第一网络设备支持第一类型的终端设备(降低性能UE)。第一网络设备还可以为第二终端设备提供服务，第二终端设备为第二类型的终端设备(例如legacy UE)。也就是说，第一网络设备还可以支持第二类型的终端设备。
本实施例提供的通信方法，包括：第一网络设备确定第一终端设备的类型为第一类型，第一网络设备向第二网络设备发送切换请求消息，所述切换请求消息包括第一指示信息，第一指示信息包含所述第一类型的标识信息，这样，第二网络设备接收到切换请求消息后，在第二网络设备不支持所述第一类型的终端设备时，向第一网络设备发送切换准备失败消息，在第二网络设备支持所述第一类型的终端设备时，按照现有切换流程继续进行，并在最终确定同意切换时向第一网络设备发送切换确认消息。通过上述过程，可以避免将第一类型的终端设备切换至不支持第一类型的网络设备中。
图4为本申请一个实施例提供的通信方法的流程示意图。本实施例的通信方法可应用于基于NG接口的切换场景中。如图4所示，本实施例的方法包括：
S401：第一网络设备确定第一终端设备的类型为第一类型。
S402：第一网络设备向AMF设备发送切换要求消息(HANDOVER REQUIRED message)，所述切换要求消息包括第一指示信息，所述第一指示信息包含所述第一类型的标识信息。
S403：AMF设备向第二网络设备发送切换请求消息(HANDOVER REQUEST message)，所述切换请求消息包括所述第一指示信息。
S404：第二网络设备向AMF设备发送切换确认消息(HANDOVER REQUEST ACKNOWLEDGE message)或者切换失败消息(HANDOVER FAILURE message)。
S405：AMF设备向第一网络设备发送切换命令消息(HANDOVER COMMAND message)或者切换准备失败消息(HANDOVER PREPARATION FAILURE message)。
本实施例与图3所示的实施例类似，不同之处在于本实施例应用于基于NG接口的切换场景中，即第一网络设备和第二网络设备之间的切换信令通过AMF设备的转发。
下面以第一终端设备为降低性能UE为例进行描述。
本实施例中，为了避免降低性能UE被切换至legacy网络设备，将表1所示的新IE或字段作为第一指示信息添加至可对AMF透传的第五指示信息中，第五指示信息例如可以为Handover Required Transfer IE。第五指示信息被包含在第一网络设备发送给AMF的切换要求消息(HANDOVER REQUIRED message)中。由于第五指示信息对于AMF来说是一个透明的IE，AMF不对第五指示信息进行解读，直接将其包含在切换请求消息(HANDOVER REQUEST message)中发送给第二网络设备。第二网络设备解读第五指示信息中包含的全部内容。若第二网络设备可以识别该第一指示信息(例如，可以识别表1中新IE/字段，或者可以识别新IE/字段携带的标识信息)，则表示第二网络设备为支持降低性能UE的网络设备，则第二网络设备按现有协议继续进行，并在最终确定同意切换时，向AMF发送切换确认消息(HANDOVER REQUEST ACKNOWLEDGE message)。若第二网络设备无法识别该第一指示信息(例如，无法识别表1中新IE/字段，或者无法识别新IE/字段携带的标识信息)，则表示第二网络设备为legacy网络设备，不支持降低性能UE，则第二网络设备拒绝切换行为，并向AMF发送切换失败消息(HANDOVER FAILURE message)，切换失败消息中携带失败原因(failure cause value)。
若AMF接收到来自于第二网络设备的切换确认消息(HANDOVER REQUEST ACKNOWLEDGE message)，则向第一网络设备发送切换命令消息(HANDOVER  COMMAND message)，以使第一网络设备获知第二网络设备已准备好切换资源，可进行切换。若AMF接收到来自于第二网络设备的切换失败消息(HANDOVER FAILURE message)，则向第一网络设备发送切换准备失败消息(HANDOVER PREPARATION FAILURE message)，以通知第一网络设备切换准备已失败。
若第一网络设备接收到AMF发送的切换命令消息(HANDOVER PREPARATION FAILURE message)，则第一网络设备在切换完成后向AMF回复切换通知消息(HANDOVER NOTIFY message)，以告知AMF终端设备已被第二网络设备的小区识别，切换完成。
本实施例提供的通信方法，包括：第一网络设备确定第一终端设备的类型为第一类型，第一网络设备向AMF发送切换要求消息，切换要求消息中包括第一指示信息，第一指示信息包含所述第一类型的标识信息，并且，第一指示信息被包含在可对AMF透传的第五指示信息中，以使AMF不对第一指示信息进行解读，直接将其包含在切换请求消息中发送给第二网络设备。第二网络设备接收到切换请求消息后，在第二网络设备不支持所述第一类型的终端设备时，向AMF发送切换失败消息，并包含失败原因(failure cause value)；AMF向第一网络设备发送切换准备失败消息，并包含失败原因(failure cause value)或者指示是否由于不支持第一类型导致切换失败。在第二网络设备支持所述第一类型的终端设备时，按照现有切换流程继续进行，并在最终确定同意切换时向AMF发送切换确认消息；AMF向第一网络设备发送切换命令消息。通过上述过程，可以避免将第一类型的终端设备(降低性能UE)切换至不支持第一类型的网络设备(legacy网络设备)中。
图5为本申请一个实施例提供的通信方法的流程示意图。本实施例的通信方法可应用于小区选择场景中。如图5所示，本实施例的方法包括：
S501：网络设备生成系统消息，所述系统消息包括第二指示信息，所述第二指示信息用于指示第一类型，所述第一类型为终端设备的多个类型中的类型。
S502：网络设备发送所述系统消息，相应的，第一终端设备接收所述系统消息。
S503：第一终端设备获取所述系统消息包含的第二指示信息。
本实施例的应用场景中，第一终端设备处于空闲态，例如第一终端设备可以是正在进行小区选择或小区重选。
在此场景中，第一终端设备完成小区搜索后，第一终端设备与小区取得下行同步，第一终端设备可以接收该小区的网络设备广播的系统消息。网络设备广播的系统消息是小区级别的信息。系统消息可以包括主信息块(master information block，MIB)和系统消息块(system information blocks，SIB)，如SIB1、SIB2等。其中，MIB包含一些数量有限但最重要也最频繁发送的参数，终端设备必须使用这些参数来获取其他的系统消息。例如，MIB中可以包括下行系统带宽、PHICH配置、SFN等。不同的SIB中可用于传输不同功能相关的系列参数。其中，SIB1中包含用来判断某小区是否适合用于小区选择的参数，SIB2中包含了公共的无线资源配置信息，等。
可选的，本实施例中的第二指示信息可以包含在SIB1中。
本实施例中，第二指示信息用于指示第一类型，其中，第一类型为终端设备的多个类型中的类型。例如，第一类型的终端设备可以为降低性能UE。换句话说，第二指示信息 指示的是网络设备支持第一类型的终端设备，或者，第二指示信息指示的是网络设备是否支持第一类型的终端设备。例如，当第一类型的终端设备为降低性能UE时，第二指示信息指示的是网络设备支持降低性能UE，或者第二指示信息指示的是网络设备支持或者是否支持降低性能UE。
应理解，在系统消息中携带第二指示信息的方式有多种，本实施例对此不作具体限定，只要第二指示信息能够指示第一类型即可。
一种可能的实施方式中，可以在SIB1中添加新的IE或字段，该IE或字段的属性可以是枚举(ENUMERATED{XXX})类型，例如可以枚举{ture/false},也可以枚举{supported/notSupported}，或者，也可以不使用枚举，本实施例对此不作具体限定。一个示例中，假设IE或字段的名称为ReducedCapabilityUE-Support，添加的ASN.1如下。对于支持降低性能UE的网络设备，可以在SIB1中增加下述IE或字段，用于指示网络设备指示降低性能UE。对于legacy网络设备，其SIB1中不包含下述IE或字段。
ReducedCapabilityUE-Support··········ENUMERATED{true}············OPTIONAL
一种可选的设计中，终端设备确定网络设备支持降低性能UE，所述SIB1中存在上述IE或者字段。也可以说，终端设备根据所述SIB1中存在上述IE或者字段，确定所述网络设备支持降低性能UE。否则，确定所述网络设备不支持降低性能UE。
终端设备接收到SIB1后，若SIB1中存在此IE或字段，则表示网络设备支持降低性能UE，即该网络设备为支持降低性能UE的网络设备。若SIB1中不存在此IE或字段，则表示网络设备不支持降低性能UE，即该网络设备为legacy网络设备。
或者，
一种可选的设计中，终端设备确定网络设备支持降低性能UE，所述SIB1中存在上述IE或者字段，并且上述IE或者字段中的指示信息为预设信息(例如true或者supported)。也可以说，终端设备根据所述SIB1中存在上述IE或者字段，并且上述IE或者字段中的指示信息为预设信息，确定所述网络设备支持降低性能UE。否则，确定所述网络设备不支持降低性能UE。
终端设备接收到SIB1后，若SIB1中存在此IE或字段，则根据该IE或字段中的指示信息来判断网络设备是否支持降低性能UE。例如，若IE或字段中的指示信息为true或者supported，则确定网络设备为支持降低性能UE的网络设备；若IE或字段中的指示信息为false或者notSupported，则确定网络设备为legacy网络设备。
一种可选的设计中，终端设备确定网络设备支持降低性能UE，所述SIB1中存在上述IE或者字段，并且上述IE或者字段指示所述网络设备支持的终端设备的类型包括第一类型。也可以说，终端设备根据所述SIB1中存在上述IE或者字段，并且上述IE或者字段指示所述网络设备支持的终端设备的类型包括第一类型，确定网络设备支持降低性能UE。否则，确定网络设备不支持降低性能UE。
另一种可能的实施方式中，还可以在SIB1中增加新的IE或字段，假设IE或字段的名称为UEType-Supported，该IE或字段中可以列举网络设备支持的一个或者多个终端设备的类型。这样，终端设备接收到SIB1后，通过对SIB1进行解析，可以获知网络设备支持的一个或者多个终端设备的类型。
又一种可能的实施方式中，还可以通过比特位图(bitmap)来指示网络设备支持或者 不支持哪些终端设备类型。例如，以终端设备的类型包括第一类型和第二类型为例，可以采用2个bit的bitmap，2个bit位分别对应网络设备是否支持第一类型、第二类型的终端设备。或者，以终端设备的类型包括第一类型和第二类型为例，可以采用1个bit的IE或字段表示对应网络设备是否支持第一类型的终端设备，若支持则此bit为1，不支持为0。
S504：第一终端设备根据所述第二指示信息，确定是否驻留在所述网络设备的小区。
当第一终端设备为降低性能UE时，第一终端设备根据第二指示信息可以确定出网络设备是否支持降低性能UE，进而确定是否驻留在该网络设备的小区；若不支持，将把此小区视为禁止的(barred)，即禁止驻留在该小区。进一步，所述第一终端设备的后续行为按现有协议进行。
一种可选的设计中，终端设备确定驻留在所述网络设备的小区，所述SIB1中存在上述IE或者字段。也可以说，终端设备根据所述SIB1中存在上述IE或者字段，确定驻留在所述网络设备的小区。否则，确定不驻留在所述网络设备的小区。
一个示例中，当新增IE或字段用于指示第一类型时，若SIB1中不存在上述新增IE或字段，则说明该网络设备不支持降低性能UE，因此确定不驻留在所述网络设备的小区。若SIB1中存在上述新增IE或字段，则说明该网络设备支持降低性能UE，因此，可以按照现有流程继续判断是否满足其他的小区选择条件，在所有条件都满足的情况下，确定驻留在该网络设备的小区。
一种可选的设计中，终端设备确定驻留在所述网络设备的小区，所述SIB1中存在上述IE或者字段，并且上述IE或者字段中的指示信息为预设信息(例如true或者supported)。也可以说，终端设备根据所述SIB1中存在上述IE或者字段，并且上述IE或者字段中的指示信息为预设信息，确定驻留在所述网络设备的小区。否则，确定不驻留在所述网络设备的小区。
另一个示例中，当新增IE或字段用于指示是否支持第一类型的终端设备时，若SIB中存在该新增IE或字段，并且该新增IE或字段中的指示信息为false或者notSupported，则确定网络设备不支持降低性能UE，因此确定不驻留在所述网络设备的小区。若新增IE或字段中的指示信息为true或者supported，则确定网络设备为支持降低性能UE的网络设备，可以按照现有流程继续判断是否满足其他的小区选择条件，在所有条件都满足的情况下，确定驻留在该网络设备的小区。
一种可选的设计中，终端设备确定驻留在所述网络设备的小区，所述SIB1中存在上述IE或者字段，并且上述IE或者字段指示所述网络设备支持的终端设备的类型包括第一类型。也可以说，终端设备根据所述SIB1中存在上述IE或者字段，并且上述IE或者字段指示所述网络设备支持的终端设备的类型包括第一类型，确定驻留在所述网络设备的小区。否则，确定不驻留在所述网络设备的小区。
再一个示例中，当新增IE或字段用于指示网络设备支持的一个或者多个终端设备的类型时，若新增IE或字段指示支持的终端设备的类型不包括第一类型，则确定网络设备不支持降低性能UE，因此确定不驻留在所述网络设备的小区。若新增IE或字段指示支持的终端设备的类型中包括第一类型，则确定网络设备为支持降低性能UE的网络设备，可以按照现有流程继续判断是否满足其他的小区选择条件，在所有条件都满足的情况下，确定驻留在该网络设备的小区。
一些示例中，SIB1中除了包含第二指示信息以外，还可以包括网络设备支持的频带信息和带宽信息，例如：上行频带列表(frequencyBandList)、下行频带列表(frequencyBandList)、载波带宽(carrierBandwidth)、上行初始BWP(initial uplink BWP)、下行初始BWP(initial downlink BWP)等中的至少一个或者多个。这样，第一终端设备可以根据第二指示信息以及所述频带信息和带宽信息，确定是否驻留在所述网络设备的小区。例如：在上述各示例的基础上，若根据新增IE或字段确定该网络设备支持降低性能UE，则第一终端设备可以继续判断自身是否支持上述频带信息和带宽信息等，基于S准则来确定是否驻留在该网络设备的小区。相应的，在上述各示例的基础上，若根据新增IE或字段确定该网络设备不支持降低性能UE，则第一终端设备可以将该小区视为禁止的(barred)，即禁止驻留在该小区。
能够理解，当第一终端设备为能力强于降低性能UE的终端设备(legacy UE)时，第一终端设备可以按照现有的小区选择流程进行，本实施例对此不作赘述。
本实施例提供的通信方法，包括：网络设备生成并发送系统消息，在系统消息中包括第二指示信息，所述第二指示信息用于指示网络设备支持第一类型的终端设备或者是否支持第一类型的终端设备，这样，终端设备根据系统消息中的第二指示信息，可以获知网络设备是否支持第一类型的终端设备，进而确定是否驻留在该网络设备的小区。对于降低性能UE而言，若根据接收到的系统消息确定网络设备不支持降低性能UE，则不驻留在该网络设备的小区；只有在确定网络设备支持降低性能UE时，才将该网络设备的小区作为小区选择的候选对象，从而能够避免降低性能UE驻留到legacy网络设备中。
图6为本申请一个实施例提供的通信方法的流程示意图。如图6所示，本实施例的方法包括：
S601：第一网络设备生成系统消息，所述系统消息包括第二指示信息，所述第二指示信息用于指示第一类型，所述第一类型为终端设备的多个类型中的类型。
S602：第一网络设备发送所述系统消息，第一终端设备接收所述系统消息。
本实施例中S601和S602的具体实施方式与图5中的S501和S502类似，此处不作赘述。
S603：第一终端设备获取所述系统消息包含的第二指示信息。
本实施例的应用场景可以为前述的ANR场景。该场景中，第一终端设备工作于第二网络设备的小区中，也就是说，第二网络设备的某一小区为第一终端设备的服务小区。第一网络设备为终端设备的服务小区的邻区对应的网络设备。第一终端设备处于连接态。
第一终端设备工作于第二网络设备的小区的情况下，第二网络设备可以指示第一终端设备对邻区进行测量。第一终端设备监听邻区的广播，例如，监听第一网络设备广播的系统消息(如MIB,SIB1)，读取邻区的全局和物理标识(即，global and physical IDs，例如：NR CGI/NR PCI，ECGI/PCI))。
本实施例中，第一网络设备广播的系统消息中可以包括第二指示信息，第二指示信息用于指示第一类型。换句话说，第二指示信息用于指示第一网络设备支持第一类型的终端设备，或者，第二指示信息用于指示第一网络设备是否支持第一类型的终端设备。例如，当第一类型为降低性能UE时，第二指示信息指示的是第一网络设备支持或者是否支持降 低性能UE。也就是说，本实施例中，通过指示第一终端设备监听第一网络设备的系统消息，第二网络设备可获得第一网络设备对降低性能UE的支持能力。
与图5所示实施例类似，可选的，本实施例中系统消息可以为SIB1。
应理解，本实施例中，在系统消息中携带第二指示信息的方式与图5所示实施例类似，此处不作赘述。
S604：第一终端设备将所述第二指示信息或者所述第二指示信息对应的确定结果发送到第二网络设备；其中，所述确定结果为第一终端设备根据第二指示信息对第一网络设备是否支持第一类型的终端设备进行判断得到的结果。
本实施例中，第一终端设备从第一网络设备广播的系统消息中解析得到第二指示信息后，可以将第二指示信息发送给第二网络设备。从而，使得第二网络设备获知第一网络设备对于第一类型终端设备的支持能力。
其中，第一终端设备将第二指示信息发送给第二网络设备，可以有多种实施方式，本实施例对此不作具体限定，下面以几种可能的实施方式为例进行描述。
一种可能的实施方式中，第一终端设备从第一网络设备接收到SIB1后，将从SIB1中解析到的第二指示信息发送给第二网络设备。例如：可以将第二指示信息携带在CGI程序报告(procedure report)、测量报告(measurement report)中发送。
另一种可能的实施方式中，第一终端设备从第一网络设备接收到SIB1后，根据SIB1中的第二指示信息确定第一网络设备是否支持第一类型的终端设备，将确定结果发送给第二网络设备。例如：可以通过在测量报告、CGI procedure report、或者其他报告中增加信息域(field)。例如，若确定结果为第一网络设备支持第一类型的终端设备，则将该新增field可设为1或者true或者supported，若确定结果为第一网络设备不支持第一类型的终端设备，则将该新增field设为0或者false或者notsupported。
第二网络设备接收到第二指示信息后，可以对第二指示信息进行存储。例如，可以存储到邻区关系表(neighbour cell relation table，NCRT)中。
下面以第二指示信息携带在CGI procedure report中发送为例，描述具体的交互过程。图7为本申请一个实施例提供的ANR场景的交互过程示意图。如图7所示，假设第一终端设备工作于第二网络设备的小区A中。第一终端设备检测到第一网络设备的小区B。ANR的交互过程包括：
S701：第一终端设备向第二网络设备发送检测到的小区B的PCI。
S702：若第二网络设备发现第一终端设备上报的小区B的PCI不可识别，则指示第一终端设备获取该PCI对应的邻区信息。
S703：第一终端设备接收小区B的SIB1，并根据从SIB1中解析得到的邻区信息生成CGI procedure report。其中，CGI procedure report中包括：PLMN列表、RAN区域码(RAN area code，RANAC)、跟踪区域码(tracking area code，TAC)、小区ID(Cell ID)、频段列表、第二指示信息中的一个或多个。
S704：第一终端设备将CGI procedure report发送给第二网络设备。
现有的ANR流程中，第一终端设备接收小区B的SIB1，通过对SIB1解析得到小区B对应的PLMN列表、TAC、Cell ID、频段列表，将这些信息携带在CGI procedure report中发送给第二网络设备。而本实施例中，在小区B的SIB1中包含第二指示信息的情况下， 第一终端设备还可以将从小区B的SIB1中解析得到的第二指示信息携带在CGI procedure report或其他报告中。这样，第二网络设备在接收到UE的上报后，根据其中携带的第二指示信息可以获知第一网络设备对第一类型的终端设备的支持能力。
本实施例中，通过将SIB1中的第二指示信息添加到CGI procedure report中，不会带来因测量或读取其他邻小区相关的信息而引起的延时。
为了以示区分，将现有ANR流程中的CGI procedure report称为原始(Original)CGI procedure report，将本实施例中CGI procedure report称为增强(Enhanced)CGI procedure report。示例性的，本实施例Enhanced CGI procedure report中包含的内容如表2所示。
表2 Enhanced CGI procedure report
Figure PCTCN2020077500-appb-000002
S705：第二网络设备向第一网络设备或第一网络设备向第二网络设备发起Xn连接建立请求，以建立网络设备间的Xn连接，此Xn连接用于后续的切换流程。
或者，第一网络设备和第二网络设备之间的切换通过NG接口进行，即经核心网AMF转发切换请求消息及切换成功/失败消息。例如，当第一网络设备和第二网络设备之间的Xn连接无法建立时，第一网络设备和第二网络设备之间的切换将通过NG接口进行。
本实施例中，当第二网络设备发起切换时，将利用从CGI procedure report中获取的信息，包括其他网络设备支持或者是否支持第一类型(降低性能UE)的信息，作为判断条件，以选择目标网络设备。例如，若待切换的终端设备的类型为降低性能UE，则第二网络设备选择支持降低性能UE的网络设备(例如第一网络设备)作为目标网络设备。从而，可以避免将降低性能UE切换至legacy网络设备中。
图8为本申请一个实施例提供的通信方法的流程示意图。如图8所示，本实施例的方法包括：
S801：第一终端设备生成能力信息，所述能力信息包括第三指示信息，所述第三指示信息用于指示第一终端设备的类型，所述第一终端设备的类型为第一类型或者第二类型。
S802：第一终端设备向网络设备发送所述能力信息。
相应的，网络设备从第一终端设备接收所述能力信息。
S803：网络设备根据所述能力信息中的第三指示信息，确定所述第一终端设备的类型为第一类型或者第二类型。
本实施例的方法可应用于终端设备的能力交互场景。终端设备的能力交互场景可以包括下述两种场景。
场景1：终端设备主动向网络设备上报自身的能力信息，例如：终端设备在网络中进行附着(attach)时，或者终端设备进行跟踪区更新(tracking area updating，TAU)，终端设备会主动上报能力信息。
场景2：网络设备向终端设备询问终端设备的能力信息。针对场景2，本实施例S801 之前，还可以包括：S800：网络设备向第一终端设备发送能力请求消息，相应的，第一终端设备从网络设备接收能力请求消息。也就是说，当网络设备需要终端设备上报能力信息时，网络设备会给终端设备下发能力请求消息(UECapabilityEnquiry)。当终端设备接收到能力请求消息(UECapabilityEnquiry)后，终端设备根据该请求消息上报UE能力信息(UECapabilityInformation)。
示例性的，第一类型的终端设备可以为降低性能UE。第二类型的终端设备可以为能力高于降低性能UE的终端设备，例如，第二类型的终端设备可以为legacy UE。
本实施例中，第一终端设备在能力信息中包括第三指示信息，用于指示第一终端设备的类型，这样，网络设备根据接收到的能力信息，可以确定出第一终端设备的类型，从而，网络设备可以根据第一终端设备的类型采用不同的处理方式。例如，若第一终端设备的类型为第一类型(降低性能UE)，则认为第一终端设备支持的带宽为其通过bitmap或其他形式上报的带宽，在第一终端设备需要切换时，将第一终端设备切换至支持降低性能UE的网络设备中。若第一终端设备的类型为第二类型(例如legacy UE)，则认为第一终端设备的带宽为其通过bitmap或其他形式上报的带宽和100MHz。
图9为本申请一个实施例提供的通信方法的流程示意图。本实施例的方法可应用于Xn接口建立场景。如图9所示，本实施例的方法包括：
S901：第一网络设备向第二网络设备发送Xn接口建立请求消息(XN SETUP REQUEST message)，所述Xn接口建立请求消息中包括询问信息，所述询问信息用于询问所述第二网络设备是否支持第一类型的终端设备。
一个示例中，假设第一类型的终端设备为降低性能UE，则可以在Xn接口建立请求消息(XN SETUP REQUEST message)中添加新的IE或字段(例如reduced capability UE accessibility)，来询问第二网络设备是否支持降低性能UE。
Xn接口建立请求消息中还可以包括第一网络设备的应用数据。其中，一个网络设备的应用数据包括但不限于：该网络设备的ID、该网络设备所对应的AMF区域信息(AMF region information)、该网络设备的小区及邻区信息，等。这样，第二网络设备可以根据第一网络设备的应用数据，确定是否与第一网络设备建立Xn接口。
S902：第二网络设备向第一网络设备发送Xn接口建立应答消息(XN SETUP RESPONSE message)或者Xn接口建立失败消息(XN SETUP FAILURE message)，其中，所述Xn接口建立应答消息包括第四指示信息，所述第四指示信息用于指示所述第二网络设备是否支持第一类型的终端设备。
若第二网络设备确定Xn接口无法建立，则第二网络设备向第一网络设备发送Xn接口建立失败消息(XN SETUP FAILURE message)。
若第二网络设备允许Xn接口的建立，则第二网络设备向第一网络设备发送Xn接口建立应答消息(XN SETUP RESPONSE message)。本实施例中，Xn接口建立应答消息中包括第四指示信息。其中，第四指示信息可以有多种形式，本实施例对此不作限定。例如，可以在Xn接口建立应答消息中新增1bit，或者复用已有的1bit来表示第四指示信息。若第二网络设备支持第一类型的终端设备，则将该bit设置为1，若第二网络设备不支持第一类型的终端设备，则将该bit设置为0。这样，第一网络设备根据第四指示信息可以获知第 二网络设备是否支持第一类型的终端设备。
当然，Xn接口建立应答消息(XN SETUP RESPONSE message)中还可以包括第二网络设备的应用数据。这样，第一网络设备根据第二网络设备的应用数据可以获知第二网络设备的相关信息。
第一网络设备还可以对第二网络设备的应用数据以及第四指示信息进行存储。当第一网络设备需要对第一类型的终端设备发起切换时，可以根据存储的各网络设备的第四指示信息，确定将第一类型的终端设备切换至哪个目标网络设备。例如，当第一网络设备需要对降低性能UE发起切换时，可以根据存储的各网络设备的第四指示信息，选择支持降低性能UE的网络设备作为目标网络设备。从而，避免将降低性能UE切换至不支持降低性能UE的网络设备中。
本申请实施例提供了一种通信装置，所述通信装置可以为网络设备或者网络设备内部的元件，例如芯片或者集成电路。下面以网络设备为例进行阐述，本领域技术人员可知，以下网络设备可以替换为芯片或者集成电路等通信装置。图10为本申请实施例提供的网络设备的结构示意图。如图10所示，本实施例的网络设备10可以包括：处理单元11、发送单元12和接收单元13中的一个或者多个。下面结合不同的应用场景，对本实施例的网络设备进行介绍。
本实施例的网络设备可应用于切换场景。在切换场景中，本实施例的网络设备10可以作为第一网络设备。这时，网络设备10可以包括处理单元11、发送单元12和接收单元13。其中，处理单元11用于确定第一终端设备的类型为第一类型；发送单元12用于发送切换请求消息，所述切换请求消息包括第一指示信息，所述第一指示信息包含所述第一类型的标识信息；接收单元13用于接收切换确认消息或者切换准备失败消息。
一种可能的实现方式中，所述第一指示信息还包含关键值指示信息，所述关键值指示信息用于指示第二网络设备在第一条件下拒绝所述切换。
一种可能的实现方式中，所述接收单元13具体用于：接收来自第二网络设备的切换确认消息，所述第二网络设备支持所述第一类型的终端设备；或者，接收来自第二网络设备的第一切换准备失败消息，所述第一切换准备失败消息包含对应所述第一类型的失败信息，所述第二网络设备不支持所述第一类型的终端设备。
一种可能的实现方式中，所述发送单元12具体用于：向第二网络设备发送所述切换请求消息；或者，通过接入和移动性管理功能AMF设备向第二网络设备发送所述切换请求消息。
本实施例的网络设备可用于实现如图3和图4所示方法实施例中第一网络设备执行的通信方法，其实现原理和技术效果类似，此处不作赘述。
在切换场景中，本实施例的网络设备10还可以作为第二网络设备。这时，网络设备10可以包括接收单元13和发送单元12。其中，接收单元13用于接收切换请求消息，所述切换请求消息包括第一指示信息，所述第一指示信息包含第一类型的标识信息，所述第一类型为终端设备的第一类型；或者所述第一类型为第一终端设备的类型；发送单元12用于发送切换确认消息或者切换准备失败消息。
一种可能的实现方式中，所述切换请求消息还包括第一终端设备的能力信息，所 述第一终端设备的类型为所述第一类型。
一种可能的实现方式中，所述第一指示信息还包含关键值指示信息，所述关键值指示信息用于指示第二网络设备在第一条件下拒绝所述切换。
一种可能的实现方式中，所述接收单元13具体用于：接收第一网络设备发送的切换请求消息；或者，通过接入和移动性管理功能AMF设备接收来自第一网络设备的切换请求消息。
本实施例的网络设备可用于实现如图3和图4所示方法实施例中第二网络设备执行的通信方法，其实现原理和技术效果类似，此处不作赘述。
本实施例的网络设备还可应用于小区选择或者小区重选或者ANR场景。该场景中，网络设备10可以包括处理单元11和发送单元12。其中，处理单元11用于生成系统消息，所述系统消息包括第二指示信息，所述第二指示信息用于指示第一类型，所述第一类型为终端设备的第一类型；发送单元12用于发送所述系统消息。
一种可能的实现方式中，所述系统消息为系统消息块SIB1。
本实施例的网络设备可用于实现如图5至图7所示方法实施例中网络设备执行的通信方法，其实现原理和技术效果类似，此处不作赘述。
本实施例的网络设备还可应用于终端设备的能力交互场景。该场景中，网络设备10可以包括接收单元13和处理单元11。其中，接收单元13用于从第一终端设备接收能力信息，所述能力信息包括第三指示信息；处理单元11用于根据所述第三指示信息，确定所述第一终端设备的类型为第一类型或者第二类型。
一种可能的实现方式中，该网络设备10还可以包括发送单元12，所述发送单元12用于向所述第一终端设备发送能力请求消息。
本实施例的网络设备可用于实现如图8所示方法实施例中网络设备执行的通信方法，其实现原理和技术效果类似，此处不作赘述。
本实施例的网络设备还可应用于Xn接口的建立场景。在Xn接口的建立场景中，本实施例的网络设备10可以作为第一网络设备。这时，网络设备10可以包括接收单元13和发送单元12。其中，发送单元12用于向第二网络设备发送Xn接口建立请求消息，所述Xn接口建立请求消息中包括询问信息，所述询问信息用于询问所述第二网络设备是否支持第一类型的终端设备；接收单元13用于从第二网络设备接收Xn接口建立应答消息或者Xn接口建立失败消息；其中，所述Xn接口建立应答消息包括第四指示信息，所述第四指示信息用于指示所述第二网络设备是否支持第一类型的终端设备。
本实施例的网络设备可用于实现如图9所示方法实施例中第一网络设备执行的通信方法，其实现原理和技术效果类似，此处不作赘述。
在Xn接口的建立场景中，本实施例的网络设备10还可以作为第二网络设备。这时，网络设备10可以包括接收单元13和发送单元12。其中，接收单元13用于从第一网络设备接收Xn接口建立请求消息，所述Xn接口建立请求消息中包括询问信息，所述询问信息用于询问所述第二网络设备是否支持第一类型的终端设备；发送单元12用于向第一网络设备发送Xn接口建立应答消息或者Xn接口建立失败消息；其中，所述Xn接口建立应答消息包括第四指示信息，所述第四指示信息用于指示所述第二网络设备是否支持第一类型的终端设备。
本实施例的网络设备可用于实现如图9所示方法实施例中第二网络设备执行的通信方法，其实现原理和技术效果类似，此处不作赘述。
本申请实施例提供了一种通信装置，所述通信装置可以为终端设备或者终端设备内部的元件，例如芯片或者集成电路。下面以终端设备为例进行阐述，本领域技术人员可知，以下终端设备可以替换为芯片或者集成电路等通信装置。图11为本申请实施例提供的终端设备的结构示意图。如图11所示，本实施例的终端设备20可以包括：处理单元21、发送单元22和接收单元23中的一个或者多个。下面结合不同的应用场景，对本实施例的终端设备进行介绍。
本实施例的终端设备可应用于小区选择或者小区重选或者ANR场景。该场景中，本实施例的终端设备10可作为第一终端设备。这时，终端设备10可以包括接收单元23和处理单元21。其中，接收单元23用于接收来自网络设备的系统消息；处理单元21用于获取所述系统消息包含的第二指示信息，所述第二指示信息用于指示第一类型，所述第一类型为终端设备的第一类型。
一种可能的实现方式中，所述系统消息为系统消息块SIB1。
一种可能的实现方式中，所述处理单元21还用于：根据所述第二指示信息，确定是否驻留在所述网络设备的小区。
一种可能的实现方式中，所述系统消息还包括：所述网络设备支持的频带信息和带宽信息；所述处理单元21具体用于：根据所述第二指示信息以及所述网络设备支持的频带信息和带宽信息，确定是否驻留在所述网络设备的小区。
一种可能的实现方式中，所述网络设备为第一终端设备的服务小区的邻区对应的网络设备；该终端设备10还可以包括发送单元22，所述发送单元22用于：发送所述第二指示信息到所述服务小区对应的网络设备。
本实施例的终端设备可用于实现图5至图7所示方法实施例中由终端设备执行的通信方法，其实现原理和技术效果类似，此处不作赘述。
本实施例的终端设备还可应用于终端设备的能力交互场景。该场景中，终端设备20可以包括发送单元22和处理单元21。其中，处理单元21用于生成能力信息，所述能力信息包括第三指示信息，所述第三指示信息用于指示第一终端设备的类型，所述第一终端设备的类型为第一类型或者第二类型；发送单元22用于向网络设备发送所述能力信息。
一种可能的实现方式中，该终端设备20还可以包括接收单元23，所述接收单元23用于从所述网络设备接收能力请求消息。
本实施例的终端设备可用于实现图8所示方法实施例中由终端设备执行的通信方法，其实现原理和技术效果类似，此处不作赘述。
图12为本申请实施例提供的网络设备的结构示意图。如图12所示，本实施例的网络设备30，可以包括：处理器31、存储器32和通信接口33。其中，处理器31的数量可以为一个或者多个。存储器32的数量可以为一个或者多个。
其中，存储器32，用于存储计算机程序；通信接口33，用于与其他网络设备或者终 端设备进行数据通信或者信号通信。处理器31，用于执行存储器32存储的计算机程序，以实现如图3和图4所示方法实施例中第一网络设备执行的通信方法，或者，实现如图3和图4所示方法实施例中第二网络设备执行的通信方法，或者，实现如图5至图7所示方法实施例中网络设备执行的通信方法，或者，实现如8所示方法实施例中网络设备执行的通信方法，或者，实现如图9所示方法实施例中第一网络设备执行的通信方法，或者，实现如图9所示方法实施例中第二网络设备执行的通信方法。
可选地，存储器32既可以是独立的，也可以跟处理器31集成在一起。当所述存储器32是独立于处理器31之外的器件时，所述网络设备30还可以包括：总线34，用于连接所述存储器32和处理器31。
在一种可能的实施方式中，图10中的处理模块11可以集成在处理器31中实现，接收模块13和发送模块12可以集成在通信接口33中实现。
在一种可能的实施方式中，处理器31可用于实现上述方法实施例中网络设备的信号处理操作，通信接口33可用于实现上述方法实施例中网络设备的信号收发操作。
本实施例提供的网络设备，可用于执行上述方法实施例中网络设备所执行的方法，其实现原理和技术效果类似，此处不再赘述。
图13为本申请实施例提供的终端设备的结构示意图。如图13所示，本实施例的终端设备40，包括：处理器41、存储器42和收发器43。其中，处理器41的数量可以为一个或者多个。存储器42的数量可以为一个或者多个。
其中，存储器42，用于存储计算机程序；收发器43，用于与网络设备进行数据通信或者信号通信。处理器41，用于执行存储器42存储的计算机程序，以实现图5至图7所示方法实施例中由终端设备执行的通信方法，或者，实现图8所示方法实施例中由终端设备执行的通信方法。
可选地，存储器42既可以是独立的，也可以跟处理器41集成在一起。当所述存储器42是独立于处理器41之外的器件时，所述终端设备40还可以包括：总线44，用于连接所述存储器42和处理器41。
在一种可能的实施方式中，图11中的处理模块21可以集成在处理器41中实现，接收模块23和发送模块22可以集成在收发器43中实现。
在一种可能的实施方式中，处理器41可用于实现上述方法实施例中终端设备的信号处理操作，收发器43可用于实现上述方法实施例中终端设备的信号收发操作。
本实施例提供的终端设备，可用于执行上述方法实施例中终端设备所执行的方法，其实现原理和技术效果类似，此处不再赘述。
本申请实施例提供一种计算机存储介质，所述计算机存储介质包括计算机程序，所述计算机程序用于实现上述方法实施例中网络设备所执行的方法，或者实现上述方法实施例中终端设备所执行的方法。
本申请实施例还提供一种芯片或者芯片系统，该芯片或者芯片系统包括至少一个处理器和通信接口，通信接口和至少一个处理器通过线路互联，至少一个处理器用于运行计算机程序或指令，以实现上述方法实施例中网络设备所执行的方法，或者实现上述方法实施例中终端设备所执行的方法。
其中，芯片中的通信接口可以为输入/输出接口、管脚或电路等。
在一种可能的实现中，本申请中上述描述的芯片或者芯片系统还包括至少一个存储器，该至少一个存储器中存储有指令。该存储器可以为芯片内部的存储单元，例如，寄存器、缓存等，也可以是该芯片的存储单元(例如，只读存储器、随机存取存储器等)。
本申请实施例还提供一种计算机程序产品，所述计算机程序产品包括计算机程序代码，当所述计算机程序代码在计算机上运行时，使得计算机执行上述方法实施例中网络设备所执行的方法，或者实现上述方法实施例中终端设备所执行的方法。
本申请实施例还提供一种通信系统，包括第一网络设备和第二网络设备。其中，第一网络设备和第二网络设备可以采用如图10或者图12所示的结构。一些场景中，第一网络设备和第二网络设备可以实现如图3或者图4所示的通信方法。另一些场景中，第一网络设备和第二网络设备可以实现如图9所示的通信方法。
本申请实施例还提供一种通信系统，包括：网络设备和终端设备。其中，网络设备可以采用如图10或者图12所示的结构，终端设备可以采用如图11或者图13所示的结构。一些场景中，网络设备和终端设备可用于实现如图5至图7所示的通信方法。另一些场景中，网络设备和终端设备可用于实现如图8所示的通信方法。
在本申请所提供的几个实施例中，应该理解到，所揭露的设备和方法，可以通过其它的方式实现。例如，以上所描述的设备实施例仅仅是示意性的，例如，所述模块的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个模块可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或模块的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的模块可以是或者也可以不是物理上分开的，作为模块显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能模块可以集成在一个处理单元中，也可以是各个模块单独物理存在，也可以两个或两个以上模块集成在一个单元中。上述模块成的单元既可以采用硬件的形式实现，也可以采用硬件加软件功能单元的形式实现。
上述以软件功能模块的形式实现的集成的模块，可以存储在一个计算机可读取存储介质中。上述软件功能模块存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器(英文：processor)执行本申请各个实施例所述方法的部分步骤。
应理解，上述处理器可以是中央处理单元(英文：central processing unit，简称：CPU)，还可以是其他通用处理器、数字信号处理器(英文：digital signal processor，简称：DSP)、专用集成电路(英文：application specific integrated circuit，简称：ASIC)等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合发明所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。
存储器可能包含高速RAM存储器，也可能还包括非易失性存储NVM，例如至少一个磁盘存储器，还可以为U盘、移动硬盘、只读存储器、磁盘或光盘等。
总线可以是工业标准体系结构(industry standard architecture，ISA)总线、外部设备 互连(peripheral component，PCI)总线或扩展工业标准体系结构(extended industry standard architecture，EISA)总线等。总线可以分为地址总线、数据总线、控制总线等。为便于表示，本申请附图中的总线并不限定仅有一根总线或一种类型的总线。
上述存储介质可以是由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。存储介质可以是通用或专用计算机能够存取的任何可用介质。
一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于专用集成电路(application specific integrated circuits，简称：ASIC)中。当然，处理器和存储介质也可以作为分立组件存在于电子设备或主控设备中。

Claims (28)

  1. 一种通信方法，其特征在于，所述方法包括：
    确定第一终端设备的类型为第一类型；
    发送切换请求消息，所述切换请求消息包括第一指示信息，所述第一指示信息包含所述第一类型的标识信息；
    接收切换确认消息或者切换准备失败消息。
  2. 根据权利要求1所述的方法，其特征在于，所述第一指示信息还包含关键值指示信息，所述关键值指示信息用于指示第二网络设备在第一条件下拒绝所述切换。
  3. 根据权利要求1或2所述的方法，其特征在于，所述接收切换确认消息或者切换准备失败消息，包括：
    接收来自第二网络设备的切换确认消息，所述第二网络设备支持所述第一类型的终端设备；
    或者，
    接收来自第二网络设备的第一切换准备失败消息，所述第一切换准备失败消息包含对应所述第一类型的失败信息，所述第二网络设备不支持所述第一类型的终端设备。
  4. 根据权利要求1至3任一项所述的方法，其特征在于，所述发送切换请求消息，包括：
    向第二网络设备发送所述切换请求消息；
    或者，
    通过接入和移动性管理功能AMF设备向第二网络设备发送所述切换请求消息。
  5. 一种通信方法，其特征在于，所述方法包括：
    接收切换请求消息，所述切换请求消息包括第一指示信息，所述第一指示信息包含第一类型的标识信息，所述第一类型为终端设备的第一类型；或者所述第一类型为第一终端设备的类型；
    发送切换确认消息或者切换准备失败消息。
  6. 根据权利要求5所述的方法，其特征在于，所述切换请求消息还包括第一终端设备的能力信息，所述第一终端设备的类型为所述第一类型。
  7. 根据权利要求5或6所述的方法，其特征在于，所述第一指示信息还包含关键值指示信息，所述关键值指示信息用于指示第二网络设备在第一条件下拒绝所述切换。
  8. 根据权利要求5至7任一项所述的方法，其特征在于，接收切换请求消息，包括：
    接收第一网络设备发送的切换请求消息；
    或者，
    通过接入和移动性管理功能AMF设备接收来自第一网络设备的切换请求消息。
  9. 一种通信方法，其特征在于，所述方法包括：
    生成系统消息，所述系统消息包括第二指示信息，所述第二指示信息用于指示第一类型，所述第一类型为终端设备的第一类型；
    发送所述系统消息。
  10. 根据权利要求9所述的方法，其特征在于，所述系统消息为系统消息块SIB1。
  11. 一种通信方法，其特征在于，所述方法包括：
    接收来自网络设备的系统消息；
    获取所述系统消息包含的第二指示信息，所述第二指示信息用于指示第一类型，所述第一类型为终端设备的第一类型。
  12. 根据权利要求11所述的方法，其特征在于，所述系统消息为系统消息块SIB1。
  13. 根据权利要求11或12所述的方法，其特征在于，所述方法还包括：
    根据所述第二指示信息，确定是否驻留在所述网络设备的小区。
  14. 根据权利要求13所述的方法，其特征在于，所述系统消息还包括：所述网络设备支持的频带信息和带宽信息；
    根据所述第二指示信息，确定是否驻留在所述网络设备的小区，包括：
    根据所述第二指示信息以及所述网络设备支持的频带信息和带宽信息，确定是否驻留在所述网络设备的小区。
  15. 根据权利要求11或12所述的方法，其特征在于，所述网络设备为第一终端设备的服务小区的邻区对应的网络设备；所述方法还包括：
    发送所述第二指示信息到所述服务小区对应的网络设备。
  16. 一种通信方法，其特征在于，所述方法包括：
    生成能力信息，所述能力信息包括第三指示信息，所述第三指示信息用于指示第一终端设备的类型，所述第一终端设备的类型为第一类型或者第二类型；
    向网络设备发送所述能力信息。
  17. 根据权利要求16所述的方法，其特征在于，生成能力信息之前，还包括：
    从所述网络设备接收能力请求消息。
  18. 一种通信方法，其特征在于，所述方法包括：
    从第一终端设备接收能力信息，所述能力信息包括第三指示信息；
    根据所述第三指示信息，确定所述第一终端设备的类型为第一类型或者第二类型。
  19. 根据权利要求18所述的方法，其特征在于，所述从第一终端设备接收能力信息之前，还包括：
    向所述第一终端设备发送能力请求消息。
  20. 一种通信装置，其特征在于，包括：
    处理单元，用于确定第一终端设备的类型为第一类型；
    发送单元，用于发送切换请求消息，所述切换请求消息包括第一指示信息，所述第一指示信息包含所述第一类型的标识信息；
    接收单元，用于接收切换确认消息或者切换准备失败消息。
  21. 一种通信装置，其特征在于，包括：
    接收单元，用于接收切换请求消息，所述切换请求消息包括第一指示信息，所述第一指示信息包含第一类型的标识信息，所述第一类型为终端设备的第一类型；或者所述第一类型为第一终端设备的类型；
    发送单元，用于发送切换确认消息或者切换准备失败消息。
  22. 一种通信装置，其特征在于，包括：
    处理单元，用于生成系统消息，所述系统消息包括第二指示信息，所述第二指示信息用于指示第一类型，所述第一类型为终端设备的第一类型；
    发送单元，用于发送所述系统消息。
  23. 一种通信装置，其特征在于，包括：
    接收单元，用于接收来自网络设备的系统消息；
    处理单元，用于获取所述系统消息包含的第二指示信息，所述第二指示信息用于指示第一类型，所述第一类型为终端设备的第一类型。
  24. 一种通信装置，其特征在于，包括：
    处理单元，用于生成能力信息，所述能力信息包括第三指示信息，所述第三指示信息用于指示第一终端设备的类型，所述第一终端设备的类型为第一类型或者第二类型；
    发送单元，用于向网络设备发送所述能力信息；
  25. 一种通信装置，其特征在于，包括：
    接收单元，用于从第一终端设备接收能力信息，所述能力信息包括第三指示信息；
    处理单元，用于根据所述第三指示信息，确定所述第一终端设备的类型为第一类型或者第二类型。
  26. 一种通信装置，其特征在于，包括：至少一个存储器和至少一个处理器，所述至少一个存储器用于存储计算机程序，所述至少一个处理器用于从所述至少一个存储器中调用并运行所述计算机程序，使得所述至少一个处理器运行所述计算机程序执行如权利要求1-4、5-8、9-10、18-19中任一项所述的通信方法。
  27. 一种通信装置，其特征在于，包括：至少一个存储器和至少一个处理器，所述至少一个存储器用于存储计算机程序，所述至少一个处理器用于从所述至少一个存储器中调用并运行所述计算机程序，使得所述至少一个处理器运行所述计算机程序执行如权利要求11-15、16-17中任一项所述的通信方法。
  28. 一种计算机存储介质，其特征在于，所述计算机存储介质包括计算机程序，所述计算机程序用于实现如权利要求1-4、5-8、9-10、18-19中任一项所述的通信方法，或者，如权利要求11-15、16-17中任一项所述的通信方法。
PCT/CN2020/077500 2020-03-02 2020-03-02 通信方法及设备 WO2021174401A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
PCT/CN2020/077500 WO2021174401A1 (zh) 2020-03-02 2020-03-02 通信方法及设备
EP20922584.6A EP4109969A4 (en) 2020-03-02 2020-11-23 METHOD AND COMMUNICATION DEVICE
CN202080097717.6A CN115211173A (zh) 2020-03-02 2020-11-23 通信方法及设备
PCT/CN2020/130932 WO2021174913A1 (zh) 2020-03-02 2020-11-23 通信方法及设备
US17/901,413 US20220417811A1 (en) 2020-03-02 2022-09-01 Communication Method and Device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/077500 WO2021174401A1 (zh) 2020-03-02 2020-03-02 通信方法及设备

Publications (1)

Publication Number Publication Date
WO2021174401A1 true WO2021174401A1 (zh) 2021-09-10

Family

ID=77612875

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/CN2020/077500 WO2021174401A1 (zh) 2020-03-02 2020-03-02 通信方法及设备
PCT/CN2020/130932 WO2021174913A1 (zh) 2020-03-02 2020-11-23 通信方法及设备

Family Applications After (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/130932 WO2021174913A1 (zh) 2020-03-02 2020-11-23 通信方法及设备

Country Status (4)

Country Link
US (1) US20220417811A1 (zh)
EP (1) EP4109969A4 (zh)
CN (1) CN115211173A (zh)
WO (2) WO2021174401A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115277491A (zh) * 2022-06-15 2022-11-01 中国联合网络通信集团有限公司 异常数据的确定方法、装置及计算机可读存储介质
WO2023104004A1 (zh) * 2021-12-06 2023-06-15 华为技术有限公司 一种通信方法及装置
WO2023206331A1 (zh) * 2022-04-29 2023-11-02 Oppo广东移动通信有限公司 通信方法及通信装置

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023092422A1 (zh) * 2021-11-25 2023-06-01 北京小米移动软件有限公司 信息传输方法、装置、通信设备和存储介质
US11997554B2 (en) * 2022-03-30 2024-05-28 T-Mobile Usa, Inc. Smart UE cell selection and reselection
WO2024065704A1 (zh) * 2022-09-30 2024-04-04 Oppo广东移动通信有限公司 通信方法及通信装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102118833A (zh) * 2011-03-04 2011-07-06 电信科学技术研究院 一种小区接入指示方法、小区选择方法和设备
CN105338519A (zh) * 2014-08-07 2016-02-17 北京三星通信技术研究有限公司 一种支持低复杂度ue接入和寻呼的方法
CN106105329A (zh) * 2014-03-19 2016-11-09 三星电子株式会社 移动通信系统中的机器类型通信用户设备的网络选择和随机接入方法及装置
CN107277870A (zh) * 2016-04-01 2017-10-20 宏达国际电子股份有限公司 处理交递的装置及方法
CN109831805A (zh) * 2019-01-17 2019-05-31 吴新胜 一种提高大数据传输稳定性的方法及计算机可读存储介质

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104770012B (zh) * 2013-01-05 2019-03-08 华为技术有限公司 小区接入控制方法、基站、终端及系统
CN106465212B (zh) * 2014-03-21 2021-03-12 寰发股份有限公司 用于lc-mtc通信ue的小区选择和重选方法及用户设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102118833A (zh) * 2011-03-04 2011-07-06 电信科学技术研究院 一种小区接入指示方法、小区选择方法和设备
CN106105329A (zh) * 2014-03-19 2016-11-09 三星电子株式会社 移动通信系统中的机器类型通信用户设备的网络选择和随机接入方法及装置
CN105338519A (zh) * 2014-08-07 2016-02-17 北京三星通信技术研究有限公司 一种支持低复杂度ue接入和寻呼的方法
CN107277870A (zh) * 2016-04-01 2017-10-20 宏达国际电子股份有限公司 处理交递的装置及方法
CN109831805A (zh) * 2019-01-17 2019-05-31 吴新胜 一种提高大数据传输稳定性的方法及计算机可读存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI: "Handover Target Selection for Category 0 UEs", 3GPP TSG RAN WG3#85 R3-141632, 8 August 2014 (2014-08-08), XP050821733 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023104004A1 (zh) * 2021-12-06 2023-06-15 华为技术有限公司 一种通信方法及装置
WO2023206331A1 (zh) * 2022-04-29 2023-11-02 Oppo广东移动通信有限公司 通信方法及通信装置
CN115277491A (zh) * 2022-06-15 2022-11-01 中国联合网络通信集团有限公司 异常数据的确定方法、装置及计算机可读存储介质
CN115277491B (zh) * 2022-06-15 2023-06-06 中国联合网络通信集团有限公司 异常数据的确定方法、装置及计算机可读存储介质

Also Published As

Publication number Publication date
WO2021174913A1 (zh) 2021-09-10
EP4109969A1 (en) 2022-12-28
CN115211173A (zh) 2022-10-18
US20220417811A1 (en) 2022-12-29
EP4109969A4 (en) 2023-07-19

Similar Documents

Publication Publication Date Title
WO2021174401A1 (zh) 通信方法及设备
US11979818B2 (en) Communication method and communications apparatus
US11375471B2 (en) Method for performing service request procedure and apparatus therefor in wireless communication system
US11197216B2 (en) Handling of collision between SR procedure and PDU session establishment procedure for PDU session handover
EP3641424B1 (en) Method for registering a user equipment with a network slice in a wireless communication system and user equipment therefor
CN112996087B (zh) 一种网络切片选择方法、终端设备及网络设备
US11638140B2 (en) Method for transmitting and receiving signal related to switching access in wireless communication system, and device therefor
US10448276B2 (en) Method and terminal for performing attach procedure for sponsored connectivity in wireless communication system
WO2019137471A1 (zh) 通信方法、接入网设备和终端设备
US10805975B2 (en) Device-to-device direct communication method in wireless communication system and device therefor
US10362559B2 (en) Method for supporting device-to-device direct communication in wireless communication system, and apparatus therefor
US9877349B2 (en) Method for performing proximity service, and user device
KR102484223B1 (ko) Pdu 세션 활성화 방법, 페이징 방법 및 그의 장치
US20200120561A1 (en) 5GSM Handling on Invalid PDU Session
US10084693B2 (en) Method for transmitting/receiving signal related to NBIFOM in wireless communication system, and apparatus therefor
US11968694B2 (en) Communication method and apparatus, and device
CN114071788B (zh) Ue和网络之间的多接入pdu会话状态同步方法及相关用户设备
US20220116818A1 (en) Handling of 5GSM Congestion Timers
CN109474987B (zh) 与长期演进网络及新无线网络通信的装置及方法
US11910488B2 (en) Enhancement of feature support after interworking
US10917841B2 (en) Method for selecting serving MME of remote UE and transmitting NAS message in wireless communication system, and apparatus for said method
WO2020024865A1 (zh) 一种会话对应关系的管理方法和终端设备
WO2023065109A1 (zh) 信息发送方法、信息接收方法、装置和系统
US20240237033A1 (en) Communication method and apparatus, and device
US20220053377A1 (en) Handling of QoS Errors in ESM Procedure

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20923110

Country of ref document: EP

Kind code of ref document: A1