WO2024000412A1 - 通信方法和通信装置 - Google Patents

通信方法和通信装置 Download PDF

Info

Publication number
WO2024000412A1
WO2024000412A1 PCT/CN2022/102841 CN2022102841W WO2024000412A1 WO 2024000412 A1 WO2024000412 A1 WO 2024000412A1 CN 2022102841 W CN2022102841 W CN 2022102841W WO 2024000412 A1 WO2024000412 A1 WO 2024000412A1
Authority
WO
WIPO (PCT)
Prior art keywords
iei
type
nas message
ies
carries
Prior art date
Application number
PCT/CN2022/102841
Other languages
English (en)
French (fr)
Inventor
卢飞
杨皓睿
Original Assignee
Oppo广东移动通信有限公司
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 Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to PCT/CN2022/102841 priority Critical patent/WO2024000412A1/zh
Priority to CN202280091296.5A priority patent/CN118679765A/zh
Publication of WO2024000412A1 publication Critical patent/WO2024000412A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/02—Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]

Definitions

  • the present application relates to the field of communication technology, and more specifically, to a communication method and a communication device.
  • the terminal device After the terminal device is connected to the core network, it can interact with the core network device in non-access stratum (NAS) messages.
  • the NAS message can contain multiple information elements (IEs) to indicate certain characteristics. For example, it can contain extended protocol discriminator IE, security header type IE, packet data unit (PDU) session status IE, etc. .
  • IEs information elements
  • the type of IE can be identified using an information element identifier (IEI). For example, when the IEI hexadecimal value is 50, it can indicate that the type of IE is a PDU session state IE.
  • This application provides a communication method and communication device. Each aspect involved in this application is introduced below.
  • a communication method including: a first device receiving a non-access layer NAS message sent by a second device; wherein the NAS message includes a first information unit IE, and the first IE includes a first The information unit identifies IEI, and the first IE carries the second IE.
  • a communication method including: a second device sending a non-access layer NAS message to a first device; wherein the NAS message includes a first information unit IE, and the first IE includes first information The unit identifier IEI, the first IE carries the second IE.
  • a communication device is provided.
  • the device is applied to a first device.
  • the device includes a processing module and a receiving module.
  • the processing module is configured to receive a non-access message sent by a second device through the receiving module.
  • layer NAS message ; wherein the NAS message includes a first information unit IE, the first IE includes a first information unit identifier IEI, and the first IE carries a second IE.
  • a communication device is provided.
  • the device is applied to a second device.
  • the device includes a processing module and a sending module.
  • the processing module is used to send a non-access layer to the first device through the sending module.
  • NAS message ; wherein the NAS message includes a first information unit IE, the first IE includes a first information unit identifier IEI, and the first IE carries a second IE.
  • a first device including a processor, a memory and a communication interface, the memory is used to store one or more computer programs, the processor is used to call the computer program in the memory so that the The first device performs some or all of the steps of the method of the first aspect.
  • a second device including a processor, a memory, and a communication interface.
  • the memory is used to store one or more computer programs.
  • the processor is used to call the computer program in the memory so that the The second device performs some or all of the steps of the method of the second aspect.
  • embodiments of the present application provide a communication system, which includes the above-mentioned first device and/or second device.
  • the system may also include other devices that interact with the first device or the second device in the solution provided by the embodiments of the present application.
  • embodiments of the present application provide a computer-readable storage medium that stores a computer program, and the computer program causes the first device or the second device to perform one of the methods of the above aspects. Some or all of the steps.
  • embodiments of the present application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to cause the first device or The second device performs some or all of the steps in the methods of the above aspects.
  • the computer program product can be a software installation package.
  • embodiments of the present application provide a chip, which includes a memory and a processor.
  • the processor can call and run a computer program from the memory to implement some or all of the steps described in the methods of the above aspects.
  • the first IE carries the second IE.
  • the type of the second IE can be determined based on the first IEI included in the first IE.
  • determining the type of the internal IE based on the IEI of the nested external IE can expand the number of IEs identified by the IEI, thereby solving the problem of insufficient IEI.
  • Figure 1 is an example diagram of a network architecture applicable to embodiments of the present application.
  • Figure 2 is an example diagram of IE's encoding method.
  • Figure 3 is another example diagram of the encoding method of IE.
  • Figure 4 is an example diagram of a communication system applicable to embodiments of the present application.
  • Figure 5 is a schematic flowchart of a communication method provided by an embodiment of the present application.
  • FIG. 6 is an example diagram of the encoding method of the first IE provided by an embodiment of the present application.
  • Figure 7 is an example diagram of the encoding method of the first IE provided by another embodiment of the present application.
  • Figure 8 is an example diagram of the encoding method of the first IE provided by yet another embodiment of the present application.
  • Figure 9 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • Figure 10 is a schematic structural diagram of a communication device provided by another embodiment of the present application.
  • Figure 11 is a schematic structural diagram of a device provided by an embodiment of the present application.
  • the technical solutions of the embodiments of this application can be applied to various communication systems, such as: fifth generation (5th generation, 5G) systems or new radio (NR) systems, long term evolution (long term evolution, LTE) systems, LTE Frequency division duplex (FDD) system, LTE time division duplex (TDD) system, etc.
  • 5G fifth generation
  • NR new radio
  • LTE long term evolution
  • FDD Frequency division duplex
  • TDD time division duplex
  • future communication systems such as the sixth generation mobile communication system, satellite communication systems, and so on.
  • Figure 1 shows an example diagram of a network architecture.
  • the network architecture shown in Figure 1 takes the 5G system as an example.
  • the network architecture can include three parts, namely the terminal equipment part, the data network (DN) part and the operator network part.
  • the operator network may include one or more of the following functional entities: access network (AN) equipment, user plane function (UPF) entity, access and mobility management function (access and mobility management function (AMF) entity, session management function (SMF) entity, policy control function (PCF) entity, application function (AF) entity, network slice selection function (network slice selection) function (NSSF) entity, authentication server function (AUSF) entity, unified data management (UDM) entity, etc.
  • the part other than the access network equipment part can be called the core network part
  • the functional entities of the core network part can be called core network equipment.
  • Terminal equipment can also be called user equipment (UE), access terminal, subscriber unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communications device, user agent or user device.
  • the terminal device in the embodiment of this application may be a device that provides voice and/or data connectivity to users, and may be used to connect people, things, and machines, such as handheld devices with wireless connection functions, vehicle-mounted devices, etc.
  • the terminal device in the embodiment of the present application can be a mobile phone (mobile phone), a tablet computer (Pad), a notebook computer, a handheld computer, a mobile internet device (mobile internet device, MID), a wearable device, a virtual reality (virtual reality, VR) equipment, augmented reality (AR) equipment, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, smart Wireless terminals in smart grid, wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home, etc.
  • the UE may be used to act as a base station.
  • a UE may act as a scheduling entity that provides sidelink signals between UEs in V2X or D2D, etc.
  • cell phones and cars use sidelink signals to communicate with each other.
  • Cell phones and smart home devices communicate between each other without having to relay communication signals through base stations.
  • Access network equipment can be used to provide network access functions for authorized terminal equipment in a specific area, and can use transmission channels of different qualities according to the level of the terminal equipment, business needs, etc. Access network equipment can manage wireless resources, provide access services to terminal equipment, and then complete the forwarding of control signals and data between terminal equipment and the core network.
  • the access network device may be a device in a wireless network.
  • Access network equipment can also be called radio access network (RAN) equipment or network equipment.
  • RAN radio access network
  • access network equipment can be a base station.
  • the access network device in the embodiment of this application may refer to a radio access network (radio access network, RAN) node (or device) that connects the terminal device to the wireless network.
  • radio access network radio access network, RAN
  • Base stations can broadly cover various names as follows, or be replaced with the following names, such as: Node B (NodeB), evolved base station (evolved NodeB, eNB), next generation base station (next generation NodeB, gNB), relay station, Access point, transmission point (transmitting and receiving point, TRP), transmitting point (TP), main station MeNB, secondary station SeNB, multi-standard wireless (MSR) node, home base station, network controller, access node , wireless node, access point (AP), transmission node, transceiver node, base band unit (BBU), radio remote unit (Remote Radio Unit, RRU), active antenna unit (active antenna unit) , AAU), radio head (remote radio head, RRH), central unit (central unit, CU), distributed unit (distributed unit, DU), positioning node, etc.
  • NodeB Node B
  • eNB evolved base station
  • next generation NodeB next generation NodeB, gNB
  • relay station Access point
  • transmission point
  • the base station may be a macro base station, a micro base station, a relay node, a donor node or the like, or a combination thereof.
  • a base station may also refer to a communication module, modem or chip used in the aforementioned equipment or devices.
  • the base station can also be a mobile switching center and a device that undertakes base station functions in device-to-device D2D, vehicle-to-everything (V2X), machine-to-machine (M2M) communications, and in 6G networks.
  • Base stations can support networks with the same or different access technologies. The embodiments of this application do not limit the specific technology and specific equipment form used by the access network equipment.
  • Base stations can be fixed or mobile.
  • a helicopter or drone may be configured to act as a mobile base station, and one or more cells may move based on the mobile base station's location.
  • a helicopter or drone may be configured to serve as a device that communicates with another base station.
  • the access network device in the embodiment of this application may refer to a CU or a DU, or the access network device includes a CU and a DU.
  • gNB can also include AAU.
  • Access network equipment and terminal equipment can be deployed on land, indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; they can also be deployed on aircraft, balloons and satellites in the sky. In the embodiments of this application, there are no limitations on the scenarios in which the access network equipment and terminal equipment are located.
  • UPF is the user plane function in the core network and can be responsible for the forwarding and reception of user data (such as service data flows) in terminal equipment. For example, UPF can receive user data from the DN and transmit it to the terminal device through the access network device; or, UPF can also receive user data from the terminal device through the access network device and then forward it to the DN.
  • the transmission resources and scheduling functions in UPF that provide services to terminal devices are managed and controlled by SMF.
  • UPF can be divided into intermediate UPF (intermediate-UPF, I-UPF) and anchor UPF (anchor-UPF, A-UPF).
  • I-UPF is connected to the access network
  • A-UPF is the UPF of the session anchor
  • A-UPF can also be called PDU session anchor (PSA).
  • PSA PDU session anchor
  • AMF is the mobility management function in the core network. It can be used to implement other functions of the mobility management entity (MME) besides session management, such as legal interception or access authorization. (or authentication) and other functions. In some embodiments, in addition to performing mobility management on the terminal device, the AMF may also be responsible for forwarding session management related messages between the terminal device and the SMF.
  • MME mobility management entity
  • the AMF may also be responsible for forwarding session management related messages between the terminal device and the SMF.
  • SMF is the session management function in the core network. It is mainly responsible for session management, Internet protocol (IP) address allocation and management of terminal devices, selection of manageable user plane functions, policy control, or charging function interfaces. endpoint and downlink data notification, configure routing information for user plane functions, etc.
  • IP Internet protocol
  • PCF is the policy management function in the core network and can be responsible for formulating policies related to mobility management, session management, and charging of terminal devices. Specifically, PCF can provide policy rule information, etc., for functional entities of the control plane (such as AMF, SMF entities, etc.) to manage and control the mobility management, session management, etc. of the terminal device.
  • control plane such as AMF, SMF entities, etc.
  • AF entity mainly supports interaction with the 3rd generation partnership project (3GPP) core network to provide services, for example, affecting data routing decisions, policy control functions, or providing some third-party services to the network side.
  • 3GPP 3rd generation partnership project
  • AF can be mainly used to convey the requirements of the application side to the network side.
  • AF can be understood as a third-party server, for example, an application server in the Internet, which provides relevant service information, including providing service quality requirement information corresponding to the service to PCF, and sending user plane data of the service to A-UPF. information.
  • the AF may also be a content provider (CP).
  • CP content provider
  • DN refers to the network that can be used to provide transmitted data.
  • DN can be a private network, such as a local area network, or an external network that is not controlled by the operator, such as the Internet. It can also be a proprietary network jointly deployed by operators, such as providing IP multimedia network subsystem (IP multimedia core). network subsystem, IMS) service network.
  • IP multimedia core IP multimedia core
  • IMS IP multimedia core
  • each of the above functional entities in the core network can also be called a network element, and this application is not limited to this.
  • the UPF entity may also be called a UPF network element
  • the AMF entity may also be called an AMF network element, etc.
  • the xx functional entity or xx network element can also be directly referred to as xx.
  • the UPF entity or UPF network element
  • the AMF entity or AMF network element
  • the xx (such as UPF, AMF, etc.) mentioned in the embodiment of this application may refer to the xx entity or the xx network element, which will not be described again later.
  • the terminal device can connect to the AN through the Uu interface for access stratum (AS), exchange AS messages and wireless data transmission; the terminal device can connect to the AMF for the non-access stratum (NAS) through the N1 interface.
  • AS access stratum
  • NAS non-access stratum
  • AN can connect to AMF through the N2 interface, which is used to transmit wireless bearer control information from the core network side to the AN;
  • UPF can transmit data to AN through the N3 interface, and transmit data to the DN through the N6 interface wait.
  • the interfaces connecting other parts or functional entities can be seen in Figure 1 and will not be described again here.
  • network architecture shown above is only an illustrative description, and the network architecture applicable to the embodiments of the present application is not limited thereto. Any network architecture that can realize the functions of each functional entity mentioned above is applicable to the embodiments of the present application.
  • access network equipment, AMF, SMF, UPF, PCF, etc. shown in Figure 1 are just names, and the names do not limit the equipment itself.
  • entities corresponding to access network equipment, AMF, SMF, UPF, PCF, etc. may also have other names, which are not specifically limited in the embodiments of this application.
  • interface names between the functional entities shown in Figure 1 are just an example.
  • the interface names between the functional entities in the specific implementation can also be other names, such as the interface names between the functional entities in the 6G network. , the embodiments of this application do not specifically limit this.
  • the terminal device After the terminal device is connected to the core network through the access network device (for example, a base station), the terminal device can communicate with the core network device.
  • the communication between the terminal device and the access network device can be understood as AS interaction, which can be realized by sending and receiving AS messages between the terminal device and the access network device.
  • Communication; the communication between terminal equipment and core network equipment can be understood as NAS interaction, which can realize communication between terminal equipment and core network equipment by sending and receiving NAS messages.
  • the terminal device can send a registration request message to the core network device.
  • the core network device can accept the registration request message of the terminal device, the core network device can send a registration request message to the core network device.
  • the terminal device returns a registration accept message.
  • Both the registration request message and the registration accept message can be understood as NAS messages, which are used for communication between the terminal device and the core network device.
  • NAS messages between the terminal device and the core network device can be forwarded by the access network device in a transparent transmission manner.
  • a NAS message may contain multiple information elements (IEs) to indicate certain features.
  • information elements may also be called information elements, information elements, etc., which are not limited in this application.
  • the NAS message may include an extended protocol discriminator (extended protocol discriminator) IE, and the extended protocol discriminator may be used to indicate whether the NAS message is a 5GMM message or a 5GSM message.
  • the NAS message may contain a security header type (security header type) IE, which may be used to indicate characteristics related to the security protection of 5G mobility management (5G mobility management, 5GMM) messages, such as the security protection of 5GMM messages. Relevant control information, etc.
  • the NAS message may include packet data unit (PDU) session status (PDU session status) IE, PDU session reactivation result (PDU session reactivation result) IE, PDU session reactivation result error reason (PDU session reactivation result error cause)IE, etc.
  • PDU session status PDU session status
  • PDU session reactivation result PDU session reactivation result
  • PDU session reactivation result error cause PDU session reactivation result error cause
  • some IEs are mandatory IEs for the NAS message, and some IEs are optional IEs for the NAS message.
  • the extended protocol discriminator IE and security header type IE mentioned above can be mandatory IEs for NAS messages, while PDU session status IE, PDU session reactivation result IE, etc. can be optional IEs for NAS messages. This application implements This example is not limiting.
  • the type of each IE may be different.
  • the type of IE can be used to indicate the function or purpose of the IE.
  • the type of IE corresponding to the extended protocol discriminator IE mentioned above is the extended protocol discriminator IE
  • the type of IE corresponding to the security header type IE is the security header type.
  • the type of IE corresponding to IE and PDU session status IE is PDU session status IE, etc.
  • IE can encode in different formats.
  • IE can use format V for encoding, where V represents value and represents the actual value of IE.
  • IE can be encoded using format LV or format LV-E, where L represents length, indicating the length information of the value; V represents value, indicating the actual value of the IE, and LV-E refers to the extended LV Format.
  • IE can be encoded using format TLV or format TLV-E, where T represents type, indicating the type of IE; L represents length, indicating the length information of the value; V represents value, indicating the actual value of the IE , TLV-E refers to the extended TLV format.
  • T type
  • the type of IE may be determined (or identified) using an information element identifier (IEI).
  • IEI information element identifier
  • an IEI value of 50 can indicate that the type of the IE is a PDU session status IE
  • an IEI value of 26 can indicate that the type of the IE is a PDU session reactivation result IE
  • the IEI value is 72, it means that the type of the IE is PDU session reactivation result error cause IE, etc.
  • the length of L (the byte size occupied by L) its corresponding IE can be divided into type 4 IE and type 6 IE.
  • this IE when the length of L is fixed and represented by 1 octet, this IE can be called a type 4 IE; when the length of L is fixed and represented by 2 octets, this IE can be called a type 4 IE.
  • type 6 IE For type 6 IE.
  • type 6 IE it can be encoded using format LV-E or format TLV-E.
  • Figure 2 shows the format LV- E is a type 6 IE encoded.
  • Figure 3 shows a type 6 IE encoded in format TLV-E.
  • LI length information
  • the length of L of type 6 IE is fixed and uses 2 octets. section, and LI is located in front of V when encoding, where the length of V can be any value from 0 to 65535 octets, for example.
  • the format TLV-E is used for encoding, the IEI used to identify the type of IE is located in front of LI, which is represented by one octet.
  • IEI can be used to identify the type of IE. Since IEI is currently represented by one octet, the number of IEIs it can represent is limited. With the rapid development of communication systems, some new features may continue to be introduced. For example, some new features may be introduced in 5G systems, 6G systems or future communication systems. These new features may be carried using new IE, so that This may cause more and more IEs to be carried in NAS messages, which may result in insufficient use of the current IEIs.
  • TLV-E which is a type 6 IE, that is, the 2 bytes after the 1 byte used to represent IEI are the bytes representing L (Bit 8 of the IEI octet set to "0" and bits 7 to 5 set to "1" indicates a TLV-E formatted type 6 IE, i.e. the following two octets are length octets).
  • the value of IEI is 0111xxxx (expressed as 70-7F in hexadecimal), which means that the format of the IE is TLV-E, type 6 IE, and the length of the IE is 2 octets. Festival. It can be seen that there are only 16 values of IEI used to identify type 6 IE (70-7F). With the increase of new features, the value range of this IEI is likely to be insufficient.
  • Table 1 takes the NAS message as a registration acceptance message as an example.
  • the registration acceptance message is sent by the core network device to the terminal device.
  • the registration acceptance message contains many IEs, where each row in Table 1 represents an IE.
  • IEI IEI
  • IEIs such as the optional IEs that exist in the registration acceptance message
  • IEIs such as the optional IEs that exist in the registration acceptance message, among which different IEIs Used to indicate that the type of the IE is different.
  • an IEI value of 70 indicates that the type of the IE is an NSSRG information (NSSRG information) IE
  • an IEI value of 7A indicates that the type of the IE is an extended emergency number list (extended emergency number list). )IE.
  • some IEs can be encoded in Format V, such as the Extended Protocol Identifier IE; some IEs can be encoded in Format TLV, such as PDU Session Status IE; some IEs can be encoded in TLV-E, such as the Extended Emergency Number List IE. etc.
  • Format V such as the Extended Protocol Identifier IE
  • TLV such as PDU Session Status IE
  • TLV-E such as the Extended Emergency Number List IE.
  • the value range of the length of the IE may be different.
  • the length of the IE refers to the byte size occupied by the entire IE.
  • the length of the IE includes L ( length) and V (value); when the IE is encoded using the format TLV-E, the length of the IE includes the byte size occupied by the IEI, L, and V parts.
  • the IEI of type 6 (70-7F in hexadecimal) has basically been used up. If there is a new IE, the IEI of type 6 needs to be used. At this time, the value of type 6 IEI is no longer sufficient. Therefore, how to extend IEI is an issue that needs to be solved urgently.
  • IEI can be extended by expanding the range of IEI values.
  • the length of the IEI can be extended.
  • the length of the IEI is currently represented by 1 octet.
  • the length of the IEI can be extended to be represented by 2 octets, or extended to more words. Festival.
  • the terminal equipment needs to indicate to the network side (core network equipment) that it supports the expanded IEI.
  • the terminal equipment needs to report a capability indication to indicate that it supports the expanded IEI. This is very important to the terminal.
  • the implementation and modification of the device is complicated; on the other hand, when the network side sends NAS messages to the terminal device, it also needs to check the capabilities of the terminal device and generate NAS message content based on different terminal device capabilities, which undoubtedly increases the implementation complexity on the network side. .
  • embodiments of the present application provide a communication method and communication device, which can solve the problem of insufficient use of IEI.
  • the technical solution of the embodiment of the present application does not require the terminal device to report capabilities, resulting in smaller implementation changes of the terminal device and lower implementation complexity on the network side.
  • FIG. 4 shows a communication system 40 provided by an embodiment of the present application.
  • the communication system 40 includes a first device 410 and a second device 420.
  • the first device 410 and the second device 420 can communicate and exchange NAS messages.
  • the first device 410 can send a NAS message to the second device 420, and the second device 420 can receive the NAS message sent by the first device 410 for subsequent processing; or the second device 420 can send a NAS message to the first device 410.
  • the first device 410 can receive the NAS message sent by the second device 420 for subsequent processing.
  • Communication between the first device 410 and the second device 420, and exchanging NAS messages may refer to direct communication and exchanging NAS messages between the first device and the second device; it may also refer to the first device and the second device communicating through Communication and exchange of NAS messages can be carried out through forwarding of other devices. For example, communication can be carried out through transparent transmission of other devices, which is not specifically limited in the embodiments of the present application.
  • the first device 410 may be a terminal device, and the second device 420 may be a core network device.
  • the first device may be a core network device, and the second device may be a terminal device.
  • the embodiments of the present application are not limited to this, as long as NAS messages can be exchanged between them.
  • the terminal device may be any terminal device mentioned above, and the core network device may refer to a device located in the core network, such as the AMF, SMF, PCF, etc. mentioned above, which is not limited in the embodiments of this application.
  • the communication system provided by the embodiment of the present application can be applied in the network architecture as shown in Figure 1, which is not limited by the embodiment of the present application.
  • the above-mentioned first device may be a terminal device, and the second device may be an AMF in the core network; or the first device The device may be an AMF in the core network, the second device may be a terminal device, and so on.
  • Figure 5 is a schematic flowchart of a communication method provided by an embodiment of the present application. The method shown in FIG. 5 is described from the perspective of interaction between a first device and a second device.
  • the first device and the second device may be the first device 410 and the second device 420 in FIG. 4 .
  • the first device may be a terminal device and the second device is a core network device; or the first device may be a core network device and the second device is a terminal device.
  • the communication method provided by the embodiment of the present application may include step S510, which step will be described in detail below.
  • step S510 the second device sends a NAS message to the first device.
  • the second device can directly send the NAS message to the first device.
  • the second device may forward the NAS message to the first device through other devices.
  • the second device can directly send a NAS message to the first device through the N1 interface; or, the second device can also send a NAS message through the access network device (
  • the base station sends a NAS message to the first device through forwarding, where the access network device can forward the NAS message in a transparent transmission manner.
  • the NAS message may be a registration request message or a registration acceptance message, etc.
  • the second device may be a terminal device, and the first device may be a core network device.
  • the NAS message may also be a registration rejection message or other NAS messages, which is not limited in the embodiments of the present application.
  • the NAS message may include the first IE.
  • the first IE may be an optional IE, that is, the presence of the first IE is optional. That is to say, in some NAS messages, the first IE may be included; in some NAS messages, the first IE may not be included.
  • multiple NAS messages may be exchanged between the first device and the second device, such as NAS message #1 and NAS message #2.
  • the NAS message #1 may include the first IE, and the NAS message #1 may include the first IE.
  • the first IE may not be included, and the embodiment of the present application is not limited to this.
  • the embodiment of the present application does not limit the value range of the length of the first IE.
  • the length of the first IE may be 3-n octets. section, n is any value greater than or equal to 3 and less than or equal to 65535.
  • the first IE may include a first IEI, and the first IEI may be used to indicate a type (type, T) of the first IE.
  • the type of the first IE can be used to represent the function or purpose of the first IE. For example, when the function of the first IE is to serve as a container to carry other IEs, the type of the first IE can be understood as a NAS message container. Or it can be understood as an IE container. Table 2 gives an example in which the first IE is included in the NAS message. As shown in Table 2, the type of the first IE is a NAS message container, and the first IE is an optional IE.
  • Table 3 gives another example of the first IE included in the NAS message.
  • the type of the first IE is an Extended Type 6 IE container (Extended Type 6 IE container), and the first IE is optional. ie.
  • the first IE includes the first IEI
  • the first IE is encoded using the format TLV or TLV-E.
  • the first IE may also include other parts or fields, such as a first length (L), a first value (value, V), etc., wherein the first value part is used to indicate the actual content or actual value of the first IE, and the first length is used to indicate the length information of the first value.
  • the length of the first IEI and/or the first length may be fixed, where the length of the first IEI or the first length may refer to the first IEI or the first length.
  • the length in bytes. That is, the first IEI and/or the first length may be represented using a fixed byte size, for example, the first IEI may be represented using 1 octet, and the first length may be represented using 1 octet or 2 represented by octets.
  • the length of the first value can be changed.
  • the length of the first value can be any value from 0 to 65535 octets, where the The length of a value may be specified by the first length.
  • Figure 6 is an example of the encoding method of the first IE given by the embodiment of the present application.
  • the first IE includes a first IEI, a first length and a first value, where the first IEI is represented by 1 represented by octets (see byte 1 shown in Figure 6), the first length is represented by 2 octets (see byte 2 and byte 3 shown in Figure 6), the first value It can be represented by 0, 1 or more octets (see byte 4 - byte n shown in Figure 6).
  • the NAS message may also contain other IEs that exist in parallel with the first IE, and these IEs may be used to indicate other characteristics other than the first IE.
  • the NAS message may also include required IEs such as the extended protocol discriminator IE and security header type IE, and may also include PDU session status IE, PDU session reactivation result IE, etc.
  • the selected IE is not limited by the embodiments of this application.
  • the first IE may be a Type 6 IE.
  • the embodiments of the present application are not limited to this.
  • the first IE may also be a type 4 IE, or it may also be other types of IEs that appear in future communication systems.
  • the first IEI may be used to indicate the type of the first IE.
  • the first IEI may be used to indicate that the first IE is a nested IE, that is, the first IE may carry the second IE.
  • the second IE carried in the first IE is introduced below.
  • the second IE may be an optional IE, that is, the presence of the second IE is optional. That is to say, in some NAS messages, the second IE may be included; in some NAS messages, the second IE may not be included.
  • the second IE may include the second IEI.
  • the second IE may be considered that the second IE is encoded using the format TLV or TLV-E.
  • the specific content of the encoding structure of the second IE please refer to the previous description of the encoding structure of the first IE. For the sake of brevity, details will not be described here.
  • the type of the second IE is determined based on the first IEI and the second IEI.
  • the first IEI can be understood as being used to mark the first IE as a nested IE
  • the second IEI can be understood as being used to jointly determine the type of the second IE with the first IEI.
  • the first IEI and the second IEI can uniquely determine the type of the second IE.
  • 80 -10 can uniquely identify the type of the second IE.
  • the type of the second IE is the IE corresponding to a new feature in the 5G system, or it can also be the IE corresponding to an existing feature in the 5G system. etc., this application does not limit this.
  • the first IE may carry one or more second IEs, which is not limited by this application.
  • the multiple second IEs may be IEs of different types.
  • the plurality of second IEs may respectively include corresponding second IEIs.
  • the first IE corresponding to the first IEI and the second IE may be Two IEIs are used to determine the type of the second IE.
  • the first IE can also be understood as an encapsulated container. That is, the type of the first IE can be understood as a NAS message container or an extended type 6 IE container.
  • the container carries There is a second IE, for example, multiple second IEs are carried.
  • the first IE carries the second IE.
  • the type of the second IE can be determined based on the first IEI included in the first IE.
  • determining the type of the internal IE based on the IEI of the nested external IE can expand the number of IEs identified by the IEI, thereby solving the problem of insufficient IEI.
  • the second IE may be nested in the numerical part of the first IE (the first numerical part), that is, the numerical part of the first IE may carry the second IE.
  • the numerical part of the first IE is nested with multiple second IEs (the 1st second IE to the kth second IE).
  • the encoding method of each second IE is similar to the encoding method of the first IE, that is, the format TLV or TLV-E can be used for encoding. That is to say, each second IE may include an IEI, such as the IEI of the first second IE, the IEI of the second second IE, and the IEI of the k-th second IE.
  • the IEI of the first IEI and the first second IE can be used to uniquely identify the type of the first second IE
  • the IEI of the first IEI and the second second IE can be used to uniquely identify the type of the second IE.
  • the third IE can be continued to be nested in the second IE, that is, the second IE still has Carrying a third IE.
  • the third IE carried in the second IE will be described below with reference to FIG. 8 .
  • the numerical part (first numerical part) of the first IE carries one or more second IEs (the 1st second IE to the k-th second IE). Some or all of the one or more second IEs also carry third IEs. For example, a certain second IE among the one or more second IEs carries a third IE, for example, the first second IE carries a third IE, or the k-th second IE carries a third IE. Three IE. Alternatively, some of the one or more second IEs carry the third IE. For example, both the first second IE and the k-th second IE may carry the third IE.
  • the third IE may be nested in the numerical part of the second IE, that is, the numerical part of the second IE may carry the third IE.
  • the numerical part (first numerical part) of the first IE carries k second IEs
  • the numerical part of the k-th second IE carries the third IE.
  • the third IE may be an optional IE, that is, the presence of the third IE is optional. That is to say, in some NAS messages, the third IE may be included; in some NAS messages, the third IE may not be included.
  • the third IE may include the third IEI.
  • the third IE includes the third IEI, it may be considered that the third IE is encoded using the format TLV or TLV-E.
  • the encoding method of the third IE which is similar to the encoding method of the first IE or the second IE, please refer to the relevant descriptions above.
  • the type of the third IE is determined based on the first IEI, the second IEI, and the third IEI.
  • the type of the third IE can be uniquely determined by combining the first IEI, the second IEI and the third IEI.
  • the second IE may carry one or more third IEs, which is not limited by this application.
  • the multiple third IEs may be IEs of different types.
  • the plurality of third IEs may respectively include corresponding third IEIs.
  • the second IE carrying the third IE may be configured according to the first IEI.
  • the second IEI corresponding to the IE and the third IEI corresponding to the third IE determine the type of the third IE.
  • the embodiment of the present application does not limit the value of the first IEI.
  • the value of the first IEI can be a certain value specified by the protocol, for example, a value in hexadecimal not yet used, which can be used as the value of the IEI, and this value can be considered to be determined (to be determined), the value to be determined may be used to specifically identify the type of the first IEI.
  • the value of the first IEI can be set to 80 in hexadecimal. , to identify the first IE as the nested IE.
  • the value of the first IEI can be an existing IEI.
  • the first IEI can use a certain value in the existing hexadecimal 70-7F.
  • the replaced IE can be redefined with other IEIs.
  • the originally replaced IE can be embedded in the first IE, and the first IEI combined with the second IEI can be used to identify the type of the replaced IE.
  • a certain value in 70-7B in hexadecimal can be used to avoid the first device discarding the entire NAS message because it cannot understand the first IE. .
  • the value of the first IEI can be set to 70 in hexadecimal to identify the first IE as a nested IE, and the IE identified by the replaced 70 (NSSRG information IE) can be embedded in In the first IE, the first IEI (70) and the second IEI (for example, 70 or other values) are jointly identified. That is to say, in this embodiment of the present application, 70 in hexadecimal can be used to identify the first IEI, and 70-70 can be used to identify the replaced IE (NSSRG information IE).
  • the value of the second IEI can adopt a certain to-be-determined value to specifically identify the second IE; the existing IEI can also be continued to be used. In this case, the replaced IE can be reused.
  • Other IEI definitions, for example, the original replaced IE can be embedded into the second IE.
  • the second IE as an IE of type 6 as an example, when the second IE uses an existing IEI, it may mean that the value range of the second IEI may be 70-7F.
  • a certain value in 70-7B in hexadecimal can be used to avoid the first device discarding the entire NAS message because it cannot understand the second IE. .
  • the first IE and/or the IE carried in the first IE are IEs that the first device is allowed to ignore.
  • the embodiment of the present application is not limited to this, that is, the first IE and/or the IE carried in the first IE may be an IE that the first device is not allowed to ignore.
  • the IEs that the first device is allowed to ignore may mean that after the first device receives the NAS message sent by the second device, if the first device cannot understand this type of IE in the NAS message (the IEs that the first device is allowed to ignore), then The first device can directly ignore this type of IE and process other IEs in the NAS message.
  • the IEs that the first device is allowed to ignore may also be called non-comprehension required IEs (no-comprehension required IEs). Take type 6 IE as an example. When the value range of type 6 IEI is expressed as 70-7B in hexadecimal, it means that the format of the IE is TLV-E. For IEs within this range, if the first device cannot Understanding this type of IE, the first device can ignore this IE and process other IEs in the NAS message.
  • IEs that are allowed to be ignored by the first device there may also be IEs that are not allowed to be ignored by the first device.
  • the first device After the first device receives the NAS message sent by the second device, if the first device cannot understand the NAS message.
  • the first device needs to discard the entire NAS message.
  • IEs that are not allowed to be ignored by the first device may also be called IEs that need to be understood (comprehension required IEs).
  • type 6 IE when the value range of type 6 IEI is 011111xx (7C-7F in hexadecimal notation), it means that the format of the IE is TLV-E. IEs within this range, The first device needs to understand the IE. If the first device cannot understand this type of IE, the first device needs to discard the entire NAS message. Optionally, after discarding the entire NAS message, the first device also needs to return a mobility management status message (for example, a 5GMM status message) to the second device to notify the second device that the NAS message was not successfully received. For example, the returned mobility management status message carries a reason value for failure to receive the NAS message, that is, it carries a reason value "invalid mandatory information unit error (invalid mandatory information)".
  • a mobility management status message for example, a 5GMM status message
  • the IE carried in the first IE may refer to the second IE carried directly in the first IE, or may refer to the third IE carried through the second IE, which is not limited in this application.
  • the first IE, the second IE and the third IE are all IEs that the first device is allowed to ignore; or, some of the first IE, the second IE and the third IE may be IEs that are allowed to be ignored by the first device. ie.
  • the first IE is an IE that the first device is allowed to ignore. After the first device receives the NAS message sent by the second device and cannot understand the first IE in the NAS message, the first device can directly ignore it.
  • the first IE processes other IEs in the NAS message except the first IE.
  • the first IE can be understood as an IE that is allowed to be ignored by the first device.
  • the embodiments of the present application are not limited to this.
  • the value range of the first IEI can also be 7C-7F in hexadecimal, that is, the first IE can also be understood IE is ignored as the first device is not allowed.
  • the first IE and/or the IE carried in the first IE are IEs that the first device is allowed to ignore, if the first device cannot understand the first IE or the IE carried in the first IE, the first device directly Ignore the first IE or the IE carried in the first IE, and process other IEs. This method has good compatibility.
  • the first IE may be a Type 6 IE.
  • the IE carried in the first IE may be a Type 6 IE or a Type 4 IE, which is not limited in this embodiment of the present application.
  • the second IE may be a type 6 IE or a type 4 IE.
  • the second IE may be a type 4 IE.
  • the IE carried in the second IE may be a Type 6 IE or a Type 4 IE.
  • the third IE may be a type 6 IE or a type 4 IE.
  • the second IE is a type 4 IE
  • the third IE may be a type 4 IE.
  • Figure 9 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • the communication device 900 shown in FIG. 9 can be applied to a first device, and the first device can be any first device mentioned above.
  • the communication device 900 may include a processing module 910 and a receiving module 920.
  • the processing module 910 may be configured to receive a NAS message sent by the second device through the receiving module 920, wherein the NAS message includes a first information unit IE, the first IE includes a first information unit identifier IEI, and the first IE carries a second IE, and the second IE includes a second IEI.
  • the type of the second IE is determined based on the first IEI and the second IEI.
  • the second IE carries a third IE
  • the third IE includes a third IEI
  • the type of the third IE is based on the first IEI, the second IEI and the third IEI OK.
  • the first IE and/or the IE carried in the first IE are IEs that the first device is allowed to ignore.
  • the first IE is a type 6 IE, and the value range of the first IEI is 70 to 7B in hexadecimal notation.
  • the NAS message is a registration acceptance message.
  • the first IE is a type 6 IE.
  • the second IE is a type 6 or type 4 IE.
  • the IE carried in the second IE is a type 6 or type 4 IE.
  • FIG. 10 is a schematic structural diagram of a communication device provided by another embodiment of the present application.
  • the communication device 1000 shown in FIG. 10 can be applied to a second device, and the second device can be any second device mentioned above.
  • the communication device 1000 may include a processing module 1010 and a sending module 1020.
  • the processing module 1010 may be configured to send a NAS message to the first device through the sending module 1020, where the NAS message includes a first information unit IE, the first IE includes a first information unit identifier IEI, and the first IE A second IE is carried, and the second IE includes a second IEI.
  • the type of the second IE is determined based on the first IEI and the second IEI.
  • the second IE carries a third IE
  • the third IE includes a third IEI
  • the type of the third IE is based on the first IEI, the second IEI and the third IEI OK.
  • the first IE and/or the IE carried in the first IE are IEs that the first device is allowed to ignore.
  • the first IE is a type 6 IE, and the value range of the first IEI is 70 to 7B in hexadecimal notation.
  • the NAS message is a registration acceptance message.
  • the first IE is a type 6 IE.
  • the second IE is a type 6 or type 4 IE.
  • the IE carried in the second IE is a type 6 or type 4 IE.
  • Figure 11 is a schematic structural diagram of a communication device according to an embodiment of the present application.
  • the dashed line in Figure 11 indicates that the unit or module is optional.
  • the device 1100 can be used to implement the method described in the above method embodiment.
  • Device 1100 may be a chip, terminal device or network device.
  • Apparatus 1100 may include one or more processors 1110.
  • the processor 1110 can support the device 1100 to implement the method described in the foregoing method embodiments.
  • the processor 1110 may be a general-purpose processor or a special-purpose processor.
  • the processor may be a central processing unit (CPU).
  • the processor can also be another general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), or an off-the-shelf programmable gate array (FPGA) Or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA off-the-shelf programmable gate array
  • a general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.
  • Apparatus 1100 may also include one or more memories 1120.
  • the memory 1120 stores a program, which can be executed by the processor 1110, so that the processor 1110 executes the method described in the foregoing method embodiment.
  • the memory 1120 may be independent of the processor 1110 or integrated in the processor 1110 .
  • Device 1100 may also include a transceiver 1130.
  • Processor 1110 may communicate with other devices or chips through transceiver 1130.
  • the processor 1110 can transmit and receive data with other devices or chips through the transceiver 1130 .
  • An embodiment of the present application also provides a computer-readable storage medium for storing a program.
  • the computer-readable storage medium can be applied in the terminal or network device provided by the embodiments of the present application, and the program causes the computer to execute the methods performed by the terminal or network device in various embodiments of the present application.
  • An embodiment of the present application also provides a computer program product.
  • the computer program product includes a program.
  • the computer program product can be applied in the terminal or network device provided by the embodiments of the present application, and the program causes the computer to execute the methods performed by the terminal or network device in various embodiments of the present application.
  • An embodiment of the present application also provides a computer program.
  • the computer program can be applied to the terminal or network device provided by the embodiments of the present application, and the computer program causes the computer to execute the methods performed by the terminal or network device in various embodiments of the present application.
  • the "instruction" mentioned may be a direct instruction, an indirect instruction, or an association relationship.
  • a indicates B which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B. relation.
  • B corresponding to A means that B is associated with A, and B can be determined based on A.
  • determining B based on A does not mean determining B only based on A.
  • B can also be determined based on A and/or other information.
  • the term "correspondence” can mean that there is a direct correspondence or indirect correspondence between the two, or it can also mean that there is an association between the two, or it can also mean indicating and being instructed, configuring and being configured, etc. relation.
  • predefinition or “preconfiguration” can be achieved by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in devices (for example, including terminal devices and network devices).
  • devices for example, including terminal devices and network devices.
  • predefined can refer to what is defined in the protocol.
  • the "protocol” may refer to a standard protocol in the communication field, which may include, for example, LTE protocol, NR protocol, and related protocols applied in future communication systems. This application does not limit this.
  • the size of the sequence numbers of the above-mentioned processes does not mean the order of execution.
  • the execution order of each process should be determined by its functions and internal logic, and should not be determined by the implementation process of the embodiments of the present application. constitute any limitation.
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented.
  • the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or they may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another, e.g., the computer instructions may be transferred from a website, computer, server, or data center Transmission to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) means.
  • the computer-readable storage medium may be any available medium that can be read by a computer or a data storage device such as a server or data center integrated with one or more available media.
  • the available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs (DVD)) or semiconductor media (e.g., solid state disks (SSD) )wait.
  • magnetic media e.g., floppy disks, hard disks, magnetic tapes
  • optical media e.g., digital video discs (DVD)
  • semiconductor media e.g., solid state disks (SSD)

