WO2022041150A1 - 一种通信方法及装置 - Google Patents

一种通信方法及装置 Download PDF

Info

Publication number
WO2022041150A1
WO2022041150A1 PCT/CN2020/112284 CN2020112284W WO2022041150A1 WO 2022041150 A1 WO2022041150 A1 WO 2022041150A1 CN 2020112284 W CN2020112284 W CN 2020112284W WO 2022041150 A1 WO2022041150 A1 WO 2022041150A1
Authority
WO
WIPO (PCT)
Prior art keywords
customized
message
indication information
communication device
format
Prior art date
Application number
PCT/CN2020/112284
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/112284 priority Critical patent/WO2022041150A1/zh
Publication of WO2022041150A1 publication Critical patent/WO2022041150A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a communication method and device.
  • the current air interface communication protocol (or communication standard) of the 3rd Generation Partnership Project (3GPP) is usually implemented based on signaling.
  • the information element information element, IE
  • the radio resource control (RRC) protocol layer includes RRC signaling predefined by the protocol
  • the RRC reconfiguration (RRC reconfiguration) message includes information elements predefined by the protocol, such as radio bearer configuration (radioBearerConfig) information element, secondary cell group (secondary CellGroup) information element, and the like.
  • extension field dedicated to extension messages or extension cells is reserved in the communication protocol, so that new functions can be implemented by using the extension fields in subsequent versions.
  • the extension field can also be used to implement a customization (or privatization) function of communication, for example, the extension field in the RRC reconfiguration message is used to implement a customized function such as radio resource management (radio resource management, RRM).
  • RRM radio resource management
  • the present application provides a communication method and device for solving the compatibility problem caused by using an extension field in the current version of the protocol to implement a customized function, but the extension field is defined as other meanings in subsequent versions of the protocol.
  • the present application provides a communication method, including:
  • the first communication device receives a first message from the second communication device, where the first message includes first indication information, where the first indication information is used to indicate customized content; the first communication device determines to support the For the customized content indicated by the first indication information, the customized content indicated by the first indication information is parsed.
  • the first message includes first indication information, where the first indication information is used to indicate the customized content, and the first communication device parses the customized content indicated by the first indication information according to the first indication information, and does not
  • the second communication device does not know how to parse the customized content, which helps to avoid the use of the extension field in the current version of the protocol to implement the customized function, but in the subsequent version of the protocol, the extension field is defined as other meanings, causing compatibility issues.
  • the customized content includes a bytecode stream of customized messages, or the customized content includes a bytecode stream of customized cells.
  • the customized content can be at the message level or the cell level, and various customized functions can be implemented through the customized content at different levels.
  • the customized content includes a bytecode stream of customized information elements
  • the method further includes: the first communication device determines that the information indicated by the first indication information is not supported Customized content, parses other information elements in the first message except the bytecode stream of the customized information element.
  • the first communication device parses other information elements except the customized content (or customized information elements) in the first message to ensure the communication function predefined by the protocol between the first communication device and the second communication device.
  • the first communication apparatus determines to support the customized content indicated by the first indication information, and parses the customized content indicated by the first indication information, including: the first indication information
  • the communication device determines to support the customized format associated with the bytecode stream in the customized content indicated by the first indication information, and parses the customized format indicated by the first indication information according to the customized format indicated by the first indication information.
  • the bytecode stream in the indicated custom content is not limited to the first indication information.
  • the first indication information is specifically used to indicate a customized format associated with the bytecode stream in the customized content, and the first communication device can determine which customized format to use to parse the customized content according to the first indication information Medium bytecode stream.
  • the method further includes: receiving, by the first communication device, a second message from the second communication device, where the second message is used to indicate that the second communication device supports Customized format.
  • the second message includes at least one identifier, and each identifier in the at least one identifier is used to indicate that the second communication apparatus supports a customized format corresponding to the identifier; or,
  • the second message includes a bitmap, and each bit in the bitmap is used to indicate whether the second communication apparatus supports the customized format corresponding to the bit.
  • the first communication apparatus supports the customized format indicated by the second indication information
  • the method further includes: the first communication apparatus supports the customization indicated by the second indication information according to the first communication apparatus. and send the third message to the second communication device, where the third message includes the second indication information and a bytecode stream conforming to the customized format indicated by the second indication information. of customized content.
  • the customized format indicated by the first indication information is the same as the customized format indicated by the second indication information; the third message is a response corresponding to the first message information.
  • the first communication device sends a third message in the same customized format as the first message to the second communication device, thereby ensuring that the second communication device can parse the third message.
  • the first communication device and the second communication device can negotiate a customized format for communication between the two.
  • the present application provides a communication apparatus, where the communication apparatus may be a terminal device, or a module, such as a chip, in the terminal device.
  • the communication device may also be a network device, or a module in the network device, such as a chip.
  • the device includes: a communication unit and a processing unit; the communication unit is configured to receive a first message from a second communication device, the first message includes first indication information, and the first indication information is used to indicate customization
  • the processing unit is configured to determine that the customized content indicated by the first indication information is supported, and parse the customized content indicated by the first indication information.
  • the customized content includes a bytecode stream of customized messages, or the customized content includes a bytecode stream of customized cells.
  • the customized content includes a bytecode stream of customized information elements
  • the processing unit is further configured to determine that the customized content indicated by the first indication information is not supported, and parse the customized content.
  • the processing unit is specifically configured to determine to support a customized format associated with the bytecode stream in the customized content indicated by the first indication information, and according to the first indication information The indicated customized format, parsing the bytecode stream in the customized content indicated by the first indication information.
  • the communication unit is further configured to receive a second message from the second communication device, where the second message is used to indicate a customized format supported by the second communication device.
  • the second message includes at least one identifier, and each identifier in the at least one identifier is used to indicate that the second communication apparatus supports a customized format corresponding to the identifier; or,
  • the second message includes a bitmap, and each bit in the bitmap is used to indicate whether the second communication apparatus supports the customized format corresponding to the bit.
  • the apparatus supports the customized format indicated by the second indication information
  • the processing unit is further configured to control the communication unit according to the customized format indicated by the second indication information Sending the third message to the second communication device, where the third message includes the customization consisting of the second indication information and a bytecode stream conforming to the customization format indicated by the second indication information content.
  • the customized format indicated by the first indication information is the same as the customized format indicated by the second indication information; the third message is a response corresponding to the first message information.
  • the present application provides a communication device, comprising a processor and a communication interface, the communication interface being configured to receive signals from other communication devices other than the communication device and transmit to the processor or transfer signals from the communication device.
  • the signal of the processor is sent to other communication devices other than the communication device, and the processor is used for implementing the first aspect or any one of the methods in the first aspect through a logic circuit or executing code instructions.
  • the present application provides a computer-readable storage medium, where a computer program or instruction is stored, and when the computer program or instruction is executed by a communication device, the above-mentioned first aspect or the first aspect is realized. any of the methods in one aspect.
  • the present application provides a computer program product, the computer program product includes a computer program or an instruction, when the computer program or instruction is executed by a communication device, implements any one of the first aspect or the first aspect above a method.
  • FIG. 1 is a schematic diagram of a communication system architecture provided by the present application.
  • 2a is a schematic structural diagram of a downlink dedicated control channel message provided by the application.
  • 2b is a schematic structural diagram of another downlink dedicated control channel message provided by the application.
  • 3a is a schematic structural diagram of an RRC reconfiguration message provided by the application.
  • 3b is a schematic structural diagram of another RRC reconfiguration message provided by the application.
  • FIG. 4 is a schematic structural diagram of a customized message in a message class provided by the application.
  • 5a is a schematic structural diagram of still another downlink dedicated control channel message provided by the application.
  • 5b is a schematic structural diagram of a customized message provided by the application.
  • 6a is a schematic structural diagram of a broadcast channel-downlink shared channel message provided by the application.
  • 6b is a schematic structural diagram of another broadcast channel-downlink shared channel message provided by the application.
  • Figure 6c is a schematic structural diagram of another customized message provided by this application.
  • FIG. 7 is a schematic structural diagram of a customized information element in an existing message provided by the present application.
  • FIG. 8a is a schematic structural diagram of still another RRC reconfiguration message provided by the application.
  • FIG. 8b is a schematic structural diagram of a customized information element provided by the application.
  • FIG. 9 is a schematic flowchart of a communication method provided by the present application.
  • FIG. 10 is a schematic flowchart of negotiating a customized format provided by the present application.
  • FIG. 11 is a schematic flowchart of a communication between a network device and a terminal device provided by the application;
  • Figure 12a, Figure 12b, Figure 12c is a schematic flowchart of the communication between the network device and the terminal device in the specific scenario provided by this application;
  • FIG. 13 is a schematic flowchart of another communication between a network device and a terminal device provided by this application;
  • FIG. 15 is a schematic structural diagram of another communication apparatus provided by the present application.
  • the terminal equipment involved in the embodiments of this application which can also be referred to as a terminal, is an entity on the user side that is used to receive or transmit signals, and is used to send uplink signals to network equipment, or receive signals from network equipment. Downlink signal. Included are devices that provide voice and/or data connectivity to a user, such as may include handheld devices with wireless connectivity, or processing devices connected to a wireless modem.
  • the terminal equipment may communicate with the core network via a radio access network (RAN), and exchange voice and/or data with the RAN.
  • RAN radio access network
  • the terminal equipment may include user equipment (UE), V2X terminal equipment, wireless terminal equipment, mobile terminal equipment, device-to-device (D2D) terminal equipment, machine-to-machine/machine-type communication ( machine-to-machine/machine-type communications, M2M/MTC) terminal equipment, Internet of things (IoT) terminal equipment, subscriber unit (subscriber unit), subscriber station (subscriber station), mobile station (mobile station) , remote station (remote station), access point (access point, AP), remote terminal (remote terminal), access terminal (access terminal), user terminal (user terminal), user agent (user agent), or user equipment (user device), wearable devices, in-vehicle devices, etc.
  • IoT Internet of things
  • subscriber unit subscriber unit
  • subscriber station subscriber station
  • mobile station mobile station
  • remote station remote station
  • access point access point
  • AP remote terminal
  • remote terminal remote terminal
  • access terminal access terminal
  • user terminal user terminal
  • user agent user agent
  • user equipment user equipment
  • the terminal device may also be a wearable device.
  • Wearable devices can also be called wearable smart devices or smart wearable devices, etc. It is a general term for the application of wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes. Wait.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-scale, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, which needs to cooperate with other devices such as smart phones.
  • Use such as all kinds of smart bracelets, smart helmets, smart jewelry, etc. for physical sign monitoring.
  • the various terminal devices described above if they are located on the vehicle (for example, placed in the vehicle or installed in the vehicle), can be considered as on-board terminal equipment.
  • the on-board terminal equipment is also called on-board unit (OBU). ).
  • the core network involved in the embodiments of this application may include network devices that process and forward user signaling and data.
  • core network equipment such as mobility management function (access and mobility management function, AMF), session management function (session management function, SMF), and user plane gateway.
  • the user plane gateway can be a server with functions such as mobility management, routing, and forwarding of user plane data, and is generally located on the network side, such as serving gateway (serving gateway, SGW) or packet data network gateway (packet data network gateway, PGW) ) or user plane function entity (user plane function, UPF), etc.
  • AMF and SMF are equivalent to mobility management entities (mobility management entities, MMEs) in the LTE system.
  • AMF is mainly responsible for access
  • SMF is mainly responsible for session management.
  • the core network may also include other network elements, which are not listed here.
  • the next generation radio access network (next generation radio access network, NG-RAN) involved in the embodiments of this application may include one or more access network devices.
  • the access network device in the NG-RAN may also be called a base station, or a RAN node, or a RAN device.
  • the access network device is an entity on the network side for transmitting and/or receiving signals, and acts as a router between the terminal and the rest of the access network, where the rest of the access network may include an IP network and the like.
  • the access network equipment can also coordinate the attribute management of the air interface.
  • the access network equipment may be an evolutional Node B (evolutional Node B, eNB or e-NodeB) in LTE, and an eNB is a device deployed in a radio access network that meets the 4G standard and provides a wireless communication function for a terminal.
  • the access network device can also be a new radio controller (NR controller), a gNode B (gNB) in a 5G system, a centralized unit, a new wireless base station, or a new wireless base station.
  • NR controller new radio controller
  • gNB gNode B
  • a micro base station also called a small cell
  • a relay a distributed unit
  • a macro base station in various forms
  • TRP transmission and reception point
  • TMF transmission measurement function
  • TP transmission point
  • any other wireless access device or a base station in next-generation communications
  • system and “network” in the embodiments of the present application may be used interchangeably.
  • plurality refers to two or more.
  • and/or which describes the association relationship between associated objects, indicates that there can be three kinds of relationships, for example, A and/or B, which can mean that A exists alone, A and B exist at the same time, and B exists alone.
  • character "/”, unless otherwise specified, generally indicates that the related objects are an "or" relationship.
  • FIG. 1 shows a schematic diagram of a possible system network of the present application.
  • a radio access network Radio access network
  • the RAN includes at least two base stations: a base station 20 and a base station 30, and only two base stations and one user equipment UE are shown in the figure.
  • the RAN is connected to a core network (core network, CN).
  • the core network includes one or more core network devices.
  • the CN may be coupled to one or more external networks (External Network), such as the Internet (Internet), public switched telephone network (public switched telephone network, PSTN) and the like.
  • Internet Internet
  • PSTN public switched telephone network
  • the present application is not limited to the system architecture shown in FIG. 1 , and can also be applied to other communication systems in the future, such as the 6th generation (6G) communication system architecture.
  • 6G 6th generation
  • the network elements involved in this application may keep the same functions in future communication systems, but their names will be changed.
  • the communication protocol reserves an extension field specially used for extension messages or cells in the current version, so that new functions can be implemented by using the reserved extension field in subsequent versions.
  • the current version is referred to as the first version
  • the subsequent versions are referred to as the second version
  • the second version is a version evolved on the basis of the first version.
  • the extension field corresponds to the message extension bit in the message class, or the extension field corresponds to the cell extension bit in the existing message.
  • the evolution process of the downlink dedicated control channel message (DL-DCCH-Message) in the RRC protocol in the protocol is taken as an example to illustrate, the downlink dedicated control channel message is in the downlink.
  • Figure 2a is a schematic diagram of the structure of the downlink dedicated control channel message in the first version of the protocol, which includes a choice structure, and the choice structure includes an RRC reconfiguration message, an RRC release (RRC release) message, an RRC re-establishment (RRC) reestablishment) message, etc.
  • the selection structure is used to represent the selection of one message from multiple messages, and the sender can select one of the messages to send in specific use.
  • the selection structure also includes a message extension bit, the message extension bit is specifically reserved (spare) or message class extension (messageClassExtension), and the message extension bit can specifically be used as a downlink dedicated control channel message for extending the RRC message. extension bits.
  • Figure 2b is a schematic structural diagram of a downlink dedicated control channel message in the second version of the protocol.
  • a new message M1 is defined in the second version of the protocol, and the message M1 occupies the message extension bit in the first version of the protocol.
  • FIG. 3a is a schematic diagram of the structure of the RRC reconfiguration message in the first version of the protocol, which includes an RRC transaction identifier (rrc-TransactionIdentifier) and a critical extension (criticalExtensions).
  • the key extension adopts a selection structure, and the selection structure includes RRC reconfiguration information elements and future critical extensions (criticalExtensionsFuture), wherein the RRC reconfiguration information element includes a radio bearer configuration information element, a secondary cell group information element, and the like.
  • the RRC reconfiguration information element also includes a cell extension bit, the cell extension bit is specifically a non-CriticalExtension, and the cell extension bit can be used as an extension in the RRC reconfiguration cell for extending the RRC cell bit.
  • FIG. 3b is a schematic structural diagram of an RRC reconfiguration message in the protocol of the second version.
  • An information element IE1 is newly defined in the protocol of the second version, and the information element IE1 occupies the information element extension bit in the protocol of the first version.
  • Customized functions can be understood as non-protocol communication functions, which can be self-defined communication functions, such as radio resource management (RRM), self-organizing network (SON), minimization of drive test ( minimization of drive-tests, MDT), etc.
  • RRM radio resource management
  • SON self-organizing network
  • minimization of drive test minimization of drive-tests, MDT
  • MDT minimization of drive-tests
  • the message extension bit or the cell extension bit in the protocol of the first version can be used to implement the customized function of communication in the system architecture shown in FIG. 1 .
  • a message is customized by using the message extension bit in the protocol of the first version, and the customized message is used to realize the customized function of communication.
  • a new message can be customized by using the message extension bit in the downlink dedicated control channel message of the first version of the protocol, and the customized message is used to realize the customized function of communication between the network device and the terminal device.
  • the customized message has a customized format (format), and the customized format specifically indicates the format of the bytecode stream (octet string or octet stream) in the customized message. For example, if the customized message adopts format 1, the customized message contains bytecode stream 1 that conforms to customized format 1. For another example, if the customized message adopts customized format 2, the customized message includes the bytecode stream 1 that conforms to customized format 2. Bytecode stream 2.
  • the customized format may be a codec format.
  • the two parties of the customization negotiate the codec format in advance, and the two parties of the customization communicate based on the negotiated codec format.
  • the network device and the terminal device negotiate a codec format in advance, the network device sends a customized message conforming to the codec format to the terminal device, and the terminal device parses the customized message according to the codec format.
  • a cell is customized by using the cell extension bits of the existing message in the protocol of the first version, and the customized cell is used to realize the customized function of communication.
  • a new cell can be customized by using the cell extension bit in the RRC reconfiguration message of the first version of the protocol, and the customized cell is used to implement the customization function of the communication between the network device and the terminal device.
  • the customized cell has a customized format, and the customized format specifically indicates the format of the bytecode stream in the customized cell. For example, if the customized cell adopts customized format 3, the customized cell contains bytecode stream 3 that conforms to customized format 3. For another example, if the customized cell adopts customized format 4, the customized cell contains bytecode stream 3 that conforms to customized format 3. Contains bytecode stream 4 conforming to custom format 4.
  • the customized format may be a codec format.
  • the two parties of the customization negotiate the codec format in advance, and the two parties of the customization communicate based on the negotiated codec format.
  • the network device and the terminal device negotiate the codec format in advance, and the network device sends an RRC reconfiguration message to the terminal device.
  • the RRC reconfiguration message includes existing cells and customized cells that conform to the codec format.
  • the device parses existing cells according to the protocol, and parses customized cells according to the pre-agreed codec format.
  • an existing message is understood as a message pre-defined by the protocol in the first version of the protocol, and a customized message is understood as a customized message that occupies a message extension bit in the first version to implement a customized function.
  • An existing cell is understood as a cell pre-defined by the protocol in the first version of the protocol, and a customized cell is understood as a self-defined cell that occupies the cell extension bits in the existing message in the first version to realize the customization function, here It should be understood that if the customized information element in the cell extension bit in the existing message in the first version is occupied, the existing message may also be called a customized message, but the customized message includes the existing information element.
  • a byte code stream may also be understood as an octet string, an octet string, a byte sequence, and the like.
  • a bytecode stream can be understood as a certain format for carrying signaling.
  • the customized format can be understood as the encoding and decoding format of the bytecode stream in the customized message or customized cell, and the customized format can also be referred to as customized structure or customized type.
  • the message extension bit in the first version of the protocol is used to customize a message, or the cell extension bit of an existing message in the first version of the protocol is used to customize a cell, the customization function of communication can be realized.
  • the message extension bit or the cell extension bit is defined as another meaning by the protocol, which will cause compatibility problems.
  • the cell extension bit IEx in the RRC reconfiguration message. If the cell extension bit IEx is occupied to customize the cell IEa, and the customized cell IEa Use custom format a. However, in the second version of the protocol, it is necessary to occupy the cell extension bit IEx to define a new standardized cell IEb.
  • the cell IEb is used for general functions in the industry, and the cell IEb adopts format b, so there is compatibility The question is whether to use the customized format a or the format b to encode and decode the cell at this position in the RRC reconfiguration message.
  • the present application provides a communication method and device, which are used to solve the problem in the prior art that the information element extension bit or the message extension bit in the first version protocol is used to realize the customized function, but in the second version protocol, the cell extension bit is used. Bits or message extension bits are defined by the protocol to have other meanings, resulting in compatibility issues.
  • messages specially used for customization can be predefined in the second version protocol, or information elements specially used for customization in existing messages can be predefined in the second version protocol, so that the specialized information can be used.
  • the customized message, or the information element specially used for customization realizes the customized function of the network device or the terminal device.
  • a message specially used for customization is pre-defined. Specifically, a new message is defined in a certain message class, and the message is specially used for realizing various customized functions of communication. For example, the message is customized into customized message a to realize customized function a, or the message is customized into customized message b to realize customized function b.
  • a cell dedicated to customization is pre-defined, specifically, a new cell is defined in an existing message, and the cell is dedicated to realize various customization functions of communication. For example, the cell is customized into a customized cell c to implement the customized function c, or the cell is customized into a customized cell d to implement the customized function d.
  • the second version of the protocol only predefines messages or cells dedicated to customization, and does not predefine the messages or cells dedicated to customization.
  • the format of the byte stream can be customized, or the format of the bytecode stream in the cell can be customized.
  • the message is customized as customized message a, and the bytecode stream in customized message a conforms to customized format a.
  • the cell is customized as a customized cell c, and the bytecode stream in the customized cell c conforms to the customized format c.
  • the customized message or customized information element includes customized content
  • the customized content includes a bytecode stream conforming to the customized format.
  • the customized content in the customized message is at the message level
  • the bytecode stream in the customized content at the message level may be referred to as a message bytecode stream. If the customized content in the customized cell is at the cell level, the bytecode stream in the customized content at the cell level can be called the cell bytecode stream.
  • N pieces of indication information may also be pre-defined in the protocol of the second version, and N is greater than 1.
  • the indication information is used to indicate the customized format corresponding to the bytecode stream in the customized content.
  • the indication information can be an identification, an index, a serial number, a customized code, and the like.
  • the customized message may further include indication information, where the indication information is used to indicate the customized format of the bytecode stream in the customized content.
  • the customized information element may further include indication information, where the indication information is used to indicate the customized format of the bytecode stream in the customized content.
  • the second version of the protocol predefines messages specially used for customization.
  • FIG. 4 is a schematic structural diagram of a message class in a protocol of the second version provided by the present application, wherein the message class includes existing messages in the protocol of the first version, such as message A, message B, and message C, . . . ..., the second version protocol defines a new message in the message class for customization, such as message D, the message D occupies the message extension bit in the message class in the first version protocol.
  • the message class includes existing messages in the protocol of the first version, such as message A, message B, and message C, . . . ...
  • the second version protocol defines a new message in the message class for customization, such as message D
  • the message D occupies the message extension bit in the message class in the first version protocol.
  • the customized message D is a message D1
  • the message D1 includes indication information D1 and customized content D1, wherein the indication information D1 indicates that the bytecode stream in the customized content D1 conforms to the customized format D1.
  • the message D can also be customized to be message D2, or message D3, or message D4, or message D5, and correspond to customized format D2, customized format D3, customized format D4, and customized format D5, respectively, and They correspond to the indication information D2, the indication information D3, the indication information D4 and the indication information D5 respectively.
  • the second version of the protocol may predefine a special message in the downlink dedicated control channel message to implement the customized function, and the message occupies the message extension bit as shown in Figure 2a.
  • a schematic structural diagram of a downlink dedicated control channel message in the second version of the protocol is shown in FIG. 5a, which includes a customized message.
  • FIG. 5b is a schematic structural diagram of a customized message provided by the present application.
  • the customized message includes the RRC transaction identifier and key extension.
  • the key extension adopts a selection structure.
  • the selection structure includes customized message information elements and future key extensions.
  • the customized message information elements may further include customized codes (customizedCode), Message container (messageContainer) and non-critical extensions (nonCriticalExtension).
  • the customized code can be understood as instruction information
  • the customized code is used to indicate the customized format
  • the message container can be understood as customized content
  • the message container contains information that conforms to the customized format indicated by the customized code. bytecode stream.
  • the second example is a schematic structural diagram of a broadcast channel-downlink shared channel message (Broadcast channel-Downlink shared channel-Message, BCCH-DL-SCH-Message) in the first version of the protocol. It should be understood that the broadcast channel-downlink shared channel message is a broadcast message type.
  • the broadcast channel-downlink shared channel message includes a selection structure, and the selection structure includes a system information (SystemInformation), a system information block (SystemInformationBlock) and a message extension bit.
  • SystemInformation system information
  • SystemInformationBlock system information block
  • message extension bit a message extension bit
  • the second version of the protocol may predefine a special message in the broadcast channel-downlink shared channel message to implement the customized function, and the message occupies the message extension bit as shown in Figure 6a.
  • a schematic structural diagram of a broadcast channel-downlink shared channel message in the second version of the protocol is shown in FIG. 6b, which includes a customized message.
  • FIG. 6c is a schematic structural diagram of a customized message provided by the present application.
  • the customized message adopts a selection structure.
  • the selection structure includes a customized system message (customizedSystemMessage) information element and a future message class extension (messegeClassExtensionFuture).
  • the customized system message information element may further include customized codes, message containers and non-critical extensions. .
  • the message can be customized in the RRC message class, and in the second example, the message can be customized in the broadcast message class.
  • the application can also customize the message in other message classes. Exemplary Yes, it can be a customized message in the Xn/X2 message class between the network device and the network device.
  • the information element dedicated to customization in the existing message is pre-defined in the protocol of the second version.
  • FIG. 7 is a schematic structural diagram of an existing message in a protocol of the second version provided by the present application, wherein the existing message includes the existing information elements in the protocol of the first version, such as information element a and information element b and information element c, ..., the second version of the protocol defines a new information element in the existing message for customization, such as the information element d, the information element d can occupy the existing message in the first version of the protocol. cell extension bits in .
  • the customized information element d is an information element d1
  • the information element d1 includes indication information d1 and customized content d1, wherein the indication information d1 indicates that the bytecode stream in the customized content d1 conforms to the customized format d1.
  • the cell d can also be customized to be cell d2, or cell d3, or cell d4, or cell d5, and correspond to customized format d2, customized format d3, customized format d4 and customized format respectively format d5, and correspond to indication information d2, indication information d3, indication information d4 and indication information d5 respectively.
  • the protocol of the second version may predefine a special cell in the RRC reconfiguration message to implement the customized function, and the cell occupies the cell extension bit as shown in Figure 3a.
  • a schematic diagram of the structure of the RRC reconfiguration message in the second version of the protocol is shown in FIG. 8a, which includes customized information elements.
  • FIG. 8b is a schematic structural diagram of a customized cell provided by the present application.
  • the customized cells include customized codes and cell containers.
  • the customized code can be understood as instruction information, the customized code is used to indicate the customized format, the information element container can be understood as customized content, and the information element container contains words that conform to the customized format indicated by the customized code. throttling stream.
  • FIG. 9 a schematic flowchart of a communication method provided by an embodiment of the present application is as follows:
  • Step 901 the second communication device sends a first message to the first communication device.
  • the first communication device receives the first message from the second communication device.
  • the first message includes first indication information, where the first indication information is any one of N pieces of pre-defined indication information, and the first indication information is used to indicate customized content associated with the first indication information.
  • the first indication information indicates the customized content, and specifically, the first indication information indicates a customized format associated with a bytecode stream in the customized content, where the bytecode stream is the actual content in the customization.
  • the first message is a customized message in a message class
  • the customized message includes first indication information and customized content
  • the customized content includes a message bytecode stream
  • the first indication information indicates the message bytecode stream.
  • the associated custom format
  • the first message is an existing message
  • the first message includes a customized information element
  • the customized information element includes first indication information and customized content
  • the customized content includes a byte code stream of the information element
  • the first The indication information indicates the customized format associated with this cell bytecode stream.
  • the first message may include at least one customized information element, and for each customized information element, the customized information element includes first indication information and customized content, and the customized content includes an information element bytecode stream, the first indication information indicates the customized format associated with the bytecode stream of the cell.
  • the first message may include at least one first indication information, and each first indication information is used to indicate the customized format associated with the bytecode stream of the cell in the customized content associated with the first indication information.
  • the first information includes customized information element 1 and customized information element 2, wherein the customized information element 1 includes first indication information 1 and customized content 1, and the first indication information 1 indicates customized content 1.
  • the customized information element 2 includes first indication information 2 and customized content 2 , and the first indication information 2 indicates the customized format 2 of the byte code stream of the information element in the customized content 2 .
  • Step 902 the first communication apparatus determines to support the customized content indicated by the first indication information, and parses the customized content indicated by the first indication information.
  • the first communication apparatus supports the customized content indicated by the first indication information. Specifically, the first communication apparatus may have the capability of parsing the bytecode stream in the customized content indicated by the first indication information.
  • the first communication device has the ability to parse the message byte code stream in the customized content indicated by the first indication information, or has the ability to parse the information byte code stream in the customized content indicated by the first indication information. ability.
  • Step 902 may have the following two situations:
  • the first message is a customized message, and there are two examples as follows:
  • Example 1 The first communication device determines, according to the first indication information, that it has the ability to parse the message bytecode stream in the customized content indicated by the first indication information, and the first communication device parses the message bytecode stream.
  • Example 2 The first communication device determines according to the first indication information that it does not have the ability to parse the message bytecode stream in the customized content indicated by the first indication information, and the first communication device sends a failure indication to the second communication device.
  • Case 2 the first message includes customized cells, there are two examples as follows:
  • Example 3 The first communication device determines, according to the first indication information, that it has the ability to parse the bytecode stream of cells in the customized content indicated by the first indication information, and the first communication device parses the existing cells and cells in the first message. bytecode stream.
  • Example 4 The first communication device determines, according to the first indication information, that it does not have the ability to parse the bytecode stream of cells in the customized content indicated by the first indication information, and the first communication device parses existing cells in the first message.
  • Example 4 is different from Example 2, in that the first communication apparatus may parse existing cells in the first message.
  • the existing information elements in the first message can be understood as other information elements other than the customized content (or customized information elements) in the first message, or the non-customized content in the first message, or the information elements in the first message.
  • the first communication device parses the existing information elements in the first message, so as to ensure the communication function predefined by the protocol between the first communication device and the second communication device.
  • the first message may include at least one customized information element, and the first communication device, for each customized information element, determines whether it has the ability to parse the customized information element according to the first indication information in the customized information element.
  • the ability to customize the message bytecode stream in the content in the meta If the first communication device is determined to have the ability to parse the message bytecode stream in the customized content in the customized information element, the implementation in Example 3 above may be referred to. If the first communication device determines that it does not have the ability to parse the message bytecode stream in the customized content in the customized information element, it can skip the customized information element, and then determine whether it can parse the next customized information element. The ability of the message bytecode stream in the customized content in the customized information element, and the ability to parse the existing information element in the first message.
  • determining whether the first communication device supports or does not support the customized content indicated by the first indication information may specifically be judging whether the customized format indicated by the first indication information is configured in the first communication device.
  • the first communication device and the second communication device are both configured with customized formats D1 to D5, and the first indication information is the indication information D1, then the first communication The device determines to support the customized content indicated by the indication information D1. For another example, if the first communication device is configured with the customized format D1, the second communication device is configured with the customized format d1, and the first indication information is the indication information d1, then the first communication device determines that the customization indicated by the indication information d1 is not supported. content.
  • the first communication device or the second communication device records the indication information that each supports the customized format. For example, the first communication device determines whether the first indication information is recorded in its own related capability record, and if so, determines that it supports the customized format. The customized content indicated by the first indication information, otherwise, it is determined that the customized content indicated by the first indication information is not supported.
  • the first communication device determines that it supports/does not support the customized content indicated by the first indication information, which can also be understood as any one or more of the following (1) to (4):
  • the first communication device determines whether the first indication information is supported/unsupported
  • the first communication device determines to support/unsupport the customized format of the customized content indicated by the first indication information
  • the first communication device determines to support/unsupport the customized format associated with the message bytecode stream or the cell bytecode stream in the customized content indicated by the first indication information;
  • the first communication apparatus determines to support/unsupport the customized format indicated by the first indication information.
  • the function of the failure indication in the above example 2 can at least have any one or more of the following (a) to (f):
  • the first message includes the first indication information and the customized content indicated by the first indication information.
  • the first indication information and the customized content indicated by the first indication information may also be carried in different messages It can be understood that the first indication information is carried in the first message, and the customized content indicated by the first indication information is carried in other messages, and the first communication device receives the first message and other messages, from the first message The first indication information is determined in the middle, and the customized content indicated by the first indication information is parsed from the other message according to the first indication information.
  • the first communication device can parse the customized content indicated by the first instruction information according to the first instruction information, and there is no problem that the second communication device does not know how to parse the customized content, which helps to avoid the occurrence of
  • the extension field in the current version is used to implement the customization function, but in the subsequent version, the extension field is defined by the protocol as other meanings, which causes compatibility problems.
  • the first communication device may determine, according to the first indication information, a customized format associated with the bytecode stream in the customized content indicated by the first indication information, and parse the customization indicated by the first indication information according to the customized format.
  • the byte code stream in the converted content does not have the problem that the second communication device does not know which format to use for parsing, which helps to avoid compatibility problems.
  • the first communication device may also send a third message to the second communication device.
  • the first communication device supports the customized format indicated by the second indication information, and the first communication device sends a third message to the second communication device according to the customized format indicated by the second indication information, wherein the third message
  • the customized content consisting of the second indication information and a bytecode stream conforming to the customized format indicated by the second indication information is included.
  • the second communication device receives the third message, determines that the customized content indicated by the second indication information is supported, and parses the customized content indicated by the second indication information.
  • the first communication apparatus parses the first message in the above steps 901 and 902 .
  • the third message may be a response message corresponding to the first message, or may be actively sent by the first communication apparatus to the second communication apparatus.
  • the first communication apparatus sends a third message to the second communication apparatus.
  • the third message is a response message corresponding to the first message, and the customized format indicated by the first indication information and the customized format indicated by the second indication information may be the same or different.
  • the first communication device determines a third message to respond to the second communication device according to the customized format indicated by the first indication information in the received first message, and the customized format indicated by the first indication information is the same as that of the second communication device.
  • the customized format indicated by the second indication information is the same.
  • the first communication device sends the third message to the second communication device.
  • the first communication device may send the third message to the second communication device based on a customized format supported by both the first communication device and the second communication device. Send a third message.
  • the first communication apparatus and the second communication apparatus negotiate the customized formats supported by each.
  • the negotiation process may be initiated by the first communication device, and refer to the schematic flowchart shown in FIG. 10 .
  • Step 1001a the first communication device sends a first request message to the second communication device.
  • the second communication device receives the first request message from the first communication device.
  • the first request message can be understood as a query request, that is, if the first communication device needs to query the second communication device for the customized format supported by the second communication device, the first request message can be sent to the second communication device .
  • the first request message is used to request indication information corresponding to a customized format supported by the second communication device.
  • the first request message is used to request the indication information 1 to the indication information 5 corresponding to the customized format 1 to the customized format 5 supported by the second communication apparatus, respectively.
  • Step 1002a the second communication device sends a second message to the first communication device.
  • the first communication device receives the second message from the second communication device.
  • the second message is used to indicate the customized format supported by the second communication device.
  • the second message is used to indicate that the customized formats supported by the second communication device are customized format 1 to customized format 5.
  • the second message includes at least one indication information, and each indication information in the at least one indication information is used to instruct the second communication apparatus to support the customized format corresponding to the indication information.
  • the second message includes indication information 1 to indication information 5 respectively corresponding to customized formats 1 to 5 supported by the second communication apparatus.
  • the indication information in the second message may be an identifier.
  • the second message includes identifiers 1 to 5, and the identifiers 1 to 5 correspond to the customized formats 1 to 5, respectively.
  • the second message includes a bitmap (bitmap), and each bit in the bitmap is used to indicate whether the second communication apparatus supports the customized format corresponding to the bit. For example, if there are currently customized formats 1 to 10, and the second communication device supports customized formats 1 to 5, the bitmap is "1111100000".
  • step 1001a is optional.
  • the first request message may further carry some indication information, and the first request message is used to instruct the second communication apparatus to determine whether it supports the indication information.
  • the second communication apparatus determines whether to support the indication information in the first request message according to the indication information in the first request message, so as to feed back to the first communication apparatus.
  • the second communication device supports customized format 1 to customized format 5
  • the first request message carries indication information 1
  • the second communication device feeds back to the first communication device information about supporting customized format 1 corresponding to the indication information 1 instruct.
  • the first request message carries the indication information 6
  • the second communication apparatus feeds back to the first communication apparatus a relevant indication that the customized format 6 corresponding to the indication information 6 is not supported.
  • the first communication device determines the customized format supported by the second communication device, and further, the first communication device adopts the customized format supported by both the first communication device and the second communication device, to the second communication device
  • the communication device sends a third message.
  • the negotiation process may also be initiated by the second communication device.
  • the second communication device sends a second request message to the first communication device, where the second request message is used to request the indication information supported by the first communication device, Or it is used to request the first communication device to determine whether it supports the indication information in the second request message.
  • the first communication device sends a response message associated with the second request message to the second communication device, wherein the response message is used to indicate the indication information supported by the first communication device, or used to indicate whether the first communication device supports The indication information in the second request message.
  • Steps 1001b and 1002b are similar to the above-mentioned steps 1001a and 1002a, and will not be repeated here.
  • the first communication device and the second communication device negotiate the customized formats supported by each other, so that the first communication device or the second communication device can have better robustness when processing customized messages or customized information elements, Avoid failure handling when the first communication device or the second communication device receives an unsupported customized message or customized information element.
  • the first communication device is a network device, and the second communication device is a terminal device; or, the first communication device is a terminal device, and the second communication device is a network device; or, the first communication device is a terminal device, and the second communication device is a network device.
  • the communication device is a terminal device; or, the first communication device is a network device, and the second communication device is a network device.
  • the first communication device is a terminal device
  • the second communication device is a network device
  • the first message is a customized message.
  • the first indication information is referred to as the first customized code
  • the first message is referred to as the first customized message.
  • the first customized message may be a customized RRC message, or a customized broadcast message, etc.
  • the customized content in the first customized message is referred to as the first customized content.
  • Step 1101 the network device sends a first customized message to the terminal device.
  • the terminal device receives the first customized message from the network device.
  • the first customized message includes a first customized code and first customized content, and the first customized code is used to indicate the first customized content, or in other words, the first customized code is used to indicate the first customized content
  • the custom format associated with the message bytecode stream in the content is used to indicate the first customized content
  • Step 1102 the terminal device determines whether the first customized content is supported, if yes, executes step 1103, otherwise, executes step 1105.
  • the terminal device determines the first customization code from the first customized message, and determines whether to support the customized format associated with the message bytecode stream in the first customized content.
  • the terminal device is configured with customized format 1 to customized format 5 indicated by customized code 1 to customized code 5 respectively. If the first customized code is customized code 1, the terminal device determines to support customized format 1 associated with the message bytecode stream in the first customized content; if the first customized code is customized code 6, the terminal The device determines that the customized format 6 associated with the message bytecode stream in the first customized content is not supported.
  • Step 1103 the terminal device parses the first customized content according to the first customized code.
  • Step 1104 the terminal device sends a response message to the network device.
  • Step 1105 the terminal device sends a failure indication to the network device.
  • the terminal device may implement a customized format that supports the association of the message bytecode stream in the first customized content by means of version update or the like.
  • the terminal device can acquire the capability of the network device to support the customized code, that is, it also includes: the terminal device sends a first request message to the network device.
  • the first request message is used to request a customized code supported by the network device, and the network device carries the customized code supported by the network device in the second message and sends it to the terminal device.
  • the network device can also actively send the customized code that it supports to the terminal device. Specifically, the network device can broadcast its own support for the customized code to the terminal device, or carry the RRC message sent to the terminal device or the control element (medium access control control element, MAC CE) or downlink of the media access control layer. In the control information (downlink control information, DCI).
  • the control element medium access control control element, MAC CE
  • DCI downlink control information
  • the first request message carries a certain customized code
  • the first request message is used to request the network device to determine whether to support the customized code in the first request message, and the network device determines whether it supports the customized code.
  • the customized code is sent to the terminal device in the response message.
  • the ability of the terminal device to obtain the network device supporting customized codes may refer to the implementation manners in the foregoing steps 1001a and 1002a, which will not be repeated here.
  • the terminal device can determine the corresponding customized content according to the customized code supported by the network device, carry the customized code and customized content in the third message, and send the third message to the network device.
  • the terminal device may also inform the network device of its ability to support customized codes, that is, the terminal device further includes: the terminal device sends the terminal customized code support capability to the network device.
  • the terminal customization code support capability may be that the terminal device actively reports to the network device, or based on the second request message of the network device, determines a response message associated with the second request message and reports it to the network device, where the response message includes the terminal Customized code support capability.
  • the terminal device notifying the network device of the terminal customized code support capability may refer to the implementation manners in the foregoing steps 1001b and 1002b, which will not be repeated here.
  • the terminal device may be referred to as a UE, and the network device may be referred to as a gNB.
  • Figure 12a is a schematic flowchart of the UE actively reporting the customized codes supported by itself to the gNB.
  • Figure 12a is a schematic flowchart of the UE actively reporting the customized codes supported by itself to the gNB.
  • FIG. 12a is a schematic flowchart of the UE actively reporting the customized codes supported by itself to the gNB.
  • step a1 the UE sends a terminal customized code support capability (UE capability of supporting customized Code) to the gNB, wherein the customized code support capability of the terminal includes customized code 1.
  • UE capability of supporting customized Code UE capability of supporting customized Code
  • step a2 the gNB sends a customized message (customizedMessage) to the UE according to the terminal customized code support capability, wherein the format of the bytecode stream in the customized message conforms to the customized format indicated by customized code 1.
  • Step a3 the UE sends a response message to the gNB, wherein the format of the bytecode stream in the response message conforms to the customized format indicated by the customized code 1.
  • FIG. 12b is a schematic flowchart of the gNB querying the capability of the UE to support customized codes.
  • FIG. 12b is a schematic flowchart of the gNB querying the capability of the UE to support customized codes.
  • this example :
  • step b1 the gNB sends a customized code query (customizedCode Query) to the UE.
  • step b2 the UE sends a customized code support (customizedCode Support) to the gNB, wherein the customized code support may be a customized code bitmap (customizedCode bitmap).
  • a customized code support customizedCode Support
  • the customized code support may be a customized code bitmap (customizedCode bitmap).
  • the customized code query is equivalent to the second request message in the above step 1001b
  • the customized code support is equivalent to the response message corresponding to the second request message in the above step 1002b.
  • Figure 12c is a schematic flowchart of the UE replying to a message of parsing failure (customization code failure).
  • parsing failure customization code failure
  • step c1 the gNB sends a customized message to the UE, wherein the format of the bytecode stream in the customized message conforms to the customized format indicated by the customized code 2.
  • step c2 the UE fails to send the customized code to the gNB (customizedCodeFailure).
  • the failure of the customized code is equivalent to the failure indication in step 1105 above.
  • the first communication device is a terminal device
  • the second communication device is a network device
  • the first message is an existing message
  • the existing message includes customized information elements.
  • the first indication information is referred to as the first customized code
  • the customized content in the first message is referred to as the first customized content
  • the customized information element in the first customized content is referred to as the first customized information element.
  • the first customized information element may be an RRC reconfiguration or RRC re-establishment or a customized information element in a system message.
  • Step 1301 the network device sends a first message to the terminal device.
  • the terminal device receives the first message from the network device.
  • the first message includes a first customized code and first customized content, and the first customized code is used to indicate the first customized content, or in other words, the first customized code is used to indicate the first customized content CITIC
  • the custom format associated with the meta bytecode stream is used to indicate the first customized code.
  • Step 1302 the terminal device determines whether the first customized content is supported, if yes, executes step 1303, otherwise, executes step 1305.
  • Step 1303 the terminal device parses the existing information element in the first message according to the protocol specification, and parses the first customized content according to the first customized code.
  • Step 1304 the terminal device sends a first response message to the network device.
  • Step 1305 the terminal device parses the existing cells in the first message according to the protocol.
  • Step 1306 the terminal device sends a second response message to the network device.
  • the terminal device can parse the radio bearer configuration information element and the secondary cell group configuration information element in the RRC reconfiguration, while ignoring the customized information element.
  • the terminal device cannot parse the customized content and cannot realize the customized function, it can guarantee the function specified by the agreement between the network device and the terminal device.
  • the first communication device is a network device
  • the second communication device is a terminal device; or, the first communication device is a terminal device, and the second communication device is a terminal device; or, the first communication device is a network device
  • the second communication device is a network device, which can be understood by referring to the flowcharts shown in FIG. 11 to FIG. 13 . The difference is that the actual messages sent by the first communication device and the second communication device are different.
  • the present application also provides a customized process, which enables the first communication device and the second communication device to communicate in a customized format indicated by the same indication information.
  • the network device sends a downlink message to the terminal device in the customized format indicated by the instruction information, and the terminal device uses the customized format indicated by the instruction information.
  • the format sends an uplink response message to the network device, so that the network device and the terminal device can use the same indication information to identify the customized downlink message and the customized uplink message.
  • the methods provided by the embodiments of the present application are respectively introduced from the perspective of interaction between various devices/apparatuses.
  • the first communication device and the second communication device may include hardware structures and/or software modules, in the form of hardware structures, software modules, or hardware structures plus software modules. realize the above functions. Whether one of the above functions is performed in the form of a hardware structure, a software module, or a hardware structure plus a software module depends on the specific application and design constraints of the technical solution.
  • each functional module in each embodiment of the present application may be integrated into one processor, or may exist physically alone, or two or more modules may be integrated into one module.
  • the above-mentioned integrated modules can be implemented in the form of hardware, and can also be implemented in the form of software function modules.
  • an embodiment of the present application further provides an apparatus 1400 for implementing the function of the first communication apparatus in the above method.
  • the apparatus may be a software module or a system-on-chip.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the apparatus 300 may include: a processing unit 1401 and a communication unit 1402 .
  • the communication unit 1402 is configured to receive a first message from a second communication device, where the first message includes first indication information, where the first indication information is used to indicate customized content; the processing The unit 1401 is configured to determine that the customized content indicated by the first indication information is supported, and parse the customized content indicated by the first indication information.
  • the customized content includes a bytecode stream of customized messages, or the customized content includes a bytecode stream of customized cells.
  • the customized content includes a bytecode stream of customized information elements
  • the processing unit 1401 is further configured to determine that the customized content indicated by the first indication information is not supported, Parse other information elements in the first message except the bytecode stream of the customized information element.
  • the processing unit 1401 is specifically configured to determine a customized format that supports the bytecode stream associated with the customized content indicated by the first indication information, according to the first indication information In the indicated customized format, the bytecode stream in the customized content indicated by the first indication information is parsed.
  • the communication unit 1402 is further configured to receive a second message from the second communication device, where the second message is used to indicate a customized format supported by the second communication device.
  • the second message includes at least one identifier, and each identifier in the at least one identifier is used to indicate that the second communication apparatus supports a customized format corresponding to the identifier; or,
  • the second message includes a bitmap, and each bit in the bitmap is used to indicate whether the second communication apparatus supports the customized format corresponding to the bit.
  • the apparatus supports the customized format indicated by the second indication information
  • the processing unit 1401 is further configured to control the communication according to the customized format indicated by the second indication information
  • the unit 1402 sends the third message to the second communication device, where the third message includes the second indication information and a bytecode stream that conforms to the customized format indicated by the second indication information. Customized content.
  • the customized format indicated by the first indication information is the same as the customized format indicated by the second indication information; the third message is a response corresponding to the first message information.
  • FIG. 15 shows an apparatus 1500 provided in this embodiment of the present application.
  • the apparatus shown in FIG. 15 may be a hardware circuit implementation of the apparatus shown in FIG. 14 .
  • the apparatus can be applied to the flowchart shown in FIG. 9 or FIG. 10 to perform the function of the first communication apparatus in the above method embodiment.
  • FIG. 15 shows only the main components of the device.
  • the apparatus 1500 shown in FIG. 15 includes at least one processor 1520, which is configured to implement any one of the methods in FIG. 9 or FIG. 10 provided in this embodiment of the present application.
  • the apparatus 1500 may also include at least one memory 1530 for storing program instructions and/or data.
  • Memory 1530 and processor 1520 are coupled.
  • the coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units or modules, which may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules.
  • Processor 1520 may cooperate with memory 1530.
  • Processor 1520 may execute program instructions stored in memory 1530 . At least one of the at least one memory may be included in the processor.
  • each step of the above-mentioned method can be completed by a hardware integrated logic circuit in a processor or an instruction in the form of software.
  • the steps of the methods disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware processor, or executed by a combination of hardware and software modules in the processor.
  • the software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art.
  • the storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware. To avoid repetition, detailed description is omitted here.
  • the processor in this embodiment of the present application may be an integrated circuit chip, which has a signal processing capability.
  • each step of the above method embodiments may be completed by a hardware integrated logic circuit in a processor or an instruction in the form of software.
  • the above-mentioned processor can be a general-purpose processor, a digital signal processing circuit (digital signal processor, DSP), an application specific integrated circuit (ASIC), a field programmable gate array (field programmable gate array, FPGA) or other programmable chips.
  • DSP digital signal processing circuit
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • Programming logic devices discrete gate or transistor logic devices, discrete hardware components.
  • a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor.
  • the software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art.
  • the storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware.
  • the memory in this embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically programmable Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • Volatile memory may be random access memory (RAM), which acts as an external cache.
  • RAM random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous DRAM
  • SDRAM double data rate synchronous dynamic random access memory
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous link dynamic random access memory
  • direct rambus RAM direct rambus RAM
  • the apparatus 1500 may also include a communication interface 1510 for communicating with other devices through a transmission medium, so that the apparatus used in the apparatus 1500 may communicate with other devices.
  • the communication interface may be a transceiver, a circuit, a bus, a module, or other types of communication interfaces.
  • the transceiver when the communication interface is a transceiver, the transceiver may include an independent receiver and an independent transmitter; it may also be a transceiver integrating a transceiver function, or an interface circuit.
  • the apparatus 1500 may also include a communication line 1540 .
  • the communication interface 1510, the processor 1520 and the memory 1530 may be connected to each other through a communication line 1540; the communication line 1540 may be a peripheral component interconnect (PCI for short) bus or an extended industry standard architecture (extended industry standard architecture). , referred to as EISA) bus and so on.
  • the communication line 1540 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in FIG. 15, but it does not mean that there is only one bus or one type of bus.
  • the present application provides a communication device including a processor and a communication interface for receiving signals from other communication devices other than the communication device and transmitting to the processor or transferring signals from the communication device.
  • the signal of the processor is sent to other communication devices other than the communication device, and the processor is used to implement the method in the flowchart shown in FIG. 9 or FIG. 10 through a logic circuit or executing code instructions.
  • the present application provides a computer-readable storage medium, in which a computer program or instruction is stored, and when the computer program or instruction is executed by a communication device, the above-mentioned FIG. 9 or FIG. 9 is realized. 10 shows the method in the flowchart.
  • the present application provides a computer program product
  • the computer program product includes a computer program or an instruction, when the computer program or instruction is executed by a communication device, the process shown in the above-mentioned FIG. 9 or FIG. 10 is realized. method in the figure.
  • the present application also provides a system including the aforementioned first communication device and second communication device.
  • the embodiments of the present application may be provided as a method, a system, or a computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, etc.) having computer-usable program code embodied therein.
  • These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory result in an article of manufacture comprising instruction means, the instructions
  • the apparatus implements the functions specified in the flow or flow of the flowcharts and/or the block or blocks of the block diagrams.

