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

通信方法和装置 Download PDF

Info

Publication number
WO2020057497A1
WO2020057497A1 PCT/CN2019/106173 CN2019106173W WO2020057497A1 WO 2020057497 A1 WO2020057497 A1 WO 2020057497A1 CN 2019106173 W CN2019106173 W CN 2019106173W WO 2020057497 A1 WO2020057497 A1 WO 2020057497A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
access network
network device
group
context
Prior art date
Application number
PCT/CN2019/106173
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 EP19863769.6A priority Critical patent/EP3840520B1/en
Publication of WO2020057497A1 publication Critical patent/WO2020057497A1/zh
Priority to US17/203,992 priority patent/US11963218B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/60—Context-dependent security
    • H04W12/69—Identity-dependent
    • H04W12/76—Group identity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/006—Transmission of channel access control information in the downlink, i.e. towards the terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • 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]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08—Access security
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/60—Context-dependent security
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/60—Context-dependent security
    • H04W12/69—Identity-dependent
    • H04W12/71—Hardware identity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/121—Wireless traffic scheduling for groups of terminals or users
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/08—User group management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present application relates to the field of communications, and more particularly, to a communication method and apparatus.
  • the access network device In current access technologies, for each terminal device accessing the access network device, the access network device needs to save a set of contexts for each terminal device. With the development of society, more and more terminal devices are connected to the network, such as low power wide area (LPWA) user equipment (UE), and various intelligent terminals, etc., are required to access the network. In the future, the 5th generation (5G) network will need to support millions of connections. In the case where a large number of terminal devices access the same access network device, according to the manner in which the access network device saves a set of contexts for each terminal device separately, a large amount of storage resources of the access network device will be consumed.
  • LPWA low power wide area
  • UE user equipment
  • 5G 5th generation
  • the present application provides a communication method and device, which can reduce storage resources or signaling overhead required for an access network device to maintain a terminal device context.
  • the present application provides a communication method.
  • the method includes: receiving a first message from a first access network device, wherein the first message includes a group identifier corresponding to the terminal device and an identifier of the terminal device, and the group identifier is used to identify the terminal The group to which the device belongs, and the identifier of the terminal device is used to identify the terminal device within the group to which the terminal device belongs, the group identifier corresponds to a public context, and the public context is owned by all terminals in the group to which the terminal device belongs Device sharing, the identity of the terminal device corresponds to the dedicated context of the terminal device; the group identity and the identity of the terminal device are saved.
  • the context of the terminal devices includes a public context corresponding to the group identity and a private context corresponding to the identity of the terminal device, where all terminal devices in each group share the same A common context, and each terminal device uses its own dedicated context.
  • the access network device maintains the context of the terminal device, it does not need to store all the context of each terminal device, which can reduce the maintenance context of the access network device.
  • Resource requirements For example, if the terminal device is the first terminal device in the group to access the first access network device, the first access network device may configure and save the public context corresponding to the group to which the terminal device belongs and the private context corresponding to the terminal device.
  • the first access network device only needs to configure and save the dedicated contexts of other terminal devices. If the first access network device has saved the public context corresponding to the packet corresponding to the terminal device before configuring the context of the terminal device, the first access network device does not need to save the public context corresponding to the terminal device.
  • the public context may include one or more of the following information: quality of service (QoS) attributes, radio resource control (RRC) configuration, and service data adaptation protocol (Service Data Adaptation) Protocol (SDAP) configuration, data radio bearer (DRB) configuration, terminal device capabilities, and types of security parameters supported by the terminal device. That is to say, for a specific packet, one or more of the QoS attributes, RRC configuration, SDAP configuration, DRB configuration, capabilities of the terminal device, and the type of security parameters supported by the terminal device are the same for all terminal devices in the group.
  • QoS quality of service
  • RRC radio resource control
  • SDAP service data adaptation protocol
  • DRB data radio bearer
  • the QoS attribute may include one or more of the following: priority, packet delay planning, packet error rate, delay sensitive indication, average window, and maximum burst of data packets.
  • the dedicated context may include security parameters.
  • the dedicated context of the terminal device may include security parameters of the terminal device.
  • the security parameters include at least one of an integrity protection algorithm, an encryption algorithm, and a security key parameter.
  • the security key parameter may be at least one of a KgNB key, a next hop (NH) key, and a next hop key (next hopping chaining count, NCC).
  • the security key parameters may also include signaling plane and / or user plane keys for integrity protection and / or encryption protection.
  • the dedicated context may also be other information, or the dedicated context may include other information in addition to the security parameters, which is not limited in the embodiment of the present application. For example, instead of using the SDAP configuration information as a public context, and using the SDAP configuration information as a private context, or part of the SDAP configuration information can be used as a public context and the other part can be used as a private context.
  • the method may further include: receiving the common context from the first access network device.
  • the method may further include: receiving the dedicated context from the first access network device.
  • the method may further include: sending a second message to a second access network device, where the second message is used to request access to the second access Network device, the second message includes an identifier of the terminal device and the group identifier, or the second message is carried on a physical resource corresponding to the group identifier and the second message includes the terminal The ID of the device.
  • Sending the second message to the second access network device enables the second access network device to determine the identifier of the terminal device and the group identifier. Therefore, when the terminal device needs to access the second access network device, the second access network device can obtain the public context and the private context from the first access network device according to the identifier of the terminal device and the group identifier.
  • a communication method includes determining a group identifier corresponding to a terminal device and an identifier of the terminal device, the group identifier is used to identify a group to which the terminal device belongs, and the terminal device identifier is used to identify within the group to which the terminal device belongs.
  • the group identifier corresponds to a public context, and the public context is shared by all terminal devices in the group to which the terminal device belongs, and the terminal device identifier corresponds to the private context of the terminal device;
  • the terminal device sends a first message, and the first message includes the group identifier and an identifier of the terminal device.
  • the context of the terminal devices includes a public context corresponding to the group identity and a private context corresponding to the identity of the terminal device, where all terminal devices in each group share the same A common context, and each terminal device uses its own private context.
  • the access network device maintains the context of the terminal device, it does not need to store all the context of each terminal device, which can reduce the access network device maintenance context. Resource requirements.
  • the group identifier corresponding to the terminal device may be determined according to the attribute information of the terminal device and a preset rule.
  • the attribute information of the terminal device may be a quality of service (QoS) attribute, a service type of the terminal device, a slice type of the terminal device, a capability of the terminal device, whether the terminal device is stationary, a power saving requirement of the terminal device, and a terminal One or more of the equipment's latency requirements.
  • the preset rule may define a correspondence between a group identifier and attribute information of the terminal device. Therefore, according to the attribute information of the terminal device, the group identifier corresponding to the terminal device can be determined.
  • the method further includes: sending the public context to the terminal device.
  • the method further includes: sending the dedicated context to the terminal device.
  • the method further includes: sending a fourth message to the core network device, the fourth message includes the group identifier, and the fourth message is used for requesting Configuring, by the core network device, a next generation application protocol stack / NG interface application layer protocol (NGAP) connection configuration parameter corresponding to the group identifier; and receiving the NGAP connection configuration parameter sent by the core network device.
  • NGAP next generation application protocol stack / NG interface application layer protocol
  • the method further includes: sending an activation request message to the core network device, the activation request message including the group identifier, and the activation request message is used for all
  • the method requests the core network device to be another terminal device (for example, terminal device # 1B below) to activate the NGAP connection configuration parameter; and receives a response sent by the core network device.
  • the response is an acknowledgment (ACK) or a negative acknowledgment (NACK).
  • the activation request message may further carry identification information used by the core network device to identify the another terminal device.
  • the identification information used for the core network equipment to identify the terminal equipment may be International Mobile Subscriber Identity (IMSI), System Architecture Evolution Temporary Mobile Subscriber Identity (S-TMSI), and IMSI or Other identification information related to S-TMSI.
  • the determining a group identifier corresponding to a terminal device includes: receiving the group identifier from a core network device.
  • the method further includes: receiving an NGAP connection configuration parameter corresponding to the group identifier sent by the core network device.
  • the method further includes: receiving activation instruction information sent by the core network device, where the activation instruction information is used to indicate that the group identifier is the group identifier
  • Another terminal device activates the NGAP connection configuration parameter; and activates the NGAP connection configuration parameter for the other terminal device according to the activation instruction information.
  • the method further includes: sending a response to the core network device.
  • the response is ACK or NACK.
  • a communication method including: a second access network device receives a second message from a terminal device, where the second message is used by the terminal device to request access to the second access network device; The second access network device determines, according to the second message, a group identifier corresponding to the terminal device and an identifier of the terminal device, where the group identifier is used to identify a group to which the terminal device belongs, and the identifier of the terminal device Configured to identify the terminal device within a group to which the terminal device belongs, the identifier of the terminal device corresponding to a dedicated context of the terminal device; the second access network device sends the first access network device A third message, the third message including the group identity and the identity of the terminal device; the second access network device receiving a third response message from the first access network device, and the third response The message includes the dedicated context.
  • the terminal devices are grouped so that the context of the terminal devices may include a public context corresponding to the grouping and a private context corresponding to the terminal device.
  • the second access network device may only The private context of the terminal device may be obtained from the first access network device, and the public context corresponding to the packet to which the terminal device belongs may not be obtained from the first access network device.
  • the first access network device can only send the dedicated context of the terminal device to the second access network device, and does not send the terminal device to the public context corresponding to the packet to which the terminal device belongs, thereby saving signaling overhead. Therefore, the method for acquiring the context of the terminal device in this application can reduce the signaling overhead of forwarding the context of the terminal device between the access network devices.
  • the third response message further includes a public context corresponding to the group identifier.
  • the public context may be obtained from the first access network device.
  • the second message includes an identifier of the terminal device and the group identifier; or the second message includes an identifier of the terminal device, and The second message is carried on a physical resource corresponding to the group identity.
  • the first access network device may determine the identity of the terminal device and the group identity.
  • the second request message further includes short message authentication code integrity or, for example, short message authentication code integrity (short message authentication code integrity), shortMAC-I) or short recovery message integrity code short integrity MAC-I), the integrity of the short message authentication code is based on the physical characteristics of the first serving cell by the terminal device. The cell identity, the cell identity of the second serving cell, and the group identity are determined.
  • the first serving cell is served by the first access network device, and the second serving cell is served by the second access network device. It should also be understood that, in the embodiment of the present application, the first access network device is a source base station, the second access network device is a target base station, or the first serving cell is a source serving cell, and the second serving cell is a target serving cell. .
  • the integrity of the short message authentication code is at least based on the physical cell identifier (PCI) of the first serving cell, the cell identifier of the second serving cell, and the terminal identifier of the terminal device in the first serving cell. (Such as the cell radio network temporary network identifier (C-RNTI)).
  • PCI physical cell identifier
  • C-RNTI cell radio network temporary network identifier
  • different terminal equipments have different terminal identities in the first serving cell, so the short message authentication code integrity used to verify the terminal equipment in the access network equipment is also different.
  • the group identifier # 1 is used instead of the terminal identifier, so that the short message authentication code integrity of the terminal identifiers with the same group identifier is the same, that is, the short message authentication code integrity can be changed from the private context of the terminal device to the public context. Therefore, the storage overhead of the dedicated context of the terminal device can be further saved.
  • the third response message further includes at least one of the following: a dedicated context of other terminal devices within the group corresponding to the group identifier; the Attribute information of the terminal equipment corresponding to the group identifier; wherein the attribute information of the terminal equipment includes at least one of the following information: quality of service attributes of services of the terminal equipment, service type of the terminal equipment, slice type of the terminal equipment, Terminal equipment capabilities, whether terminal equipment is stationary, terminal equipment power saving requirements, and terminal equipment delay requirements.
  • the first access network device may return the context requested by the second access network device to the second access network device, and return the terminal device to the second access network device in addition to the terminal device.
  • the identity of the at least one other terminal device and the corresponding dedicated context In this way, if any terminal device other than the terminal device (for example, terminal device # 1C) in the group to which the terminal device belongs needs to access the second access network device, the second access network device does not need to provide the first access network device
  • the access network device sends a request message to request the dedicated context of the terminal device # 1C. Thereby, signaling overhead can be further saved.
  • the first access network device may return the context requested by the second access network device to the second access network device, and return the terminal device corresponding to the group corresponding to the group identifier to the second access network device. Attribute information.
  • the second access network device can better manage each terminal device in the corresponding group of the group identifier according to the group identifier and the attribute information of the terminal device corresponding to the group identifier, thereby helping to improve system performance.
  • the common context includes at least one of the following information: quality of service QoS attributes, radio resource control RRC configuration, service data adaptive protocol SDAP configuration, data The radio bearer DRB configuration, the capabilities of the terminal equipment, and the type of security parameters supported by the terminal equipment.
  • the third message includes indication information, where the indication information is used to indicate whether a public context corresponding to the group identifier is requested, or the indication information It is used to indicate whether to request only a dedicated context corresponding to the identity of the terminal device, or the indication information is used to indicate whether to request all contexts of the terminal device.
  • a communication method including: the first access network device receives a third message from the second access network device, and the third message includes a group identifier corresponding to the terminal device and the An identifier of a terminal device, the group identifier is used to identify a group to which the terminal device belongs, the identifier of the terminal device is used to identify the terminal device within a group to which the terminal device belongs, and the identifier of the terminal device and the The dedicated context of the terminal device corresponds; the first access network device sends a third response message, and the third response message includes the dedicated context.
  • the terminal devices are grouped so that the context of the terminal devices may include a public context corresponding to the grouping and a private context corresponding to the terminal device.
  • the second access network device may only The private context of the terminal device may be obtained from the first access network device, and the public context corresponding to the packet to which the terminal device belongs may not be obtained from the first access network device.
  • the first access network device can only send the dedicated context of the terminal device to the second access network device, and does not send the terminal device to the public context corresponding to the packet to which the terminal device belongs, thereby saving signaling overhead. Therefore, the method for acquiring the context of the terminal device in this application can reduce the signaling overhead of forwarding the context of the terminal device between the access network devices.
  • the third response message further includes a public context corresponding to the group identifier.
  • the third response message further includes at least one of the following: a dedicated context of other terminal devices within a group corresponding to the group identifier; the Attribute information of the terminal equipment corresponding to the group identifier; wherein the attribute information of the terminal equipment includes at least one of the following information: service quality attributes of the services of the terminal equipment, the service type of the terminal equipment, the slice type of the terminal equipment, Terminal equipment capabilities, whether terminal equipment is stationary, terminal equipment power saving requirements, and terminal equipment delay requirements.
  • the common context includes at least one of the following information: quality of service QoS attributes, radio resource control RRC configuration, service data adaptive protocol SDAP configuration, data The radio bearer DRB configuration, the capabilities of the terminal equipment, and the type of security parameters supported by the terminal equipment.
  • the third message includes indication information, where the indication information is used to indicate whether a public context corresponding to the group identifier is requested, or the indication information It is used to indicate whether to request only a dedicated context corresponding to the identity of the terminal device, or the indication information is used to indicate whether to request all contexts of the terminal device.
  • a communication method including: determining a group identifier of a terminal device and an NGAP connection configuration parameter corresponding to the group identifier; and sending the NGAP connection configuration parameter to the first access network device.
  • the determining the group identifier of the terminal device includes: receiving a fourth message from the first access network device, where the fourth message includes the group identifier of the terminal device The fourth message is used to request the core network device to configure an NGAP connection configuration parameter corresponding to the group identifier.
  • the method further includes: receiving an activation request message from the first access network device, the activation request message including the group identifier, and the activation
  • the request message is used for requesting the core network device to be another terminal device (for example, terminal device # 1B hereinafter) to activate the NGAP connection configuration parameter; and receiving a response sent by the core network device.
  • the response is ACK or NACK.
  • the activation request message may further carry identification information used by the core network device to identify the another terminal device.
  • the identification information used for the core network equipment to identify the terminal equipment may be International Mobile Subscriber Identity (IMSI), System Architecture Evolution Temporary Mobile Subscriber Identity (S-TMSI), and IMSI or Other identification information related to S-TMSI.
  • the method further includes: sending activation instruction information to a first access network device, where the activation instruction information is used to indicate the first access network device Activate the NGAP connection configuration parameter for another terminal device whose group identifier is the group identifier.
  • the method further includes: receiving a response from the first access network device.
  • the response is a confirmation message or a failure message or a rejection message.
  • a communication device includes a unit or a module for executing the first aspect or any possible implementation manner of the first aspect.
  • the communication device of the sixth aspect may be a terminal device, or may be a component (such as a chip or a circuit) that can be used for the terminal device.
  • an embodiment of the present application provides a communication device, where the device includes a unit or a module for executing the second aspect or any possible implementation manner of the second aspect.
  • the communication apparatus of the seventh aspect may be an access network device, or may be a component (such as a chip or a circuit) that can be used for the access network device.
  • an embodiment of the present application provides a communication device, where the device includes a unit or a module for executing the third aspect or any possible implementation manner of the third aspect.
  • the communication device of the eighth aspect may be the second access network device in the foregoing method embodiment, or may be a component (such as a chip or a circuit) for the second access network device.
  • an embodiment of the present application provides a communication device, where the device includes a unit or a module for executing the fourth aspect or any possible implementation manner of the fourth aspect.
  • the communication device in the ninth aspect may be the first access network device provided in the fourth aspect, or may be a component (such as a chip or a circuit) for the first access network device.
  • an embodiment of the present application provides a communication device, where the device includes a unit or a module for executing the fifth aspect or any one of the possible implementation manners of the fifth aspect.
  • the communication device of the tenth aspect may be the core network device in the foregoing method embodiment, or may be a component (such as a chip or a circuit) used for the core network device.
  • a communication device including a processor and a memory, where the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the apparatus executes the first aspect to The fifth aspect or the method in any one of the first aspect to the fifth aspect may be implemented.
  • processors there are one or more processors, and one or more memories.
  • the memory may be integrated with the processor, or the memory is separately provided from the processor.
  • the communication device further includes a transceiver or a transceiver circuit, configured to complete a function of transmitting and receiving information.
  • the present application provides a computer-readable storage medium.
  • the computer-readable storage medium stores a computer program.
  • the computer program is executed, the first to fifth aspects or the first aspect is implemented.
  • the method in any one of the possible implementation manners from the aspect to the fifth aspect.
  • the present application provides a computer program product including a computer program.
  • the computer program When the computer program is executed, implement the method in any one of the possible implementation manners of the first to fifth aspects or the first to fifth aspects.
  • the present application provides a chip system that includes an input-output interface and at least one processor, where the at least one processor is configured to call an instruction in a memory to perform the foregoing first to fifth aspects or Operation of the method in any one of the foregoing possible implementation manners of the first to fifth aspects.
  • system chip may further include at least one memory and a bus, and the at least one memory is configured to store instructions executed by the processor.
  • the input / output interface is implemented in an interface circuit manner.
  • FIG. 1 is a schematic diagram of a communication system applied to the present application.
  • FIG. 2 is a schematic flowchart of a communication method provided by the present application.
  • FIG. 3 is a schematic flowchart of another communication method provided by the present application.
  • FIG. 4 is a schematic flowchart of a specific embodiment of a communication method provided by the present application.
  • FIG. 5 is a schematic flowchart of a communication method provided by the present application.
  • FIG. 6 is a schematic flowchart of another communication method provided by the present application.
  • FIG. 7 is a schematic block diagram of a communication device according to the present application.
  • FIG. 8 is a schematic block diagram of a communication device provided by the present application.
  • FIG. 9 is a schematic block diagram of another communication device provided by the present application.
  • FIG. 10 is a schematic block diagram of another communication device provided by the present application.
  • FIG. 11 is a structural block diagram of a terminal device according to an embodiment of the present invention.
  • FIG. 12 is a structural block diagram of an access network device according to an embodiment of the present invention.
  • FIG. 13 is a schematic block diagram of a communication device provided by the present application.
  • FIG. 14 is a structural block diagram of a core network device according to an embodiment of the present invention.
  • GSM global mobile communication
  • CDMA code division multiple access
  • WCDMA broadband code division multiple access
  • GPRS general packet radio service
  • LTE long term evolution
  • FDD frequency division duplex
  • TDD Time Division Duplex
  • UMTS Universal Mobile Telecommunications System
  • WiMAX Worldwide Interoperability for Microwave Access
  • 5G 5th generation
  • 5G 5th generation
  • NR new radio
  • FIG. 1 is a schematic structural diagram of a mobile communication system applied in an embodiment of the present application.
  • the mobile communication system includes a core network device 110, an access network device 120, and terminal devices 130A to 130D.
  • the terminal devices 130A to 130D have the same characteristics, for example, all belong to a smart home or all belong to a smart street light.
  • the terminal device may refer to user equipment, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device.
  • Terminal equipment can also be cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), and wireless communications Functional handheld device, computing device, or other processing device connected to a wireless modem, in-vehicle device, wearable device, terminal device in a 5G network, or terminal in a future evolved public land mobile network (PLMN)
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDAs personal digital assistants
  • PLMN personal digital assistants
  • the equipment and the like are not limited in the embodiments of the present application.
  • the access network equipment can be a global mobile communication (GSM) system or a base station (BTS) in code division multiple access (CDMA), or a broadband code division multiple station (BTS).
  • the network device can be a relay station, an access point, an in-vehicle device, a wearable device, a network device in a 5G network, or a network device in a future evolved PLMN network.
  • the application examples are not limited.
  • the core network device may be a mobility management entity (MME), or a core network access and mobility management function (AMF), or may be other responsible for terminal device access management And mobility management devices, which are not limited in the embodiments of the present application.
  • MME mobility management entity
  • AMF core network access and mobility management function
  • the access network device 120 is connected to the core network device 110 in a wireless or wired manner.
  • the core network device 110 and the access network device 120 may be separate physical devices, or the functions of the core network device 110 and the logical functions of the access network device may be integrated on the same physical device, or may be a physical device. Some functions of the core network device 210 and some functions of the access network device 120 are integrated on the device.
  • the terminal devices 130A to 130D are respectively connected to the access network device 120 in a wireless manner.
  • the terminal devices 130A to 130D have the same attributes and their context may include the same parts, according to the prior art, the access network device 120 still needs to save the context for each terminal device in the terminal devices 130A to 130D, resulting in storage Large resource consumption reduces the performance of access network equipment.
  • the context herein may include configuration information of the terminal device in the network and / or capability information of the terminal device, and the specific content of the context in the embodiment of the present application is not limited.
  • the present application provides a method for obtaining the context of a terminal device, which can reduce the storage resources required for the access network device to store the context of the terminal device.
  • the terminal device context can be divided into two parts: a public context and a private context.
  • Each terminal device of a group is shared, and the dedicated context is the context specific to each terminal device.
  • the access network device stores a common context for each group and the private context of each terminal device in the group, so as to maintain the maintenance of each terminal device.
  • the purpose of the context Since the access network device does not have to store a copy of the same part of the context of multiple terminal devices with the same attributes, it is possible to reduce the storage resources required for the access network device to store the context of the terminal device.
  • the present application will be described in detail.
  • the attribute information may be a quality of service (QoS) attribute, a service type of the terminal device, a slice type of the terminal device, a capability of the terminal device, whether the terminal device is stationary, a power saving requirement of the terminal device, And the latency requirements of terminal equipment.
  • QoS quality of service
  • the attribute information of the terminal device listed here is only an exemplary description, and should not constitute any limitation to this application.
  • the attribute information of the terminal device may also be other information.
  • the QoS attribute may include, for example, one or more of the following: priority, packet delay planning, packet error rate, delay-sensitive indication, average window, and maximum burst of data packets. This application does not limit the content included in the QoS attribute.
  • terminal devices belonging to the same group may have terminal devices with the same QoS attribute.
  • terminal devices belonging to the same group may have the same service type and slice type.
  • the power saving requirements and delay requirements of terminal devices belonging to the same group are the same.
  • a terminal device and / or a network device may perform some or all of the steps in the embodiments of the present application. These steps or operations are merely examples.
  • the present application Embodiments can also perform other operations or variations of various operations.
  • each step may be performed in a different order presented in the embodiments of the present application, and it may not be necessary to perform all operations in the embodiments of the present application.
  • FIG. 2 shows a schematic flowchart 200 of a communication method according to an embodiment of the present application.
  • the method 200 can be applied to the communication system 100 shown in FIG. 1, but the embodiment of the present application is not limited thereto.
  • the first access network device determines a group identifier corresponding to the terminal device # 1A and an identifier of the terminal device.
  • the first access network device may be an access network device to which the terminal device # 1A accesses the network for the first time, but this embodiment is not limited thereto.
  • the first access network device may also be Any one of the access network devices serving terminal device # 1A.
  • the first access network device sends a first message to the terminal device # 1A, where the first message includes the group identifier and the terminal device identifier.
  • Terminal device # 1A stores the group identifier and the terminal device identifier.
  • the group identifier is used to identify a group to which the terminal device belongs, and the terminal device identifier is used to identify the terminal device within the group to which the terminal device belongs.
  • the group identity corresponds to the public context
  • the identity of the terminal device corresponds to the private context of terminal device # 1A.
  • a group identifier is associated with a public context
  • a terminal device identifier is associated with a private context.
  • the public context and the private context constitute the context of the terminal device # 1A or the entire context of the terminal device # 1A, and the public context is shared by all terminal devices in the group, and the private context is the terminal device # 1A Dedicated context.
  • the context of any terminal device belonging to the same group is composed of a public context corresponding to the group identifier identifying the group and a private context of the terminal device.
  • the group identifier and the terminal device identifier corresponding to the terminal device # 1A may be determined, and may be a terminal Device # 1A allocates a public context corresponding to the group identity and a private context corresponding to the identity of the terminal device.
  • the group identifier and the terminal device identifier may be sent to the terminal device # 1A through a first message.
  • the terminal device # 1A can save the group identifier and the terminal device identifier.
  • the first access network device needs to access the network again, it can access the network according to the group identity and the identity of the terminal device.
  • terminal devices are grouped.
  • the terminal device context includes a public context corresponding to the group identifier and a private context corresponding to the identifier of the terminal device. All terminal devices in each group share the same common context. And each terminal device uses its own dedicated context. In this way, when the access network device maintains the context of the terminal device, it does not need to store all the context of each terminal device, which can reduce the resource requirements of the access network device to maintain the context. For example, if the terminal device is the first terminal device in the group to access the first access network device, the first access network device may configure and save the public context corresponding to the group to which the terminal device belongs and the private context corresponding to the terminal device.
  • the first access network device only needs to configure and save the dedicated contexts of other terminal devices. If the first access network device has saved the public context corresponding to the packet corresponding to the terminal device before configuring the context of the terminal device, the first access network device does not need to save the public context corresponding to the terminal device.
  • the group identifier corresponding to the terminal device # 1A is described as: Group ID # 1, and the identifier of the terminal device # 1A is described as: ID #A, and the embodiment of the present application is described in detail.
  • the terminal device # 1A may be any terminal device.
  • the group identifier and the terminal device identifier may have different expressions, which is not limited in the embodiment of the present application.
  • the first access network device may determine a group identifier corresponding to the terminal device # 1A according to a preset rule or an autonomously determined grouping rule.
  • the preset rule may be determined through negotiation by several network devices (for example, the network device may include an access network device and / or a core network device), or determined by the core network device and then sent to the first access network device, or may be operated by the operator. And management entity (OAM) configuration, or stipulated by the agreement, this embodiment of the present application does not limit this.
  • the preset rule may define a correspondence between a group identifier and attribute information of a terminal device.
  • the first access network device determines the group identifier of the terminal device as the group identifier # 1.
  • the first access network device determines the group ID of the terminal device as group ID # 2.
  • the attribute information of the terminal device may include one or more of the following information: the QoS attribute of the terminal device, the service type of the terminal device, the slice type of the terminal device, the capability of the terminal device, whether the terminal device is stationary, The power saving requirements of terminal equipment and the delay requirements of terminal equipment.
  • the attribute information of the terminal equipment listed here is only an exemplary description, and should not constitute any limitation to this application.
  • the attribute information of the terminal equipment may also be other information.
  • the QoS attribute may include, for example, one or more of the following: priority, packet delay planning, packet error rate, delay-sensitive indication, average window, and maximum burst of data packets. This application does not limit the content included in the QoS attribute.
  • the attribute information of the terminal device may be sent by the terminal device # 1A to the first access network device, or may be obtained by the first access network device from the core network device (for example, the first core network device).
  • This application does not limit how the first access network device obtains the attribute information of the terminal device # 1A.
  • a preset rule is used to define the correspondence between the delay requirement of the terminal device and the group identifier as an example.
  • the first access network device is exemplified. How to independently determine the group identifier corresponding to terminal device # 1A according to a preset rule.
  • Group ID Delay requirement (ms) Group ID # 1 ⁇ 2 Group ID # 2 > 2 and ⁇ 4 Group ID # 3 > 4 and ⁇ 5 ... ...
  • the group identifier of the terminal device whose delay requirement satisfies 2ms or less can be determined as the group identification # 1
  • the group identifier of the terminal device whose delay requirement satisfies 2ms and 4ms can be determined as Group ID # 2.
  • the group ID of a terminal device whose delay requirement satisfies more than 4 ms and less than or equal to 5 ms may be determined as group ID # 3.
  • the first access network device obtains a group identifier corresponding to the terminal device # 1A sent by the core network device. For example, when the terminal device # 1A requests access to the network, the first access network device may send the attribute information of the terminal device # 1A to the core network device, and the core network device determines the terminal device # according to the attribute information of the terminal device # 1A. Group ID corresponding to 1A. Then, the core network device sends the determined group identifier to the first access network device, and the first access network device determines the received group identifier as the group identifier corresponding to the terminal device # 1A. Similar to the first method, the core network device may determine the group identifier of the terminal device # 1A according to a preset rule. For details, refer to the description of the first method, and details are not described herein again.
  • the first access network device may determine a public context corresponding to the group identification # 1 and a private context corresponding to the identification #A.
  • the public context corresponding to the group identifier may be predefined or pre-configured.
  • the first access network device may save a public context corresponding to each group identifier in advance.
  • the first access network device may determine the public context of the terminal device # 1A according to the public context corresponding to the saved group identifier # 1.
  • the first access network device may configure and save the public context corresponding to the group identification # 1 when the first terminal device configured as the group identification # 1 accesses the first access network device.
  • the public context corresponding to the group identifier # 1 may be the first terminal device configured as the group identifier # 1 to access the first access network device, and the first access network device corresponds to the group identifier # 1.
  • the attribute information and / or other information of the terminal device is configured.
  • terminal device # 1A is the first terminal device configured as group ID # 1
  • the first access network device needs to configure and save the group Public context corresponding to ID # 1
  • terminal device # 1A is not the first terminal device configured as group ID # 1
  • the first The access network device does not need to repeatedly configure and save the public context corresponding to the group identifier # 1.
  • the way for the first access network device to configure the public context may be that the first access network device configures the public context independently, or it may obtain the public context for the core network device configuration, or the first access network device configuration protocol.
  • the specified public context is not limited in the embodiments of the present application.
  • the group identifier may be used to identify a group in a certain area.
  • the certain area may be pre-configured, for example, pre-configured by an operation and management entity (OAM).
  • OAM operation and management entity
  • the certain area may be specified by an agreement.
  • the certain area may be determined by interaction between the first access network device and other access network devices.
  • each network device for example, an access network device and / or a core network device
  • each network device for example, an access network device and / or a core network device
  • each network device for example, an access network device and / or a core network device
  • the common context of the two terminal devices determined by the two access network devices the same.
  • group identification # 1 identifies a group in a certain area
  • the public context is configured by the core network device in the certain area
  • the terminal devices have different terminal device identifications
  • the common context may include one or more of the following information: QoS attributes, RRC configuration, SDAP configuration, DRB configuration, capabilities of the terminal device, and types of security parameters supported by the terminal device. That is to say, for a specific packet, one or more of the QoS attributes, RRC configuration, SDAP configuration, DRB configuration, capabilities of the terminal device, and the type of security parameters supported by the terminal device are the same for all terminal devices in the group.
  • the dedicated context may include security parameters.
  • the dedicated context of terminal device # 1A may include the security parameters of terminal device # 1A.
  • the security parameters include at least one of an integrity protection algorithm, an encryption algorithm, and a security key parameter.
  • the security key parameter may be at least one of a KgNB key, a next hop (NH) key, and a next hop key (next hopping chaining count, NCC).
  • the security key parameters may also include a security key for the signaling plane and / or user plane for integrity protection and / or encryption.
  • the dedicated context may also be other information, or the dedicated context may include other information in addition to the security parameters, which is not limited in the embodiment of the present application. For example, instead of using the SDAP configuration information as a public context, and using the SDAP configuration information as a private context, or part of the SDAP configuration information can be used as a public context and the other part can be used as a private context.
  • the dedicated contexts corresponding to each terminal device are different.
  • the dedicated contexts corresponding to each terminal device in the group corresponding to the identifier # 1 are different, but this application does not exclude the correspondence of multiple terminal devices in the same group. The possibility of the same private context.
  • the first access network device may further send the public context to the terminal device # 1A.
  • the first access network device may send the public context corresponding to the group identifier # 1 to the terminal device # 1A.
  • the terminal device # 1A may not distinguish which information in the information sent by the first access network device is a group identifier and which information is an identifier of the terminal device.
  • the length of group identification # 1 is 5 bits
  • the length of identification #A is 4 bits.
  • the first access network device sends a 9-bit identification information to terminal device # 1A. Terminal device # 1A does not need to distinguish this. Which bits within 9bit are group identification and which bits are identification of terminal equipment. Further, the terminal device may not distinguish which contexts are public contexts and which are private contexts.
  • the first access network device may not send the public context to the terminal device # 1A.
  • the public context corresponding to the group identifier may be pre-configured for the terminal device, and then the terminal device # 1A may determine the corresponding public context according to the group identifier # 1 sent by the first access network device. It should be noted that, in this case, the terminal device # 1A needs to distinguish which information in the identification information sent to the first access network device is a group identification and which context is a public context.
  • the first access network device may further send the dedicated context to the terminal device # 1A.
  • the first access network device may re-establish the terminal device # 1A. Assign the identity of the terminal device. It should be understood that the first access network device may also reassign the group identifier to the terminal device # 1A, but this is not limited in the embodiment of the present application.
  • the method may further include:
  • the terminal device # 1A sends a second message to the second access network device.
  • the second message may be used to request access to a second access network device.
  • terminal device # 1A when terminal device # 1A is in an inactive state, if terminal device # 1A moves to a second serving cell covered by the second access network device, terminal device # 1A may send a second message to the second access network device. Request access to the second access network device.
  • the second message may be, for example, a random access request message, an RRC connection request message, a recovery request message, and the like, which is not limited in this application.
  • the inactive state may be an RRC deactivated state, an RRC_INACTIVE state, a light RRC connection state (light RRC connection), or an enhanced idle state.
  • the terminal device and the access network device store the context of the terminal device.
  • the terminal device and the core network device store the context of the non-access layer of the terminal device.
  • the access network device and the core network device may also maintain the connection of the terminal device between the access network device and the core network device.
  • the second message may be used by the second access network device to determine the group identity # 1 and the identity #A.
  • the second message may include the identification of the terminal device # 1A, that is, the identification #A.
  • the second message may further include a group identifier # 1.
  • the second message may be carried on a physical resource corresponding to the group identifier # 1, and the second access network device may determine the group identifier corresponding to the terminal device # 1A as the group identifier # 1 according to the physical resource sending the second message.
  • the second access network device broadcasts or is pre-configured with a mapping relationship: ⁇ [group identifier # 1, physical resource # 1]; [group identifier # 2, physical resource # 2], ... ⁇ , then the terminal device # If 1A sends a second request on physical resource # 1, the second access network device can determine that terminal device # 1A corresponds to group identification # 1.
  • the physical resource may specifically be a physical random access channel (PRACH) resource, for example, including a physical random access preamble, and / or, a physical random access time / frequency domain resource, but this application is not limited thereto. herein.
  • PRACH physical random access channel
  • the second access network device responds to the terminal device # 1A according to the existing technology.
  • the second access network device may configure the terminal device # 1A to enter an idle state, an inactive state, or an active state. state.
  • the second access network device may configure the terminal device # 1A to enter an idle state, an inactive state, or an active state. state.
  • the second message may further include short message authentication code integrity or, for example, shortMAC-I or short MACMAC-I, and the short message authentication code integrity is terminal device # 1A Determined according to the physical cell identity PCI of the first serving cell, the cell identity of the second serving cell, and the group identity # 1.
  • short message authentication code integrity is terminal device # 1A Determined according to the physical cell identity PCI of the first serving cell, the cell identity of the second serving cell, and the group identity # 1.
  • the first serving cell is a cell covered by the first access network device
  • the second serving cell is a cell covered by the second access network device.
  • the first serving cell may be a source serving cell
  • the second serving cell may be a target cell or a new serving cell.
  • the second access network device may obtain the context of the terminal device # 1A by using the method 300 shown in FIG. 3 to connect the terminal device # 1A to the second access network device of the network. This will be described in detail below.
  • FIG. 3 shows a schematic flowchart 300 of a communication method according to an embodiment of the present application.
  • the method 300 can be applied to a scenario where the terminal device # 1A is switched from the first access network device to the second access network device, but the embodiment of the present application is not limited to this application scenario.
  • the same concepts, words, or terms appearing in the following as in the foregoing can be referred to the explanations and explanations made above, and will not be repeated hereafter.
  • the first access network device in the method 300 is the first access network device in the method 200.
  • the second access network device receives a second message from the terminal device # 1A.
  • the second message may be used for the terminal device # 1A to request access to the second access network device.
  • the second message may be used for the terminal device # 1A to request access to the second access network device.
  • the second access network device determines the group identifier corresponding to the terminal device # 1A and the identifier of the terminal device # 1A according to the second message, that is, the second access network device determines the group identifier # 1 and the identifier #A.
  • the second message may include group identification # 1 and identification #A.
  • the second message may include the identifier #A, the second message may be carried on the physical resource corresponding to the group identifier # 1, and the second access network device may determine the terminal device # 1A according to the physical resource that sends the second message.
  • the corresponding group ID is group ID # 1.
  • the second access network device may learn that the context of the terminal device needs to be obtained from the first access network device according to the second message.
  • the second message may include identification information used to indicate the first access network device.
  • the second access network device sends a third message to the first access network device.
  • the first access network device receives a third message from the second access network device.
  • the third message may include a group identifier # 1 and an identifier #A, and the third message may be used to request a dedicated context corresponding to the identifier #A.
  • the third message may also be used to request a public context corresponding to the group identifier # 1. Accordingly, the third response message may further include a public context corresponding to the group identifier # 1.
  • the third message may include indication information, and the indication information may be used to indicate whether a public context corresponding to the group identifier # 1 is requested, or the indication information is used to indicate whether to request only the corresponding identifier #A. Or the indication information is used to indicate whether all the contexts of the terminal device # 1A are requested, where all the contexts refer to the public context and the private context corresponding to the terminal device # 1A. In a possible way, the indication information may be used to indicate whether to request a public context corresponding to the group identifier # 1. It can be understood as an implicit or default indication that a dedicated context corresponding to the identifier #A is requested.
  • the dedicated context corresponding to the request identifier #A is not separately indicated.
  • the indication information can be used to indicate the public context corresponding to the request group identifier # 1, it means that the request context and the private context corresponding to the identifier #A are requested. Indicates that the public context corresponding to the group ID # 1 is not requested, and indicates that only the private context corresponding to the ID #A is requested.
  • the first access network device can determine the type of the context requested by the second access network device, that is, only the private context is requested, or the public context and the private context are requested.
  • the indication information may be 1-bit information. For example, when the bit value is TRUE or 1, it is used to indicate that the third request message is used for the private context corresponding to the request identifier #A and the public context corresponding to the group identifier # 1. When the bit value is FALSE or 0 , Used to indicate that the third request message is only used to request the public context corresponding to the group identifier # 1.
  • the second access network device may only request the public context corresponding to the group identity # 1.
  • the second access network device may obtain the group identification # 1 sent by the terminal device # 1A, other terminal devices (for example, the terminal device # 1B) in the group to which the terminal device # 1A belongs need to access the second access network.
  • the second access network device has obtained and saved the public context corresponding to the group identifier # 1 from the first access network device.
  • the second access network device does not need to obtain the public context corresponding to the group identity # 1 from the first access network device again, but only needs to obtain the private context corresponding to the identity #A.
  • the second access network device may determine the public context corresponding to the group ID # 1 from the public contexts that it pre-stores according to the group ID # 1, without acquiring the group ID # 1 from the first access network device. Corresponding public context.
  • the second access network device may request the first access network device for the corresponding group identification # 1.
  • Public context It should be understood that when the second access network device determines that it holds the public context corresponding to the group identifier # 1, it may also request the public context corresponding to the group identifier # 1, which is not limited in this application.
  • the first access network device sends a third response message to the second access network device.
  • the second access network device receives a third response message from the first access network device.
  • the third response message includes a dedicated context corresponding to the identification #A.
  • the first access network device may delete the dedicated context corresponding to the identifier #A. Further, the first access network device may also delete the public context corresponding to the group identifier # 1.
  • the embodiments of the present application group terminal devices, and the context of the terminal devices includes a public context corresponding to the grouping and a private context corresponding to the terminal device.
  • the second access network device may only The private context of the terminal device may be obtained from the first access network device, and the public context corresponding to the packet to which the terminal device belongs may not be obtained from the first access network device.
  • the first access network device can only send the dedicated context of the terminal device to the second access network device, and does not send the terminal device to the public context corresponding to the packet to which the terminal device belongs, thereby saving signaling overhead.
  • the method for acquiring the context of the terminal device in this application can reduce the signaling overhead of forwarding the context of the terminal device between the access network devices.
  • the third message may further include a short message authentication code integrity or, for example, may be shortMAC-I or short MACMAC-I, and the short message authentication code integrity is terminal device # 1A Determined according to the physical cell identity PCI of the first serving cell, the cell identity of the second serving cell, and the group identity # 1.
  • the first serving cell is a cell covered by the first access network device
  • the second serving cell is a cell covered by the second access network device.
  • the first serving cell is a source serving cell
  • the second serving cell is a target cell or a new serving cell.
  • the third response message further includes (1) or (2) in the following, or may include both (1) and (2).
  • the first access network device may return the context requested by the second access network device to the second access network device, and return to the second access network device the terminal except for the terminal belonging to the packet belonging to the terminal device # 1A.
  • any terminal device for example, terminal device # 1C
  • the second access network device does not need to The first access network device sends a request message to request the dedicated context of the terminal device # 1C. Thereby, signaling overhead can be further saved.
  • the attribute information of the terminal device corresponding to the group identifier # 1 may be a demand for power saving. It should be understood that the attributes of each terminal device in the group identifier # 1 include a power saving requirement, or that the first access network device is configured with the group identifier of the terminal device having the power saving requirement as the group identifier # 1.
  • the first access network device may return the context requested by the second access network device to the second access network device, and return the group address corresponding to the group identifier # 1 to the second access network device. Attribute information of the corresponding terminal device.
  • the second access network device can better manage each terminal device in the group corresponding to the group identifier # 1 according to the attribute information of the terminal device corresponding to the group identifier # 1 and the group identifier # 1, which is conducive to improving system performance.
  • FIG. 4 shows a specific example of a method for acquiring a context of a terminal device provided by the present application.
  • the first access network device determines the group identifier # 1 and the identifier #A, and determines that the public context corresponding to the group identifier # 1 corresponds to the identifier #A. Public context.
  • the first access network device may receive the attribute information sent by the terminal device # 1A, or receive the attribute information of the terminal device # 1A sent by the core network device, and determine the group identifier # 1 according to the attribute information of the terminal device # 1A. And logo #A.
  • the first access network device determines the public context corresponding to the group identifier # 1 and the public context corresponding to the identifier #A, reference may be made to the foregoing description, and details are not described herein again.
  • S402. The first access network device sends the first message to the terminal device # 1A.
  • the first message includes group identification # 1 and identification #A.
  • group identification # 1 and identification #A For example, when the first access network device configures the terminal device to enter a non-connected state, such as an idle state, an inactive state, or another non-connected state, the group identifier # 1 and the identifier #A may be sent to the terminal device # 1A.
  • the first access network device sends the public context and the private context to the terminal device # 1A.
  • the messages sent by the first access network device to the terminal device # 1A in the public context and the private context may be the same or different.
  • the terminal device # 1A sends an RRC recovery request message (that is, an example of the second message) to the second access network device, and the RRC recovery request message includes the group identifier # 1 and the identifier #A.
  • the RRC recovery request may further include a short message authentication code integrity or may be, for example, shortMAC-I or shortresumeMAC-I.
  • the second access network device sends an acquisition context request message (that is, an example of the third message) to the first access network device, where the acquisition context request message includes a group identifier # 1 and an identifier #A.
  • the acquisition context request message may include indication information.
  • the indication information may be used to indicate whether a public context is requested; or the indication information may be used to indicate whether to request the entire context of the terminal device # 1A; or the indication information may be used to indicate whether to request only the dedicated context of the terminal device # 1A. For example, if the terminal device # 1B has accessed the second access network device before S405, it means that the second access network device has saved the public context corresponding to the group identifier # 1. At this time, the indication information is used to indicate that only the dedicated context of the terminal device # 1A is requested, that is, the dedicated context corresponding to the identification #A is requested. It should be understood that the description is made by taking the indication information only for requesting the dedicated context of the terminal device # 1A as an example, but this application does not limit whether the indication information is used only for requesting the dedicated context of the terminal device # 1A.
  • the first access network device sends the dedicated context of the terminal device # 1A to the second access network device.
  • the first access network device sends only the dedicated context of the terminal device # 1A to the second access network device according to the instruction information sent by the second access network device. Since the first access network device does not need to send the public context corresponding to the group identifier # 1 again, it can save signaling overhead.
  • the first access network device may also send the public context corresponding to the group identifier # 1 in S406, which is not limited in this embodiment of the present application.
  • the context of the terminal devices includes a public context corresponding to the group and a private context corresponding to the terminal device, where all terminal devices in each group share the same Public context, and each terminal device uses its own private context.
  • the foregoing mainly describes the interaction based on the group identifier between the terminal device and the access network device. It is easy to understand that the access network device and the core network device can also interact based on the group identifier. Detailed description will be made below with reference to the communication method 500 shown in FIG. 5 and the communication method 600 shown in FIG. 6.
  • FIG. 5 is a communication method provided by the present application. This method can be applied to a scenario in which an access network device allocates a group identity to a terminal device.
  • the first access network device determines that the group identifier of the terminal device # 1A is the group identifier # 1.
  • the first access network device may allocate a group identifier # 1 to the terminal device # 1A. For example, the first access network device may allocate the group identifier # 1 to the terminal device # 1A according to the attribute information of the terminal device # 1A.
  • the first access network device may allocate the group identifier # 1 to the terminal device # 1A according to the attribute information of the terminal device # 1A.
  • the first access network device sends a fourth message to the core network device.
  • the fourth message includes a group identifier # 1, and the fourth message is used to request the core network device to configure the NGAP connection configuration parameter corresponding to the group identifier # 1.
  • the NGAP connection configuration parameters include at least one of PDU session resource configuration, QoS flow configuration, and DRB configuration.
  • the core network device determines and saves the NGAP connection configuration parameters corresponding to the group identifier # 1.
  • the core network device sends the NGAP connection configuration parameter corresponding to the group identifier # 1 to the first access network device.
  • the first access network device after receiving the NGAP connection configuration parameter corresponding to the group identifier # 1, the first access network device saves the NGAP connection configuration parameter corresponding to the group identifier # 1.
  • the first access network device determines that the group identifier of the terminal device # 1B is the group identifier # 1.
  • the first access network device may assign a group identifier # 1 to the terminal device # 1B.
  • the first access network device may also allocate an identification of the terminal device # 1B (that is, the identification #B) to the terminal device # 1B. For example, the first access network device may assign a group identifier # 1 to the terminal device # 1B according to the attribute information of the terminal device # 1B. How the first access network device assigns a group identifier to the terminal device # 1B may be determined by referring to the above. The description made by the group identifier of the terminal device # 1A will not be repeated here.
  • the first access network device sends an activation request message to the core network device.
  • the activation request message is used to request the core network device to activate the NGAP connection configuration parameter corresponding to the group identifier # 1 described above for the terminal device # 1B.
  • the activation request message may carry group identification # 1.
  • the activation request message may also carry identification information used by the core network device to identify the terminal device # 1B.
  • the identification information used for the core network equipment to identify the terminal equipment may be International Mobile Subscriber Identity (IMSI), System Architecture Evolution Temporary Mobile Subscriber Identity (S-TMSI), and IMSI or At least one of other identification information related to S-TMSI.
  • the core network device activates the NGAP connection configuration parameter corresponding to the terminal device # 1B for the group identifier # 1 according to the activation request message.
  • the method may further include:
  • S580 The core network device sends a response to the first access network device.
  • the response may be a confirmation message or a failure message or a rejection message.
  • the first access network device may determine that the core network device is a terminal Device # 1B activates the NGAP connection configuration parameters corresponding to group ID # 1.
  • the communication method in the embodiment of the present application can reduce the establishment of NGAP connections by grouping terminal devices and configuring the same NGAP connection configuration parameters for terminal devices belonging to the same group. Since the core network device only needs to save a set of NGAP connection configuration parameters corresponding to each group, and does not need to save the NGAP connection configuration parameters of each terminal device, it can save the storage resources of the core network device.
  • FIG. 6 is a communication method provided by the present application. This method can be applied to a scenario in which a core network device allocates a group identity to a terminal device.
  • the core network device determines that the group identifier of the terminal device # 1A is the group identifier # 1.
  • the terminal device # 1A needs to establish an NGAP connection with the core network device.
  • the group identifier # 1 may be determined for the terminal device # 1A.
  • the core network device may determine the group identifier # 1 for the terminal device # 1A according to the attribute information of the terminal device # 1A.
  • the method for determining the group identity of the core network device for the terminal device # 1A is similar to that described above, except that the execution subject of the group identity is different. The method and principle of determining the group identity are similar, and are not repeated here.
  • the core network device determines and saves the NGAP connection configuration parameters corresponding to the group identifier # 1.
  • the core network device sends the NGAP connection configuration parameter corresponding to the group identifier # 1 and the group identifier # 1 to the first access network device.
  • the first access network device after receiving the NGAP connection configuration parameter corresponding to the group identifier # 1, the first access network device saves the NGAP connection configuration parameter corresponding to the group identifier # 1.
  • the core network device determines that the group identifier of the terminal device # 1B is the group identifier # 1.
  • the core network device may determine the group identifier # 1 for the terminal device # 1B.
  • the method for determining the group identity of the core network device for the terminal device # 1B is similar to that of S220, except that the execution subject of the group identity is different. The method and principle of determining the group identity are similar, and are not repeated here.
  • S650 The core network device sends activation instruction information to the first access network device.
  • the activation instruction information is used to instruct the first access network device to activate the NGAP connection configuration parameter corresponding to the group identifier # 1 described above for the terminal device # 1B.
  • the activation indication information may carry a group identifier # 1, which is used by the first access network device to determine the group identifier that needs to activate the NGAP connection configuration parameter.
  • the first access network device activates the NGAP connection configuration parameter corresponding to the terminal device # 1B for the group identifier # 1 according to the activation instruction information.
  • the method may further include:
  • the first access network device sends a response to the core network device.
  • the response may be a confirmation message or a failure message or a rejection message.
  • the core network device may determine that the first access network device is a terminal Device # 1B activates the NGAP connection configuration parameters corresponding to group ID # 1.
  • the communication method in the embodiment of the present application can reduce the establishment of NGAP connections by grouping terminal devices and configuring the same NGAP connection configuration parameters for terminal devices belonging to the same group, thereby saving signaling overhead. Since the core network device only needs to save a set of NGAP connection configuration parameters corresponding to each group, and does not need to save the NGAP connection configuration parameters of each terminal device, it can save the storage resources of the core network device.
  • FIG. 7 is a schematic structural diagram of a communication device according to an embodiment of the present application.
  • the communication device may be a terminal device or a component (such as a chip or a circuit) that can be used for the terminal device.
  • the communication apparatus may be configured to implement the processes or steps corresponding to those performed by the terminal devices in the foregoing method embodiments.
  • the communication device 700 may include a receiving unit 710 and a storage unit 720.
  • the receiving unit 710 is configured to receive a first message from a first access network device, where the first message includes a group identifier corresponding to the communication device and an identifier of the communication device, and the group identifier Is used to identify a group to which the communication device belongs, and the identifier of the communication device is used to identify the communication device within the group to which the communication device belongs, the group identifier corresponds to a public context, and the public context is determined by the communication device It is shared by all communication devices in the belonging group, and the identity of the communication device corresponds to the dedicated context of the communication device.
  • the storage unit 720 is configured to store the group identifier and the identifier of the communication device.
  • the receiving unit 710 may be implemented by a transmitter, and the storage unit 720 may be implemented by a memory.
  • the storage unit 720 may be implemented by a memory.
  • a communication device may be a terminal device or a component (such as a chip or a circuit) that can be used for the terminal device.
  • the communication device may include a transceiver and a memory, and optionally, may further include a processor.
  • the memory may be used to implement the corresponding functions and operations of the storage unit 720, and the transceiver is used to implement the corresponding functions and operations of the receiving unit 710.
  • the memory may also be used to store execution instructions or application program code, and controlled by the processor to implement the communication method corresponding to the terminal device in the embodiments of the present application; and / or, it may also be used to temporarily store some Data and instruction information.
  • the memory may exist independently of the processor. At this time, the memory may be connected to the processor through a communication line. In another possible design, the memory may also be integrated with the processor, which is not limited in the embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a communication device according to an embodiment of the present application.
  • the communication device may be an access network device or a component (such as a chip or a circuit) that can be used for the access network device.
  • the communication apparatus may be configured to implement a process or step corresponding to the first access network device in the method embodiments shown in FIG. 2 or FIG. 4 or FIG. 5 or FIG. 6.
  • the communication device 800 may include a processing unit 810 and a sending unit 820.
  • the communication device 800 is used to implement the method embodiment shown in FIG. 2 or FIG. 4:
  • a processing unit 810 is configured to determine a group identifier corresponding to a terminal device and an identifier of the terminal device, the group identifier is used to identify a group to which the terminal device belongs, and the identifier of the terminal device is used to group the terminal to which the terminal device belongs
  • the terminal device is internally identified, the group identifier corresponds to a public context, the public context is shared by all terminal devices in a group to which the terminal device belongs, and the terminal device identifier corresponds to a dedicated context of the terminal device;
  • the sending unit 820 is configured to send a first message to the terminal device, where the first message includes the group identifier and the identifier of the terminal device.
  • the processing unit 810 is configured to determine a group identifier corresponding to the terminal device # 1A. Further, the processing unit 810 may also be used to determine a group identifier of the terminal # 1B.
  • the sending unit 820 may be configured to send a fourth message to the core network device. Further, the sending unit 820 may also send an activation request message to the core network device.
  • the activation request message may carry a group identifier for requesting a NGAP connection corresponding to the group identifier. Configuration parameters.
  • the communication device 800 may further include a receiving unit, which may be configured to receive the NGAP configuration parameter corresponding to the group identifier from the core network device.
  • a receiving unit which may be configured to receive the NGAP configuration parameter corresponding to the group identifier from the core network device.
  • the receiving unit is configured to receive the NGAP connection configuration parameter corresponding to the group identifier # 1 and the group identifier # 1 from the core network device.
  • it may also be used to receive activation instruction information from the core network device, where the activation instruction information is used to instruct the first access network device to activate the NGAP connection configuration parameter corresponding to the group identifier # 1 described above for the terminal device # 1B.
  • the processing unit 810 is configured to activate the NGAP connection configuration parameter corresponding to the terminal device # 1B for the group identifier # 1 according to the activation instruction information.
  • the sending unit 820 is configured to send a response to the core network device.
  • the sending unit 820 may be implemented by a transmitter
  • the processing unit 810 may be implemented by a processor
  • the receiving unit may be implemented by a receiver
  • the receiver and the transmitter may be separately set or integrated together (referred to as transceiver).
  • processing unit 810 the sending unit 820, and the receiving unit can be referred to above for the first access network device in the method shown in FIG. 2 or FIG. 4 or FIG. 5 or FIG. The description is not repeated here.
  • a communication device is also provided, and the communication device may be an access network device or a component (such as a chip or a circuit) that can be used for the access network device.
  • the communication device may include a processor and a transceiver, and optionally, may further include a memory.
  • the processor may be used to implement the corresponding functions and operations of the processing unit 810, and the transceiver is used to implement the corresponding functions and operations of the sending unit 820.
  • the memory may be used to store execution instructions or application program code, and controlled by the processor to implement the communication method provided in FIG. 2 or FIG. 4 or FIG. 5 or FIG.
  • the memory may exist independently of the processor. At this time, the memory may be connected to the processor through a communication line. In another possible design, the memory may also be integrated with the processor, which is not limited in the embodiment of the present application.
  • FIG. 9 is a structural block diagram of a communication device according to an embodiment of the present application.
  • the communication device 900 includes a receiving unit 910, a processing unit 920, and a sending unit 930.
  • the communication device 900 may be an access network device or a component (such as a circuit or a chip) that can be used for the access network device.
  • the communication apparatus may be configured to implement a process or step corresponding to any one of the foregoing method embodiments performed by the second access network device.
  • the receiving unit 910 is configured to receive a second message from a terminal device, where the second message is used by the terminal device to request access to the communication device;
  • the processing unit 920 is configured to determine a group identifier corresponding to the terminal device and an identifier of the terminal device according to the second message, where the group identifier is used to identify a group to which the terminal device belongs, and The identifier of the terminal device is used to identify the terminal device within a group to which the terminal device belongs, and the identifier of the terminal device corresponds to a dedicated context of the terminal device;
  • the sending unit 930 is configured to send a third message to the first access network device, where the third message includes the group identifier and the identifier of the terminal device, and the third message is used for requesting A dedicated context corresponding to the identity of the terminal device;
  • the receiving unit 910 is further configured to receive a third response message from the first access network device, where the third response message includes the dedicated context.
  • the receiving unit 910 and the sending unit 930 may be implemented by a transmitter.
  • the processing unit 920 may be implemented by a processor.
  • the receiving unit 910, the processing unit 920, and the sending unit 930 reference may be made to the description of the second access network device in the method shown in FIG. 3, and details are not described herein again.
  • a communication device may be an access network device or a component (such as a chip or a circuit) that can be used for the access network device.
  • the communication device may include a transceiver and a processor, and optionally, may further include a memory.
  • the transceiver may be used to implement the corresponding functions and operations corresponding to the receiving unit 910 and the sending unit 930, and the processor may be used to implement the corresponding functions and operations of the processing unit 920.
  • the memory may be used to store execution instructions or application program code, and controlled by the processor to implement the method provided in FIG. 3 or FIG. 4; and / or, it may also be used to store some data, instruction information, or received by the transceiver. Information, etc.
  • the memory may exist independently of the processor. At this time, the memory may be connected to the processor through a communication line. In another possible design, the memory may also be integrated with the processor, which is not limited in the embodiment of the present application.
  • FIG. 10 is a structural block diagram of a communication device according to an embodiment of the present application.
  • the communication device 1000 includes a receiving unit 1010 and a transmitting unit 1020.
  • the communication device 1000 may be an access network device or a component (such as a circuit or a chip) that can be used for the access network device.
  • the communication apparatus may be configured to implement a process or step corresponding to that performed by the first access network device in the method embodiment shown in FIG. 3.
  • a receiving unit 1010 is configured to receive a third message from a second access network device, where the third message includes a group identifier corresponding to the terminal device and an identifier of the terminal device, and the group identifier is used to identify the terminal device belongs to A group, the identifier of the terminal device is used to identify the terminal device within a group to which the terminal device belongs, and the identifier of the terminal device corresponds to a dedicated context of the terminal device;
  • the sending unit 1020 is configured to send a third response message, where the third response message includes the dedicated context.
  • the receiving unit 1010 and the sending unit 1020 may be implemented by a transceiver.
  • the receiving unit 1010 and the sending unit 1020 refer to the first access in the method shown in FIG. 3 above. The description made by the network equipment will not be repeated here.
  • the communication device shown in FIG. 10 may further implement the method in any of the embodiments shown in FIG. 2 or FIG. 4-6.
  • a communication device may be an access network device or a component (such as a chip or a circuit) that can be used for the access network device.
  • the communication device may include a transceiver, and optionally, may further include a processor and a memory.
  • the transceiver may be used to implement the corresponding functions and operations of the receiving unit 1010 and the sending unit 1020 described above.
  • the memory may be used to store execution instructions or application program code, and controlled by the processor to implement the method provided in FIG. 3; and / or, it may also be used to store some data, instruction information, or information received by the transceiver, etc. .
  • the memory may exist independently of the processor.
  • the memory may be connected to the processor through a communication line.
  • the memory may also be integrated with the processor, which is not limited in the embodiment of the present application.
  • the communication device may further implement the method in any of the embodiments shown in FIG. 2 or FIG. 4-6.
  • FIG. 11 is a structural block diagram of a terminal device according to an embodiment of the present invention.
  • the terminal device 1100 includes a processor 1101, a memory 1102, a radio frequency circuit, an antenna, and an input / output device.
  • the processor 1101 may be configured to process a communication protocol and communication data, control a terminal, execute a software program, and process data of the software program.
  • the memory 1102 is mainly used to store software programs and data.
  • the radio frequency circuit is mainly used for the conversion of baseband signals and radio frequency signals and the processing of radio frequency signals.
  • the antenna is mainly used to transmit and receive radio frequency signals in the form of electromagnetic waves.
  • Input / output devices such as a touch screen, a display screen, and a keyboard, are mainly used to receive data input by the user and output data to the user. It should be noted that some types of terminals may not have input / output devices.
  • the processor 1101 When data needs to be sent, the processor 1101 performs baseband processing on the data to be sent, and then outputs the baseband signal to a radio frequency circuit. After the radio frequency circuit processes the baseband signal, the radio frequency signal is sent out in the form of electromagnetic waves through an antenna.
  • the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor.
  • the processor converts the baseband signal into data and processes the data.
  • FIG. 11 only one memory and processor are shown in FIG. 11. In an actual end product, there may be one or more processors and one or more memories.
  • the memory may also be referred to as a storage medium or a storage device.
  • the memory may be set independently of the processor or integrated with the processor, which is not limited in the embodiment of the present application.
  • the antenna and the radio frequency circuit having the transmitting and receiving function may be regarded as the transceiver 1103 of the terminal, and the processor having the processing function may be regarded as the processing unit of the terminal device.
  • the transceiver may also be referred to as a transceiver unit, a transceiver, a transceiver device, and the like.
  • the processing unit may also be called a processor, a processing single board, a processing module, a processing device, and the like.
  • the device for implementing the receiving function in the transceiver 1103 can be regarded as a receiving unit, and the device for implementing the transmitting function in the transceiver 1103 can be regarded as a transmitting unit, that is, the transceiver 1103 includes a receiving unit and a transmitting unit.
  • the receiving unit may also be called a receiver, a receiver, or a receiving circuit.
  • the transmitting unit may also be called a transmitter, a transmitter, or a transmitting circuit.
  • the processor 1101, the memory 1102, and the transceiver 1103 communicate with each other through an internal connection path, and transfer control and / or data signals.
  • the method disclosed in the foregoing embodiment of the present invention may be applied to the processor 1101, or implemented by the processor 1101.
  • the processor 1101 may be an integrated circuit chip with signal processing capabilities.
  • each step of the above method may be completed by an integrated logic circuit of hardware in the processor 1101 or an instruction in the form of software.
  • the processor described in the embodiments of the present application may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), and a ready-made programmable gate array (field programmable gate array). , FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • 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 combination with the embodiments of the present invention may be directly implemented by a hardware decoding processor, or may be performed by using a combination of hardware and software modules in the decoding processor.
  • Software modules can be located in random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory or electrically erasable programmable memory, registers, etc.
  • Storage media The storage medium is located in a memory, and the processor reads the instructions in the memory and completes the steps of the foregoing method in combination with its hardware.
  • the memory 1102 may store instructions for executing the method performed by the terminal device in the method shown in FIG. 2 or FIG. 3.
  • the processor 1101 may execute the instructions stored in the memory 1102 in combination with other hardware (for example, the transceiver 1103) to complete the steps performed by the terminal device in the method shown in FIG. 2 or FIG. Description in the illustrated embodiment.
  • the memory 1102 may store instructions for executing the method performed by the terminal device in the method shown in FIG. 2 or FIG. 3.
  • the processor 1101 may execute instructions stored in the memory 1102 in combination with other hardware (such as the transceiver 1103) to complete the steps performed by the terminal device in the method shown in FIG. 2 or FIG. Description in the illustrated embodiment.
  • An embodiment of the present application further provides a chip, and the chip includes a transceiver unit and a processing unit.
  • the transceiver unit may be an input / output circuit or a communication interface;
  • the processing unit is a processor or a microprocessor or an integrated circuit integrated on the chip.
  • the chip can execute the method on the terminal device side in the foregoing method embodiment.
  • the embodiment of the present application further provides a computer-readable storage medium, which stores instructions thereon, and when the instructions are executed, the method on the terminal device side in the foregoing method embodiment is executed.
  • the embodiment of the present application further provides a computer program product containing instructions, and when the instructions are executed, the method on the terminal device side in the foregoing method embodiment is executed.
  • FIG. 12 is a structural block diagram of an access network device according to an embodiment of the present invention.
  • the access network device 1200 shown in FIG. 12 includes a processor 1201, a memory 1202, and a transceiver 1203.
  • the processor 1201, the memory 1202, and the transceiver 1203 communicate with each other through an internal connection path, and transfer control and / or data signals.
  • the method disclosed in the foregoing embodiment of the present invention may be applied to the processor 1201, or implemented by the processor 1201.
  • the processor 1201 may be an integrated circuit chip and has a signal processing capability. In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the processor 1201 or an instruction in the form of software.
  • the above processor 1201 may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA), or other Programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA off-the-shelf programmable gate array
  • Various methods, steps, and logical block diagrams disclosed in the embodiments of the present invention may be implemented or executed.
  • 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 combination with the embodiments of the present invention may be directly implemented by a hardware decoding processor, or may be performed by using a combination of hardware and software modules in the decoding processor.
  • Software modules can be located in random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory or electrically erasable programmable memory, registers, etc.
  • Storage media The storage medium is located in the memory 1202, and the processor 1201 reads the instructions in the memory 1202 and completes the steps of the foregoing method in combination with its hardware.
  • the memory 1202 may store a function for executing the first access network device in the method shown in FIG. 2 to FIG. 6 or the second access network device in the method shown in FIG. 3-6. Instructions for the method.
  • the processor 1201 may execute instructions stored in the memory 1202 in combination with other hardware (such as the transceiver 1203) to complete the first access network device in the method shown in FIG. 2-3 or the second access network in the method shown in FIG. 3-6.
  • other hardware such as the transceiver 1203
  • An embodiment of the present application further provides a chip, and the chip includes a transceiver unit and a processing unit.
  • the transceiver unit may be an input / output circuit or a communication interface;
  • the processing unit is a processor or a microprocessor or an integrated circuit integrated on the chip.
  • the chip can execute the method performed on the access network device side in the foregoing embodiment.
  • a computer-readable storage medium which stores instructions thereon, and when the instructions are executed, the method on the access network device side in the foregoing method embodiment is executed.
  • a computer program product containing instructions is provided.
  • the instructions are executed, the method on the access network device side in the foregoing method embodiment is executed.
  • FIG. 13 is a structural block diagram of a communication device according to an embodiment of the present application.
  • the communication device 1300 includes a processing unit 1310 and a transmitting unit 1320.
  • the communication device 1300 may be a core network device or a component (such as a circuit or a chip) that can be used for the core network device.
  • the communication apparatus may be configured to implement a process or step corresponding to a core network device in the foregoing method embodiment.
  • a processing unit 1310 configured to determine a group identifier of the terminal device and an NGAP connection configuration parameter corresponding to the group identifier;
  • the sending unit 1320 is configured to send the NGAP connection configuration parameter to the first access network device.
  • the processing unit 1310 may be implemented by a processor, and the sending unit 1320 may be implemented by a transceiver.
  • the processing unit 1310 and the sending unit 1320 may be implemented by a transceiver.
  • a communication device may be a core network device or a component (such as a chip or a circuit) that can be used for the core network device.
  • the communication device may include a transceiver, and optionally, may further include a processor and a memory.
  • the transceiver may be used to implement the corresponding functions and operations of the sending unit 1320.
  • the memory may be used to store execution instructions or application program code, and controlled by the processor to implement the method provided in FIG. 5 or FIG. 6; and / or, may also be used to store some data, instruction information, or received by the transceiver Information, etc.
  • the memory may exist independently of the processor. At this time, the memory may be connected to the processor through a communication line. In another possible design, the memory may also be integrated with the processor, which is not limited in the embodiment of the present application.
  • FIG. 14 is a structural block diagram of a core network device according to an embodiment of the present invention.
  • the core network device 1400 shown in FIG. 14 includes a processor 1401, a memory 1402, and a transceiver 1403.
  • the processor 1401, the memory 1402, and the transceiver 1403 communicate with each other through an internal connection path, and transfer control and / or data signals.
  • the method disclosed in the foregoing embodiment of the present invention may be applied to the processor 1401, or implemented by the processor 1401.
  • the processor 1401 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the processor 1401 or an instruction in the form of software.
  • the above processor 1401 may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA), or other Programmable logic devices, discrete hardware components.
  • 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 or the like.
  • the steps of the method disclosed in combination with the embodiments of the present invention may be directly implemented by a hardware decoding processor, or may be performed by using a combination of hardware and software modules in the decoding processor.
  • Software modules can be located in random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory or electrically erasable programmable memory, registers, etc.
  • Storage media The storage medium is located in the memory 1402, and the processor 1401 reads the instructions in the memory 1402 and completes the steps of the foregoing method in combination with its hardware.
  • the memory 1402 may store instructions for executing a method performed by a core network device in the method shown in FIG. 5 or FIG. 6.
  • the processor 1401 may execute instructions stored in the memory 1402 in combination with other hardware (for example, the transceiver 1403) to complete the method implemented by the core network device in the method shown in FIG. 5 or FIG. Description in the embodiment shown in FIG. 6.
  • An embodiment of the present application further provides a chip, and the chip includes a transceiver unit and a processing unit.
  • the transceiver unit may be an input / output circuit or a communication interface;
  • the processing unit is a processor or a microprocessor or an integrated circuit integrated on the chip.
  • the chip can execute the method performed on the core network device side in the foregoing embodiment.
  • a computer-readable storage medium which stores instructions thereon, and when the instructions are executed, the method on the core network device side in the foregoing method embodiment is executed.
  • a computer program product containing instructions is provided, and when the instructions are executed, the method on the core network device side in the foregoing method embodiment is executed.
  • the disclosed systems, devices, and methods may be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the unit is only a logical function division.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, which may be electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objective of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each of the units may exist separately physically, or two or more units may be integrated into one unit.
  • the units in the embodiments of the present application may also be referred to as modules.
  • 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 devices.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be from a website site, computer, server, or data center Transmission by wire (for example, coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (for example, infrared, wireless, microwave, etc.) to another website site, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, a data center, and the like that includes one or more available medium integration.
  • the available medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (Solid State Disk (SSD)), and the like.
  • a magnetic medium for example, a floppy disk, a hard disk, a magnetic tape
  • an optical medium for example, a DVD
  • a semiconductor medium for example, a solid state disk (Solid State Disk (SSD)

Landscapes

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

Abstract

本申请提供了一种通信方法和装置，能够降低接入网设备存储终端设备的上下文所需的存储资源。该方法包括：接入网设备对具有相同属性的终端设备进行分组，终端设备的上下文分为公共上下文和专用上下文两部分，公共上下文由一个分组的各终端设备共享，专用上下文为各终端设备特有的上下文，接入网设备通过为每个分组存储一份公共上下文以及存储该分组内各终端设备的专用上下文，达到维护各终端设备的上下文的目的。

Description

通信方法和装置
本申请要求于2018年09月18日提交中国专利局、申请号为201811090248.6、申请名称为“通信方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，并且更具体地，涉及一种通信方法和装置。
背景技术
当前接入技术中，对于接入接入网设备的各终端设备，接入网设备需要为每个终端设备分别保存一套上下文。随着社会发展，越来越多的终端设备接入网络，比如低功耗大覆盖(low power wide area，LPWA)用户设备(user equipment，UE)，各种智能终端等需要接入网络。未来第五代(5th generation，5G)网络更是需要支持百万连接的需求。在大量的终端设备接入同一接入网设备的情况下，按照上述接入网设备为每个终端设备分别保存一套上下文的方式，将大量消耗接入网设备的存储资源。
发明内容
本申请提供了一种通信方法和装置，能够降低接入网设备维护终端设备上下文所需的存储资源或者信令开销。
第一方面，本申请提供了一种通信方法。该方法包括：从第一接入网设备接收第一消息，其中，所述第一消息包括所述终端设备对应的组标识和所述终端设备的标识，所述组标识用于标识所述终端设备所属分组，所述终端设备的标识用于在所述终端设备所属分组内识别所述终端设备，所述组标识和公共上下文对应，所述公共上下文由所述终端设备所属分组内的所有终端设备共享，所述终端设备的标识与所述终端设备的专用上下文对应；保存所述组标识和所述终端设备的标识。
本申请实施例的通信方法，通过对终端设备进行分组，使得终端设备的上下文包括对应于组标识的公共上下文和对应于终端设备的标识的专用上下文，其中每个分组内的所有终端设备共享同一个公共上下文，并且每个终端设备使用各自的专用上下文，这样，接入网设备在维护终端设备的上下文时，不需要存储每个终端设备的所有上下文，从而能够降低接入网设备维护上下文的资源需求。例如，若终端设备为该分组内第一个接入第一接入网设备的终端设备，第一接入网设备可以配置并保存终端设备所属分组对应的公共上下文以及终端设备对应的专用上下文。若后续需要为属于该分组的其他终端设备配置上下文，第一接入网设备只需配置和保存其他终端设备的专用上下文。若第一接入网设备在配置终端设备的上下文之前，已经保存了终端设备对应的分组所对应的该公共上下文，那么第一接入网设备无需保存该终端设备对应的公共上下文。
可选地，公共上下文可以包括下述信息中的一种或多种：服务质量(quality of service，QoS)属性、无线资源控制(radio resource control，RRC)配置、业务数据适应协议(Service Data Adaptation Protocol,SDAP)配置、数据无线承载(data radio bearer，DRB)配置、终端设备的能力、以及终端设备支持的安全参数类型。也就是说，对于特定分组，该分组内所有终端设备的QoS属性、RRC配置、SDAP配置、DRB配置、终端设备的能力、以及终端设备支持的安全参数类型中的一种或者多种相同。
进一步地，QoS属性可以包括下述中的一种或多种：优先级、包时延规划、错包率、时延敏感指示、平均窗口、以及数据包最大突发量。
可选地，专用上下文可以包括安全参数。比如，终端设备的专用上下文可以包括终端设备的安全参数。安全参数包括完整性保护算法、加密算法、安全密钥参数的至少一种。安全密钥参数可以为KgNB密钥、下一跳(next hop，NH)密钥、下一跳密钥(next hop chaining count，NCC)的至少一种。安全密钥参数还可以包括用于完整性保护和/或加密保护的信令面和/或用户面密钥。应理解，专用上下文也可以是其他的信息，或者专用上下文除包括安全参数外，还可以包括其他的信息，本申请实施例对此不作限定。比如，不将SDAP配置信息作为公共上下文，而将SDAP配置信息作为专用上下文，或者，SDAP配置信息中的一部分可以作为公共上下文，另一部分可以作为专用上下文。
结合第一方面，在第一方面的某些实现方式中，该方法还可以包括：从所述第一接入网设备接收所述公共上下文。
结合第一方面，在第一方面的某些实现方式中，该方法还可以包括：从所述第一接入网设备接收所述专用上下文。
结合第一方面，在第一方面的某些实现方式中，该方法还可以包括：向第二接入网设备发送第二消息，所述第二消息用于请求接入所述第二接入网设备，所述第二消息包括所述终端设备的标识和所述组标识，或者，所述第二消息承载于与所述组标识对应的物理资源上且所述第二消息包括所述终端设备的标识。
通过向第二接入网设备发送第二消息，使得第二接入网设备可以确定终端设备的标识和所述组标识。从而在终端设备需要接入第二接入网设备时，第二接入网设备可以根据终端设备的标识和所述组标识，从第一接入网设备获取公共上下文和专用上下文。
第二方面，提供了一种通信方法。该方法包括：确定终端设备对应的组标识和所述终端设备的标识，所述组标识用于标识所述终端设备所属分组，所述终端设备的标识用于在所述终端设备所属分组内识别所述终端设备，所述组标识和公共上下文对应，所述公共上下文由所述终端设备所属分组内的所有终端设备共享，所述终端设备的标识与所述终端设备的专用上下文对应；向所述终端设备发送第一消息，所述第一消息包括所述组标识和所述终端设备的标识。
本申请实施例的通信方法，通过对终端设备进行分组，使得终端设备的上下文包括对应于组标识的公共上下文和对应于终端设备的标识的专用上下文，其中每个分组内的所有终端设备共享同一个公共上下文，并且每个终端设备使用各自的专用上下文，这样，接入网设备在维护终端设备的上下文时，不需要存储每个终端设备的所有上下文，从而能够降低接入网设备维护上下文的资源需求。
可选地，可以根据终端设备的属性信息以及预设规则确定终端设备对应的组标识。该 终端设备的属性信息可以是服务质量(quality of service，QoS)属性、终端设备的业务类型、终端设备的切片类型、终端设备的能力、终端设备是否静止、终端设备的节电需求、以及终端设备的时延需求中的一种或多种。该预设规则可以定义组标识与终端设备的属性信息之间的对应关系。从而，根据终端设备的属性信息，可以确定终端设备所对应的组标识。
结合第二方面，在第二方面的某些实现方式中，所述方法还包括：向所述终端设备发送所述公共上下文。
结合第二方面，在第二方面的某些实现方式中，所述方法还包括：向所述终端设备发送所述专用上下文。
结合第二方面，在第二方面的某些实现方式中，所述方法还包括：向核心网设备发送第四消息，所述第四消息包括所述组标识，所述第四消息用于请求所述核心网设备配置所述组标识对应的下一代应用协议栈/NG接口应用层协议(next generation application protocol，NGAP)连接配置参数；接收所述核心网设备发送的所述NGAP连接配置参数。
结合第二方面，在第二方面的某些实现方式中，所述方法还包括：向核心网设备发送激活请求消息，所述激活请求消息包括所述组标识，所述激活请求消息用于所述请求所述核心网设备为另一终端设备(例如，下文中的终端设备#1B)激活所述NGAP连接配置参数；接收所述核心网设发送的响应。其中，所述响应为肯定应答(acknowledgment，ACK)或者否定应答(negative acknowledgment，NACK)。
可选地，该激活请求消息中还可以携带用于核心网设备识别所述另一终端设备的标识信息。用于核心网设备识别终端设备的标识信息可以是国际移动用户标识(International Mobile Subscriber Identity，IMSI)、系统架构演进临时移动用户标识(System Architecture Evolution Temporary Mobile Subscriber Identity，S-TMSI)，和IMSI或S-TMSI相关的其它标识信息。
结合第二方面，在第二方面的某些实现方式中，所述确定终端设备对应的组标识，包括：从核心网设备接收所述组标识。
结合第二方面，在第二方面的某些实现方式中，所述方法还包括：接收所述核心网设备发送的所述组标识对应的NGAP连接配置参数。
结合第二方面，在第二方面的某些实现方式中，所述方法还包括：接收所述核心网设备发送的激活指示信息，所述激活指示信息用于指示为组标识为所述组标识的另一终端设备激活所述NGAP连接配置参数；根据所述激活指示信息，为所述另一终端设备激活所述NGAP连接配置参数。
结合第二方面，在第二方面的某些实现方式中，所述方法还包括：向所述核心网设备发送响应。其中，所述响应为ACK或者NACK。
第三方面，提供了一种通信方法，包括：第二接入网设备从终端设备接收第二消息，所述第二消息用于所述终端设备请求接入所述第二接入网设备；第二接入网设备根据所述第二消息，确定所述终端设备对应的组标识和所述终端设备的标识，所述组标识用于标识所述终端设备所属分组，所述终端设备的标识用于在所述终端设备所属分组内识别所述终端设备，所述终端设备的标识与所述终端设备的专用上下文对应；所述第二接入网设备向所述第一接入网设备发送第三消息，所述第三消息包括所述组标识和所述终端设备的标 识；所述第二接入网设备从所述第一接入网设备接收第三响应消息，所述第三响应消息包括所述专用上下文。
本申请实施例的通信方法，通过对终端设备进行分组，使得终端设备的上下文可以包括对应于分组的公共上下文和对应于该终端设备的专用上下文。在第二接入网设备需要从第一接入网设备获取第一终端的上下文，但其已经保存或者可以确定该终端设备所属分组对应的公共上下文的情况下，第二接入网设备可以只从第一接入网设备获取终端设备的专用上下文即可，而不从第一接入网设备获取终端设备所属分组对应的公共上下文。相应地，第一接入网设备可以只向第二接入网设备发送终端设备的专用上下文，而不向终端设备发送终端设备所属分组对应的公共上下文，从而能够节省信令开销。因此，本申请的获取终端设备上下文的方法，能够降低接入网设备间转发终端设备的上下文的信令开销。
结合第三方面，在第三方面的某些实现方式中，所述第三响应消息还包括与所述组标识对应的公共上下文。
比如，在第二接入网设备未保存与所述组标识对应的公共上下文的情况下，可以从第一接入网设备处获取该公共上下文。
结合第三方面，在第三方面的某些实现方式中，所述第二消息包括所述终端设备的标识和所述组标识；或者，所述第二消息包括所述终端设备的标识，并且所述第二消息承载于与所述组标识对应的物理资源上。
因此，根据第二消息，第一接入网设备可以确定所述终端设备的标识和所述组标识。
结合第三方面，在第三方面的某些实现方式中，所述第二请求消息还包括短的消息认证码完整性或者，例如可以是短的消息认证码完整性(short message authentication code integrity，shortMAC-I)或者短的恢复消息认证码完整性(short resume message authentication code integrity，short resumeMAC-I)，所述用于短的消息认证码完整性是所述终端设备根据第一服务小区的物理小区标识、第二服务小区的小区标识和所述组标识确定的。
应理解，第一服务小区由第一接入网设备提供服务，第二服务小区由第二接入网设备提供服务。还应理解，在本申请实施例中，第一接入网设备为源基站，第二接入网设备为目标基站，或者说第一服务小区为源服务小区，第二服务小区为目标服务小区。
一种可能的方式中，短的消息认证码完整性至少根据第一服务小区的物理小区标识(physical cell identifier,PCI)、第二服务小区的小区标识和终端设备在第一服务小区的终端标识(比如小区无线网络临时标识(cell radio network temporary identifier，C-RNTI))确定。一般来说，不同的终端设备在第一服务小区的终端标识不同，因此在接入网设备中用于验证终端设备的短的消息认证码完整性也不同。本实施例中用组标识#1代替终端标识，使得具有相同组标识的终端标识的短的消息认证码完整性相同，即短的消息认证码完整性可以从终端设备的专用上下文变为公共上下文，从而可以进一步的节省终端设备的专用上下文的存储开销。
结合第三方面，在第三方面的某些实现方式中，所述第三响应消息还包括下述中的至少一种：所述组标识对应的分组内的其他终端设备的专用上下文；所述组标识对应的终端设备的属性信息；其中，所述终端设备的属性信息包括下述信息中的至少一种：终端设备的业务的服务质量属性、终端设备的业务类型、终端设备的切片类型、终端设备的能力、终端设备是否静止、终端设备节电需求和终端设备的时延需求。
举例来说，第一接入网设备可以在向第二接入网设备返回第二接入网设备所请求的上下文的同时，向第二接入网设备返回终端设备所属分组内除该终端设备外的至少一个其他终端设备的标识和对应的专用上下文。这样，若该终端设备所属分组内除该终端设备外的其他任一终端设备(例如，终端设备#1C)需要接入第二接入网设备时，第二接入网设备不需要向第一接入网设备发送请求消息，以请求终端设备#1C的专用上下文。从而，能够进一步节省信令开销。
或者，第一接入网设备可以在向第二接入网设备返回第二接入网设备所请求的上下文的同时，向第二接入网设备返回组标识对应的分组所对应的终端设备的属性信息。第二接入网设备根据组标识和组标识对应的终端设备的属性信息，可以更好的管理组标识对应分组内的各终端设备，从而有利于提高系统性能。
结合第三方面，在第三方面的某些实现方式中，所述公共上下文包括下述信息中的至少一种：服务质量QoS属性、无线资源控制RRC配置、业务数据自适应协议SDAP配置、数据无线承载DRB配置、终端设备的能力和终端设备支持的安全参数类型。
结合第三方面，在第三方面的某些实现方式中，上述第三消息包括指示信息，其中，所述指示信息用于指示是否请求与所述组标识对应的公共上下文，或者所述指示信息用于指示是否仅请求与所述终端设备的标识对应的专用上下文，或者所述指示信息用于指示是否请求所述终端设备的全部上下文。
第四方面，提供了一种通信方法，其特征在于，包括：第一接入网设备从第二接入网设备接收第三消息，所述第三消息包括终端设备对应的组标识和所述终端设备的标识，所述组标识用于标识所述终端设备所属分组，所述终端设备的标识用于在所述终端设备所属分组内识别所述终端设备，所述终端设备的标识与所述终端设备的专用上下文对应；所述第一接入网设备发送第三响应消息，所述第三响应消息包括所述专用上下文。
本申请实施例的通信方法，通过对终端设备进行分组，使得终端设备的上下文可以包括对应于分组的公共上下文和对应于该终端设备的专用上下文。在第二接入网设备需要从第一接入网设备获取第一终端的上下文，但其已经保存或者可以确定该终端设备所属分组对应的公共上下文的情况下，第二接入网设备可以只从第一接入网设备获取终端设备的专用上下文即可，而不从第一接入网设备获取终端设备所属分组对应的公共上下文。相应地，第一接入网设备可以只向第二接入网设备发送终端设备的专用上下文，而不向终端设备发送终端设备所属分组对应的公共上下文，从而能够节省信令开销。因此，本申请的获取终端设备上下文的方法，能够降低接入网设备间转发终端设备的上下文的信令开销。
结合第四方面，在第四方面的某些实现方式中，所述第三响应消息还包括与所述组标识对应的公共上下文。
结合第四方面，在第四方面的某些实现方式中，所述第三响应消息还包括下述中的至少一种：所述组标识对应的分组内的其他终端设备的专用上下文；所述组标识对应的终端设备的属性信息；其中，所述终端设备的属性信息包括下述信息中的至少一种：终端设备的业务的服务质量属性、终端设备的业务类型、终端设备的切片类型、终端设备的能力、终端设备是否静止、终端设备节电需求和终端设备的时延需求。
结合第四方面，在第四方面的某些实现方式中，所述公共上下文包括下述信息中的至少一种：服务质量QoS属性、无线资源控制RRC配置、业务数据自适应协议SDAP配置、 数据无线承载DRB配置、终端设备的能力和终端设备支持的安全参数类型。
结合第四方面，在第四方面的某些实现方式中，上述第三消息包括指示信息，其中，所述指示信息用于指示是否请求与所述组标识对应的公共上下文，或者所述指示信息用于指示是否仅请求与所述终端设备的标识对应的专用上下文，或者所述指示信息用于指示是否请求所述终端设备的全部上下文。
第五方面，提供了一种通信方法，包括：确定终端设备的组标识，以及与所述组标识对应的NGAP连接配置参数；向所述第一接入网设备发送所述NGAP连接配置参数。
关于组标识具体可以参见上文中对组标识的描述，这里不再赘述。
结合第五方面，在第五方面的某些实现方式中，所述确定终端设备的组标识，包括：从第一接入网设备接收第四消息，所述第四消息包括终端设备的组标识，所述第四消息用于请求所述核心网设备配置所述组标识对应的NGAP连接配置参数。
结合第五方面，在第五方面的某些实现方式中，所述方法还包括：从所述第一接入网设备接收激活请求消息，所述激活请求消息包括所述组标识，所述激活请求消息用于所述请求所述核心网设备为另一终端设备(例如，下文中的终端设备#1B)激活所述NGAP连接配置参数；接收所述核心网设发送的响应。其中，所述响应为ACK或者NACK。
可选地，该激活请求消息中还可以携带用于核心网设备识别所述另一终端设备的标识信息。用于核心网设备识别终端设备的标识信息可以是国际移动用户标识(International Mobile Subscriber Identity，IMSI)、系统架构演进临时移动用户标识(System Architecture Evolution Temporary Mobile Subscriber Identity，S-TMSI)，和IMSI或S-TMSI相关的其它标识信息。
结合第五方面，在第五方面的某些实现方式中，所述方法还包括：向第一接入网设备发送激活指示信息，所述激活指示信息用于指示所述第一接入网设备为组标识为所述组标识的另一终端设备激活所述NGAP连接配置参数。
结合第五方面，在第五方面的某些实现方式中，所述方法还包括：从所述第一接入网设备接收响应。其中，所述响应为确认消息或者失败消息或者拒绝消息。
第六方面，提供了一种通信装置，该装置包括用于执行第一方面或第一方面的任一种可能的实现方式的单元或者模块。
可选地，第六方面的通信装置可以为终端设备，或者可以为可用于终端设备的部件(例如芯片或者电路等)。
第七方面，本申请实施例提供一种通信装置，该装置包括用于执行第二方面或第二方面的任一种可能的实现方式的单元或者模块。
可选地，第七方面的通信装置可以为接入网设备，或者可以为可用于接入网设备的部件(例如芯片或者电路等)。
第八方面，本申请实施例提供一种通信装置，该装置包括用于执行第三方面或第三方面的任一种可能的实现方式的单元或者模块。
可选地，第八方面的通信装置可以为上述方法实施例中的第二接入网设备、或者可以为用于第二接入网设备的部件(例如芯片或者电路等)。
第九方面，本申请实施例提供一种通信装置，该装置包括用于执行第四方面或第四方面的任一种可能的实现方式的单元或者模块。
可以选的，第九方面的通信装置可以为上述第四方面提供的第一接入网设备、或者可以为用于第一接入网设备的部件(例如芯片或者电路等)。
第十方面，本申请实施例提供一种通信装置，该装置包括用于执行第五方面或第五方面的任一种可能的实现方式的单元或者模块。
可选地，第十方面的通信装置可以为上述方法实施例中的核心网设备、或者可以为用于核心网设备的部件(例如芯片或者电路等)。
第十一方面，提供了一种通信设备，包括，处理器和存储器，该存储器用于存储计算机程序，该处理器用于从存储器中调用并运行该计算机程序，使得所述装置执行第一方面至第五方面或第一方面至第五方面中任一种可能实现方式中的方法。
可选地，所述处理器为一个或多个，所述存储器为一个或多个。
可选地，所述存储器可以与所述处理器集成在一起，或者所述存储器与处理器分离设置。
可选地，所述通信设备还包括，收发器或收发电路，用于完成对信息的收发功能。
第十二方面，本申请提供了一种计算机可读存储介质，该计算机可读存储介质中存储有计算机程序，当该计算机程序被执行时，实现上述第一方面至第五方面或上述第一方面至第五方面中任意一种可能的实现方式中的方法。
第十三方面，本申请提供了一种包含计算机程序的计算机程序产品。当该计算机程序被运行时，实现上述第一方面至第五方面或上述第一方面至第五方面中任意一种可能的实现方式中的方法。
第十四方面，本申请提供了一种芯片系统，该芯片系统包括输入输出接口和至少一个处理器，该至少一个处理器用于调用存储器中的指令，以进行上述第一方面至第五方面或上述第一方面至第五方面中任意一种可能的实现方式中的方法的操作。
可选地，该系统芯片还可以包括至少一个存储器和总线，该至少一个存储器用于存储处理器执行的指令。
可选的，该输入输出接口以接口电路的方式实现。
附图说明
图1是应用于本申请的通信系统的示意图。
图2是本申请提供的通信方法的示意性流程图。
图3是本申请提供的另一通信方法的示意性流程图。
图4是本申请提供的通信方法的一个具体实施例的示意性流程图。
图5是本申请提供的一种通信方法的示意性流程图。
图6是本申请提供的另一通信方法的示意性流程图。
图7是根据本申请的通信装置的示意性框图。
图8是本申请提供的通信装置的示意性框图。
图9是本申请提供的另一通信设备的示意性框图。
图10是本申请提供的另一通信设备的示意性框图。
图11是根据本发明实施例提供的终端设备的结构框图。
图12是根据本发明实施例提供的接入网设备的结构框图。
图13是本申请提供的通信设备的示意性框图。
图14是根据本发明实施例提供的核心网设备的结构框图。
具体实施方式
本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通信(global system for mobile communications，GSM)系统、码分多址(code division multiple access，CDMA)系统、宽带码分多址(wideband code division multiple access，WCDMA)系统、通用分组无线业务(general packet radio service，GPRS)、长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、通用移动通信系统(universal mobile telecommunication system，UMTS)、全球互联微波接入(worldwide interoperability for microwave access，WiMAX)通信系统、第五代(5th generation，5G)系统或新无线(new radio，NR)等。
图1是本申请的实施例应用的移动通信系统的架构示意图。如图1所示，该移动通信系统包括核心网设备110、接入网设备120和终端设备130A至130D。终端设备130A至130D为具有相同的特性，例如，都属于智能家居或者都属于智能街灯。
其中，终端设备可以指用户设备、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。终端设备还可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，5G网络中的终端设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端设备等，本申请实施例对此并不限定。
接入网设备可以是全球移动通信(global system for mobile communications，GSM)系统或码分多址(code division multiple access，CDMA)中的基站(base transceiver station，BTS)，也可以是宽带码分多址(wideband code division multiple access，WCDMA)系统中的基站(NodeB，NB)，还可以是LTE系统中的演进型基站(evolved NodeB，eNB或eNodeB)，还可以是云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器，或者该网络设备可以为中继站、接入点、车载设备、可穿戴设备以及5G网络中的网络设备或者未来演进的PLMN网络中的网络设备等，本申请实施例并不限定。
核心网设备可以是移动性管理实体(mobility management entity，MME)，或者，核心网接入和移动性管理功能(core access and mobility management function，AMF)，或者还可以是其他负责终端设备接入管理和移动性管理的设备，本申请实施例对此不作限定。
参见图1，接入网设备120通过无线或有线方式与核心网设备110连接。核心网设备110与接入网设备120可以是独立的不同的物理设备，也可以是将核心网设备110的功能与接入网设备的逻辑功能集成在同一个物理设备上，还可以是一个物理设备上集成了部分核心网设备210的功能和部分的接入网设备120的功能。
终端设备130A至130D分别通过无线的方式与接入网设备120相连。虽然终端设备130A至130D具有相同的属性，它们的上下文可能包括相同的部分，但根据现有技术，接入网设备120仍然需要保存针对终端设备130A至130D中每个终端设备的上下文，导致 存储资源消耗较大，降低了接入网设备的性能。一种可能的方式，此处的上下文可包括终端设备在网络中的配置信息和/或终端设备的能力信息，本申请实施例上下文的具体内容不做限定。
为解决上述问题，本申请提供了一种获取终端设备的上下文的方法，能够降低接入网设备存储终端设备的上下文所需的存储资源。
一种可能的方式中，本申请实施例提供的一种通信方法中，通过对具有相同属性信息的终端设备进行分组，使得终端设备的上下文可以分为公共上下文和专用上下文两部分，公共上下文由一个分组的各终端设备共享，专用上下文为各终端设备特有的上下文，接入网设备为每个分组存储一份公共上下文以及存储该分组内各终端设备的专用上下文，从而达到维护各终端设备的上下文的目的。由于接入网设备不必将具有相同属性的多个终端设备的上下文的相同部分都存储一份，因此能够降低接入网设备存储终端设备的上下文所需的存储资源。以下，将对本申请进行详细描述。
可选地，所述属性信息可以是服务质量(quality of service，QoS)属性、终端设备的业务类型、终端设备的切片类型、终端设备的能力、终端设备是否静止、终端设备的节电需求、以及终端设备的时延需求。应理解，这里所列举的终端设备的属性信息仅是示例性说明，并不应对本申请构成任何限定，在具体实施时，终端设备的属性信息还可以是其他的信息。进一步地，QoS属性例如可以包括下述中的一种或多种：优先级、包时延规划、错包率、时延敏感指示、平均窗口、以及数据包最大突发量。本申请也不对QoS属性所包括的内容作限定。
可以理解，示例性地，属于同一组的终端设备可以具有相同QoS属性的终端设备。或者，属于同一组的终端设备可以具有相同的业务类型和切片类型。或者，属于同一组的终端设备的节电需求和时延需求相同。
应理解，在本申请实施例中，终端设备和/或网络设备(接入网设备或核心网设备)可以执行本申请实施例中的部分或全部步骤，这些步骤或操作仅是示例，本申请实施例还可以执行其它操作或者各种操作的变形。此外，各个步骤可以按照本申请实施例呈现的不同的顺序来执行，并且有可能并非要执行本申请实施例中的全部操作。
图2示出了本申请实施例的通信方法的示意性流程图200。该方法200可以应用于图1所示的通信系统100，但本申请实施例不限于此。
S210，第一接入网设备确定终端设备#1A对应的组标识和终端设备的标识。
应理解，第一接入网设备可以是终端设备#1A首次接入网络时所接入的接入网设备，但本申请实施例对此不作限定，比如，第一接入网设备也可以是任意一个为终端设备#1A提供服务的接入网设备。
S220，第一接入网设备向终端设备#1A发送第一消息，第一消息包括该组标识和该终端设备的标识。
S230，终端设备#1A保存该组标识和该终端设备的标识。
其中，组标识用于标识终端设备所属分组，终端设备的标识用于在终端设备所属分组内识别该终端设备。组标识与公共上下文对应，终端设备的标识与终端设备#1A的专用上下文对应。一种可能的方式中，一个组标识与一份公共上下文关联，一个终端设备的标识与一份专用上下文关联。该公共上下文和该专用上下文组成该终端设备#1A的上下文或者 说该终端设备#1A的上下文全部上下文，并且，该公共上下文由该分组内的所有终端设备共享，该专用上下文是终端设备#1A专用的上下文。
可选的，属于同一分组的任一终端设备的上下文由该标识该分组的组标识对应的公共上下文和该终端设备的专用上下文组成。
具体来讲，在一种可能的方式中，第一接入网设备在与终端设备#1A建立连接的过程中，可以确定终端设备#1A对应的组标识和终端设备的标识，并且可以为终端设备#1A分配该组标识对应的公共上下文和该终端设备的标识对应的专用上下文。第一接入网设备配置终端设备#1A进入非连接态的过程中，可以通过第一消息向终端设备#1A发送该组标识和该终端设备的标识。终端设备#1A接收到网络设备分配的组标识和终端设备的标识后，可以保存该组标识和该终端设备的标识。在第一接入网设备需要再次接入网络时，可以根据该组标识和该终端设备的标识接入网络。
因此，本申请实施例对终端设备进行分组，终端设备的上下文包括对应于组标识的公共上下文和对应于终端设备的标识的专用上下文，其中每个分组内的所有终端设备共享同一个公共上下文，并且每个终端设备使用各自的专用上下文，这样，接入网设备在维护终端设备的上下文时，不需要存储每个终端设备的所有上下文，从而能够降低接入网设备维护上下文的资源需求。例如，若终端设备为该分组内第一个接入第一接入网设备的终端设备，第一接入网设备可以配置并保存终端设备所属分组对应的公共上下文以及终端设备对应的专用上下文。若后续需要为属于该分组的其他终端设备配置上下文，第一接入网设备只需配置和保存其他终端设备的专用上下文。若第一接入网设备在配置终端设备的上下文之前，已经保存了终端设备对应的分组所对应的该公共上下文，那么第一接入网设备无需保存该终端设备对应的公共上下文。
以下，为了便于理解和描述，将终端设备#1A对应的组标识记为：组标识#1，将终端设备#1A的标识记为：标识#A，对本申请实施例进行详细描述。应理解，终端设备#1A可以是任一终端设备。可以理解的是，组标识和终端设备的标识可以有不同的表示方式，本申请实施例对此不作限定。
下面，首先举例说明第一接入网设备确定终端设备#1A对应的组标识的两种方式。
方式一
第一接入网设备可以根据预设规则或者自主确定的分组规则，确定终端设备#1A对应的组标识。预设规则可以由若干个网络设备(例如，该网络设备可以包括接入网设备和/或核心网设备)协商确定，或者由核心网设备确定后发送给第一接入网设备，或者由运营和管理实体(operation and Management，OAM)配置，或者由协议规定，本申请实施例对此不作限定。例如，该预设规则可以定义组标识与终端设备的属性信息之间的对应关系。举例来说，若预设规则或分组规则定义了组标识#1与满足第一条件的A属性信息对应，组标识#2与满足第二条件的A属性信息对应，那么，在某一终端设备的A属性信息满足第一条件时，第一接入网设备就将该终端设备的组标识确定为组标识#1，在该终端设备的A属性信息满足第二条件时，第一接入网设备就将该终端设备的组标识确定为组标识#2。
可选地，终端设备的属性信息可以包括下述信息中的一种或者多种：终端设备的QoS属性、终端设备的业务类型、终端设备的切片类型、终端设备的能力、终端设备是否静止、终端设备的节电需求、以及终端设备的时延需求。应理解，这里所列举的终端设备的属性 信息仅是示例性说明，并不应对本申请构成任何限定，在具体实施时，终端设备的属性信息还可以是其他的信息。进一步地，QoS属性例如可以包括下述中的一种或多种：优先级、包时延规划、错包率、时延敏感指示、平均窗口、以及数据包最大突发量。本申请也不对QoS属性所包括的内容作限定。本申请中，终端设备的属性信息可以是终端设备#1A发送给第一接入网设备的，也可以是第一接入网设备从核心网设备(例如，第一核心网设备)处获取的，本申请并不限定第一接入网设备如何获取终端设备#1A的属性信息。
为使本领域技术人员更好的理解本申请，接下来以预设规则定义了终端设备的时延需求与组标识之间的对应关系为例，结合表1，举例说明第一接入网设备如何根据预设规则自主确定终端设备#1A对应的组标识。
表1
组标识 时延需求(ms)
组标识#1 ≤2
组标识#2 ＞2，且≤4
组标识#3 ＞4，且≤5
…… ……
如表1所示，时延需求满足小于或者等于2ms的终端设备的组标识可以被确定为组标识#1，时延需求满足大于2ms且小于或者等于4ms的终端设备的组标识可以被确定为组标识#2，时延需求满足大于4ms且小于或者等于5ms的终端设备的组标识可以被确定为组标识#3。本申请实施例中假定终端设备#1A的时延需求满足小于或者等于2ms，因此其组标识被配置为组标识#1。
方式二
第一接入网设备获取核心网设备发送的终端设备#1A对应的组标识。比如，在终端设备#1A请求接入网络时，第一接入网设备可以将终端设备#1A的属性信息发送给核心网设备，由核心网设备根据终端设备#1A的属性信息确定终端设备#1A对应的组标识。然后，核心网设备再将所确定的组标识发送给第一接入网设备，第一接入网设备将所接收到的组标识确定为终端设备#1A对应的组标识。与方式一类似，核心网设备可以根据预设规则确定终端设备#1A的组标识，具体可以参见对方式一所作的说明，这里不再赘述。
进一步地，在第一接入网设备确定组标识#1和标识#A后，第一接入网设备可以确定该组标识#1对应的公共上下文，以及标识#A对应的专用上下文。
在一种实现方式中，可以预定义或者预配置组标识所对应的公共上下文。例如，第一接入网设备可以预先保存与各个组标识对应的公共上下文。当第一接入网设备确定终端设备#1A的组标识为#1时，第一接入网设备可以根据已经保存的组标识#1对应的公共上下文确定终端设备#1A的公共上下文。
在另一种实现方式中，第一接入网设备可以在第一个被配置为组标识#1的终端设备接入第一接入网设备时，配置并保存组标识#1对应的公共上下文。举例来说，组标识#1对应的公共上下文可以是第一个被配置为组标识#1的终端设备接入第一接入网设备时，第一接入网设备根据组标识#1对应的终端设备的属性信息和/或其他信息配置的。也就是说，若终端设备#1A为第一个被配置为组标识#1的终端设备，当终端设备#1A接入第一接 入网设备时，第一接入网设备需要配置并保存组标识#1对应的公共上下文；若终端设备#1A不是第一个被配置为组标识#1的终端设备，则说明第一接入网设备已经保存了组标识#1对应的公共上下文，第一接入网设备不用重复配置并保存组标识#1对应的公共上下文。
需要说明的是，第一接入网设备配置公共上下文的方式可以是第一接入网设备自主配置公共上下文，也可以是获取核心网设备配置的公共上下文，或者第一接入网设备配置协议规定的公共上下文，本申请实施例对此不作限定。
应理解，组标识可以用来在一定区域内标识一个分组。该一定区域可以是预先配置的，例如，由运营和管理实体(operation and Management，OAM)预先配置。或者，该一定区域可以由协议规定。或者，该一定区域可以由第一接入网设备和其它接入网设备交互确定。在组标识在一定区域内标识一个分组的场景下，可以为该一定区域内的各网络设备(例如，接入网设备和/或核心网设备)预配置各组标识所对应的公共上下文。那么，若组标识相同但终端设备的标识不同的两个终端设备分别接入该一定区域内的两个接入网设备，该两个接入网设备所确定的这两个终端设备的公共上下文相同。
另外，在组标识#1在一定区域内标识一个分组的场景下，若公共上下文由该一定区域内的核心网设备配置，类似地，若组标识相同但终端设备的标识不同的两个终端设备分别接入该一定区域内属于同一核心网设备的不同接入网设备时，该两个接入网设备所确定的这两个终端设备的公共上下文相同。
可选地，公共上下文可以包括下述信息中的一种或多种：QoS属性、RRC配置、SDAP配置、DRB配置、终端设备的能力、以及终端设备支持的安全参数类型。也就是说，对于特定分组，该分组内所有终端设备的QoS属性、RRC配置、SDAP配置、DRB配置、终端设备的能力、以及终端设备支持的安全参数类型中的一种或者多种相同。
可选地，专用上下文可以包括安全参数。比如，终端设备#1A的专用上下文可以包括终端设备#1A的安全参数。安全参数包括完整性保护算法、加密算法、安全密钥参数的至少一种。安全密钥参数可以为KgNB密钥、下一跳(next hop，NH)密钥、下一跳密钥(next hop chaining count，NCC)的至少一种。安全密钥参数还可以包括用于完整性保护和/或加密的信令面和/或用户面的安全密钥。应理解，专用上下文也可以是其他的信息，或者专用上下文除包括安全参数外，还可以包括其他的信息，本申请实施例对此不作限定。比如，不将SDAP配置信息作为公共上下文，而将SDAP配置信息作为专用上下文，或者，SDAP配置信息中的一部分可以作为公共上下文，另一部分可以作为专用上下文。
一般地，不同的组标识对应的公共上下文不同，但本申请也不排除不同组标识对应相同公共上下文的可能性。类似地，一般情况下，各终端设备对应的专用上下文不同，比如，标识#1对应的分组内的各终端设备对应的专用上下文不同，但本申请也不排除同一分组内的多个终端设备对应相同专用上下文的可能性。
可选地，作为本申请一个实施例，第一接入网设备确定该组标识#1对应的公共上下文后，还可以向终端设备#1A发送该公共上下文。
例如，在公共上下文由第一接入网设备自主配置，或者由核心网设备配置的情况下，第一接入网设备可以向终端设备#1A发送组标识#1对应的公共上下文。需要说明的是，在此情况下，终端设备#1A可以不区分第一接入网设备发送的信息中哪些信息是组标识，哪些信息是终端设备的标识。比如，组标识#1的长度为5个比特(bit)，标识#A的长度为 4bit，第一接入网设备发送一个9bit的标识信息给终端设备#1A，终端设备#1A不需要区别该9bit内哪些比特是组标识的，哪些比特是终端设备的标识。进一步地，终端设备也可以不区分哪些上下文是公共上下文，哪些是专用上下文。
此外，第一接入网设备也可以不向终端设备#1A发送公共上下文。例如，可以为终端设备预配置组标识所对应的公共上下文，那么终端设备#1A根据第一接入网设备发送的组标识#1可以确定对应的公共上下文。需要说明的是，在此情况下，终端设备#1A需要区分第一接入网设备向其发送的标识信息中哪些信息是组标识，哪些上下文是公共上下文。
可选地，作为本申请一个实施例，第一接入网设备确定该专用上下文后，还可以向终端设备#1A发送该专用上下文。
可选地，作为本申请一个实施例，终端设备#1A接收到第一消息处于非激活态后，若再次接入第一接入网设备，第一接入网设备可以为终端设备#1A重新分配该终端设备的标识。应理解，第一接入网设备也可以为终端设备#1A重新分配组标识，但本申请实施例对此不作限定。
可选地，该方法还可以包括：
S240，终端设备#1A向第二接入网设备发送第二消息。
一种可能的方式中，第二消息可以用于请求接入第二接入网设备。比如，当终端设备#1A处于非激活态时，若终端设备#1A移动到第二接入网设备覆盖的第二服务小区，终端设备#1A可以向第二接入网设备发送第二消息，请求接入第二接入网设备。第二消息例如可以是随机接入请求消息、RRC连接请求消息、恢复请求消息等，本申请对此不作限定。
应理解，非激活态可以为RRC去激活态RRC_INACTIVE状态、轻RRC连接状态(light RRC connection)或者增强的空闲态。
一种可能的方式中，当终端设备在非激活态时，接入网设备虽然释放了该终端设备的RRC连接，但终端设备和接入网设备存储着终端设备的上下文。终端设备和核心网设备存储终端设备的非接入层的上下文。可选地，接入网设备和核心网设备还可以保持该终端设备在接入网设备和核心网设备的连接。
第二消息可以用于第二接入网设备确定组标识#1和标识#A。比如，第二消息可以包括终端设备#1A的标识，即标识#A。进一步地，第二消息还可以包括组标识#1。或者，第二消息可以承载于与组标识#1对应的物理资源上，第二接入网设备根据发送第二消息的物理资源，可以确定终端设备#1A对应的组标识为组标识#1。比如，若第二接入网设备广播或预先配置了映射关系：{[组标识#1,物理资源#1]；[组标识#2,物理资源#2],…}，那么，终端设备#1A若在物理资源#1上发送第二请求，第二接入网设备便可以确定终端设备#1A对应组标识#1。所述物理资源具体可以是物理随机接入信道(physical random access channel，PRACH)资源，比如包括物理随机接入前导，和/或，物理随机接入时/频域资源，但本申请并不限定于此。
应理解，第二接入网设备接收到第二消息后，依照现有技术对终端设备#1A进行响应，比如第二接入网设备可以配置终端设备#1A进入空闲态、非激活态或者激活态。具体的响应流程可以参照现有技术，这里不再赘述。
可选地，作为本申请一个实施例，第二消息还可以包括短的消息认证码完整性或者，例如可以是shortMAC-I或者short resumeMAC-I，短的消息认证码完整性是终端设备#1A 根据第一服务小区的物理小区标识PCI、第二服务小区的小区标识和组标识#1确定的。
应理解，在本申请实施例中，第一服务小区为第一接入网设备所覆盖的小区，第二服务小区为第二接入网设备所覆盖的小区。第一服务小区可以是源服务小区，相应地，第二服务小区可以是目标小区或新服务小区。
终端设备#1A发送第二消息后，第二接入网设备可以通过图3所示的方法300获取终端设备#1A的上下文，以将终端设备#1A接入网第二接入网设备。下面，对此进行详细说明。
图3示出了本申请实施例的通信方法的示意性流程图300。方法300可以应用于终端设备#1A从第一接入网设备切换至第二接入网设备的场景中，但本申请实施例并不仅限于此应用场景。需要说明的是，下文中出现的与上文中相同的概念、词语或者术语，，可以参见上文中对其所作的解释和说明，下文中将不再赘述。比如，方法300中的第一接入网设备为方法200中的第一接入网设备。
S310，第二接入网设备接收来自终端设备#1A的第二消息。
其中，第二消息可以用于终端设备#1A请求接入第二接入网设备，具体可以参见上文中对第二消息所作的说明，这里不再赘述。
S320，第二接入网设备根据第二消息，确定终端设备#1A对应的组标识和终端设备#1A的标识，即，第二接入网设备确定组标识#1和标识#A。
比如，第二消息可以包括组标识#1和标识#A。又如，第二消息可以包括标识#A，第二消息可以承载于与组标识#1对应的物理资源上，第二接入网设备根据发送第二消息的物理资源，可以确定终端设备#1A对应的组标识为组标识#1。
应理解，第二接入网设备根据第二消息可以获知需要从第一接入网设备处获取终端设备的上下文。比如，第二消息可以包括用于指示第一接入网设备的标识信息。
S330，第二接入网设备向第一接入网设备发送第三消息。
相应地，第一接入网设备接收来自第二接入网设备的第三消息。
其中，第三消息可以包括组标识#1和标识#A，第三消息可以用于请求标识#A对应的专用上下文。
可选地，作为本申请一个实施例，第三消息还可以用于请求组标识#1对应的公共上下文。相应地，第三响应消息还可以包括组标识#1对应的公共上下文。
作为第三消息的一种实现方式，第三消息可以包括指示信息，该指示信息可以用于指示是否请求组标识#1对应的公共上下文，或者该指示信息用于指示是否仅请求标识#A对应的专用上下文，或者该指示信息用于指示是否请求终端设备#1A的全部上下文，其中全部上下文是指终端设备#1A对应的公共上下文和专用上下文。一种可能的方式中，对该指示信息可以用于指示是否请求组标识#1对应的公共上下文的情况，可以理解为是隐式的或者默认的指示需要请求对于标识#A对应的专用上下文，也就说不单独指示请求标识#A对应的专用上下文，当该指示信息可以用于指示请求组标识#1对应的公共上下文，表示请求公共上下文和标识#A对应的专用上下文，当该指示信息指示不请求组标识#1对应的公共上下文，表示仅请求标识#A对应的专用上下文。综上，第一接入网设备根据该指示信息，能够确定第二接入网设备所请求的上下文的类型，即，仅请求专用上下文，还是请求公共上下文和专用上下文。
举例来说，该指示信息可以是1比特(bit)的信息。比如，当该比特取值为TRUE或者1时，用于指示第三请求消息用于请求标识#A对应的专用上下文以及组标识#1对应的公共上下文，当该比特取值为FALSE或者0时，用于指示第三请求消息仅用于请求组标识#1对应的公共上下文。
举例来说，若第二接入网设备已保存有与组标识#1对应的公共上下文，则第二接入网设备可以仅请求组标识#1对应的公共上下文。比如，第二接入网设备在获取到终端设备#1A发送的组标识#1之前，终端设备#1A所属分组内的其他终端设备(例如，终端设备#1B)需要接入第二接入网设备，并且第二接入网设备已经从第一接入网设备处获取并保存了组标识#1对应的公共上下文。此时，第二接入网设备不需要再次从第一接入网设备处获取组标识#1对应的公共上下文，而只需获取标识#A对应的专用上下文。又如，第二接入网设备可以根据组标识#1，从其预先保存的公共上下文中确定组标识#1对应的公共上下文，而不需要从第一接入网设备处获取组标识#1对应的公共上下文。
举例来说，在第二接入网设备确定其未保存有或无法确定与组标识#1对应的公共上下文时，第二接入网设备可以向第一接入网设备请求组标识#1对应的公共上下文。应理解，在第二接入网设备确定其保存有与组标识#1对应的公共上下文时，也可以请求组标识#1对应的公共上下文，本申请对此不作限定。
S340，第一接入网设备向第二接入网设备发送第三响应消息。
相应地，第二接入网设备接收来自第一接入网设备的第三响应消息。其中，第三响应消息包括标识#A对应的专用上下文。
可选地，第一接入网设备向第二接入网设备发送第三响应消息后，第一接入网设备可以删除标识#A对应的专用上下文。进一步地，第一接入网设备也可以删除组标识#1对应的公共上下文。
综上，本申请实施例对终端设备进行分组，终端设备的上下文包括对应于分组的公共上下文和对应于该终端设备的专用上下文。在第二接入网设备需要从第一接入网设备获取第一终端的上下文，但其已经保存或者可以确定该终端设备所属分组对应的公共上下文的情况下，第二接入网设备可以只从第一接入网设备获取终端设备的专用上下文即可，而不从第一接入网设备获取终端设备所属分组对应的公共上下文。相应地，第一接入网设备可以只向第二接入网设备发送终端设备的专用上下文，而不向终端设备发送终端设备所属分组对应的公共上下文，从而能够节省信令开销。
因此，本申请的获取终端设备上下文的方法，能够降低接入网设备间转发终端设备的上下文的信令开销。
可选地，作为本申请一个实施例，第三消息还可以包括短的消息认证码完整性或者，例如可以是shortMAC-I或者short resumeMAC-I，短的消息认证码完整性是终端设备#1A根据第一服务小区的物理小区标识PCI、第二服务小区的小区标识和组标识#1确定的。
应理解，在本申请实施例中，第一服务小区为第一接入网设备所覆盖的小区，第二服务小区为第二接入网设备所覆盖的小区。第一服务小区为源服务小区，相应地，第二服务小区为目标小区或新服务小区。
可选地，作为本申请一个实施例，第三响应消息还包括下述中的(1)或(2)，或者可以同时包括(1)和(2)。
(1)组标识#1对应的分组内的其他终端设备的专用上下文。
具体来讲，第一接入网设备可以在向第二接入网设备返回第二接入网设备所请求的上下文的同时，向第二接入网设备返回终端设备#1A所属分组内除终端设备#1A外的至少一个其他终端设备的标识和对应的专用上下文。这样，若终端设备#1A所属分组内除终端设备#1A外的其他任一终端设备(例如，终端设备#1C)需要接入第二接入网设备时，第二接入网设备不需要向第一接入网设备发送请求消息，以请求终端设备#1C的专用上下文。从而，能够进一步节省信令开销。
(2)组标识#1对应的分组所对应的终端设备的属性信息，或者说，组标识#1对应的终端设备的属性信息，或者说，组标识#1内所有终端设备的公共属性信息。
举例来说，组标识#1对应的终端设备的属性信息可以是有节电需求。应理解，组标识#1内的各终端设备的属性都包括有节电需求，或者说，第一接入网设备配置具有节电需求的终端设备的组标识为组标识#1。
在S340步骤中，第一接入网设备可以在向第二接入网设备返回第二接入网设备所请求的上下文的同时，向第二接入网设备返回组标识#1对应的分组所对应的终端设备的属性信息。第二接入网设备根据组标识#1和组标识#1对应的终端设备的属性信息，可以更好的管理组标识#1对应分组内的各终端设备，从而有利于提高系统性能。
为使本领域技术人员更好地理解本申请，以下结合图4所示获取终端设备的上下文的方法400，对本申请的方法进行详细描述。
图4示出了本申请提供的获取终端设备的上下文的方法的一个具体示例。
S401，终端设备#1A与第一接入网设备建立连接的过程中，第一接入网设备确定组标识#1和标识#A，并且确定组标识#1对应的公共上下文和标识#A对应的公共上下文。
可选地，第一接入网设备可以接收终端设备#1A发送的属性信息，或者接收核心网设备发送的终端设备#1A的属性信息，根据终端设备#1A的属性信息，确定组标识#1和标识#A。
第一接入网设备如何确定组标识#1对应的公共上下文和标识#A对应的公共上下文可以参照上文中的描述，这里不再赘述。S402，第一接入网设备向终端设备#1A发送上述第一消息。
第一消息包括组标识#1和标识#A。比如，当第一接入网设备配置终端设备进入非连接态时，比如空闲态，非激活态或者其它非连接态，可以向终端设备#1A发送组标识#1和标识#A。
S403，第一接入网设备向终端设备#1A发送公共上下文和专用上下文。
可以理解地，第一接入网设备向终端设备#1A发送公共上下文和专用上下文的消息可以相同，也可以不同。
S404，终端设备#1A向第二接入网设备发送RRC恢复请求消息(即，第二消息的一例)，该RRC恢复请求消息包括组标识#1和标识#A。
可选地，RRC恢复请求还可以包括短的消息认证码完整性或者，例如可以是shortMAC-I或者short resumeMAC-I。
S405，第二接入网设备向第一接入网设备发送获取上下文请求消息(即，第三消息的一例)，该获取上下文请求消息包括组标识#1和标识#A。
获取上下文请求消息可以包括指示信息。该指示信息可以用于指示是否请求公共上下文；或者，该指示信息可以用于指示是否请求终端设备#1A的全部上下文；或者该指示信息可以用于指示是否仅请求终端设备#1A的专用上下文。比如，若在S405之前，终端设备#1B已经接入第二接入网设备，则说明第二接入网设备已经保存了组标识#1对应的公共上下文。此时，该指示信息用于指示仅请求终端设备#1A的专用上下文，即标识#A对应的专用上下文。应理解，这里以指示信息仅用于请求终端设备#1A的专用上下文为例进行描述，但本申请并不限定指示信息是否仅用于请求终端设备#1A的专用上下文。
S406，第一接入网设备向第二接入网设备发送终端设备#1A的专用上下文。
比如，第一接入网设备根据第二接入网设备发送的指示信息，仅向第二接入网设备发送终端设备#1A的专用上下文。由于第一接入网设备不需要再次发送组标识#1对应的公共上下文，因此能够节省信令开销。
应理解，若S405中指示信息还用于请求公共上下文，第一接入网设备也可以在S406中发送组标识#1对应的公共上下文，本申请实施例对此不作限定。
因此，本申请实施例的通信方法，通过对终端设备进行分组，终端设备的上下文包括对应于分组的公共上下文和对应于该终端设备的专用上下文，其中每个分组内的所有终端设备共享同一个公共上下文，并且每个终端设备使用各自的专用上下文，这样，接入网设备在维护或交互终端设备的上下文时，不需要存储或传输每个终端设备的所有上下文内容，从而能够降低接入网设备维护上下文的资源需求。
上文中主要对终端设备与接入网设备之间基于组标识进行交互进行了说明，容易理解，接入网设备和核心网设备之间也可以基于组标识进行交互。下文中将结合图5所示的通信方法500以及图6所示的通信方法600进行详细说明。
图5是本申请提供的一种通信方法。该方法可以应用于接入网设备为终端设备分配组标识的场景中。
S510，第一接入网设备确定终端设备#1A的组标识为组标识#1。
具体地，第一接入网设备与终端设备#1A建立连接时或者获取到终端设备#1A的属性信息后，第一接入网设备可以为终端设备#1A分配组标识#1。比如，第一接入网设备可以根据终端设备#1A的属性信息，为终端设备#1A分配组标识#1，具体可以参照上文中所作的说明，这里不再赘述。
S520，第一接入网设备向核心网设备发送第四消息。
第四消息包括组标识#1，第四消息用于请求核心网设备配置组标识#1对应的NGAP连接配置参数。
可选的，NGAP连接配置参数包括PDU会话资源配置，QoS流配置，DRB配置中的至少一种。
S530，核心网设备确定并保存组标识#1对应的NGAP连接配置参数。
S540，核心网设备向第一接入网设备发送组标识#1对应的NGAP连接配置参数。
相应地，第一接入网设备接收组标识#1对应的NGAP连接配置参数后，保存组标识#1对应的NGAP连接配置参数。
S550，第一接入网设备确定终端设备#1B的组标识为组标识#1。
具体地，第一接入网设备与终端设备#1B建立连接时或者获取到终端设备#1B的属性 信息后，第一接入网设备可以为终端设备#1B分配组标识#1。
进一步地，第一接入网设备还可以为终端设备#1B分配终端设备#1B的标识(即，标识#B)。比如，第一接入网设备可以根据终端设备#1B的属性信息，为终端设备#1B分配组标识#1，第一接入网设备如何为终端设备#1B分配组标识可以参照上文中对确定终端设备#1A的组标识所作的说明，这里不再赘述。
S560，第一接入网设备向核心网设备发送激活请求消息。
该激活请求消息用于请求核心网设备为终端设备#1B激活上述中的组标识#1对应的NGAP连接配置参数。该激活请求消息可以携带组标识#1。
可选地，该激活请求消息中还可以携带用于核心网设备识别终端设备#1B的标识信息。用于核心网设备识别终端设备的标识信息可以是国际移动用户标识(International Mobile Subscriber Identity，IMSI)、系统架构演进临时移动用户标识(System Architecture Evolution Temporary Mobile Subscriber Identity，S-TMSI)，和IMSI或S-TMSI相关的其它标识信息的至少一种。
S570，核心网设备根据该激活请求消息，为终端设备#1B激活组标识#1对应的NGAP连接配置参数。
可选地，该方法还可以包括：
S580，核心网设备向第一接入网设备发送响应。
第一接入网设备接收到响应后，其中，所述响应可以是确认消息或者失败消息或者拒绝消息，当所述响应是确认消息时，第一接入网设备可以确定核心网设备已经为终端设备#1B激活了组标识#1对应的NGAP连接配置参数。
因此，本申请实施例的通信方法，通过对终端设备进行分组，并为属于同一分组内的终端设备配置相同的NGAP连接配置参数，能够减少NGAP连接的建立。由于核心网设备只需要保存各分组对应的一套NGAP连接配置参数，而不需要保存每个终端设备的NGAP连接配置参数，因此能够节省核心网设备的存储资源。
图6是本申请提供的一种通信方法。该方法可以应用于核心网设备为终端设备分配组标识的场景中。
S610，核心网设备确定终端设备#1A的组标识为组标识#1。
具体地，第一接入网设备接入网络的过程中，终端设备#1A需要建立和核心网设备的NGAP连接。在核心网设备建立核心网设备与终端设备#1A的NGAP连接的过程中，可以为终端设备#1A确定组标识#1。比如，核心网设备可以根据终端设备#1A的属性信息，为终端设备#1A确定组标识#1。其中，核心网设备为终端设备#1A确定组标识的方式与前文类似，只是确定组标识的执行主体有所区别，在确定组标识的方式和原理上是类似的，这里不再赘述。
S620，核心网设备确定并保存组标识#1对应的NGAP连接配置参数。
NGAP连接配置参数具体可以参照上文描述，此处不再赘述。
S630，核心网设备向第一接入网设备发送组标识#1和组标识#1对应的NGAP连接配置参数。
相应地，第一接入网设备接收组标识#1对应的NGAP连接配置参数后，保存组标识#1对应的NGAP连接配置参数。
S640，核心网设备确定终端设备#1B的组标识为组标识#1。
具体地，核心网设备建立核心网设备与终端设备#1B的NGAP时，可以由核心网设备为终端设备#1B确定组标识#1。其中，核心网设备为终端设备#1B确定组标识的方式与S220类似，只是确定组标识的执行主体有所区别，在确定组标识的方式和原理上是类似的，这里不再赘述。
S650，核心网设备向第一接入网设备向发送激活指示信息。
该激活指示信息用于指示第一接入网设备为终端设备#1B激活上述中的组标识#1对应的NGAP连接配置参数。该激活指示信息可以携带组标识#1，用于第一接入网设备确定需要激活NGAP连接配置参数的组标识。
S660，第一接入网设备根据该激活指示信息，为终端设备#1B激活组标识#1对应的NGAP连接配置参数。
可选地，该方法还可以包括：
S670，第一接入网设备向该核心网设备发送响应。
第一接入网设备接收到响应后，其中，所述响应可以是确认消息或者失败消息或者拒绝消息，当所述响应是确认消息时，核心网设备可以确定第一接入网设备已经为终端设备#1B激活了组标识#1对应的NGAP连接配置参数。
因此，本申请实施例的通信方法，通过对终端设备进行分组，并为属于同一分组内的终端设备配置相同的NGAP连接配置参数，能够减少NGAP连接的建立，从而能够节省信令开销。由于核心网设备只需要保存各分组对应的一套NGAP连接配置参数，而不需要保存每个终端设备的NGAP连接配置参数，因此能够节省核心网设备的存储资源。
图7是根据本申请实施例提供的通信装置的结构示意图。该通信装置可以为终端设备，也可以为可用于终端设备的部件(例如芯片或者电路)。该通信装置可以用于实现对应于上述各个方法实施例中终端设备所执行的流程或者步骤。
如图7所示，通信装置700可以包括接收单元710和存储单元720。
可选的，接收单元710，用于从第一接入网设备接收第一消息，其中，所述第一消息包括所述通信装置对应的组标识和所述通信装置的标识，所述组标识用于标识所述通信装置所属分组，所述通信装置的标识用于在所述通信装置所属分组内识别所述通信装置，所述组标识和公共上下文对应，所述公共上下文由所述通信装置所属分组内的所有通信装置共享，所述通信装置的标识与所述通信装置的专用上下文对应。
可选的，存储单元720，用于保存所述组标识和所述通信装置的标识。
一种可能的方式中，接收单元710可以由发送器实现，存储单元720可以由存储器实现。存储单元720和接收单元710具体功能和有益效果可以参见上文中所示的方法中的终端设备#1A所作的说明，在此就不再赘述。
一种可能的实施例中，还提供了一种通信装置，该通信装置可以为终端设备，也可以为可用于终端设备的部件(例如芯片或者电路)。该通信装置可以包括收发器和存储器，可选的，还可以包括处理器。其中存储器可以用于实现存储单元720的相应功能和操作，收发器用于实现接收单元710的相应功能和操作。可选的，存储器还可以用于存储执行指令或者应用程序代码，并由处理器来控制执行，实现本申请实施例中对应于终端设备的通信方法；和/或，也可以用于暂存一些数据和指令信息等。存储器可以独立于处理器存在， 此时，存储器可以通过通信线路与处理器相连接。又一种可能的设计中，存储器也可以和处理器集成在一起，本申请实施例对此不作限定。
图8是根据本申请实施例提供的通信装置的结构示意图。该通信装置可以为接入网设备，也可以为可用于接入网设备的部件(例如芯片或者电路)。该通信装置可以用于实现对应于图2或者图4或者图5或者图6所示方法实施例中第一接入网设备所执行的流程或者步骤。
如图8所示，通信装置800可以包括处理单元810和发送单元820。当通信装置800用于实现图2或者图4所示方法实施例时：
处理单元810，用于确定终端设备对应的组标识和所述终端设备的标识，所述组标识用于标识所述终端设备所属分组，所述终端设备的标识用于在所述终端设备所属分组内识别所述终端设备，所述组标识和公共上下文对应，所述公共上下文由所述终端设备所属分组内的所有终端设备共享，所述终端设备的标识与所述终端设备的专用上下文对应；
可选的，发送单元820，用于向所述终端设备发送第一消息，所述第一消息包括所述组标识和所述终端设备的标识。
可选的，当通信装置800用于实现图5所示方法实施例时：
处理单元810，用于确定终端设备#1A对应的组标识，进一步的，还可以用于确定终端#1B的组标识。
发送单元820可以用于向核心网设备发送第四消息，进一步的，还可以向该核心网设备发送激活请求消息，该激活请求消息中可以携带组标识，用于请求和组标识对应的NGAP连接配置参数。
可选的，通信装置800还可以包括接收单元，可以用于从核心网设备接收对组标识对应的NGAP配置参数。
当所述通信装置800用于实现图6所示的方法时：
接收单元，用于从核心网设备接收组标识#1和组标识#1对应的NGAP连接配置参数。可选的，还可以用于从核心网设备接收激活指示信息，该激活指示信息用于指示第一接入网设备为终端设备#1B激活上述中的组标识#1对应的NGAP连接配置参数。
处理单元810用于根据激活指示信息，为终端设备#1B激活组标识#1对应的NGAP连接配置参数。
发送单元820用于向该核心网设备发送响应。一种可能的方式中，发送单元820可以由发送器实现，处理单元810可以由处理器实现，接收单元可以由接收器实现，接收器和发送器可以单独设置，也可以集成在一起(称为收发器)。
可以理解的是，处理单元810、发送单元820和接收单元的具体功能和有益效果可以参见上文中对图2或者图4或者图5或者图6所示的方法中的第一接入网设备所作的说明，在此就不再赘述。
一种可能的实施例中，还提供了一种通信装置，该通信装置可以为接入网设备，也可以为可用于接入网设备的部件(例如芯片或者电路)。该通信装置可以包括处理器和收发器，可选的，还可以包括存储器。其中处理器可以用于实现处理单元810的相应功能和操作，收发器用于实现发送单元820的相应功能和操作。存储器可以用于存储执行指令或者应用程序代码，并由处理器来控制执行，实现本申请图2或者图4或者图5或者图6中所 提供的通信方法；和/或，也可以用于存储一些数据、指令信息或者收发器接收到的信息等。存储器可以独立于处理器存在，此时，存储器可以通过通信线路与处理器相连接。又一种可能的设计中，存储器也可以和处理器集成在一起，本申请实施例对此不作限定。
图9是根据本申请实施例提供的通信装置的结构框图。如图9所示，通信装置900包括接收单元910、处理单元920和发送单元930。通信装置900可以为接入网设备，也可以为可用于接入网设备的部件(例如电路或者芯片)。该通信装置可以用于实现对应于上述任意一个方法实施例中第二接入网设备所执行的流程或者步骤。
可选的，接收单元910，用于从终端设备接收第二消息，所述第二消息用于所述终端设备请求接入所述通信装置；
可选的，处理单元920，用于根据所述第二消息，确定所述终端设备对应的组标识和所述终端设备的标识，所述组标识用于标识所述终端设备所属分组，所述终端设备的标识用于在所述终端设备所属分组内识别所述终端设备，所述终端设备的标识与所述终端设备的专用上下文对应；
可选的，发送单元930，用于向所述第一接入网设备发送第三消息，所述第三消息包括所述组标识和所述终端设备的标识，所述第三消息用于请求所述终端设备的标识对应的专用上下文；
可选的，所述接收单元910还用于，从所述第一接入网设备接收第三响应消息，所述第三响应消息包括所述专用上下文。
可选的，接收单元910和发送单元930可以由发送器实现。处理单元920可以由处理器实现。接收单元910、处理单元920和发送单元930的具体功能和有益效果可以参见上文对图3所示的方法中的第二接入网设备所作的说明，在此就不再赘述。
一种可能的实施例中，还提供了一种通信装置，该通信装置可以为接入网设备，也可以为可用于接入网设备的部件(例如芯片或者电路)。该通信装置可以包括收发器和处理器，可选的，还可以包括存储器。其中收发器可以用于实现对应于接收单元910和发送单元930的相应功能和操作，处理器可以用于实现上述处理单元920的相应功能和操作。存储器可以用于存储执行指令或者应用程序代码，并由处理器来控制执行，实现图3或图4所提供的方法；和/或，也可以用于存储一些数据、指令信息或者收发器接收到的信息等。存储器可以独立于处理器存在，此时，存储器可以通过通信线路与处理器相连接。又一种可能的设计中，存储器也可以和处理器集成在一起，本申请实施例对此不作限定。
图10是根据本申请实施例提供的通信装置的结构框图。如图10所示，通信装置1000包括接收单元1010和发送单元1020。通信装置1000可以为接入网设备，也可以为可用于接入网设备的部件(例如电路或者芯片)。该通信装置可以用于实现对应于上述图3所示方法实施例中第一接入网设备所执行的流程或者步骤。
接收单元1010，用于从第二接入网设备接收第三消息，所述第三消息包括终端设备对应的组标识和所述终端设备的标识，所述组标识用于标识所述终端设备所属分组，所述终端设备的标识用于在所述终端设备所属分组内识别所述终端设备，所述终端设备的标识与所述终端设备的专用上下文对应；
发送单元1020，用于发送第三响应消息，所述第三响应消息包括所述专用上下文。
一种可能的方式中，接收单元1010和发送单元1020可以由收发器实现，接收单元 1010和发送单元1020的具体功能和有益效果可以参见上文对图3所示的方法中的第一接入网设备所作的说明，在此就不再赘述。
可以理解的是，图10所示的通信装置也可以进一步实现图2或者图4-6所示任一实施例的方法。
一种可能的实施例中，还提供了一种通信装置，该通信装置可以为接入网设备，也可以为可用于接入网设备的部件(例如芯片或者电路)。该通信装置可以包括收发器，可选的，还可以包括处理器和存储器。其中收发器可以用于实现上述接收单元1010和发送单元1020的相应功能和操作。存储器可以用于存储执行指令或者应用程序代码，并由处理器来控制执行，实现图3所提供的方法；和/或，也可以用于存储一些数据、指令信息或者收发器接收到的信息等。存储器可以独立于处理器存在，此时，存储器可以通过通信线路与处理器相连接。又一种可能的设计中，存储器也可以和处理器集成在一起，本申请实施例对此不作限定。进一步的，该通信装置也可以进一步实现图2或者图4-6所示任一实施例的方法。
图11是根据本发明实施例提供的终端设备的结构框图。如图11所示，终端设备1100包括处理器1101、存储器1102、射频电路、天线以及输入输出装置。处理器1101可以用于对通信协议以及通信数据进行处理，以及对终端进行控制，执行软件程序，处理软件程序的数据等。存储器1102主要用于存储软件程序和数据。射频电路主要用于基带信号与射频信号的转换以及对射频信号的处理。天线主要用于收发电磁波形式的射频信号。输入输出装置，例如触摸屏、显示屏，键盘等主要用于接收用户输入的数据以及对用户输出数据。需要说明的是，有些种类的终端可以不具有输入输出装置。
当需要发送数据时，处理器1101对待发送的数据进行基带处理后，输出基带信号至射频电路，射频电路将基带信号进行射频处理后将射频信号通过天线以电磁波的形式向外发送。当有数据发送到终端时，射频电路通过天线接收到射频信号，将射频信号转换为基带信号，并将基带信号输出至处理器，处理器将基带信号转换为数据并对该数据进行处理。为便于说明，图11中仅示出了一个存储器和处理器。在实际的终端产品中，可以存在一个或多个处理器和一个或多个存储器。存储器也可以称为存储介质或者存储设备等。存储器可以是独立于处理器设置，也可以是与处理器集成在一起，本申请实施例对此不做限制。
在本申请实施例中，可以将具有收发功能的天线和射频电路视为终端的收发器1103，将具有处理功能的处理器视为终端设备的处理单元。收发器也可以称为收发单元、收发机、收发装置等。处理单元也可以称为处理器，处理单板，处理模块、处理装置等。可选的，可以将收发器1103中用于实现接收功能的器件视为接收单元，将收发器1103中用于实现发送功能的器件视为发送单元，即收发器1103包括接收单元和发送单元。接收单元有时也可以称为接收机、接收器、或接收电路等。发送单元有时也可以称为发射机、发射器或者发射电路等。
处理器1101、存储器1102和收发器1103之间通过内部连接通路互相通信，传递控制和/或数据信号
上述本发明实施例揭示的方法可以应用于处理器1101中，或者由处理器1101实现。处理器1101可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器1101中的硬件的集成逻辑电路或者软件形式的指令完成。
本申请各实施例所述的处理器可以是通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本发明实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本发明实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存取存储器(random access memory，RAM)、闪存、只读存储器(read-only memory，ROM)、可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的指令，结合其硬件完成上述方法的步骤。
可选的，在一些实施例中，存储器1102可以存储用于执行如图2或者图3所示方法中终端设备执行的方法的指令。处理器1101可以执行存储器1102中存储的指令结合其他硬件(例如收发器1103)完成如图2或者图3所示方法中终端设备执行的步骤，具体工作过程和有益效果可以参见图2或者图3所示实施例中的描述。
可选的，在一些实施例中，存储器1102可以存储用于执行如图2或者图3所示方法中终端设备执行的方法的指令。处理器1101可以执行存储器1102中存储的指令结合其他硬件(例如收发器1103)完成如图2或者图3所示方法中终端设备执行的步骤，具体工作过程和有益效果可以参见图2或图3所示实施例中的描述。
本申请实施例还提供一种芯片，该芯片包括收发单元和处理单元。其中，收发单元可以是输入输出电路、通信接口；处理单元为该芯片上集成的处理器或者微处理器或者集成电路。该芯片可以执行上述方法实施例中终端设备侧的方法。
本申请实施例还提供一种计算机可读存储介质，其上存储有指令，该指令被执行时执行上述方法实施例中终端设备侧的方法。
本申请实施例还提供一种包含指令的计算机程序产品，该指令被执行时执行上述方法实施例中终端设备侧的方法。
图12是根据本发明实施例提供的接入网设备的结构框图。图12所示的接入网设备1200包括：处理器1201、存储器1202和收发器1203。
处理器1201、存储器1202和收发器1203之间通过内部连接通路互相通信，传递控制和/或数据信号。
上述本发明实施例揭示的方法可以应用于处理器1201中，或者由处理器1201实现。处理器1201可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器1201中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器1201可以是通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本发明实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本发明实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存取存储器(random access memory， RAM)、闪存、只读存储器(read-only memory，ROM)、可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器1202，处理器1201读取存储器1202中的指令，结合其硬件完成上述方法的步骤。
可选的，在一些实施例中，存储器1202可以存储用于执行如图2-图6所示方法中第一接入网设备或者图3-6所示方法中第二接入网设备执行的方法的指令。处理器1201可以执行存储器1202中存储的指令结合其他硬件(例如收发器1203)完成如图2-3所示方法中第一接入网设备或者图3-6所示方法中第二接入网设备的步骤，具体工作过程和有益效果可以参见图2-6所示实施例中的描述。
本申请实施例还提供一种芯片，该芯片包括收发单元和处理单元。其中，收发单元可以是输入输出电路、通信接口；处理单元为该芯片上集成的处理器或者微处理器或者集成电路。该芯片可以执行上述实施例中接入网设备侧执行的方法。
作为本实施例的另一种形式，提供一种计算机可读存储介质，其上存储有指令，该指令被执行时执行上述方法实施例中接入网设备侧的方法。
作为本实施例的另一种形式，提供一种包含指令的计算机程序产品，该指令被执行时执行上述方法实施例中接入网设备侧的方法。
图13是根据本申请实施例提供的通信装置的结构框图。如图13所示，通信装置1300包括处理单元1310和发送单元1320。通信装置1300可以为核心网设备，也可以为可用于核心网设备的部件(例如电路或者芯片)。该通信装置可以用于实现对应于上述方法实施例中核心网设备所执行的流程或者步骤。
处理单元1310，用于确定终端设备的组标识，以及与所述组标识对应的NGAP连接配置参数；
发送单元1320，用于向所述第一接入网设备发送所述NGAP连接配置参数。
一种可能的方式中，处理单元1310可以由处理器实现，发送单元1320可以由收发器器实现，接处理单元1310和发送单元1320的具体功能和有益效果可以参见上文对图5和图6所示的方法中的核心网设备所作的说明，在此就不再赘述。
一种可能的实施例中，还提供了一种通信装置，该通信装置可以为核心网设备，也可以为可用于核心网设备的部件(例如芯片或者电路)。该通信装置可以包括收发器，可选的，还可以包括处理器和存储器。其中收发器可以用于实现上述发送单元1320的相应功能和操作。存储器可以用于存储执行指令或者应用程序代码，并由处理器来控制执行，实现图5或图6所提供的方法；和/或，也可以用于存储一些数据、指令信息或者收发器接收到的信息等。存储器可以独立于处理器存在，此时，存储器可以通过通信线路与处理器相连接。又一种可能的设计中，存储器也可以和处理器集成在一起，本申请实施例对此不作限定。
图14是根据本发明实施例提供的核心网设备的结构框图。图14所示的核心网设备1400包括：处理器1401、存储器1402和收发器1403。
处理器1401、存储器1402和收发器1403之间通过内部连接通路互相通信，传递控制和/或数据信号。
上述本发明实施例揭示的方法可以应用于处理器1401中，或者由处理器1401实现。处理器1401可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法 的各步骤可以通过处理器1401中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器1401可以是通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立硬件组件。可以实现或者执行本发明实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本发明实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存取存储器(random access memory，RAM)、闪存、只读存储器(read-only memory，ROM)、可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器1402，处理器1401读取存储器1402中的指令，结合其硬件完成上述方法的步骤。
可选的，在一些实施例中，存储器1402可以存储用于执行如图5或者图6所示方法中核心网设备执行的方法的指令。处理器1401可以执行存储器1402中存储的指令结合其他硬件(例如收发器1403)完成如图5或者图6所示方法中核心网设备所实现的方法，具体工作过程和有益效果可以参见图5或图6所示实施例中的描述。
本申请实施例还提供一种芯片，该芯片包括收发单元和处理单元。其中，收发单元可以是输入输出电路、通信接口；处理单元为该芯片上集成的处理器或者微处理器或者集成电路。该芯片可以执行上述实施例中核心网设备侧执行的方法。
作为本实施例的另一种形式，提供一种计算机可读存储介质，其上存储有指令，该指令被执行时执行上述方法实施例中核心网设备侧的方法。
作为本实施例的另一种形式，提供一种包含指令的计算机程序产品，该指令被执行时执行上述方法实施例中核心网设备侧的方法。
在本专利申请中可能出现的对各种消息/信息/设备/网元/系统/装置/动作/操作/流程/概念等各类客体进行了赋名，但这些具体的名称并不构成对相关客体的限定，所赋名称可随着场景，语境或者使用习惯等因素而变更，对相关客体的技术含义的理解，应主要从其在技术方案中所体现/执行的功能和技术效果来确定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。可选的，本申请实施例中的单元也可以称为模块。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (24)

  1. 一种通信方法，其特征在于，包括：
    从第一接入网设备接收第一消息，其中，所述第一消息包括终端设备对应的组标识和所述终端设备的标识，所述组标识用于标识所述终端设备所属分组，所述终端设备的标识用于在所述终端设备所属分组内识别所述终端设备，所述组标识和公共上下文对应，所述公共上下文由所述终端设备所属分组内的所有终端设备共享，所述终端设备的标识与所述终端设备的专用上下文对应；
    保存所述组标识和所述终端设备的标识。
  2. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    从所述第一接入网设备接收所述公共上下文。
  3. 如权利要求1或2所述的方法，其特征在于，所述方法还包括：
    从所述第一接入网设备接收所述专用上下文。
  4. 如权利要求1至3中任一项所述的方法，其特征在于，所述方法还包括：
    向第二接入网设备发送第二消息，所述第二消息包括所述终端设备的标识和所述组标识，或者，所述第二消息承载于与所述组标识对应的物理资源上且所述第二消息包括所述终端设备的标识。
  5. 一种通信方法，其特征在于，包括：
    确定终端设备对应的组标识和所述终端设备的标识，所述组标识用于标识所述终端设备所属分组，所述终端设备的标识用于在所述终端设备所属分组内识别所述终端设备，所述组标识和公共上下文对应，所述公共上下文由所述终端设备所属分组内的所有终端设备共享，所述终端设备的标识与所述终端设备的专用上下文对应；
    向所述终端设备发送第一消息，所述第一消息包括所述组标识和所述终端设备的标识。
  6. 如权利要求5所述的方法，其特征在于，所述方法还包括：
    向所述终端设备发送所述公共上下文。
  7. 如权利要求5或6所述的方法，其特征在于，所述方法还包括：
    向所述终端设备发送所述专用上下文。
  8. 一种通信方法，其特征在于，包括：
    第二接入网设备从终端设备接收第二消息，所述第二消息用于所述终端设备请求接入所述第二接入网设备；
    第二接入网设备根据所述第二消息，确定所述终端设备对应的组标识和所述终端设备的标识，所述组标识用于标识所述终端设备所属分组，所述终端设备的标识用于在所述终端设备所属分组内识别所述终端设备，所述终端设备的标识与所述终端设备的专用上下文对应；
    所述第二接入网设备向所述第一接入网设备发送第三消息，所述第三消息包括所述组标识和所述终端设备的标识；
    所述第二接入网设备从所述第一接入网设备接收第三响应消息，所述第三响应消息包 括所述专用上下文。
  9. 如权利要求8所述的方法，其特征在于，所述第三响应消息还包括与所述组标识对应的公共上下文。
  10. 如权利要求8至9所述的方法，其特征在于，所述第二消息包括所述终端设备的标识和所述组标识；或者，
    所述第二消息包括所述终端设备的标识，并且所述第二消息承载于与所述组标识对应的物理资源上。
  11. 如权利要求8至10中任一项所述的方法，其特征在于，所述第二请求消息还包括短的消息认证码完整性，所述短的消息认证码完整性是所述终端设备根据第一服务小区的物理小区标识、第二服务小区的小区标识和所述组标识确定的。
  12. 如权利要求8至11中任一项所述的方法，其特征在于，所述第三响应消息还包括下述中的至少一种：
    所述组标识对应的分组内的其他终端设备的专用上下文；
    所述组标识对应的终端设备的属性信息；
    其中，所述终端设备的属性信息包括下述信息中的至少一种：终端设备的业务的服务质量属性、终端设备的业务类型、终端设备的切片类型、终端设备的能力、终端设备是否静止、终端设备节电需求和终端设备的时延需求。
  13. 如权利要求8至12中任一项所述的方法，其特征在于，所述公共上下文包括下述信息中的至少一种：
    服务质量QoS属性、无线资源控制RRC配置、业务数据自适应协议SDAP配置、数据无线承载DRB配置、终端设备的能力和终端设备支持的安全参数类型。
  14. 如权利要求8-13中任一项所述的方法，其特征在于，所述第三消息包括指示信息，其中，所述指示信息用于指示是否请求与所述组标识对应的公共上下文，或者所述指示信息用于指示是否仅请求与所述终端设备的标识对应的专用上下文，或者所述指示信息用于指示是否请求所述终端设备的全部上下文。
  15. 一种通信方法，其特征在于，包括：
    第一接入网设备从第二接入网设备接收第三消息，所述第三消息包括终端设备对应的组标识和所述终端设备的标识，所述组标识用于标识所述终端设备所属分组，所述终端设备的标识用于在所述终端设备所属分组内识别所述终端设备，所述终端设备的标识与所述终端设备的专用上下文对应；
    所述第一接入网设备发送第三响应消息，所述第三响应消息包括所述专用上下文。
  16. 如权利要求15所述的方法，其特征在于，所述第三响应消息还包括与所述组标识对应的公共上下文。
  17. 如权利要求15或16所述的方法，其特征在于，所述第三响应消息还包括下述中的至少一种：
    所述组标识对应的分组内的其他终端设备的专用上下文；
    所述组标识对应的终端设备的属性信息；
    其中，所述终端设备的属性信息包括下述信息中的至少一种：终端设备的业务的服务质量属性、终端设备的业务类型、终端设备的切片类型、终端设备的能力、终端设备是否 静止、终端设备节电需求和终端设备的时延需求。
  18. 如权利要求15至17中任一项所述的方法，其特征在于，所述公共上下文包括下述信息中的至少一种：
    服务质量QoS属性、无线资源控制RRC配置、业务数据自适应协议SDAP配置、数据无线承载DRB配置、终端设备的能力和终端设备支持的安全参数类型。
  19. 如权利要求15-18任一项所述的方法，其特征在于，所述第三消息包括指示信息，其中，所述指示信息用于指示是否请求与所述组标识对应的公共上下文，或者所述指示信息用于指示是否仅请求与所述终端设备的标识对应的专用上下文，或者所述指示信息用于指示是否请求所述终端设备的全部上下文。
  20. 一种通信装置，其特征在于，所述通信装置用于实现如权利要求1至4中任一项所述的方法。
  21. 一种通信装置，其特征在于，所述通信装置用于实现如权利要求5至7中任一项所述的方法。
  22. 一种通信装置，其特征在于，所述通信装置用于实现如权利要求8至14中任一项所述的方法的单元。
  23. 一种通信装置，其特征在于，所述通信装置用于实现如权利要求15至19中任一项所述的方法。
  24. 一种存储介质，其特征在于，所存储介质存储用于实现如权利要求1至19中任一项所述的方法的指令。
PCT/CN2019/106173 2018-09-18 2019-09-17 通信方法和装置 WO2020057497A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP19863769.6A EP3840520B1 (en) 2018-09-18 2019-09-17 Communication method and apparatus
US17/203,992 US11963218B2 (en) 2018-09-18 2021-03-17 Communications method and communications apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811090248.6A CN110913507B (zh) 2018-09-18 2018-09-18 通信方法和装置
CN201811090248.6 2018-09-18

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/203,992 Continuation US11963218B2 (en) 2018-09-18 2021-03-17 Communications method and communications apparatus

Publications (1)

Publication Number Publication Date
WO2020057497A1 true WO2020057497A1 (zh) 2020-03-26

Family

ID=69813032

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/106173 WO2020057497A1 (zh) 2018-09-18 2019-09-17 通信方法和装置

Country Status (4)

Country Link
US (1) US11963218B2 (zh)
EP (1) EP3840520B1 (zh)
CN (1) CN110913507B (zh)
WO (1) WO2020057497A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112559252B (zh) * 2020-12-23 2021-09-03 广州技象科技有限公司 一种基于属性分类的配置数据管理方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102647667A (zh) * 2011-02-21 2012-08-22 华为技术有限公司 群组的管理方法及push服务器
CN102905252A (zh) * 2011-07-26 2013-01-30 中兴通讯股份有限公司 无线局域网中标识分配方法及装置
US20130189951A1 (en) * 2012-01-20 2013-07-25 Verizon Patent And Licensing Inc. Optimizing user device context for mobility management entity (mme) resiliency
CN106535135A (zh) * 2015-09-10 2017-03-22 大唐移动通信设备有限公司 一种集群业务实现方法及装置

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101222388B (zh) * 2007-01-12 2013-01-16 华为技术有限公司 一种确定接入点存在广播/多播缓存帧的方法和系统
CN102238512B (zh) 2010-04-29 2015-11-25 中兴通讯股份有限公司 机器类通信mtc的策略应用方法及策略和计费执行实体
CN102647665B (zh) * 2011-02-21 2015-02-04 华为技术有限公司 群组消息处理方法、设备及系统
EP2702823B1 (en) * 2011-04-29 2020-05-06 LG Electronics Inc. Channel access method and apparatus in wireless local area network system
US9473997B2 (en) * 2011-12-27 2016-10-18 Lg Electronics Inc. Method for offloading data in wireless communication system and apparatus for same
CN107637146A (zh) * 2015-06-23 2018-01-26 华为技术有限公司 一种寻呼的方法及装置
US20180295603A1 (en) * 2015-08-28 2018-10-11 Nokia Solutions And Networks Oy Data routing in cellular communication system
CN113938845B (zh) * 2018-05-21 2023-07-18 华为技术有限公司 上下文管理方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102647667A (zh) * 2011-02-21 2012-08-22 华为技术有限公司 群组的管理方法及push服务器
CN102905252A (zh) * 2011-07-26 2013-01-30 中兴通讯股份有限公司 无线局域网中标识分配方法及装置
US20130189951A1 (en) * 2012-01-20 2013-07-25 Verizon Patent And Licensing Inc. Optimizing user device context for mobility management entity (mme) resiliency
CN106535135A (zh) * 2015-09-10 2017-03-22 大唐移动通信设备有限公司 一种集群业务实现方法及装置

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
HUAWEI; HISILICON; TELECOM ITALIA; CHINA MOBILE; CATT: "Solution for Group Communication for IoT-V2X SIDs", 3GPP DRAFT; S2-188561-SOLUTION ON GROUP COMMUNICATION-GROUPCAST FOR IOT-V2X SIDS, vol. SA WG2, 26 August 2018 (2018-08-26), Sophia Antipolis, France, pages 1 - 12, XP051537412 *
NOKIA; ALCATEL-LUCENT SHANGHAI BELL: "Fl-C UE associated functions", 3GPP TSG RAN WG3 ADHOC NR R3-172330, vol. RAN WG3, 29 June 2017 (2017-06-29), Qingdao, China, pages 1 - 3, XP051307739 *
See also references of EP3840520A4

Also Published As

Publication number Publication date
EP3840520B1 (en) 2024-03-27
EP3840520A4 (en) 2021-11-03
EP3840520A1 (en) 2021-06-23
US20210204314A1 (en) 2021-07-01
US11963218B2 (en) 2024-04-16
CN110913507B (zh) 2023-04-18
CN110913507A (zh) 2020-03-24

Similar Documents

Publication Publication Date Title
US11606786B2 (en) Data transmission method, terminal device, and access network device
CN112910913B (zh) 一种会话建立的方法和网络系统
US20220330361A1 (en) Method for establishing connection and obtaining relay service code and communications apparatus
WO2019056383A9 (zh) 资源配置的方法、终端设备和网络设备
WO2017166141A1 (zh) 数据传输的方法、终端及基站
US11470674B2 (en) Communication method and communications apparatus
WO2020221223A1 (zh) 通信方法、装置和系统
US11259362B2 (en) Method for repeatedly transmitting data and device
US20220272577A1 (en) Communication method and communication apparatus
WO2021000701A1 (zh) 一种通信方法及相关设备
WO2020057497A1 (zh) 通信方法和装置
WO2018145292A1 (zh) 通信方法、装置和系统
WO2023024931A1 (zh) 用于设备间通信的方法和装置
WO2018054336A1 (zh) 消息的发送方法和装置
US20210250850A1 (en) Network access method and apparatus
WO2021088090A1 (zh) 接入控制方法及通信装置
CN108064088B (zh) Rrc连接释放方法、终端、接入网设备及存储介质
WO2020087546A1 (zh) 一种网络信息传输方法、获取方法、网络设备及终端设备
EP4277432A2 (en) Control plane latency reduction in a wireless communication network
WO2022205444A1 (zh) 广播消息的发送方法、接收方法、装置、设备及存储介质
WO2024027260A1 (zh) 通信方法、终端、通信装置及存储介质
TWI838071B (zh) 用於中繼節點標識符獲取的方法及其使用者設備
WO2022160275A1 (zh) 无线通信方法、设备及存储介质
WO2023108564A1 (zh) 无线通信方法、终端设备以及网络设备
US20240155325A1 (en) Information obtaining method and apparatus, and system

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019863769

Country of ref document: EP

Effective date: 20210315