Landscapes

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

Abstract

提供了一种通信方法和通信装置。该通信方法包括：第一设备接收第二设备发送的NAS消息；其中，该NAS消息包括第一IE，第一IE包括第一IEI，第一IE中携带有第二IE。在本申请实施例中，第一IE中携带有第二IE，如此一来，第二IE的类型可以基于第一IE包含的第一IEI确定。相比于传统的仅使用IE本身包含IEI确定IE的类型的情况，基于嵌套的外部IE的IEI确定内部IE的类型能够扩展IEI标识的IE的数量，从而能够解决IEI不够用的问题。

Description

通信方法和通信装置 技术领域
本申请涉及通信技术领域，并且更为具体地，涉及一种通信方法和通信装置。
背景技术
终端设备接入核心网后，能够与核心网设备进行非接入层(non-access stratum，NAS)消息交互。NAS消息中可以包含多个信息单元(information element，IE)以指示某些特性，例如，可以包含扩展协议鉴别符IE、安全头类型IE、分组数据单元(packet data unit，PDU)会话状态IE等。某些情况下，IE的类型可以使用信息单元标识(information element identifier，IEI)来标识，例如IEI十六进制取值为50时可以表示IE的类型为PDU会话状态IE。
随着通信系统的快速发展，可能会引入一些新的特性，使得NAS消息中携带的IE越来越多，可能会导致目前的IEI不够使用。因此，如何对IEI进行扩展是亟待解决的问题。
发明内容
本申请提供一种通信方法和通信装置。下面对本申请涉及的各个方面进行介绍。
第一方面，提供了一种通信方法，包括：第一设备接收第二设备发送的非接入层NAS消息；其中，所述NAS消息包括第一信息单元IE，所述第一IE包括第一信息单元标识IEI，所述第一IE中携带有第二IE。
第二方面，提供了一种通信方法，包括：第二设备向第一设备发送非接入层NAS消息；其中，所述NAS消息包括第一信息单元IE，所述第一IE包括第一信息单元标识IEI，所述第一IE中携带有第二IE。
第三方面，提供了一种通信装置，所述装置应用于第一设备，所述装置包括处理模块和接收模块，所述处理模块用于通过所述接收模块接收第二设备发送的非接入层NAS消息；其中，所述NAS消息包括第一信息单元IE，所述第一IE包括第一信息单元标识IEI，所述第一IE中携带有第二IE。
第四方面，提供了一种通信装置，所述装置应用于第二设备，所述装置包括处理模块和发送模块，所述处理模块用于通过所述发送模块向第一设备发送非接入层NAS消息；其中，所述NAS消息包括第一信息单元IE，所述第一IE包括第一信息单元标识IEI，所述第一IE中携带有第二IE。
第五方面，提供了一种第一设备，包括处理器、存储器以及通信接口，所述存储器用于存储一个或多个计算机程序，所述处理器用于调用所述存储器中的计算机程序使得所述第一设备执行第一方面的方法中的部分或全部步骤。
第六方面，提供了一种第二设备，包括处理器、存储器以及通信接口，所述存储器用于存储一个或多个计算机程序，所述处理器用于调用所述存储器中的计算机程序使得所述第二设备执行第二方面的方法中的部分或全部步骤。
第七方面，本申请实施例提供了一种通信系统，该系统包括上述的第一设备和/或第二设备。在另一种可能的设计中，该系统还可以包括本申请实施例提供的方案中与该第一设备或第二设备进行交互的其他设备。
第八方面，本申请实施例提供了一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，所述计算机程序使得第一设备或第二设备执行上述各个方面的方法中的部分或全部步骤。
第九方面，本申请实施例提供了一种计算机程序产品，其中，所述计算机程序产品包括存储了计算机程序的非瞬时性计算机可读存储介质，所述计算机程序可操作来使第一设备或第二设备执行上述各个方面的方法中的部分或全部步骤。在一些实现方式中，该计算 机程序产品可以为一个软件安装包。
第十方面，本申请实施例提供了一种芯片，该芯片包括存储器和处理器，处理器可以从存储器中调用并运行计算机程序，以实现上述各个方面的方法中所描述的部分或全部步骤。
在本申请实施例中，第一IE中携带有第二IE，如此一来，第二IE的类型可以基于第一IE包含的第一IEI确定。相比于传统的仅使用IE本身包含IEI确定IE的类型的情况，基于嵌套的外部IE的IEI确定内部IE的类型能够扩展IEI标识的IE的数量，从而能够解决IEI不够用的问题。
附图说明
图1是可应用于本申请实施例的网络架构的示例图。
图2是IE的编码方式的一个示例图。
图3是IE的编码方式的另一个示例图。
图4是可应用于本申请实施例的通信系统的示例图。
图5是本申请实施例提供的通信方法的流程示意图。
图6是本申请一实施例提供的第一IE的编码方式的示例图。
图7是本申请另一实施例提供的第一IE的编码方式的示例图。
图8是本申请又一实施例提供的第一IE的编码方式的示例图。
图9是本申请一实施例提供的通信装置的结构示意图。
图10是本申请另一实施例提供的通信装置的结构示意图。
图11是本申请实施例提供的装置的示意性结构图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信系统，例如：第五代(5th generation，5G)系统或新无线(new radio，NR)系统、长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)系统等。本申请提供的技术方案还可以应用于未来的通信系统，如第六代移动通信系统，又如卫星通信系统，等等。
首先简单介绍适用于本申请的网络架构。
作为示例，图1示出了一种网络架构的示例图。图1示出的网络架构是以5G系统为例。该网络架构中可以包括三部分，分别是终端设备部分、数据网络(data network，DN)部分和运营商网络部分。其中，运营商网络可以包括以下功能实体中的一个或多个：接入网(access network，AN)设备、用户面功能(user plane function，UPF)实体、接入和移动性管理功能(access and mobility management function，AMF)实体、会话管理功能(session management function，SMF)实体、策略控制功能(policy control function，PCF)实体、应用功能(application function，AF)实体、网络切片选择功能(network slice selection function，NSSF)实体、认证授权业务功能(authentication server function，AUSF)实体、统一数据管理(unified data management，UDM)实体等。上述运营商网络中，除接入网设备部分之外的部分可以称为核心网部分，核心网部分的功能实体可以称为核心网设备。
下面对该网络架构中涉及的各个部分或功能实体在5G网络中的功能分别进行示例性说明。
终端设备：终端设备也可以称为用户设备(user equipment，UE)、接入终端、用户单元、用户站、移动站、移动台(mobile station，MS)、移动终端(mobile terminal，MT)、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。本申请实施例中的终端设备可以是指向用户提供语音和/或数据连通性的设备，可以用于连 接人、物和机，例如具有无线连接功能的手持式设备、车载设备等。本申请的实施例中的终端设备可以是手机(mobile phone)、平板电脑(Pad)、笔记本电脑、掌上电脑、移动互联网设备(mobile internet device，MID)、可穿戴设备，虚拟现实(virtual reality，VR)设备、增强现实(augmented reality，AR)设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等。可选地，UE可以用于充当基站。例如，UE可以充当调度实体，其在V2X或D2D等中的UE之间提供侧行链路信号。比如，蜂窝电话和汽车利用侧行链路信号彼此通信。蜂窝电话和智能家居设备之间通信，而无需通过基站中继通信信号。
接入网设备：接入网设备可以用于为特定区域的授权终端设备提供入网功能，并能够根据终端设备的级别、业务需求等使用不同质量的传输通道。接入网设备能够管理无线资源，为终端设备提供接入服务，进而完成控制信号和数据在终端设备和核心网之间的转发。
接入网设备可以是无线网络中的设备。接入网设备也可以称为无线接入网(radio access network，RAN)设备或网络设备，如接入网设备可以是基站。本申请实施例中的接入网设备可以是指将终端设备接入到无线网络的无线接入网(radio access network，RAN)节点(或设备)。基站可以广义的覆盖如下中的各种名称，或与如下名称进行替换，比如：节点B(NodeB)、演进型基站(evolved NodeB，eNB)、下一代基站(next generation NodeB，gNB)、中继站、接入点、传输点(transmitting and receiving point，TRP)、发射点(transmitting point，TP)、主站MeNB、辅站SeNB、多制式无线(MSR)节点、家庭基站、网络控制器、接入节点、无线节点、接入点(access point，AP)、传输节点、收发节点、基带单元(base band unit，BBU)、射频拉远单元(Remote Radio Unit，RRU)、有源天线单元(active antenna unit，AAU)、射频头(remote radio head，RRH)、中心单元(central unit，CU)、分布式单元(distributed unit，DU)、定位节点等。基站可以是宏基站、微基站、中继节点、施主节点或类似物，或其组合。基站还可以指用于设置于前述设备或装置内的通信模块、调制解调器或芯片。基站还可以是移动交换中心以及设备到设备D2D、车辆外联(vehicle-to-everything，V2X)、机器到机器(machine-to-machine，M2M)通信中承担基站功能的设备、6G网络中的网络侧设备、未来的通信系统中承担基站功能的设备等。基站可以支持相同或不同接入技术的网络。本申请的实施例对接入网设备所采用的具体技术和具体设备形态不做限定。
基站可以是固定的，也可以是移动的。例如，直升机或无人机可以被配置成充当移动基站，一个或多个小区可以根据该移动基站的位置移动。在其他示例中，直升机或无人机可以被配置成用作与另一基站通信的设备。
在一些部署中，本申请实施例中的接入网设备可以是指CU或者DU，或者，接入网设备包括CU和DU。gNB还可以包括AAU。
接入网设备和终端设备可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上；还可以部署在空中的飞机、气球和卫星上。本申请实施例中对接入网设备和终端设备所处的场景不做限定。
UPF实体：UPF为核心网中的用户面功能，可以负责终端设备中用户数据(如业务数据流)的转发和接收。示例性地，UPF可以从DN接收用户数据，通过接入网设备传输给终端设备；或者，UPF还可以通过接入网设备从终端设备接收用户数据，然后转发到DN。UPF中为终端设备提供服务的传输资源和调度功能是由SMF管理控制的。在一些实施例中，UPF可以分为中间UPF(intermediate-UPF，I-UPF)和锚点UPF(anchor-UPF，A-UPF)。其中，I-UPF与接入网连接，A-UPF为会话锚点的UPF，A-UPF又可以称为PDU会话锚点(PDU session anchor，PSA)。
AMF实体：AMF为核心网中的移动性管理功能，可以用于实现移动性管理实体(mobility management entity，MME)的功能中除会话管理之外的其它功能，例如，合法监听、或接入授权(或鉴权)等功能。在一些实施例中，AMF除可以对终端设备进行移动性管理之外，还可以负责会话管理相关消息在终端设备和SMF之间的转发。
SMF实体：SMF为核心网中的会话管理功能，主要负责会话管理、终端设备的网络互连协议(internet protocol，IP)地址分配和管理、选择可管理用户平面功能、策略控制、或收费功能接口的终结点以及下行数据通知、为用户面功能配置路由信息等。
PCF实体：PCF为核心网中的策略管理功能，可以负责制定对终端设备的移动性管理、会话管理、计费等相关的策略。具体地，PCF可以为控制面的功能实体(例如AMF，SMF实体等)提供策略规则信息等，以对终端设备的移动性管理、会话管理等进行管理控制。
AF实体：AF主要支持与第三代合作伙伴计划(3rd generation partnership project，3GPP)核心网交互来提供服务，例如，影响数据路由决策、策略控制功能、或者向网络侧提供第三方的一些服务。或者说，AF可以主要用于传递应用侧对网络侧的需求。在一些实施例中，AF可以理解为第三方服务器，例如，Internet中的应用服务器，提供相关业务信息，包括向PCF提供业务对应的服务质量需求信息，以及向A-UPF发送业务的用户面数据信息。在一些实施例中，AF也可以是服务提供商(content provider，CP)。
DN：DN是指可以用于提供传输数据的网络。DN可以是私有网络，如局域网，也可以是不受运营商管控的外部网络，如因特网(internet)，还可以是运营商共同部署的专有网络，如提供IP多媒体网络子系统(IP multimedia core network subsystem，IMS)服务的网络。
应理解，核心网中的以上各个功能实体也可以称为网元，本申请对此并不限定。示例性地，UPF实体也可以称为UPF网元，AMF实体也可以称为AMF网元等。
还应理解，在一些实施例中，xx功能实体或xx网元也可以直接简称为xx，例如UPF实体(或UPF网元)可以简称为UPF，AMF实体(或AMF网元)可以简称为AMF。为了便于描述，本申请实施例提及的xx(如UPF、AMF等)可以是指xx实体或xx网元，后文将不再赘述。
图1所示的网络架构中，各个部分或功能实体之间可以通过接口进行通信。比如，终端设备可以通过Uu接口与AN进行接入层(access stratum，AS)连接，交互AS消息及无线数据传输；终端设备可以通过N1接口与AMF进行非接入层(none access stratum，NAS)连接，交互NAS消息；AN可以通过N2接口与AMF进行连接，用于传递核心网侧至AN的无线承载控制信息等；UPF可以通过N3接口与AN进行数据传输，通过N6接口与DN进行数据传输等。其他部分或功能实体之间连接的接口可以参见图1，此处不再赘述。
应理解，上述所示的网络架构仅是示例性说明，适用本申请实施例的网络架构并不局限于此，任何能够实现上述各个功能实体的功能的网络架构都适用于本申请实施例。
应理解，图1所示的接入网设备、AMF、SMF、UPF和PCF等仅是一个名字，名字对设备本身不构成限定。在5G网络以及未来其它的网络中，接入网设备、AMF、SMF、UPF和PCF等所对应的实体也可以是其他的名字，本申请实施例对此不作具体限定。
应理解，图1所示的各个功能实体之间的接口名字只是一个示例，具体实现中各个功能实体之间的接口名字也可以是其他的名字，例如6G网络中的功能实体之间的接口名字，本申请实施例对此不作具体限定。
应理解，本申请中的通信设备的全部或部分功能也可以通过在硬件上运行的软件功能来实现，或者通过平台(例如云平台)上实例化的虚拟化功能来实现。
应理解，本申请实施例描述的网络架构是为了更清楚地说明本申请实施例的技术方案，并不构成对本申请实施例提供的技术方案的限定，本领域技术人员可知，随着网络架构的演变，本申请实施例对于类似的技术问题，同样可以适用。
终端设备通过接入网设备(例如，基站)接入核心网后，终端设备能够与核心网设备之间进行通信。终端设备通过接入网设备接入核心网的过程中，终端设备与接入网设备之间的通信可以理解为是AS交互，其可以通过收发AS消息来实现终端设备与接入网设备之间的通信；终端设备与核心网设备之间的通信可以理解为是NAS交互，其可以通过收发NAS消息来实现终端设备与核心网设备之间的通信。例如，终端设备向核心网设备发起NAS注册的过程中，终端设备可以向核心网设备发送注册请求(registration request)消息，核心网设备如果能够接受终端设备的注册请求消息，则核心网设备可以向终端设备返回注册接受(registration accept)消息，该注册请求消息和注册接受消息均可以理解为是NAS消息，其用于终端设备与核心网设备之间的通信。
作为一种实现方式，终端设备与核心网设备之间的NAS消息可以由接入网设备以透传的方式进行转发。
NAS消息中可以包含多个信息单元(information element，IE)以指示某些特性(feature)，在一些实施例中，信息单元也可以称为信息元素、信元等，本申请对此不作限定。示例性地，NAS消息中可以包含扩展协议鉴别符(extended protocol discriminator)IE，扩展协议鉴别符可以用于表示该NAS消息是5GMM消息还是5GSM消息。或者，NAS消息中可以包含安全头类型(security header type)IE，该IE可以用于指示与5G移动性管理(5G mobility management，5GMM)消息的安全保护相关的特性，例如与5GMM消息的安全保护有关的控制信息等。又或者，NAS消息中可以包含分组数据单元(packet data unit，PDU)会话状态(PDU session status)IE、PDU会话重新激活结果(PDU session reactivation result)IE、PDU会话重新激活结果错误原因(PDU session reactivation result error cause)IE等，这些IE可以用于指示与PDU会话相关的特性等。
NAS消息中包含的多个IE中，部分IE是NAS消息必选的IE，部分IE是NAS消息可选的IE。例如，前文提及的扩展协议鉴别符IE、安全头类型IE可以是NAS消息必选的IE，而PDU会话状态IE、PDU会话重新激活结果IE等可以是NAS消息可选的IE，本申请实施例对此并不限定。
NAS消息中包含的多个IE中，每个IE的类型(type)可以是不同的。IE的类型可以用于指示该IE的功能或目的，例如，前文提及的扩展协议鉴别符IE对应的IE的类型为扩展协议鉴别符IE、安全头类型IE对应的IE的类型为安全头类型IE、PDU会话状态IE对应的IE的类型为PDU会话状态IE等。
IE可以采用不同的格式(format)进行编码。作为一种实现方式，IE可以采用格式V来进行编码，其中V代表value，表示IE实际的数值。作为另一种实现方式，IE可以采用格式LV或格式LV-E来进行编码，其中L代表length，表示数值的长度信息；V代表value，表示IE实际的数值，LV-E是指扩展的LV格式。作为又一种实现方式，IE可以采用格式TLV或格式TLV-E来进行编码，其中T代表type，表示IE的类型；L代表length，表示数值的长度信息；V代表value，表示IE实际的数值，TLV-E是指扩展的TLV格式。
可以看出，IE采用格式TLV或TLV-E进行编码时，会使用T(type)来标识IE的类型。在一些实施例中，IE的类型可以使用信息单元标识(information element identifier，IEI)来确定(或标识)。例如，采用十六进制的表示方法时，IEI取值为50时可以表示该IE的类型为PDU会话状态IE；IEI取值为26时可以表示该IE的类型为PDU会话重新激活结果IE；IEI取值为72时表示该IE的类型为PDU会话重新激活结果错误原因IE等。不过本申请并不限定采用格式TLV或TLV-E进行编码时，所有IE都需要使用IEI来标识IE的类型，例如，对于NAS消息中的某些必选的IE，可以不使用IEI进行标识，比如扩展协议鉴别符IE、安全头类型IE等必选的IE可以不使用IEI进行标识。
在一些实施例中，按照L的长度(L所占的字节大小)可以将其对应的IE划分为类型4的IE和类型6的IE。具体的，L的长度固定使用1个八位字节(octet)表示时，这种IE 可以称为类型4的IE；L的长度固定使用2个八位字节表示时，这种IE可以称为类型6的IE。
对于类型6的IE而言，其可以使用格式LV-E或使用格式TLV-E进行编码，具体可以参见图2和图3示出的类型6的IE的示意图，其中图2为采用格式LV-E进行编码的类型6的IE，图3为采用格式TLV-E进行编码的类型6的IE。在图2和图3的示例中，类型6的IE的L的长度信息用LI(length information)来标识，可以看出，类型6的IE的L的长度是固定的，使用2个八位字节来表示，且编码时LI位于V的前面，其中V的长度例如可以是0-65535个八位字节中的任意值。如果是采用格式TLV-E进行编码时，用于标识IE的类型的IEI是位于LI的前面，其是采用1个八位字节来表示的。
如前文所述，可以使用IEI来标识IE的类型。由于目前IEI是采用1个八位字节来表示的，其能够表示的IEI的数量有限。随着通信系统的快速发展，可能会不断引入一些新的特性，例如5G系统、6G系统或未来的通信系统中可能会引入一些新的特性，这些新的特性可能使用新的IE来承载，这样可能会使得NAS消息中携带的IE越来越多，进而可能会导致目前的IEI不够使用。
以类型6的IE为例，在5G系统协议5GMM和5GSM中规定：用于表示IEI的1个八位字节中，比特位8被设置为0且比特位7至比特位5被设置为1时表示：该IEI标识的IE是采用格式TLV-E进行编码的，其是类型6的IE，即用于表示IEI的1个字节之后的2个字节为表示L的字节(Bit 8 of the IEI octet set to"0"and bits 7 to 5 set to"1"indicates a TLV-E formatted type 6 IE,i.e.the following two octets are length octets)。也就是说，IEI的取值为0111xxxx(在十六进制下表示为70-7F)表示该IE的格式是TLV-E，类型6的IE，该IE的length的长度是2个八位字节。可以看出，用来标识类型6的IE的IEI的取值只有16种(70-7F)，随着新特性的增加，该IEI的取值范围很可能不够使用。
下面结合表1，给出NAS消息的一个示例，以此来示例性说明类型6的IEI可能不够使用。
表1
Figure PCTCN2022102841-appb-000001
Figure PCTCN2022102841-appb-000002
Figure PCTCN2022102841-appb-000003
表1是以NAS消息为注册接受消息为例的，该注册接受消息是核心网设备向终端设备发送的。该注册接受消息中包含很多IE，其中表1中的每一行代表一个IE。
这些IE中，有些是必选的(用M(mandatory)来表示)，有些是可选的(用O(optional)来表示)。
这些IE中，有些IE是不需要用IEI进行标识的，比如注册接受消息中必须存在的IE；有些IE是需要用IEI进行标识的，比如注册接受消息中可选存在的IE，其中不同的IEI用于表示该IE的类型不同，例如，IEI取值为70表示该IE的类型为NSSRG信息(NSSRG information)IE；IEI取值为7A表示该IE的类型为扩展紧急号码列表(extended emergency number list)IE。
这些IE中，可以采用相同或不同的格式进行编码。例如，有些IE可以采用格式V进行编码，比如扩展协议鉴别符IE；有些IE可以采用格式TLV进行编码，比如PDU会话状态IE；有些IE可以采用TLV-E进行编码，比如扩展紧急号码列表IE，等等。
这些IE中，IE的长度的取值范围可以是不同的，其中IE的长度是指整个IE所占的字节大小，例如，该IE采用格式LV-E进行编码时，IE的长度包括L(length)以及V(value)两部分总体所占的字节大小；该IE采用格式TLV-E进行编码时，IE的长度包括IEI、L以及V几部分总体所占的字节大小。
从表1的示例可以看出，在该注册接受消息中，类型6的IEI(在十六进制下为70-7F)基本已经被用完了，如果有新的IE需要使用类型6的IEI表示时，类型6的IEI的值已经不够用了。因此，如何对IEI进行扩展是亟待解决的问题。
作为一种可能的实现方式，可以通过扩充IEI值的范围来对IEI进行扩展。具体地，可以将IEI的长度延长，例如，目前IEI的长度是采用1个八位字节来表示，可以将IEI的长度延长至采用2个八位字节来表示，或者延长至更多字节。但是，为了支持这样的方案，一方面，终端设备需要向网络侧(核心网设备)指示其支持扩充的IEI，例如，终端设备需要进行能力指示上报，以指示其支持扩充的IEI，这对终端设备的实现改动复杂；另一方面，网络侧在向终端设备发送NAS消息时，还需要检查终端设备的能力，根据不同的终端设备能力生成NAS消息内容，无疑又增加了网络侧的实现复杂度。
基于此，本申请实施例提供了一种通信方法和通信装置，能够解决IEI不够使用的问题。此外，相对于将IEI的长度延长的方案而言，本申请实施例的技术方案无需终端设备进行能力上报，使得终端设备的实现改动较小，且网络侧的实现复杂度也较低。
在介绍本申请实施例之前，先对本申请实施例适用的通信系统进行介绍。
图4为本申请实施例提供的通信系统40，该通信系统40包括第一设备410和第二设备420。
第一设备410和第二设备420可以进行通信，交互NAS消息。例如，第一设备410可以向第二设备420发送NAS消息，第二设备420可以接收第一设备410发送的NAS消息以进行后续处理；或者，第二设备420可以向第一设备410发送NAS消息，第一设备410可以接收第二设备420发送的NAS消息以进行后续处理。
第一设备410和第二设备420之间进行通信，交互NAS消息可以是指，第一设备和第二设备之间直接通信，交互NAS消息；也可以是指，第一设备和第二设备通过其他设备的转发进行通信，交互NAS消息，例如可以通过其他设备的透传进行通信，本申请实施例 对此不作具体限定。
本申请实施例提供的通信系统中，第一设备410可以是终端设备，第二设备420可以是核心网设备。或者，第一设备可以是核心网设备，第二设备可以是终端设备，本申请实施例对此并不限定，只要其之间可以进行NAS消息的交互即可。其中，终端设备可以是前文提及的任一终端设备，核心网设备可以是指位于核心网中的设备，例如前文提及的AMF、SMF、PCF等，本申请实施例对此并不限定。
可选地，本申请实施例提供的通信系统可以应用于如图1所示的网络架构中，本申请实施例对此不进行限定。示例性地，若本申请实施例提供的通信系统应用于如图1所示的网络架构中，则上述的第一设备可以是终端设备，第二设备可以是核心网中的AMF；或者第一设备可以是核心网中的AMF，第二设备可以是终端设备，等等。
下面结合图5至图8，对本申请实施例提供的通信方法进行详细介绍。
图5为本申请实施例提供的通信方法的流程示意图。图5所示的方法是站在第一设备和第二设备交互的角度进行描述的，第一设备和第二设备例如可以是图4中的第一设备410和第二设备420。示例性地，第一设备可以是终端设备，第二设备是核心网设备；或者第一设备可以是核心网设备，第二设备是终端设备。本申请实施例提供的通信方法可以包括步骤S510，下面对该步骤进行详细描述。
在步骤S510，第二设备向第一设备发送NAS消息。
作为一种实现方式，第二设备可以直接向第一设备发送NAS消息。作为另一种实现方式，第二设备可以通过其他设备转发，以向第一设备发送NAS消息。以5G系统为例，假设第一设备和第二设备分别为终端设备和AMF，第二设备可以通过N1接口直接向第一设备发送NAS消息；或者，第二设备也可以通过接入网设备(比如，基站)的转发向第一设备发送NAS消息，其中，接入网设备可以以透传的方式转发该NAS消息。
NAS消息的类型可以包括多种。示例性地，NAS消息可以为注册请求消息，也可以为注册接受消息等。以NAS消息为注册请求消息为例，第二设备可以是终端设备，第一设备可以是核心网设备。以NAS消息为注册接受消息为例，第二设备可以是核心网设备，第一设备可以是终端设备。当然，NAS消息也可以是注册拒绝消息等其他NAS消息，本申请实施例对此并不限定。
该NAS消息可以包括第一IE。在一些实施例中，第一IE可以是可选的IE，即第一IE的存在性(presence)为可选的。也就是说，在某些NAS消息中，可以包括第一IE；在某些NAS消息中，也可以不包括第一IE。示例性地，第一设备和第二设备之间可以进行多条NAS消息的交互，比如包括NAS消息#1和NAS消息#2，在NAS消息#1中，可以包括第一IE，在NAS消息#2中，可以不包括第一IE，本申请实施例对此并不限定。
本申请实施例对第一IE的长度的取值范围不作限定，例如，第一IE为采用格式TLV或者TLV-E进行编码的IE时，第一IE的长度可以是3-n个八位字节，n是大于或等于3，且小于或等于65535的任意值。
第一IE可以包括第一IEI，第一IEI可以用于指示第一IE的类型(type，T)。第一IE的类型可以用于表示第一IE的功能或目的，例如，第一IE的功能是作为容器携带其他IE时，第一IE的类型可以理解为是NAS消息容器(NAS message container)，或者可以理解为是IE容器。表2给出了NAS消息中包含第一IE的一个示例，如表2所示，第一IE的类型是NAS消息容器，且第一IE为可选的IE。
表2
IEI IE 类型/参考 存在 格式 长度
第一IEI 第一IE NAS消息容器 O TLV-E 3-n
表3给出了NAS消息中包含第一IE的另一个示例，如表3所示，第一IE的类型是扩展类型6 IE容器(Extended Type 6 IE container)，且第一IE为可选的IE。
表3
IEI IE 类型/参考 存在 格式 长度
第一IEI 第一IE 扩展类型6 IE容器 O TLV-E 3-n
在第一IE包括第一IEI的情况下，可以认为，第一IE是采用格式TLV或者TLV-E进行编码的。第一IE采用格式TLV或TLV-E进行编码时，第一IE除包括第一IEI之外，还可以包括其他部分或字段，例如包括第一长度(length，L)、第一数值(value，V)等，其中，第一数值部分用于指示第一IE实际的内容或实际的数值，第一长度用于指示第一数值的长度信息。
第一IE采用格式TLV或TLV-E进行编码时，第一IEI和/或第一长度的长度均可以是固定的，其中第一IEI或第一长度的长度可以是指第一IEI或第一长度所占的字节大小。也就是说，第一IEI和/或第一长度可以使用固定的字节大小来表示，例如第一IEI可以使用1个八位字节表示，第一长度可以使用1个八位字节或2个八位字节表示。而第一数值的长度则是可以变化的，例如当第一长度使用2个八位字节表示时，第一数值的长度可以是0-65535个八位字节中的任意值，其中，第一数值的长度可以是由第一长度来指定的。图6为本申请实施例给出的第一IE的编码方式的一个示例，如图6所示，第一IE包括第一IEI、第一长度以及第一数值，其中第一IEI是用1个八位字节表示的(参见图6示出的字节1)，第一长度是用2个八位字节表示的(参见图6示出的字节2和字节3)，第一数值可以用0个、1个或多个八位字节来表示(参见图6示出的字节4-字节n)。
在一些实施例中，该NAS消息中除包含第一IE之外，还可以包含与第一IE并列存在的其他IE，这些IE可以用于指示第一IE之外的其他特性。示例性地，NAS消息中除包含第一IE之外，还可以包含扩展协议鉴别符IE、安全头类型IE等必选的IE，也可以包含PDU会话状态IE、PDU会话重新激活结果IE等可选的IE，本申请实施例对此并不限定。
在一些实施例中，第一IE可以是类型6的IE。但本申请实施例并不限定于此，例如第一IE也可以是类型4的IE，或者也可以是未来通信系统中出现的其他类型的IE等。
如前文所述，第一IEI可以用于指示第一IE的类型。在一些实施例中，第一IEI例如可以用于指示第一IE为嵌套的IE，即第一IE中可以携带有第二IE。下面对第一IE中携带的第二IE进行介绍。
在一些实施例中，第二IE可以是可选的IE，即第二IE的存在性(presence)为可选的。也就是说，在某些NAS消息中，可以包括第二IE；在某些NAS消息中，也可以不包括第二IE。
在一些实施例中，第二IE可以包括第二IEI，在第二IE包括第二IEI的情况下，可以认为，第二IE采用格式TLV或TLV-E进行编码。关于第二IE的编码结构的具体内容，可以参见前文第一IE的编码结构的相关描述，为了简洁，此处不再赘述。
在一些实施例中，第二IE的类型是基于第一IEI和第二IEI确定的。其中，第一IEI可以理解为是用于标记第一IE是嵌套的IE，第二IEI可以理解为是用于和第一IEI联合确定第二IE的类型，如此一来，结合第一IEI和第二IEI便可以唯一确定第二IE的类型。示例性地，假设规定第一IEI的取值为十六进制下的80(当然可以其他数值，此处仅为示例)，第二IEI的取值为十六进制下的10，则80-10可以唯一标识第二IE的类型，例如第二IE的类型为5G系统中新增的某个特性所对应的IE，或者，也可以是5G系统中现有的某个特性所对应的IE等，本申请对此不作限定。
第一IE中可以携带有一个或多个第二IE，本申请对此并不限定。在第一IE中携带有多个第二IE的情况下，该多个第二IE可以是类型不同的IE。该多个第二IE可以分别包括对应的第二IEI，如此一来，对于多个第二IE中的某个第二IE而言，便可以根据第一IEI和该第二IE所对应的第二IEI来确定该第二IE的类型。
在第一IE中携带有第二IE的情况下，第一IE也可以理解为是封装的容器，即第一IE的类型可以理解为是NAS消息容器或者扩展类型6 IE容器，该容器中携带有第二IE，例如，携带有多个第二IE。
在本申请实施例中，第一IE中携带有第二IE，如此一来，第二IE的类型可以基于第一IE包含的第一IEI确定。相比于传统的仅使用IE本身包含IEI确定IE的类型的情况，基于嵌套的外部IE的IEI确定内部IE的类型能够扩展IEI标识的IE的数量，从而能够解决IEI不够用的问题。
在一些实施例中，第二IE可以嵌套在第一IE的数值部分(第一数值部分)，即第一IE的数值部分可以携带有第二IE。如图7所示，第一IE的数值部分嵌套有多个第二IE(第1个第二IE至第k个第二IE)。每个第二IE的编码方式类似于第一IE的编码方式，即均可以采用格式TLV或TLV-E进行编码。也就是说，每个第二IE都可以包括一个IEI，例如第1个第二IE的IEI，第2个第二IE的IEI，至第k个第二IE的IEI。如此一来，第一IEI和第1个第二IE的IEI可以用于唯一标识第1个第二IE的类型，第一IEI和第2个第二IE的IEI可以用于唯一标识第2个第二IE的类型，等等。
为了避免第一IE中携带有第二IE的情况下还不能完全解决IEI值不够用的问题，在一些实施例中，可以在第二IE中继续嵌套第三IE，即第二IE中还携带有第三IE。下面结合图8对第二IE中携带有第三IE进行说明。
如图8所示，在第一IE的数值部分(第一数值部分)携带有一个或多个第二IE(第1个第二IE至第k个第二IE)。该一个或多个第二IE中的部分或全部第二IE中还携带有第三IE。例如，该一个或多个第二IE中的某个第二IE中携带有第三IE，比如，第1个第二IE中携带有第三IE，或者第k个第二IE中携带有第三IE。或者，该一个或多个第二IE中的某些第二IE中携带有第三IE，比如，第1个第二IE和第k个第二IE中均可以携带有第三IE。
在一些实施例中，第三IE可以嵌套在第二IE的数值部分，即第二IE的数值部分可以携带有第三IE。以图8为例，第一IE的数值部分(第一数值部分)携带有k个第二IE，且第k个第二IE的数值部分携带有第三IE。
在一些实施例中，第三IE可以是可选的IE，即第三IE的存在性(presence)为可选的。也就是说，在某些NAS消息中，可以包括第三IE；在某些NAS消息中，也可以不包括第三IE。
第三IE可以包括第三IEI，在第三IE包括第三IEI的情况下，可以认为，第三IE采用格式TLV或TLV-E进行编码。关于第三IE的编码方式，其与第一IE或第二IE的编码方式是类似的，可以参见前文的相关描述。
在一些实施例中，第三IE的类型是基于第一IEI、第二IEI和第三IEI确定的。结合第一IEI、第二IEI和第三IEI可以唯一确定第三IE的类型。
第二IE中可以携带有一个或多个第三IE，本申请对此并不限定。在第二IE中携带有多个第三IE的情况下，该多个第三IE可以是类型不同的IE。该多个第三IE可以分别包括对应的第三IEI，如此一来，对于多个第三IE中的某个第三IE而言，便可以根据第一IEI、携带该第三IE的第二IE所对应的第二IEI、以及该第三IE所对应的第三IEI来确定该第三IE的类型。
本申请实施例对第一IEI的取值不作限定。示例性地，第一IEI的取值可以是协议规定的某个值，例如是十六进制下某个还未被使用的，可以作为IEI的值，该值可以认为是待确定(to be determined)的值，该待确定的值可以用于专门标识第一IEI的类型。作为一个具体示例，假设十六进制下的80(当然可以其他数值，此处仅为示例)目前还未被使用为IEI，则第一IEI的取值可以设置为十六进制下的80，以标识第一IE为嵌套的IE。
或者，第一IEI的取值可以是采用现有的IEI，例如第一IE为类型6的IE时，第一IEI可以使用现有的十六进制的70-7F中的某个值，这种情况下，被替代的IE可以重新用其他IEI定义。例如，可以将原来被替代的IE嵌到第一IE中，用第一IEI结合第二IEI来标识该被替代的IE的类型。优选地，第一IEI的取值采用现有的IEI时，可以使用十六进制下 的70-7B中的某个值，以避免第一设备因不能理解该第一IE而丢弃整个NAS消息。作为一个具体示例，第一IEI的取值可以设置为十六进制下的70，以标识第一IE为嵌套的IE，而被替代的70所标识的IE(NSSRG信息IE)可以嵌入到第一IE中，用第一IEI(70)和第二IEI(比如，70或其他数值)来联合标识。也就是说，在本申请实施例中，十六进制下的70可以用于标识第一IEI，而70-70可以用于标识被替代的IE(NSSRG信息IE)。
在一些实施例中，第二IEI的取值可以采用某个待确定的值，用于专门标识第二IE；也可以继续使用现有的IEI，这种情况下，被替代的IE可以重新用其他IEI定义，比如可以将原来被替代的IE嵌到第二IE中。以第二IE为类型6的IE为例，第二IE采用现有的IEI时，可以是指第二IEI的取值范围可以是70-7F。优选地，第二IEI的取值采用现有的IEI时，可以使用十六进制下的70-7B中的某个值，以避免第一设备因不能理解该第二IE而丢弃整个NAS消息。
在一些实施例中，第一IE和/或第一IE中携带的IE为允许第一设备忽略的IE。但本申请实施例并不限定于此，即第一IE和/或第一IE中携带的IE可以为不允许第一设备忽略的IE。
允许第一设备忽略的IE可以是指，第一设备接收到第二设备发送的NAS消息后，如果第一设备不能理解该NAS消息中的这类IE(允许第一设备忽略的IE)，则第一设备可以直接忽略这类IE，而处理NAS消息中的其他IE。在一些实施例中，允许第一设备忽略的IE也可以称为非需要理解的IE(no-comprehension required IE)。以类型6的IE为例，类型6的IEI的取值范围在十六进制下表示为70-7B时表示该IE的格式是TLV-E，在该范围内的IE，如果第一设备不能理解这类IE，第一设备可以忽略该IE，处理NAS消息中的其他IE。
对应地，除了允许第一设备忽略的IE之外，还可以存在不允许第一设备忽略的IE，第一设备接收到第二设备发送的NAS消息后，如果第一设备不能理解NAS消息中的这类IE(不允许第一设备忽略的IE)，则第一设备需要丢弃整个NAS消息。在一些实施例中，不允许第一设备忽略的IE也可以称为需要理解的IE(comprehension required IE)。仍然以类型6的IE为例，类型6的IEI的取值范围为011111xx(在十六进制下表示为7C-7F)时表示该IE的格式是TLV-E，在该范围内的IE，第一设备需要理解该IE，如果第一设备不能理解这类IE，第一设备需要丢弃整个NAS消息。可选地，第一设备丢弃整个NAS消息后，还需要向第二设备返回移动性管理状态消息(例如，5GMM状态消息)，以通知第二设备未成功接收NAS消息。示例性地，返回的移动性管理状态消息中携带有未成功接收NAS消息的原因值，即携带有原因值“必选信息单元差错(invalid mandatory information)”。
第一IE中携带的IE可以是指第一IE中直接携带的第二IE，也可以是指通过第二IE携带的第三IE，本申请对此不作限定。示例性地，第一IE、第二IE和第三IE均为允许第一设备忽略的IE；或者，第一IE、第二IE和第三IE中的部分IE可以为允许第一设备忽略的IE。
作为一个具体示例，第一IE是允许第一设备忽略的IE，则第一设备接收到第二设备发送的NAS消息后，不能理解该NAS消息中的第一IE时，第一设备可以直接忽略第一IE，处理NAS消息中的除第一IE之外的其他IE。以第一IE为类型6的IE为例，在第一IEI的取值范围在十六进制下为70-7B的情况下，第一IE可以理解为允许第一设备忽略的IE。但本申请实施例并不限定于此，例如，第一IE为类型6的IE时，第一IEI的取值范围在十六进制下也可以是7C-7F，即第一IE也可以理解为是不允许第一设备忽略的IE。
在第一IE和/或第一IE中携带的IE为允许第一设备忽略的IE的情况下，如果第一设备不能理解该第一IE或第一IE中携带的IE时，第一设备直接忽略第一IE或第一IE中携带的IE，而处理其他的IE，这种方式具有良好的兼容性。
如前文所述，在一些实施例中，第一IE可以为类型6的IE。在第一IE为类型6的IE 的情况下，第一IE中携带的IE可以是类型6的IE，也可以是类型4的IE，本申请实施例对此不作限定。示例性地，第一IE中携带有第二IE的情况下，第一IE为类型6的IE时，第二IE可以是类型6的IE，也可以是类型4的IE。第一IE为类型4的IE时，第二IE可以是类型4的IE。
在一些实施例中，第二IE为类型6的IE时，第二IE中携带的IE可以是类型6的IE，也可以是类型4的IE。换句话说，第三IE可以是类型6的IE，也可以是类型4的IE。第二IE为类型4的IE时，第三IE可以是类型4的IE。
上文结合图1至图8，详细描述了本申请的方法实施例，下面结合图9至图11，详细描述本申请的装置实施例。应理解，方法实施例的描述与装置实施例的描述相互对应，因此，未详细描述的部分可以参见前面方法实施例。
图9是本申请一实施例提供的通信装置的结构示意图。图9所示的通信装置900可以应用于第一设备，该第一设备可以是前文提及的任一第一设备。通信装置900可以包括处理模块910和接收模块920。
处理模块910可以用于通过接收模块920接收第二设备发送的NAS消息，其中，所述NAS消息包括第一信息单元IE，所述第一IE包括第一信息单元标识IEI，所述第一IE中携带有第二IE，所述第二IE包括第二IEI。
可选地，所述第二IE的类型基于所述第一IEI和所述第二IEI确定。
可选地，所述第二IE中携带有第三IE，所述第三IE包括第三IEI，所述第三IE的类型基于所述第一IEI、所述第二IEI和所述第三IEI确定。
可选地，所述第一IE和/或所述第一IE中携带的IE为允许所述第一设备忽略的IE。
可选地，所述第一IE为类型6的IE，所述第一IEI的取值范围在十六进制下为70至7B。
可选地，所述NAS消息为注册接受消息。
可选地，所述第一IE为类型6的IE。
可选地，所述第二IE为类型6或类型4的IE。
可选地，所述第二IE中携带的IE为类型6或类型4的IE。
图10是本申请另一实施例提供的通信装置的结构示意图。图10所示的通信装置1000可以应用于第二设备，该第二设备可以是前文提及的任一第二设备。通信装置1000可以包括处理模块1010和发送模块1020。
处理模块1010可以用于通过发送模块1020向第一设备发送NAS消息，其中，所述NAS消息包括第一信息单元IE，所述第一IE包括第一信息单元标识IEI，所述第一IE中携带有第二IE，所述第二IE包括第二IEI。
可选地，所述第二IE的类型基于所述第一IEI和所述第二IEI确定。
可选地，所述第二IE中携带有第三IE，所述第三IE包括第三IEI，所述第三IE的类型基于所述第一IEI、所述第二IEI和所述第三IEI确定。
可选地，所述第一IE和/或所述第一IE中携带的IE为允许所述第一设备忽略的IE。
可选地，所述第一IE为类型6的IE，所述第一IEI的取值范围在十六进制下为70至7B。
可选地，所述NAS消息为注册接受消息。
可选地，所述第一IE为类型6的IE。
可选地，所述第二IE为类型6或类型4的IE。
可选地，所述第二IE中携带的IE为类型6或类型4的IE。
图11是本申请实施例的通信装置的示意性结构图。图11中的虚线表示该单元或模块为可选的。该装置1100可用于实现上述方法实施例中描述的方法。装置1100可以是芯片、终端设备或网络设备。
装置1100可以包括一个或多个处理器1110。该处理器1110可支持装置1100实现前文方法实施例所描述的方法。该处理器1110可以是通用处理器或者专用处理器。例如，该处理器可以为中央处理单元(central processing unit，CPU)。或者，该处理器还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
装置1100还可以包括一个或多个存储器1120。存储器1120上存储有程序，该程序可以被处理器1110执行，使得处理器1110执行前文方法实施例所描述的方法。存储器1120可以独立于处理器1110也可以集成在处理器1110中。
装置1100还可以包括收发器1130。处理器1110可以通过收发器1130与其他设备或芯片进行通信。例如，处理器1110可以通过收发器1130与其他设备或芯片进行数据收发。
本申请实施例还提供一种计算机可读存储介质，用于存储程序。该计算机可读存储介质可应用于本申请实施例提供的终端或网络设备中，并且该程序使得计算机执行本申请各个实施例中的由终端或网络设备执行的方法。
本申请实施例还提供一种计算机程序产品。该计算机程序产品包括程序。该计算机程序产品可应用于本申请实施例提供的终端或网络设备中，并且该程序使得计算机执行本申请各个实施例中的由终端或网络设备执行的方法。
本申请实施例还提供一种计算机程序。该计算机程序可应用于本申请实施例提供的终端或网络设备中，并且该计算机程序使得计算机执行本申请各个实施例中的由终端或网络设备执行的方法。
应理解，本申请中术语“系统”和“网络”可以被可互换使用。另外，本申请使用的术语仅用于对本申请的具体实施例进行解释，而非旨在限定本申请。本申请的说明书和权利要求书及所述附图中的术语“第一”、“第二”、“第三”和“第四”等是用于区别不同对象，而不是用于描述特定顺序。此外，术语“包括”和“具有”以及它们任何变形，意图在于覆盖不排他的包含。
在本申请的实施例中，提到的“指示”可以是直接指示，也可以是间接指示，还可以是表示具有关联关系。举例说明，A指示B，可以表示A直接指示B，例如B可以通过A获取；也可以表示A间接指示B，例如A指示C，B可以通过C获取；还可以表示A和B之间具有关联关系。
在本申请实施例中，“与A相应的B”表示B与A相关联，根据A可以确定B。但还应理解，根据A确定B并不意味着仅仅根据A确定B，还可以根据A和/或其它信息确定B。
在本申请实施例中，术语“对应”可表示两者之间具有直接对应或间接对应的关系，也可以表示两者之间具有关联关系，也可以是指示与被指示、配置与被配置等关系。
本申请实施例中，“预定义”或“预配置”可以通过在设备(例如，包括终端设备和网络设备)中预先保存相应的代码、表格或其他可用于指示相关信息的方式来实现，本申请对于其具体的实现方式不做限定。比如预定义可以是指协议中定义的。
本申请实施例中，所述“协议”可以指通信领域的标准协议，例如可以包括LTE协议、NR协议以及应用于未来的通信系统中的相关协议，本申请对此不做限定。
本申请实施例中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何 限定。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够读取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，数字通用光盘(digital video disc，DVD))或者半导体介质(例如，固态硬盘(solid state disk，SSD))等。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (43)

  1. 一种通信方法，其特征在于，包括：
    第一设备接收第二设备发送的非接入层NAS消息；
    其中，所述NAS消息包括第一信息单元IE，所述第一IE包括第一信息单元标识IEI，所述第一IE中携带有第二IE。
  2. 根据权利要求1所述的方法，其特征在于，所述第二IE包括第二IEI，所述第二IE的类型基于所述第一IEI和所述第二IEI确定。
  3. 根据权利要求1或2所述的方法，其特征在于，所述第二IE中携带有第三IE，所述第三IE包括第三IEI，所述第三IE的类型基于所述第一IEI、所述第二IE包含的第二IEI和所述第三IEI确定。
  4. 根据权利要求1-3中任一项所述的方法，其特征在于，所述第一IE和/或所述第一IE中携带的IE为允许所述第一设备忽略的IE。
  5. 根据权利要求1-4中任一项所述的方法，其特征在于，所述第一IE为类型6的IE，所述第一IEI的取值范围在十六进制下为70至7B。
  6. 根据权利要求1-5中任一项所述的方法，其特征在于，所述NAS消息为注册接受消息。
  7. 根据权利要求1-4、6中任一项所述的方法，其特征在于，所述第一IE为类型6的IE。
  8. 根据权利要求1-7中任一项所述的方法，其特征在于，所述第二IE为类型6或类型4的IE。
  9. 根据权利要求1-8中任一项所述的方法，其特征在于，所述第二IE中携带的IE为类型6或类型4的IE。
  10. 一种通信方法，其特征在于，包括：
    第二设备向第一设备发送非接入层NAS消息；
    其中，所述NAS消息包括第一信息单元IE，所述第一IE包括第一信息单元标识IEI，所述第一IE中携带有第二IE。
  11. 根据权利要求10所述的方法，其特征在于，所述第二IE包括第二IEI，所述第二IE的类型基于所述第一IEI和所述第二IEI确定。
  12. 根据权利要求10或11所述的方法，其特征在于，所述第二IE中携带有第三IE，所述第三IE包括第三IEI，所述第三IE的类型基于所述第一IEI、所述第二IE包含的第二IEI和所述第三IEI确定。
  13. 根据权利要求10-12中任一项所述的方法，其特征在于，所述第一IE和/或所述第一IE中携带的IE为允许所述第一设备忽略的IE。
  14. 根据权利要求10-13中任一项所述的方法，其特征在于，所述第一IE为类型6的IE，所述第一IEI的取值范围在十六进制下为70至7B。
  15. 根据权利要求10-14中任一项所述的方法，其特征在于，所述NAS消息为注册接受消息。
  16. 根据权利要求10-13、15中任一项所述的方法，其特征在于，所述第一IE为类型6的IE。
  17. 根据权利要求10-16中任一项所述的方法，其特征在于，所述第二IE为类型6或类型4的IE。
  18. 根据权利要求10-17中任一项所述的方法，其特征在于，所述第二IE中携带的IE为类型6或类型4的IE。
  19. 一种通信装置，其特征在于，所述装置应用于第一设备，所述装置包括处理模块和接收模块，
    所述处理模块用于通过所述接收模块接收第二设备发送的非接入层NAS消息；
    其中，所述NAS消息包括第一信息单元IE，所述第一IE包括第一信息单元标识IEI，所述第一IE中携带有第二IE。
  20. 根据权利要求19所述的装置，其特征在于，所述第二IE包括第二IEI，所述第二IE的类型基于所述第一IEI和所述第二IEI确定。
  21. 根据权利要求19或20所述的装置，其特征在于，所述第二IE中携带有第三IE，所述第三IE包括第三IEI，所述第三IE的类型基于所述第一IEI、所述第二IE包含的第二IEI和所述第三IEI确定。
  22. 根据权利要求19-21中任一项所述的装置，其特征在于，所述第一IE和/或所述第一IE中携带的IE为允许所述第一设备忽略的IE。
  23. 根据权利要求19-22中任一项所述的装置，其特征在于，所述第一IE为类型6的IE，所述第一IEI的取值范围在十六进制下为70至7B。
  24. 根据权利要求19-23中任一项所述的装置，其特征在于，所述NAS消息为注册接受消息。
  25. 根据权利要求19-22、24中任一项所述的装置，其特征在于，所述第一IE为类型6的IE。
  26. 根据权利要求19-25中任一项所述的装置，其特征在于，所述第二IE为类型6或类型4的IE。
  27. 根据权利要求19-26中任一项所述的装置，其特征在于，所述第二IE中携带的IE为类型6或类型4的IE。
  28. 一种通信装置，其特征在于，所述装置应用于第二设备，所述装置包括处理模块和发送模块，
    所述处理模块用于通过所述发送模块向第一设备发送非接入层NAS消息；
    其中，所述NAS消息包括第一信息单元IE，所述第一IE包括第一信息单元标识IEI，所述第一IE中携带有第二IE。
  29. 根据权利要求28所述的装置，其特征在于，所述第二IE包括第二IEI，所述第二IE的类型基于所述第一IEI和所述第二IEI确定。
  30. 根据权利要求28或29所述的装置，其特征在于，所述第二IE中携带有第三IE，所述第三IE包括第三IEI，所述第三IE的类型基于所述第一IEI、所述第二IE包含的第二IEI和所述第三IEI确定。
  31. 根据权利要求28-30中任一项所述的装置，其特征在于，所述第一IE和/或所述第一IE中携带的IE为允许所述第一设备忽略的IE。
  32. 根据权利要求28-31中任一项所述的装置，其特征在于，所述第一IE为类型6的IE，所述第一IEI的取值范围在十六进制下为70至7B。
  33. 根据权利要求28-32中任一项所述的装置，其特征在于，所述NAS消息为注册接受消息。
  34. 根据权利要求28-31、33中任一项所述的装置，其特征在于，所述第一IE为类型6的IE。
  35. 根据权利要求28-34中任一项所述的装置，其特征在于，所述第二IE为类型6或类型4的IE。
  36. 根据权利要求28-35中任一项所述的装置，其特征在于，所述第二IE中携带的IE为类型6或类型4的IE。
  37. 一种第一设备，其特征在于，包括存储器和处理器，所述存储器用于存储程序，所述处理器用于调用所述存储器中的程序，以使所述第一设备执行如权利要求1-9中任一项所述的方法。
  38. 一种第二设备，其特征在于，包括存储器和处理器，所述存储器用于存储程序，所述处理器用于调用所述存储器中的程序，以使所述第二设备执行如权利要求10-18中任一项所述的方法。
  39. 一种装置，其特征在于，包括处理器，用于从存储器中调用程序，以使所述装置执行如权利要求1-18中任一项所述的方法。
  40. 一种芯片，其特征在于，包括处理器，用于从存储器调用程序，使得安装有所述芯片的设备执行如权利要求1-18中任一项所述的方法。
  41. 一种计算机可读存储介质，其特征在于，其上存储有程序，所述程序使得计算机执行如权利要求1-18中任一项所述的方法。
  42. 一种计算机程序产品，其特征在于，包括程序，所述程序使得计算机执行如权利要求1-18中任一项所述的方法。
  43. 一种计算机程序，其特征在于，所述计算机程序使得计算机执行如权利要求1-18中任一项所述的方法。