Landscapes

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

Abstract

一种通信方法及装置，其中方法包括：第一通信装置接收来自第二通信装置的第一消息，所述第一消息中包括第一指示信息，所述第一指示信息用于指示定制化内容；所述第一通信装置确定支持所述第一指示信息所指示的定制化内容，解析所述第一指示信息所指示的定制化内容。该技术方案用于解决采用当前版本协议中扩展字段实现定制化功能，但在后续版本协议中该扩展字段被定义为其他含义，而引起的兼容性问题。

Description

一种通信方法及装置 技术领域
本申请涉及通信技术领域，尤其涉及一种通信方法及装置。
背景技术
当前第三代伙伴计划(The 3rd Generation Partnership Project，3GPP)的空口(air interface)通信协议(或称为通信标准)通常是基于信令实现的，该信令或信令中信元(information element，IE)可以由协议预先定义。比如，无线资源控制(radio resource control，RRC)协议层中包括由协议预先定义的RRC信令；RRC重配置(RRC reconfiguration)消息中包括由协议预先定义的信元，如无线承载配置(radioBearerConfig)信元、辅小区组(secondaryCellGroup)信元等。
此外，通信协议中会预留专门用于扩展消息或扩展信元的扩展字段，从而在后续版本中利用该扩展字段实现新的功能。该扩展字段还可以用于实现通信的定制化(或私有化)功能，比如，RRC重配置消息中扩展字段用于实现定制化功能如无线资源管理(radio resource management，RRM)。
但是现有技术中，本来被用于实现定制化功能的扩展字段一旦在后续版本协议中被定义为其他含义，则会引起兼容性问题。
发明内容
本申请提供一种通信方法及装置，用于解决采用当前版本协议中扩展字段实现定制化功能，但在后续版本协议中该扩展字段被定义为其他含义，而引起的兼容性问题。
第一方面，本申请提供一种通信方法，包括：
第一通信装置接收来自第二通信装置的第一消息，所述第一消息中包括第一指示信息，所述第一指示信息用于指示定制化内容；所述第一通信装置确定支持所述第一指示信息所指示的定制化内容，解析所述第一指示信息所指示的定制化内容。
基于上述技术方案，第一消息中包括第一指示信息，该第一指示信息用于指示定制化内容，第一通信装置根据第一指示信息，解析第一指示信息所指示的定制化内容，不会存在第二通信装置不知道如何解析定制化内容的问题，有助于避免出现采用当前版本协议中扩展字段实现定制化功能，但在后续版本协议中该扩展字段被定义为其他含义，而引起的兼容性问题。
在一种可能的实现方式中，所述定制化内容中包括定制化消息的字节码流，或所述定制化内容中包括定制化信元的字节码流。
基于上述技术方案，定制化内容可以是消息级别的，也可以是信元级别的，可以通过不同级别的定制化内容实现各种定制化功能。
在一种可能的实现方式中，所述定制化内容中包括定制化信元的字节码流，所述方法还包括：所述第一通信装置确定不支持所述第一指示信息所指示的定制化内容，解析所述第一消息中除所述定制化信元的字节码流以外的其他信元。
基于上述技术方案，第一通信装置解析第一消息中除定制化内容(或定制化信元)以 外的其他信元，保障第一通信装置与第二通信装置之间协议预先定义的通信功能。
在一种可能的实现方式中，所述第一通信装置确定支持所述第一指示信息所指示的定制化内容，解析所述第一指示信息所指示的定制化内容，包括：所述第一通信装置确定支持所述第一指示信息所指示的定制化内容中字节码流相关联的定制化格式，根据所述第一指示信息所指示的定制化格式，解析所述第一指示信息所指示的定制化内容中字节码流。
基于上述技术方案，第一指示信息具体用于指示定制化内容中字节码流相关联的定制化格式，第一通信装置可以根据第一指示信息，确定通过哪种定制化格式解析定制化内容中字节码流。
在一种可能的实现方式中，所述方法还包括：所述第一通信装置接收来自所述第二通信装置的第二消息，所述第二消息用于指示所述第二通信装置支持的定制化格式。
在一种可能的实现方式中，所述第二消息中包括至少一个标识，所述至少一个标识中每个标识用于指示所述第二通信装置支持所述标识对应的定制化格式；或，所述第二消息中包括比特位图，所述比特位图中每个比特位用于指示所述第二通信装置是否支持所述比特位对应的定制化格式。
在一种可能的实现方式中，所述第一通信装置支持第二指示信息所指示的定制化格式，所述方法还包括：所述第一通信装置根据所述第二指示信息所指示的定制化格式，向所述第二通信装置发送所述第三消息，所述第三消息中包括所述第二指示信息和符合所述第二指示信息所指示的定制化格式的字节码流组成的定制化内容。
在一种可能的实现方式中，所述第一指示信息所指示的定制化格式与所述第二指示信息所指示的定制化格式相同；所述第三消息是所述第一消息对应的响应消息。
基于上述技术方案，第一通信装置向第二通信装置发送与第一消息相同定制化格式的第三消息，从而保障第二通信装置能够解析第三消息。此外，可以通过该方式，实现第一通信装置和第二通信装置协商二者通信所使用的定制化格式。
第二方面，本申请提供一种通信装置，该通信装置可以是终端设备，或终端设备中的模块，例如芯片。该通信装置还可以是网络设备，或网络设备中的模块，例如芯片。
所述装置包括：通信单元和处理单元；所述通信单元用于接收来自第二通信装置的第一消息，所述第一消息中包括第一指示信息，所述第一指示信息用于指示定制化内容；所述处理单元用于确定支持所述第一指示信息所指示的定制化内容，解析所述第一指示信息所指示的定制化内容。
在一种可能的实现方式中，所述定制化内容中包括定制化消息的字节码流，或所述定制化内容中包括定制化信元的字节码流。
在一种可能的实现方式中，所述定制化内容中包括定制化信元的字节码流，所述处理单元还用于确定不支持所述第一指示信息所指示的定制化内容，解析所述第一消息中除所述定制化信元的字节码流以外的其他信元。
在一种可能的实现方式中，所述处理单元具体用于确定支持所述第一指示信息所指示的定制化内容中字节码流相关联的定制化格式，根据所述第一指示信息所指示的定制化格式，解析所述第一指示信息所指示的定制化内容中字节码流。
在一种可能的实现方式中，所述通信单元还用于接收来自所述第二通信装置的第二消息，所述第二消息用于指示所述第二通信装置支持的定制化格式。
在一种可能的实现方式中，所述第二消息中包括至少一个标识，所述至少一个标识中 每个标识用于指示所述第二通信装置支持所述标识对应的定制化格式；或，所述第二消息中包括比特位图，所述比特位图中每个比特位用于指示所述第二通信装置是否支持所述比特位对应的定制化格式。
在一种可能的实现方式中，所述装置支持第二指示信息所指示的定制化格式，所述处理单元还用于根据所述第二指示信息所指示的定制化格式，控制所述通信单元向所述第二通信装置发送所述第三消息，所述第三消息中包括所述第二指示信息和符合所述第二指示信息所指示的定制化格式的字节码流组成的定制化内容。
在一种可能的实现方式中，所述第一指示信息所指示的定制化格式与所述第二指示信息所指示的定制化格式相同；所述第三消息是所述第一消息对应的响应消息。
第三方面，本申请提供一种通信装置，包括处理器和通信接口，所述通信接口用于接收来自所述通信装置之外的其它通信装置的信号并传输至所述处理器或将来自所述处理器的信号发送给所述通信装置之外的其它通信装置，所述处理器通过逻辑电路或执行代码指令用于实现上述第一方面或第一方面中的任意一种方法。
第四方面，本申请提供一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机程序或指令，当所述计算机程序或指令被通信装置执行时，实现上述第一方面或第一方面中的任意一种方法。
第五方面，本申请提供一种计算机程序产品，所述计算机程序产品包括计算机程序或指令，当所述计算机程序或指令被通信装置执行时，实现上述第一方面或第一方面中的任意一种方法。
上述第二方面至第五方面中任一方面可以达到的技术效果可以参照上述第一方面中有益效果的描述，此处不再重复赘述。
附图说明
图1为本申请提供的一种通信系统架构示意图；
图2a为本申请提供的一种下行专用控制信道消息的结构示意图；
图2b为本申请提供的另一种下行专用控制信道消息的结构示意图；
图3a为本申请提供的一种RRC重配置消息的结构示意图；
图3b为本申请提供的另一种RRC重配置消息的结构示意图；
图4为本申请提供的一种消息类中定制化消息的结构示意图；
图5a为本申请提供的再一种下行专用控制信道消息的结构示意图；
图5b为本申请提供的一种定制化消息的结构示意图；
图6a为本申请提供的一种广播信道-下行共享信道消息的结构示意图；
图6b为本申请提供的另一种广播信道-下行共享信道消息的结构示意图；
图6c为本申请提供的另一个定制化消息的结构示意图；
图7为本申请提供的一种已有消息中定制化信元的结构示意图；
图8a为本申请提供的再一种RRC重配置消息的结构示意图；
图8b为本申请提供的一种定制化信元的结构示意图；
图9为本申请提供的一种通信方法的流程示意图；
图10为本申请提供的一种协商定制化格式的流程示意图；
图11为本申请提供的一种网络设备和终端设备通信的流程示意图；
图12a、图12b、图12c为本申请提供的具体场景中网络设备和终端设备通信的流程示意图；
图13为本申请提供的另一种网络设备和终端设备通信的流程示意图；
图14为本申请提供的一种通信装置的结构示意图；
图15为本申请提供的另一种通信装置的结构示意图。
具体实施方式
为更好说明本申请实施例，先对本申请实施例所涉及的专业术语、技术解释如下。
1)、本申请实施例中所涉及的终端设备，又可以称之为终端，是用户侧的一种用于接收或发射信号的实体，用于向网络设备发送上行信号，或从网络设备接收下行信号。包括向用户提供语音和/或数据连通性的设备，例如可以包括具有无线连接功能的手持式设备、或连接到无线调制解调器的处理设备。该终端设备可以经无线接入网(radio access network，RAN)与核心网进行通信，与RAN交换语音和/或数据。该终端设备可以包括用户设备(user equipment，UE)、V2X终端设备、无线终端设备、移动终端设备、设备到设备通信(device-to-device，D2D)终端设备、机器到机器/机器类通信(machine-to-machine/machine-type communications，M2M/MTC)终端设备、物联网(internet of things，IoT)终端设备、订户单元(subscriber unit)、订户站(subscriber station)，移动站(mobile station)、远程站(remote station)、接入点(access point，AP)、远程终端(remote terminal)、接入终端(access terminal)、用户终端(user terminal)、用户代理(user agent)、或用户装备(user device)、可穿戴设备、车载设备等。
作为示例而非限定，在本申请实施例中，该终端设备还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备或智能穿戴式设备等，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能头盔、智能首饰等。
而如上介绍的各种终端设备，如果位于车辆上(例如放置在车辆内或安装在车辆内)，都可以认为是车载终端设备，车载终端设备例如也称为车载单元(on-board unit，OBU)。
2)、本申请实施例中所涉及的核心网，可以包括对用户的信令和数据进行处理和转发的网络设备。例如，包括移动性管理功能(access and mobility management function，AMF)、会话管理功能(session management function，SMF)以及用户面网关等核心网设备。其中用户面网关可以是具有对用户面数据进行移动性管理、路由、转发等功能的服务器，一般位于网络侧，如服务网关(serving gateway，SGW)或分组数据网络网关(packet data network gateway，PGW)或用户面网元功能实体(user plane function，UPF)等。AMF以及SMF相当于LTE系统中的移动管理实体(mobility management entity，MME)。AMF主要负责准入方面，SMF主要负责会话管理。当然，核心网中也可以包括其他网元，这里不一一列举。
3)、本申请实施例中所涉及的下一代无线接入网络(next generation radio access network， NG-RAN)，可以包括一个或多个接入网设备。NG-RAN中的接入网设备又可以称为基站，或者RAN节点，或者RAN设备。接入网设备是网络侧的一种用于发射和/或接收信号的实体，作为终端与接入网的其余部分之间的路由器，其中接入网的其余部分可以包括IP网络等。接入网设备还可以协调对空中接口的属性管理。例如，接入网设备可以是LTE中的演进型基站(evolutional Node B，eNB或e-NodeB)，eNB是一种部署在无线接入网中满足4G标准的为终端提供无线通信功能的装置。接入网设备还可以是新无线控制器(new radio controller，NR controller)，可以是5G系统中的gNode B(gNB)，可以是集中式网元(centralized unit)，可以是新无线基站，可以是射频拉远模块，可以是微基站(也称为小站)，可以是中继(relay)，可以是分布式网元(distributed unit)，可以是各种形式的宏基站，可以是传输接收点(transmission reception point，TRP)、传输测量功能(transmission measurement function，TMF)或传输点(transmission point，TP)或者任何其它无线接入设备，或者下一代通信中的基站，但本申请实施例不限于此。
4)、本申请实施例中的术语“系统”和“网络”可被互换使用。术语“多个”是指两个或两个以上。术语“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，字符“/”，如无特殊说明，一般表示前后关联对象是一种“或”的关系。
下面将结合附图，对本申请实施例进行详细描述。
图1示出了本申请的一种可能的系统网络示意图。如图1所示，至少一个终端10与无线接入网(Radio access network，RAN)进行通信。所述RAN至少包括两个基站：基站20和基站30，图中只示出两个基站和一个用户设备UE。所述RAN与核心网络(core network，CN)相连。所述核心网络包括一个或多个核心网设备。可选的，所述CN可以耦合到一个或者更多的外部网络(External Network)，例如英特网(Internet)，公共交换电话网(public switched telephone network，PSTN)等。其中，UE在移动过程中，与无线接入网的连接可以由基站20切换至基站30，此时，基站20可以称为源基站，基站30可以称为目标基站，UE可以通过空中接口(例如Uu接口)与基站通信。
需要说明的是，本申请并不限定于图1所示的系统架构，还可以应用于未来其它的通信系统，例如第六代(the 6th generation，6G)通信系统架构等。并且，本申请所涉及网元，在未来通信系统中，可能保持功能相同，但名称会改变。
通信协议会在当前版本中预留专门用于扩展消息或信元的扩展字段，从而在后续版本中利用该预留的扩展字段实现新的功能。
为方便描述，将当前版本称为第一版本，将后续版本称为第二版本，换言之，第二版本是在第一版本的基础上演进的版本。第一版本协议中，扩展字段在消息类中对应消息扩展位，或扩展字段在已有消息中对应信元扩展位。
结合如图2a和如图2b，以RRC协议中下行专用控制信道消息(downlink dedicated control channel Message，DL-DCCH-Message)在协议中的演进过程为例说明，该下行专用控制信道消息是在下行专用控制信道(dedicated control channel Message，DCCH)上发送的RRC消息的集合。应理解，下行专用控制信道消息为RRC消息类。
如图2a为第一版本协议中下行专用控制信道消息的结构示意图，其中包括一个选择 (choice)结构，该选择结构中包括RRC重配置消息、RRC释放(RRC release)消息、RRC重建立(RRC reestablishment)消息等，该选择结构用于表征从多个消息中选择一个，具体使用时发送端可以选择其中一个来发送。
进一步的，该选择结构中还包括消息扩展位，该消息扩展位具体为预留(spare)或消息类扩展(messageClassExtension)，该消息扩展位具体可作为下行专用控制信道消息中用于扩展RRC消息的扩展位。
如图2b为第二版本协议中下行专用控制信道消息的结构示意图，第二版本协议中新定义一个消息M1，该消息M1占用第一版本协议中消息扩展位。
再结合如图3a和如图3b，以RRC重配置消息在协议中的演进过程为例说明。
如图3a为第一版本协议中RRC重配置消息的结构示意图，其中包括RRC事务标识(rrc-TransactionIdentifier)和关键扩展(criticalExtensions)，关键扩展采用选择结构，该选择结构中包括RRC重配置信元和未来关键扩展(criticalExtensionsFuture)，其中，RRC重配置信元中包括无线承载配置信元、辅小区组信元等。该RRC重配置信元中还包括信元扩展位，该信元扩展位具体为非关键扩展(nonCriticalExtension)，该信元扩展位具体可作为RRC重配置信元中用于扩展RRC信元的扩展位。
如图3b为第二版本协议中RRC重配置消息的结构示意图，第二版本协议中新定义一个信元IE1，该信元IE1占用第一版本协议中信元扩展位。
如上，还可以利用第一版本协议中消息扩展位或信元扩展位实现通信的定制化功能。定制化功能可以理解为非协议规定的通信功能，可以是自行定义的通信功能，比如无线资源管理(radio resource management，RRM)、自组织网络(self-organizing network，SON)、最小化路测(minimization of drive-tests，MDT)等，该定制化功能是在协议规定的通信功能基础上，进一步提升的功能。
示例性的，可以利用第一版本协议中消息扩展位或信元扩展位，实现如图1所示系统架构中通信的定制化功能。有如下第一种情况和第二种情况。
第一种情况，利用第一版本协议中消息扩展位来定制化一个消息，该定制化消息用于实现通信的定制化功能。
结合图2a，可以利用第一版本协议的下行专用控制信道消息中消息扩展位来定制化一个新的消息，该定制化消息用于实现网络设备和终端设备之间通信的定制化功能。
定制化消息具有定制化格式(format)，该定制化格式具体指示该定制化消息中字节码流(octet string或octet stream)的格式。比如，定制化消息采用格式1，则定制化消息中包含符合定制化格式1的字节码流1，再比如，定制化消息采用定制化格式2，则定制化消息中包含符合定制化格式2的字节码流2。
进一步的，定制化格式可以是编解码格式，具体实现中，定制化双方事先协商编解码格式，定制化双方基于协商好的编解码格式进行通信。举例来说，网络设备和终端设备事先协商编解码格式，网络设备向终端设备发送符合该编解码格式的定制化消息，终端设备根据该编解码格式解析该定制化消息。
第二种情况中，利用第一版本协议中已有消息的信元扩展位来定制化一个信元，该定制化信元用于实现通信的定制化功能。
结合图3a，可以利用第一版本协议的RRC重配置消息中信元扩展位来定制化一个新的信元，该定制化信元用于实现网络设备和终端设备之间通信的定制化功能。
定制化信元具有定制化格式，该定制化格式具体指示该定制化信元中字节码流的格式。比如，定制化信元采用定制化格式3，则定制化信元中包含符合定制化格式3的字节码流3，再比如，定制化信元采用定制化格式4，则定制化信元中包含符合定制化格式4的字节码流4。
进一步的，定制化格式可以是编解码格式，具体实现中，定制化双方事先协商编解码格式，定制化双方基于协商好的编解码格式进行通信。举例来说，网络设备和终端设备事先协商编解码格式，网络设备向终端设备发送RRC重配置消息，该RRC重配置消息中包括已有信元和符合该编解码格式的定制化信元，终端设备根据协议解析已有信元，以及根据事先约定的编解码格式解析定制化信元。
本申请中，已有消息理解为在第一版本协议中由协议预先定义的消息，定制化消息理解为占用第一版本中消息扩展位实现定制化功能的自定义消息。已有信元理解为在第一版本协议中由协议预先定义的信元，定制化信元理解为占用第一版本中已有消息中信元扩展位实现定制化功能的自定义信元，此处应理解，占用第一版本中已有消息中信元扩展位定制化信元，该已有消息也可以称为是定制化消息，只是该定制化消息中包括已有信元。
本申请中，字节码流也可以理解为八位字节字符串、八位位组串、字节序列等。字节码流可以理解为用于承载信令的某种格式。定制化格式可以理解为定制化消息或定制化信元中字节码流的编解码格式，定制化格式也可以称为是定制化结构(structure)或定制化类型(type)等。
基于此，若占用第一版本协议中消息扩展位来定制化一个消息，或占用第一版本协议中已有消息的信元扩展位来定制化一个信元，实现通信的定制化功能，而在第二版本协议中该消息扩展位或信元扩展位又被协议定义为其他含义，则会引起兼容性问题。
结合上述第二种情况举例说明，在第一版本协议中，RRC重配置消息中存在信元扩展位IEx，若占用该信元扩展位IEx来定制化信元IEa，且该定制化信元IEa采用定制化格式a。但在第二版本协议中，需要占用该信元扩展位IEx来新定义某个标准化的信元IEb，该信元IEb用于行业内通用功能，且该信元IEb采用格式b，则存在兼容性问题为：采用定制化格式a还是格式b来编解码RRC重配置消息中该位置上的信元。
基于此，本申请提供一种通信方法及装置，用于解决现有技术中，采用第一版本协议中信元扩展位或消息扩展位实现定制化功能，但在第二版本协议中该信元扩展位或消息扩展位被协议定义为其他含义，而引起的兼容性问题。
本申请中，可以在第二版本协议中预先定义专门用于定制化的消息，或在第二版本协议中预先定义已有消息中专门用于定制化的信元，从而可以采用该专门用于定制化的消息，或该专门用于定制化的信元来实现网络设备或终端设备的定制化功能。
第二版本协议中预先定义专门用于定制化的消息，具体为，在某个消息类中定义一个新的消息，该消息专门用于实现通信的各种定制化功能。比如，将该消息定制化为定制化消息a来实现定制化功能a，或将该消息定制化为定制化消息b来实现定制化功能b。
第二版本协议中预先定义专门用于定制化的信元，具体为，在某个已有消息中定义一个新的信元，该信元专门用于实现通信的各种定制化功能。比如，将该信元定制化为定制化信元c来实现定制化功能c，或将该信元定制化为定制化信元d来实现定制化功能d。
应理解，第二版本协议仅预先定义专门用于定制化的消息或专门用于定制化的信元，并未预先定义该专门用于定制化的消息或专门用于定制化的信元中字节码流的格式。进一步的，在进行定制化中，可以定制化该消息中字节码流的格式，或定制化该信元中字节码流的格式。比如，定制该消息为定制化消息a，定制化消息a中字节码流符合定制化格式a。再比如，定制该信元为定制化信元c，定制化信元c中字节码流符合定制化格式c。
进一步的，定制化消息或定制化信元中包括定制化内容，该定制化内容包括符合定制化格式的字节码流。示例性的，定制化消息中定制化内容为消息级别的，可以将该消息级别的定制化内容中字节码流称为消息字节码流。定制化信元中定制化内容为信元级别的，可以将信元级别的定制化内容中字节码流称为信元字节码流。
此外，还可以在第二版本协议中预先定义N个指示信息，N大于1。该指示信息用于指示定制化内容中字节码流所对应的定制化格式。指示信息可以是标识、索引、序号、定制化码等。
示例性的，定制化消息中还可以包括指示信息，该指示信息用于指示定制化内容中字节码流的定制化格式。示例性的，定制化信元中还可以包括指示信息，该指示信息用于指示定制化内容中字节码流的定制化格式。
下面，结合第二版本协议中预先定义指示信息，分情况说明第二版本协议中预先定义专门用于定制化的消息和预先定义已有消息中专门用于定制化的信元的实现方式。
实现方式一，第二版本协议预先定义专门用于定制化的消息。
如图4为本申请示例性提供的一种第二版本协议中消息类的结构示意图，其中，该消息类中包括第一版本协议中的已有消息如消息A、消息B和消息C，……，第二版本协议在该消息类中新定义一个消息用于定制化，该消息比如消息D，该消息D占用第一版本协议中该消息类中的消息扩展位。
比如，定制化该消息D为消息D1，消息D1中包括指示信息D1和定制化内容D1，其中，指示信息D1指示定制化内容D1中字节码流符合定制化格式D1。
同样的，还可以定制化该消息D为消息D2，或消息D3，或消息D4，或消息D5，并分别对应定制化格式D2、定制化格式D3、定制化格式D4和定制化格式D5，以及分别对应指示信息D2、指示信息D3、指示信息D4和指示信息D5。
下面，结合具体实现场景提供两个具体示例：
第1个示例，第二版本协议可以在下行专用控制信道消息中预先定义一个专门的消息用于实现定制化功能，该消息占用如图2a中消息扩展位。示例性的，第二版本协议中下行专用控制信道消息的结构示意图如图5a所示，其中包括定制化消息。
进一步的，如图5b为本申请提供的一种定制化消息的结构示意图。该定制化消息中包括RRC事务标识和关键扩展，关键扩展采用选择结构，该选择结构中包括定制化消息信元和未来关键扩展，定制化消息信元中可以进一步包括定制化码(customizedCode)、消息容器(massageContainer)和非关键扩展(nonCriticalExtension)。其中，定制化码可以理解为指示信息，该定制化码用于指示定制化格式，消息容器可以理解为定制化内容(customizedContent)，消息容器中包含有符合定制化码所指示的定制化格式的字节码流。
第2个示例，如图6a为第一版本协议中广播信道-下行共享信道消息(Broadcast channel-Downlink shared channel-Message，BCCH-DL-SCH-Message)的结构示意图。应理解，广播信道-下行共享信道消息为广播消息类。
示例性的，该广播信道-下行共享信道消息中包含了选择结构，该选择结构中包括系统消息(SystemInformation)、系统消息块(SystemInformationBlock)和消息扩展位。
第二版本协议可以在广播信道-下行共享信道消息中预先定义一个专门的消息用于实现定制化功能，该消息占用如图6a中消息扩展位。示例性的，第二版本协议中广播信道-下行共享信道消息的结构示意图如图6b所示，其中包括定制化消息。
进一步的，如图6c为本申请提供的一种定制化消息的结构示意图。定制化消息采用选择结构，该选择结构中包括定制化系统消息(customizedSystemMessege)信元和未来消息类扩展(messegeClassExtensionFuture)，定制化系统消息信元中可以进一步包括定制化码、消息容器和非关键扩展。
上述第1个示例中，可以在RRC消息类中定制化消息，第2个示例中，可以在广播消息类中定制化消息，此外，本申请也可以在其他消息类中定制化消息，示例性的，可以是在网络设备与网络设备之间的Xn/X2消息类中定制化消息。
实现方式二，第二版本协议中预先定义已有消息中专门用于定制化的信元。
如图7为本申请示例性提供的一种第二版本协议中已有消息的结构示意图，其中，该已有消息中包括第一版本协议中的已有信元如信元a、信元b和信元c，……，第二版本协议在该已有消息中新定义一个信元用于定制化，该信元比如信元d，该信元d可以占用第一版本协议中该已有消息中的信元扩展位。
比如，定制化该信元d为信元d1，信元d1中包括指示信息d1和定制化内容d1，其中，指示信息d1指示定制化内容d1中字节码流符合定制化格式d1。
同样的，还可以定制化该信元d为信元d2，或信元d3，或信元d4，或信元d5，并分别对应定制化格式d2、定制化格式d3、定制化格式d4和定制化格式d5，以及分别对应指示信息d2、指示信息d3、指示信息d4和指示信息d5。
具体实现场景中，第二版本协议可以在RRC重配置消息中预先定义一个专门的信元用于实现定制化功能，该信元占用如图3a中信元扩展位。示例性的，第二版本协议中RRC重配置消息的结构示意图如图8a所示，其中包括定制化信元。
进一步的，如图8b为本申请提供的一种定制化信元的结构示意图。定制化信元中包括定制化码和信元容器。其中，定制化码可以理解为指示信息，该定制化码用于指示定制化格式，信元容器可以理解为定制化内容，信元容器中包含有符合定制化码所指示的定制化格式的字节码流。
如图9所示，为本申请实施例提供的一种通信方法流程示意图，该方法流程如下：
步骤901，第二通信装置向第一通信装置发送第一消息。
相应的，第一通信装置接收来自第二通信装置的第一消息。
其中，该第一消息中包括第一指示信息，第一指示信息是预先定义的N个指示信息中任一个，第一指示信息用于指示与该第一指示信息相关联的定制化内容。
第一指示信息指示定制化内容，具体可以是，第一指示信息指示定制化内容中字节码流相关联的定制化格式，其中，字节码流是定制化中实际内容。
一个示例中，第一消息为消息类中定制化消息，定制化消息包括第一指示信息和定制化内容，该定制化内容包括消息字节码流，第一指示信息指示该消息字节码流相关联的定 制化格式。
另一个示例中，第一消息为已有消息，第一消息包括定制化信元，定制化信元包括第一指示信息和定制化内容，该定制化内容包括信元字节码流，第一指示信息指示该信元字节码流相关联的定制化格式。
本示例中，第一消息中可以包括至少一个定制化信元，针对每个定制化信元来说，该定制化信元中包括第一指示信息和定制化内容，该定制化内容包括信元字节码流，第一指示信息指示该信元字节码流相关联的定制化格式。
也可以说，第一消息中可以包括至少一个第一指示信息，每个第一指示信息用于指示与该第一指示信息相关联的定制化内容中信元字节码流相关联的定制化格式。
示例性的，第一信息中包括定制化信元1和定制化信元2，其中，定制化信元1包括第一指示信息1和定制化内容1，第一指示信息1指示定制化内容1中信元字节码流的定制化格式1。定制化信元2包括第一指示信息2和定制化内容2，第一指示信息2指示定制化内容2中信元字节码流的定制化格式2。
步骤902，第一通信装置确定支持第一指示信息所指示的定制化内容，解析第一指示信息所指示的定制化内容。
第一通信装置支持第一指示信息所指示的定制化内容，具体可以是，第一通信装置具有解析第一指示信息所指示的定制化内容中字节码流的能力。
进一步可以是，第一通信装置具有解析第一指示信息所指示的定制化内容中消息字节码流的能力，或，具有解析第一指示信息所指示的定制化内容中信元字节码流的能力。
步骤902可以有如下两种情况：
情况1，第一消息为定制化消息，有如下两种示例：
示例1，第一通信装置根据第一指示信息确定具有解析第一指示信息所指示的定制化内容中消息字节码流的能力，第一通信装置解析该消息字节码流。
示例2，第一通信装置根据第一指示信息确定不具有解析第一指示信息所指示的定制化内容中消息字节码流的能力，第一通信装置向第二通信装置发送失败指示。
情况2，第一消息中包括定制化信元，有如下两种示例：
示例3，第一通信装置根据第一指示信息确定具有解析第一指示信息所指示的定制化内容中信元字节码流的能力，第一通信装置解析该第一消息中已有信元和信元字节码流。
示例4，第一通信装置根据第一指示信息确定不具有解析第一指示信息所指示的定制化内容中信元字节码流的能力，第一通信装置解析第一消息中已有信元。
需要指出的是，示例4区分于示例2，第一通信装置可以解析第一消息中已有信元。第一消息中已有信元可以理解为，第一消息中除定制化内容(或定制化信元)以外的其他信元，或第一消息中的非定制化内容，或第一消息中的非定制化信元，或第一消息中由协议预先定义的具有固定格式的信元。
通过该方式，第一通信装置解析第一消息中已有信元，保障第一通信装置与第二通信装置之间协议预先定义的通信功能。
需要指出的是，第一消息中可以包括至少一个定制化信元，第一通信装置针对每个定制化信元，根据该定制化信元中第一指示信息，确定是否具有解析该定制化信元中定制化内容中消息字节码流的能力。若第一通信装置确定具有解析该定制化信元中定制化内容中 消息字节码流的能力，则可参照上述示例3中实现方式。若第一通信装置确定不具有解析该定制化信元中定制化内容中消息字节码流的能力，则可以跳过该定制化信元，然后确定是否能够解析该定制化信元的下一个定制化信元中定制化内容中消息字节码流的能力，以及解析第一消息中已有信元。
本申请中，第一通信装置确定支持/不支持第一指示信息所指示的定制化内容，具体可以是判断第一通信装置中是否配置有该第一指示信息所指示的定制化格式。
结合如图4和如图7所示的例子，比如，第一通信装置和第二通信装置均配置有定制化格式D1至定制化格式D5，第一指示信息为指示信息D1，则第一通信装置确定支持指示信息D1所指示的定制化内容。再比如，第一通信装置配置有定制化格式D1，第二通信装置配置有定制化格式d1，第一指示信息为指示信息d1，则第一通信装置确定不支持指示信息d1所指示的定制化内容。
也可以理解，第一通信装置或第二通信装置中记录有各自支持定制化格式的指示信息，比如，第一通信装置确定自身相关能力记录中是否记录有第一指示信息，若是，则确定支持该第一指示信息所指示的定制化内容，否则，确定不支持该第一指示信息所指示的定制化内容。
本申请中，第一通信装置确定支持/不支持第一指示信息所指示的定制化内容，也可以理解为如下(1)至(4)中任一个或多个：
(1)第一通信装置确定支持/不支持第一指示信息；
(2)第一通信装置确定支持/不支持第一指示信息所指示的定制化内容的定制化格式；
(3)第一通信装置确定支持/不支持第一指示信息所指示的定制化内容中消息字节码流或信元字节码流所关联的定制化格式；
(4)第一通信装置确定支持/不支持第一指示信息所指示的定制化格式。
基于此，上述示例2中失败指示的作用至少可以有如下(a)至(f)中任一个或多个：
(a)通知第二通信装置其不支持第一指示信息；
(b)通知第二通信装置其不支持第一指示信息所指示的定制化内容；
(c)通知第二通信装置其不支持第一指示信息所指示的定制化内容的定制化格式；
(d)通知第二通信装置其不支持第一指示信息所指示的定制化内容中消息字节码流或信元字节码流所关联的定制化格式；
(e)通知第二通信装置其不支持第一指示信息所指示的定制化格式；
(f)通知第二通信装置其解析该第一消息中定制化内容失败。
本申请实施例中，第一消息中包括第一指示信息和该第一指示信息指示的定制化内容，此外，第一指示信息和该第一指示信息指示的定制化内容也可以承载于不同消息中，可以理解，第一指示信息承载于第一消息中，而第一指示信息指示的定制化内容承载于其它消息中，第一通信装置接收该第一消息和其它消息，从该第一消息中确定第一指示信息，根据第一指示信息从该其它消息中解析第一指示信息指示的定制化内容。
上述技术方案中，第一通信装置可以根据第一指示信息，解析第一指示信息所指示的定制化内容，不会存在第二通信装置不知道如何解析定制化内容的问题，有助于避免出现采用当前版本中扩展字段实现定制化功能，但在后续版本中该扩展字段被协议定义为其他含义，而引起的兼容性问题。
进一步的，第一通信装置可以根据第一指示信息，确定第一指示信息所指示定制化内容中字节码流相关联的定制化格式，并根据该定制化格式解析第一指示信息所指示定制化内容中字节码流，不会存在第二通信装置不知道采用何种格式解析的问题，有助于避免出现兼容性问题。
本申请中，第一通信装置还可以向第二通信装置发送第三消息。具体的，第一通信装置支持第二指示信息所指示的定制化格式，第一通信装置根据第二指示信息所指示的定制化格式，向第二通信装置发送第三消息，其中，第三消息中包括第二指示信息和符合第二指示信息所指示的定制化格式的字节码流组成的定制化内容。
相应的，第二通信装置接收第三消息，确定支持第二指示信息所指示的定制化内容，解析第二指示信息所指示的定制化内容。该步骤可以参照上述步骤901和步骤902中第一通信装置解析第一消息的具体实现方式。
本申请实施例中，第三消息可以是第一消息对应的响应消息，或者是第一通信装置主动向第二通信装置发送的。
可选的，步骤903，第一通信装置向第二通信装置发送第三消息。第三消息是第一消息对应的响应消息，第一指示信息所指示的定制化格式与第二指示信息所指示的定制化格式可以相同或不同。
示例性的，第一通信装置根据接收到的第一消息中第一指示信息所指示的定制化格式，确定向第二通信装置响应的第三消息，第一指示信息所指示的定制化格式与第二指示信息所指示的定制化格式相同。
本申请实施例中，第一通信装置向第二通信装置发送第三消息，具体可以为，第一通信装置基于第一通信装置和第二通信装置均支持的定制化格式，向第二通信装置发送第三消息。
可选的，第一通信装置和第二通信装置协商各自支持的定制化格式。
一种实现中，协商过程可以是第一通信装置发起的，参照如图10所示的流程示意图。
步骤1001a，第一通信装置向第二通信装置发送第一请求消息。
相应的，第二通信装置接收来自第一通信装置的第一请求消息。
其中，第一请求消息可以理解为查询请求，也即，若第一通信装置需要向第二通信装置查询第二通信装置支持的定制化格式，则可以向第二通信装置发送该第一请求消息。
一种具体实现中，第一请求消息用于请求第二通信装置支持的定制化格式对应的指示信息。比如，第一请求消息用于请求第二通信装置支持的定制化格式1至定制化格式5分别对应的指示信息1至指示信息5。
步骤1002a，第二通信装置向第一通信装置发送第二消息。
相应的，第一通信装置接收来自第二通信装置的第二消息。
第二消息用于指示第二通信装置所支持的定制化格式。举个例子，第二消息用于指示第二通信装置所支持的定制化格式为定制化格式1至定制化格式5。
一种具体实现中，第二消息中包括至少一个指示信息，该至少一个指示信息中每个指示信息用于指示第二通信装置支持该指示信息对应的定制化格式。比如，第二消息中包括第二通信装置支持的定制化格式1至定制化格式5分别对应的指示信息1至指示信息5。
此外，该第二消息中指示信息可以是标识，比如，第二消息中包括标识1至标识5，该标识1至标识5分别对应定制化格式1至定制化格式5。
另一种具体实现中，第二消息中包括比特位图(bitmap)，比特位图中每个比特位用于指示第二通信装置是否支持比特位对应的定制化格式。比如，当前共有定制化格式1至定制化格式10，第二通信装置支持定制化格式1至定制化格式5，则比特位图为“1111100000”。
在某些场景中，步骤1001a为可选步骤。
此外，在该实现方式中，第一请求消息中还可以携带某个指示信息，第一请求消息用于指示第二通信装置确定其是否支持该指示信息。相应的，第二通信装置根据该第一请求消息中指示信息，确定是否支持该第一请求消息中指示信息，从而向第一通信装置反馈。
比如，第二通信装置支持定制化格式1至定制化格式5，第一请求消息中携带指示信息1，第二通信装置向第一通信装置反馈支持该指示信息1对应的定制化格式1的相关指示。再比如，第一请求消息中携带指示信息6，第二通信装置向第一通信装置反馈不支持该指示信息6对应的定制化格式6的相关指示。
基于上述步骤1001a和步骤1002a，第一通信装置确定第二通信装置支持的定制化格式，进一步的，第一通信装置采用第一通信装置和第二通信装置均支持的定制化格式，向第二通信装置发送第三消息。
此外，该协商过程还可以是第二通信装置发起的，步骤1001b，第二通信装置向第一通信装置发送第二请求消息，其中第二请求消息用于请求第一通信装置支持的指示信息，或用于请求第一通信装置确定其是否支持第二请求消息中指示信息。步骤1002b，第一通信装置向第二通信装置发送与第二请求消息相关联的响应消息，其中该响应消息用于指示第一通信装置支持的指示信息，或用于指示第一通信装置是否支持第二请求消息中指示信息。步骤1001b和1002b与上述步骤1001a和1002a类似，不再赘述。
本申请中，第一通信装置和第二通信装置协商各自支持的定制化格式，可以实现第一通信装置或第二通信装置处理定制化消息或定制化信元时有更好的鲁棒性，避免第一通信装置或第二通信装置收到不能支持的定制化消息或定制化信元时引发的错误处理(failure handling)。
本申请中，第一通信装置为网络设备，第二通信装置为终端设备；或，第一通信装置为终端设备，第二通信装置为网络设备；或，第一通信装置为终端设备，第二通信装置为终端设备；或，第一通信装置为网络设备，第二通信装置为网络设备。
下面结合具体实现场景，描述本申请实施例。
在第一个具体实现场景中，第一通信装置是终端设备，第二通信装置是网络设备，第一消息为定制化消息。为方便描述，将第一指示信息称为第一定制化码，将第一消息称为第一定制化消息，第一定制化消息可以是定制化的RRC消息，或定制化的广播消息等，第一定制化消息中的定制化内容称为第一定制化内容。
如图11所示的流程图中：
步骤1101，网络设备向终端设备发送第一定制化消息。
相应的，终端设备接收来自网络设备的第一定制化消息。
其中，第一定制化消息中包括第一定制化码和第一定制化内容，第一定制化码用于指示第一定制化内容，或者说，第一定制化码用于指示第一定制化内容中消息字节码流相关联的定制化格式。
步骤1102，终端设备确定是否支持第一定制化内容，若是，则执行步骤1103，否则， 执行步骤1105。
终端设备从第一定制化消息中确定第一定制化码，并确定是否支持第一定制化内容中消息字节码流相关联的定制化格式。
举例来说，终端设备中配置有定制化码1至定制化码5分别指示的定制化格式1至定制化格式5。若第一定制化码为定制化码1，则终端设备确定支持第一定制化内容中消息字节码流相关联的定制化格式1，若第一定制化码为定制化码6，则终端设备确定不支持第一定制化内容中消息字节码流相关联的定制化格式6。
步骤1103，终端设备根据第一定制化码解析第一定制化内容。
步骤1104，终端设备向网络设备发送响应消息。
步骤1105，终端设备向网络设备发送失败指示。
实际应用中，终端设备可以通过版本更新等方式，实现支持第一定制化内容中消息字节码流相关联的定制化格式。
上述步骤1101至步骤1105的具体实现可参照上述实施例中步骤901至步骤903。
需要指出的是，终端设备可以获取网络设备支持定制化码的能力，也即还包括：终端设备向网络设备发送第一请求消息。
一种实现中，该第一请求消息用于请求网络设备支持的定制化码，网络设备将其支持的定制化码携带于第二消息中发送至终端设备。
在该种实现中，网络设备也可以将自己支持的定制化码主动发送至终端设备。具体的，网络设备可以将自己支持定制化码的广播至终端设备，或者，承载于向终端设备发送的RRC消息或媒体接入控制层的控制单元(medium access control control element，MAC CE)或下行控制信息(downlink control information，DCI)中。
又一种实现中，该第一请求消息中携带某个定制化码，该第一请求消息用于请求网络设备确定是否支持该第一请求消息中的定制化码，网络设备将其是否支持该定制化码的响应消息中发送至终端设备。
终端设备获取网络设备支持定制化码的能力可以具体参照上述步骤1001a和1002a中实现方式，此处不再赘述。
通过上述方式，终端设备可以根据网络设备支持的定制化码，确定对应的定制化内容，并将该定制化码和定制化内容携带于第三消息中，并向网络设备发送该第三消息。
在本申请实施例中，终端设备也可以将自己支持定制化码的能力告知网络设备，也即还包括：终端设备向网络设备发送终端定制化码支持能力。该终端定制化码支持能力可以是终端设备主动上报至网络设备，或者基于网络设备的第二请求消息，确定与第二请求消息相关联的响应消息并上报至网络设备，该响应消息中包含终端定制化码支持能力。
终端设备将终端定制化码支持能力告知网络设备可以具体参照上述步骤1001b和1002b中实现方式，此处不再赘述。
结合上述第一个具体场景，如图12a至12c为本申请示例性提供的三种具体例子。可以将终端设备称为是UE，网络设备称为是gNB。
如图12a为UE将自己支持的定制化码主动上报至gNB的流程示意图。该例子中：
步骤a1，UE向gNB发送终端定制化码支持能力(UE capability of supporting customizedCode)，其中该终端定制化码支持能力中包括定制化码1。
步骤a2，gNB根据终端定制化码支持能力向UE发送定制化消息(customizedMessage)， 其中定制化消息中字节码流的格式符合定制化码1指示的定制化格式。
步骤a3，UE向gNB发送响应消息，其中该响应消息中字节码流的格式符合定制化码1指示的定制化格式。
如图12b为gNB查询UE支持定制化码的能力的流程示意图。该例子中：
步骤b1，gNB向UE发送定制化码查询(customizedCode Query)。
步骤b2，UE向gNB发送定制化码支持(customizedCode Support)，其中定制化码支持可以是定制化码比特位图(customizedCode bitmap)。
此处，定制化码查询相当于上述步骤1001b中第二请求消息，定制化码支持相当于上述步骤1002b中与第二请求消息相对应的响应消息。
如图12c为UE回复解析失败(定制化码失败)的消息的流程示意图。该例子中：
步骤c1，gNB向UE发送定制化消息，其中定制化消息中字节码流的格式符合定制化码2指示的定制化格式。
步骤c2，UE向gNB发送定制化码失败(customizedCodeFailure)。定制化码失败相当于上述步骤1105中失败指示。
在第二个具体实现场景中，第一通信装置是终端设备，第二通信装置是网络设备，第一消息为已有消息，该已有消息中包括定制化信元。
为方便描述，将第一指示信息称为第一定制化码，第一消息中定制化内容称为第一定制化内容，第一定制化内容中定制化信元称为第一定制化信元，第一定制化信元可以是RRC重配置或RRC重建立或系统消息中定制化信元。
如图13所示的流程图中：
步骤1301，网络设备向终端设备发送第一消息。
相应的，终端设备接收来自网络设备的第一消息。
其中，第一消息中包括第一定制化码和第一定制化内容，第一定制化码用于指示第一定制化内容，或者说，第一定制化码用于指示第一定制化内容中信元字节码流相关联的定制化格式。
步骤1302，终端设备确定是否支持第一定制化内容，若是，则执行步骤1303，否则，执行步骤1305。
步骤1303，终端设备根据协议规定解析第一消息中已有信元，以及根据第一定制化码解析第一定制化内容。
步骤1304，终端设备向网络设备发送第一响应消息。
步骤1305，终端设备根据协议规定解析第一消息中已有信元。
步骤1306，终端设备向网络设备发送第二响应消息。
此处，结合如图8a举例来说，终端设备可以解析RRC重配置中无线承载配置信元和辅小区组配置信元，而忽略定制化信元。通过该方式，终端设备虽不能解析定制化内容，不能实现定制化功能，但能保证网络设备和终端设备之间协议规定的功能。
上述步骤1301至步骤1306的具体实现可参照上述实施例中步骤901至步骤903。
此外，本申请中，第一通信装置为网络设备，第二通信装置为终端设备；或，第一通信装置为终端设备，第二通信装置为终端设备；或，第一通信装置为网络设备，第二通信装置为网络设备，均可参照上述如图11至如图13示出流程图来理解。区别在于第一通信装置和第二通信装置发送的实际消息不同。
本申请还提供一种定制化流程，实现第一通信装置和第二通信装置采用相同指示信息所指示的定制化格式进行通信。仍以第一通信装置为终端设备，第二通信装置为网络设备为例说明，网络设备通过指示信息所指示的定制化格式向终端设备发送下行消息，终端设备通过该指示信息所指示的定制化格式向网络设备发送上行响应消息，从而实现网络设备和终端设备采用同一个指示信息标识定制化的下行消息和定制化的上行消息。
本文中描述的各个实施例可以为独立的方案，也可以根据内在逻辑进行组合，这些方案都落入本申请的保护范围中。
上述本申请提供的实施例中，分别从各个设备/装置之间交互的角度对本申请实施例提供的方法进行了介绍。为了实现上述本申请实施例提供的方法中的各功能，第一通信装置和第二通信装置可以包括硬件结构和/或软件模块，以硬件结构、软件模块、或硬件结构加软件模块的形式来实现上述各功能。上述各功能中的某个功能以硬件结构、软件模块、还是硬件结构加软件模块的方式来执行，取决于技术方案的特定应用和设计约束条件。
本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。另外，在本申请各个实施例中的各功能模块可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
与上述构思相同，如图14所示，本申请实施例还提供一种装置1400用于实现上述方法中第一通信装置的功能。例如，该装置可以为软件模块或者芯片系统。本申请实施例中，芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
该装置300可以包括：处理单元1401和通信单元1402。
示例性的，所述通信单元1402用于接收来自第二通信装置的第一消息，所述第一消息中包括第一指示信息，所述第一指示信息用于指示定制化内容；所述处理单元1401用于确定支持所述第一指示信息所指示的定制化内容，解析所述第一指示信息所指示的定制化内容。
在一种可能的实现方式中，所述定制化内容中包括定制化消息的字节码流，或所述定制化内容中包括定制化信元的字节码流。
在一种可能的实现方式中，所述定制化内容中包括定制化信元的字节码流，所述处理单元1401还用于确定不支持所述第一指示信息所指示的定制化内容，解析所述第一消息中除所述定制化信元的字节码流以外的其他信元。
在一种可能的实现方式中，所述处理单元1401具体用于确定支持所述第一指示信息所指示的定制化内容中字节码流相关联的定制化格式，根据所述第一指示信息所指示的定制化格式，解析所述第一指示信息所指示的定制化内容中字节码流。
在一种可能的实现方式中，所述通信单元1402还用于接收来自所述第二通信装置的第二消息，所述第二消息用于指示所述第二通信装置支持的定制化格式。
在一种可能的实现方式中，所述第二消息中包括至少一个标识，所述至少一个标识中每个标识用于指示所述第二通信装置支持所述标识对应的定制化格式；或，所述第二消息中包括比特位图，所述比特位图中每个比特位用于指示所述第二通信装置是否支持所述比特位对应的定制化格式。
在一种可能的实现方式中，所述装置支持第二指示信息所指示的定制化格式，所述处 理单元1401还用于根据所述第二指示信息所指示的定制化格式，控制所述通信单元1402向所述第二通信装置发送所述第三消息，所述第三消息中包括所述第二指示信息和符合所述第二指示信息所指示的定制化格式的字节码流组成的定制化内容。
在一种可能的实现方式中，所述第一指示信息所指示的定制化格式与所述第二指示信息所指示的定制化格式相同；所述第三消息是所述第一消息对应的响应消息。
如图15所示为本申请实施例提供的装置1500，图15所示的装置可以为图14所示的装置的一种硬件电路的实现方式。该装置可适用于图9或图10所示出的流程图中，执行上述方法实施例中第一通信装置的功能。为了便于说明，图15仅示出了该装置的主要部件。
图15所示的装置1500包括至少一个处理器1520，用于实现本申请实施例提供的图9或图10中任一方法。
装置1500还可以包括至少一个存储器1530，用于存储程序指令和/或数据。存储器1530和处理器1520耦合。本申请实施例中的耦合是装置、单元或模块之间的间接耦合或通信连接，可以是电性，机械或其它的形式，用于装置、单元或模块之间的信息交互。处理器1520可能和存储器1530协同操作。处理器1520可能执行存储器1530中存储的程序指令。所述至少一个存储器中的至少一个可以包括于处理器中。
在实现过程中，上述方法的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。为避免重复，这里不再详细描述。
应注意，本申请实施例中的处理器可以是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理电路(digital signal processor，DSP)、专用集成芯片(application specific integrated circuit，ASIC)、现场可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同 步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
装置1500还可以包括通信接口1510，用于通过传输介质和其它设备进行通信，从而用于装置1500中的装置可以和其它设备进行通信。在本申请实施例中，通信接口可以是收发器、电路、总线、模块或其它类型的通信接口。在本申请实施例中，通信接口为收发器时，收发器可以包括独立的接收器、独立的发射器；也可以集成收发功能的收发器、或者是接口电路。
装置1500还可以包括通信线路1540。其中，通信接口1510、处理器1520以及存储器1530可以通过通信线路1540相互连接；通信线路1540可以是外设部件互连标准(peripheral component interconnect，简称PCI)总线或扩展工业标准结构(extended industry standard architecture，简称EISA)总线等。所述通信线路1540可以分为地址总线、数据总线、控制总线等。为便于表示，图15中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
与上述构思相同，本申请提供一种通信装置，包括处理器和通信接口，所述通信接口用于接收来自所述通信装置之外的其它通信装置的信号并传输至所述处理器或将来自所述处理器的信号发送给所述通信装置之外的其它通信装置，所述处理器通过逻辑电路或执行代码指令用于实现上述图9或图10所示出的流程图中方法。
与上述构思相同，本申请提供一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机程序或指令，当所述计算机程序或指令被通信装置执行时，实现上述图9或图10所示出的流程图中方法。
与上述构思相同，本申请提供一种计算机程序产品，所述计算机程序产品包括计算机程序或指令，当所述计算机程序或指令被通信装置执行时，实现上述图9或图10所示出的流程图中方法。
与上述构思相同，本申请还提供一种系统，包括前述的第一通信装置和第二通信装置。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装 置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (19)

  1. 一种通信方法，其特征在于，包括：
    第一通信装置接收来自第二通信装置的第一消息，所述第一消息中包括第一指示信息，所述第一指示信息用于指示定制化内容；
    所述第一通信装置确定支持所述第一指示信息所指示的定制化内容，解析所述第一指示信息所指示的定制化内容。
  2. 如权利要求1所述的方法，其特征在于，所述定制化内容中包括定制化消息的字节码流，或所述定制化内容中包括定制化信元的字节码流。
  3. 如权利要求1或2所述的方法，其特征在于，所述定制化内容中包括定制化信元的字节码流，所述方法还包括：
    所述第一通信装置确定不支持所述第一指示信息所指示的定制化内容，解析所述第一消息中除所述定制化信元的字节码流以外的其他信元。
  4. 如权利要求1至3任一项所述的方法，其特征在于，所述第一通信装置确定支持所述第一指示信息所指示的定制化内容，解析所述第一指示信息所指示的定制化内容，包括：
    所述第一通信装置确定支持所述第一指示信息所指示的定制化内容中字节码流相关联的定制化格式，根据所述第一指示信息所指示的定制化格式，解析所述第一指示信息所指示的定制化内容中字节码流。
  5. 如权利要求1至4任一项所述的方法，其特征在于，所述方法还包括：
    所述第一通信装置接收来自所述第二通信装置的第二消息，所述第二消息用于指示所述第二通信装置支持的定制化格式。
  6. 如权利要求5所述的方法，其特征在于，所述第二消息中包括至少一个标识，所述至少一个标识中每个标识用于指示所述第二通信装置支持所述标识对应的定制化格式；或，所述第二消息中包括比特位图，所述比特位图中每个比特位用于指示所述第二通信装置是否支持所述比特位对应的定制化格式。
  7. 如权利要求1至6任一项所述的方法，其特征在于，所述第一通信装置支持第二指示信息所指示的定制化格式，所述方法还包括：
    所述第一通信装置根据所述第二指示信息所指示的定制化格式，向所述第二通信装置发送所述第三消息，所述第三消息中包括所述第二指示信息和符合所述第二指示信息所指示的定制化格式的字节码流组成的定制化内容。
  8. 如权利要求7所述的方法，其特征在于，所述第一指示信息所指示的定制化格式与所述第二指示信息所指示的定制化格式相同；所述第三消息是所述第一消息对应的响应消息。
  9. 一种通信装置，其特征在于，包括：
    通信单元和处理单元；
    所述通信单元用于接收来自第二通信装置的第一消息，所述第一消息中包括第一指示信息，所述第一指示信息用于指示定制化内容；
    所述处理单元用于确定支持所述第一指示信息所指示的定制化内容，解析所述第一指示信息所指示的定制化内容。
  10. 如权利要求9所述的装置，其特征在于，所述定制化内容中包括定制化消息的字节码流，或所述定制化内容中包括定制化信元的字节码流。
  11. 如权利要求9或10所述的装置，其特征在于，所述定制化内容中包括定制化信元的字节码流，所述处理单元还用于确定不支持所述第一指示信息所指示的定制化内容，解析所述第一消息中除所述定制化信元的字节码流以外的其他信元。
  12. 如权利要求9至11任一项所述的装置，其特征在于，所述处理单元具体用于确定支持所述第一指示信息所指示的定制化内容中字节码流相关联的定制化格式，根据所述第一指示信息所指示的定制化格式，解析所述第一指示信息所指示的定制化内容中字节码流。
  13. 如权利要求9至12任一项所述的装置，其特征在于，所述通信单元还用于接收来自所述第二通信装置的第二消息，所述第二消息用于指示所述第二通信装置支持的定制化格式。
  14. 如权利要求13所述的装置，其特征在于，所述第二消息中包括至少一个标识，所述至少一个标识中每个标识用于指示所述第二通信装置支持所述标识对应的定制化格式；或，所述第二消息中包括比特位图，所述比特位图中每个比特位用于指示所述第二通信装置是否支持所述比特位对应的定制化格式。
  15. 如权利要求9至14任一项所述的装置，其特征在于，所述装置支持第二指示信息所指示的定制化格式，所述处理单元还用于根据所述第二指示信息所指示的定制化格式，控制所述通信单元向所述第二通信装置发送所述第三消息，所述第三消息中包括所述第二指示信息和符合所述第二指示信息所指示的定制化格式的字节码流组成的定制化内容。
  16. 如权利要求15所述的装置，其特征在于，所述第一指示信息所指示的定制化格式与所述第二指示信息所指示的定制化格式相同；所述第三消息是所述第一消息对应的响应消息。
  17. 一种通信装置，其特征在于，包括处理器和通信接口，所述通信接口用于接收来自所述通信装置之外的其它通信装置的信号并传输至所述处理器或将来自所述处理器的信号发送给所述通信装置之外的其它通信装置，所述处理器通过逻辑电路或执行代码指令用于实现如权利要求1至8中任一项所述的方法。
  18. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有计算机程序或指令，当所述计算机程序或指令被通信装置执行时，实现如权利要求1至8中任一项所述的方法。
  19. 一种计算机程序产品，其特征在于，所述计算机程序产品包括计算机程序或指令，当所述计算机程序或指令被通信装置执行时，实现如权利要求1至8中任一项所述的方法。