PCT/CN2022/102841 2022-06-30 2022-06-30 通信方法和通信装置 WO2024000412A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2022/102841 WO2024000412A1 (zh) 2022-06-30 2022-06-30 通信方法和通信装置
CN202280091296.5A CN118679765A (zh) 2022-06-30 2022-06-30 通信方法和通信装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/102841 WO2024000412A1 (zh) 2022-06-30 2022-06-30 通信方法和通信装置

Publications (1)

Publication Number Publication Date
WO2024000412A1 true WO2024000412A1 (zh) 2024-01-04

Family

ID=89383724

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/102841 WO2024000412A1 (zh) 2022-06-30 2022-06-30 通信方法和通信装置

Country Status (2)

Country Link
CN (1) CN118679765A (zh)
WO (1) WO2024000412A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024094902A1 (en) * 2024-01-30 2024-05-10 Lenovo (Singapore) Pte. Ltd. Method and apparatus for extended information element identifier

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170318463A1 (en) * 2016-04-27 2017-11-02 Qualcomm Incorporated Enhanced non-access stratum security
CN108809565A (zh) * 2017-05-04 2018-11-13 华为技术有限公司 消息的传输方法、及设备
CN110557785A (zh) * 2018-05-30 2019-12-10 大唐移动通信设备有限公司 一种基于mec的数据分流方法及装置
CN110574407A (zh) * 2018-03-06 2019-12-13 联发科技（新加坡）私人有限公司 用于保护初始非接入层消息的装置和方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170318463A1 (en) * 2016-04-27 2017-11-02 Qualcomm Incorporated Enhanced non-access stratum security
CN108809565A (zh) * 2017-05-04 2018-11-13 华为技术有限公司 消息的传输方法、及设备
CN110574407A (zh) * 2018-03-06 2019-12-13 联发科技（新加坡）私人有限公司 用于保护初始非接入层消息的装置和方法
CN110557785A (zh) * 2018-05-30 2019-12-10 大唐移动通信设备有限公司 一种基于mec的数据分流方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Security aspects of Machine-Type and other Mobile Data Applications Communications Enhancements; (Release 12)", 3GPP TR 33.868, no. V0.15.0, 30 September 2013 (2013-09-30), pages 1 - 115, XP050712804 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024094902A1 (en) * 2024-01-30 2024-05-10 Lenovo (Singapore) Pte. Ltd. Method and apparatus for extended information element identifier