PCT/CN2020/112284 2020-08-28 2020-08-28 一种通信方法及装置 WO2022041150A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/112284 WO2022041150A1 (zh) 2020-08-28 2020-08-28 一种通信方法及装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/112284 WO2022041150A1 (zh) 2020-08-28 2020-08-28 一种通信方法及装置

Publications (1)

Publication Number Publication Date
WO2022041150A1 true WO2022041150A1 (zh) 2022-03-03

Family

ID=80352468

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/112284 WO2022041150A1 (zh) 2020-08-28 2020-08-28 一种通信方法及装置

Country Status (1)

Country Link
WO (1) WO2022041150A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102111393A (zh) * 2009-12-24 2011-06-29 华为技术有限公司 数据报文传输方法和通信装置
CN106452839A (zh) * 2016-09-05 2017-02-22 杭州华为数字技术有限公司 一种消息上报方法及装置
CN108064088A (zh) * 2018-02-13 2018-05-22 广东欧珀移动通信有限公司 Rrc连接释放方法、终端、接入网设备及存储介质
CN109392178A (zh) * 2017-08-10 2019-02-26 维沃移动通信有限公司 Mpdu传输的方法、用户侧设备和网络侧设备
CN110650533A (zh) * 2019-09-29 2020-01-03 中兴通讯股份有限公司 一种数据传输和信息确定方法、装置和存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102111393A (zh) * 2009-12-24 2011-06-29 华为技术有限公司 数据报文传输方法和通信装置
CN106452839A (zh) * 2016-09-05 2017-02-22 杭州华为数字技术有限公司 一种消息上报方法及装置
CN109392178A (zh) * 2017-08-10 2019-02-26 维沃移动通信有限公司 Mpdu传输的方法、用户侧设备和网络侧设备
CN108064088A (zh) * 2018-02-13 2018-05-22 广东欧珀移动通信有限公司 Rrc连接释放方法、终端、接入网设备及存储介质
CN110650533A (zh) * 2019-09-29 2020-01-03 中兴通讯股份有限公司 一种数据传输和信息确定方法、装置和存储介质

Similar Documents

Publication Publication Date Title
US20230073469A1 (en) Sidelink relay communication method and apparatus, device and medium
US11064557B2 (en) Method and device for establishing radio resource control connection
US20190166526A1 (en) Method for establishing a fronthaul interface, method for performing access for a ue, method and apparatus for performing a handover for a ue, data forwarding method, user equipment and base station
US20210400490A1 (en) Communication method and device
CN111837415B (zh) Eps承载处理方法及用户设备
WO2021164720A1 (zh) 重建立的方法和通信装置
WO2013091161A1 (en) A method and apparatus for mobility robustness optimization
US20220014901A1 (en) Method and apparatus for identifying user equipment capability in sidelink transmission
WO2021159989A1 (zh) 用户设备能力传输方法、信息传输方法及相关产品
WO2020216133A1 (zh) 一种通信方法及设备
US20230254922A1 (en) Multipath transmission method and communication apparatus
US20230035694A1 (en) Service guarantee method and apparatus
CN113228717B (zh) 一种通信方法及装置
US20200404740A1 (en) Multi-destination control message for integrated access and backhaul nodes
US20230090232A1 (en) Terminal device and network device
WO2021000688A1 (zh) 一种发送、接收能力信息的方法及设备
CN115804201A (zh) 集中式单元和分布式单元分离架构中的数据转发
WO2021027942A1 (en) Method and apparatus for capability information transfer
CN115136651A (zh) 切换方法和通信装置
WO2022041150A1 (zh) 一种通信方法及装置
WO2021238318A1 (zh) 一种通信方法及装置
WO2021163832A1 (zh) 数据传输的方法和装置
KR20240032861A (ko) 사이드링크 drx 구성들을 결정하기 위한 방법들 및 장치들
CN114915917B (zh) 传输多播业务的方法及装置
US20230371049A1 (en) Ulticast service transmission method and apparatus

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

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

Country of ref document: EP

Kind code of ref document: A1