Also Published As

Publication number Publication date
CN118679765A (zh) 2024-09-20

Similar Documents

Publication Publication Date Title
US11765686B2 (en) Packet transmission method and apparatus for communicating between terminals of a same 5G LAN group
WO2022257549A1 (zh) 网络切片方法、设备及存储介质
EP4138363A1 (en) Packet transmission method and system
US20230199550A1 (en) Relay Management Method and Communication Apparatus
WO2021136211A1 (zh) 授权结果的确定方法及装置
US11259362B2 (en) Method for repeatedly transmitting data and device
WO2022052851A1 (zh) 一种服务质量QoS的监测方法
US20230254922A1 (en) Multipath transmission method and communication apparatus
WO2022033543A1 (zh) 一种中继通信方法及通信装置
US11510257B2 (en) Communications method and apparatus
WO2024000412A1 (zh) 通信方法和通信装置
JP2024506066A (ja) 災害ローミング方法、装置、およびシステム
EP4401384A1 (en) Data transmission method and communication apparatus
US20220360969A1 (en) Communication method and apparatus
WO2023020481A1 (zh) 用于传输数据的方法和装置
CN116132581A (zh) 来电拦截方法及装置、终端设备、计算机可读存储介质
WO2021138784A1 (zh) 一种接入网络的方法、装置及系统
WO2021042381A1 (zh) 一种通信方法、装置及系统
WO2018228545A1 (zh) 信息处理方法以及相关装置
WO2022188156A1 (zh) 通信方法和通信装置
WO2023087262A1 (zh) 通信方法及通信装置
WO2023205959A1 (zh) 通信方法及通信装置
WO2023155046A1 (zh) 通信方法和通信装置
WO2023123315A1 (zh) 无线通信的方法、终端设备和网络设备
WO2024145884A1 (zh) 通信方法及通信装置

Legal Events

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

Ref document number: 22948517

Country of ref document: EP

Kind code of ref document: A1